Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
I'm still pretty new to linux, but so far I'm starting to see a weird trend. On windows systems, I dread running them for too long because I know they'll crash. On my linux box at home, I actually dread rebooting my system, because something inevitably goes wrong. If I leave it on, no worries, but if I have to reboot to re-initialize something, god have mercy . . .
this morning's reboot problem is a lovely x error:
Fatal error:
no screens found
last reboot X worked fine. I changed my inittab to set the base init level to 4 so my box would boot straight into an x client instead of a terminal window (I'm running slackware 9.0, if that helps anyone). I didn't mess w/ any other settings that I'm aware of that would mess up X. I've even tried setting my init level back to 3 (boot to terminal) and starting x from there, but I get the same error.
Any ideas? In the meantime I guess I get to hone my terminal skills, which isn't all that bad a thing, but I miss my desktop. Any help would be greatly appreciated.
I went w/ the automatic setup when I installed slack 9.0. I'm running an old ATI xpert 2000 pro card, which uses the Rage 128 Pro chip. thanks for the help!
I am new to slack also, I had that same problem when I booting this morning. I used KDE to change a resolution, but it also changed mouse settings in m XF86 config file. Strange. I had to fix my config file.
I ran xfree86setup and X restarted, but now my resolution is like 1800 x 1400 or something crazy like that. I tried going into the config file from there to reset it down to something less tiny, but can't figure out which directive sets the resolution.
shanenin, thanx for letting me know the config stuff is available from within KDE-- I found it fine, and tried setting the resolution down a bit from there, but still nothing has changed. When I restart X, it goes back to the increadibly miniscule 1800 x 1400 resolution. Did this happen to you too, and how did you get your resolution set back to your liking?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.