Lack of GUI login after upgrade - SuSE v10.0 to openSuSE v 10.2

Forums › Linux › Lack of GUI login after upgrade - SuSE v10.0 to openSuSE v 10.2

Alpnz

15 posts

Geek

#16454 11-Oct-2007 08:54

Has anyone had a similar experience.
I upgraded one box without any drama ... the second one which used GNOME I upgraded choosing to load KDE as well to have similar desktops.
Now I get only a boot to VT0, console. If I log in and call KDM I get the GUI login on tty7. In other words the GUI manager is not configured correctly. I get a message on a reboot saying the x server is not working, or not setup correctly. If I set it up etc and save it no change. Any ideas?

chakkaradeep

799 posts

Ultimate Geek

Trusted

#90599 11-Oct-2007 09:48

Alpnz: Has anyone had a similar experience.
I upgraded one box without any drama ... the second one which used GNOME I upgraded choosing to load KDE as well to have similar desktops.
Now I get only a boot to VT0, console. If I log in and call KDM I get the GUI login on tty7. In other words the GUI manager is not configured correctly. I get a message on a reboot saying the x server is not working, or not setup correctly. If I set it up etc and save it no change. Any ideas?

From the VT0 login, log in as root, and configure your X server again with SaX2. So, just run the command Sax2 and see whether it configures or not and also dont forget to check your runlevel

Regards,
Chaks

Desktop : Intel Quad Core Q9400 2.66GHz - 8GB RAM - 500 GB + 500 GB HDD - NVidia GeForce 9800GT - LG246WH Flatron Display - Windows Server 2008 R2 Enterprise with Hyper-V
Virtual Machine : Powered by Hyper-V and VMWare Workstation
Laptop: HP dv7-3004TX Entertainment Notebook PC | HP Touchsmart tx2 1119au - Windows 7 Ultimate x64
Mac: iMac 21.5" Snow Leopard
Mobile : iPhone 3GS

Alpnz

15 posts

Geek

#90663 11-Oct-2007 15:39

Oh that I am aware of, what I am saying is that after running SaX2 and saving the settings etc, it still wont reboot.
KDM is not available to set the runlevel on, and a serach of packages on the install dvd fails on KDM, so I am not sure what I am looking for to get KDM to work on the Boot. Many thanks for your help ...

barf

643 posts

Ultimate Geek

#90676 11-Oct-2007 16:48

I don't use SuSE but kdm is usually stored outside of the default PATH, so typing 'kdm' isn't going to work specify the full path to it like '/opt/kde/bin/kdm'

actually, I think your kdm will be working fine and your /etc/X11/xorg.conf needs a tweak instead
type 'X' to test if your xorg.conf is configured properly, if it is you will be able to move the mouse on a blank screen, use ctrl-alt-backspace to bail out
you'll get an error otherwise pointing to the problem

Sniffing the glue holding the Internet together

Alpnz

15 posts

Geek

#90718 11-Oct-2007 20:13

X works fine always has ...

One thing I did find during a quick look today, was a the install had not been configured correctly, in that no display manager had been set in sysVconfig, I have set it to KDM but did not have time to reboot to check it out, so will have to wait for a result on that one. Possibly this was caused by some sort of conflict during the change to KDE, and yet I have done this in the past without many problems ... not that this is a major, as it is on a server.

One thing of note is that the screen does not appear to go to standby after 30 mins, which suggests some sort of power settings are not set up right as well.

Time and patience will have it back to good health, just finding the time is a challenge.

regards to all helpers

Alpnz

15 posts

Geek

#90863 12-Oct-2007 21:10

OK system back up and running ...

I am assuming that when I chose to install KDE over the GNOME setup, there were some legacy files in thar that did not like the arrangement.

By removing GNOME completely, it got lost ... using the yast syconfig in the system part of yast it is possible to set the Login manager to KDM, however this will not rid you of the old GDM, as underneath the Display manager, is a selection for the window Manager, and it must be changed to KDE, I found mine set to GNOME after 3-4 tries at setting the display manager to KDM, only to watch SuSEConfig set the GDM display manager. After changing to KDE all came right.

I assume that SuSEConfig sees GNOME as the window manager, and defaults to GDM, and if GNOME is not there, you have no Display manager.

This is all a bit mish mash, however it is possible sort it out, so if this happens to you, just be patient, and attend to your sysconfig settings. Possibly best to let sleeping dogs lie for a bit, before running an upgrade to 10.3

x1Ler

1 post

Wannabe Geek

#92903 29-Oct-2007 14:55

Annoyed that I finally found someone that fixed this problem, but you didn't list exactly how you did it so what the heck is the point in posting if you don't say what you did EXACTLY? eh?

chakkaradeep

799 posts

Ultimate Geek

Trusted

#92952 29-Oct-2007 17:47

Alpnz: OK system back up and running ...
I am assuming that when I chose to install KDE over the GNOME setup, there were some legacy files in thar that did not like the arrangement. By removing GNOME completely, it got lost ... using the yast syconfig in the system part of yast it is possible to set the Login manager to KDM, however this will not rid you of the old GDM, as underneath the Display manager, is a selection for the window Manager, and it must be changed to KDE, I found mine set to GNOME after 3-4 tries at setting the display manager to KDM, only to watch SuSEConfig set the GDM display manager. After changing to KDE all came right.
I assume that SuSEConfig sees GNOME as the window manager, and defaults to GDM, and if GNOME is not there, you have no Display manager.
This is all a bit mish mash, however it is possible sort it out, so if this happens to you, just be patient, and attend to your sysconfig settings. Possibly best to let sleeping dogs lie for a bit, before running an upgrade to 10.3

Wat was the default desktop manager in /etc/X11/default-desktop-manager ? Do you remember that ? I have a doubt that that was set to /usr/bin/gdm and not /usr/bin/kdm

Sharesies

Trade NZ and US shares and funds with Sharesies (affiliate link).

Alpnz

15 posts

Geek

#92993 29-Oct-2007 22:29

x1Ler: Annoyed that I finally found someone that fixed this problem, but you didn't list exactly how you did it so what the heck is the point in posting if you don't say what you did EXACTLY? eh?

Yes well that is a fair comment ... however, I have explained what I did, that I believe caused the issue, and some of the fault finding that I carried out, finally arriving at the sysconfig in yast, which I made sure had all the setting correct to make KDM the graphics manager. I am sorry I cannot be specific as to A. What the problem was, or B. Not knowing exactly what the problem was, not really knowing for sure what the solution was. Kinda like coding for Microsoft eh. I would like to comment that the system slowed down somewhat, recently and I rebooted it, which seemed to bring it right. Possibly some chron was at work on some humongous mission, there are a couple on that system to carry out.