Ethernet Products
Determine ramifications of Intel® Ethernet products and technologies
5236 Discussions

[Agilex]: igb probe failed with error -13

raju1421
New Contributor I
2,014 Views

Dear Intel Team,

We are currently encountering an issue with our Intel Agilex 7 SoC Development Kit connected to an I210-T1 Ethernet Server Adapter during the Linux boot-up process.

The error message we are encountering is as follows:

[ 1.384867] igb: Copyright (c) 2007-2014 Intel Corporation.

[ 1.390565] igb 0000:01:00.0: enabling device (0000 -> 0002)

[ 1.403729] igb: probe of 0000:01:00.0 failed with error -13

We kindly request your guidance and support to help us resolve this issue.

 

Thanks & Regards

Satrasala Raju

0 Kudos
1 Solution
IntelSupport
Community Manager
1,945 Views

Hello raju1421,

 

It seems like there is a compiler mismatch.

 

Ensure that the kernel source headers you are using match the kernel version running on your target system. If there is a mismatch, it can lead to compilation errors.

Did you check the information and the support on The Yocto Project as well?

 

Kindly let us know if you have any questions.

 

Regards,

Hayat

Intel Customer Support


View solution in original post

0 Kudos
8 Replies
IntelSupport
Community Manager
1,963 Views

Hello raju1421,

 

Thank you for posting in Intel Community.

 

Can we confirm that you have the latest kernel and drivers up to date?

 

If the driver is not up to date, please check and update your driver here: Intel® Ethernet Adapter Complete Driver Pack

 

Can you please specify the OS you are using.

 

Can I also get an output for the command:

dmesg | grep igb

modprobe -r igb

modprobe igb

lspci -v

 

Kindly let us know if you have any questions.

 

Regards,

Hayat

Intel Customer Support


0 Kudos
raju1421
New Contributor I
1,961 Views

Hi,

Thank you for your response.
We are utilizing files from Rocketboards Agilex PCIe Root Port Documentation.
https://www.rocketboards.org/foswiki/Documentation/AgilexPcieRootPort

Below are the details 

root@agilexfm61:~# uname -r
5.15.90-156414-g0b11acba1131-dirty
root@agilexfm61:~# cat /proc/version
Linux version 5.15.90-156414-g0b11acba1131-dirty (root@Precision-3650) (aarch64-none-linux-gnu-gcc (GNU Toolchain for the Arm Architecture 11.2-2022.02 (arm-11.14)) 11.2.1 20220111, GNU ld (GNU Toolchain for the Arm Architecture 11.2-2022.02 (arm-11.14)) 2.37.20220122) #1 SMP PREEMPT Fri Nov 17 14:05:48 IST 2023
root@agilexfm61:~# dmesg | grep igb
[ 1.379324] igb: Intel(R) Gigabit Ethernet Network Driver
[ 1.384710] igb: Copyright (c) 2007-2014 Intel Corporation.
[ 1.390404] igb 0000:01:00.0: enabling device (0000 -> 0002)
[ 1.403556] igb: probe of 0000:01:00.0 failed with error -13
[ 1.409292] igbvf: Intel(R) Gigabit Virtual Function Network Driver
[ 1.415549] igbvf: Copyright (c) 2009 - 2012 Intel Corporation.
root@agilexfm61:~# modprobe -r igb
modprobe: FATAL: Module igb not found.
root@agilexfm61:~# modprobe igb
modprobe: FATAL: Module igb not found in directory /lib/modules/5.15.90-156414-g0b11acba1131-dirty
root@agilexfm61:~# cat /etc/os-release
ID=poky
NAME="Poky (Yocto Project Reference Distro)"
VERSION="4.1.3 (langdale)"
VERSION_ID=4.1.3
PRETTY_NAME="Poky (Yocto Project Reference Distro) 4.1.3 (langdale)"
DISTRO_CODENAME="langdale"

 

Thanks & Regards

Satrasala Raju

0 Kudos
IntelSupport
Community Manager
1,959 Views

Hello raju1421,

 

Can we confirm that you have the latest kernel and drivers up to date?

 

If the driver is not up to date, please check and update your driver here: Intel® Ethernet Adapter Complete Driver Pack

According to The Yocto Project here, it seems like you are currently using the Langdale which has already been EOL.

I would suggest you to consider reaching out to the Yocto Project community or support channels for assistance. They may be able to provide guidance on resolving module-related issues specific to Yocto Project.

Kindly let us know if you have any questions.

 

Regards,

Hayat

Intel Customer Support


0 Kudos
raju1421
New Contributor I
1,955 Views

Hi,

Thank you for your response.

After downloading the latest drivers, we also obtained the ARM cross-compiler from the previously mentioned link.

However, we are encountering errors during  compilation process.

 

filtering include/net/flow_keys.h out
filtering include/linux/jump_label_type.h out
filtering include/linux/jump_label_type.h out
*** The target kernel has CONFIG_MODULE_SIG_ALL enabled, but
*** the signing key cannot be found. Module signing has been
*** disabled for this build.
make[1]: Entering directory '/usr/src/linux-headers-6.2.0-34-generic'
warning: the compiler differs from the one used to build the kernel
The kernel was built by: x86_64-linux-gnu-gcc-11 (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
You are using:
CC [M] /src/igb_main.o
/bin/sh: line 1: aarch64-none-linux-gnu-gcc-11: command not found
make: *** [Makefile:87: default] Error 2

 

Thanks & Regards

Satrasala Raju

 

0 Kudos
IntelSupport
Community Manager
1,946 Views

Hello raju1421,

 

It seems like there is a compiler mismatch.

 

Ensure that the kernel source headers you are using match the kernel version running on your target system. If there is a mismatch, it can lead to compilation errors.

Did you check the information and the support on The Yocto Project as well?

 

Kindly let us know if you have any questions.

 

Regards,

Hayat

Intel Customer Support


0 Kudos
IntelSupport
Community Manager
1,873 Views

Hello raju1421,

 

Regarding your thread, we are following up to find out if you were able to complete the actions, we previously recommended.

 

Please reply to this thread to confirm, so we can continue helping with a resolution. Looking forward to receiving your reply!


Else if none, kindly confirm the thread closure.

 

Thank you.

 

Regards,

Hayat

Intel® Customer Support


0 Kudos
raju1421
New Contributor I
1,869 Views

Hi 

 

Thank you,

 

Close the Thread.

 

Regards

Satrasala Raju

0 Kudos
IntelSupport
Community Manager
1,866 Views

Hi raju1421,


Thank you for your confirmation.


We will proceed for the thread closure.


Once the thread is closed, it will no longer be monitored by Intel


Kindly reopen a new thread if you have further questions.


Regards,

Hayat

Intel Customer Support






0 Kudos
Reply