Packard Bell (portable)/mandriva 2010 free freezes when about to select user

Torben Friis · 09-01-2010, 06:38 AM

I then have to shut down the computer. When restarting, it corrects files on sda5, reboots the computer aut. and it works (and there are no errors in syslog). When I shut down normally I see in the shutdown sequence that there is an error (ECHEC in red), but it goes too fast for me to see what it is. It looks like some files are destroyed in shut down.
Pressing "I" during start up does'nt work, and I can't slow the shut down sequence.

business_kid · 09-02-2010, 04:41 AM

Shutdowns are logged also, you know in /var/log/messages you find most of it.
Never tried this, but you could try
shutdown -r now > somefile 2>&1

make sure somefile is on the root partition, as it's the last to be unmounted

Torben Friis · 09-06-2010, 03:11 AM

Quote:

Originally Posted by business_kid

Shutdowns are logged also, you know in /var/log/messages you find most of it.
Never tried this, but you could try
shutdown -r now > somefile 2>&1

make sure somefile is on the root partition, as it's the last to be unmounted

Hi business kid,
Thank you for your reply - I have been trying out stuff. I tried your command: shutdown -r now > /christian 2>&1 where /christian is a file created in gedit. It deleted the contents of /christian (no problem), but did not write anything. Did I do anything wrong?
So far I have not had any success, so I may have to wait until a new Mandriva version solves the problem.
I have tried cat /var/log/messages and cat /var/log/syslog. It is beyond me to understand the output, but I don't see anything indicating errors. And yet I saw the word ECHEC (french for failure) flashing by at shut-down. Is there a way to store these messages as they appear on the screen? Caps-I doesn't work at start-up.
When I reinstall the system and reboot it works OK. But thereafter I have to shut down the computer at least once so it can correct the files.
I use GNOME, but have tries KDE, but then the desk top does not appear.
It seams to be a graphics problem, because that is where the system stops.
Best regard
torben

business_kid · 09-07-2010, 03:11 AM

grep /the logs for words like failed, error, and anything else you can think of.

Failures on shutdown are an indication something may have gone out to lunch before the shutdown. If you really can't read it, try a photo of the screen. Even a poser phone can get a legible photo of the screen.

Torben Friis · 09-07-2010, 07:24 AM

Quote:

Originally Posted by business_kid

grep /the logs for words like failed, error, and anything else you can think of.

Failures on shutdown are an indication something may have gone out to lunch before the shutdown. If you really can't read it, try a photo of the screen. Even a poser phone can get a legible photo of the screen.

In syslog and messages I find ACPI Exception/- Error/ firmware bug.
Fx.:
Sept 6 09:37:54 localhost kernel: ACPI Error (psparse-0537):Method parce/Execution failed[\_PR.CPUO._PSSJ Node.db410ee8),AE_AML_PACKAGE_LIMIT

In a very long record covering many, many lines I find ...lastError.../...BusError.../...Exception.
Apparently a problem with ACPI - what is that?
Very confusing to me.

I think that I have attached the result of cat....|grep....Error > /home/kirsten/attestations.txt.
Regards
torben
PS! First attempt at photo failed.

business_kid · 09-08-2010, 03:17 AM

Google (1st search result) tells me it's a bug. I'm not the only one allowed to use google, you know:-)).

http://www.mail-archive.com/acpi-bug.../msg10659.html

Try updating your distro - they might have it fixed in the updates