Why I have to reboot my comp each and every day, after switch on SUSE 11.0
Hi.
A very strange behaviour of my comp I noticed, after installing SUSE 11.0. Each day, after cold boot, my comp stopped after login screen, with a black screen and a cursor blinking. I have to Ctrl+Alt+F2 (F4) and enter the command as root "Shutdown -r now". Only then the comp boot into SUSE 11.0. After that, everything works normally. But next day, I have to repeat the procedure again. Any suggestion?? |
What happens if you press ctrl-alt-backspace?
|
Quote:
|
Hi AceofSpades19,
Nothing happened when ctrl-Alt-backspace. |
Run this command in a terminal:
Code:
grep default /etc/inittab Code:
# The default runlevel is defined here Save the file, then test it by re-booting? You should be able to boot to GUI mode (runlevel 5). |
Quote:
this is what I get: bogomir@linux-58xe:~> grep default /etc/inittab # The default runlevel is defined here id:5:initdefault: # runlevel 0 is System halt (Do not use this for initdefault!) # runlevel 6 is System reboot (Do not use this for initdefault!) bogomir@linux-58xe:~> Seems to be O.K. |
Hi everybody,
Still no solution for that. This is very annoying. Every day when I switch my computer on, I have to reboot it to get SUSE desktop back. Do you have any idea how to correct this??? |
ctl+alt+backspace works a little different in suse 11.0;
While holding down ctl+alt, hit backspace twice within two seconds - What happens then? |
Quote:
|
So, after hitting Ctrl+Alt+F2 (F4) you have an active shell.
Did you try startx? |
Quote:
After you get the blank screen and reboot, when you get the sign on screen, does the "session type" show anything different from the first time? If the list under "session type" has kde4 as current, try selecting kde3 and sign in. |
Hi,
There is only KDE4, no KDE3 |
If you think that the problem could be kde4 , it possible to install kde3.5
Easy way of course when the system is up Startup yast>filter>choice patterns> kde3. in the window below filter After install restart at login screen goto session type choice kde3 |
I agree with ronlau9, that there is a good possibility the problem is with KDE4.0, which has been quit buggy; 4.1 is better, but it is still buggy. KDE 3.5.9 is the best bet.
Where I was headed was to try and find what worked and what made it different from what did not work. Shut the computer down - to power off. Then power it on and let it boot (make note of anything that may be on the grub command line before it boots). before doing anything with the sign-on screen look at the "session type" tell us what the default is. then let it fail, and do what you do to get it started; again, when you get the signon screen, check the session type and tell us what the default is this time. |
Hi garyg007 & ronlau9 ,
Sorry for beeing so late but I was on holidays for the last 18 days. Now I wabnted to try what you suggested, but I got another error message and I cant enter anything in YAST2. The Xmessage is: "Error while creating client module sw_single" I do not know what that means and when it happened. |
All times are GMT -5. The time now is 12:16 AM. |