Thanks for the info. Suspend is not a major requirement for me, so I may just leave things as is. More than anything, I wanted to bring up the issue for upstream correction in future versions.
It is my firm belief that Linux can be and is almost everything that Windows isn't. I also believe that the non-technical user will not even think of switching until the system is intuitive and working as designed 99% of the time. I am trying to force Linux into a box that was designed for windows, which is the cause of most of my issues. My next computer WILL be shipped with Linux of some flavor. Thanks again for your help. ~ Dave ~ On Mon, Nov 16, 2009 at 09:08, Christian Ramseier <chr...@gmail.com> wrote: > Here is some kind of workaround I found: > > 1. When suspending, use "sudo pm-suspend" instead of the "Suspend" menu > from Gnome. > 2. After resuming, your keyboard will be broken, but Gnome's password > prompt won't appear. This way you can still use your Desktop and do stuff > with the mouse. > 3. Log off (using the mouse) > 4. Log in again > > >From now on, suspend is working properly (either with pm-suspend or the > "Suspend" menu). > > I think this indicates that something goes wrong when the machine is > first started up. Maybe some module / driver is not ready when X starts > upon boot and some initialization fails... > > -- > keyboard does not work after suspend > https://bugs.launchpad.net/bugs/465475 > You received this bug notification because you are a direct subscriber > of the bug. > > Status in “linux” package in Ubuntu: New > > Bug description: > OS: Ubuntu 9.10 Karmic (new install, updates applied) > Computer: HP dv5 > > On resume from suspend, unable to enter password due to keyboard being > unresponsive. All other hardware appears to be working, including USB mouse. > Only solution is to restart system, at which point keyboard is fine. Detail: > when keyboard is not working, the scroll lock light is on and state cannot > be changed. > > Temporary workaround: suspend disabled from power management for lid close. > > ProblemType: Bug > Architecture: amd64 > ArecordDevices: > **** List of CAPTURE Hardware Devices **** > card 0: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog] > Subdevices: 2/2 > Subdevice #0: subdevice #0 > Subdevice #1: subdevice #1 > AudioDevicesInUse: > USER PID ACCESS COMMAND > /dev/snd/controlC0: david 2872 F.... pulseaudio > CRDA: Error: [Errno 2] No such file or directory > Card0.Amixer.info: > Card hw:0 'SB'/'HDA ATI SB at 0xd2400000 irq 16' > Mixer name : 'IDT 92HD71B7X' > Components : 'HDA:111d76b2,103c30f2,00100302 > HDA:11c11040,103c137e,00100200' > Controls : 35 > Simple ctrls : 22 > Card1.Amixer.info: > Card hw:1 'HDMI'/'HDA ATI HDMI at 0xd2310000 irq 19' > Mixer name : 'ATI RS690/780 HDMI' > Components : 'HDA:1002791a,00791a00,00100000' > Controls : 4 > Simple ctrls : 1 > Card1.Amixer.values: > Simple mixer control 'IEC958',0 > Capabilities: pswitch pswitch-joined > Playback channels: Mono > Mono: Playback [off] > Date: Fri Oct 30 16:11:43 2009 > DistroRelease: Ubuntu 9.10 > HibernationDevice: RESUME=UUID=d8037aed-4ba3-470b-bacb-b8b26315e9d3 > InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) > MachineType: Hewlett-Packard HP Pavilion dv5 Notebook PC > NonfreeKernelModules: fglrx > Package: linux-image-2.6.31-14-generic 2.6.31-14.48 > ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-14-generic > root=UUID=30ab27ad-2abc-4d4f-84ee-454f164c70cf ro quiet splash > ProcEnviron: > LANG=en_US.UTF-8 > SHELL=/bin/bash > ProcVersionSignature: Ubuntu 2.6.31-14.48-generic > RelatedPackageVersions: > linux-backports-modules-2.6.31-14-generic N/A > linux-firmware 1.24 > RfKill: > 0: phy0: Wireless LAN > Soft blocked: no > Hard blocked: no > SourcePackage: linux > Uname: Linux 2.6.31-14-generic x86_64 > XsessionErrors: > (gnome-settings-daemon:2921): GLib-CRITICAL **: g_propagate_error: > assertion `src != NULL' failed > (gnome-settings-daemon:2921): GLib-CRITICAL **: g_propagate_error: > assertion `src != NULL' failed > (polkit-gnome-authentication-agent-1:3125): GLib-CRITICAL **: > g_once_init_leave: assertion `initialization_value != 0' failed > (nautilus:3078): Eel-CRITICAL **: eel_preferences_get_boolean: assertion > `preferences_is_initialized ()' failed > dmi.bios.date: 09/23/2008 > dmi.bios.vendor: Hewlett-Packard > dmi.bios.version: F.13 > dmi.board.asset.tag: Base Board Asset Tag > dmi.board.name: 30F2 > dmi.board.vendor: HP > dmi.board.version: 98.24 > dmi.chassis.type: 10 > dmi.chassis.vendor: Quanta > dmi.chassis.version: N/A > dmi.modalias: > dmi:bvnHewlett-Packard:bvrF.13:bd09/23/2008:svnHewlett-Packard:pnHPPaviliondv5NotebookPC:pvrRev1:rvnHP:rn30F2:rvr98.24:cvnQuanta:ct10:cvrN/A: > dmi.product.name: HP Pavilion dv5 Notebook PC > dmi.product.version: Rev 1 > dmi.sys.vendor: Hewlett-Packard > -- keyboard does not work after suspend https://bugs.launchpad.net/bugs/465475 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
