Hi,

I have formatted my HDD and installed again both OS (WinXP pro and SUSE 10.0). The reason was a virus which destroyed my MBR and I was not asble to repair it. But this is not a point. A point is that after successfully installing both systems, everything was working fine. SUSE, when installed, was updated via YAST and then the problem began. Kernel was upgraded so was KDE(to ver. 3.5)and some other packages. I rebooted and when( in text mode before login screen)it reaches the line:

Starting powersaved 8accessing ACPI events over acpid) everything stopped, the cursor is blinking, I can write , but nothing happened. It is like the comp is in a suspended mode??? I can switch it of by pressing power switch off/on or by reset switch. The resulčt is the same. When reaching the same spot it stops. I have disabled ACPI in BIOS, the same resul. What can I do?(besides reinstall SUSE)???

Hello riba,

The short answer as far as I have been able to make out in my
I've had the same problem; the only solution I could come up was to reinstall SuSE 10. Fortunately, I had my /home directory on a second hard-drive with SuSE installed on my primary/first hard-drive.

In my case the boot-up process used to hang at 'starting amavisd-new'. So I booted up in fail-safe mode, and then called up yast2 on the command line, and uninstalled everything to do with amavisd. Then boot-up process used to hang in the next line up 'starting acpid'. So again, I'd boot up in fail-safe mode, call up yast2 from the commmand line, and uninstall everything to do with acpi. Third time round, the boot-up process hung at 'starting HAL daemon'. Not being a script-kiddie, but just a desktop user, I just re-installed SuSE 10. And I'll be sticking to KDE 3.4 !!
But of course, all this relatively painless for me, as I've got my /home directory on my slave HDD.

I'm sorry I couldn't help you with a method for solving the problem, but you are not alone in having a problem with this matter.

Regards
bunyip

Actually, it is not a good idea to upgrade KDE to version 3.5.
The kernel-update on my computer was sucessfull.

I have reinstalled SUSE and now !!! everything is O.K.
I thought that KDE upgrade is the reason for the error.

Thanks guys!

This is a timely post - I've reinstalled twice in as many days with the same problem (I have /home on another partition so not *too* much of a pain). Being the idiot that I am, I am updating to KDE3.5 as I type...

This is a strange problem. I was using KDE 3.5 for ages without facing a single issue. Then as discussed, I rebooted a few days ago and it hung at 'starting vmware services' (I forget the exact message). I reinstalled, updated to KDE3.5 and I thought all was good. Rebooted and it hung again.

Well, I for one will not be updating to KDE3.5 if this happens again (3rd time lucky?). In fact, I recently installed Arch a few days ago on a spare partition. Although yet to tinker with it, it looks very promising (KDE3.5 as standard). However, that is another story .....

There is a thread that explains this problem, http://www.linuxquestions.org/questi...d.php?t=419793

There's no need to reinstall SuSE. Essentially there is a problem with the package kdebase3-kdm version 3.5.1-27. Read the thread you'll find several ways to to a workaround for this problem.

Hey man, this worked. Nice. I thought this problem was strange and having just read a few posts on the board I see it is a common problem.

Hi guys,

I could not help, but I just went and upgraded my SUSE 10.0 again. This time I used synaptic for upgrading. There wasonly one difference. Following the suggestions in this thread, I unchecked the kdebase3-kdm for upgrading and it works. I have system upgraded to the last version and after rebooting everything works.