Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi,
I installed some updates and rebooted, and now I am stuck in a command screen. I tried to use startkde and kde and a few other cpmmands, and it just tells me stuff like "xset: unable to open display" "Aborting. $Display is not set" "No Such File or Directory" "Can't contact Kdeinit!" "Can't connect to server" "Running shutdown scripts"
Any idea on what is wrong?
I am using Suse 10.0, the install was downloaded from the novell site and burned on 5 cds.
What did you update? It sounds like your just booting into runlevel 3 instead of 4 or 5. And some of the error messages sound like you've su'ed to root before trying to start kde. That won't work without some extra parameters.
Try this: As your user, not root and not su'ed, issue the command startx. If that doesn't work use Midnight Commander (type mc on the commandline) and view your /home/<current username>/.xinitrc file. It should have just one line that reads
startkde
Other stuff can be in there but this is the only line required to start a kde session.
Hmmm...based on the new information you've given and the previous error messages I have two ideas (unless someone else can offer more):
1. Try creating the $DISPLAY environment variable before starting X
set DISPLAY=0:0
2. It might be an X configuration problem such as an incorrect video driver. Check the graphics device section of /etc/X11R6/Xorg.conf. Yours might be different because of the distro but it should be close.
Here is exactly what I happens when I type startkde
Ian@linux:/startkde
xset: unable to open display
xset: unable to open display
xsetroot: unable to open display
Startkde: Starting up...
Kdeinit: Aborting. Display is not set
Warning: Connect () Failed: No such file or directory
Ksmserver: Cannot connect to X server
Error: Couldn't attach to DCOP server!
Startkde: Shutting down...
Warning: Connect () Failed: No such file or directory
Error: Can't connect kdeinit!
Unix_connect: Can't connect to server (Linux:/tmp/ksocket-Ian/linux.site-lbcd-43797866)
Startkde: Running shutdown scripts
Startkde: Done
The Failsafe got me to runlevel 3. I am in Sax2, now what?
Update: I got out of sax2, and tried Startx. It worked!!!
Thank you all for your help
Before I reboot in regularly, do I need to change anything?
Update 2: It locked up (as it sometimes does, for reasons I don't know), but it booted up fine.
Any idea on how to stop it from randomly locking up? Would upgrading to kde 3.5 (from 3.4) or upgrading the kernel from default (2.6.13) to 2.6.15 help?
You first need to find out why it's locking up.... lockups are -usually- hardware related but not always..
Forgot about needing to be at init3, sorry bout that. For future reference, you can type init3 in the boot options line (after pressing F2 at the initial SuSE boot prompt) to boot into init3, ot you can, as root, type init3 at a shell to get you there if already in X)
Anyway, start looking at your log files... as always, with Linux there's more than one way to accomplish thing... In Yast you can use the system log viewer... launch Yast, choose Miscellanous, then choose View System Log. You can choose the different logs at the top.
Start viewing those to see if there are any glaring problems then post the error message(s) that seem relevent.
Also take a look at you're .xsession-errors file in your home dir... notice the '.' at teh beginning of the file....
I am not sure what a problem would look like in the logs. Do you know of a site that has a list of things to look for?
Edit: Here is what I found so far (in the messages section of the system log).
Dec 25 15:49:38 linux kernel: uhci_hcd 0000:00:08.0: host system error, PCI problems?
Dec 25 15:49:38 linux kernel: uhci_hcd 0000:00:08.0: host controller process error, something bad happened!
------------------
Dec 25 15:49:43 linux kernel: powernow: This module only works with AMD K7 CPUs
Dec 25 15:49:43 linux rcpowersaved: CPU frequency scaling is not supported by your processor.
Dec 25 15:49:43 linux rcpowersaved: enter 'CPUFREQD_MODULE=off' in /etc/sysconfig/powersave/cpufreq to avoid this warning.
Dec 25 15:49:43 linux rcpowersaved: Cannot load cpufreq governors - No cpufreq driver available
Dec 25 15:49:43 linux [powersave]: ERROR (CPUFreq_Kernel:21) Can not set ondemand governor, maybe your cpufreq driver is too slow.
Dec 25 15:49:43 linux [powersave]: ERROR (CPUFreq_Kernel:23) Try CPUFREQ_CONTROL=userspace in /etc/sysconfig/powersave/cpufreq.
Dec 25 15:49:43 linux [powersave]: ERROR (PM_Interface:231) Cannot create cpufreq objects
Dec 25 15:49:43 linux SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled.
---------------------------
Dec 25 15:49:52 linux modprobe: FATAL: Error inserting sonypi (/lib/modules/2.6.13-15-default/kernel/drivers/char/sonypi.ko): No such device
-------------------------------
Dec 26 00:08:53 linux kernel: ehci_hcd 0000:00:08.2: startup error -19
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.