LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Suse/Novell (http://www.linuxquestions.org/questions/suse-novell-60/)
-   -   Why I have to reboot my comp each and every day, after switch on SUSE 11.0 (http://www.linuxquestions.org/questions/suse-novell-60/why-i-have-to-reboot-my-comp-each-and-every-day-after-switch-on-suse-11-0-a-654007/)

riba43 07-07-2008 02:28 AM

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??

AceofSpades19 07-07-2008 02:46 AM

What happens if you press ctrl-alt-backspace?

riba43 07-07-2008 03:06 AM

Quote:

Originally Posted by AceofSpades19 (Post 3206247)
What happens if you press ctrl-alt-backspace?

Never tried that. Next time i will try and report. Thanks for help.

riba43 07-08-2008 02:06 AM

Hi AceofSpades19,

Nothing happened when ctrl-Alt-backspace.

bigrigdriver 07-08-2008 02:22 AM

Run this command in a terminal:
Code:

grep default /etc/inittab
Do you see this?
Code:

# The default runlevel is defined here
id:5:initdefault:

The line *id:5:initdefault:* sets the default runlevel at runlevel 5. If your /etc/inittab shows a different number, change it to 5.

Save the file, then test it by re-booting? You should be able to boot to GUI mode (runlevel 5).

riba43 07-08-2008 03:08 AM

Quote:

Originally Posted by bigrigdriver (Post 3207369)
Run this command in a terminal:
Code:

grep default /etc/inittab
Do you see this?
Code:

# The default runlevel is defined here
id:5:initdefault:

The line *id:5:initdefault:* sets the default runlevel at runlevel 5. If your /etc/inittab shows a different number, change it to 5.

Save the file, then test it by re-booting? You should be able to boot to GUI mode (runlevel 5).

Hi,
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.

riba43 08-05-2008 03:29 AM

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???

garyg007 08-07-2008 07:24 PM

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?

riba43 08-08-2008 01:14 AM

Quote:

Originally Posted by garyg007 (Post 3240338)
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?

Well, nothing. I just get a login screen. When I enter my name &password, the same thing happened - a black screen with mouse pointer. I must reboot and then everything works.

Sjonnie48 08-08-2008 06:32 AM

So, after hitting Ctrl+Alt+F2 (F4) you have an active shell.
Did you try startx?

garyg007 08-08-2008 09:24 AM

Quote:

Originally Posted by riba43 (Post 3240538)
Well, nothing. I just get a login screen. When I enter my name &password, the same thing happened - a black screen with mouse pointer. I must reboot and then everything works.

Lower left of the screen, click on "session type" what does it show? Can you tell what it shows as the default?

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.

riba43 08-08-2008 11:04 AM

Hi,
There is only KDE4, no KDE3

ronlau9 08-08-2008 11:58 AM

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

garyg007 08-08-2008 03:11 PM

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.

riba43 08-25-2008 03:00 PM

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 05:36 AM.