Custom Query (41 matches)

The r8169 driver from may 2013 is loaded fine and lantran.log shows no error. The IP setup of the network interface is also ok. The localhost interface is working but access to other hosts on the network fails (e.g. with ping). RtlChipId? shows that the hardware revision for this device is 39. Using an older adapter with hardware revision 32 works without any problems.

Lenovo Thinkpad W520 4276-37U. The ethernet is Intel 82579LM. If setup.cmd specifies DHCPSTRT, the machine usually freezes on boot, and have to power off. When I did an alt-F2 boot, it did not freeze, but DHCPSTRT did not acquire an IP address. If setup.cmd specifies an IP address, boot is normal.

I got a new Lenovo ThinkPad? L530. It has a Realtek "Device 8168h RTL8111/8168B PCI Express Gigabit Ethernet controller in it" (from PCI.EXE). I tried Multimac from r8169-0.2.1.wpi. It loads okay, and most of the time, it will get an address from my router, using DHCP. However if I actually try to use it, the machine hangs hard. The only option is to force a power off. I also tried the older multimac driver (R8110), but it hung hard when the driver loaded. I then tried two GENMAC drivers, with no success. The driver from rtgnda13.zip does work, but seems to have a couple of minor problems. Of course, it works perfectly in Win7 Pro 64.

By "actually try to use it", I mean: I loaded Firefox (10.0.12esr), which has a home page of a file on my system. As soon as I try to go to a URL on the internet, I see the Pulse widget indicate about 60% IRQ load. That lasts for about 5 seconds, then the machine is locked. The mouse won't even move. The only way out is forced power off. I also, eventually, see the 60% IRQ load, if I just let the machine sit idle (probably the router doing something), followed shortly by the hard hang.

I traced the operation on my router, but all it shows is the initial connection, which succeeded.

I loaded the TRACE R8169 driver, but since the machine is locked, I can do nothing with it. I did take a trace after a reboot, without actually trying to use the network interface (not sure if it will help).

PCI.EXE output is in L530.txt. I included the whole thing, since this is a relatively new machine, with UEFI BIOS.

Trace output is in L530_10EC_8168.ftf.

Probably useless information: I did find a hit (that I can't find again) that sounds exactly the same in SUSE linux. It mentioned that UBUNTU linux does NOT have the problem.