Boot Stops At "Starting Powersave"

Red Knuckles · 02-26-2006, 01:53 PM

When trying to boot into Suse It stops at the line "Starting Powersave: [accessing ACPI events over acpid]". How do I fix this??? I can log into Ubuntu and Suse Failsafe. In Suse Failsafe I do a console login and then run 'startx' so I am in Suse now.

msusten · 02-26-2006, 03:07 PM

New to SUSE. My fsatb is the same as the mount.
However, I believe(?) that the drives are reversed. dev/hdc media/dvd is the cdrw and the
dev/hdd media/cdrecorder is the cdrw.

When i put a cd in the cd nothing happens. When I put a cd in the dvd the suse software can read the songs, reject disc works, but no sound?
Help.

Thanks

mark

crazibri · 02-27-2006, 09:26 AM

Knuckles, I'm having the same problem after updating packages via Software Management. I've been trying to roll the packages back but no go.
Failsafe works though. I posted my work around in this thread:
http://www.linuxquestions.org/questi...d.php?t=419776

Let me know if you find an issue. It seems to be releated to init 5 not kicking in correctly.

Red Knuckles · 02-27-2006, 12:22 PM

Quote:

Originally Posted by crazibri

Knuckles, I'm having the same problem after updating packages via Software Management. I've been trying to roll the packages back but no go.
Failsafe works though. I posted my work around in this thread:
http://www.linuxquestions.org/questi...d.php?t=419776

Let me know if you find an issue. It seems to be releated to init 5 not kicking in correctly.

After a recent update I got the same problem. On mine when it freezes up at "Starting Powersaved" I press CTRL+D and it finishes rebooting. Hope this helps.

Red Knuckles · 02-27-2006, 12:49 PM

How and where do I file a bug report???

emg · 02-27-2006, 01:20 PM

Quote:

Originally Posted by crazibri

Knuckles, I'm having the same problem after updating packages via Software Management. I've been trying to roll the packages back but no go.
Failsafe works though. I posted my work around in this thread:
http://www.linuxquestions.org/questi...d.php?t=419776

Let me know if you find an issue. It seems to be releated to init 5 not kicking in correctly.

The problem is with the kdebase3-kdm xx.xx-27.rpm .... roll it back to the kdebase3-kdm xx.xx-18.rpm and you should be good to go ... this has been talked about alot in IRC (freenode.org) #suse channel ....

jomen · 02-27-2006, 01:36 PM

This might well be a bug - but rather one in your motherboards Bios - the ACPI-implementation to be more specific.
You could - to narrow the problem down - turn off ACPI.
Eighter on boot with an additional boot-option - I believe: noapic acpi=off
- add this to the kernel ... line in /boot/grub/menu.lst
or
take out the service (Starting Powersave) - disable it so it is not executed anymore on boot.
Sorry, but I don't know how to do that in suse. Usually the init-files are executable shell-scripts. If you change this one to be not executable - it will probably not be executed (with a message on boot saying so but it will still go on)
If it is the problem - try using APM instead of ACPI

pilotgi · 02-27-2006, 04:29 PM

I'm having the same problem. Hitting ctrl-d worked for me when the boot stalled at powersave. I'm not getting connected to my network at boot any more either. I have to restart the network then it works fine.

I rolled kdebase3-kdm back to 3.5.1-18 and it makes it through the boot process now but I still have to restart my network to connect.

Edit: I tried turning off acpi but that didn't help.

victorh · 02-27-2006, 07:22 PM

Well, I'm officially joining this club. I also have this problem. It started today after I did the normal update using YaST, among the updates I traced the followings kdebase3 3.5.1-27, kdebase3-kdm 3.5.1-27, kdebase3-ksysguard 3.5.1-27, kdebase3-samba 3.5.1-27 and kdebase3-session 3.5.1-27. I left my system for about an hour and when I came back the monitor was off (normal) but when I moved my mouse or type anything in the keyboard the monitor couldn't start. I was forced to do a hard reboot.

But when I reboot in SuSE, the process stopped in the following line:

Quote:

Starting powersaved (accesing ACPI events over acpid)

I boot again but this time with failsafe, login as my normal user, type startx and I was back in KDE, exactly as crazibi pointed out.

After reading this thread I decided to try the workaround provided by Red Knuckles and it also worked. Thanks Red Knuckles. I noticed one unusual thing, when the system is going dowm for reboot a window appears with a warning saying "The powersave daemon is not running".

I was tempted to roll back the kdebase3 package but I supposed I have to do the same with all the kde packages updated?

Right now I can use the workaround (Ctrl+D) to boot in SuSE, but what I keep wondering is: if I left my system again for more than 15 minutes and the monitor shut down, will I gain back control of the system?

emg · 02-27-2006, 07:39 PM

Quote:

Originally Posted by victorh

Well, I'm officially joining this club. I also have this problem. It started today after I did the normal update using YaST, among the updates I traced the followings kdebase3 3.5.1-27, kdebase3-kdm 3.5.1-27, kdebase3-ksysguard 3.5.1-27, kdebase3-samba 3.5.1-27 and kdebase3-session 3.5.1-27. I left my system for about an hour and when I came back the monitor was off (normal) but when I moved my mouse or type anything in the keyboard the monitor couldn't start. I was forced to do a hard reboot.

But when I reboot in SuSE, the process stopped in the following line:

I boot again but this time with failsafe, login as my normal user, type startx and I was back in KDE, exactly as crazibi pointed out.

After reading this thread I decided to try the workaround provided by Red Knuckles and it also worked. Thanks Red Knuckles. I noticed one unusual thing, when the system is going dowm for reboot a window appears with a warning saying "The powersave daemon is not running".

I was tempted to roll back the kdebase3 package but I supposed I have to do the same with all the kde packages updated?

Right now I can use the workaround (Ctrl+D) to boot in SuSE, but what I keep wondering is: if I left my system again for more than 15 minutes and the monitor shut down, will I gain back control of the system?

Just rollback the kdebase3-kdm package or edit your services and disable earlykdm ... either will fix the problem

crazibri · 02-27-2006, 10:01 PM

Is there a rollback option in Yast or is that a konsole function?

Also, I found a better workaround than the one I published earlier. If on my grub boot option, I just add "3", it will boot only to runlevel3. Then I just log in and type KDM. It works similar to "failsafe" but just without all the ACPI disabling.

I went and disabled earlykdm so its not checked at any runlevel and it rebooted perfectly.

jomen · 02-28-2006, 03:20 AM

Quote:

Is there a rollback option...

rollback the kdebase3-kdm package -> downgrade to the version you had installed before
edit your services and disable earlykdm -> this it the better solution I think

victorh · 02-28-2006, 09:44 AM

Thanks for the suggestions jomen, when I go to YaST -> Software Management and select kdebase3-kdm, you have the options:
Keep
Delete
Update
Protected
To rollback this package you have to delete it? Or I use other option?. I'm afraid that if I delete this package this will cause serious unmet dependencies from the other packages.

Anyway, when I came back this morning I could start again the monitor and everything is working fine, except that I think that I don't have the powersave daemon running. Normally I don't shut down my system, is the powersave daemon necessary?

jomen · 02-28-2006, 11:48 AM

maybe "Update" - but with the older version?
If you ask me - "Delete" and then install the older version.
I don't know how this is done in suse - there are several ways and I'm not familiar with eighter one.
Why don't you just disable the service like emg suggested?

EclipseAgent · 02-28-2006, 11:00 PM

You can boot into boot level 3, or failsafe mode, then run startx, that will get you in, then you can roll back the install or turn off the bad service.. kind ashitty.. IMO..

How the hell did that pass QA?