Hi, I tried with the given kernel and the result is: - exactly the same symptons as in 2.6.8 - the backported kernel is built with gcc 4.0.2 (not sure about the subdigits) which are not part of Sarge, making building of additional modules impossible. Such a backported kernel should be built with gcc from Sarge (IMHO). -- and I know it's an unrelated comment :-)
And to come back to your point on filing a separate bug for 2.6.8, I just remember that I clearly said in my first bug report that I need actually a fix for 2.4.x because of other dependencies; I only tried 2.6.8 because I was asked to... Thanks, Eric > On Mon, Sep 19, 2005 at 04:19:21PM +0200, Eric Lavarde wrote: >> Package: kernel-image-2.4.27-2-686 >> Version: 2.4.27-10 >> Followup-For: Bug #315110 >> >> >> Hi, >> >> after some time, I tried to work under kernel 2.6.8 and I don't even get >> the module to work. > > Hi, if this is a problem with 2.6.8, it is probably best to file it as a > separate bug. However, as 2.6.8 is now in deep freeze, I have to be > honest and say that the chances of the problem being resolved are slim. > > As an alternateive, would it be possible for you to test the backport of > 2.6.12 that has been made for sarge. > > You can find it as 2.6.12-5.99.sarge1 in > http://packages.vergenet.net/testing/linux-2.6/ > > > > -- > Horms > > --
