Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller
Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev ff) (prog-if ff) !!! Unknown header type 7f
kernel 2.6.21.5 module r8169 Exact. This is. I can't get it working. Tell me what information may be needed. Thanks to all. |
There are many similar threads on the internet.
Try to check them for possible solution. |
Do these in a command prompt as root:
$ifconfig $lsmod and post the output. Does $ifconfig eth0 up make it work? |
Sorry for the delay, here is ifconfig
Code:
Morphy documentation # ifconfig eth0 Code:
Morphy documentation # lsmod |
You might be running on a dhcp server, plug in the ethernet cable to your PC and type in as root either;
/etc/rc.d/rc.inet1 eth0_restart or ifconfig eth0 up dhcpcd eth0 if it works but it doesn't work on startup, then your /etc/rc.d/rc.inet1 isn't activated. as root; chmod +x /etc/rc.d/rc.inet1 |
The correct module is loaded and an interface appears in `ifconfig` output, meaning it is active. It just isn't configured. Have you run `netconfig` as root (or alternatively edit /etc/rc.d/rc.inet1.conf manually and restart the network interface)? I've had some problems with RealTek cards that required manually defining some connection attributes, but I don't know if it affects that card. See `man ethtool` if netconfig doesn't get it working (you may have to set the duplex and set the speed of the connection -- and turn autoneg off. You would have to try all of the combinations of half/full duplex and 1000/100/10 Mbps speed). Hopefully that isn't a problem on your card though.
|
I have a similar card
Code:
04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02) Code:
lsmod | grep 816 The issue I had, the ethernet device would be recognized, sometimes get an IP, sometimes not. Then when it did get an IP, after some time, it would drop it. For other RTL8169 cards, the default r8169 module works fine. Code:
02:0a.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet (rev 10) |
Ok, I downloaded r8169-6.008.00.tar.bz2 from the link of Realtek but you adviced me not to istall r8169 but r8168. I read somewhere that both modules work fine with our card. Should I try the one I downloaded?
|
On my HP lappy the wireless card is detected as eth0 and the IP address from netconfig gets assigned to it. So wired networking doesn't work as eth1 doesn't have an address. I have to edit /etc/rc.d/rc.inet1.conf , delete the eth0 values and put them in eth1.
|
I have same onboard NIC, I think.
as root: lspci shows RTL8111/8168B... lsmod shows r8169. This worked for me using slack12.1 with the 2.6.24.5 kernel and I haven't had any problems since. I have the 2.6.25.20, 2.6.26.8 and 2.6.27.6 kernels and it works for all of them. But, I reread your inital post and see 2.6.21.. indicating slackware 12.0? The header error message also suggests problem. First recommendation is to upgrade to slackware 12.1. If you don't want to do that get newer kernel. I would go with at least 2.6.25.11 but you should probably go with latest in 2.6.25 series. I'm having some problems with 2.6.26 and can't yet recommend. If you want you can try to install the r8169 you downloaded. Post if it works. |
Err.. that NIC has been supported ever since 2.6.18. I should know because I have been using this type of NIC for the last three years.
|
Quote:
|
Quote:
Don't see how it's possible your R8168 card was support with a vanilla kernel prior to 2.26.3, here's from that changelog Quote:
2.26.5 does support some of the r8168 cards. But not all. There have been a plethoria of patches to the r8169 driver. 2.6.26.3 may have fixed the issue with my r8168, but I don't feel like updating the kernel again, as the Realtek drivers work just fine. Quote:
Quote:
|
Quote:
As for the type that came out only this year, you must be referring to the 8111C (mind the C, not B). Yes, it is quite possible that support was simply patched on (note that the NIC used the r8169 or r1000 module at the time) but then nearly all distros did it (I think Slackware is the only major distro I did not give a spin back then; of all the rest, only Gentoo took somewhat longer to support the r8168). As for the issues you mention, yes, I had those too when I reached 2.6.24 but not before (the realtek driver worked fine, though). Right now, I am not sure what is happening. Either my modem is dying or the driver still does not work properly because I have been experiencing the occasional glitch again those lost few days... |
Quote:
I'm using the gigabyte 780g board. With the stock slackware 12.1 some of the PCI components showed up as unknown but they basically all worked. Using this NIC with stock drivers, I upgraded kernel. After 2.6.25 the PCI components are identified and no longer labeled as unknown. There's never been any problem with the NIC. In all cases, the module r8169 is used and worked well with the NIC that shows up in lspci as RTL8111/8168B.. |
All times are GMT -5. The time now is 02:47 PM. |