Tiny Core Base > TCB Talk

ASUS NUC 14

<< < (2/4) > >>

Rich:
Hi bohfoitoch
Install pciutils.tcz.

What do these 2 commands return:

--- Code: ---lspci -nn
modinfo r8169
--- End code ---

bohfoitoch:
I installed pciutils.tcz, but still not eth0


--- Code: ---intree:         Y
vermagic:       6.12.11-tinycore64 SMP mod_unload
firmware:       rtl_nic/rtl18126a-3.fw
firmware:       rtl_nic/rtl18126a-2.fw
firmware:       rtl_nic/rtl18125b-2.fw
firmware:       rtl_nic/rtl18125a-3.fw
firmware:       rtl_nic/rtl1810?e-2.fw
firmware:       rtl_nic/rtl18168?p-3.fw
firmware:       rtl_nic/rtl18168h-3.fw
firmware:       rtl_nic/rtl18168g-3.fw
firmware:       rtl_nic/rtl18106e-2.fw
firmware:       rtl_nic/rtl18106e-1.fw
firmware:       rtl_nic/rtl18411-2.fw
firmware:       rtl_nic/rtl18411-1.fw
firmware:       rtl_nic/rtl18402-1.fw
firmware:       rtl_nic/rtl18168f-1.fw
firmware:       rtl_nic/rtl18105e-1.fw
firmware:       rtl_nic/rtl18168e-3.fw
firmware:       rtl_nic/rtl18168e-2.fw
firmware:       rtl_nic/rtl18168e-1.fw
firmware:       rtl_nic/rtl18168d-2.fw
firmware:       rtl_nic/rtl18168d-1.fw

--- End code ---

GNUser:
Hi bohfoitoch. The firmware files included in the firmware extensions can sometimes change over time.

Maybe the driver is failing to find the firmware it needs? We should exclude that possibility. Please run these commands:


--- Code: ---tce-load -wi firmware-rtl_nic
sudo modprobe r8169

--- End code ---
then run this command and kindly post its output here:


--- Code: ---dmesg | grep firmware
--- End code ---

bohfoitoch:
This is the output of lspci -nn:
00:02.0 VGA compatible controller [0300]: Intel Corporation Alder Lake-N [Intel Graphics] [8086:46d4]
00:04.0 Signal processing controller [1180]: Intel Corporation Alder Lake Innovation Platform Framework Processor Participant [8086:461d]
00:08.0 System peripheral [0880]: Intel Corporation GNA Scoring Accelerator [8086:467e]
00:0a.0 Signal processing controller [1180]: Intel Corporation Platform Monitoring Technology [8086:467d] (rev 01)
00:0d.0 USB controller [0c03]: Intel Corporation Alder Lake-N Thunderbolt 4 USB Controller [8086:46e4]
00:12.0 Serial controller [0700]: Intel Corporation Device [8086:54fc]
00:14.0 USB controller [0c03]: Intel Corporation Alder Lake-N PCH USB 3.2 xHCI Host Controller [8086:54ed]
00:14.2 RAM memory [0500]: Intel Corporation Alder Lake-N PCH Shared SRAM [8086:54ef]
00:14.3 Network controller [0280]: Intel Corporation CNVi: Wi-Fi [8086:54f0]
00:16.0 Communication controller [0780]: Intel Corporation Alder Lake-N PCH HECI Controller [8086:54e0]
00:1c.0 PCI bridge [0604]: Intel Corporation Alder Lake-N PCI Express Root Port #7 [8086:54be]
00:1f.0 ISA bridge [0601]: Intel Corporation Alder Lake-N PCH eSPI Controller [8086:5481]
00:1f.3 Multimedia audio controller [0401]: Intel Corporation Alder Lake-N PCH High Definition Audio Controller [8086:54c8]
00:1f.4 SMBus [0c05]: Intel Corporation Alder Lake-N SMBus [8086:54a3]
00:1f.5 Serial bus controller [0c80]: Intel Corporation Alder Lake-N SPI (flash) Controller [8086:54a1]
01:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:8125] (rev 0c)


sudo modprobe r8169
error -ENODEV: unknown chip XID 688, contact r8169 maintainers

dmesg | grep firmware returns nothing

GNUser:
Usually there's a firmware load error in dmesg when the problem is missing firmware. So missing firmware is probably not the culprit here.

The ENODEV error suggests that the r8169 driver is seeing your hardware but not recognizing its XID. Then the driver is probably bailing out without even trying to load the firmware, because it needs to recognize the specific device in order to determine the necessary firmware file.

If your ethernet hardware worked with TCL before (presumably when using an older TCL version), I think this points to a regression/bug in the r8169 driver.

I'm afraid you may be in for a headache. You'd probably have to find a patch for the driver that fixes this bug, recompile the driver, then tweak your TCL to use the recompiled driver rather than the upstream version. It may be easier to use different hardware or, if you are married to this hardware, to use the older TCL version whose r8169 driver was working well for you.

Navigation

[0] Message Index

[#] Next page

[*] Previous page