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.

Introduction to Linux - A Hands on Guide

This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.

I looks like nouveau caused a kernel oops. This just happened on one of my boxes that I cobbled together and added the new (cheap) nVidia 610 card to.

I was able to load slackware current 32bit (RC3) just fine, but the box would not boot. I got a kernel oops after the nouveau kernel driver attepted to load. I solved the problem by passing the nomodeset flag at the lilo prompt. At the lilo boot screen hit TAB and enter

Code:

Linux 3 nomodeset

Tried this. Didn't get an explicit error message this time, but was instead left on a screen of white text that ends in this:

it really ssems like the drm/noeveua is bugged with your hardware - the previous reports saying that you should disable modesettings might not be enough. however the installation of slackware works - which really means this as it worked to install.

Put the slackware cd in the driver, startup the installer. instead of starting the setup program for slackware do this:

it really ssems like the drm/noeveua is bugged with your hardware - the previous reports saying that you should disable modesettings might not be enough. however the installation of slackware works - which really means this as it worked to install.

Put the slackware cd in the driver, startup the installer. instead of starting the setup program for slackware do this:

To see if it is the nouveaou driver you can just unistall it. Basically do what you've done by booting with the install disk, mount your drive like you had, then chroot into the installed system. Remove the package.

Code:

chroot /hello
removepkg /var/log/packages/xf86-video-nouveau#hit tab to complete the driver name which I don't have access to your version number#
exit

Reboot the computer. You'll see that I don't know the actual installed version of the driver you have installed, but by hitting the tab key after you have the first part typed out it will complete the rest of the package name. I do not remember enough about the kernel mode setting issue to know if you will still need to pass those options at boot or if it is only in cases where the nouveau driver is installed, so you might try to just boot it up and if it fails then pass the options that people have already given you on the next reboot.

That should make sure no stupid things are loaded at boot!
cd /hello
chroot .
removepkg /var/log/packages/xf86-video-nouveau-*

[obviously deletes the stupid xorg driver]

Note! X might not start at all, but it should do with the preconfigured vesa driver. It did for me when i did'nt load any modules in 13.37. Hope this really works!
IF IT DID NOT WORK TRY TO EDIT /hello/etc/modprobe.d/blacklist.conf
and remove the line with blacklist video if it did'nt work.

Regards

Last edited by slacktroll; 09-06-2012 at 10:55 PM.
Reason: Looked through slack 13.37 deeply and found what nouvea depend on.added _NOT_