Small possibility this was a variation of Bug #107084 . However as the
issue is no longer seen marking bug as invalid as requested by reporter.
** Changed in: linux-restricted-modules-2.6.20 (Ubuntu)
Status: Incomplete => Invalid
** Changed in: linux-restricted-modules-2.6.22 (Ubuntu)
Sitsofe:
I cannot recreate the problem any more. I just re-booted to
2.6.20-16-generic and it came up using nvidia-glx without a problem.
Yesterday it was giving me API mismatch errors. I couldn't fix it in
2.6.20-16 so I reverted to 2.6.20-15 and did depmod and modprobe stuff,
and probably apt-ge
foolishchild:
You will need
linux-restricted-modules-generic
installed to make sure that the lrm is updated every time a kernel update comes
out. I have seen computers with 2.6.20-16-generic on them using restricted
drivers so I would like to know more about this issue. It would be interesting
t
Problem resolved by:
remove all of linux-restricted-modules*, nvidia* with --purge
install envy
- use envy to install nvidia-glx
- use envy to remove nvidia-glx
- use envy to clean-up all ATI and Nvidia installations
remove envy
install linux-restricted-modules-generic* first, then install nvidi
Sitsofe:
Blacklisting the modules in the /etc/default/linux-restricted-modules-common
was not enough (as some users reported). Therefore I commented out the
/etc/modprobe.d/lrm-video .
--
nvidia-glx installation is broken after reboot
https://bugs.launchpad.net/bugs/130832
You received this bug
Sitsofe:
I used envy because this problem was already happening. So I thought I'd see if
envy worked. It didn't. So I uninstalled it, with a little trouble, because it
didn't clean up after itself without a little manual intervention.
I am very familiar with the second link you gave me. It is w
foolishchild:
Was your issue resolved by Alberto's steps combined with your dpkg-reconfigure?
--
nvidia-glx installation is broken after reboot
https://bugs.launchpad.net/bugs/130832
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
Alberto:
It edits both?! How come?
--
nvidia-glx installation is broken after reboot
https://bugs.launchpad.net/bugs/130832
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.ubuntu.com
h
Sistofe:
No, Envy also edits the /etc/default/linux-restricted-modules-common
--
nvidia-glx installation is broken after reboot
https://bugs.launchpad.net/bugs/130832
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
Alberto:
Was using /etc/default/linux-restricted-modules-common unreliable?
foolishchild:
Woah! I didn't say that the bug was definitely in
linux-restricted-modules-2.6.20. You never said you had installed envy until
after I changed the component... You can do what you like to your system but
y
@Sitsofe Wheeler
Envy comments it out when you install the driver and uncomments it when you
uninstall the driver.
@foolishchild
This is a problem that Ubuntu's dev should deal with. If you are still willing
to use Envy (always at your risk) I can help you diagnose the problem but not
here. May
OK:
Followed Alberto's suggestion. Results identical to before. Nothing in dmesg
that looks relevant, can't modprobe nvidia (result was
FATAL: Could not open '/lib/modules/2.6.20-15-386/volatile/nvidia.ko': No such
file or directory
FATAL: Error running install command for nvidia)
ran depmod, st
Alberto:
Does envy always comment out /etc/modprobe.d/lrm-video ?
--
nvidia-glx installation is broken after reboot
https://bugs.launchpad.net/bugs/130832
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
well, since you used Envy you will have to uninstall the driver through
Envy.
then type:
sudo apt-get install --reinstall restricted-manager
and finally edit your /etc/modprobe.d/lrm-video as I suggested
--
nvidia-glx installation is broken after reboot
https://bugs.launchpad.net/bugs/130832
Yo
open your /etc/modprobe.d/lrm-video and make it look like the following:
## Make nvidia/nvidia_legacy and fglrx use /sbin/lrm-video to load
#install fglrx /sbin/lrm-video fglrx $CMDLINE_OPTS
install nvidia /sbin/lrm-video nvidia $CMDLINE_OPTS
#install nvidia_legacy /sbin/lrm-video nvidia_legacy $C
Is there a way I can remove EVERYTHING to do with this. I mean linux-
restricted-modules, nvidia-glx, nvidia-kernel-common, any old crap left
around by other installers (e.g. envy) and then reinstall a known
working set of packages? That's what I was trying to do with "sudo apt-
get install nvidia
$ sudo apt-get install linux-restricted-modules-`uname -r`
Password:
Reading package lists... Done
Building dependency tree
Reading state information... Done
linux-restricted-modules-2.6.20-15-386 is already the newest version.
linux-restricted-modules-2.6.20-15-386 set to manual installed.
what happens if you type:
sudo apt-get install linux-restricted-modules-`uname -r`
--
nvidia-glx installation is broken after reboot
https://bugs.launchpad.net/bugs/130832
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-
foolishchild:
> What does "Really punting from linux-restricted-modules-2.6.22 ->
> linux-restricted-modules-2.6.20" mean?
It means I'm changing the component this bug is filed against. 2.6.22
kernels are distributed with Gutsy, 2.6.20 kernels are Feisty ones (the
architecture isn't tracked in th
(Subscribed Alberto Milone)
--
nvidia-glx installation is broken after reboot
https://bugs.launchpad.net/bugs/130832
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.ubuntu.com
https://
I've remembered another strange thing. I have kernel 2.6.20-16-386 but I
can't persuade the nvidia module to work at all with that. Hence I'm
using kernel 2.6.20-15-386.
Is this a dup of 95956?
I found Bug #108578 which looks somewhat similar. It pointed me to
/etc/modprobe.d/lrm-video, which w
dmesg | tail after reboot:
[ 49.429327] EXT3-fs: mounted filesystem with ordered data mode.
[ 50.923915] input: Power Button (FF) as /class/input/input4
[ 50.929040] ACPI: Power Button (FF) [PWRF]
[ 50.965199] input: Power Button (CM) as /class/input/input5
[ 50.970293] ACPI: Power Butto
Thanks for your help. What does "Really punting from linux-restricted-
modules-2.6.22 -> linux-restricted-modules-2.6.20" mean? I am running
linux-restricted-modules-2.6.20-15-386.
dpkg -l \*restricted\* | grep ii
ii linux-restricted-modules-2.6.20-15-386 2.6.20.5-15.20 Non-free Linux
2.6.20
Really punting from linux-restricted-modules-2.6.22 -> linux-restricted-
modules-2.6.20 .
** Changed in: linux-restricted-modules-2.6.20 (Ubuntu)
Sourcepackagename: linux-restricted-modules-2.6.22 =>
linux-restricted-modules-2.6.20
--
nvidia-glx installation is broken after reboot
https://bugs.
Hmm. Kernel is the 386 version too...
foolishchild:
Is there anything unusual about your setup? Have you followed any advice to
modify various files?
Have you ever installed the binary drivers "by hand" or have you always used
the repositories? Can you upload your
/etc/fstab
file?
After rebooti
Kernel is not from Gutsy - this looks like a Feisty install. Punting
from linux-restricted-modules-2.6.22 -> linux-restricted-modules-2.6.20
.
--
nvidia-glx installation is broken after reboot
https://bugs.launchpad.net/bugs/130832
You received this bug notification because you are a member of Ub
And to continue answering I attach a file describing the steps I just took to
gather this information, which includes answers to things like dpkg -l
\*nvidia\* | grep ii...
It's called nvidia.prob.
In it you will see I believe the problem is that the nvidia module is
not being properly installed
You may be right (about support) but I think it is a bug, probably in
the install information of one of the packages? Which one though?
To answer your questions:
I am running kubuntu 7.04 Feisty Fawn. Is there a uname type command to show
this?
uname -a ==> Linux server0 2.6.20-15-386 #2 Sun Apr
To continue answering, I attach the dmesg output after booting and
Xserver not working
** Attachment added: "nvidia.dmesg"
http://launchpadlibrarian.net/8742987/nvidia.dmesg
--
nvidia-glx installation is broken after reboot
https://bugs.launchpad.net/bugs/130832
You received this bug notifica
foolishchild:
This sounds more like a support issue ( https://answers.launchpad.net/ ) than a
bug report - you may have a better/quicker using one of the methods described
on http://www.ubuntu.com/support/CommunitySupport .
When it fails to start can attach your
/var/log/Xorg.0.log
and the outpu
30 matches
Mail list logo
