On Sun, Aug 20, 2006 at 02:44:39AM +0200, [EMAIL PROTECTED] wrote: > >On Sun, Jun 18, 2006 at 10:42:54PM +0200, Laszlo Boszormenyi wrote: > > On Sun, 2006-06-18 at 21:53 +0200, [EMAIL PROTECTED] wrote: > > > Package: kernel > > > Version: > > Which version do you use? Own or from package? > > >Thanks Laszlo. > > >The kernel.org bug report says Debian's 2.6.15. > > >Tomek: Can you try the 2.6.16 kernel from sid to see if the problem > >goes away? I'm unaware of any patches in the Debian kernel that are > >likely to change this behavior. > > >-- > >dann frazier > > Hi. Sorry for replying so late, but I've just noticed that someone replied to > my mail... (I should have subscribed to the list, now I have) > > I have now the 2.6.16-2 kernel (from testing) and the problem went > away:) but I have also a 2.6.17.4 from kernel.org (which I prefer to > use as my graphics card's driver does not work properly with kernels < > 2.6.17) and the problem is present with this kernel... So maby it is > a kernel configuration problem, which maby have changed from 2.6.15 to > 2.6.16 in debian's kernels? And I don't remember which config file I > used (the one from debian's 2.6.15 or from debian's 2.6.16) to > generate the configuration for 2.6.17.4. I will try 2.6.17.9 (as it is > the newest) with the kernel config from debians 2.6.16 and let you > know about the results.
seriously learn to use the enter key. (broke aboves in several lines) fetch linux-image 2.6.17 from unstable, should give you the best of both worlds :) regards -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
