Comment 4 for bug 399587

On 07/15/2009 11:15 AM, Steve Langasek wrote:
> On Wed, Jul 15, 2009 at 08:14:16AM -0000, Darshaka Pathirana wrote:
>>> The correct fix for this bug is for the toshiba kernel module to
>>> generate a key event using the kernel input layer. Can you follow
>>> https://wiki.ubuntu.com/Hotkeys/Troubleshooting to verify whether the
>>> kernel is outputting a key event, and if not, can you check whether this
>>> is fixed in the 2.6.31 kernel in karmic?
>
>> Thanks for the link! I will have a look at it.
>> To double check again: Installing the 2.6.31 kernel is enough? (I
>> had no intension on upgrading to karmic.)
>
> Yes, you should be able to install the 2.6.31 kernel package from karmic on
> jaunty, and this should be sufficient for testing on this bug. If it's
> easier for you, a test with the upstream 2.6.31 kernel should also tell us
> everything we need to know.

Ok. I installed the karmic kernel 2.6.31-3-generic but I am very
sorry to say that the kernel were not able to boot. Not even in the
recovery mode!

It feels like the X-Server gets started but the screen keeps blank
(with some kind of backlight). There must be a severe problem with
the kernel (and my notebook) but I ran out of ideas to debug the
problem (as the boot output blanks away too fast, ALT+CTRL+F1 had no
effect and the /var/log/syslog got corrupt after the restart).

Maybe I can ssh into the machine but for that I need a second
machine first...

Any other clues for me of what I can do?

Greetings,
 - Darsha