start KDE from command line (Debian Lenny on iMac)
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.
start KDE from command line (Debian Lenny on iMac)
Hello,
my first posting here! I have a nearly 10 years old iMac at home and installed Lenny on (somehow, I had to thrash Mac OS 9.2 :-P). Everything was successful until now, but on entering "startkde", the screen fills with
kpersonalizer: cannot connect to X server
lines. Upon looking at other threads here I tried mdetect, installing X11... but to no avail.
X.Org X Server 1.4.2
[...]
Invalid IO Allocation b: ... e: ... correcting
end of block range ... < begin ...
Unable to find a valid framebuffer device
R128: Failed to open framebuffer device, consult warnings and/or errors...
Screen(s) found, but none have a usable configuration.
Fatal server error:
no screens found
waiting for X server to begin accepting connections
giving up.
xinit: Connection reset by peer (errno 104): unable to connect to X server
xinit: No such process (errno 3): Server error.
"..." were hexadecimal numbers (pointers, I believe you call them).
What is your graphic card?
In any case, you can use the subobtimal vesa driver (that won't use the advanced features of your graphic card if any)
Edit /etc/X11/xorg.conf
In the [Device] section, change the driver to "vesa"
with nano I've changed the line you mentioned to "vesa". Before, it already was "r128".
Either way, with "vesa" or "r128", it still gives the errors I have written above:
Code:
X.Org X Server 1.4.2
[...]
Invalid IO Allocation b: ... e: ... correcting
end of block range ... < begin ...
Unable to find a valid framebuffer device
R128: Failed to open framebuffer device, consult warnings and/or errors...
Screen(s) found, but none have a usable configuration.
Fatal server error:
no screens found
waiting for X server to begin accepting connections
giving up.
xinit: Connection reset by peer (errno 104): unable to connect to X server
xinit: No such process (errno 3): Server error.
Are you sure you changed the file and saved the changes? I still see the r128 driver complaining in that output, not the vesa one.
However, your best option is to upload these two files to a service like pastebin.ca:
Code:
/etc/X11/xorg.conf
/var/log/Xorg.0.log
So we can review them and see what's happening.
About kde, you need to put this line into a file called ~/.xinitrc:
Code:
startkde
Otherwise, the "startx" command will start the default session (usually twm and a few xterm's), or whatever you have configured in your distro by default, which will surely not be kde. But, if X is failing to start, that's the first thing to worry about. Kde will not work without X, of course.
By the way, you forced me to look up how to mount an USB stick and copy these files. Until now, I have 30 minutes of Linux experience... learning by doing.
About kde, you need to put this line into a file called ~/.xinitrc:
Code:
startkde
Otherwise, the "startx" command will start the default session (usually twm and a few xterm's), or whatever you have configured in your distro by default, which will surely not be kde. But, if X is failing to start, that's the first thing to worry about. Kde will not work without X, of course.
In your home directory. What I wrote above is a shortcut for that. '~' means the home dir, just like $HOME. So, '~/.xinitrc' is a file called '.xinitrc' which is located in your home directory.
I will review the logs above as soon as I can. I have no idea if that will be today, real life always gets in the middle :P , but other members around might be able to help as well.
On a quick look, I can see that your video card section has no "Driver" line on it. So, your Xorg is using using autodetection, and picking what it thinks is the best available driver, which in your case is the r128 one. That driver is throwing a few warnings (WW) and some error messages (EE) in the Xorg.0.log file. My inexperience with this concrete driver prevents me from being able to give further insight on what the problem is until I can research a bit more.
In any case, if you want to try the vesa driver, you can try to modify your video driver section, just add one line, so it looks like this:
Using config file: "/etc/X11/xorg.conf"
(EE) Failed to load module "vesa" (module does not exist, 0)
(EE) No drivers available.
Fatal server error:
no screens found
I hope I can get this old machine running.. some time...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
