Fwd: [Bug 469470] Re: proprietary nvidia driver does not work under karmic

[NoOp]

On 11/16/2009 11:31 PM, Leonard wrote:
> NoOp wrote:
...
> Well, I don't think you want to look at all related things in my 
> logs-:o) but I'll list a few that may confirm your race condition 
> theory. BTW, I think so too.  Anyway:
> xorg.0.log shows
> (==) ModulePath set to "/usr/lib/xorg/modules"
> (WW) AllowEmptyInput is on, devices using drivers 'kbd', 'mouse' or 
> 'vmmouse' will be disabled.
> (WW) Disabling Keyboard0
> (WW) Disabling Mouse0
> But later on toward the end they are initialized.

Not to worry; those are listed in the logs for *all* my machines.

> 
> after an entry saying configuring hal and a few lines later it shows
> (II) AT Translated Set 2 keyboard: Device reopened after 1 attempts.
> (II) Power Button: Device reopened after 1 attempts.
> (II) Power Button: Device reopened after 1 attempts.
> (II) Macintosh mouse button emulation: Device reopened after 1 attempts.
> (II) USB Optical Mouse: Device reopened after 1 attempts.
> These are the last 5 lines in the log.
> kdm.log shows
> first line
> error setting MTRR (base = 0xe0000000, size = 0x10000000, type = 1) 
Google/launchpad that one.
(https://launchpad.net/+search?field.text=error+setting+MTRR)
> Invalid argument (22)
>   ddxSigGiveUp: Closing log
> This shows up and repeated multiple times:
> (EE) open /dev/fb0: No such file or directory
Google/launchpad that one.
> (EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not 
> found)

Sounds like it hasn't been loaded. Do you show it with:

$ lsmod |grep nv
$ modinfo nvidia

Also see:
<http://www.google.com/webhp?complete=0#complete=0&hl=en&q=ubuntu+%2B"Failed+to+initialize+GLX+extension+(Compatible+NVIDIA+X+driver+not+%0Afound)"&fp=a79ec0e3c59ba40a>

> error setting MTRR (base = 0xe0000000, size = 0x10000000, type = 1) 
> Invalid argument (22)
>   ddxSigGiveUp: Closing log
> 
> Fatal server error:
> Server is already active for display 0
>          If this server is no longer running, remove /tmp/.X0-lock
>          and start again.

Do you have a '/tmp/.X0-lock' file?
...
> syslog had:
> Nov 16 22:43:41 karmic-desktop kdm[1653]: X server died during startup
> Nov 16 22:43:41 karmic-desktop kdm[1653]: Failed to start X server. 
> Starting failsafe X server.
> Repeated at least once but didn't scroll through the whole file.
> Messaged had:
> Nov 16 22:43:26 karmic-desktop kernel: [   13.252180] usplash:361 
> freeing invalid memtype fffffffff9000000-fffffffff9e00000
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Google again:
<http://www.google.com/webhp?complete=0#complete=0&hl=en&q=ubuntu+%2B"freeing+invalid+memtype+fffffffff9000000-fffffffff9e00000"&fp=a79ec0e3c59ba40a>
...
>>
>> Turn off the monitor w/autologin and test. Takes about 5 minutes to do.
>> My point here is that some other bugs, similar to yours, indicated
>> issues with digital cable connections. Doesn't take a genious to set
>> autologin&  reboot with the monitor off :-)
>>
> Got auto login set up and rebooted with monitor on which caused startup 
> X errors for first boot in about 6 times.  Will now try without monitor 
> being on.  Wait, wait; must save draft, must save draft. With monitor 
> off first reboot gave a highpitched rapid beeping noise; a warning 
> right?  On second reboot with monitor off the beeping didn't stop and in 
> both cases I had a black screen with a blinking cursor and only the 
> magic blue button held down for several long seconds would shut it down.

Sounds like a bios and/or hardware issue. Check your bios & turn off
warn to beep on missing keyboard/monitor.

> Rebooting with monitor on went through auto login to kde without issue.
> Seems like my new xorg.conf is still working-:o)

Sounds like you have a seriously messed up system. Karmic should boot
just fine without a monitor attached or no xorg.config[1]; albeit it
will be default of 800x600, but shouldn't get a black screen.

[1] Remember that karmic doesn't even use an xorg.conf by default. It
only uses it if you put one there.

> 
>>> I rmed xorg.conf and got the message shown on the bug report but can't
>>> remember whether it was on the first reboot or not.  Anyway,
>>> nvidia-setting wouldn't work

It's 'nvidia-settings' - notice the 's'. But even if that was a typo,
nvidia-settings won't work if the nvidia module(s) haven't been loaded
at boot.
...