X0-lock in SM6.0 live, no X
Hi All, I am new to the forum but not a complete newbie to linux, but certainly do not consider myself an expert. I think after trying many different distro's Mepis is the one for me. I am using 3.3.1 (and Lite), 3.4-3 and 6.0 on different machines. I have been working with Linux for about 2,5 years intensively and enjoying it, before that I have given Linux a try sometimes but each time it went straight over my head. I am doing pretty much everything that I want to do with a pc now in Mepis Linux. I am still very dependent on what X has to offer. So when X decides not to start I have a problem. Now to give some background info on the problem I have, on 2 different machines I have alomost similar problems, on a third one these problems were not present at all. When booting the live cd on one machine I get presented with a console login and a message stating to press ctrl + alt + f7 or f8 to get a graphical login; after pressing the f8 option I can log in and all is fine. On the other machine I get the same console login but no graphical login is to be found. When I enter 'startx' i get a return message stating that x is already in use and I should remove the file /tmp/.X0-lock and try again. after doing this, nothing changes. This system runs fine under 3.4-3 both live and hd install. Does anyone know about this problem and may be what to do about it? any reply is much appreciated, thanks. Ronald.
Did You Verify Your CDs?
wabbalee, it sounds to me like your CD may not have been complete. Especially since you seem to be having the same results on multiple computers. Where did you get the CD image from? Did you perform a check of the md5sum to ensure that you got the whole thing?
If you are using Mepis, the normal "console" (not konsole) that X starts in is found by pressing ctrl+alt+f7. If you pressed ctrl+alt+f8 you were probably trying to start a second X session. This is possible to do, but I don't recommend it until you know how to navigate through multiple users and sessions.
The /tmp/.X0-lock file will exist when X is started. If you know absolutely that X is not running you can delete it (as user root) and try to start X again. But all of this should be unnecessary.
Please verify that your disks are good and try a re-install on one of your boxes to see if that solves the problem
Jon
Jon, Thanks, for you
Jon,
Thanks, for you reply,
I have checked the md5sum (was ok), burned a new copy, rebooted twice on cd. As I go through the several terminals I find the following on tty5:
sep 17 22:51:32 localhost kdm_config[3736]: unrecognized key 'colorScheme' in section [X-*-Greeter] at /etc/kde3/kdm/kdmrc:29
and on tty1 where I gave the 'startx' command again it showed:
fatal server error:
server is already active for display 0
if this server is no longer running, remove /tmp/.X0-lock
and start again
I removed the .X0-lock file and gave another 'startx'. then a whole story follows on tty1 and no graphical login appears.
the message is a long one this time but the bottom line is I get no X.
xauth: creating new authority file /root/.serverauth.3842
x window system 7.0.0
release date: 21 december 2005
x protocol version 11, revision 0, release 7.0
build operating system: linux 2.6.15.7 i686
current operating system: linux mepis1 2.6.15-26-386 #1 preempt wed jul 19 12:14:26 EDT 2006 i686
build date: 16 march 2006
before reporting problems, check http://wiki.x.org
to make sure you have the latest version
module loader present
markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line,(!!)notice,(II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??)unknown,
(==)log file: "/var/log/Xorg.0.log", time: sun sep 17 23:00:49 2006
(==) using config file: "/etc/X11/xorg.conf"
dlopen: "/usr/lib/xorg/modules/extensions/libGLcore.so: undefined symbol:__glXLastContext
(EE) failed to load /usr/lib/xorg/modules/extensions/libGLcore.so
(EE) failed to load module 'GLcore" (loader failed, 7)
as you can see a long story, again, no problem when I boot with SM3.4-3 final CD in drive. I am pretty sure that there is no problem with the disc it self as I have succesfully installed SM6.0 on a brand spanking new AMD 3500+ on an ASUS A8N sli motherboard with ATI PCIe 256mb graphics including ATI drivers and an ACER 19" wide lcd (resolution 1440 x 900) and a SATA2 hd from a friend of mine with that particular disc.
Regards, Ron.