I had the same issue. I used Greg Lund-Chaix's suggestion and it seems
to have resolved it.
--
package python-xml 0.8.4-10.1ubuntu2 failed to install/upgrade:
https://bugs.launchpad.net/bugs/367955
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
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 you
Yep, it's working now. I did a search for the file after updating and
was very excited to find it. Rebooting activated it and everything is
once again functioning as expected.
Thanks!
--
[Gutsy] Upgrade to 2.6.22-12 causes iwl3945 to stop functioning
https://bugs.launchpad.net/bugs/144252
You
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.
I'm
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 NVID
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
Bug
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 /lib/linux-restricted-modules/2.6.22-14-generi
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 nvidi
Public bug reported:
I have a ThinkPad T61 running Gutsy.
Since upgrading to the 2.6.22-12 kernel in yesterday's batch of updates,
I have been unable to use either the nVidia drivers or the iwlwifi
drivers. The nVidia drivers appear to have a kernel mismatch, while the
iwlwifi drivers for the 39
It looks like the update to the nVidia drivers was just released, so
that's now working on 2.6.22-12.
However, the iwlwifi/3945 issue is still present. I'm not even sure
where to begin looking to address this.
** Summary changed:
- [Gutsy] 2.6.22-12 does not recognize nVidia or iwlwifi drivers
K8BeBop:
This sounds like a different problem. My problem with the nVidia drivers was
just a kernel version mismatch; I could see as much in the system logs.
Probably worth opening a new bug for your specific issue.
I'm a total newb to Ubuntu and linux in general (but enough of a
computer ner
Specified the suspected package to which this bug pertains.
** Changed in: linux-ubuntu-modules-2.6.22 (Ubuntu)
Sourcepackagename: None => linux-ubuntu-modules-2.6.22
--
[Gutsy] Upgrade to 2.6.22-12 causes iwl3945 to stop functioning
https://bugs.launchpad.net/bugs/144252
You received this bug n
Affirming error, just did an update.
--
[apport] NetworkManager crashed with signal 5 in main()
https://bugs.launchpad.net/bugs/85113
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ub
Are you getting any debug info from the various system logs?
--
Upgrade to 2.6.22.12 - NVidia driver does not work
https://bugs.launchpad.net/bugs/144551
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Public bug reported:
I'm using a Thinkpad T61 with Gusty fully up to date. My T61 has the
Intel 3945 integrated wireless chip, and is using the IWL3945 drivers.
In general, the drivers work as expected. However, if ever the wireless
connection drops for whatever reason (signal strength too low,
Public bug reported:
I have a ThinkPad T61 running Gutsy.
Since upgrading to the 2.6.22-12 kernel in yesterday's batch of updates,
I have been unable to use either the nVidia drivers or the iwlwifi
drivers. The nVidia drivers appear to have a kernel mismatch, while the
iwlwifi drivers for the 39
It looks like the update to the nVidia drivers was just released, so
that's now working on 2.6.22-12.
However, the iwlwifi/3945 issue is still present. I'm not even sure
where to begin looking to address this.
** Summary changed:
- [Gutsy] 2.6.22-12 does not recognize nVidia or iwlwifi drivers
K8BeBop:
This sounds like a different problem. My problem with the nVidia drivers was
just a kernel version mismatch; I could see as much in the system logs.
Probably worth opening a new bug for your specific issue.
I'm a total newb to Ubuntu and linux in general (but enough of a
computer ner
Specified the suspected package to which this bug pertains.
** Changed in: linux-ubuntu-modules-2.6.22 (Ubuntu)
Sourcepackagename: None => linux-ubuntu-modules-2.6.22
--
[Gutsy] Upgrade to 2.6.22-12 causes iwl3945 to stop functioning
https://bugs.launchpad.net/bugs/144252
You received this bug n
Affirming error, just did an update.
--
[apport] NetworkManager crashed with signal 5 in main()
https://bugs.launchpad.net/bugs/85113
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ub
Are you getting any debug info from the various system logs?
--
Upgrade to 2.6.22.12 - NVidia driver does not work
https://bugs.launchpad.net/bugs/144551
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Yep, it's working now. I did a search for the file after updating and
was very excited to find it. Rebooting activated it and everything is
once again functioning as expected.
Thanks!
--
[Gutsy] Upgrade to 2.6.22-12 causes iwl3945 to stop functioning
https://bugs.launchpad.net/bugs/144252
You
Public bug reported:
I'm using a Thinkpad T61 with Gusty fully up to date. My T61 has the
Intel 3945 integrated wireless chip, and is using the IWL3945 drivers.
In general, the drivers work as expected. However, if ever the wireless
connection drops for whatever reason (signal strength too low,
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.
I'm
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 NVID
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
Bug
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 /lib/linux-restricted-modules/2.6.22-14-generi
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 nvidi
I had the same issue. I used Greg Lund-Chaix's suggestion and it seems
to have resolved it.
--
package python-xml 0.8.4-10.1ubuntu2 failed to install/upgrade:
https://bugs.launchpad.net/bugs/367955
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
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 you
I had the same issue. I used Greg Lund-Chaix's suggestion and it seems
to have resolved it.
--
package python-xml 0.8.4-10.1ubuntu2 failed to install/upgrade:
https://bugs.launchpad.net/bugs/367955
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
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 you
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.
I'm
Public bug reported:
I have a ThinkPad T61 running Gutsy.
Since upgrading to the 2.6.22-12 kernel in yesterday's batch of updates,
I have been unable to use either the nVidia drivers or the iwlwifi
drivers. The nVidia drivers appear to have a kernel mismatch, while the
iwlwifi drivers for the 39
It looks like the update to the nVidia drivers was just released, so
that's now working on 2.6.22-12.
However, the iwlwifi/3945 issue is still present. I'm not even sure
where to begin looking to address this.
** Summary changed:
- [Gutsy] 2.6.22-12 does not recognize nVidia or iwlwifi drivers
K8BeBop:
This sounds like a different problem. My problem with the nVidia drivers was
just a kernel version mismatch; I could see as much in the system logs.
Probably worth opening a new bug for your specific issue.
I'm a total newb to Ubuntu and linux in general (but enough of a
computer ner
Specified the suspected package to which this bug pertains.
** Changed in: linux-ubuntu-modules-2.6.22 (Ubuntu)
Sourcepackagename: None => linux-ubuntu-modules-2.6.22
--
[Gutsy] Upgrade to 2.6.22-12 causes iwl3945 to stop functioning
https://bugs.launchpad.net/bugs/144252
You received this bug n
Affirming error, just did an update.
--
[apport] NetworkManager crashed with signal 5 in main()
https://bugs.launchpad.net/bugs/85113
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ub
Are you getting any debug info from the various system logs?
--
Upgrade to 2.6.22.12 - NVidia driver does not work
https://bugs.launchpad.net/bugs/144551
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Yep, it's working now. I did a search for the file after updating and
was very excited to find it. Rebooting activated it and everything is
once again functioning as expected.
Thanks!
--
[Gutsy] Upgrade to 2.6.22-12 causes iwl3945 to stop functioning
https://bugs.launchpad.net/bugs/144252
You
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 NVID
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
Bug
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 /lib/linux-restricted-modules/2.6.22-14-generi
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 nvidi
Public bug reported:
I'm using a Thinkpad T61 with Gusty fully up to date. My T61 has the
Intel 3945 integrated wireless chip, and is using the IWL3945 drivers.
In general, the drivers work as expected. However, if ever the wireless
connection drops for whatever reason (signal strength too low,
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 you
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.
I'm
Public bug reported:
I'm using a Thinkpad T61 with Gusty fully up to date. My T61 has the
Intel 3945 integrated wireless chip, and is using the IWL3945 drivers.
In general, the drivers work as expected. However, if ever the wireless
connection drops for whatever reason (signal strength too low,
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 NVID
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
Bug
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 /lib/linux-restricted-modules/2.6.22-14-generi
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 nvidi
Public bug reported:
I have a ThinkPad T61 running Gutsy.
Since upgrading to the 2.6.22-12 kernel in yesterday's batch of updates,
I have been unable to use either the nVidia drivers or the iwlwifi
drivers. The nVidia drivers appear to have a kernel mismatch, while the
iwlwifi drivers for the 39
It looks like the update to the nVidia drivers was just released, so
that's now working on 2.6.22-12.
However, the iwlwifi/3945 issue is still present. I'm not even sure
where to begin looking to address this.
** Summary changed:
- [Gutsy] 2.6.22-12 does not recognize nVidia or iwlwifi drivers
K8BeBop:
This sounds like a different problem. My problem with the nVidia drivers was
just a kernel version mismatch; I could see as much in the system logs.
Probably worth opening a new bug for your specific issue.
I'm a total newb to Ubuntu and linux in general (but enough of a
computer ner
Specified the suspected package to which this bug pertains.
** Changed in: linux-ubuntu-modules-2.6.22 (Ubuntu)
Sourcepackagename: None => linux-ubuntu-modules-2.6.22
--
[Gutsy] Upgrade to 2.6.22-12 causes iwl3945 to stop functioning
https://bugs.launchpad.net/bugs/144252
You received this bug n
Affirming error, just did an update.
--
[apport] NetworkManager crashed with signal 5 in main()
https://bugs.launchpad.net/bugs/85113
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ub
Are you getting any debug info from the various system logs?
--
Upgrade to 2.6.22.12 - NVidia driver does not work
https://bugs.launchpad.net/bugs/144551
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Yep, it's working now. I did a search for the file after updating and
was very excited to find it. Rebooting activated it and everything is
once again functioning as expected.
Thanks!
--
[Gutsy] Upgrade to 2.6.22-12 causes iwl3945 to stop functioning
https://bugs.launchpad.net/bugs/144252
You
I had the same issue. I used Greg Lund-Chaix's suggestion and it seems
to have resolved it.
--
package python-xml 0.8.4-10.1ubuntu2 failed to install/upgrade:
https://bugs.launchpad.net/bugs/367955
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
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 you
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.
I'm
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 NVID
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
Bug
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 /lib/linux-restricted-modules/2.6.22-14-generi
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 nvidi
Public bug reported:
I have a ThinkPad T61 running Gutsy.
Since upgrading to the 2.6.22-12 kernel in yesterday's batch of updates,
I have been unable to use either the nVidia drivers or the iwlwifi
drivers. The nVidia drivers appear to have a kernel mismatch, while the
iwlwifi drivers for the 39
It looks like the update to the nVidia drivers was just released, so
that's now working on 2.6.22-12.
However, the iwlwifi/3945 issue is still present. I'm not even sure
where to begin looking to address this.
** Summary changed:
- [Gutsy] 2.6.22-12 does not recognize nVidia or iwlwifi drivers
K8BeBop:
This sounds like a different problem. My problem with the nVidia drivers was
just a kernel version mismatch; I could see as much in the system logs.
Probably worth opening a new bug for your specific issue.
I'm a total newb to Ubuntu and linux in general (but enough of a
computer ner
Specified the suspected package to which this bug pertains.
** Changed in: linux-ubuntu-modules-2.6.22 (Ubuntu)
Sourcepackagename: None => linux-ubuntu-modules-2.6.22
--
[Gutsy] Upgrade to 2.6.22-12 causes iwl3945 to stop functioning
https://bugs.launchpad.net/bugs/144252
You received this bug n
Affirming error, just did an update.
--
[apport] NetworkManager crashed with signal 5 in main()
https://bugs.launchpad.net/bugs/85113
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ub
Are you getting any debug info from the various system logs?
--
Upgrade to 2.6.22.12 - NVidia driver does not work
https://bugs.launchpad.net/bugs/144551
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Yep, it's working now. I did a search for the file after updating and
was very excited to find it. Rebooting activated it and everything is
once again functioning as expected.
Thanks!
--
[Gutsy] Upgrade to 2.6.22-12 causes iwl3945 to stop functioning
https://bugs.launchpad.net/bugs/144252
You
I had the same issue. I used Greg Lund-Chaix's suggestion and it seems
to have resolved it.
--
package python-xml 0.8.4-10.1ubuntu2 failed to install/upgrade:
https://bugs.launchpad.net/bugs/367955
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
Public bug reported:
I'm using a Thinkpad T61 with Gusty fully up to date. My T61 has the
Intel 3945 integrated wireless chip, and is using the IWL3945 drivers.
In general, the drivers work as expected. However, if ever the wireless
connection drops for whatever reason (signal strength too low,
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 you
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.
I'm
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 NVID
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
Bug
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 /lib/linux-restricted-modules/2.6.22-14-generi
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 nvidi
Public bug reported:
I have a ThinkPad T61 running Gutsy.
Since upgrading to the 2.6.22-12 kernel in yesterday's batch of updates,
I have been unable to use either the nVidia drivers or the iwlwifi
drivers. The nVidia drivers appear to have a kernel mismatch, while the
iwlwifi drivers for the 39
It looks like the update to the nVidia drivers was just released, so
that's now working on 2.6.22-12.
However, the iwlwifi/3945 issue is still present. I'm not even sure
where to begin looking to address this.
** Summary changed:
- [Gutsy] 2.6.22-12 does not recognize nVidia or iwlwifi drivers
K8BeBop:
This sounds like a different problem. My problem with the nVidia drivers was
just a kernel version mismatch; I could see as much in the system logs.
Probably worth opening a new bug for your specific issue.
I'm a total newb to Ubuntu and linux in general (but enough of a
computer ner
Specified the suspected package to which this bug pertains.
** Changed in: linux-ubuntu-modules-2.6.22 (Ubuntu)
Sourcepackagename: None => linux-ubuntu-modules-2.6.22
--
[Gutsy] Upgrade to 2.6.22-12 causes iwl3945 to stop functioning
https://bugs.launchpad.net/bugs/144252
You received this bug n
Affirming error, just did an update.
--
[apport] NetworkManager crashed with signal 5 in main()
https://bugs.launchpad.net/bugs/85113
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ub
Are you getting any debug info from the various system logs?
--
Upgrade to 2.6.22.12 - NVidia driver does not work
https://bugs.launchpad.net/bugs/144551
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Yep, it's working now. I did a search for the file after updating and
was very excited to find it. Rebooting activated it and everything is
once again functioning as expected.
Thanks!
--
[Gutsy] Upgrade to 2.6.22-12 causes iwl3945 to stop functioning
https://bugs.launchpad.net/bugs/144252
You
1 - 100 of 102 matches
Mail list logo
