- Arch Linux
- #1 2020-03-08 09:25:59
- Intel LAN driver incompatible with kernel
- #2 2020-03-08 11:46:34
- Re: Intel LAN driver incompatible with kernel
- #3 2020-03-08 13:58:21
- Re: Intel LAN driver incompatible with kernel
- #4 2020-03-09 11:27:59
- Re: Intel LAN driver incompatible with kernel
- missing linux/pci-aspm.h in latest Linux release candidate #19
- Comments
- stuart-little commented Sep 25, 2019 •
- rockyprabowo commented Nov 2, 2019
- simonbcn commented Dec 3, 2019
- r900 commented Dec 22, 2019
- Fatal error linux pci aspm h no such file or directory
- Ошибки PCIe Bus Error: severity=Corrected при выключении в Linux
- fatal error: sys/wait.h: No such file or directory #1086
- Comments
- zhou0 commented Dec 20, 2017
- include
- zhou0 commented Dec 21, 2017 •
- include
- cbrt64 commented Jan 12, 2018
- amaau commented Apr 9, 2018
- mati865 commented Apr 9, 2018
- amaau commented Apr 9, 2018
- LinshuH commented Apr 21, 2019 •
- StarWolf3000 commented Apr 21, 2019 •
- Alexpux commented Apr 21, 2019 •
- kovalexpro commented Aug 14, 2020 •
- mati865 commented Aug 14, 2020
- kovalexpro commented Aug 14, 2020
- StarWolf3000 commented Aug 14, 2020
- mati865 commented Aug 14, 2020 •
- yuki-kimoto commented Mar 11, 2021 •
Arch Linux
You are not logged in.
#1 2020-03-08 09:25:59
Intel LAN driver incompatible with kernel
Errors on compiling network driver for
Intel I211AT LAN
As I understand current kernel release
have no linux/pci-aspm.h
all functions moved to linux/pci.h
Move ASPM definitions and function prototypes from include/linux/pci-aspm.h
to include/linux/pci.h so users only need to include
:
PCIE_LINK_STATE_L0S
PCIE_LINK_STATE_L1
PCIE_LINK_STATE_CLKPM
pci_disable_link_state()
pci_disable_link_state_locked()
pcie_no_aspm()
User can edit intel driver src file kcompat.h
replace pci-aspm.h with linux/pci.h
problem on Kernel and Kernel-Headers: 5.5.6, 5.5.8
How to solve it? Any patch?
Last edited by mashrum (2020-03-08 11:34:03)
#2 2020-03-08 11:46:34
Re: Intel LAN driver incompatible with kernel
The igb kernel module is included in the archlinux kernels , why are you trying to build an older version ?
Post lspci -knn please.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
Did you use the guided installer ? If yes, I can’t help you.
(A works at time B) && (time C > time B ) ≠ (A works at time C)
#3 2020-03-08 13:58:21
Re: Intel LAN driver incompatible with kernel
I was not be sure that build-in version is actual
[root@fobot-01 maxim]# lspci -knn
00:00.0 Host bridge [0600]: Intel Corporation Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register [8086:0f00] (rev 11)
Subsystem: Intel Corporation Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register [8086:7270]
Kernel driver in use: iosf_mbi_pci
00:02.0 VGA compatible controller [0300]: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 11)
Subsystem: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:7270]
Kernel driver in use: i915
Kernel modules: i915
00:13.0 IDE interface [0101]: Intel Corporation Atom Processor E3800 Series SATA IDE Controller [8086:0f21] (rev 11)
Subsystem: Intel Corporation Atom Processor E3800 Series SATA IDE Controller [8086:7270]
Kernel driver in use: ata_piix
Kernel modules: ata_piix, pata_acpi, ata_generic
00:1a.0 Encryption controller [1080]: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Trusted Execution Engine [8086:0f18] (rev 11)
Subsystem: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Trusted Execution Engine [8086:7270]
Kernel driver in use: mei_txe
Kernel modules: mei_txe
00:1b.0 Audio device [0403]: Intel Corporation Atom Processor Z36xxx/Z37xxx Series High Definition Audio Controller [8086:0f04] (rev 11)
Subsystem: Intel Corporation Atom Processor Z36xxx/Z37xxx Series High Definition Audio Controller [8086:7270]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
00:1c.0 PCI bridge [0604]: Intel Corporation Atom Processor E3800 Series PCI Express Root Port 1 [8086:0f48] (rev 11)
Kernel driver in use: pcieport
00:1c.1 PCI bridge [0604]: Intel Corporation Atom Processor E3800 Series PCI Express Root Port 2 [8086:0f4a] (rev 11)
Kernel driver in use: pcieport
00:1c.2 PCI bridge [0604]: Intel Corporation Atom Processor E3800 Series PCI Express Root Port 3 [8086:0f4c] (rev 11)
Kernel driver in use: pcieport
00:1c.3 PCI bridge [0604]: Intel Corporation Atom Processor E3800 Series PCI Express Root Port 4 [8086:0f4e] (rev 11)
Kernel driver in use: pcieport
00:1d.0 USB controller [0c03]: Intel Corporation Atom Processor Z36xxx/Z37xxx Series USB EHCI [8086:0f34] (rev 11)
Subsystem: Intel Corporation Atom Processor Z36xxx/Z37xxx Series USB EHCI [8086:7270]
Kernel driver in use: ehci-pci
Kernel modules: ehci_pci
00:1f.0 ISA bridge [0601]: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Power Control Unit [8086:0f1c] (rev 11)
Subsystem: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Power Control Unit [8086:7270]
Kernel driver in use: lpc_ich
Kernel modules: lpc_ich
00:1f.3 SMBus [0c05]: Intel Corporation Atom Processor E3800 Series SMBus Controller [8086:0f12] (rev 11)
Subsystem: Intel Corporation Atom Processor E3800 Series SMBus Controller [8086:7270]
Kernel driver in use: i801_smbus
Kernel modules: i2c_i801
01:00.0 Ethernet controller [0200]: Intel Corporation I211 Gigabit Network Connection [8086:1539] (rev 03)
Subsystem: Intel Corporation I211 Gigabit Network Connection [8086:0000]
Kernel driver in use: igb
Kernel modules: igb
02:00.0 Ethernet controller [0200]: Intel Corporation I211 Gigabit Network Connection [8086:1539] (rev 03)
Subsystem: Intel Corporation I211 Gigabit Network Connection [8086:0000]
Kernel modules: igb
#4 2020-03-09 11:27:59
Re: Intel LAN driver incompatible with kernel
I suggest you try with the built-in version first.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
Did you use the guided installer ? If yes, I can’t help you.
(A works at time B) && (time C > time B ) ≠ (A works at time C)
Источник
missing linux/pci-aspm.h in latest Linux release candidate #19
Comments
stuart-little commented Sep 25, 2019 •
r8168_n.c includes linux/pci-aspm.h:
The problem: the latest releases of the Linux kernel remove that file from the tree. For instance, there’s
r8168_n.c already includes linux/pci.h unconditionally, so it should be fine on this front. I do however get a number of warnings when I comment out the #include
in r8168_n.c (different issue).
The text was updated successfully, but these errors were encountered:
rockyprabowo commented Nov 2, 2019
I think this repo doesn’t accept any kind of patches, it only publish/mirror the official release from Realtek. So you need to fork and patch the source by yourself or wait for a new official version from Realtek.
If you really need to build this on your own, you can checkout my fork: https://github.com/rockyprabowo/r8168
I’ll try my best to keep up with any changes introduced by upcoming Linux release.
simonbcn commented Dec 3, 2019
@rockyprabowo the problem is that the sources in your repository are not up to date. The last version is 8.047.05 and in your repository the last version is 8.047.04 .
r900 commented Dec 22, 2019
@simonbcn 8.047.05 has the same problem, this little patch here helps for now: https://701200.bugs.gentoo.org/attachment.cgi?id=600406
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
Источник
Fatal error linux pci aspm h no such file or directory
Installed latest Ubuntu 20.04 the other day, and ever since my Intel X520-T2 is throwing billions of «Warning firmware error detected FWSM: 0x00000000» errors. So I thought an update from the old ixgbe 5.1.0-k that is shipped with Ubuntu to the latest ixgbe 5.6.5 were in order, but the thing is it can’t be compiled. Fails with the following error: «fatal error: linux/pci-aspm.h: No such file or directory # include
«
Read that recently the linux/pci-aspm.h header file was removed from the kernel source or something, hence it’s failing. Ubuntu 20 uses kernel 5.4 and latest available ixgbe drivers are supported up to kernel 5.3.
Anyone here that can provide a quick fix for this maybe?
Best regards, marcus!
- Отметить как новое
- Закладка
- Подписаться
- Отключить
- Подписка на RSS-канал
- Выделить
- Печать
- Электронная почта другу
- Сообщить о недопустимом содержимом
Thank you for posting in our Intel® Ethernet Communities Forum.
To provide you the best suggestion, please provide the following information;
1. Please confirm the Distro and Version of the Linux OS that you are using and please provide any additional configuration that you added.
To set your expectations, we may need some time to investigate on this one after you provide the information above.
Looking forward to your reply, should we not get your reply, we will follow up with you after 3 business days.
Intel Customer Support
- Отметить как новое
- Закладка
- Подписаться
- Отключить
- Подписка на RSS-канал
- Выделить
- Печать
- Электронная почта другу
- Сообщить о недопустимом содержимом
Hi, AlfredS_Intel and thanks for you answer.
I’m using the latest Ubuntu 20.04 LTS (Focal Fossa) server with kernel version 5.4.0-26 and this is a fresh install with no additional configurations added that could have any impact on the ixgbe driver build process.
Your Intel ixgbe 5.6.5 package supports Ubuntu up to 19.10 — 5.3.*-* kernel version, but nothing newer. This I know because I just made a fresh Ubuntu 19.10 VmWare install and built/compiled the ixgbe 5.6.5 driver there without any problems.
There’s been some changes made in Ubuntu 20.04 that rendered the driver impossible to install without you guys (Intel) updating the code.
I’m hoping for the best here. Thanks in advance!
To make it more clear, this is the driver package:
Источник
Ошибки PCIe Bus Error: severity=Corrected при выключении в Linux
После обновления Linux, при следующем выключении компьютера на экран повалилась куча одинаковых сообщений об ошибке: «pcieport 0000:00:1c.3: PCIe Bus Error: severity=Corrected, type=Physical Layer«. Причём длится это безобразие довольно долго, так что рука тянется принудительно выключить компьютер с кнопки, что я пару раз и проделал, пока не нашёл решения проблемы.
Как я уже сказал выше, выключение или перезагрузка компьютера стала адовой процедурой — лог повторяющихся ошибок бежал по экрану в течении (!) двух минут. Оказалось, что данная проблема постигла практически всех владельцев интеловских процессоров и, по всей видимости, связана с попытками понизить питание на порту PCIe. На тематических Linux-форумах предлагается добавить следующие два параметра при загрузке ядра:
pci = nomsi — отключает использование прерываний MSI;
pci = noaer — отключает расширенный отчёт об ошибках ядра.
Однако, возвращаться к использованию устаревших методов доставки прерываний мне совсем не хотелось — костыли, так себе. Решил пойти другим путём и просто отключить технологию ASPM (Active-State Power Management).
ASPM позволяет управлять энергопотреблением шин PCI Express (PCIe) посредством их перевода в энергосберегающий режим, если устройство не используются. В то же время, активация ASPM приводит к задержке ответа от устройств, так как требуется некоторое время на переключение режимов работы шины.
Поведением ASPM можно управлять, добавив параметр pcie_aspm в загрузчик или внеся изменения в файле /sys/module/pcie_aspm/parameters/policy (pcie_aspm=off отключает ASPM, а pcie_aspm=force принудительно задействует, даже на поддерживающих технологию устройствах). Я подправил загрузчик GRUB:
В моём случае, ошибку выдавал встроенный Wi-Fi адаптер, который в принципе не отличался стабильностью в работе и постоянно отваливался. Отдельно отключить энергосбережение для WiFi поможет продвинутая консольная утилита для управления питанием TLP (/etc/default/tlp):
Если считаете статью полезной,
не ленитесь ставить лайки и делиться с друзьями.
Источник
fatal error: sys/wait.h: No such file or directory #1086
Comments
zhou0 commented Dec 20, 2017
D:/msys32/usr/lib/perl5/core_perl/CORE/perl.h:804:13: fatal error: sys/wait.h: No such file or directory
include
The text was updated successfully, but these errors were encountered:
zhou0 commented Dec 21, 2017 •
I have msys2-devel and msys2-runtime-devel installed. This error blocks a lot of Perl modules from compiling, an example looks like
Running install for module ‘Unicode::UTF8’
Checksum for /home/Li ZHOU/.cpan/sources/authors/id/C/CH/CHANSEN/Unicode-UTF8-0.62.tar.gz ok
Configuring C/CH/CHANSEN/Unicode-UTF8-0.62.tar.gz with Makefile.PL
Checking if your kit is complete.
Looks good
Generating a Unix-style Makefile
Writing Makefile for Unicode::UTF8
Writing MYMETA.yml and MYMETA.json
CHANSEN/Unicode-UTF8-0.62.tar.gz
/usr/bin/perl Makefile.PL INSTALLDIRS=site — OK
Running make for C/CH/CHANSEN/Unicode-UTF8-0.62.tar.gz
cp lib/Unicode/UTF8.pod blib/lib/Unicode/UTF8.pod
cp lib/Unicode/UTF8.pm blib/lib/Unicode/UTF8.pm
Running Mkbootstrap for Unicode::UTF8 ()
chmod 644 «UTF8.bs»
«/usr/bin/perl.exe» «-Iinc» «/usr/share/perl5/core_perl/ExtUtils/xsubpp» -typemap «/usr/share/perl5/core_perl/ExtUtils/typemap» UTF8.xs > UTF8.xsc && mv UTF8.xsc UTF8.c
gcc -c -I. -DPERL_USE_SAFE_PUTENV -D_GNU_SOURCE -U__STRICT_ANSI__ -march=i686 -mtune=generic -O2 -pipe -fwrapv -fno-strict-aliasing -fstack-protector-strong -DUSEIMPORTLIB -march=i686 -mtune=generic -O2 -pipe -DVERSION=»0.62″ -DXS_VERSION=»0.62″ «-I/usr/lib/perl5/core_perl/CORE» UTF8.c
In file included from UTF8.xs:3:0:
D:/msys32/usr/lib/perl5/core_perl/CORE/perl.h:804:13: fatal error: sys/wait.h: No such file or directory
include
compilation terminated.
make: *** [Makefile:343:UTF8.o] 错误 1
CHANSEN/Unicode-UTF8-0.62.tar.gz
make — NOT OK
cbrt64 commented Jan 12, 2018
Just throwing out an idea; maybe you’re using the MINGW32 shell instead of MSYS shell? The former can’t find sys/foo.h because that’s in /usr/include , which is normally only used in MSYS.
I learned this myself the hard way. 🙂
amaau commented Apr 9, 2018
there’s no sys/wait.h in windows
mati865 commented Apr 9, 2018
amaau commented Apr 9, 2018
@mati865 right, my mistake
LinshuH commented Apr 21, 2019 •
@mati865 when I do
sudo apt-get install msys2-runtime-devel it shows «cannot locate package.
When I try to install by the url by
sudo add-apt-repository http://repo.msys2.org/msys/i686/msys2-runtime-devel-3.0.6-1-i686.pkg.tar.xz
it shows the repository can’t be authenticated
Then I open sources.list by sudo vim /etc/apt/sources.list
and add one line
deb [trusted=yes] http://repo.msys2.org/msys/i686/msys2-runtime-devel-3.0.6-1-i686.pkg.tar.xz jessie main
I save the file, run the sudo add-apt-repository [that long url] command again, and see the error message
«E: The repository ‘http://repo.msys2.org/msys/i686/msys2-runtime-devel-3.0.6-1-i686.pkg.tar.xz bionic Release’ does not have a Release file. N: Updating from such a repository can’t be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: The repository ‘http://repo.msys2.org/msys/i686/msys2-runtime-devel-3.0.6-1-i686.pkg.tar.xz jessie Release’ does not have a Release file. N: Data from such a rep
»
Then I want to use «—allow-unauthenticated» to bypass the security setting, however, apt-add-repository does not have this flag, I wonder how to install package «msys2-runtime-devel» by Ubuntu, Linux subsystem for windows?
Also, I also try directly download the package by command pacman -S msys2-runtime-devel , it says «no display possible».
Are there suggest how can I use package msys2-runtime-devel?
StarWolf3000 commented Apr 21, 2019 •
@LinshuH There are several issues here with what you’re doing:
- You are trying to add a pacman repository to a dpkg/APT-based package manager. Of course that won’t work.
- Even if it would work, then you’re doing it wrong: You need to add the repository url to the sources.list, not a single package like you did.
- Why would you want to run Windows binaries directly inside the Linux subsystem on Windows? MSYS2 and MINGW are to be run directly on Windows.
Just forget about the Ubuntu subsystem and install MSYS2 directly on Windows, it is not supposed to be run inside a Linux distribution, it makes everything more complicated.
Alexpux commented Apr 21, 2019 •
@LinshuH msys2 use pacman package manager ported from Arch Linux.
Read wiki before posting such noob questions
kovalexpro commented Aug 14, 2020 •
Seems like GCC under MSYS2 does not look up /usr/include :
Adding /usr/include manually helps my toy example:
mati865 commented Aug 14, 2020
@kovalexpro you posted output of mingw-w64-x86_64-gcc.
kovalexpro commented Aug 14, 2020
@mati865 Sure, do I have any other compiler under MSYS2? Or do you mean that ming32 would work while migw64 would not?
I’m trying to build cross compiler under MSYS2 now and hit same issue as reported. I would expect gcc to look under regular folders like /usr/include for build/host compilation at least.
StarWolf3000 commented Aug 14, 2020
MSYS2 has it’s own compiler set.
mati865 commented Aug 14, 2020 •
@kovalexpro There are 3 subsystems:
Each of them have its own compiler and you cannot mix headers and libraries from different subsystems and expect things to work.
yuki-kimoto commented Mar 11, 2021 •
Hi, I want to install Perl XS module. XS means C language extension.
I get the same error as this topic.
Strawberry Perl can install this SPVM module.
Источник