-   SUSE / openSUSE (
-   -   No KDE Login screen (

sirsharp1 06-02-2005 07:41 PM

No KDE Login screen
I've been running Suse 9.3 Pro and each time I reboot it, I get further and further from being able to run KDE.
Lately, after booting up, I get a grey screen with a login and password prompt plus a console window in the corner.
In the console window is displayed the following message:

sector 0
Jun 2 17:13:38 linux ifup: No configuration found for sit0

I'm not sure what that means and I don't know how to proceed.

If I type in my username and password, I'm taken to another screen that is the same grey color with the same console window displayed in the corner. If I left click anywhere on the grey area, I get a menu. At the top of the menu is the title "TWM"

I want my KDE back!

Any suggestions? Is it possible that the message I'm getting in the console window regarding ifup and sit0 are unrelated to the grey screen with the TWM?

crazibri 06-03-2005 01:50 AM

Hmm I cant really explain why its doing the ifup stuff but it sounds like you're just in X w/ no KDE

Try logging in as root and typing "kdm" and see what you get. Thats the command to launch KDE.

Xian 06-03-2005 05:44 AM

Look here: KDM Login Problems

bkadkins 06-13-2005 09:47 PM

No KDE Login screen
On the login screen: Go to 'menu'-> Session type -> and make sure 'KDE' is checked. TWM is a window manager that usually comes with SuSE.

As for sit0, it's the interface to tunnel IPv6 packets over IPv4 networks. Unless you are using IPv6 (99% of the net period is not equipped to), this is nothing to worry about. Comment out the lines (i.e., # at the beginning of the line) in /etc/modprobe.conf if the msg bugs you.

alias sit0 ipv6
alias net-pf-10 ipv6

if you get this error: inux kernel: end_request: I/O error, dev fd0, sector 0, ...just means that the kernel sees that you do not have a floppy in the drive. Not all errors ar e bad some like this are just 'fyi's' to the user...

hope this helps :D

abisko00 06-14-2005 03:37 AM

Xian's link will help you. It seems to be a common problem of 9.3.

I don't think that the message about sit0 affects your system or is causing this behaviour. It is just a message from the syslog system.

All times are GMT -5. The time now is 01:05 AM.