Uniwill 258KA doesn't resume after suspend/hibernation

Are there any logs from when you resume? You can find out how to retrieve your computer's logs here:
https://wiki.ubuntu.com/DebuggingUbiquity/AttachingLogs

Hi, thank you for your help.
I think there're no logs were written to these files after resuming after suspend.
Before doing hibernate and suspend i did cleared my logs.
Then I did hibernate, and then suspend.
After hibernate my pc was turned off, then when i powered it up, it was booting, i saw splash, and then splash disappered and nothing more. CTRL+ALT+DEL doesn't reboots my pc. I only can power off it by pressing power button for about 5 secs.
Then i did suspend. It gone to sleep, sleeping led was blanking. When i turn it on, it doesn't resume at all.
And, by the way after suspend my laptop doesn't boot at all, even if i power off it and then power on. No picture on the
screen, even no bios posts. To boot it i have to take off a battery and power cable, then plug it back, and then it boots normally.
Sorry for bad english :)
-------------------- acpid
[Wed Jan 3 22:46:14 2007] starting up
[Wed Jan 3 22:46:14 2007] 56 rules loaded
[Wed Jan 3 22:46:16 2007] client connected from 4088[0:0]
[Wed Jan 3 22:46:16 2007] 1 client rule loaded
[Wed Jan 3 22:46:38 2007] client connected from 4403[0:0]
[Wed Jan 3 22:46:38 2007] 1 client rule loaded
[Wed Jan 3 22:46:45 2007] client connected from 4442[108:108]
[Wed Jan 3 22:46:45 2007] 1 client rule loaded
[Wed Jan 3 23:04:14 2007] received event "button/lid LID 00000080 00000001"
[Wed Jan 3 23:04:14 2007] notifying client 4088[0:0]
[Wed Jan 3 23:04:14 2007] notifying client 4403[0:0]
[Wed Jan 3 23:04:14 2007] notifying client 4442[108:108]
[Wed Jan 3 23:04:14 2007] executing action "/etc/acpi/lid.sh"
[Wed Jan 3 23:04:14 2007] BEGIN HANDLER MESSAGES
ERROR: Couldn't attach to DCOP server!
[Wed Jan 3 23:04:15 2007] END HANDLER MESSAGES
[Wed Jan 3 23:04:15 2007] action exited with status 1
[Wed Jan 3 23:04:15 2007] executing action "/etc/acpi/fglrx-powermode.sh"
[Wed Jan 3 23:04:15 2007] BEGIN HANDLER MESSAGES
fglrx: setting low power
[Wed Jan 3 23:04:15 2007] END HANDLER MESSAGES
[Wed Jan 3 23:04:15 2007] action exited with status 0
[Wed Jan 3 23:04:15 2007] completed event "button/lid LID 00000080 00000001"
[Wed Jan 3 23:08:09 2007] starting up
[Wed Jan 3 23:08:09 2007] 56 rules loaded
[Wed Jan 3 23:08:10 2007] client connected from 4005[0:0]
[Wed Jan 3 23:08:10 2007] 1 client rule loaded
[Wed Jan 3 23:08:20 2007] received event "battery BAT0 00000001 00000001"
[Wed Jan 3 23:08:20 2007] notifying client 4005[0:0]
[Wed Jan 3 23:08:20 2007] executing action "/etc/acpi/power.sh"
[Wed Jan 3 23:08:20 2007] BEGIN HANDLER MESSAGES
[Wed Jan 3 23:08:20 2007] END HANDLER MESSAGES
[Wed Jan 3 23:08:20 2007] action exited with status 0
[Wed Jan 3 23:08:20 2007] completed event "battery BAT0 00000001 00000001"
[Wed Jan 3 23:08:20 2007] received event "battery BAT0 00000080 00000001"
[Wed Jan 3 23:08:20 2007] notifying client 4005[0:0]
[Wed Jan 3 23:08:20 2007] executing action "/etc/acpi/power.sh"
[Wed Jan 3 23:08:20 2007] BEGIN HANDLER MESSAGES
[Wed Jan 3 23:08:21 2007] END HANDLER MESSAGES
[Wed Jan 3 23:08:21 2007] action exited with status 0
[Wed Jan 3 23:08:21 2007] completed event "battery BAT0 00000080 00000001"
[Wed Jan 3 23:08:30 2007] client connected from 4326[0:...

----------- kdm -----------------
********************************************************************************
Note that your system uses syslog. All of kdm's internally generated messages
(i.e., not from libraries and external programs/scripts it uses) go to the
daemon.* syslog facility; check your syslog configuration to find out to which
file(s) it is logged. PAM logs messages related to authentication to authpriv.*.
********************************************************************************

X Window System Version 7.1.1
Release Date: 12 May 2006
X Protocol Version 11, Revision 0, Release 7.1.1
Build Operating System: Linux 2.6.15.7 i686
Current Operating System: Linux vlad-laptop 2.6.17-10-generic #2 SMP Fri Oct 13 18:45:35 UTC 2006 i686
Build Date: 07 July 2006
 Before reporting problems, check http://wiki.x.org
 to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
 (++) from command line, (!!) notice, (II) informational,
 (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Wed Jan 3 22:46:16 2007
(==) Using config file: "/etc/X11/xorg.conf"
(EE) Failed to load module "v4l" (module does not exist, 0)
(EE) AIGLX error: dlsym for __driCreateNewScreen_20050727 failed (/usr/lib/dri/fglrx_dri.so: undefined symbol: __driCreateNewScreen_20050727)
(EE) AIGLX: reverting to software rendering
error opening security policy file /usr/lib/xserver/SecurityPolicy
    xkb_keycodes { include "xfree86+aliases(qwerty)" };
    xkb_types { include "complete" };
    xkb_compatibility { include "complete" };
    xkb_symbols { include "pc(pc104)+us+ru(winkeys):2+group(alt_shift_toggle)" };
    xkb_geometry { include "pc(pc104)" };
(EE) xf86OpenSerial: Cannot open device /dev/wacom
 No such file or directory.
Error opening /dev/wacom : Invalid argument
(EE) xf86OpenSerial: Cannot open device /dev/wacom
 No such file or directory.
Error opening /dev/wacom : Invalid argument
(EE) xf86OpenSerial: Cannot open device /dev/wacom
 No such file or directory.
Error opening /dev/wacom : Invalid argument
(EE) xf86OpenSerial: Cannot open device /dev/wacom
 No such file or directory.
Error opening /dev/wacom : Invalid argument
(EE) xf86OpenSerial: Cannot open device /dev/wacom
 No such file or directory.
Error opening /dev/wacom : Invalid argument
(EE) xf86OpenSerial: Cannot open device /dev/wacom
 No such file or directory.
Error opening /dev/wacom : Invalid argument
Synaptics DeviceInit called
SynapticsCtrl called.
Synaptics DeviceOn called
Could not init font path element /usr/share/fonts/X11/TTF/, removing from list!
Could not init font path element /usr/share/fonts/X11/OTF, removing from list!
Could not init font path element /usr/share/fonts/X11/CID/, removing from list!
X Error: BadDevice, invalid or uninitialized input device 169
  Major opcode: 149
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 169
  Major opcode: 149
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
QImage::co...

Vlad, a couple of points:

This machine has a lot of memory (more than 1GB, as far as I can tell from reading your logs) but it does not have very much swap (less than 0.5GB). swap space can be used for hibernation - would it be possible for you to add more swap space (if you have enough free disk space) so that you have at least as much swap space as memory?

It might be useful to boot with "quiet" disabled, so that we get complete logs. Try the following:

1. start a terminal window and run the command

    sudo logrotate -f

2. Reboot the machine;

3. When the grub menu appears, use the arrow keys to move to the first entry in the list (if there is no menu, hit esc when the "grub loading" line appears - this will have a countdown timer, typically a few seconds).

4. type e to edit the boot options

5. use the arrow keys to select the kernel line (second line, usually)

6. type e to edit the kernel options

7. use the arrow keys to get to "quiet" and the backspace or delete key to erase the word quiet

8. hit esc

9. type b to boot the system

10. when you get to your regular user session, hibernate the machine

11. either resume of reboot - just reboot normally

12. attach /var/log/syslog to this report - please refer to https://wiki.ubuntu.com/DebuggingUbiquity/AttachingLogs. Please DO NOT put the log file in the body of the comment, this makes it very difficult to read the bug report.

Hello!
I resized my swap to 1.6Gb. Then i did hibernate. While resuming i even saw my desktop! But the picture was broken, there wasn't mouse pointer, and when i pressed ctrl+alt+del, it did reboot.
Here is my complete syslog:
http://beework.isgreat.org/var/log/syslog.tar.gz
Thanks for any help!

Vlad, thanks for the syslog, there are some interesting things in there.

First, please try this: Shutdown, disconnect your PPP device (the USB device you use for your network connection), reboot, then try the hibernate (there is a message questioning whether the device driver - cdc_acm - can be suspended, and there are other bugs that feature this device, though I don't know how important it is).

Please report what that does (I'm not expecting it to help, just want to eliminate the possibility).

Next, there are memory corruption messages from kdm_greet. First, what version of kde do you have? (Try "dpkg --list \*kde\*") kde 3.5.2 apparently had problems that led to suspend/resume problems (bug #37529).

Please check your /etc/X11/xorg.conf file to see if you have compositing enabled, i.e., does the file contain

Section "Extensions"
     Option "Composite" "Enabled"
EndSection

?? If so, do the following

sudo cp /etc/X11/xorg.conf /etc/X11/xorg.conf.working
sudo nano /etc/X11/xorg.conf
sudo dpkg-reconfigure xserver-xorg

You can replace nano with vi or whatever editor you use. Comment out the composite line by adding # at the beginning of that line.

Once you've run the reconfigure command, try hibernating again (you may need to reboot, of course).

Third, something else to try is to use gdm instead of kdm, or anyother window manager. This will help nail down whether KDE is at fault. I won't provide on how to get there, as it could be a lot of work, and is only something you should attempt if you already know how to do it!

Lastly, there are APIC errors/warnings. I won't suggest booting with noapic because I don't know how your machine will behave. But you may want to do some research on your machine, e.g., by googling for your model, noapic and nolapic. Again, I won't suggest taking these steps, unless you are satisfied from your research that they are the right ones to take.

Can you please include in your report the output of "uname -a"? Attaching the output of "sudo dmidecode" and "sudo lspci -v" never hurts, either.

Hello!
1. Composite was disabled in xorg.conf
2. I tried to add noapic, it booting and then freezes, when it must show me login screen.
3. When i use nolapic it boots, but USB devices doesn't work. And machine doesn't resume after hibernation too. The sreenshot of my screen after hibernation are here:
http://beework.isgreat.org/var/log/screenshot.JPG
4. I plugged out all my USB devices, rebooted and then tried to do hibernation. The same situation. All my syslog you can see here:
http://beework.isgreat.org/var/log/syslog2.tar.gz

And "uname -a", "sudo dmidecode" and "sudo lspci -v" are here:
http://beework.isgreat.org/var/log/outputs.txt

By the way, GDM doesn't resume too, i had Ubuntu 6.10 before, but then i formatted HDD and reinstalled Kubuntu.

Thanks for your help!

Vlad, Based on your various replies, my guess is that this is a kernel problem (esp. since it failed with GDM as well).

According to uname -a, you are running a generic kernel, but your chip is an Athlon 64. Have you tried installing and running an-AMD specific kernel?

Peter, i don't have amd64 edgy eft distro at this moment. And i'll need to reinstall current Ubuntu to AMD64 version to get k8 kernel to work, isn't it?

On Wed, 2007-01-17 at 10:05 +0000, Vlad Alekseev wrote:
> i don't have amd64 edgy eft distro at this moment. And
> i'll need to reinstall current Ubuntu to AMD64 version
> to get k8 kernel to work, isn't it?

>From reading http://www.ubuntuforums.org/archive/index.php/t-287.html I
believe you should be able to install the kernel (and perhaps the i686
libc6).

Honestly, I don't know if it will help. I'm clutching at straws, trying
to figure out what might be going on, based on the logs you've posted.
Given that the kernel is ultimately responsible for hibernation and
resume, having a kernel optimized for your processor may help. But no
guarantees....

Hello, i downloaded and installed Ubuntu Edgy AMD64, hibernation is working now, very good! :) But suspend still doesn't works.

Vlad, this is good news! Now that you have the Edgy AMD64 kernel, can you please attach the output of the following commands:

uname -a

sudo lspci -vv

sudo lspci -vvn

sudo dmidecode

Thanks!

Also, just for completeness, can you please describe how you are attempting to suspend the machine (panel menu, hotkey, lid close, etc.) and what happens when you try this (nothing at all, links blink but then stop, machine crashes, TV turns on :->)? You get the idea: A little more information to help us figure out what might be happening.

Thanks, ii!

Hello, Peter!
Here is output of all things that you requested :)
http://beework.isgreat.org/var/log/x64outputs.tar.gz
I've recorded video how i putting my pc into sleep, i can publish it but only on this friday because at this moment i can't do it because of speed and cost of my GPRS connection :)
But i can describe it. I click red button in the corner of the screen, then i click Sleep (i don't know how it called in english, but in russian it is Спящий режим, Sleep mode, i think..), then PC fall to z-z-z-z-z, the led which shows sleep mode is blinking.. Like everythink is ok.
Then, to wake up laptop i have to press power button. I have pressed it. Laptop begins to work, even USB mouse works :) And HDD led is blinking, sometimes. But if i press Caps Lock button, for example, the capslock led doesn't bright! Numlock the same..
Then, after some time, monitor shows some broken picture, white background with several vertical lines. If i press Power button there's no reaction. In normal mode PC is turning off. I have to press it for 5 seconds, and then it will be turned off.

Thanks for any help, Peter!

Marked confirmed and redirected based on enclosed logs.

Hi, thank you for changing the status!
Can you tell me what the problem?

On Thu, 2007-02-15 at 14:53 +0000, Vlad Alekseev wrote:
> Hi, thank you for changing the status!
> Can you tell me what the problem?

Not specifically: There have been kernel updates, and much work
has been done in the kernel to improve ACPI support.

Hello, i had installed Mandrive one 2007 yesterday, and suspend works normally. But hibernate doesn't work... and pc doesn't reboot... :)
Well, i'm just want to say that suspend works.

Vlad, if at all possible, could you please try the debugging hints on https://wiki.ubuntu.com/KernelSuspendDebugging ? Thanks!

Peter, i have opened that link, but "the page doesn't exist yet". Maybe you mean this? https://wiki.ubuntu.com/DebuggingKernelProblems

Try https://wiki.ubuntu.com/DebuggingKernelSuspend

(think they must have corrected the naming inconsistency)

Hi, Peter. I'm sorry that i was in silience this time, i have problems with my PC. I was can't install Ubuntu because it's partition manager didn't seen my exsiting partitions. So i was not able to create partitions for Linux. I have created it under Partition Magic, then under GParted, and Ubuntu was not still able to detect my partitons.
Well, i have downloaded Feisty distro, Kubuntu (32-bit). Suspend to disk is working! :)
I'll post here kernel debug now.

http://www.esnips.com/doc/a9a54c75-01d6-405c-9267-738dcf1be100/k_feisty_dmesg_32.txt.tar

Hi,

i found out something.
I'm able to resume from suspend to RAM, but with some mistakes.
Sleeping is alright. But then, after resuming, if i'll press CTRL+ALT+F7, i'll get back to my X session.
But CPU is 100% busy because of VBETOOL. It takes 99% of time, so everything works slow.
And there's no sound.
I think that scripts after "15-video-post.sh" doesn't even begin running, because 15-video-post.sh never ends.
If i type "sudo killall vbetool", then my screen goes blank and i can't reboot. I can only push my power button for several seconds to power off.
Is there any replacement for vbetool? Or any other methods to make "warm-boot" of videocard?

I got it working!
I disabled vbetool post at all, and enabled everything else, and double console switching too. So it works fine now!
Thanks for help!!
Sorry for bad english :)

I am assigning this bug to the 'ubuntu-kernel-team' per their bug policy. For future reference you can learn more about their bug policy at https://wiki.ubuntu.com/KernelTeamBugPolicies .

In Ubuntu 7.10 amd64 everything works out of box.

The 18 month support period for Edgy Eft 6.10 has reached it's end of life. As a result, we are closing the linux-source-2.6.17 Edgy Eft kernel task.

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.