Changed monitors and now startx doesn't start. What to do?
SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Changed monitors and now startx doesn't start. What to do?
Seems my sweet LCD monitor died on me, so I'm using a backup, clunk CRT monitor. However, after Slackware 10.2 boots up and I log in, startx doesn't start. Or at least it tries to, but the "core devices" don't load properly and it dies. I'm sure it's the monitor. How can I setup the new monitor from the command line?
Log-on as root at run level three and run xorgconfig. Over-write your old xorgconfig file. Your settings for the LCD monitor will perhaps be different than the CRT.
Check the specs for your CRT monitor and set accordingly. You should be fine.
Over-write your old xorgconfig file. Your settings for the LCD monitor will perhaps be different than the CRT.
Please consider not overwriting you old config file! Save a backup copy of the file. When/if you replace the clunky CRT monitor with a newer LCD, you'll have a config file to work from to configure your newer monitor. If you obtain the same model LCD monitor then all you need do is copy the backup config file.
FWIW, many people struggle with the command line xorg config tools. So please consider saving a backup of your config file before tinkering.
Lastly, you can edit the config file with multiple device settings. After you get things working with the temporary CRT monitor, add that monitor configuration to you original config file "Monitor" section. Name that new section something that makes sense, like Identifier "Viewsonic 7 CRT". This way, in the future, should you have problems with your monitor you can then quickly edit the config file to use the CRT monitor or the LCD monitor.
Please consider not overwriting you old config file! Save a backup copy of the file. When/if you replace the clunky CRT monitor with a newer LCD, you'll have a config file to work from to configure your newer monitor. If you obtain the same model LCD monitor then all you need do is copy the backup config file.
FWIW, many people struggle with the command line xorg config tools. So please consider saving a backup of your config file before tinkering.
Lastly, you can edit the config file with multiple device settings. After you get things working with the temporary CRT monitor, add that monitor configuration to you original config file "Monitor" section. Name that new section something that makes sense, like Identifier "Viewsonic 7 CRT". This way, in the future, should you have problems with your monitor you can then quickly edit the config file to use the CRT monitor or the LCD monitor.
Yep, that'll work just fine. Great suggestions:-)
I personally don't have a lot of difficulty setting up xorgconfig.
Please consider not overwriting you old config file! Save a backup copy of the file. When/if you replace the clunky CRT monitor with a newer LCD, you'll have a config file to work from to configure your newer monitor. If you obtain the same model LCD monitor then all you need do is copy the backup config file.
That's a great point, but I personally wouldn't back up the xorg.conf file. Rather, I would just write down the relevant vertical and horizontal refresh rates for the monitor. The other values are imho pretty obvious.
xorgsetup works with most versions of Xorg included since at least Slackware 10.0, not just -current. Backup your xorg.conf, and run xorgsetup like this (Do as root, or su):
xorgsetup works with most versions of Xorg included since at least Slackware 10.0, not just -current. Backup your xorg.conf, and run xorgsetup like this (Do as root, or su):
I think I found out what the problem was. I had just man rc.hotplug non-executable and had rebooted to see fast the computer would boot up now. I had been putting up with long boot time for months because I didn't know how to turn it off. Anyhow, when I reboot, the LCD died.
It was saying mouse not found errors, no /dev/mouse device or something to that effect, whenever I tried running startx. I made rc.hotplug executable again and now X boots up. Go figure. Now I need to figure out a way to make that mouse configuration permanent, because hotplug start takes ages.
Thanks for the tips and the newly acquired knowledge however.
Slackware doesn't have a preference. There are at least five available options:
X -configure
xorgsetup
xorgcfg
xorgconfig
Manually edit xorg.conf
Try them all. See which you like. Make sure to read the logfile. It can get frustrating if xorg.conf gets saved to an alternate location. You will edit /etc/X11/xorg.conf and nothing will change.
Quote:
Originally Posted by dugan
I personally wouldn't back up the xorg.conf file. Rather, I would just write down the relevant vertical and horizontal refresh rates for the monitor. The other values are imho pretty obvious.
Everything is obvious, unless it's not. Backing up the whole file A) Reminds you what those "obvious" config options were when you forget, and B) Puts everything somewhere where you won't lose it (as opposed to writing it down).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.