Wilbur:
There's definitely something in your files which looks hand edited but it's not
going to result in this particular problem (although it may cause you a
different problem sometime down the line, possibly when you go to upgrade that
Ubuntu install to 7.10...).
At any rate I think you're
Wilbur:
Did you follow an online guide of some sort to enable your binary drivers and
if so what steps did you follow? Your configuration is showing signs of manual
changes...
** Changed in: linux-source-2.6.20 (Ubuntu)
Status: Unconfirmed = Needs Info
--
kernel 2.6.20-16 nvidia-glx
Wilbur:
Could you also post the output of:
ls -l /etc/rcS.d/
?
--
kernel 2.6.20-16 nvidia-glx and nvidia-glx-new won't load
https://bugs.launchpad.net/bugs/118221
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
No, I never followed an online guide to enable the binary drivers. I
only used the restricted driver manager and synaptic.
I just installed the new 2.6.20-16.29 linux and I have the same
problems, maybe it is because there doesn't seem to be a new 16.29
restricted drivers?
Is there a possible
I changed my fstab so that /lib was not being mounted on /md0/lib.
Then I rebooted and rsync'ed what was in /md0/lib into /lib
After that the system boots fine, my cdrom is visible and my /dev/sdc is also
visible.
So something is different between the -15 and -16 kernel in how soon the /lib
Wilbur:
I've just realised one of my earlier questions might not have been clear so
I'll rephrase it.
Is this install of Fesity an upgrade from Edgy/some other earlier
version of Linux?
Could you also indicate what steps or advice you followed to enable to
the NVIDIA binary drivers on Feisty?
This was a clean install of feisty on new hard drives from the final
version of the Feisty alternate CD.
Originally I just used the restricted driver manager to enable the
nvidia driver, then I just did the updates via synaptic. After the -16
kernel update, where I had installed the restricted
[EMAIL PROTECTED]:~$ ls -l /lib/modules/2.6.20-16-generic/volatile
total 0
[EMAIL PROTECTED]:~$
I have noticed that no matter what I do, the volatile directory is
always empty.
Wilbur
--
kernel 2.6.20-16 nvidia-glx and nvidia-glx-new won't load
https://bugs.launchpad.net/bugs/118221
You
Wilbur:
Can you run
uname -a
sudo sh -x /sbin/lrm-manager
and post the results here?
--
kernel 2.6.20-16 nvidia-glx and nvidia-glx-new won't load
https://bugs.launchpad.net/bugs/118221
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
Wilbur:
Can you also post the output of
cat /etc/default/linux-restricted-modules-common
?
--
kernel 2.6.20-16 nvidia-glx and nvidia-glx-new won't load
https://bugs.launchpad.net/bugs/118221
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
Wilbur:
Looking at that /etc/fstab makes me feel uneasy. I've not known people to use
so many bind mounts with such key pieces of the file system. Can you attach the
full unmodified /etc/fstab to this bug please?
--
kernel 2.6.20-16 nvidia-glx and nvidia-glx-new won't load
Using the mount --bind was the only way I could figure out how to make a
software raid0 work under ubuntu.
In general, people don't seem to be able to make the software raid work under
Ubuntu.
Software raid seems to work fine under Fedora without such measures.
Wilbur
** Attachment added:
Wilbur:
OK. At any rate we shall sidestep the RAID setup up for now. Can you please
post the results of
uname -a
sudo sh -x /sbin/lrm-manager
cat /etc/default/linux-restricted-modules-common
?
--
kernel 2.6.20-16 nvidia-glx and nvidia-glx-new won't load
https://bugs.launchpad.net/bugs/118221
First, you realize that I am using this system, I don't have a separate system
I am reading this on.
When I boot, I have the nv driver loaded.
To run the things you ask me to run, I edit the /etc/X11/xorg.conf file to put
the nvidia driver back in.
[EMAIL PROTECTED]:~$ uname -a
Linux lu2f64
I think that we are closing in on the solution.
I noticed that after running sudo sh -x /sbin/lrm-manager, that the volatile
directory was full of modules.
I tried to re-start X and it worked!!!
I then rebooted, same problem, no X. The volatile directory was empty as
well. I then, from the
I also, cannot see my /dev/hda (DVD drive) with the -16 kernel
--
kernel 2.6.20-16 nvidia-glx and nvidia-glx-new won't load
https://bugs.launchpad.net/bugs/118221
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
Wilbur:
You might want to take a look at Bug #117413 with regard to the DVD drive issue.
--
kernel 2.6.20-16 nvidia-glx and nvidia-glx-new won't load
https://bugs.launchpad.net/bugs/118221
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
Wilbur:
Darn. Thanks for persisting with this. What is the result of
sudo modprobe --ignore-install nvidia_new
? Can you do attach the full log of
sudo strace -f modprobe --ignore-install nvidia_new
? Can you then also include the output of
dmesg | tail -20
after running those commands?
(You did
Yes, I did reboot, several times.
[EMAIL PROTECTED]:~$ sudo modprobe --ignore-install nvidia_new
Password:
FATAL: Module nvidia_new not found.
[EMAIL PROTECTED]:~$
[EMAIL PROTECTED]:~$ dmesg | tail -20
[ 54.113655] NET: Registered protocol family 31
[ 54.113657] Bluetooth: HCI device and
Wilbur:
Can you post the output of
ls -l /lib/modules/2.6.20-16-generic/volatile/
?
--
kernel 2.6.20-16 nvidia-glx and nvidia-glx-new won't load
https://bugs.launchpad.net/bugs/118221
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
Wilbur:
OK that lets us rule out unusual changes.
Can you post the output of:
sudo sh -x /sbin/lrm-video nvidia
?
Something has just occurred to me. Did you used to have nvidia-glx-new
installed and then decided to switch to just nvidia-glx ?
--
kernel 2.6.20-16 nvidia-glx and nvidia-glx-new
Yes, when I upgraded to the 2.6.20-16, I also installed the nvidia-glx-
new. When it didn't work, I went back to the nvidia-glx.
[EMAIL PROTECTED]:~$ sudo sh -x /sbin/lrm-video nvidia
Password:
+ PATH=/sbin:/bin
+ MODULE=nvidia
+ shift
+ [ nvidia = nvidia ]
+ [ -e
Wilbur:
OK if you are switching from nvidia-glx-new to nvidia-glx then you are going to
suffer from Bug #106217 (as described on
https://help.ubuntu.com/community/BinaryDriverHowto/Nvidia ).
I suspect if you _now_ uninstall nvidia-glx , reinstall nvidia-glx-new ,
switch xorg.conf to nvidia and
Ok, I tried that, yes the .nvidia_new_installed file was there.
I tried to delete it and restart X, stil no luck
Then I tried to re-install nvidia-glx-new and restart X, still no luck.
When I try to modprobe nvidia I get this
[EMAIL PROTECTED]:~$ sudo lsmod | grep nv
Password:
sata_nv
I included the dmesg output.
I tried all of the above and no change, still no nvidia driver loaded.
Mine is a GeForce 6600 128MB.
Maybe the difference is that I am running Feisty7.04-64Bit?
** Attachment added: dmesg.txt
http://launchpadlibrarian.net/7924430/dmesg.txt
--
kernel 2.6.20-16
Wilbur:
Can you attach the contents of
/etc/X11/xorg.conf
to this bug report? Can you also add the output of running
dpkg -l linux-restricted-modules-* | cat
Can you include the output of
sudo modprobe nvidia
After this can you do
sudo depmod
then again include the output of
sudo modprobe nvidia
?
[EMAIL PROTECTED]:~/tmp/tmp2$ dpkg -l linux-restricted-modules-* | cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name
Wilbur:
Did you ever manually install the NVIDIA binary drivers (or use a 3rd party
tool to do so) in the past?
--
kernel 2.6.20-16 nvidia-glx and nvidia-glx-new won't load
https://bugs.launchpad.net/bugs/118221
You received this bug notification because you are a member of Ubuntu
Bugs, which
No, this was fresh Feisty install and I only installed them through
Synaptic.
--
kernel 2.6.20-16 nvidia-glx and nvidia-glx-new won't load
https://bugs.launchpad.net/bugs/118221
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
you'll neeed to show the output of dmesg so we can see what it says about the
NVIDIA module. Also, did you disable the nvidia restricted module within
/etc/default/linux-restricted-modules-common file? put nv within the quotes and
it will load the nvidia-glx-new driver, that's how I got my
When a nvidia proprietary driver is install and the kernel is updated, the
restricted modules are not updated automatically.
Could you install linux-restricted-modules-2.6.20-16-generic?
Just seach nvidia in Synaptic. You should see that
linux-restricted-modules-2.6.20-15-generic is installed
31 matches
Mail list logo
