Can't login anymore because there is nothing on the screen to enter the login/password

Hi, today I tried booting up my computer but I can’t log on it anymore since the only thing displayed on the screen is the default login theme and nothing else. There is no dialog to type anything.

I am pretty new to linux, so any help is really appreciated.

Thanks.

Can you please at least tell us which version of openSUSE you use.
And also which desktop environment (KDE, Gnome, other).

And some more omformation about your problem when possible or is this immedialtly after installation? When it did function earlier, do you have any idea what you changed latley (e.g. some update or software install).

Remember we are not clairvoyant. We need your precise descriptions to get any idea about what might be wrong.

Sorry for the incomplete post before.

I am running KDE4 with the lateste stable update (I used the terminal about 1hr ago to try and update it) and running OpenSuse13.1.

I have used the system for about 1 month without any problems and yesterday the only thing I did was trying to install some h264 codec packs (ffmpeg). I also installed nvidiag02 (or something close to that) from Yast and later on removed the same package.

Is there a way to workaround the login screen? Like login from the terminal and then start X already logged? Right now I am at my workplace staring at the monitor with no idea how to start solving this.

Thanks again.

EDIT: Tried booting up in recovery mode and the log on screen gets halted on “[OK] Reached targeted Graphical Interface”. After this, nothing happens

Well, as you were tinkering with nvidia packages, I would say that that went wrong somewhere. That must be repaired. What if you choose the Advanced option from the GRUB bootscreen and then the use the recovery mode?

Try to use a different login manager, like xdm f.e. (should be installed by default)
You can set this in /etc/sysconfig/displaymanager (variable “DISPLAYMANAGER”).

And please post a picture of your Login Screen, maybe that provides a clue what could be wrong.
I would guess it’s theme-related though, so try to switch to a different one in “Configure Desktop”/systemsettings->“Login Screen” or turn theming off altogether.
And try to re-install kdm’s openSUSE theme package:

sudo zypper in -f kdm-branding-openSUSE

I think nvidia package shouldn’t be the problem, otherwise I shouldnt see anything graphical related, right? Right now I can see the opensuse background image, just the login form is missing.

When I said I tried booting in recovery mode, I was talking about selecting advanced options > recovery mode. I don’t know another way to boot up in recovery.

I looked around everywhere in the web and the best I could found was someone talking about killing /usr/lib64/kde4/libexec/kscreenlocker_greet which I have no idea how to do

It is definitly kdm related. I tried chaging to xdm and now I can login into the system, even though I have no network (something about p5p1 failing to lookup dns) and the xdm looking ugly as hell.

Here is a pic of what I was talking about: Imgur: The magic of the Internet

As you can see there is nothing else on the screen but the background…

Uhuuu reinstalling the opensuse theme did the trick! You are a boss!

Any idea what might have caused the problem?

Thanks a lot, you saved me! (posting from my linux system)

I suspect that when you uninstalled the NVIDIA what ever package you also uninstalled other parts of the NVIDIA driver. So if you now have a usable desktop go to Yast and reinstall the NVIDIA drivers. If you don’t know which version to install tell us you card and we will givemoe detailed instructions. Do NOT just install anything that has NVIDIA in the Name mixing driver version will cause problems.

This is the card I am using:

VGA compatible controller [0300]: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller])        Subsystem: Dell Device [1028:0576]
        Flags: bus master, fast devsel, latency 0, IRQ 45
        Memory at f7400000 (64-bit, non-prefetchable) [size=4]
        Memory at d0000000 (64-bit, prefetchable) [size=256]
        I/O ports at f000 [size=64]
        Expansion ROM at <unassigned> [disabled]
        Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
        Capabilities: [d0] Power Management version 2
        Capabilities: [a4] PCI Advanced Features                                                                                                                                  
        Kernel driver in use: i915                                                                                                                                                
        Kernel modules: i915   

Which driver should I install then?

Right now I have installed (according to Yast when searched for “nvidia”):
nvidia-computeG03

|nvidia-gfxG03-kmp-desktop
|

xf86-video-nv

xorg-x11-driver-video-nouveau

libdrm_nouveau2

libdrm_nouveau2-32bit
|

[/size][/size][/size]

Not necessarily.
There could be just some specific graphic issues.
I doubt that it would cause something like you describe, though.

When I said I tried booting in recovery mode, I was talking about selecting advanced options > recovery mode. I don’t know another way to boot up in recovery.

That’s what he meant.
Normally this should even boot to a graphical system even when your graphics driver installation is broken.

Maybe you miss the file /etc/X11/xorg.conf.install?

I looked around everywhere in the web and the best I could found was someone talking about killing /usr/lib64/kde4/libexec/kscreenlocker_greet which I have no idea how to do

That’s completely irrelevant here.
kscreenlocker_greet shows the screen locker’s password dialog.
There was a bug in KDE that it didn’t show the dialog under certain circumstances when a password was required after resuming from sleep/hibernate.
Killing kscreenlocker_greet would make the dialog appear, as kscreenlocker_greet would be restarted automatically in this case.

But that issue should be fixed already anyway.

That is NOT a NVIDIA it is some flavor of Intel. Is this by any case a notebook and does it have 2 graphics cards Intel+NVIDIA

If so you need some special programs to manage such a configuration

This is not a laptop, it is one of those business desktop sold by Dell. I do have 2 graphics card though, but I am using the onboard one.

# lspci -vnn | grep VGA -A 12

00:02.0 VGA compatible controller [0300]: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller])
        Subsystem: Dell Device [1028:0576]
        Flags: bus master, fast devsel, latency 0, IRQ 45
        Memory at f7400000 (64-bit, non-prefetchable) [size=4]
        Memory at d0000000 (64-bit, prefetchable) [size=256]
        I/O ports at f000 [size=64]
        Expansion ROM at <unassigned> [disabled]
        Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
        Capabilities: [d0] Power Management version 2
        Capabilities: [a4] PCI Advanced Features                                                                                                                                  
        Kernel driver in use: i915                                                                                                                                                
        Kernel modules: i915                                                                                                                                                      


--
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF119 [GeForce GT 620 OEM] [10de:1049] (rev a1) (prog-if 00 [VGA controller])
        Subsystem: NVIDIA Corporation Device [10de:0977]
        Flags: bus master, fast devsel, latency 0, IRQ 16
        Memory at f6000000 (32-bit, non-prefetchable) [size=16]
        Memory at e0000000 (64-bit, prefetchable) [size=128]
        Memory at e8000000 (64-bit, prefetchable) [size=32]
        I/O ports at e000 [size=128]
        Expansion ROM at f7000000 [disabled] [size=512]
        Capabilities: [60] Power Management version 3
        Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+
        Capabilities: [78] Express Endpoint, MSI 00
        Capabilities: [b4] Vendor Specific Information: Len=14 <?>
        Capabilities: [100] Virtual Channel



[/size][/size][/size][/size][/size][/size][/size][/size]

I doubt that the network issue is related… :wink:

Although using xdm instead of kdm might result in your user session not correctly being registered with logind, which causes all sorts of issues (because of insufficient permissions) like not being able to connect to the network or mounting USB devices.
But that’s just a guess. Doesn’t really matter now because kdm is working again… :wink:

Here is a pic of what I was talking about: Imgur: The magic of the Internet

As you can see there is nothing else on the screen but the background…

I’m not convinced that kdm is even starting.
This screen looks like the openSUSE plymouth boot splash.

Did you see a mouse cursor? I cannot spot one on your picture, so I don’t think Xorg is running.

Not really. Maybe some theme files got removed or damaged somehow which prevented kdm from starting.

Just to give further information:

I was not able to see the mouse cursor, just the background image and indeed the network issue was not related (easily fixed that). Right now when I login I see the splash image with a loading icon. Only after that the screen flashes and then the login form shows up. This behavior didn’t happen before, but it is not an issue.

The onboard one is the intel, right?
So you should not install the nvidia driver, as this breaks the intel driver.

PS, regarding recovery mode:

If kdm really failed to start because of the damaged kdm-branding-openSUSE, it would of course also fail to start in recovery mode as well.
This would cause the system to drop back to text mode.

In normal mode, you still see the plymouth splash screen though (because it is not stopped by kdm), pressing ESC would probably get you to text mode.

So, should I remove nvidia-computeg03 and nvidia-gfxG03-kmp-desktop? I already have installed xf86-video-intel and vaapi-intel-driver

Again guessing Bet the onboard graphics is the Intel. The NVIDIA is doing nothing just eating power. Run kinfocenter and see which is the active card

If you want to use the NVIDIA you will need to disable the Intel in the BIOS or make a custom xorg.conf file

Intel and NVIDIA are different and don’t work together Use one or the other

So actually kdm indeed failed to start, what you saw was plymouth, not kdm.

Right now when I login I see the splash image with a loading icon. Only after that the screen flashes and then the login form shows up. This behavior didn’t happen before, but it is not an issue.

I don’t really understand what you mean here.

You should see the splash image without any “loading icon” during boot.
Then when kdm is starting the screen should go black and show a “busy” mouse cursor, until it finished loading and then shows the greeter (with the user/password input).

Because you played around with the nvidia driver, you should maybe check that the intel driver is still working now.
Please install the package “Mesa-demo-x” and post the output of:

glxinfo | grep render

Btw, for your nvidia card you would need the G03 driver (although the G02 one should work as well).
But again, DO NOT install the nvidia driver when using the onboard (intel) graphics. This will break Mesa and the intel driver because it replaces some system libraries (libglx and libGL) with its own incompatible versions.

It shouldn’t be necessary to disable the onboard graphics (I never had to do this on any of my systems).
And you definitely don’t need a custom xorg.conf file.
Just connect the monitor to the nvidia card and X should find it.

Intel and NVIDIA are different and don’t work together Use one or the other

This isn’t completely true.
Of course they are different, but they should be able to work together, at least with the nouveau driver. But I have no idea if you would really be able to use both at the same time, I have to say.
Installing the nvidia driver breaks the intel driver though, as explained already.