On Tue, Jun 07, 2005 at 08:50:37AM -0700, Alan W. Irwin wrote: > On 2005-06-07 17:48+0900 Horms wrote: > > >On Sun, Jun 05, 2005 at 01:11:54PM +0200, Norbert Tretkowski wrote: > >>severity 311357 grave > >>thanks > >> > >>* Alan W. Irwin wrote: > >>>This is a confirmation of the bad problem with the via-rhine module > >>>for the latest version of the 386 version of the 2.6.8 kernel. > >> > >>Sounds like a RC bug, so I'm setting it's severity to grave. > >> > >>>I "upgraded" today from kernel-image-2.6.8.2-386 version 2.6.8-13 to > >>>2.6.8-16, and my network card (D-link 10/100 DFE-530TX) that is > >>>controlled by the via-rhine module immediately quit working > >> > >>Too bad this bug didn't get realized when -16 was in unstable... > >>looks like it's too late to fix this for 3.1r0. > > > >True, there was some late minute package shiffling which meant that -16 > >ended up going straight into sarge. Unfortunately now we have this bug. > >A similar thing seems to have happened with 2.4.27 and some neftilter > >symbols. It partly my fault (in the sense that I uploaded the packages) > >and partly a process issue. I do appologise for any inconvenience and > >I'll try and get updates together over the next few days. But we have > >clearly missed the boat for 3.1r0. > > Hi Horms: > > Thanks for acknowledging the via-rhine problem that has gotten into 3.1r0. > For Debian sarge users it sounds like you have plans to fix version 2.6.8-16 > which is excellent. But until that happens, and for on-going Debian testing > users like me what kernel 2.6 solution do you recommend for all those who > require via-rhine for their networking? For example, do you (or anybody > else paying attention to this bug thread) know whether the via-rhine > problems also occur for kernel-image-2.6.11 (currently in unstable)?
I haven't heard any reports that they occur in 2.6.11, and I imagine there are people using that combination, so if I was in your shoes I would try that. I do have a box with a VIA rhine card, I will fire it up and see if I can a) reproduce the problem in 2.6.8-16, b) if it goes away in 2.6.11-5 and c) get some fixes available for 2.6.8. But its not the D Link card in question, so I am not sure if I am in a position to test if a given kernel works. On a brighter note, I have been unable to reproduce the nefilter bug I mumbled about in my previous post, so that appears to have been a false alarm. -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
