This fix is also in hardy.
** Changed in: linux-restricted-modules-2.6.22 (Ubuntu)
Assignee: LaMont Jones (lamont) = (unassigned)
Status: Fix Committed = Fix Released
--
Hidden file does not get removed when switching from
nvidia-glx-new/nvidia-glx-legacy to nvidia-glx causing X
nvidia-glx-config enable
DID THE TRICK
then have to
sudo nvidia-settings
:-)
feisty
--
Hidden file does not get removed when switching from
nvidia-glx-new/nvidia-glx-legacy to nvidia-glx causing X not to start due to
mismatch of versions
https://bugs.launchpad.net/bugs/106217
You received
Copied to gutsy-updates, closing gutsy task. Please do the same fix for
Hardy. Thank you!
** Changed in: linux-restricted-modules-2.6.22 (Ubuntu Gutsy)
Status: Fix Committed = Fix Released
--
Hidden file does not get removed when switching from
nvidia-glx-new/nvidia-glx-legacy to
Verification completed successfully.
After installation and removal of nvidia-glx-new version
100.14.19+2.6.22.4-14.9, the file
/lib/linux-restricted-modules/.nvidia.new.installed still exists.
After installation and removal of nvidia-glx-new version
100.14.19+2.6.22.4-14.10, the file
Accepted into gutsy-proposed, please test.
** Changed in: linux-restricted-modules-2.6.22 (Ubuntu Gutsy)
Status: New = Fix Committed
** Changed in: linux-restricted-modules-2.6.20 (Ubuntu Gutsy)
Status: New = Invalid
** Tags added: verification-needed
** Tags removed: bitesize
I believe lamont has uploaded a package to gutsy-proposed that includes
Leann's patch. Should make its way to gutsy-updates after the SRU
process.
** Changed in: linux-restricted-modules-2.6.22 (Ubuntu)
Assignee: Ubuntu Kernel Team (ubuntu-kernel-team) = LaMont Jones (lamont)
Status:
I can confirm this. Still happens in Gutsy with VGA compatible
controller: nVidia Corporation NV17 [GeForce4 440 Go] (rev a3).
--
Hidden file does not get removed when switching from
nvidia-glx-new/nvidia-glx-legacy to nvidia-glx causing X not to start due to
mismatch of versions
Peter:
Experience says that many mismatch problems usually arise when people manually
compile the driver for themselves / use a tool like envy or automatrix to
install the driver (additionally the NVIDIA driver should not be initramfs
because it is not needed to boot the system. It could have
I did indeed manually install the NVIDIA drivers... but only after the X
system was completely broken. I used the built-in package update
program (is it called aptitude??) to change drivers initially. Once
done, I rebooted and X failed to come up. I tried to use 'dselect' to
go back to the
As I don't have nvidia hardware, I'm not likely to be able to help with any
underlying problems.
I hadn't realised there was common practice for people to be installing non
Ubuntu versions of these pacakges.
If there are bugs with the Ubuntu shipped verison of the drivers, please
find the
Thanks much for the advice. I did uninstall and reinstall the mentioned
drivers. That alone does not seem to have fixed the problem, but
perhaps it helped. While installing one of them, I noticed that it
mentioned that I should run /usr/sbin/nvidia-glx-config.
I tried the enable and disable
Actually, I'm not sure how I got in this state, but my problem is of the
same sort but even more of a pain to fix. Not only did that .file have
to be deleted as discussed, but SOMETHING ins insmod'ing an old nvidia
driver from somewhere. The only way I can get X to load is to rmmod
nvidia and
Try:
sudo update-initramfs -u
To copy the new driver into the initrd. That might be where its getting
loaded from.
If this helps, and the new driver was installed via an official Ubuntu
package, please note back here, as that update hook probably ought to be
run after being installed. I'm not
I've emailed a patch to the kernel-team mailing list for their
consideration.
https://lists.ubuntu.com/archives/kernel-team/2007-October/001874.html
Thanks!
** Tags added: bitesize
--
Hidden file does not get removed when switching from
nvidia-glx-new/nvidia-glx-legacy to nvidia-glx causing
** Changed in: linux-restricted-modules-2.6.22 (Ubuntu)
Importance: Undecided = High
Assignee: (unassigned) = Ubuntu Kernel Team (ubuntu-kernel-team)
Status: Confirmed = Triaged
Target: None = gutsy-updates
--
Hidden file does not get removed when switching from
Sorry Ben. I have now been educated on the setting of triaged.
Thanx for the help.
zeddock
On 10/18/07, Ben Collins [EMAIL PROTECTED] wrote:
** Changed in: linux-restricted-modules-2.6.22 (Ubuntu)
Importance: Undecided = High
Assignee: (unassigned) = Ubuntu Kernel Team
I hit this one as well on Gutsy 7.10rc today, machine wouldnt start gdm
using an nvidia-glx after first having nvidia-glx-new installed. Had to
manually insmodding the correct nvidia.ko and then start gdm, bit of a
pain as nvidia-glx-new is no good for nouveau Reverse Engineering (it
causes
This is definitely still a bug in gutsy up to today. It would be nice if
it were fixed by Gutsy's release, as it should just be another rm
statement in postrm. Flipping between nvidia-glx/nvidia-glx-new is
pretty common for people who are trying to troubleshoot desktop-effects
glitches and this is
tried to nominate for Gusty but it was not listed.
zeddock
--
Hidden file does not get removed when switching from
nvidia-glx-new/nvidia-glx-legacy to nvidia-glx causing X not to start due to
mismatch of versions
https://bugs.launchpad.net/bugs/106217
You received this bug notification
Still a bug in gutsy (just ran into it). Removing the offending file
worked for me.
--
Hidden file does not get removed when switching from
nvidia-glx-new/nvidia-glx-legacy to nvidia-glx causing X not to start due to
mismatch of versions
https://bugs.launchpad.net/bugs/106217
You received this
** Also affects: linux-restricted-modules-2.6.22 (Ubuntu)
Importance: Undecided
Status: New
--
Hidden file does not get removed when switching from
nvidia-glx-new/nvidia-glx-legacy to nvidia-glx causing X not to start due to
mismatch of versions
https://bugs.launchpad.net/bugs/106217
The problem seems to be in the prerm script of the deb file. Instead of
removing /lib/linux-restricted-modules/.nvidia_new_installed it tries to
remove /lib/linux-restricted-modules/.nvidia_legacy_installed.
--
Hidden file does not get removed when switching from
I can confirm the bug is still present in Gutsy Tribe 4 (still silently
messes up manual installation of the binary nvidia drivers).
--
Hidden file does not get removed when switching from
nvidia-glx-new/nvidia-glx-legacy to nvidia-glx causing X not to start due to
mismatch of versions
Bug #130799 says that this issue is still happening in Gutsy...
--
Hidden file does not get removed when switching from
nvidia-glx-new/nvidia-glx-legacy to nvidia-glx causing X not to start due to
mismatch of versions
https://bugs.launchpad.net/bugs/106217
You received this bug notification
It took me like 3 hours to find this bug and get rid of the file, this
should really be fix ASAP! ;-)
--
Hidden file does not get removed when switching from
nvidia-glx-new/nvidia-glx-legacy to nvidia-glx causing X not to start due to
mismatch of versions
https://bugs.launchpad.net/bugs/106217
AAAGHHH
It took me two days and crawling the Nvidia forums to sort this one out
:(
In case anyone is reading this looking for a solution, here it is :
sudo rm /lib/linux-restricted-modules/.nvidia.new.installed
I know this is a temporary solution, still ...
--
Hidden file does
As to why people are messing with there nvidia drivers at all, here is
how I fell into this:
- boot 7.04 from a live cd
- use restricted manager to install nvidia (thought id try it out first)
- it finishes ok but then says needs to reboot, which I did not do figuring the
changes would go away
Aaron:
That issue is almost certainly worth spinning off into a new bug of its own...
--
Hidden file does not get removed when switching from
nvidia-glx-new/nvidia-glx-legacy to nvidia-glx causing X not to start due to
mismatch of versions
https://bugs.launchpad.net/bugs/106217
You received
I can confirm this bug, removing that file solved the problem.
--
Hidden file does not get removed when switching from
nvidia-glx-new/nvidia-glx-legacy to nvidia-glx causing X not to start due to
mismatch of versions
https://bugs.launchpad.net/bugs/106217
You received this bug notification
This bug is cropping up A LOT on the nvidia linux forum. It would be
good from a Ubuntu publicity angle if a fix was backported to Feisty
fairly soon. Just my 2 cents..
--
Hidden file does not get removed when switching from
nvidia-glx-new/nvidia-glx-legacy to nvidia-glx causing X not to
Richard:
Hmm that's worrying (I noticed that was cropping up a lot too and I've been
trying to add the most frequently reported bugs to
https://help.ubuntu.com/community/BinaryDriverHowto/Nvidia with the most common
problems nearer the top) but this is only a symptom. People are switching from
** Summary changed:
- hidden file controlling NVIDIA driver does not get removed when switching
from nvidia-glx-new back to nvidia-glx causing X not to start due to mismatch
of versions
+ Hidden file does not get removed when switching from
nvidia-glx-new/nvidia-glx-legacy to nvidia-glx
Ludi:
Your issue appears to be precisely this bug so I was completely wrong. I was
unaware that you had nvidia-glx-legacy and had then subsequently tried to
install nvidia-glx.
--
Hidden file does not get removed when switching from
nvidia-glx-new/nvidia-glx-legacy to nvidia-glx causing X not
33 matches
Mail list logo
