LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   Doesnt Make it to the login screen. (http://www.linuxquestions.org/questions/slackware-14/doesnt-make-it-to-the-login-screen-4175440621/)

ThatSlacker 12-08-2012 07:33 PM

Doesnt Make it to the login screen.
 
Hi ive been using slackware for many years and have never encountered a problem such as this. I have my machine set to run level 3 as per installation default, and it randomly will stop loading during initialization at different points each time. I played around a bit with video settings even though I figured run level 3 it wouldnt matter much but apparently I can see it finish loading to the login screen on broken resolutions that are fragmented. So this lead me to believe it was a noveau problem which I went from my slackware disk and used pkgtool to enabled the blacklisted noveau package from extra and removed the other xf86 novaeu package. This still didnt solve the problem, I was curious if anyone had any ideas my machine hardware is:

amd phenom 10xx 6 core 2.8ghz
Gigabyte GTS450 GFX card

The things I have at my disposal are just the slackware installation disk and this machine. Any ideas or direction would be greatly appreciated. I am still assuming this is a video problem of some sort but not completely sure as per I can only tell that it gets to the login screen when I use an unsupported resolution that fragments my vision, if I use a supported resolution the text just stops moving at a certain point but it gets to the login screen I just dont see the text being drawn anymore at that point.

STDOUBT 12-09-2012 12:12 AM

Have you tried using the nvidia closed source driver? I have to assume you have since nouveau is really only a problem if you're trying to run the closed nvidia driver.

If you don't want to use the closed driver, my recommendation is to uninstall the nouveau blacklist thingey and replace the xf86 nouveau driver (you didn't need to remove it to blacklist it) so that X is back to its defaults.
Then, what I would try is running /usr/share/mkinitrd/mkinitrd_command_generator.sh (run its output to create the initrd.gz) and modify lilo to use the new initrd.gz (remember to run lilo after).

If you already are running the closed driver, the mkinitrd thing can help there too. I have found that even before you "startx", the resolution of whatever video driver you're using comes into play.

astrogeek 12-09-2012 12:32 AM

As you are unsure whether it is a video driver problem or not, the following thread might be useful:

RC5 - Long delay during boot

I first thought this was a video problem but turned out to be a wireless device initialization problem.

I have since seen other threads with similar problems - might be worth exploring as well.

nivieru 12-09-2012 01:40 AM

I used to have a problem which sounds like what you're describing, something to do with some gigabyte mobos. it was solved by adding the line
Quote:

append="acpi_skip_timer_override"
to lilo.conf, perhaps you should try that.
to check it before changing lilo.conf, you could supply this option at boot time using <tab> in the lilo prompt.

ThatSlacker 12-14-2012 08:58 PM

Quote:

Originally Posted by astrogeek (Post 4845518)
As you are unsure whether it is a video driver problem or not, the following thread might be useful:

RC5 - Long delay during boot

I first thought this was a video problem but turned out to be a wireless device initialization problem.

I have since seen other threads with similar problems - might be worth exploring as well.


Nah there is no actual delay, I thought it was a delay also till I changed to a video mode I didnt support and I could see text still going on the terminal after it hits the fractured area of the startup which is what I assume video driver related.


Quote:

Originally Posted by nivieru (Post 4845531)
I used to have a problem which sounds like what you're describing, something to do with some gigabyte mobos. it was solved by adding the line

to lilo.conf, perhaps you should try that.
to check it before changing lilo.conf, you could supply this option at boot time using <tab> in the lilo prompt.

it isnt a gigabyte motherboard but I tried this solution just incase and it didnt fix the problem.

Quote:

Originally Posted by STDOUBT (Post 4845514)
Have you tried using the nvidia closed source driver? I have to assume you have since nouveau is really only a problem if you're trying to run the closed nvidia driver.

If you don't want to use the closed driver, my recommendation is to uninstall the nouveau blacklist thingey and replace the xf86 nouveau driver (you didn't need to remove it to blacklist it) so that X is back to its defaults.
Then, what I would try is running /usr/share/mkinitrd/mkinitrd_command_generator.sh (run its output to create the initrd.gz) and modify lilo to use the new initrd.gz (remember to run lilo after).

If you already are running the closed driver, the mkinitrd thing can help there too. I have found that even before you "startx", the resolution of whatever video driver you're using comes into play.


well since I cant actually get into my nix system and all I have is a slackware disk and my slackware installed which cant boot in, this has become difficult. I have the driver
accessible from the slackware disk via wget but I has to many errors when I run the NVIDIA.run file related to missing utilities etc. Normally my solution
would be to just get slackware 13.37 like I used to have but that isnt an option atm. Is there another way to tackle installing these nvidia drivers from my slackware installer? Everything needs to be done
from the terminal on my slackware setup disk.


All times are GMT -5. The time now is 09:18 AM.