Trackpad and SOME keys fail after suspend - worked in Alpha Ibex not in beta

Colin Murphy lists at spudulike.me.uk
Fri Oct 17 17:49:00 UTC 2008


On Tuesday 14 October 2008 19:26:42 Colin Murphy wrote:

>
> I would like to submit a helpful bug report but I am struggling to get the
> info I think you need.

Is this the right list to ask such questions?  I want to help you guys but I 
don't have the technical knowledge to produce the information I think you 
need.  If it's the wrong list then some suggestions of somewhere better to 
post the problem would be welcome.
>
>      On my Lenovoa N100 suspend worked well on kernel 2.6.27-2-generic
> which came with an Alpha release of Intrepid.  With later releases, after a
> suspend / resume, the trackpad gives no response and SOME of the keys have
> confused mapping - 'u' yields a backspace, 'l' yields '~', 'p' gives '*',
> to name but some.  All are keys on the right hand side. Keys on the left
> hand side seem to work as expected.
>
>      Seeing as I seem to have access to a working systems, for one kernel
> at least, is there any helpful information I can provide to see why suspend
> doesn't play quite so nicely in later versions?
>
>      I had found a webpage describing "resume-trace" where some info is
> supposed to be placed in RTC memory but I don't think this is working for
> me - the RTC doesn't get reset in any case.  Does this output mean
> anything?
>
> root at colin-laptop:/home/colin/Bugs/working# sync; echo 1
>
> > /sys/power/pm_trace; /etc/acpi/sleep.sh force
>
> cat: /etc/network/run/ifstate: No such file or directory
> cat: /etc/network/run/ifstate: No such file or directory
>  * Shutting down ALSA...                                                 [
> OK ]
>  * Saving the system clock
> Function not supported
> Function not supported
>  * Setting the system clock
>  * Setting up ALSA...                                                    [
> OK ]
> FATAL: Module acpi_sbs not found.
> FATAL: Module acpi_sbs not found.
>

How useful is the information that 'resume-trace' will provide, if I can get 
it working.  Remember, I have one working kernel and more than one failing 
kernel on the same laptop.  Would 'resume-trace' info from both sides be 
useful?

>      Is there other info I can submit to launchpad?  When I do, what
> package would I submit it under?
>



-- 
Colin at spudulike.me.uk
Gotta' go, things to be, people to do, stuff to, err, stuff.




More information about the Ubuntu-bugsquad mailing list