PDA

View Full Version : HOWTO: Latest NVIDIA drivers on Ubuntu Breezy


Pages : 1 2 3 4 [5] 6 7

kenito443
February 15th, 2006, 03:22 AM
never mind just figured it out-sorry

does anyone know how to get xorg.conf to recognize dual monitors,..thx in advance

kenito443
February 15th, 2006, 04:06 AM
ahh man i feel dumb--i used the twin view option and it worked fine..but i big thanks to tselliot alot of help from your guide thanks!

tseliot
February 15th, 2006, 05:16 AM
I can access the configuration menu I made, but there are only 4 checkboxes, I don't see any refresh rate or resolution settings like in the Nvidia manager for windows.
It's ok, this is not Winxp ;)

^^^ I HAVE NO IDEA WHAT THAT MEANS!! ^^^
It looks like a segmentation fault. You might have problems with OpenGL.
Can you try to open XMMS and play a song (make sure the codecs are installed)?

weird that 'smeg' doesn't work. is that command a joke or am i being noobtastic?

and YES I did RESTART :) please help me !! :D
You're absolutely right. I guess the author of that guide is a bit Gnome-centric:p (just kidding, I really appreciate your work ArtificialIntelligence :) )

The truth is that "smeg" (which is ONLY a menu editor) won't work for you since it comes with Ubuntu (=GNOME desktop) while Kubuntu (=KDE) has it's own menu editor (as I

tseliot
February 15th, 2006, 05:19 AM
Wow. So I tried Method 2 at the beginning of this thread and got to step 6 (reboot) after I recompiled the kernel. When I try to load the new kernel, the system hangs on

*Checking battery state... [ok]

and just stays there. :confused:

I have had the worst luck lol!

Do I have to be using 2.6.12-10-386 kernel for the latest nvidia drivers?

Thanks guys!
Did you recompile the kernel? Are you sure? And how did you do that?
In method 2 I suggest to install a new kernel.

A quick fix:
Turn on your computer and keep pressing ESC until you get to the GRUB menu.
Select your previous kernel and press ENTER.

acorrigan
February 16th, 2006, 01:36 AM
I followed the instructions exactly, but I got an error message that the nvidia module is already loaded. To get back into KDE I rebooted, but now my computer stopped booting :(

tseliot
February 16th, 2006, 08:53 AM
I followed the instructions exactly, but I got an error message that the nvidia module is already loaded. To get back into KDE I rebooted, but now my computer stopped booting :(
I need you to reproduce the error.

Set the nvidia driver in your /etc/X11/xorg.conf (or if it's already set leave it as it is.
When GDM (or kdm) crashes at startup Press CTRL+ALT+F1
Then type

Then:
sudo /etc/init.d/gdm stop (if you use GDM)
OR
sudo /etc/init.d/kdm stop (if you use KDM)

startx -- -verbose 5 -logverbose 5

You will get the same error.

sudo cp /var/log/Xorg.0.log /home/your_username/Xorg.0.log
(Of course you have to replace "your_username" with your username)

and post the content of that file (which you can find under /home/your_username/Xorg.0.log )


BTW if you want to access the GNOME or KDE again you can use this quick fix:
sudo nano /etc/X11/xorg.conf
Set the driver back to "nv" instead of "nvidia"
CTRL+O to save
CTRL+X to exit

sudo /etc/init.d/gdm stop (if you use GDM)
OR
sudo /etc/init.d/kdm stop (if you use KDM)

Then
sudo /etc/init.d/gdm start (if you use GDM)
OR
sudo /etc/init.d/kdm start (if you use KDM)

acorrigan
February 16th, 2006, 10:11 AM
thank you for the help tseliot.

Unfortunately, the booting freezes before it even gets to kdm. I'll see if I can switch to a console from where it freezes. I'll have to try tonight as I just got to school for the day.

tendo
February 16th, 2006, 11:57 AM
mine is working now (i think) i can run glxgears and it showed like 20K FPS. how can i see if im using the "bleeding edge" driver or the "legacy" one. i know this is a pretty stupid question, but that's how i roll.

tseliot
February 16th, 2006, 12:10 PM
mine is working now (i think) i can run glxgears and it showed like 20K FPS. how can i see if im using the "bleeding edge" driver or the "legacy" one. i know this is a pretty stupid question, but that's how i roll.
Post the output of this command:
glxinfo | grep OpenGL

tseliot
February 16th, 2006, 12:12 PM
thank you for the help tseliot.

Unfortunately, the booting freezes before it even gets to kdm. I'll see if I can switch to a console from where it freezes. I'll have to try tonight as I just got to school for the day.
You can try this then:
Turn on your computer and keep pressing ESC until you get to the GRUB menu.
Select "Recovery mode" (the xserver won't be started therefore it shouldn't freeze)
Then use the commands I suggested before.

PsTJsT
February 17th, 2006, 10:24 AM
Okay, my experience comes with good news and bad news...

The good news is that I didn't encounter any problems while following Method 2 and I've installed the latest nVidia drivers for my card.

The bad news is that as soon as I completed the process, I lost my wireless device (ath0). It doesn't show up with either "lspci" or "iwconfig -a". Additionally, "ifup ath0" states the device isn't found/valid. The device (a D-Link DWL-G520 w/ an Atheros chipset) has been working fine with the standard madwifi drivers ever since I installed Breezy several weeks ago, and I'm pretty sure it's not a hardware issue because it's identified and works when I boot with a Breezy live cd.

An unrelated thread suggested the fix for a similar problem experienced by someone else was "apt-get install linux-restricted-modules-$(uname -r)" but that doesn't seem to be an option for me since I can't get online (with that computer) and, even if I could, I'm not sure how this would impact my new nVidia drivers.

Any ideas?

P.S. I encountered a prompt not mentioned in the How-To. In "step 10," after the installer asked whether I wanted to compile a module for my kernel, I was prompted to allow the installer to modify my xorg.conf file so that the drivers could be started automatically and, at the same time, to allow the installer to create a backup of my xorg.conf file. This was before "step 11" of Method 2, so answering yes to that prompt would result in the backup suggested in step 11 being nothing more than a backup of the modified xorg.conf file. Correct?

eqisow
February 17th, 2006, 10:45 AM
Forgive me if this has already been asked, but 102 pages of replies is a lot to search through.

After following method 2, is there any way to go back to using the drivers in the repository? I have tried simply going back and following method 1, but it resulted in OpenGL being broken. when I try to run glxgears I get the following error:

Xlib: extension "GLX" missing on display ":0.0".
Error: couldn't get an RGB, Double-buffered visual

My xorg.conf is as follows:

Section "Files"
FontPath "/usr/share/X11/fonts/misc"
FontPath "/usr/share/X11/fonts/cyrillic"
FontPath "/usr/share/X11/fonts/100dpi/:unscaled"
FontPath "/usr/share/X11/fonts/75dpi/:unscaled"
FontPath "/usr/share/X11/fonts/Type1"
FontPath "/usr/share/X11/fonts/CID"
FontPath "/usr/share/X11/fonts/100dpi"
FontPath "/usr/share/X11/fonts/75dpi"
# paths to defoma fonts
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/CID"
EndSection

Section "Module"
Load "bitmap"
Load "dbe"
Load "ddc"
# Load "dri"
# Load "GLcore"
Load "extmod"
Load "freetype"
Load "glx"
Load "int10"
Load "record"
Load "type1"
Load "v4l"
Load "vbe"
EndSection

Section "InputDevice"
Identifier "Generic Keyboard"
Driver "kbd"
Option "CoreKeyboard"
Option "XkbRules" "xorg"
Option "XkbModel" "pc104"
Option "XkbLayout" "us"
EndSection

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ImPS/2"
Option "Emulate3Buttons" "true"
Option "ZAxisMapping" "4 5"
EndSection

Section "Device"
Identifier "NVIDIA Corporation NV40 [GeForce 6800]"
Driver "nvidia"
BusID "PCI:1:0:0"
Option "RenderAccel" "On"
Option "IgnoreDisplayDevices" "DFP,TV"
Option "NoRenderExtension" "On"
Option "Accel" "On"
Option "AllowGLXWithComposite" "Off"
EndSection

Section "Monitor"
Identifier "Generic Monitor"
Option "DPMS"
HorizSync 30-75
VertRefresh 50-85
EndSection

Section "Screen"
Identifier "Default Screen"
Device "NVIDIA Corporation NV40 [GeForce 6800]"
Monitor "Generic Monitor"
DefaultDepth 24
SubSection "Display"
Depth 1
Modes "1600x1200" "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 4
Modes "1600x1200" "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 8
Modes "1600x1200" "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 15
Modes "1600x1200" "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 16
Modes "1600x1200" "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 24
Modes "1600x1200" "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
EndSection

Section "ServerLayout"
Identifier "Default Layout"
Screen "Default Screen"
InputDevice "Generic Keyboard"
InputDevice "Configured Mouse"
EndSection

Section "DRI"
Mode 0666
EndSection


Edit: Also, the nvidia-settings app shows my driver version as 1.0-7667 (the ver. from the repository)

Edit 2: Under system services (I use KDE) there is an entry for nvidia-glx. It is set to start at boot, but it is not running. I cannot start it manually either.

tseliot
February 17th, 2006, 11:04 AM
Okay, my experience comes with good news and bad news...

The good news is that I didn't encounter any problems while following Method 2 and I've installed the latest nVidia drivers for my card.

The bad news is that as soon as I completed the process, I lost my wireless device (ath0). It doesn't show up with either "lspci" or "iwconfig -a". Additionally, "ifup ath0" states the device isn't found/valid. The device (a D-Link DWL-G520 w/ an Atheros chipset) has been working fine with the standard madwifi drivers ever since I installed Breezy several weeks ago, and I'm pretty sure it's not a hardware issue because it's identified and works when I boot with a Breezy live cd.

An unrelated thread suggested the fix for a similar problem experienced by someone else was "apt-get install linux-restricted-modules-$(uname -r)" but that doesn't seem to be an option for me since I can't get online (with that computer) and, even if I could, I'm not sure how this would impact my new nVidia drivers.

Any ideas?
The restricted modules are needed but if you had your connection up and running I could help you to compile ONLY the module for "madwifi driver".

First off let's solve the problem with the connection:
Type this while using your installed Ubuntu:
uname -r
and write the output somewhere as you will need it later (it's the name of your kernel)

Boot off the Ubuntu livecd (or even better the Knoppix livecd which mounts all your partitions) and download the restricted modules for your kernel (they will have a name such as linux-restricted-modules-name_of_your_kernel)
You can get the restricted modules (it's only 1 file) here:
http://mirrors.dotsrc.org/ubuntu/pool/restricted/l/linux-restricted-modules-2.6.12/
Save the file to a USB pen or or mount your harddisk and save it there.

Then boot in Ubuntu (the installed one) copy the files to a folder:
cd that_folder_of_yours
sudo dpkg -i name_of_the_file_you_downloaded.deb

then
sudo nano /etc/X11/xorg.conf
you can edit the file and set the driver back from "nvidia" to "nv" (so as to use the opensource driver (i.e. your previous driver)
CTRL+O to save
CTRL+X to exit

Then restart your computer and your connection should be back.
If everything works fine then I'll give you further instructions

This was before "step 11" of Method 2, so answering yes to that prompt would result in the backup suggested in step 11 being nothing more than a backup of the modified xorg.conf file. Correct?
Yes, that's right

tseliot
February 17th, 2006, 11:07 AM
Forgive me if this has already been asked, but 102 pages of replies is a lot to search through.

After following method 2, is there any way to go back to using the drivers in the repository? I have tried simply going back and following method 1, but it resulted in OpenGL being broken. when I try to run glxgears I get the following error
You have to uninstall the latest driver first:
CTRL+ALT+F1
sudo /etc/init.d/gdm stop (or kdm stop if you use KDM)
cd path_to_the_nvidia_installer
sudo sh Name_of_the_nvidia_installer_you_used --uninstall
sudo /etc/init.d/gdm start (or kdm start if you use KDM)

and Bob's yer uncle;) !

eqisow
February 17th, 2006, 11:33 AM
You have to uninstall the latest driver first:
CTRL+ALT+F1
sudo /etc/init.d/gdm stop (or kdm stop if you use KDM)
cd path_to_the_nvidia_installer
sudo sh Name_of_the_nvidia_installer_you_used --uninstall
sudo /etc/init.d/gdm start (or kdm start if you use KDM)

I didn't keep the .run file, but I went back to Nvidia's site and downloaded it again; no problem there. Everything seemed to uninstall correctly.

Now, however, X will not start at all. nvidia-glx and the restricted modules are both installed through apt-get again, but when I run 'dpkg-reconfigure xserver-xorg' nvidia does not show up as a driver under the driver list. If I set it to nvidia manually in the xorg.conf, X will not load. If I set it to nv it loads, but the desktop looks very glitchy and isn't even really usable.

tseliot
February 17th, 2006, 11:59 AM
I didn't keep the .run file, but I went back to Nvidia's site and downloaded it again; no problem there. Everything seemed to uninstall correctly.

Now, however, X will not start at all. nvidia-glx and the restricted modules are both installed through apt-get again, but when I run 'dpkg-reconfigure xserver-xorg' nvidia does not show up as a driver under the driver list. If I set it to nvidia manually in the xorg.conf, X will not load. If I set it to nv it loads, but the desktop looks very glitchy and isn't even really usable.
Try this:
Boot Ubuntu as usual, open terminal and type (just copy and paste these commands):

sudo apt-get --purge remove linux-restricted-modules-`uname -r` nvidia-glx nvidia-settings nvidia-kernel-common

then
sudo apt-get install linux-restricted-modules-`uname -r` nvidia-glx nvidia-settings nvidia-kernel-common

and set the driver to "nvidia" in your xorg.conf.

Log out and press CTRL+ALT+Backspace to restart the xserver

eqisow
February 17th, 2006, 12:24 PM
I had actually tried that during the interval before you replied. It was complaining about not being able to overwrite some files and refused to purge nvidia-glx. i removed the files manually and was able to continue. I rebooted the system and was greeted with the login screen. Now, however, I am plagued by something quite intriguing. Whenever I attempt to login it goes black as if it's about to boot into KDM... then goes right back to the login screen. This happens no matter who I log in as. Very confusing. :confused:

Edit: If I ctrl+alt+F1 to the command line I am able to log in. If I then issue the stop command for KDM, followed by the start command, it takes me back to the login screen. The only difference is that under switch users it shows me loged on twice. if I switch it just takes me back to the command line. Under session it shows nothing selected, I'm not sure if this is normal or not. If I select a KDE session and then attempt to login the same thing happens, and it reverts back to no selection under session.

tseliot
February 17th, 2006, 01:53 PM
I had actually tried that during the interval before you replied. It was complaining about not being able to overwrite some files and refused to purge nvidia-glx. i removed the files manually and was able to continue. I rebooted the system and was greeted with the login screen. Now, however, I am plagued by something quite intriguing. Whenever I attempt to login it goes black as if it's about to boot into KDM... then goes right back to the login screen. This happens no matter who I log in as. Very confusing. :confused:

Edit: If I ctrl+alt+F1 to the command line I am able to log in. If I then issue the stop command for KDM, followed by the start command, it takes me back to the login screen. The only difference is that under switch users it shows me loged on twice. if I switch it just takes me back to the command line. Under session it shows nothing selected, I'm not sure if this is normal or not. If I select a KDE session and then attempt to login the same thing happens, and it reverts back to no selection under session.
Weird. Ok, not that weird ;) I've managed to mess up my system worse than you've done when I was a newbie.

My suggestion:
Reinstall Ubuntu (ok, I know it's annoying)

Rasymas
February 17th, 2006, 02:04 PM
Hey there Tseliot...

How's your single (double) click Nvidia drivers 8x.xx installer project going? Can you tell me the release date or what's its status..

I'm really looking forward to install that thing..

eqisow
February 17th, 2006, 02:08 PM
Ouch... yea, that's no fun. I'll probably tinker with it some more first, but might end up having to do that I guess.

Thanks for all the help.

PsTJsT
February 17th, 2006, 02:20 PM
If everything works fine then I'll give you further instructions



I appreciate the help. I'll try this tonight when I have access to that computer and follow up afterwards.

Thanx.

eqisow
February 17th, 2006, 02:54 PM
If I boot into command line mode and run startx i get the following:

/etc/X11/xinit/xinitrc: line9: /etc/X11/Xsession: No such file or directory

It would seem that my manual deleting of things in order to get nvidia-glx to purge may have caused a smaaaall problem... any thoughts? Am I pretty much just screwed?

Edit: As these post are getting somewhat off-topic, I have continued with my issue here (http://ubuntuforums.org/showthread.php?p=744719#post744719).

tseliot
February 17th, 2006, 03:45 PM
Hey there Tseliot...

How's your single (double) click Nvidia drivers 8x.xx installer project going? Can you tell me the release date or what's its status..

I'm really looking forward to install that thing..
I'm afraid I can't continue my project unless I find the required documentation. I've tried with Google but I guess I need contact the Debian or Ubuntu mantainers of the nvidia packages. I doubt they will have the time to give me a guide to make packages out of the Nvidia installer though :(

tseliot
February 17th, 2006, 03:54 PM
If I boot into command line mode and run startx i get the following:

/etc/X11/xinit/xinitrc: line9: /etc/X11/Xsession: No such file or directory

It would seem that my manual deleting of things in order to get nvidia-glx to purge may have caused a smaaaall problem... any thoughts? Am I pretty much just screwed?
I couldn't figure out what you meant by "manually removing the packages". There is a reason if a package manager exists.

You could try this thing:
CTRL+ALT+F1
sudo /etc/init.d/gdm stop
sudo apt-get --purge -remove xserver-xorg
sudo apt-get install xserver-xorg

eqisow
February 17th, 2006, 04:00 PM
I meant that apt-get gave me something like, 'cannot overwrite file x with file y' when i tried to purge nvidia-glx so I used rm to get rid of file x myself... and no, it probably wasn't the brightest thing ever. I was actually just about to try purging xserver-xorg, so will let you know how it goes.

Edit: Situation doesn't change at all after purging and reinstalling.

tseliot
February 17th, 2006, 04:41 PM
I meant that apt-get gave me something like, 'cannot overwrite file x with file y' when i tried to purge nvidia-glx so I used rm to get rid of file x myself... and no, it probably wasn't the brightest thing ever. I was actually just about to try purging xserver-xorg, so will let you know how it goes.

Edit: Situation doesn't change at all after purging and reinstalling.
Reinstall Ubuntu and don't remove files manually any more. Next time you have a problem with APT just post it and we'll help you out.

Ben Stamper
February 18th, 2006, 07:15 PM
I have been having issues, as described here: http://ubuntuforums.org/showthread.php?p=748215#post748215 . I tried method 2 as described in the first post, and while trying to compile a module it gives me this error: "Unable to find the kernal source tree". I'm running a 5.10 upgraded from 5.04.

Rasymas
February 19th, 2006, 03:44 AM
Can you post your

sudo gedit /etc/apt/sources.list, Tseliot? :-k

tseliot
February 19th, 2006, 05:29 AM
I have been having issues, as described here: http://ubuntuforums.org/showthread.php?p=748215#post748215 . I tried method 2 as described in the first post, and while trying to compile a module it gives me this error: "Unable to find the kernal source tree". I'm running a 5.10 upgraded from 5.04.
1) I need the model of your graphic card
2) If you get the error that make everything freeze but your mouse pointer there is a fix:
Follow this guide of mine:
http://ubuntuforums.org/showthread.php?t=75281

Get to this part: "b) If you have installed Ubuntu..."

and use "noapic" as boot parameter.

3) as far as the error "Unable to find the kernal source tree" is concerned:
try this:
sudo apt-get install linux-headers-`uname -r`
sudo sh nameofthenvidiainstaller --kernel-source-path=/usr/src/linux-headers-`uname -r`

NOTE: the ` is different from a '

tseliot
February 19th, 2006, 05:30 AM
Can you post your

sudo gedit /etc/apt/sources.list, Tseliot? :-k

#deb cdrom:[Ubuntu 5.10 _Breezy Badger_ - Release i386 (20051012)]/ breezy main restricted


deb http://it.archive.ubuntu.com/ubuntu breezy main restricted
deb-src http://it.archive.ubuntu.com/ubuntu breezy main restricted

## Major bug fix updates produced after the final release of the
## distribution.
deb http://it.archive.ubuntu.com/ubuntu breezy-updates main restricted
deb-src http://it.archive.ubuntu.com/ubuntu breezy-updates main restricted

## Uncomment the following two lines to add software from the 'universe'
## repository.
## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team, and may not be under a free licence. Please satisfy yourself as to
## your rights to use the software. Also, please note that software in
## universe WILL NOT receive any review or updates from the Ubuntu security
## team.
deb http://it.archive.ubuntu.com/ubuntu breezy universe
deb-src http://it.archive.ubuntu.com/ubuntu breezy universe

## Uncomment the following two lines to add software from the 'backports'
## repository.
## N.B. software from this repository may not have been tested as
## extensively as that contained in the main release, although it includes
## newer versions of some applications which may provide useful features.
## Also, please note that software in backports WILL NOT receive any review
## or updates from the Ubuntu security team.
deb http://it.archive.ubuntu.com/ubuntu breezy-backports main restricted universe multiverse
deb-src http://it.archive.ubuntu.com/ubuntu breezy-backports main restricted universe multiverse

deb http://security.ubuntu.com/ubuntu breezy-security main restricted
deb-src http://security.ubuntu.com/ubuntu breezy-security main restricted

deb http://security.ubuntu.com/ubuntu breezy-security universe
deb-src http://security.ubuntu.com/ubuntu breezy-security universe


deb http://archive.ubuntu.com/ubuntu/ breezy universe main restricted multiverse

##deb http://wine.sourceforge.net/apt/ binary/

##deb http://people.ubuntu.com/~doko/OOo2 ./

## deb http://public.planetmirror.com/pub/plf/ubuntu/plf/ breezy free non-free

#deb ftp://ftp.free.fr/pub/Distributions_Linux/plf/ubuntu/plf/ breezy free non-free
#deb-src ftp://ftp.free.fr/pub/Distributions_Linux/plf/ubuntu/plf/ breezy free non-free

deb http://deb.opera.com/opera/ etch non-free
## deb http://seveas.ubuntulinux.nl/ breezy-seveas breezy-backports breezy-custom breezy-extras freenx madwifi
## deb-src http://seveas.ubuntulinux.nl/ breezy-seveas breezy-backports breezy-custom breezy-extras freenx madwifi

deb http://archive.ubuntu.com/ubuntu breezy-backports main restricted universe multiverse
deb http://ubuntu-backports.mirrormax.net/ breezy-extras main restricted universe multiverse

deb http://kubuntu.org/packages/kde351 breezy main
deb ftp://bolugftp.uni-bonn.de/pub/kde/stable/3.5.1/kubuntu breezy main
deb http://www.mirrorservice.org/sites/ftp.kde.org/pub/kde/stable/3.5.1/kubuntu breezy main
deb http://mirror.cc.columbia.edu/pub/software/kde/stable/3.5.1/kubuntu breezy main

Jose Monteiro
February 19th, 2006, 08:06 AM
I've followed your guide using the option 2. No error messages, everything goes fine, but when I try to startx receive just a black screen, can't even type. The only way to restore is using the recovery mode and restoring the xorg.conf or changing "nvidia" to "nv". I using 5.10 and my card is a Gforce FX 5200.

This is the exit of dmesg:

LOWMEM available.
[4294667.296000] found SMP MP-table at 000f4d60
[4294667.296000] On node 0 totalpages: 262128
[4294667.296000] DMA zone: 4096 pages, LIFO batch:1
[4294667.296000] Normal zone: 225280 pages, LIFO batch:31
[4294667.296000] HighMem zone: 32752 pages, LIFO batch:15
[4294667.296000] DMI 2.3 present.
[4294667.296000] ACPI: RSDP (v000 GBT ) @ 0x00 0f6700
[4294667.296000] ACPI: RSDT (v001 GBT AWRDACPI 0x42302e31 AWRD 0x01010101) @ 0x3fff3040
[4294667.296000] ACPI: FADT (v001 GBT AWRDACPI 0x42302e31 AWRD 0x01010101) @ 0x3fff30c0
[4294667.296000] ACPI: MCFG (v001 GBT AWRDACPI 0x42302e31 AWRD 0x01010101) @ 0x3fff6b80
[4294667.296000] ACPI: MADT (v001 GBT AWRDACPI 0x42302e31 AWRD 0x01010101) @ 0x3fff6ac0
[4294667.296000] ACPI: DSDT (v001 GBT AWRDACPI 0x00001000 MSFT 0x0100000c) @ 0x00000000
[4294667.296000] ACPI: PM-Timer IO Port: 0x408
[4294667.296000] ACPI: Local APIC address 0xfee00000
[4294667.296000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
[4294667.296000] Processor #0 15:4 APIC version 20
[4294667.296000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
[4294667.296000] Processor #1 15:4 APIC version 20
[4294667.296000] WARNING: NR_CPUS limit of 1 reached. Processor ignored.
[4294667.296000] ACPI: LAPIC_NMI (acpi_id[0x00] dfl dfl lint[0x1])
[4294667.296000] ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1])
[4294667.296000] ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
[4294667.296000] IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
[4294667.296000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[4294667.296000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[4294667.296000] ACPI: IRQ0 used by override.
[4294667.296000] ACPI: IRQ2 used by override.
[4294667.296000] ACPI: IRQ9 used by override.
[4294667.296000] Enabling APIC mode: Flat. Using 1 I/O APICs
[4294667.296000] Using ACPI (MADT) for SMP configuration information
[4294667.296000] Allocating PCI resources starting at 40000000 (gap: 40000000:90 000000)
[4294667.296000] Built 1 zonelists
[4294667.296000] Kernel command line: root=/dev/sda1 ro single
[4294667.296000] mapped APIC to ffffd000 (fee00000)
[4294667.296000] mapped IOAPIC to ffffc000 (fec00000)
[4294667.296000] Initializing CPU#0
[4294667.296000] PID hash table entries: 4096 (order: 12, 65536 bytes)
[4294667.296000] Detected 2994.151 MHz processor.
[4294667.296000] Using pmtmr for high-res timesource
[4294667.296000] Console: colour VGA+ 80x25
[4294667.649000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes )
[4294667.650000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[4294667.668000] Memory: 1031036k/1048512k available (1415k kernel code, 16524k reserved, 763k data, 224k init, 131008k highmem)
[4294667.669000] Checking if this processor honours the WP bit even in superviso r mode... Ok.
[4294667.669000] Calibrating delay loop... 5914.62 BogoMIPS (lpj=2957312)
[4294667.693000] Security Framework v1.0.0 initialized
[4294667.693000] SELinux: Disabled at boot.
[4294667.693000] Mount-cache hash table entries: 512
[4294667.693000] CPU: After generic identify, caps: bfebfbff 20100000 00000000 0 0000000 0000641d 00000000 00000000
[4294667.693000] CPU: After vendor identify, caps: bfebfbff 20100000 00000000 00 000000 0000641d 00000000 00000000
[4294667.693000] monitor/mwait feature present.
[4294667.693000] using mwait in idle threads.
[4294667.693000] CPU: Trace cache: 12K uops, L1 D cache: 16K
[4294667.693000] CPU: L2 cache: 1024K
[4294667.693000] CPU: After all inits, caps: bfebfbff 20100000 00000000 00000080 0000641d 00000000 00000000
[4294667.693000] CPU: Intel(R) Pentium(R) 4 CPU 3.00GHz stepping 01
[4294667.693000] Enabling fast FPU save and restore... done.
[4294667.693000] Enabling unmasked SIMD FPU exception support... done.
[4294667.693000] Checking 'hlt' instruction... OK.
[4294667.697000] Checking for popad bug... OK.
[4294667.697000] checking if image is initramfs... it is
[4294668.069000] Freeing initrd memory: 4821k freed
[4294668.073000] ACPI: Looking for DSDT in initrd... not found!
[4294668.110000] not found!
[4294668.118000] ENABLING IO-APIC IRQs
[4294668.118000] ..TIMER: vector=0x31 pin1=2 pin2=-1
[4294668.229000] NET: Registered protocol family 16
[4294668.229000] EISA bus registered
[4294668.229000] ACPI: bus type pci registered
[4294668.232000] PCI: PCI BIOS revision 3.00 entry at 0xfac70, last bus=1
[4294668.232000] PCI: Using MMCONFIG
[4294668.232000] mtrr: v2.0 (20020519)
[4294668.233000] ACPI: Subsystem revision 20050729
[4294668.240000] ACPI: Interpreter enabled
[4294668.241000] ACPI: Using IOAPIC for interrupt routing
[4294668.241000] ACPI: PCI Root Bridge [PCI0] (0000:00)
[4294668.241000] PCI: Probing PCI hardware (bus 00)
[4294668.241000] ACPI: Assume root bridge [\_SB_.PCI0] segment is 0
[4294668.243000] PCI: Ignoring BAR0-3 of IDE controller 0000:00:1f.1
[4294668.243000] Boot video device is 0000:01:00.0
[4294668.243000] PCI: Transparent bridge - 0000:00:1e.0
[4294668.248000] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
[4294668.248000] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.HUB0._PRT]
[4294668.252000] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 *5 6 7 9 10 11 12 14 15)
[4294668.252000] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *9 10 11 12 14 15)
[4294668.253000] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 7 9 10 11 12 14 15)
[4294668.253000] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 9 10 *11 12 14 15)
[4294668.254000] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 9 10 *11 12 14 15)
[4294668.254000] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 9 *10 11 12 14 15)
[4294668.254000] ACPI: PCI Interrupt Link [LNK0] (IRQs 3 4 5 6 7 9 10 11 12 14 1 5) *0, disabled.
[4294668.255000] ACPI: PCI Interrupt Link [LNK1] (IRQs 3 4 5 6 7 9 *10 11 12 14 15)
[4294668.255000] Linux Plug and Play Support v0.97 (c) Adam Belay
[4294668.255000] pnp: PnP ACPI init
[4294668.258000] pnp: PnP ACPI: found 14 devices
[4294668.258000] PnPBIOS: Disabled by ACPI PNP
[4294668.259000] PCI: Using ACPI for IRQ routing
[4294668.259000] PCI: If a device doesn't work, try "pci=routeirq". If it helps , post a report
[4294668.268000] pnp: 00:0b: ioport range 0x400-0x4bf could not be reserved
[4294668.268000] audit: initializing netlink socket (disabled)
[4294668.268000] audit: initialized
[4294668.268000] highmem bounce pool size: 64 pages
[4294668.269000] VFS: Disk quotas dquot_6.5.1
[4294668.269000] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[4294668.269000] devfs: 2004-01-31 Richard Gooch (rgooch@atnf.csiro.au)
[4294668.269000] devfs: boot_options: 0x0
[4294668.269000] Initializing Cryptographic API
[4294668.269000] isapnp: Scanning for PnP cards...
[4294668.619000] isapnp: No Plug & Play device found
[4294668.638000] PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 i rq 1,12
[4294668.640000] serio: i8042 AUX port at 0x60,0x64 irq 12
[4294668.640000] serio: i8042 KBD port at 0x60,0x64 irq 1
[4294668.640000] Serial: 8250/16550 driver $Revision: 1.90 $ 54 ports, IRQ shari ng enabled
[4294668.640000] ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[4294668.641000] ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
[4294668.643000] ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[4294668.643000] ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
[4294668.643000] ACPI: PCI Interrupt 0000:01:01.0[A] -> GSI 20 (level, low) -> I RQ 20
[4294668.646000] io scheduler noop registered
[4294668.646000] io scheduler anticipatory registered
[4294668.646000] io scheduler deadline registered
[4294668.646000] io scheduler cfq registered
[4294668.646000] RAMDISK driver initialized: 16 RAM disks of 65536K size 1024 bl ocksize
[4294668.647000] EISA: Probing bus 0 at eisa.0
[4294668.647000] Cannot allocate resource for EISA slot 6
[4294668.647000] EISA: slot 7 : @@T0000 detected (disabled).
[4294668.647000] EISA: Detected 1 card.
[4294668.647000] NET: Registered protocol family 2
[4294668.656000] IP: routing cache hash table of 8192 buckets, 64Kbytes
[4294668.656000] TCP established hash table entries: 262144 (order: 9, 2097152 b ytes)
[4294668.657000] TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
[4294668.657000] TCP: Hash tables configured (established 262144 bind 65536)
[4294668.657000] NET: Registered protocol family 8
[4294668.657000] NET: Registered protocol family 20
[4294668.657000] ACPI wakeup devices:
[4294668.657000] PCI0 PEX0 PEX1 PEX2 PEX3 HUB0 USB0 USB1 USB2 USB3 USBE AC97 MC9 7 AZAL
[4294668.658000] ACPI: (supports S0 S1 S4 S5)
[4294668.658000] Freeing unused kernel memory: 224k freed
[4294668.667000] input: AT Translated Set 2 keyboard on isa0060/serio0
[4294668.690000] Capability LSM initialized
[4294668.701000] NET: Registered protocol family 1
[4294668.712000] Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
[4294668.712000] ide: Assuming 33MHz system bus speed for PIO modes; override wi th idebus=xx
[4294668.712000] ACPI: bus type ide registered
[4294668.721000] SCSI subsystem initialized
[4294668.722000] libata version 1.11 loaded.
[4294668.723000] ata_piix version 1.03
[4294668.723000] ACPI: PCI Interrupt 0000:00:1f.2[B] -> GSI 19 (level, low) -> I RQ 19
[4294668.723000] PCI: Setting latency timer of device 0000:00:1f.2 to 64
[4294668.723000] ata1: SATA max UDMA/133 cmd 0xC800 ctl 0xCC02 bmdma 0xD800 irq 19
[4294668.723000] ata2: SATA max UDMA/133 cmd 0xD000 ctl 0xD402 bmdma 0xD808 irq 19
[4294668.877000] ata1: dev 0 cfg 49:2f00 82:346b 83:7f01 84:4003 85:3c68 86:3c01 87:4003 88:20ff
[4294668.877000] ata1: dev 0 ATA, max UDMA7, 312581808 sectors: lba48
[4294668.877000] ata1: dev 0 configured for UDMA/133
[4294668.877000] scsi0 : ata_piix
[4294669.038000] ATA: abnormal status 0x7F on port 0xD007
[4294669.038000] ata2: disabling port
[4294669.038000] scsi1 : ata_piix
[4294669.038000] Vendor: ATA Model: SAMSUNG SP1614C Rev: SW10
[4294669.038000] Type: Direct-Access ANSI SCSI revision : 05
[4294669.043000] ICH6: IDE controller at PCI slot 0000:00:1f.1
[4294669.043000] ACPI: PCI Interrupt 0000:00:1f.1[A] -> GSI 18 (level, low) -> I RQ 18
[4294669.043000] ICH6: chipset revision 5
[4294669.043000] ICH6: not 100% native mode: will probe irqs later
[4294669.043000] ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb: pio
[4294669.043000] ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:pio, hdd: pio
[4294669.043000] Probing IDE interface ide0...
[4294669.715000] hda: HL-DT-ST DVDRAM GSA-4167B, ATAPI CD/DVD-ROM drive
[4294670.021000] ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
[4294670.021000] Probing IDE interface ide1...
[4294670.540000] Probing IDE interface ide1...
[4294671.058000] Probing IDE interface ide2...
[4294671.570000] Probing IDE interface ide3...
[4294672.082000] Probing IDE interface ide4...
[4294672.594000] Probing IDE interface ide5...
[4294673.112000] hda: ATAPI 48X DVD-ROM DVD-R-RAM CD-R/RW drive, 2048kB Cache
[4294673.112000] Uniform CD-ROM driver Revision: 3.20
[4294673.124000] SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
[4294673.124000] SCSI device sda: drive cache: write back
[4294673.124000] SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
[4294673.124000] SCSI device sda: drive cache: write back
[4294673.124000] /dev/scsi/host0/bus0/target0/lun0: p1 p2 < p5 >
[4294673.151000] Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
[4294673.407000] Attempting manual resume
[4294673.407000] swsusp: Suspend partition has wrong signature?
[4294673.468000] 8139cp: 10/100 PCI Ethernet driver v1.2 (Mar 22, 2004)
[4294673.468000] 8139cp: pci dev 0000:01:05.0 (id 10ec:8139 rev 10) is not an 81 39C+ compatible chip
[4294673.469000] 8139cp: Try the "8139too" driver instead.
[4294673.470000] 8139too Fast Ethernet driver 0.9.27
[4294673.470000] ACPI: PCI Interrupt 0000:01:05.0[A] -> GSI 21 (level, low) -> I RQ 21
[4294673.471000] eth0: RealTek RTL8139 at 0x9000, 00:0f:ea:aa:8b:3c, IRQ 21
[4294673.471000] eth0: Identified 8139 chip type 'RTL-8100B/8139D'
[4294675.742000] ACPI: CPU0 (power states: C1[C1])
[4294675.742000] ACPI: Processor [CPU0] (supports 2 throttling states)
[4294675.807000] Attempting manual resume
[4294675.808000] swsusp: Suspend partition has wrong signature?
[4294675.816000] EXT3-fs: INFO: recovery required on readonly filesystem.
[4294675.817000] EXT3-fs: write access will be enabled during recovery.
[4294678.023000] kjournald starting. Commit interval 5 seconds
[4294678.023000] EXT3-fs: recovery complete.
[4294678.024000] EXT3-fs: mounted filesystem with ordered data mode.
[4294679.214000] md: md driver 0.90.1 MAX_MD_DEVS=256, MD_SB_DISKS=27
[4294681.539000] Adding 3036244k swap on /dev/sda5. Priority:-1 extents:1
[4294681.724000] EXT3 FS on sda1, internal journal
[4294683.264000] parport: PnPBIOS parport detected.
[4294683.265000] parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE]
[4294683.351000] lp0: using parport0 (interrupt-driven).
[4294683.418000] mice: PS/2 mouse device common for all mice
[4294683.518000] Linux agpgart interface v0.101 (c) Dave Jones
[4294683.704000] nvidia: module license 'NVIDIA' taints kernel.
[4294683.709000] input: ImPS/2 Generic Wheel Mouse on isa0060/serio1
[4294683.741000] ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> I RQ 16
[4294683.741000] NVRM: loading NVIDIA Linux x86 NVIDIA Kernel Module 1.0-8178 Wed Dec 14 16:22:51 PST 2005
[4294683.987000] ts: Compaq touchscreen protocol output
[4294686.751000] device-mapper: 4.4.0-ioctl (2005-01-12) initialised: dm-devel@r edhat.com
[4294687.358000] cdrom: open failed.
[4294688.581000] agpgart: Detected an Intel 915G Chipset.
[4294688.611000] agpgart: AGP aperture is 256M @ 0x0
[4294688.702000] hw_random: RNG not detected
[4294689.306000] ACPI: PCI Interrupt 0000:00:1e.2[A] -> GSI 17 (level, low) -> I RQ 17
[4294689.306000] PCI: Setting latency timer of device 0000:00:1e.2 to 64
[4294689.615000] intel8x0_measure_ac97_clock: measured 49662 usecs
[4294689.615000] intel8x0: clocking to 48000
[4294690.391000] usbcore: registered new driver usbfs
[4294690.394000] usbcore: registered new driver hub
[4294690.565000] ohci_hcd: 2004 Nov 08 USB 1.1 'Open' Host Controller (OHCI) Dri ver (PCI)
[4294690.608000] USB Universal Host Controller Interface driver v2.2
[4294691.236000] CSLIP: code copyright 1989 Regents of the University of Califor nia
[4294691.244000] PPP generic driver version 2.4.2
[4294691.272000] NET: Registered protocol family 17
[4294691.296000] NET: Registered protocol family 10
[4294691.296000] Disabled Privacy Extensions on device c02eb280(lo)
[4294691.296000] IPv6 over IPv4 tunneling driver
[4294691.307000] eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
[4294691.411000] NET: Registered protocol family 24
[4294696.596000] ip_tables: (C) 2000-2002 Netfilter core team
[4294701.600000] eth0: no IPv6 routers present
[4294813.746000] ACPI: Power Button (FF) [PWRF]
[4294813.746000] ACPI: Power Button (CM) [PWRB]
[4294813.847000] ibm_acpi: ec object not found
[4294819.520000] apm: BIOS version 1.2 Flags 0x07 (Driver version 1.16ac)
[4294819.520000] apm: overridden by ACPI.
[4294820.023000] Bluetooth: Core ver 2.7
[4294820.023000] NET: Registered protocol family 31
[4294820.023000] Bluetooth: HCI device and connection manager initialized
[4294820.023000] Bluetooth: HCI socket layer initialized
[4294820.051000] Bluetooth: L2CAP ver 2.7
[4294820.051000] Bluetooth: L2CAP socket layer initialized
[4294820.128000] Bluetooth: RFCOMM ver 1.5
[4294820.128000] Bluetooth: RFCOMM socket layer initialized
[4294820.128000] Bluetooth: RFCOMM TTY layer initialized

Can You help me?

tseliot
February 19th, 2006, 09:10 AM
I've followed your guide using the option 2. No error messages, everything goes fine, but when I try to startx receive just a black screen, can't even type. The only way to restore is using the recovery mode and restoring the xorg.conf or changing "nvidia" to "nv". I using 5.10 and my card is a Gforce FX 5200

I need you to reproduce the error.

Set the nvidia driver in your /etc/X11/xorg.conf (or if it's already set leave it as it is.
When GDM (or kdm) crashes at startup Press CTRL+ALT+F1
Then type

Then:
sudo /etc/init.d/gdm stop (if you use GDM)
OR
sudo /etc/init.d/kdm stop (if you use KDM)

startx -- -verbose 5 -logverbose 5

You will get the same error.

sudo cp /var/log/Xorg.0.log /home/your_username/Xorg.0.log
(Of course you have to replace "your_username" with your username)

and post the content of that file (which you can find under /home/your_username/Xorg.0.log )


BTW if you want to access the GNOME or KDE again you can use this quick fix:
sudo nano /etc/X11/xorg.conf
Set the driver back to "nv" instead of "nvidia"
CTRL+O to save
CTRL+X to exit

sudo /etc/init.d/gdm stop (if you use GDM)
OR
sudo /etc/init.d/kdm stop (if you use KDM)

Then
sudo /etc/init.d/gdm start (if you use GDM)
OR
sudo /etc/init.d/kdm start (if you use KDM)

Jose Monteiro
February 19th, 2006, 01:52 PM
Thank you for your attention. This is the result of /var/log/Xorg.0.log
BTW: I had to cut some text, because exceeded the post limit.

(II) Loading font FreeType
(II) LoadModule: "glx"
(II) Loading /usr/X11R6/lib/modules/extensions/libglx.so
(II) Module glx: vendor="NVIDIA Corporation"
compiled for 4.0.2, module version = 1.0.8178
Module class: XFree86 Server Extension
ABI class: XFree86 Server Extension, version 0.1
(II) Loading extension GLX
(II) LoadModule: "int10"
(II) Loading /usr/X11R6/lib/modules/linux/libint10.a
(II) Module int10: vendor="X.Org Foundation"
compiled for 6.8.2, module version = 1.0.0
ABI class: X.Org Video Driver, version 0.7
(II) LoadModule: "type1"
(II) Loading /usr/X11R6/lib/modules/fonts/libtype1.a
(II) Module type1: vendor="X.Org Foundation"
compiled for 6.8.2, module version = 1.0.2
Module class: X.Org Font Renderer
ABI class: X.Org Font Renderer, version 0.4
(II) Loading font Type1
(II) Loading font CID
(II) LoadModule: "vbe"
(II) Loading /usr/X11R6/lib/modules/libvbe.a
(II) Module vbe: vendor="X.Org Foundation"
compiled for 6.8.2, module version = 1.1.0
ABI class: X.Org Video Driver, version 0.7
(II) LoadModule: "nv"
(II) Loading /usr/X11R6/lib/modules/drivers/nv_drv.o
(II) Module nv: vendor="X.Org Foundation"
compiled for 6.8.2, module version = 1.0.1
Module class: X.Org Video Driver
ABI class: X.Org Video Driver, version 0.7
(II) LoadModule: "kbd"
(II) Loading /usr/X11R6/lib/modules/input/kbd_drv.o
(II) Module kbd: vendor="X.Org Foundation"
compiled for 6.8.2, module version = 1.0.0
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 0.4
(II) LoadModule: "mouse"
(II) Loading /usr/X11R6/lib/modules/input/mouse_drv.o
(II) Module mouse: vendor="X.Org Foundation"
compiled for 6.8.2, module version = 1.0.0
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 0.4
(II) NV: driver for NVIDIA chipsets: RIVA 128, RIVA TNT, RIVA TNT2,
Unknown TNT2, Vanta, RIVA TNT2 Ultra, RIVA TNT2 Model 64,
Aladdin TNT2, GeForce 256, GeForce DDR, Quadro, GeForce2 MX/MX 400,
GeForce2 MX 100/200, GeForce2 Go, Quadro2 MXR/EX/Go,
GeForce2 Integrated GPU, GeForce2 GTS, GeForce2 Ti, GeForce2 Ultra,
Quadro2 Pro, GeForce4 MX 460, GeForce4 MX 440, GeForce4 MX 420,
GeForce4 MX 440-SE, GeForce4 440 Go, GeForce4 420 Go,
GeForce4 420 Go 32M, GeForce4 460 Go, Quadro4 550 XGL,
GeForce4 440 Go 64M, Quadro4 NVS, Quadro4 500 GoGL,
GeForce4 410 Go 16M, GeForce4 MX 440 with AGP8X,
GeForce4 MX 440SE with AGP8X, GeForce4 MX 420 with AGP8X,
GeForce4 MX 4000, GeForce4 448 Go, GeForce4 488 Go, Quadro4 580 XGL,
Quadro4 280 NVS, Quadro4 380 XGL, Quadro NVS 50 PCI, GeForce4 448 Go,
GeForce4 MX Integrated GPU, GeForce3, GeForce3 Ti 200,
GeForce3 Ti 500, Quadro DCC, GeForce4 Ti 4600, GeForce4 Ti 4400,
0x0252, GeForce4 Ti 4200, Quadro4 900 XGL, Quadro4 750 XGL,
Quadro4 700 XGL, GeForce4 Ti 4800, GeForce4 Ti 4200 with AGP8X,
GeForce4 Ti 4800 SE, GeForce4 4200 Go, Quadro4 700 GoGL,
Quadro4 980 XGL, Quadro4 780 XGL, GeForce FX 5800 Ultra,
GeForce FX 5800, Quadro FX 2000, Quadro FX 1000,
GeForce FX 5600 Ultra, GeForce FX 5600, 0x0313, GeForce FX 5600SE,
0x0316, 0x0317, GeForce FX Go5600, GeForce FX Go5650,
Quadro FX Go700, 0x031D, 0x031E, 0x031F, GeForce FX 5200,
GeForce FX 5200 Ultra, GeForce FX 5200, GeForce FX 5200SE,
GeForce FX Go5200, GeForce FX Go5250, GeForce FX 5500,
GeForce FX 5100, GeForce FX Go5200 32M/64M, 0x0329,
Quadro NVS 280 PCI, Quadro FX 500/600 PCI, GeForce FX Go53xx Series,
GeForce FX Go5100, 0x032F, GeForce FX 5900 Ultra, GeForce FX 5900,
GeForce FX 5900XT, GeForce FX 5950 Ultra, Quadro FX 700,
GeForce FX 5900ZT, Quadro FX 3000, GeForce FX 5700 Ultra,
GeForce FX 5700, GeForce FX 5700LE, GeForce FX 5700VE, 0x0345,
GeForce FX Go5700, GeForce FX Go5700, 0x0349, 0x034B,
Quadro FX Go1000, Quadro FX 1100, 0x034F, GeForce 6800 Ultra,
GeForce 6800, GeForce 6800 LE, 0x0043, GeForce 6800 GT, 0x0049,
Quadro FX 4000, 0x00C0, GeForce 6800, GeForce 6800 LE,
GeForce Go 6800, GeForce Go 6800 Ultra, Quadro FX Go1400, 0x00CD,
Quadro FX 1400, GeForce 6600 GT, GeForce 6600, 0x0142, 0x0143,
GeForce Go 6600, GeForce 6610 XL, GeForce Go 6600 TE/6200 TE, 0x0147,
GeForce Go 6600, 0x0149, 0x014B, 0x014C, 0x014D, Quadro FX 540,
GeForce 6200, 0x0160, GeForce 6200 TurboCache(TM), 0x0162, 0x0163,
GeForce Go 6200, 0x0163, GeForce Go 6250, GeForce Go 6200,
GeForce Go 6250, 0x0169, 0x016B, 0x016C, 0x016D, 0x016E, 0x0210,
GeForce 6800, GeForce 6800 LE, GeForce 6800 GT, 0x0220, 0x0221,
0x0222, 0x0228
(II) Primary Device is: PCI 01:00:0
(--) Assigning device section with no busID to primary device
(--) Chipset GeForce FX 5200 found
(II) resource ranges after xf86ClaimFixedResources() call:
[0] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B)
[1] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
[2] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[3] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[4] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[5] -1 0 0xf2002000 - 0xf20020ff (0x100) MX[B]
[6] -1 0 0xf2000000 - 0xf2001fff (0x2000) MX[B]
[7] -1 0 0xf3002000 - 0xf30020ff (0x100) MX[B]
[8] -1 0 0xf3001000 - 0xf30011ff (0x200) MX[B]
[9] -1 0 0xe0000000 - 0xefffffff (0x10000000) MX[B](B)
[10] -1 0 0xf0000000 - 0xf0ffffff (0x1000000) MX[B](B)
[11] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[12] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
[13] -1 0 0x00009000 - 0x000090ff (0x100) IX[B]
[14] -1 0 0x00006800 - 0x000068ff (0x100) IX[B]
[15] -1 0 0x00000500 - 0x0000051f (0x20) IX[B]
[16] -1 0 0x0000d800 - 0x0000d80f (0x10) IX[B]
[17] -1 0 0x0000d400 - 0x0000d403 (0x4) IX[B]
[18] -1 0 0x0000d000 - 0x0000d007 (0x8) IX[B]
[19] -1 0 0x0000cc00 - 0x0000cc03 (0x4) IX[B]
[20] -1 0 0x0000c800 - 0x0000c807 (0x8) IX[B]
[21] -1 0 0x0000f000 - 0x0000f00f (0x10) IX[B]
[22] -1 0 0x0000bc00 - 0x0000bc3f (0x40) IX[B]
[23] -1 0 0x0000b800 - 0x0000b8ff (0x100) IX[B]
(II) resource ranges after probing:
[0] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B)
[1] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
[2] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[3] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[4] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[5] -1 0 0xf2002000 - 0xf20020ff (0x100) MX[B]
[6] -1 0 0xf2000000 - 0xf2001fff (0x2000) MX[B]
[7] -1 0 0xf3002000 - 0xf30020ff (0x100) MX[B]
[8] -1 0 0xf3001000 - 0xf30011ff (0x200) MX[B]
[9] -1 0 0xe0000000 - 0xefffffff (0x10000000) MX[B](B)
[10] -1 0 0xf0000000 - 0xf0ffffff (0x1000000) MX[B](B)

[11] 0 0 0x000a0000 - 0x000affff (0x10000) MS[B]
[12] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[B]
[13] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[B]
[14] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[15] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
[16] -1 0 0x00009000 - 0x000090ff (0x100) IX[B]
[17] -1 0 0x00006800 - 0x000068ff (0x100) IX[B]
[18] -1 0 0x00000500 - 0x0000051f (0x20) IX[B]
[19] -1 0 0x0000d800 - 0x0000d80f (0x10) IX[B]
[20] -1 0 0x0000d400 - 0x0000d403 (0x4) IX[B]
[21] -1 0 0x0000d000 - 0x0000d007 (0x8) IX[B]
[22] -1 0 0x0000cc00 - 0x0000cc03 (0x4) IX[B]
[23] -1 0 0x0000c800 - 0x0000c807 (0x8) IX[B]
[24] -1 0 0x0000f000 - 0x0000f00f (0x10) IX[B]
[25] -1 0 0x0000bc00 - 0x0000bc3f (0x40) IX[B]
[26] -1 0 0x0000b800 - 0x0000b8ff (0x100) IX[B]
[27] 0 0 0x000003b0 - 0x000003bb (0xc) IS[B]
[28] 0 0 0x000003c0 - 0x000003df (0x20) IS[B]
(II) Setting vga for screen 0.
(II) Loading sub module "int10"
(II) LoadModule: "int10"
(II) Reloading /usr/X11R6/lib/modules/linux/libint10.a
(II) NV(0): Initializing int10
(II) NV(0): Primary V_BIOS segment is: 0xc000
(--) NV(0): Chipset: "GeForce FX 5200"
(**) NV(0): Depth 24, (--) framebuffer bpp 32
(==) NV(0): RGB weight 888
(==) NV(0): Default visual is TrueColor
(II) Loading sub module "vgahw"
(II) LoadModule: "vgahw"
(II) Loading /usr/X11R6/lib/modules/libvgahw.a
(II) Module vgahw: vendor="X.Org Foundation"
compiled for 6.8.2, module version = 0.1.0
ABI class: X.Org Video Driver, version 0.7
(==) NV(0): Using HW cursor
(--) NV(0): Linear framebuffer at 0xE0000000
(--) NV(0): MMIO registers at 0xF0000000
(II) Loading sub module "i2c"
(II) LoadModule: "i2c"
(II) Reloading /usr/X11R6/lib/modules/libi2c.a
(II) Loading sub module "ddc"
(II) LoadModule: "ddc"
(II) Reloading /usr/X11R6/lib/modules/libddc.a
(II) NV(0): I2C bus "DDC" initialized.
(II) NV(0): Probing for analog device on output A...
(--) NV(0): ...found one
(II) NV(0): Probing for analog device on output B...
(--) NV(0): ...can't find one
(II) NV(0): Probing for EDID on I2C bus A...
(II) NV(0): I2C device "DDC:ddc2" registered at address 0xA0.
(II) NV(0): I2C device "DDC:ddc2" removed.
(--) NV(0): DDC detected a CRT:
(II) NV(0): Manufacturer: SAM Model: 1057 Serial#: 1146106167
(II) NV(0): Year: 2001 Week: 48
(II) NV(0): EDID Version: 1.1
(II) NV(0): Analog Display Input, Input Voltage Level: 0.700/0.700 V
(II) NV(0): Sync: Separate
(II) NV(0): Max H-Image Size [cm]: horiz.: 32 vert.: 24
(II) NV(0): Gamma: 2.26
(II) NV(0): DPMS capabilities: StandBy Suspend Off; RGB/Color Display
(II) NV(0): redX: 0.645 redY: 0.321 greenX: 0.285 greenY: 0.600
(II) NV(0): blueX: 0.142 blueY: 0.057 whiteX: 0.283 whiteY: 0.298
(II) NV(0): Supported VESA Video Modes:
(II) NV(0): 720x400@70Hz
(II) NV(0): 720x400@88Hz
(II) NV(0): 640x480@60Hz
(II) NV(0): 640x480@67Hz
(II) NV(0): 640x480@72Hz
(II) NV(0): 640x480@75Hz
(II) NV(0): 800x600@56Hz
(II) NV(0): 800x600@60Hz
(II) NV(0): 800x600@72Hz
(II) NV(0): 800x600@75Hz
(II) NV(0): 832x624@75Hz
(II) NV(0): 1024x768@87Hz (interlaced)
(II) NV(0): 1024x768@60Hz
(II) NV(0): 1024x768@70Hz
(II) NV(0): 1024x768@75Hz
(II) NV(0): Manufacturer's mask: 0
(II) NV(0): Supported Future Video Modes:
(II) NV(0): #0: hsize: 640 vsize 480 refresh: 85 vid: 22833
(II) NV(0): #1: hsize: 800 vsize 600 refresh: 85 vid: 22853
(II) NV(0): #2: hsize: 1024 vsize 768 refresh: 85 vid: 22881
(II) NV(0): #3: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
(II) NV(0): Supported additional Video Mode:
(II) NV(0): clock: 94.5 MHz Image Size: 306 x 230 mm
(II) NV(0): h_active: 1024 h_sync: 1072 h_sync_end 1168 h_blank_end 1376 h_border: 0
(II) NV(0): v_active: 768 v_sync: 769 v_sync_end 772 v_blanking: 808 v_border: 0
(II) NV(0): Supported additional Video Mode:
(II) NV(0): clock: 56.2 MHz Image Size: 306 x 230 mm
(II) NV(0): h_active: 800 h_sync: 832 h_sync_end 896 h_blank_end 1048 h_border: 0
(II) NV(0): v_active: 600 v_sync: 601 v_sync_end 604 v_blanking: 631 v_border: 0
(II) NV(0): Ranges: V min: 50 V max: 160 Hz, H min: 30 H max: 70 kHz, PixClock max 110 MHz
(II) NV(0): Serial No: HXARB03663
(II) NV(0): Probing for EDID on I2C bus B...
(II) NV(0): I2C device "DDC:ddc2" registered at address 0xA0.
(II) NV(0): I2C device "DDC:ddc2" removed.
(II) NV(0): ... none found
(--) NV(0): CRTC 0 appears to have a CRT attached
(II) NV(0): Using CRT on CRTC 0
(--) NV(0): VideoRAM: 262144 kBytes
(==) NV(0): Using gamma correction (1.0, 1.0, 1.0)
(II) NV(0): Generic Monitor: Using default hsync range of 30.00-70.00 kHz
(II) NV(0): Generic Monitor: Using default vrefresh range of 50.00-160.00 Hz
(II) NV(0): Clock range: 12.00 to 350.00 MHz
(II) NV(0): Not using default mode "1280x960" (hsync out of range)
(II) NV(0): Not using default mode "640x480" (hsync out of range)
(II) NV(0): Not using default mode "1280x1024" (hsync out of range)
(II) NV(0): Not using default mode "640x512" (hsync out of range)
(II) NV(0): Not using default mode "1280x1024" (hsync out of range)
(II) NV(0): Not using default mode "640x512" (hsync out of range)
(II) NV(0): Not using default mode "1600x1200" (hsync out of range)
(II) NV(0): Not using default mode "800x600" (hsync out of range)
(II) NV(0): Not using default mode "1600x1200" (hsync out of range)
(II) NV(0): Not using default mode "800x600" (hsync out of range)
(II) NV(0): Not using default mode "1600x1200" (hsync out of range)
(II) NV(0): Not using default mode "800x600" (hsync out of range)
(II) NV(0): Not using default mode "1600x1200" (hsync out of range)
(II) NV(0): Not using default mode "800x600" (hsync out of range)
(II) NV(0): Not using default mode "1600x1200" (hsync out of range)
(II) NV(0): Not using default mode "800x600" (hsync out of range)
(II) NV(0): Not using default mode "1792x1344" (hsync out of range)
(II) NV(0): Not using default mode "896x672" (hsync out of range)
(II) NV(0): Not using default mode "1792x1344" (hsync out of range)
(II) NV(0): Not using default mode "896x672" (hsync out of range)
(II) NV(0): Not using default mode "1856x1392" (hsync out of range)
(II) NV(0): Not using default mode "928x696" (hsync out of range)
(II) NV(0): Not using default mode "1856x1392" (hsync out of range)
(II) NV(0): Not using default mode "928x696" (hsync out of range)
(II) NV(0): Not using default mode "1920x1440" (hsync out of range)
(II) NV(0): Not using default mode "960x720" (hsync out of range)
(II) NV(0): Not using default mode "1920x1440" (hsync out of range)
(II) NV(0): Not using default mode "960x720" (hsync out of range)
(II) NV(0): Not using default mode "1152x864" (hsync out of range)
(II) NV(0): Not using default mode "576x432" (hsync out of range)
(WW) (1400x1050,Generic Monitor) mode clock 122MHz exceeds DDC maximum 110MHz
(II) NV(0): Not using default mode "1400x1050" (hsync out of range)
(II) NV(0): Not using default mode "700x525" (hsync out of range)
(II) NV(0): Not using default mode "1400x1050" (hsync out of range)
(II) NV(0): Not using default mode "700x525" (hsync out of range)
(II) NV(0): Not using default mode "1400x1050" (hsync out of range)
(II) NV(0): Not using default mode "700x525" (hsync out of range)
(WW) (1680x1050,Generic Monitor) mode clock 147.14MHz exceeds DDC maximum 110MHz
(II) NV(0): Not using default mode "1920x1200" (hsync out of range)
(II) NV(0): Not using default mode "960x600" (hsync out of range)
(II) NV(0): Not using default mode "1920x1200" (hsync out of range)
(II) NV(0): Not using default mode "960x600" (hsync out of range)
(II) NV(0): Not using default mode "1920x1440" (hsync out of range)
(II) NV(0): Not using default mode "960x720" (hsync out of range)
(II) NV(0): Not using default mode "2048x1536" (hsync out of range)
(II) NV(0): Not using default mode "1024x768" (hsync out of range)
(II) NV(0): Not using default mode "2048x1536" (hsync out of range)
(II) NV(0): Not using default mode "1024x768" (hsync out of range)
(II) NV(0): Not using default mode "2048x1536" (bad mode clock/interlace/doublescan)

(II) NV(0): Not using default mode "1024x768" (hsync out of range)
(II) NV(0): Not using default mode "1680x1050" (width too large for virtual size)
(II) NV(0): Not using default mode "1400x1050" (width too large for virtual size)
(II) NV(0): Not using default mode "1440x900" (width too large for virtual size)
(--) NV(0): Virtual size is 1280x1024 (pitch 1280)
(**) NV(0): *Default mode "1280x1024": 108.0 MHz, 64.0 kHz, 60.0 Hz
(II) NV(0): Modeline "1280x1024" 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync
(**) NV(0): *Default mode "1024x768": 94.5 MHz, 68.7 kHz, 85.0 Hz
(II) NV(0): Modeline "1024x768" 94.50 1024 1072 1168 1376 768 769 772 808 +hsync +vsync
(**) NV(0): *Default mode "832x624": 57.3 MHz, 49.7 kHz, 74.6 Hz
(II) NV(0): Modeline "832x624" 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync
(**) NV(0): *Default mode "800x600": 56.3 MHz, 53.7 kHz, 85.1 Hz
(II) NV(0): Modeline "800x600" 56.30 800 832 896 1048 600 601 604 631 +hsync +vsync
(**) NV(0): *Default mode "720x400": 35.5 MHz, 37.9 kHz, 85.0 Hz
(II) NV(0): Modeline "720x400" 35.50 720 756 828 936 400 401 404 446 -hsync +vsync
(**) NV(0): *Default mode "640x480": 36.0 MHz, 43.3 kHz, 85.0 Hz
(II) NV(0): Modeline "640x480" 36.00 640 696 752 832 480 481 484 509 -hsync -vsync
(**) NV(0): Default mode "1280x960": 108.0 MHz, 60.0 kHz, 60.0 Hz
(II) NV(0): Modeline "1280x960" 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync
(**) NV(0): Default mode "1280x800": 83.5 MHz, 49.7 kHz, 60.0 Hz
(II) NV(0): Modeline "1280x800" 83.46 1280 1344 1480 1680 800 801 804 828
(**) NV(0): Default mode "1152x864": 108.0 MHz, 67.5 kHz, 75.0 Hz
(II) NV(0): Modeline "1152x864" 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync
(**) NV(0): Default mode "1280x768": 80.1 MHz, 47.7 kHz, 60.0 Hz
(II) NV(0): Modeline "1280x768" 80.14 1280 1344 1480 1680 768 769 772 795
(**) NV(0): Default mode "1152x768": 65.0 MHz, 44.2 kHz, 54.8 Hz
(II) NV(0): Modeline "1152x768" 65.00 1152 1178 1314 1472 768 771 777 806 +hsync +vsync
(**) NV(0): Default mode "1024x768": 78.8 MHz, 60.1 kHz, 75.1 Hz
(II) NV(0): Modeline "1024x768" 78.80 1024 1040 1136 1312 768 769 772 800 +hsync +vsync
(**) NV(0): Default mode "1024x768": 75.0 MHz, 56.5 kHz, 70.1 Hz
(II) NV(0): Modeline "1024x768" 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync
(**) NV(0): Default mode "1024x768": 65.0 MHz, 48.4 kHz, 60.0 Hz
(II) NV(0): Modeline "1024x768" 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync
(**) NV(0): Default mode "1024x768": 44.9 MHz, 35.5 kHz, 87.1 Hz (I)
(II) NV(0): Modeline "1024x768" 44.90 1024 1032 1208 1264 768 768 776 817 interlace +hsync +vsync
(**) NV(0): Default mode "800x600": 49.5 MHz, 46.9 kHz, 75.0 Hz
(II) NV(0): Modeline "800x600" 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync
(**) NV(0): Default mode "800x600": 50.0 MHz, 48.1 kHz, 72.2 Hz
(II) NV(0): Modeline "800x600" 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync
(**) NV(0): Default mode "800x600": 40.0 MHz, 37.9 kHz, 60.3 Hz
(II) NV(0): Modeline "800x600" 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync
(**) NV(0): Default mode "800x600": 36.0 MHz, 35.2 kHz, 56.2 Hz
(II) NV(0): Modeline "800x600" 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync
(**) NV(0): Default mode "840x525": 73.6 MHz, 65.2 kHz, 60.1 Hz (D)
(II) NV(0): Modeline "840x525" 73.57 840 892 984 1128 525 525 527 543 doublescan
(**) NV(0): Default mode "700x525": 61.0 MHz, 64.9 kHz, 60.0 Hz (D)
(II) NV(0): Modeline "700x525" 61.00 700 744 820 940 525 526 532 541 doublescan +hsync +vsync
(**) NV(0): Default mode "640x512": 54.0 MHz, 64.0 kHz, 60.0 Hz (D)
(II) NV(0): Modeline "640x512" 54.00 640 664 720 844 512 512 514 533 doublescan +hsync +vsync
(**) NV(0): Default mode "720x450": 54.4 MHz, 56.9 kHz, 60.2 Hz (D)
(II) NV(0): Modeline "720x450" 54.42 720 736 940 956 450 459 463 473 doublescan +hsync +vsync
(**) NV(0): Default mode "640x480": 31.5 MHz, 37.5 kHz, 75.0 Hz
(II) NV(0): Modeline "640x480" 31.50 640 656 720 840 480 481 484 500 -hsync -vsync
(**) NV(0): Default mode "640x480": 31.5 MHz, 37.9 kHz, 72.8 Hz
(II) NV(0): Modeline "640x480" 31.50 640 664 704 832 480 489 491 520 -hsync -vsync
(**) NV(0): Default mode "640x480": 25.2 MHz, 31.5 kHz, 60.0 Hz
(II) NV(0): Modeline "640x480" 25.20 640 656 752 800 480 490 492 525 -hsync -vsync
(**) NV(0): Default mode "640x480": 54.0 MHz, 60.0 kHz, 60.0 Hz (D)
(II) NV(0): Modeline "640x480" 54.00 640 688 744 900 480 480 482 500 doublescan +hsync +vsync
(**) NV(0): Default mode "640x400": 31.5 MHz, 37.9 kHz, 85.1 Hz
(II) NV(0): Modeline "640x400" 31.50 640 672 736 832 400 401 404 445 -hsync +vsync
(**) NV(0): Default mode "640x400": 41.7 MHz, 49.7 kHz, 60.0 Hz (D)
(II) NV(0): Modeline "640x400" 41.73 640 672 740 840 400 400 402 414 doublescan
(**) NV(0): Default mode "576x432": 54.0 MHz, 67.5 kHz, 75.0 Hz (D)
(II) NV(0): Modeline "576x432" 54.00 576 608 672 800 432 432 434 450 doublescan +hsync +vsync
(**) NV(0): Default mode "640x384": 40.1 MHz, 47.7 kHz, 60.1 Hz (D)
(II) NV(0): Modeline "640x384" 40.07 640 672 740 840 384 384 386 397 doublescan
(**) NV(0): Default mode "640x350": 31.5 MHz, 37.9 kHz, 85.1 Hz
(II) NV(0): Modeline "640x350" 31.50 640 672 736 832 350 382 385 445 +hsync -vsync
(**) NV(0): Default mode "576x384": 32.5 MHz, 44.2 kHz, 54.8 Hz (D)
(II) NV(0): Modeline "576x384" 32.50 576 589 657 736 384 385 388 403 doublescan +hsync +vsync
(**) NV(0): Default mode "512x384": 47.2 MHz, 68.7 kHz, 85.0 Hz (D)
(II) NV(0): Modeline "512x384" 47.25 512 536 584 688 384 384 386 404 doublescan +hsync +vsync
(**) NV(0): Default mode "512x384": 39.4 MHz, 60.1 kHz, 75.1 Hz (D)
(II) NV(0): Modeline "512x384" 39.40 512 520 568 656 384 384 386 400 doublescan +hsync +vsync
(**) NV(0): Default mode "512x384": 37.5 MHz, 56.5 kHz, 70.1 Hz (D)
(II) NV(0): Modeline "512x384" 37.50 512 524 592 664 384 385 388 403 doublescan -hsync -vsync
(**) NV(0): Default mode "512x384": 32.5 MHz, 48.4 kHz, 60.0 Hz (D)
(II) NV(0): Modeline "512x384" 32.50 512 524 592 672 384 385 388 403 doublescan -hsync -vsync
(**) NV(0): Default mode "512x384": 22.4 MHz, 35.5 kHz, 87.1 Hz (D)
(II) NV(0): Modeline "512x384" 22.45 512 516 604 632 384 384 388 409 interlace doublescan +hsync +vsync
(**) NV(0): Default mode "416x312": 28.6 MHz, 49.7 kHz, 74.7 Hz (D)
(II) NV(0): Modeline "416x312" 28.64 416 432 464 576 312 312 314 333 doublescan -hsync -vsync
(**) NV(0): Default mode "400x300": 28.1 MHz, 53.7 kHz, 85.3 Hz (D)
(II) NV(0): Modeline "400x300" 28.15 400 416 448 524 300 300 302 315 doublescan +hsync +vsync
(**) NV(0): Default mode "400x300": 24.8 MHz, 46.9 kHz, 75.1 Hz (D)
(II) NV(0): Modeline "400x300" 24.75 400 408 448 528 300 300 302 312 doublescan +hsync +vsync
(**) NV(0): Default mode "400x300": 25.0 MHz, 48.1 kHz, 72.2 Hz (D)
(II) NV(0): Modeline "400x300" 25.00 400 428 488 520 300 318 321 333 doublescan +hsync +vsync
(**) NV(0): Default mode "400x300": 20.0 MHz, 37.9 kHz, 60.3 Hz (D)
(II) NV(0): Modeline "400x300" 20.00 400 420 484 528 300 300 302 314 doublescan +hsync +vsync
(**) NV(0): Default mode "400x300": 18.0 MHz, 35.2 kHz, 56.3 Hz (D)
(II) NV(0): Modeline "400x300" 18.00 400 412 448 512 300 300 301 312 doublescan +hsync +vsync
(**) NV(0): Default mode "320x240": 18.0 MHz, 43.3 kHz, 85.2 Hz (D)
(II) NV(0): Modeline "320x240" 18.00 320 348 376 416 240 240 242 254 doublescan -hsync -vsync
(**) NV(0): Default mode "320x240": 15.8 MHz, 37.5 kHz, 75.0 Hz (D)
(II) NV(0): Modeline "320x240" 15.75 320 328 360 420 240 240 242 250 doublescan -hsync -vsync
(**) NV(0): Default mode "320x240": 15.8 MHz, 37.9 kHz, 72.8 Hz (D)
(II) NV(0): Modeline "320x240" 15.75 320 332 352 416 240 244 245 260 doublescan -hsync -vsync
(**) NV(0): Default mode "320x240": 12.6 MHz, 31.5 kHz, 60.1 Hz (D)
(II) NV(0): Modeline "320x240" 12.60 320 328 376 400 240 245 246 262 doublescan -hsync -vsync
(**) NV(0): Default mode "360x200": 17.8 MHz, 37.9 kHz, 85.0 Hz (D)
(II) NV(0): Modeline "360x200" 17.75 360 378 414 468 200 200 202 223 doublescan -hsync +vsync
(**) NV(0): Default mode "320x200": 15.8 MHz, 37.9 kHz, 85.3 Hz (D)
(II) NV(0): Modeline "320x200" 15.75 320 336 368 416 200 200 202 222 doublescan -hsync +vsync
(**) NV(0): Default mode "320x175": 15.8 MHz, 37.9 kHz, 85.3 Hz (D)
(II) NV(0): Modeline "320x175" 15.75 320 336 368 416 175 191 192 222 doublescan +hsync -vsync
(--) NV(0): Display dimensions: (320, 240) mm
(--) NV(0): DPI set to (101, 108)
(II) Loading sub module "fb"
(II) LoadModule: "fb"
(II) Loading /usr/X11R6/lib/modules/libfb.a
Skipping "/usr/X11R6/lib/modules/libfb.a:fbmmx.o": No symbols found
(II) Module fb: vendor="X.Org Foundation"
compiled for 6.8.2, module version = 1.0.0
ABI class: X.Org ANSI C Emulation, version 0.2
(II) Loading sub module "xaa"
(II) LoadModule: "xaa"
(II) Loading /usr/X11R6/lib/modules/libxaa.a
(II) Module xaa: vendor="X.Org Foundation"
compiled for 6.8.2, module version = 1.2.0
ABI class: X.Org Video Driver, version 0.7
(II) Loading sub module "ramdac"
(II) LoadModule: "ramdac"
(II) Loading /usr/X11R6/lib/modules/libramdac.a
(II) Module ramdac: vendor="X.Org Foundation"
compiled for 6.8.2, module version = 0.1.0
ABI class: X.Org Video Driver, version 0.7
(--) Depth 24 pixmap format is 32 bpp
(II) do I need RAC? No, I don't.
(II) resource ranges after preInit:
[0] 0 0 0xe0000000 - 0xefffffff (0x10000000) MX[B]
[1] 0 0 0xf0000000 - 0xf0ffffff (0x1000000) MX[B]
[2] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B)
[3] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
[4] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[5] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[6] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[7] -1 0 0xf2002000 - 0xf20020ff (0x100) MX[B]
[8] -1 0 0xf2000000 - 0xf2001fff (0x2000) MX[B]
[9] -1 0 0xf3002000 - 0xf30020ff (0x100) MX[B]
[10] -1 0 0xf3001000 - 0xf30011ff (0x200) MX[B]
[11] -1 0 0xe0000000 - 0xefffffff (0x10000000) MX[B](B)
[12] -1 0 0xf0000000 - 0xf0ffffff (0x1000000) MX[B](B)
[13] 0 0 0x000a0000 - 0x000affff (0x10000) MS[B](OprD)
[14] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[B](OprD)
[15] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[B](OprD)
[16] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[17] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
[18] -1 0 0x00009000 - 0x000090ff (0x100) IX[B]
[19] -1 0 0x00006800 - 0x000068ff (0x100) IX[B]
[20] -1 0 0x00000500 - 0x0000051f (0x20) IX[B]
[21] -1 0 0x0000d800 - 0x0000d80f (0x10) IX[B]
[22] -1 0 0x0000d400 - 0x0000d403 (0x4) IX[B]
[23] -1 0 0x0000d000 - 0x0000d007 (0x8) IX[B]
[24] -1 0 0x0000cc00 - 0x0000cc03 (0x4) IX[B]
[25] -1 0 0x0000c800 - 0x0000c807 (0x8) IX[B]
[26] -1 0 0x0000f000 - 0x0000f00f (0x10) IX[B]
[27] -1 0 0x0000bc00 - 0x0000bc3f (0x40) IX[B]
[28] -1 0 0x0000b800 - 0x0000b8ff (0x100) IX[B]
[29] 0 0 0x000003b0 - 0x000003bb (0xc) IS[B](OprU)
[30] 0 0 0x000003c0 - 0x000003df (0x20) IS[B](OprU)
(==) NV(0): Write-combining range (0xe0000000,0x10000000)
(II) NV(0): Using XFree86 Acceleration Architecture (XAA)
Screen to screen bit blits
Solid filled rectangles
8x8 mono pattern filled rectangles
Indirect CPU to Screen color expansion
Solid Lines
Scanline Image Writes
Offscreen Pixmaps
Setting up tile and stipple cache:
32 128x128 slots
32 256x256 slots
16 512x512 slots
(==) NV(0): Backing store disabled

(==) NV(0): Silken mouse enabled
(**) Option "dpms"
(**) NV(0): DPMS enabled
(==) RandR enabled
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension LBX
(II) Initializing built-in extension XC-APPGROUP
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFIXES
(II) Initializing built-in extension XFree86-Bigfont
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
(II) Initializing built-in extension XEVIE
(EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not found)
(**) Option "CoreKeyboard"
(**) Generic Keyboard: Core Keyboard
(**) Option "Protocol" "standard"
(**) Generic Keyboard: Protocol: standard
(**) Option "AutoRepeat" "500 30"
(**) Option "XkbRules" "xorg"
(**) Generic Keyboard: XkbRules: "xorg"
(**) Option "XkbModel" "abnt2"
(**) Generic Keyboard: XkbModel: "abnt2"
(**) Option "XkbLayout" "br"
(**) Generic Keyboard: XkbLayout: "br"
(**) Option "XkbVariant" "abnt2"
(**) Generic Keyboard: XkbVariant: "abnt2"
(**) Option "CustomKeycodes" "off"
(**) Generic Keyboard: CustomKeycodes disabled
(**) Option "Protocol" "ImPS/2"
(**) Configured Mouse: Device: "/dev/input/mice"
(**) Configured Mouse: Protocol: "ImPS/2"
(**) Option "CorePointer"
(**) Configured Mouse: Core Pointer
(**) Option "Device" "/dev/input/mice"
(**) Option "Emulate3Buttons" "true"
(**) Configured Mouse: Emulate3Buttons, Emulate3Timeout: 50
(**) Option "ZAxisMapping" "4 5"
(**) Configured Mouse: ZAxisMapping: buttons 4 and 5
(**) Configured Mouse: Buttons: 5
(II) XINPUT: Adding extended input device "Configured Mouse" (type: MOUSE)
(II) XINPUT: Adding extended input device "Generic Keyboard" (type: KEYBOARD)
(II) Configured Mouse: ps2EnableDataReporting: succeeded
Warning: font renderer for ".pcf" already registered at priority 0
Warning: font renderer for ".pcf.Z" already registered at priority 0
Warning: font renderer for ".pcf.gz" already registered at priority 0
Warning: font renderer for ".snf" already registered at priority 0
Warning: font renderer for ".snf.Z" already registered at priority 0
Warning: font renderer for ".snf.gz" already registered at priority 0
Warning: font renderer for ".bdf" already registered at priority 0
Warning: font renderer for ".bdf.Z" already registered at priority 0
Warning: font renderer for ".bdf.gz" already registered at priority 0
Warning: font renderer for ".pmf" already registered at priority 0

Ben Stamper
February 19th, 2006, 02:48 PM
I'm about to attempt to recreate the problems I've been having. Ubuntu 5.04 works fine of a Live CD, and xorg.conf uses this code:

Section "Device"
Identifier "NVIDIA Corporation NV34 [GeForce FX 5500]"
Driver "nv"
BusID "PCI:1:0:0"
EndSection

Unfortuneately, X on my normal boot has been giving me this problem:

Fatal Server Error:
Caught signal 11. Server aborting.

The problem only started occuring after I ran the nVidia 8178 installer.
My Video card is an nVidia GeForce FX 5500. I put in the code you suggested, but haven't had the oppurtunity to test it, due to the errors mentioned above.

tseliot
February 19th, 2006, 05:20 PM
BTW: I had to cut some text, because exceeded the post limit.

Can you post also the part you cut?

tseliot
February 19th, 2006, 05:34 PM
I'm about to attempt to recreate the problems I've been having. Ubuntu 5.04 works fine of a Live CD, and xorg.conf uses this code:

Unfortuneately, X on my normal boot has been giving me this problem:

The problem only started occuring after I ran the nVidia 8178 installer.
My Video card is an nVidia GeForce FX 5500. I put in the code you suggested, but haven't had the oppurtunity to test it, due to the errors mentioned above.
Turn on your computer keep pressing ESC until you get to GRUB menu
Select recovery mode
the xserver won't be enabled
type:
nano /etc/X11/xorg.conf
scroll down the file and get to the Section Device
set "vesa" (or "nv") instead of "nvidia" (beside the word "Driver")
CTRL+O to save
CTRL+X to exit

then type:
reboot

Now the xserver should work again.

ruddyadam
February 19th, 2006, 10:17 PM
deleted post

ruddyadam
February 19th, 2006, 10:25 PM
deleted post

ruddyadam
February 19th, 2006, 10:40 PM
TS, sorry for the waste of space in the forum! :-# I didn't read the nvidia-installer error log close enough:

[15272.530979] PCI: No IRQ known for interrupt pin A of device 0000:01:00.0.
Please try using pci=biosirq.
[15272.531002] NVRM: Can't find an IRQ for your NVIDIA card!
[15272.531008] NVRM: Please check your BIOS settings.
[15272.531014] NVRM: [Plug & Play OS] should be set to NO
[15272.531020] NVRM: [Assign IRQ to VGA] should be set to YES

...and I fixed those 2 options in my bios and viola! Nvidia splash screen and all!
thanks again for the awesome guide! I would have been lost without it!

Adam \\:D/

tseliot
February 20th, 2006, 08:49 AM
TS, sorry for the waste of space in the forum! :-# I didn't read the nvidia-installer error log close enough:

[15272.530979] PCI: No IRQ known for interrupt pin A of device 0000:01:00.0.
Please try using pci=biosirq.
[15272.531002] NVRM: Can't find an IRQ for your NVIDIA card!
[15272.531008] NVRM: Please check your BIOS settings.
[15272.531014] NVRM: [Plug & Play OS] should be set to NO
[15272.531020] NVRM: [Assign IRQ to VGA] should be set to YES

...and I fixed those 2 options in my bios and viola! Nvidia splash screen and all!
thanks again for the awesome guide! I would have been lost without it!

Adam \\:D/
I'm glad you solved the problem without my help :)

acorrigan
February 20th, 2006, 12:03 PM
thanks for the help.. sorry i forgot to reply.

anyway I just reinstalled ubuntu all together and started over with installing the drivers. This time the installation didn't fail (I installed gcc-3.4 this time around - needed to update repositories to get access, last time I just continued when I told me it couldn't find 3.4)

I got an error saying that my kernel wasn't available or something when i was in nvidia's installation program and it couldn't find one from nvidia, but i just went ahead and now it's all working great.

Jessevl
February 20th, 2006, 12:59 PM
Which of the methods will work with Ubuntu 6.04 DapperFlight4 and a Nvidia Geforce fx5200?

ruddyadam
February 20th, 2006, 03:21 PM
I'm glad you solved the problem without my help :)

Ok, actually since I used the installer, whenever I booted up, The Xserver crashed, and I got an error when i looked in the log. It was:

Error: API mismatch: the NVIDIA kernel module is version 1.0.7667, but this X module is 1.0.8778
(EE) Nvidia (0): Failed to initialize the Nvidia kernel module!

Ok, so I figure that with the bios options correct, I could do a clean install and everything would be dandy if I did method 1. Not so. I got gdm up, but I checked xorg.conf and it automatically installed the "nv" module. So I made the correct changes per method 1, and Xserver crashed. I changed it back to nv, and it worked again. I figured that I needed to modprobe nvidia, so I did that and I saw it in lsmod, but still Xserver crashed even when I stopped gdm, started it, and startx.

The error I got after the clean install and changed xorg.conf to "method 1" was:
(EE) failed to load module "nvidia" (module does not exist, 0) - I think there was a zero there...maybe not
...but that was because the module wasn't automatically loading, right?

Anyways, Do I need to do the installer for it to work or what do you think? Do you need me to post more code?
Thanks,
Adam

tseliot
February 20th, 2006, 04:19 PM
Which of the methods will work with Ubuntu 6.04 DapperFlight4 and a Nvidia Geforce fx5200?
I suggest you to use Method 1: it will install the latest driver (8178)

tseliot
February 20th, 2006, 04:28 PM
Ok, actually since I used the installer, whenever I booted up, The Xserver crashed, and I got an error when i looked in the log. It was:

Error: API mismatch: the NVIDIA kernel module is version 1.0.7667, but this X module is 1.0.8778
(EE) Nvidia (0): Failed to initialize the Nvidia kernel module!

Ok, so I figure that with the bios options correct, I could do a clean install and everything would be dandy if I did method 1. Not so. I got gdm up, but I checked xorg.conf and it automatically installed the "nv" module. So I made the correct changes per method 1, and Xserver crashed. I changed it back to nv, and it worked again. I figured that I needed to modprobe nvidia, so I did that and I saw it in lsmod, but still Xserver crashed even when I stopped gdm, started it, and startx.

The error I got after the clean install and changed xorg.conf to "method 1" was:
(EE) failed to load module "nvidia" (module does not exist, 0) - I think there was a zero there...maybe not
...but that was because the module wasn't automatically loading, right?

Anyways, Do I need to do the installer for it to work or what do you think? Do you need me to post more code?
Thanks,
Adam
Method 1 and Method 2 mustn't be used together.
Make sure the driver (in your xorg.conf) is set to "nv".

Remove the driver you installed in Method 1:
sudo apt-get --purge remove nvidia-glx nvidia-kernel-common linux-restricted-modules-`uname -r`

Then follow Method 2 again.

Let me know how it goes

myubuntuname
February 21st, 2006, 03:04 AM
Then find the section Device and make sure the word I put in red is “nvidia”:

Code:

Section "Device" Identifier "NVIDIA Corporation NV40 [GeForce 6200 TurboCache]" Driver "nvidia" BusID "PCI:1:0:0"


Code:

CTRL+O to save (yes, use the same name and overwrite the file) CTRL+X to exit

sudo gedit /usr/share/applications/NVIDIA-Settings.desktop
OR (if you use KDE)
sudo kate /usr/share/applications/NVIDIA-Settings.desktop[/code]

Insert the following lines into the new file:
Code:

[Desktop Entry] Name=NVIDIA Settings Comment=NVIDIA Settings Exec=nvidia-settings Icon= Terminal=false Type=Application Categories=Application;System;


Save the edited file.

Log out and press CTRL+ALT+BACKSPACE (so as to restart the xserver).


OK.......After this control-alt-bkspce step.......I got an enormous error saying that my xserver is now configured incorrectly and I'm a n00b and have no idea how to fix what this just did...will you help me please. When I boot up I get 2 errors: One tells me my system is now configured incorrectly and the second one tells me I need to fix it.....then it dumps me at the terminal and I'm lost......Its a damn good thing I have another computer in the house to get back on here to the forums and (hopefully) fix this.......This has been a friggin nightmare.

http://ubuntuforums.org/showthread.php?t=128509
http://ubuntuforums.org/showthread.php?t=133935 (after THIS post I discovered your thread)

volvoguy
February 21st, 2006, 03:57 AM
I don't know if it's the driver or the 5200 FX, but I've set up X to use the binary driver a million times and nothing seems to be working in Dapper right now. Both the driver in the repository and the one from Nvidia's site seem to fail to put the "nvidia.ko" file anywhere. The only thing I see is:

/lib/modules/2.6.15-15-686/kernel/drivers/video/nvidia/nvidiafb.ko

Could something have changed in the kernel or xorg config that's making life difficult? I set this all up on another machine about 3 days ago and it worked fine (with the driver in the repository).

Aaron

tseliot
February 21st, 2006, 04:40 AM
OK.......After this control-alt-bkspce step.......I got an enormous error saying that my xserver is now configured incorrectly and I'm a n00b and have no idea how to fix what this just did...will you help me please. When I boot up I get 2 errors: One tells me my system is now configured incorrectly and the second one tells me I need to fix it.....then it dumps me at the terminal and I'm lost......Its a damn good thing I have another computer in the house to get back on here to the forums and (hopefully) fix this.......This has been a friggin nightmare.

http://ubuntuforums.org/showthread.php?t=128509
http://ubuntuforums.org/showthread.php?t=133935 (after THIS post I discovered your thread)
Turn on your computer and keep pressing ESC until you get to the GRUB menu
You will see a list of all your kernels
Select "Recovery mode"
You won't see anything but the command line.
Type this:
nano /etc/X11/xorg.conf
and set the driver back to "nv" or "vesa" instead of "nvidia"

CTRL+O to save
CTRL+X to exit

Then type:
reboot

And everthing should work again

tseliot
February 21st, 2006, 05:16 AM
I don't know if it's the driver or the 5200 FX, but I've set up X to use the binary driver a million times and nothing seems to be working in Dapper right now. Both the driver in the repository and the one from Nvidia's site seem to fail to put the "nvidia.ko" file anywhere. The only thing I see is:

/lib/modules/2.6.15-15-686/kernel/drivers/video/nvidia/nvidiafb.ko

Could something have changed in the kernel or xorg config that's making life difficult? I set this all up on another machine about 3 days ago and it worked fine (with the driver in the repository).

Aaron
Please don't mix Method 1 with Method 2.

1) Uninstall the driver from Method 2
Log out
Press CTRL+ALT+F1
sudo /etc/init.d/gdm stop
cd path_to_the_nvidia_installer_you_used
sudo sh name_of_the_nvidia_installer_you_used --uninstall

2) Make sure you have the restricted modules installed (just copy and paste this command):
sudo apt-get install linux-restricted-modules-`uname -r`

3) Let's try to reproduce the error.

Set the nvidia driver in your /etc/X11/xorg.conf (or if it's already set leave it as it is.
When GDM (or kdm) crashes at startup Press CTRL+ALT+F1
Then type

Then:
startx -- -verbose 5 -logverbose 5

You will get the same error.

sudo cp /var/log/Xorg.0.log /home/your_username/Xorg.0.log
(Of course you have to replace "your_username" with your username)

and post the content of that file (which you can find under /home/your_username/Xorg.0.log )


BTW if you want to access the GNOME or KDE again you can use this quick fix:
sudo nano /etc/X11/xorg.conf
Set the driver back to "nv" instead of "nvidia"
CTRL+O to save
CTRL+X to exit

sudo /etc/init.d/gdm stop (if you use GDM)
OR
sudo /etc/init.d/kdm stop (if you use KDM)

Then
sudo /etc/init.d/gdm start (if you use GDM)
OR
sudo /etc/init.d/kdm start (if you use KDM)

ruddyadam
February 21st, 2006, 10:40 AM
Method 1 and Method 2 mustn't be used together.
Make sure the driver (in your xorg.conf) is set to "nv".

Remove the driver you installed in Method 1:
sudo apt-get --purge remove nvidia-glx nvidia-kernel-common linux-restricted-modules-`uname -r`

Then follow Method 2 again.

Let me know how it goes

Thanks TS, I must have missed installing something from method 1 - those bios changes were all I really needed to correct, and after doing method 1 again it all seems to be working fine... splash screen and all after reboot.

Thank you much, TS!
Adam

JazzSax
February 21st, 2006, 10:48 AM
Hello TS....

Just finished with your tut. It worked beautifully on my Inspiron 9300/Nvidia 6800 Go. The question I have is when I was looking at my xorg.conf file it had the 'nv' driver in the module section as opposed to the 'nvidia' driver that you said was supposed to be there. I change it to 'nvidia' and x would not start. Changed it back to 'nv' and it works. Also after the install (with no errors by the way) it installed NVIDIA X Server Settings under System Tool.(That would tell me that the install was ok...???) Anywho just curious....BTW using Dapper and Nvidia 8178



Erik

Master Shake
February 21st, 2006, 10:50 AM
Did it last night, when I installed Linux on a friend's machine..

Works very well,!

PsTJsT
February 21st, 2006, 12:45 PM
Then restart your computer and your connection should be back.
If everything works fine then I'll give you further instructions

Okay, my system is up and running again. FWIW, I ran into several problems after I reinstalled the restricted modules, so I tried to "self-diagnose" based on other people's problems and solutions and completely hosed my system. I've now reinstalled Breezy.

So, now I'd like to use Method 2 to install the latest nVidia drivers, but I obviously don't want to recreate the problems/issues related to my need for the restricted modules due to my use of the madwifi driver. Is it possible to modify Method 2 (or do something after Method 2 is complete) to avoid the loss of my wireless device?

Thanks again.

tseliot
February 21st, 2006, 01:05 PM
Hello TS....

Just finished with your tut. It worked beautifully on my Inspiron 9300/Nvidia 6800 Go. The question I have is when I was looking at my xorg.conf file it had the 'nv' driver in the module section as opposed to the 'nvidia' driver that you said was supposed to be there. I change it to 'nvidia' and x would not start. Changed it back to 'nv' and it works.
If you use "nv" (the open source driver) you don't use "nvidia" (the proprietary driver my guide is about).

Also after the install (with no errors by the way) it installed NVIDIA X Server Settings under System Tool.(That would tell me that the install was ok...???) Anywho just curious....BTW using Dapper and Nvidia 8178
Did you use Method 1 or Method 2?

Dapper has nvidia 8178 in the repos, therefore Method 1 is warmly recommended

tseliot
February 21st, 2006, 01:07 PM
Did it last night, when I installed Linux on a friend's machine..

Works very well,!
It's good to "hear" that :)

tseliot
February 21st, 2006, 01:27 PM
Okay, my system is up and running again. FWIW, I ran into several problems after I reinstalled the restricted modules, so I tried to "self-diagnose" based on other people's problems and solutions and completely hosed my system. I've now reinstalled Breezy.

So, now I'd like to use Method 2 to install the latest nVidia drivers, but I obviously don't want to recreate the problems/issues related to my need for the restricted modules due to my use of the madwifi driver. Is it possible to modify Method 2 (or do something after Method 2 is complete) to avoid the loss of my wireless device?

Thanks again.
You can follow this guide to compile your madwifi modules (so that you won't need the restricted-modules):
http://ubuntuforums.org/showthread.php?t=75451

Jessevl
February 21st, 2006, 05:07 PM
It seems i can't install nvidia-glx and nvidia-settings together, I can apt-get glx but when i apt-get nvidia-settings, it will uninstall nvidia-glx, and the other way around. btw, I'm using dapperflight4

PsTJsT
February 21st, 2006, 05:27 PM
You can follow this guide to compile your madwifi modules (so that you won't need the restricted-modules):
http://ubuntuforums.org/showthread.php?t=75451
All done... Madwifi and newest nVidia drivers peacefully coexisting! Thanks again for the tutorial and your help.

mschievano
February 21st, 2006, 06:08 PM
me too!
My new kernel (2.6.15-16-k7) disabled the nvidia functionality. The glx packages wants the restricted modules from 2.6.15.14-386 but i don't need them!


mschievano@uainex:~$ sudo apt-get install nvidia-glx
Password:
Lettura della lista dei pacchetti in corso... Fatto
Generazione dell'albero delle dipendenze in corso... Fatto
I seguenti pacchetti verranno inoltre installati:
linux-restricted-modules-2.6.15-14-386
Pacchetti suggeriti:
avm-fritz-firmware-2.6.15-14
I seguenti pacchetti saranno RIMOSSI:
nvidia-settings
I seguenti pacchetti NUOVI (NEW) saranno installati:
linux-restricted-modules-2.6.15-14-386 nvidia-glx
0 aggiornati, 2 installati, 1 da rimuovere e 1 non aggiornati.
È necessario prendere 0B/11,6MB di archivi.
Dopo l'estrazione, verranno occupati 32,2MB di spazio su disco.
Continuare [S/n]?


So now i run linux whit the nv driver. The restricted driver for my kernel doesn't exist :-k

mschievano@uainex:~$ sudo apt-get install linux-restricted-modules-`uname -r` Lettura della lista dei pacchetti in corso... Fatto
Generazione dell'albero delle dipendenze in corso... Fatto
E: Impossibile trovare linux-restricted-modules-2.6.15-16-k7
mschievano@uainex:~$

kayrune
February 21st, 2006, 06:15 PM
It seems i can't install nvidia-glx and nvidia-settings together, I can apt-get glx but when i apt-get nvidia-settings, it will uninstall nvidia-glx, and the other way around. btw, I'm using dapperflight4

I have the same problem, also I'm converting from gentoo, and the nvidia driver seems very slow, slow on redraw of screen and windows and scrolling.

XGL works fine though, but

# glxinfo |grep direct
Gives me :(
direct rendering: No

FuriousLettuce
February 21st, 2006, 07:14 PM
I can't believe how more efficient the new drivers than the old! Thanks for the guide, am eternally grateful! Windows and scrolling is just much better.

Now I just got to get openAL working in UT2k4...

SuTuRa
February 21st, 2006, 07:20 PM
I just followed your method 2 and the driver is installed but when I try to boot with it, it doesn't start GDM. Looking at the log file it says that the error is being caused by my nvidia-kernel being version 7667 and my drivers are 8178. Thanks tseliot for all your effort helping people

EDIT: Forget it... Everything is solved:) And tseliot you really da man

mschievano
February 22nd, 2006, 03:11 AM
me too!
My new kernel (2.6.15-16-k7) disabled the nvidia functionality. The glx packages wants the restricted modules from 2.6.15.14-386 but i don't need them!


mschievano@uainex:~$ sudo apt-get install nvidia-glx
Password:
Lettura della lista dei pacchetti in corso... Fatto
Generazione dell'albero delle dipendenze in corso... Fatto
I seguenti pacchetti verranno inoltre installati:
linux-restricted-modules-2.6.15-14-386
Pacchetti suggeriti:
avm-fritz-firmware-2.6.15-14
I seguenti pacchetti saranno RIMOSSI:
nvidia-settings
I seguenti pacchetti NUOVI (NEW) saranno installati:
linux-restricted-modules-2.6.15-14-386 nvidia-glx
0 aggiornati, 2 installati, 1 da rimuovere e 1 non aggiornati.
È necessario prendere 0B/11,6MB di archivi.
Dopo l'estrazione, verranno occupati 32,2MB di spazio su disco.
Continuare [S/n]?


So now i run linux whit the nv driver. The restricted driver for my kernel doesn't exist :-k

mschievano@uainex:~$ sudo apt-get install linux-restricted-modules-`uname -r` Lettura della lista dei pacchetti in corso... Fatto
Generazione dell'albero delle dipendenze in corso... Fatto
E: Impossibile trovare linux-restricted-modules-2.6.15-16-k7
mschievano@uainex:~$


still have the problem. I think it depend's on the missing linux-restricted-modules-2.6.15-16-k7

tseliot
February 22nd, 2006, 04:38 AM
It seems i can't install nvidia-glx and nvidia-settings together, I can apt-get glx but when i apt-get nvidia-settings, it will uninstall nvidia-glx, and the other way around. btw, I'm using dapperflight4
Ok, perhaps there's a mismatch (a dependency problem) between the 2 packages.

Install only nvidia-glx, (nvidia settings is not fundamental)

tseliot
February 22nd, 2006, 04:40 AM
me too!
My new kernel (2.6.15-16-k7) disabled the nvidia functionality. The glx packages wants the restricted modules from 2.6.15.14-386 but i don't need them!


mschievano@uainex:~$ sudo apt-get install nvidia-glx
Password:
Lettura della lista dei pacchetti in corso... Fatto
Generazione dell'albero delle dipendenze in corso... Fatto
I seguenti pacchetti verranno inoltre installati:
linux-restricted-modules-2.6.15-14-386
Pacchetti suggeriti:
avm-fritz-firmware-2.6.15-14
I seguenti pacchetti saranno RIMOSSI:
nvidia-settings
I seguenti pacchetti NUOVI (NEW) saranno installati:
linux-restricted-modules-2.6.15-14-386 nvidia-glx
0 aggiornati, 2 installati, 1 da rimuovere e 1 non aggiornati.
È necessario prendere 0B/11,6MB di archivi.
Dopo l'estrazione, verranno occupati 32,2MB di spazio su disco.
Continuare [S/n]?


So now i run linux whit the nv driver. The restricted driver for my kernel doesn't exist :-k

mschievano@uainex:~$ sudo apt-get install linux-restricted-modules-`uname -r` Lettura della lista dei pacchetti in corso... Fatto
Generazione dell'albero delle dipendenze in corso... Fatto
E: Impossibile trovare linux-restricted-modules-2.6.15-16-k7
mschievano@uainex:~$

As Dapper is under development it's likely that they haven't uploaded the restricted modules for your kernel yet. You should wait them to upload the right package.

Remeber that Dapper in unstable (ok, it's pretty stable for being an alpha)

missmoondog
February 22nd, 2006, 08:37 AM
holy cow!! FINALLY got this stupid computer setup to use my nvidia vanta/vanta drivers using this guide. i have gone through it before, but it just didn't work. must be since the last linux-image update and now going through this got it together.

now, can you tell me how to get rid of one of the "nvidia settings" items in applications/system tools section. i removed it through synaptic and rebooted, but i still have 2 in there.

btw,
i used method 1. i had changed the "nv" to "nvidia" and back at least twice before, but whatever i did different this time worked!

great job :)

THANK YOU!!

gg234
February 22nd, 2006, 08:55 AM
i just followed these and it worked like charm

Nvidia drivers installation in ubuntu and debian (http://www.debianhelp.co.uk/nvidia.htm)

JazzSax
February 22nd, 2006, 09:53 AM
If you use "nv" (the open source driver) you don't use "nvidia" (the proprietary driver my guide is about).


Did you use Method 1 or Method 2?

Dapper has nvidia 8178 in the repos, therefore Method 1 is warmly recommended


Hello, TS

To answer your questions, I used method 2. The install with the nvidia driver (from their site) went flawless, but after the install I noticed the 'nv' driver was the one being used as opposed to the 'nvidia' driver. If the install did not give errors, why would it still be using 'nv'....?? Also should I attempt Method 1? What would I need to remove to try this? What would change in the tut with Dapper? Thanks again for your knowledge and time :D

Erik

JazzSax
February 22nd, 2006, 10:51 AM
Hello,

tried to install using Method 1 and recieved this error on first step:

erik@ubuntu:~$ sudo apt-get install nvidia-glx nvidia-settings linux-restricted-modules-`uname -r`
Password:
Reading package lists... Done
Building dependency tree... Done
nvidia-settings is already the newest version.
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies.
nvidia-glx: Conflicts: nvidia-settings but 1.0-3ubuntu7 is to be installed
E: Broken packages
erik@ubuntu:~$ sudo apt-get install nvidia-glx nvidia-settings linux-restricted-modules-`uname -r`
Reading package lists... Done
Building dependency tree... Done
nvidia-settings is already the newest version.
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies.
nvidia-glx: Conflicts: nvidia-settings but 1.0-3ubuntu7 is to be installed
E: Broken packages
erik@ubuntu:~$


Any thoughts???

kayrune
February 22nd, 2006, 01:11 PM
jaxxsax,


use this

sudo apt-get install nvidia-glx linux-restricted-modules-`uname -r`

tseliot
February 22nd, 2006, 01:48 PM
now, can you tell me how to get rid of one of the "nvidia settings" items in applications/system tools section. i removed it through synaptic and rebooted, but i still have 2 in there.

remove them from the Menu editor

tseliot
February 22nd, 2006, 01:50 PM
i just followed these and it worked like charm

Nvidia drivers installation in ubuntu and debian (http://www.debianhelp.co.uk/nvidia.htm)
Ubuntu is NOT Debian.

DO NOT add those repositories to your sources.list or you might have dependency problems.

tseliot
February 22nd, 2006, 01:54 PM
Hello, TS

To answer your questions, I used method 2. The install with the nvidia driver (from their site) went flawless, but after the install I noticed the 'nv' driver was the one being used as opposed to the 'nvidia' driver. If the install did not give errors, why would it still be using 'nv'....?? Also should I attempt Method 1? What would I need to remove to try this? What would change in the tut with Dapper? Thanks again for your knowledge and time :D

Erik
To remove the driver from method 2 (otherwise you might have a driver mismatch):
CTRL+ALT+F1
sudo /etc/init.d/gdm stop (or "kdm stop" if you use KDM)

cd path_to_the_nvidia_installer
sudo sh name_of_the_nvidia_installer --uninstall

sudo /etc/init.d/gdm start (or "kdm start" if you use KDM)

tseliot
February 22nd, 2006, 01:55 PM
jaxxsax,


use this

sudo apt-get install nvidia-glx linux-restricted-modules-`uname -r`
That's right, it's a dependency problem. If you do not install nvidia-settings you won't have that problem

kayrune
February 22nd, 2006, 03:30 PM
Can anyone tell me if this is correct ?

#glxinfo |grep direct
direct rendering: No

?? Is anyone else getting this?

the problem is XGL, XGL seems to break direct rendering. If I start X without XGL, then I have direct rendering: yes

The reason I'm concerned is that I changed from gentoo to ubuntu, and the display seems slower in ubuntu. CPU usage takes quite a hit moving windows in XGL, can't see I noticed that on gentoo.

#cat /proc/driver/nvidia/agp/status
Status: Enabled
Driver: NVIDIA
AGP Rate: 4x
Fast Writes: Disabled
SBA: Disabled

mschievano
February 22nd, 2006, 03:46 PM
finally:


I seguenti pacchetti NUOVI (NEW) saranno installati:
linux-restricted-modules-2.6.15-14-386 linux-restricted-modules-2.6.15-16-k7
nvidia-glx


the restricted modules appear...

and the nvidia driver return to perform! \\:D/

tseliot
February 22nd, 2006, 04:51 PM
Can anyone tell me if this is correct ?

#glxinfo |grep direct
direct rendering: No

?? Is anyone else getting this?

the problem is XGL, XGL seems to break direct rendering. If I start X without XGL, then I have direct rendering: yes

The reason I'm concerned is that I changed from gentoo to ubuntu, and the display seems slower in ubuntu. CPU usage takes quite a hit moving windows in XGL, can't see I noticed that on gentoo.

#cat /proc/driver/nvidia/agp/status
Status: Enabled
Driver: NVIDIA
AGP Rate: 4x
Fast Writes: Disabled
SBA: Disabled
Sorry but I've never tried XGL. :(

Jose Monteiro
February 22nd, 2006, 05:59 PM
Sorry for being absent these days...The prob is in my home computer and I have come late from work :(
You have asked me to paste the part of the Xorg.0.log I have cutted (see message 1033 in this thread). BTW: There is a phrase which have called my attention (in the previous message too) (EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not found). But see down the initial part of the file I've cutted:

X Window System Version 6.8.2 (Ubuntu 6.8.2-77 20051010174523 root@vernadsky.buildd)
Release Date: 9 February 2005
X Protocol Version 11, Revision 0, Release 6.8.2
Build Operating System: Linux 2.6.10 i686 [ELF]
Current Operating System: Linux SirFire 2.6.12-9-386 #1 Mon Oct 10 13:14:36 BST 2005 i686
Build Date: 10 October 2005
Before reporting problems, check http://wiki.X.Org
to make sure that you have the latest version.
Module Loader present
OS Kernel: Linux version 2.6.12-9-386 (buildd@rothera) (gcc version 3.4.5 20050809 (prerelease) (Ubuntu 3.4.4-6ubuntu8)) #1 Mon Oct 10 13:14:36 BST 2005 T
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Wed Feb 22 16:21:55 2006
(==) Using config file: "/etc/X11/xorg.conf"
(==) ServerLayout "Default Layout"
(**) |-->Screen "Default Screen" (0)
(**) | |-->Monitor "Generic Monitor"
(**) | |-->Device "NVIDIA Corporation NV34 [GeForce FX 5200]"
(**) |-->Input Device "Generic Keyboard"
(**) |-->Input Device "Configured Mouse"
(WW) The directory "/usr/share/X11/fonts/cyrillic" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/share/X11/fonts/CID" does not exist.
Entry deleted from font path.
(WW) `fonts.dir' not found (or not valid) in "/var/lib/defoma/x-ttcidfont-conf.d/dirs/CID".
Entry deleted from font path.
(Run 'mkfontdir' on "/var/lib/defoma/x-ttcidfont-conf.d/dirs/CID").
(**) FontPath set to "/usr/share/X11/fonts/misc,/usr/share/X11/fonts/100dpi/:unscaled,/usr/share/X11/fonts/75dpi/:unscaled,/usr/share/X11/fonts