Thursday, 21 May 2009

Kernel issues - Debian and pristine

Ever since I bought this laptop I was quite content with it running Debian GNU/Linux (Lenny) and, except the sleep functionality not working (bug reported, but I have no answer for any new approaches) I have no other major issues.


Actually, the problems are partially solved since I am in a "pick your favourite bug" situation:
  • with the 2.6.26 kernel from Debian the information about the power source is incorrect (kernel bug which goes away for me right since 2.6.27)
  • while with a newer (>=2.6.27) pristine kernel, power information is accurate, but the entire bluetooth stack (init.d scripts and apps) needs a restart after a hibernate/resume cycle to work again; I added my info in the corresponding upstream bug and I hope it gets fixed
Still, I am really curious, since the Debian Kernel Team policy is to accept only patches accepted upstream, theorecally that would mean newer upstream kernels should work wrt that bluettoth issue, assuming this isn't a regression (it doesn't look like one from my experience).

So what is present in Debian kernels that isn't in the pristine ones that makes BT work afer resume? If you know the answer, please add it to the bug report.


On the Debian side of the kernel, which are the chances that newer Lenny kernels will include the power fixes necessary for MSI laptops to report power related info correctly? I know, I know, I should probably report a bug, but I want to know first if there will be a lenny-n-half release, otherwise it doesn't make sense.

4 comments:

Anonymous said...

Have you tried Debian's 2.6.29 kernels from unstable?

Anonymous said...

Have you tried compiling the bluetooth stuff as a module? Then some power management script might automagically reload the relevant modules.

eddyp said...

Have you tried Debian's 2.6.29 kernels from unstable? Just did today and 2.6.29 regressed wrt to bluetooth, too. Maybe the regression appeared during 2.6.27 development cycle.

eddyp said...

Have you tried compiling the bluetooth stuff as a module? Then some power management script might automagically reload the relevant modules.Debian kernels are modular and I base my configuration on the official config files from those packages.

In other words all my kernels use modules.