Thanks, I will try that. I have noticed some oddities with my network drivers, so perhaps this will solve those as well.

I need to pose a thought for you: was this laptop previously used with a higher-resolution external monitor? Could be causing the problem somehow, but someone who knows something (not 'more', just 'something'! )about such a setup would have to help you further here.

FWIW, I always set Linux up to start in runlevel 3 (text login) instead of rl 5 (graphical login), and set lilo or grub to text also. This was mentioned by henchard in the long message above; about paragraph 10 counting by blank lines.

Once I am logged in that way, I have Ctrl-Alt F1~~F6 text consoles (but each needs its own login, as root or any other user).

To start your usual graphical desktop, simply type
startx
& press enter, & there you go.

Two advantages to this all-text startup:

1) even if the graphics get mesed up, you can still log in with the consoles & multi-user availability, and

2) I have found that the text-text then startx has less problems anyway, for RH9, Mdk 8.1 & 9.2, and SuSe 7.3 & 9.0, on a variety of cpu/vcard/&c computers.

Best Luck To All !

Well, that confirms it, I think.
I disabled automatically starting eth0, and while the first few reboots I ran into the same problem, everything since has been good.
Still got the network problems though, but that is for another forum.

Ditto - very useful

Especially if you need to get to the PC and a particular file (or website, using links) very quickly without waiting for X and KDE to kick into gear.

I have had this problem before also. Same thing, hanging at restoring session (85%), same knotify error message. If your board has on-board sound it could be the problem, causing an issue with aRts. After much head-ache, and many different drivers I finally disabled my on-board sound in the system bios. Installed a pci sound card, configured, and was up and running, havn't had any trouble since.

Simply disabling my O.B. audio made it so I could log in properly. If you do not have on board audio, try a different driver for your audio card. If you cannot get into kde at all you can login under gnome, go to configure computer and create a new user, every time you create a new user you can login into KDE once with that user.

I to thought it was etho causing the problem but after disabling that and clearing my restore session option I still had trouble. O.B. audio? Just a thought. Good Luck.