** Tags added: valid-xorg-conf
--
latest xorg / nvidia-glx-new /linux-restricted-modules breaks xserver
https://bugs.launchpad.net/bugs/151213
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Just another 'me too'. In my case, none of the posted fixes worked, so I
resolved it by installing Alberto Milone's Envy (
http://albertomilone.com/nvidia_scripts1.html ) and letting it install a
newer nVidia driver.
nVidia 6200 TC, latest Gutsy.
Cheers.
--
latest xorg / nvidia-glx-new
The original reporter said that the issue is fixed for him, and someone
pointed out that a newer upstream version worked, so I'm closing this as
fixed (in Hardy at least).
** Changed in: linux-restricted-modules-2.6.22 (Ubuntu)
Status: New = Fix Released
--
latest xorg / nvidia-glx-new
Here is the solution:
#157773
--
latest xorg / nvidia-glx-new /linux-restricted-modules breaks xserver
https://bugs.launchpad.net/bugs/151213
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Sorry, correct link:
Bug #157773
--
latest xorg / nvidia-glx-new /linux-restricted-modules breaks xserver
https://bugs.launchpad.net/bugs/151213
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Alex's comment above is how I worked around the problem as well. It
seems that what's happening is the X server is loading the older 9xxx
version of the kernel module and trying while trying to use the newer
100.14.19 X driver. Updating that file solved the issue for me and
forced it to load the
(sorry to multi-post but I didn't find the way to add more then one file
at a time)
This attachement is the file generated by :
strace X :2 strace.log 21
A few more information :
[EMAIL PROTECTED]:~# lsmod|grep nvidia
nvidia 6218832 0
i2c_core 25104 2
Hi,
I'm new to this one but the topic seems realy related to my problem.
My xorg crash when trying to start.
** Attachment added: xorg.conf
http://launchpadlibrarian.net/10076330/xorg.conf
--
latest xorg / nvidia-glx-new /linux-restricted-modules breaks xserver
oups, I forgot.
the debian mailing list point out to this :
http://www.nvnews.net/vbulletin/showthread.php?s=7858bb6d26391d3abf310c8788143778t=99016
(it's about disabling the composite extention)
which look related, but it didn't help me much.
--
latest xorg / nvidia-glx-new
my Xorg logfile is quiete funny too just have a look at the end
** Attachment added: Xorg.2.log
http://launchpadlibrarian.net/10076331/Xorg.2.log
--
latest xorg / nvidia-glx-new /linux-restricted-modules breaks xserver
https://bugs.launchpad.net/bugs/151213
You received this bug notification
Confirm still broken.
I can start X successfully if I put
DISABLED_MODULES=nvidia_legacy nvidia in /etc/default/linux_restricted_modules
and restart the machine.
--
latest xorg / nvidia-glx-new /linux-restricted-modules breaks xserver
https://bugs.launchpad.net/bugs/151213
You received this
On Tue, 2007-10-16 at 22:20 +, Ryan McClure wrote:
I tried dmesg | grep -nv and found this:
[13.044000] nvidia: module license 'NVIDIA' taints kernel
That doesn't sound good.
that's just a standard warning about the nonfree license under which
nvidia modules are distributed. nothing
Matt: Ah, okay.
Alex: Did you try the two commands I mentioned in my previous comment?
It looks like you're doing something functionally similar, but without
forcibly removing the problem components.
It seems that the core of the problem is that nvidia_new is not
overriding nvidia_legacy or
No, although I'm now getting a different error message in Xorg.0.log.
Also, using nv doesn't work -- all I get is a black screen. I can't
switch to a console, though I can reboot with ctrl-alt-delete.
New error from Xorg.0.log. Full log attached.
(EE) NVIDIA(0): Failed to initialize the
Sorry, correction -- there is no difference for me at this juncture.
The error messages are the same as before.
--
latest xorg / nvidia-glx-new /linux-restricted-modules breaks xserver
https://bugs.launchpad.net/bugs/151213
You received this bug notification because you are a member of Ubuntu
I tried dmesg | grep -nv and found this:
[13.044000] nvidia: module license 'NVIDIA' taints kernel
That doesn't sound good.
I also tried the advice from http://forum.ubuntu-
fr.org/viewtopic.php?id=154950, but to no avail.
The most damning indicator continues to be the Xorg error (that weirdly
Okay, I fixed it -- once.
The problem appears to have been that the nvidia.ko and nvidia_legacy.ko
module files were still hanging around. I discovered this by using
modprobe -l nv*
I deleted them forcibly, leaving only the nvidia_new.ko. Starting X (I
was in a terminal) immediately presented
Sorry for the rapid-fire comment spam.
I have, I think, fixed it. The fix required forcibly deleting the
.mod.o files, rather than the .ko files. The commands I used were:
sudo rm -r /lib/linux-restricted-modules/2.6.22-14-generic/nvidia
sudo rm -r
On Sun, 2007-10-14 at 06:11 +, Ryan McClure wrote:
Matt,
Previously, sudo modprobe nvidia resulted in an error, as you say.
However, I just tried it just now and got no reaction (other than a
return to the prompt). This has not changed the status of the issue,
though, as switching to
Another confirmation. I also couldn't get the drivers working with
manual installation of the drivers off nvidia's website.
This issue only started for me after upgrading to the latest kernel, on
a test install based on the beta release.
In the previous kernel (2.6.22-14.43 restricted
Matt,
Previously, sudo modprobe nvidia resulted in an error, as you say.
However, I just tried it just now and got no reaction (other than a
return to the prompt). This has not changed the status of the issue,
though, as switching to nvidia still yields an error. Vesa continues to
function.
attaching my xorg.conf
** Attachment added: xorg.conf-nvidia-working-20070921
http://launchpadlibrarian.net/9926775/xorg.conf-nvidia-working-20070921
--
latest xorg / nvidia-glx-new /linux-restricted-modules breaks xserver
https://bugs.launchpad.net/bugs/151213
You received this bug
disabling failsafe mode in gdm.conf allowed me to capture my xorg error:
FATAL: Could not open /lib/modules/2.6.22-14-generic/volatile/nvidia.ko
and in fact, this module is missing.
not sure whether this is suppposed to belong to linux-restricted-modules
or nvidia-glx-new, or whether maybe xorg
Confirming this problem, too -- I think. Any time I attempt to enable
nvidia as the driver, it is rejected and I am dropped back to vesa.
--
latest xorg / nvidia-glx-new /linux-restricted-modules breaks xserver
https://bugs.launchpad.net/bugs/151213
You received this bug notification because
ryan, can you sudo modprobe nvidia? i get an uninformative failure
notice when i try that.
also, what's your hardware? i'm working with a dell latitude d820,
graphics card is nvidia geforce go 7400.
package versions are as follows:
xserver-xorg:
Installed: 1:7.2-5ubuntu13
nvidia-glx-new:
25 matches
Mail list logo
