[SOLVED] Scientific Linux 6 hangs on startup... suddenly.
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.
I don't even know where to begin with fixing this issue. I use Scientific Linux 6.1 on an HP desktop with dual displays controlled by an nVidia GeForce 9400 GT, and I have GRUB set up to allow me dual boot in to Sci Linux and into Windows Vista.
I didn't install anything, didn't update any drivers, didn't do anything today except print some PDFs and check my webmail. I shut the system down and came back to it later in the day. Twice it stalled after lighting up both monitors with the logo and the rotating circle. The third time, I hit escape to watch the daemons start. It got as far as WINE, then ground to a halt. If I do it this way, I can Alt-F2 and get to the console, but I'm at a loss for what to do once I get there. I uninstalled WINE -- I don't really use it anyway -- but it hung at the same spot, which is now after the at daemon.
Sci linux doesn't use xorg.conf anymore; that's ordinarily the first place I would check. This seems very much like something that would happen after a video driver updated, but I haven't touched my nvidia drivers, the kernel, or anything. And, the kicker is, Vista still works fine, including with both monitors.
So, my question is, where do I begin? And, what information can I give you to help me?
When you create it it gets listed under / as xorg.conf.new then you have to move it to /etc/X11/xorg.conf
Also the official nvidia driver should be available thru your package manager. I also have the 9400GT & it works well. If you install nvidia you can also install nvidia-settings which is a gui tool which can configure both monitors.
I don't even know where to begin with fixing this issue. I use Scientific Linux 6.1 on an HP desktop with dual displays controlled by an nVidia GeForce 9400 GT, and I have GRUB set up to allow me dual boot in to Sci Linux and into Windows Vista.
I didn't install anything, didn't update any drivers, didn't do anything today except print some PDFs and check my webmail. I shut the system down and came back to it later in the day. Twice it stalled after lighting up both monitors with the logo and the rotating circle. The third time, I hit escape to watch the daemons start. It got as far as WINE, then ground to a halt. If I do it this way, I can Alt-F2 and get to the console, but I'm at a loss for what to do once I get there. I uninstalled WINE -- I don't really use it anyway -- but it hung at the same spot, which is now after the at daemon.
Sci linux doesn't use xorg.conf anymore; that's ordinarily the first place I would check. This seems very much like something that would happen after a video driver updated, but I haven't touched my nvidia drivers, the kernel, or anything. And, the kicker is, Vista still works fine, including with both monitors.
So, my question is, where do I begin? And, what information can I give you to help me?
Thank you very much!
I've hit a similar problem on two machines. One is a VM (Virtualbox) running under Win7, Scientific Linux 6.1, and the other is SL 6.1 as the host system. Both were working fine for many months until a recent yum update. Now the GUI won't start. I get Xorg errors about version mismatch for the various video drivers on both the VM and the SL 6.1 full installation. The stand alone full installation is installed on a machine with an on-board Intel card, but the xorg-drv-intel won't load. The VM is using whatever the standard virtual video that VirtualBox runs.
I tried booting into older kernels, with no luck. I can get into runlevel 3, and networking, etc works fine. But no X :-(. Also Xorg -configure throws the same errors about "failed to load..." for each video driver.
Anyone know if there's an update in the pipeline that will fix this??
Thanks,
Micha
Last edited by micha_silver; 07-12-2012 at 07:06 AM.
I've hit a similar problem on two machines. One is a VM (Virtualbox) running under Win7, Scientific Linux 6.1, and the other is SL 6.1 as the host system. Both were working fine for many months until a recent yum update. Now the GUI won't start. I get Xorg errors about version mismatch for the various video drivers on both the VM and the SL 6.1 full installation. The stand alone full installation is installed on a machine with an on-board Intel card, but the xorg-drv-intel won't load. The VM is using whatever the standard virtual video that VirtualBox runs.
I tried booting into older kernels, with no luck. I can get into runlevel 3, and networking, etc works fine. But no X :-(. Also Xorg -configure throws the same errors about "failed to load..." for each video driver.
Anyone know if there's an update in the pipeline that will fix this??
Thanks,
Micha
There was an automatic yum update that ran yesterday on my machine, coinciding with my machine breaking. I undid the update in yum, and now it doesn't hang, but it still stops before X can begin. Runlevel 3 is fine for me too. Maybe you can try a yum downgrade on xorg?
There was an automatic yum update that ran yesterday on my machine, coinciding with my machine breaking. I undid the update in yum, and now it doesn't hang, but it still stops before X can begin. Runlevel 3 is fine for me too. Maybe you can try a yum downgrade on xorg?
I've jumped past the problem (on two machines) by upgrading to Scientific Linux 6.2. I got into the grub menu (press any key at the boot screen) and enter 'e' to edit the boot line. Add "single" at the end to enter single user mode. THen at the command prompt I first ran
Code:
telinit 3
(to get into runlevel 3 with networking). Next
Code:
yum --releasever=6.2 update
There are 100's of MB of new, replacement packages. When it finished I rebooted, and the X system came up.
It's unfortunate that a broken update snuck into the repo, but I guess it happens on rare occasions. I'm sure that the packages for 6.1 will be fixed and pushed out soon, but 6.2 has been out for several months, so no reason not to go ahead and upgrade.
Last edited by micha_silver; 07-12-2012 at 10:59 AM.
I've jumped past the problem (on two machines) by upgrading to Scientific Linux 6.2. I got into the grub menu (press any key at the boot screen) and enter 'e' to edit the boot line. Add "single" at the end to enter single user mode. THen at the command prompt I first ran
Code:
telinit 3
(to get into runlevel 3 with networking). Next
Code:
yum --releasever=6.2 update
There are 100's of MB of new, replacement packages. When it finished I rebooted, and the X system came up.
It's unfortunate that a broken update snuck into the repo, but I guess it happens on rare occasions. I'm sure that the packages for 6.1 will be fixed and pushed out soon, but 6.2 has been out for several months, so no reason not to go ahead and upgrade.
I'm in the midst of trying the same thing (well, a slightly different way, but with the same end result). I'll keep you posted.
downgrading Xorg - a very bad idea and NOT easy
and in this case not needed
that auto update probably installed a new kernel
NOW if you installed the nvidia driver FROM "yum" using the kmod-nvidia
the nvidia driver WILL AUTO UPDATE with a new kernel
HOWEVER
if you used the nvidia.run driver THEN For EVERY kernel and X11 update you will have to MANUALLY reinstall the nvidia.run driver -- EVERY TIME
I've jumped past the problem (on two machines) by upgrading to Scientific Linux 6.2.
I eventually gave in and did the same. Problem solved, though not exactly in the way I wanted to solve it.
Quote:
It's unfortunate that a broken update snuck into the repo, but I guess it happens on rare occasions. I'm sure that the packages for 6.1 will be fixed and pushed out soon, but 6.2 has been out for several months, so no reason not to go ahead and upgrade.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.