Latest working kernel version: 2.6.26 Earliest failing kernel version:2.6.24 Distribution:opensuse 11.0 Hardware Environment:MSI-945GCM7 MB w/celeron e1200 dual core Software Environment:32 bit suse linux 11.0 Problem Description:RTL8111C onboard NIC, intermittently, does not connect after boot. when it doesn't connect version number shown as 0xff instead of 0x02. After googling RTL8111C I found similar problem reported for archlinux and ubuntu but no one has reported the version number change AFAIK. I had to compile the driver into (CONFIG_R8169=y) the kernels prior to 2.6.26 in order for the nic to work after boot 99% of the time. Whatever has happened in the 2.6.26 version has enabled me to use the stock kernel with no changes but I now have the same behaviour as the compiled in driver in previous kernels. See https://bugzilla.novell.com/show_bug.cgi?id=412823 . Steps to reproduce:2.6.25 kernel and 945GCM7 w/RTL8111C
> Latest working kernel version: 2.6.26 > Earliest failing kernel version:2.6.24 I will assume that these are backwards, and shall mark it as a regression.
In case I don't understand the field properly. When I first had the 945GCM7 I had a 2.6.24 kernel installed. With 2.6.24 and 2.6.25 kernels I had to compile the driver into the kernel, as opposed to loading as a module, with the 2.6.26 kernel the problem is 99% solved, maybe I shouldn't have filled in the Latest working kernel version: field?
Dave Plater 2008-08-10 00:09: [...] > when it doesn't connect version number shown as 0xff instead of > 0x02. I guess 'lspci -vvxx' would claim an 'unknown header format' and report only 0xff in the PCI configuration space of the device. Similar reports have been fixed with commit (included in 2.6.27-rc1) 77332894c21165404496c56763d7df6c15c4bb09 Can you give 2.6.27-rc1 or 2.6.27-rc2 a try and report if there is any difference ? In any case, I would appreciate a complete dmesg from boot including the XID line emitted by the driver. -- Ueimor
Created attachment 17163 [details] nic not working version shown as ff
Created attachment 17164 [details] boot.omsg is saved from a successful driver load The only difference I could see between when the nic works and when it doesn't is the version number loaded as ff instead of 02. This shows up in hwinfo --netcard too. The only other difference I have found is ethtool shows the nic running at 1000 Mb/s, which is a result of no external connection maybe, and 100Mb/s when it works.
Created attachment 17165 [details] A good and bad hwinfo --netcard
Created attachment 17166 [details] Yast2 hardware info save
Although I have an nVidia card, this bug was present with onboard Intel 945 graphics and I saw no change in the behaviour at all.
I will try 2.6.27-rc2 on Monday, I am unable to download large files at the moment.
Created attachment 17167 [details] 2.6.26 to 2.6.27-rc2 r8169 patch Dave Plater 2008-08-10 06:35:40 : [...] > I will try 2.6.27-rc2 on Monday, I am unable to download large files at the > moment. If you are in a hurry I have attached the (~10 ko) patch against 2.6.26. Thanks for your help. -- Ueimor
2.6.27-rc2 installed, I see an extra message, r8169: eth0: link up, displayed twice. I had a failure first boot this morning with 2.6.26 kernel but could not make it happen again. Do you have any idea about what causes the incorrect version number?
Dave Plater 2008-08-11 01:18:11 : [...] > Do you have any idea about what causes the incorrect version number? It is probably commit 77332894c21165404496c56763d7df6c15c4bb09. May I close the bug ? -- Ueimor
Sure, no more problems so far and the first boot seemed to consistently fail with 2.6.26 kernel.