shutdown errors on satellite s103

[Guest chrismcdirty]

I just installed Mandrake 9.1 onto a Toshiba Satellite 1115-S103 on Sunday, with little-to-no problems. I use KDE as a window manager and that works fine, until I try to shut down. KDE logs out and I'm given a blank screen that sits and hangs. I restarted and booted to Enlightenment, and that rebooted okay. Once I got back to the login (mdkKDM), I rebooted and it worked fine. Once again, logged into KDE, then logged out without problems, and rebooted. I figued I'd just have to logout before a reboot each time. But when I logged out later, the same thing happened as when I shut down earlier in the day.

 

Does anybody have any idea besides KDE being stupid?

[Guest myates]

It is possible that ACPI power management breaks the shutdown. See:

 

http://www.mandrakeclub.com/article.php?sid=474

 

You might also search bugzilla:

 

http://qa.mandrakesoft.com

[Guest myates]

If the sutdown problem is specific to KDE, a possible workaround may be to open Konsole, then type (as root):

 

shutdown -h now

[bvc]

Actually...(as root) try;

poweroff

as it's specificlly for acpi (if I remember correctly). It goes to

/proc/acpi/event

which is where the acpi daemon listens for...you guessed it, an event :P

 

Of course if you're apm this would do no good and acpi and acpid should'nt be ran at startup in the Mandrake Control Center>System>DrakeXServices. If you do have acpi make sure they are there.

 

You can poke through (as root) /proc/acpi and see what's going on with you sys with the cat command. You can see below that acpid is listening to event because it's busy.

[root@localhost bvc]# ls /proc/acpi

ac_adapter/  button/               event  info             sleep

alarm        dsdt                  fadt   power_resource/  thermal_zone/

battery/     embedded_controller/  fan/   processor/

[root@localhost bvc]# cat /proc/acpi/event

cat: /proc/acpi/event: Device or resource busy

[root@localhost bvc]# ls -a /proc/acpi

./           alarm     dsdt                  fadt  power_resource/  thermal_zone/

../          battery/  embedded_controller/  fan/  processor/

ac_adapter/  button/   event                 info  sleep

[root@localhost bvc]# cat /proc/acpi/info

version:                 20030122

states:                  S0 S1 S4 S5

[root@localhost bvc]# ls -a /proc/acpi/processor

./  ../  CPU0/

[root@localhost bvc]# ls -a /proc/acpi/processor/CPU0

./  ../  info  limit  performance  power  throttling

[root@localhost bvc]# cat /proc/acpi/processor/CPU0/info

processor id:            0

acpi id:                 0

bus mastering control:   no

power management:        yes

throttling control:      yes

performance management:  no

limit interface:         yes

[root@localhost bvc]#

I'd do something more interesting but as you can see I have the early days half _ _ _ acpi crappy OEM bios :lol: and half of these do nothing for me on this desktop, but I need acpi in order to shutdown and a few other things. I did some on lawsonrc's laptop and found the cpu temp and all kinds of good stuff. Have fun!

 

WARNING Be careful in

/proc/sys

specifically /proc/sys/kernel

 

and

/proc/i20

 

/proc/kmsg

/proc/ksyms

 

doing cat on the wrong thing can lock up your sys...guess how I found out I haven't gone through everything but they're the ones I do know to stay away from. :wink: generally kernel stuff.

[pmpatrick]

It may be an ACPI problem, but the symptoms you describe are also well documented bugs with certain ATI grapics cards. I had the identical problem with my Radeon 7500 with both Mandrake 9.1 and Knoppix/Debian, both of which use the new XFree. Fortunately there is already a fix in rpm form for Mandrake 9.1. Check out this link if your laptop has an ATI graphics adapter:

 

http://www.zebulon.org.uk/