Fwd: [Bug 469470] Re: proprietary nvidia driver does not work under karmic
Leonard Chatagnier
lenc5570 at sbcglobal.net
Wed Nov 18 05:59:56 UTC 2009
NoOp wrote:
> On 11/16/2009 11:31 PM, Leonard wrote:
>
>> NoOp wrote:
>>
> Snipped to clean up irrevelant info.
>> 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)
>
Read through most of first 40 messages. Saw no fixes but saw that there
are a lot of bugs on the MTRR
error.
>> 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.
>
I have no /dev/fb0. one report said to create one but not knowing how
Hal works I hesitate to use MAKEDEV -d /dev/fb0
Another had something to add to Hal, .fdi., which I didn't understand
but can't find the link again, sorry.
>> (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
>
Yes.
lchata at karmic-desktop:/dev/.udev$ lsmod |grep nv
nvidia 10316904 30
lchata at karmic-desktop:/dev/.udev$ modinfo nvidia
filename: /lib/modules/2.6.31-15-generic/updates/dkms/nvidia.ko
license: NVIDIA
alias: char-major-195-*
alias: pci:v000010DEd*sv*sd*bc03sc02i00*
alias: pci:v000010DEd*sv*sd*bc03sc00i00*
depends:
vermagic: 2.6.31-15-generic SMP mod_unload modversions
parm: NVreg_EnableVia4x:int
parm: NVreg_EnableALiAGP:int
parm: NVreg_ReqAGPRate:int
parm: NVreg_EnableAGPSBA:int
parm: NVreg_EnableAGPFW:int
parm: NVreg_Mobile:int
parm: NVreg_ResmanDebugLevel:int
parm: NVreg_RmLogonRC:int
parm: NVreg_ModifyDeviceFiles:int
parm: NVreg_DeviceFileUID:int
parm: NVreg_DeviceFileGID:int
parm: NVreg_DeviceFileMode:int
parm: NVreg_RemapLimit:int
parm: NVreg_UpdateMemoryTypes:int
parm: NVreg_UseVBios:int
parm: NVreg_RMEdgeIntrCheck:int
parm: NVreg_UsePageAttributeTable:int
parm: NVreg_EnableMSI:int
parm: NVreg_MapRegistersEarly:int
parm: NVreg_RmNvclkIdleGraphics:int
parm: NVreg_RegistryDwords:charp
parm: NVreg_NvAGP:int
> 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>
>
>
I just read several of the links and can't even remember what they
said. Time for me to stop for awhile. Not finding any solutions, that
I understand, anyway.
>> 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?
>
>
Yes, cat /tmp/.X0-lock says 1814
>> 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>
> ...
>
I see this thread; no solutions
>>> 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.
>
Going to do that assuming I don't forget.
>
>> 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.
>
Dugh, I never have added one manually but maybe running some nvidia
command did.
Every time I've looked in /etc/X11 in Karmic, I see one of the new,
useless default type.
>
>>
>>>> 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.
>
It was a typo and nvidia-xconfig put one it that apparently is still
working but occasionally still have to drop to a console and wait a few
seconds.
As you mentioned, I think it;s a timeing thing but I haven't a clue on
what to do about it.
> ...
>
>
>
More information about the ubuntu-users
mailing list