R8169 on thinkpad 600 not working

linuxhaxz · 12-09-2006, 04:24 AM

As the title, i have an Ibm Thinkpad 600 and a Realtek rtl8169 pcmcia network card.

After much searching and experimenting i found several options that could help if they were passed to the kernel.

I have managed to get the card detected and the modules loaded by passing

Code:

pci=noacpi 
pci=noirq

to the kernel, however it still does not get an ip address, either from my router, or even if i plug it directly into my cable modem.

Dmesg reports that the link is not ready

Code:

i2c_core: exports duplicate symbol i2c_register_driver (owned by kernel)
PCI: Found IRQ 11 for device 0000:00:02.0
PCI: Sharing IRQ 11 with 0000:00:03.0
Yenta: CardBus bridge found at 0000:00:02.0 [1014:0092]
Yenta: Enabling burst memory read transactions
Yenta: Using CSCINT to route CSC interrupts to PCI
Yenta: Routing CardBus interrupts to PCI
Yenta TI: socket 0000:00:02.0, mfunc 0xfba97543, devctl 0x62
Yenta: ISA IRQ mask 0x04b8, PCI irq 11
Socket status: 30000006
PCI: Found IRQ 11 for device 0000:00:02.1
Yenta: CardBus bridge found at 0000:00:02.1 [1014:0092]
Yenta: Using CSCINT to route CSC interrupts to PCI
Yenta: Routing CardBus interrupts to PCI
Yenta TI: socket 0000:00:02.1, mfunc 0xfba97543, devctl 0x62
Yenta: ISA IRQ mask 0x04b8, PCI irq 11
Socket status: 30000020
piix4_smbus 0000:00:07.3: Found 0000:00:07.3 device
piix4_smbus 0000:00:07.3: IBM Laptop detected; this module may corrupt your serial eeprom! Refusing to load module!
piix4_smbus: probe of 0000:00:07.3 failed with error -1
firmware_class: exports duplicate symbol release_firmware (owned by kernel)
firmware_class: exports duplicate symbol release_firmware (owned by kernel)
pccard: CardBus card inserted into slot 1
cs: IO port probe 0xc00-0xcff: excluding 0xcf8-0xcff
cs: IO port probe 0x820-0x8ff: clean.
cs: IO port probe 0x800-0x80f: clean.
cs: IO port probe 0x3e0-0x4ff: excluding 0x4d0-0x4d7
cs: IO port probe 0x100-0x3af: clean.
cs: IO port probe 0xa00-0xaff: clean.
cs: IO port probe 0xc00-0xcff: excluding 0xcf8-0xcff
cs: IO port probe 0x820-0x8ff: clean.
cs: IO port probe 0x800-0x80f: clean.
cs: IO port probe 0x3e0-0x4ff: excluding 0x4d0-0x4d7
cs: IO port probe 0x100-0x3af: clean.
cs: IO port probe 0xa00-0xaff: clean.
r8169 Gigabit Ethernet driver 2.2LK loaded
PCI: Enabling device 0000:05:00.0 (0000 -> 0003)
PCI: Setting latency timer of device 0000:05:00.0 to 64
eth0: Identified chip type is 'RTL8169s/8110s'.
eth0: RTL8169 at 0xc88ec000, 00:13:3b:02:b1:25, IRQ 11
USB Universal Host Controller Interface driver v3.0
kmem_cache_create: duplicate cache uhci_urb_priv
 <c014dd1f> kmem_cache_create+0x30f/0x3b0  <c88d4033> uhci_hcd_init+0x33/0x92 [uhci_hcd]
 <c0130e52> sys_init_module+0xe2/0x160  <c0102de7> syscall_call+0x7/0xb
sd 2:0:0:0: Attached scsi generic sg0 type 0
input: PC Speaker as /class/input/input1
input: PS/2 Generic Mouse as /class/input/input2
lp: driver loaded but no devices found
Linux agpgart interface v0.101 (c) Dave Jones
Capability LSM initialized
r8169: eth0: link down
USB Universal Host Controller Interface driver v3.0
kmem_cache_create: duplicate cache uhci_urb_priv
 <c014dd1f> kmem_cache_create+0x30f/0x3b0  <c88fd033> uhci_hcd_init+0x33/0x92 [uhci_hcd]
 <c0130e52> sys_init_module+0xe2/0x160  <c0102de7> syscall_call+0x7/0xb
r8169: eth0: link down
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
ADDRCONF(NETDEV_UP): eth0: link is not ready
IPv6 over IPv4 tunneling driver

and ifconfig-a shows it is recognised but has no ip

Code:

root@Laptop:~# ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:13:3B:02:B1:25
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Interrupt:11 Base address:0xc000

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

sit0      Link encap:UNSPEC  HWaddr 00-00-00-00-30-30-30-3A-00-00-00-00-00-00-00-00
          NOARP  MTU:1480  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

Just for completeness this is lsmod

Code:

root@Laptop:~# lsmod
Module                  Size  Used by
ipv6                  223584  10
capability              3336  0
commoncap               5376  1 capability
agpgart                28080  0
lp                      9800  0
parport_pc             24132  0
parport                30024  2 lp,parport_pc
pcspkr                  2432  0
psmouse                34952  0
sg                     26524  0
r8169                  23560  0
evdev                   8064  0
pcmcia                 30116  0
serio_raw               5252  0
i2c_piix4               7696  0
yenta_socket           23436  3
rsrc_nonstatic         10752  1 yenta_socket
pcmcia_core            34192  3 pcmcia,yenta_socket,rsrc_nonstatic

Im running slackware 11 with the 2.6.17.13 kernel

Any suggestions for getting it working would be very appreciated!

If you need any more info, just ask and i will get it

gegechris99 · 12-09-2006, 05:10 PM

You need to set up your network to get an IP address (either Static IP or DHCP).

Please refer to the following documentation:

http://slackbook.org/html/network-co...ion-tcpip.html

linuxhaxz · 12-10-2006, 02:30 AM

The network is set up via DHCP, but at boot time it just tries to connect, i get flashing lights, but no ip.

Ive tried it plugged into various ports of my router, and directly into my cable modem, with no luck.

Ive even tried reserving an ip on my router for the mac address of the card, but that didnt work either.

rspeiser · 12-26-2006, 10:34 AM

I have exactly the same problem and have been looking all over for a solution.

Problem: ifup and dmesg always report link down or link is not ready on Trendnet TEG-PCITXR, recognized as RealTek 8169. The cable/switch/router is all verified.

This is with Mandrake 2007. The r8169 driver is included in the kernel.

Every 3-4 seconds the activity light flashes on the NIC, but the link light is always dark.

Card works great under Windows XP (dual boot).

Any ideas or do I just (try to) return the card?

Thanks,
Russ

mku · 02-05-2007, 10:38 AM

Same problem here. I have an onboard r8169 nic on a 3 year old msi mainboard. Works fine under windows, worked under Linux 2.6.16 before I made a bios update to the latest bios version (from 2004). Didn't work under Linux since then. So I used a PCI-8139 nic instead.

Today I compiled the new kernel 2.6.20 (lots of changes of r8169 driver) and when running it at first the r8169 got "link up". Then I replaced the r8139 nic because I thought there was no more need for it. However, now there is again the same problem with the r8169 telling me "link down".

That's funny, isn't it? It only worked for one run.

But try kernel 2.6.20. Maybe you have more luck or figure out whats necessary to get it working all the time.

Eosie · 06-17-2007, 08:33 AM

Same problem here. The link had been down, then I tried kernel 2.6.22-rc3 with some patches for r8169, worked a few hours and then the link was down again. An option passed to the kernel: acpi=off (just for sure that acpi has no impact on it). I have no idea what can cause this problem.

Road_map · 06-17-2007, 09:20 AM

Quote:

Originally Posted by linuxhaxz

I have managed to get the card detected and the modules loaded by passing

Code:

pci=noacpi 
pci=noirq

to the kernel, however it still does not get an ip address, either from my router, or even if i plug it directly into my cable modem.

Are you sure that pci=noirq is the correct option?

mku · 06-18-2007, 03:32 AM

Meanwhile I figured out that it may not be a problem with any particular linux kernel at all. It might rather be connected to the suspend mode of the r8169 that causes problems on a dual boot machine.

As my r8169 is an onboard nic, I can disable it in the bios, re-enable it, boot linux and everything works fine. But as soon as I boot windows and then reboot to linux the know problem with "link down" re-appears.

So I guess that windows sends the nic into some kind of suspend mode and the linux kernel driver is not able to get it out of this mode.

Eosie · 06-19-2007, 07:26 AM

Thank you for your advice but disabling and re-enabling it in BIOS does not work for me. I found another solution how to prevent windows not to suspend r8169 - just boot windows, connect to your network and do a hard reset. Then boot linux and everything works fine.

I would consider it as a linux kernel driver bug or perhaps an unimplemented feature because it cannot wake up r8169.