General Support - Suspend trubles on pc libcha - 17.04.2010, 14:51 Uhr Titel: Suspend trubles on pc
Hello,
I'm a well-surprised newbie on Kanotix. But this problem is really serious. I can't make the system suspend properly.
The problem is the same everytime - it suspends. But when i try to wake it up (by power button; kbd and mouse wakeup is disabled by bios (or by design)), only the fan and disks turn, but mouse, kbd and screen are completely frozen, so i must do hard restart.
I tried various utils, first echo something > somewere, second uswsusp, third pm-suspend.
The problems is, that all the manuals and solutions around internet are focused on suspending on laptops (some utils try to find out laptop version from hw =-O), but my home-made desktop seems to be unsupported
However, on ubuntu and winxp suspendig works fine....
Any experiences with suspending debian/kanotix on desktops ?
Thanks very much...
libcha - 17.04.2010, 14:55 Uhr Titel: Suspend trubles on pc
oh, i forgot to mention my hw: mb asus p5vdc-mx; gc nv fx-5200; proc p4
TheOne - 17.04.2010, 17:46 Uhr Titel: Suspend trubles on pc
hi libcha,
first welcome to Kanotix
it is more useful to use the shell command
Code:
infobash -v3
(as user) to get system specs, so post the output here please
btw if you visit the IRC and want to post your specs direct to the channel that works too, if you type /infobash -v
TheOne
libcha - 17.04.2010, 22:46 Uhr Titel:
# infobash -v
Host/Kernel/OS "princezna" running Linux 2.6.32-9-generic i686 [ Kanotix Excalibur 20091227-18:37 ]
CPU Info (1) Intel Pentium 4 clocked at [ 2800.088 MHz ]
(2) Intel Pentium 4 clocked at [ 2800.088 MHz ]
Videocard ATI RV280 [Radeon 9200 PRO] [ ]
Processes 131 | Uptime 1min | Memory 123.9/2012.7MB | HDD Size 81GB (84%used) | Client Shell | Infobash v2.67.1
Kano - 18.04.2010, 01:11 Uhr Titel:
You should not run that tool as root. Btw. you can not do much, basically only a kernel update, maybe even try the .33 test kernel you find here:
It's a tar.gz with install.sh script to be used. Do NOT try suspend to disk, only supend to ram.
libcha - 18.04.2010, 12:29 Uhr Titel:
What means i cannot do much ?
a) it's a small mistake about eg. a video driver, which doesnt cause only black screen, but complete computer freeze
b) it demands hundreds of shell script lines to make it func
c) it is allmost hopeless
..?
hibernating to disk is without problems (eg with s2disk, or kpowersave, which btw uses s2disk), but slow for me.
ok, i'll try the 33 kernel, but i'm looking forward to build my own 34rc4 kernel.
in that case, what settings shall i focus on ?
TheOne - 18.04.2010, 14:03 Uhr Titel:
Hi libcha,
try out some different Kernels. I remember s2ram with 2.6.32-9 didn't work for me too. In contrast 2.6.32-13 works really good. On a different machine i use the 33 which suspend just as well.
Cheers TheOne
libcha - 18.04.2010, 22:48 Uhr Titel:
So I tried the 33-2-ck1 kernel from Kano, run s2ram with all possible hackout parameters, and the error seems all the same...
I'm quite tired from how it doesn't work
Is there a way to debug this ?
Kano - 19.04.2010, 01:35 Uhr Titel:
Sorry, i do not use suspend normally, no laptop here. But you should definitely disable suspend 2 disk when you dual/multiboot. As when you boot the "wrong" system after wakeup then data loss is very likely. Use S2D only when it is 100% clear that you will resume from the same partition as you suspended it. Maybe you have to use another distro, no idea.
libcha - 19.04.2010, 19:22 Uhr Titel:
I'm sad about changing distro, Ktx is for me very good surprise - it's well configured and easytouse just after install. Only the suspending... The last thing is to try another graphics card, it may func, if there is no fatal mistake.
After s2disk - it didnt happen for me yet to boot the wrong system - or i did it intentionally, but nothing bad happened. Etx2fsd does nothing with linux partition, and linux sees the xp ntfs partition with hibernated system locked.
libcha - 04.05.2010, 23:21 Uhr Titel:
WOW, changes
It wasn't possible to suspend even on other linux systems, like ubuntu...
I changed somehow (randomly ) BIOS setting and it works now fine
So... solved. Sorry for clueless disturb...