Re: r8168b woes
Okay I finally gave up on trying to get nvidia-dkms working on the
3.2.0-4 kernel and just booted to text mode to try out mediatomb,
which was one of the few applications that seems to give consistant
failures by stressing the network card. It looks like 3.2.0-4 is
stable on my machine, so hopefully the next version of Debian will at
least have that fix in the kernel by the time the next release rolls
around.
Thanks for the help and I hope my contribution will at least give some
confidence as to which version of the driver is working correctly.
Jeffrey
On Mon, Oct 22, 2012 at 9:50 AM, Jeffrey <jcanon+debian@flying-baker.com> wrote:
> Sigh,
>
> After adding the firmware-realtek, the error is gone and the message
> goes away, however my machine still will not netboot, where the
> VirtualBox PXE_Boot image will. I suspect this means the driver still
> isn't fixed, at least not with compiling from source from unstable.
> One last thing I can try is to unpack the actual deb package and place
> the files in the correct locations and try again, however for the
> moment the only stable version of the r8196 driver is in the current
> stable kernel.
>
> Now get ready for the real kicker. I wanted as a precaution to set up
> the driver from realtek r8168 and compiled it against the stable
> kernel. That driver exhibits the same behavior as the broken r8169
> drivers of the later kernels! It almost makes me wonder if the error
> is in the r8168 code and it somehow got copied into later kernels
> r8169 code to expand it's support. Even though I "don't have a
> problem" I'm going to be very nervous upgrading my system, or even
> introducing an updated stable kernel.
>
> Looks like for the moment I'm keeping a copy of the current kernel
> .deb packages just in case a future update breaks the driver.
>
> The saga continues
> Jeffrey
>
> On Mon, Oct 22, 2012 at 12:35 AM, Jeffrey
> <jcanon+debian@flying-baker.com> wrote:
>> I got a netboot version of the kernel installed, it was created using
>> the linux-source-3.2 from the unstable branch then using the
>> live-build scripts created the netboot.
>>
>> It won't boot to completion, the last few messages I get are:
>> r8169 0000:02:00.0: eth0: unable to load firmware patch
>> rtl_nic/rtl8168e-3.fw (-2)
>> r8169 0000:02:00.0: eth0: link down
>> ADDRCONF(NETDEV_UP): eth0: link is not ready
>> IP-Config: eth0 hardware address XX:XX:XX:XX:XX:XX mtu 1500 DHCP RARP
>>
>> However The image does work when running on a VirtualBox PXE Boot
>> image. So I'm still suspecting the network driver here, although I
>> can't get far enough into the boot process to actually look at dmesg.
>> I'll try recreating the image including the firmware-realtek package
>> see if that helps.
>>
>> I'm not sure if I'm using the same kernel as with unstable since I'm
>> compiling from source. I'm not sure if the fix is a debian specific
>> patch or if the kernel image is supposed to have the fix included. I
>> was unable to get a netboot of sid working but I'm guessing that
>> live-debian is supposed to be based on stable.
>>
>> I'll update as I learn more.
>>
>> Jeffrey
>>
>> On Sun, Oct 21, 2012 at 4:03 PM, Thorsten Glaser <t.glaser@tarent.de> wrote:
>>> On Fri, 19 Oct 2012, Ben Hutchings wrote:
>>>
>>>> Do you get a 'NETDEV WATCHDOG' warning in the kernel log? If so this
>>>> may be a known bug which is fixed in 3.2.25. Try the package from
>>>> unstable (linux-image-3.2.0-4-amd64 version 3.2.30-1).
>>>
>>> For what it’s worth, installing 3.2.0-4 on a manitu dedicated server
>>> fixes that problem for me, twice (i.e. on two boxen, all r8169, with
>>> different configurations).
>>>
>>> bye,
>>> //mirabilos
>>> --
>>> 15:41⎜<Lo-lan-do:#fusionforge> Somebody write a testsuite for helloworld :-)
>>>
>>>
>>> --
>>> To UNSUBSCRIBE, email to debian-backports-request@lists.debian.org
>>> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>>> Archive: [🔎] alpine.DEB.2.02.1210220103080.18486@tglase.lan.tarent.de">http://lists.debian.org/[🔎] alpine.DEB.2.02.1210220103080.18486@tglase.lan.tarent.de
>>>
Reply to: