in natty, nvidia kernel module does not seem to install, or nvidia installer crashes

Bug #775935 reported by Dwayne Voelker
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Mythbuntu
Expired
Undecided
Unassigned
Ubuntu
Expired
Undecided
Unassigned

Bug Description

I had opened this bug for ubiquity but since 11.04 was released, it now seems to be an nvidia/kernel bug, at least i can now get 11.04 to install, but it wont boot afterwards.
The ubiquity bug was marked as a duplicate or another bug, which it is probably not, but that bug is:
https://bugs.launchpad.net/bugs/744553

Since no-one will probably look at that one anymore, i am opening this one...
Here is what i posted earlier:

ok i tried the released 11.04 today and this is what i found:

pretty much the same as last week, but I have more info this time:

to reproduce, i:

1. booted with the 11.04 release cd and selected install (vs. boot into live cd mode). I did not change any command line entries, i.e. remove "quiet splash" or add noapic, etc.

2. selected install alongside windows 7

3. selected the option to install the third-party codecs, etc. but did not select the check-box to download updates(i thought that this may have been a problem in pre-release, in that it was failing to update the nvidia driver which also somehow disables the driver included on the cd).

4. after the install finishes, click reboot.

5. on reboot the splash screen displays for a very short time doesn't seem to animate at all, and then everything seems to freeze(if i hit caps lock or num lock no lights appear)

6. reboot again by holding the power button in. At the grub screen select 'e' to edit the selected boot entry. remove "quiet" and "splash" from the kernel line and select ctrl-x to boot

7. the log messages come up and i notice a few things there. (i will attach a picture that I took of it):

init: ureadahead-other main process (626) terminated with status 4
init: udev-fallback-graphics main process (675) terminated with status 1

... later on ...

starting automatic crash report generation [fail]

8. a few lines later the machine becomes unresponsive

Once i boot back into windows, i can mount the ext drives and i got the install, etc. logs from them which i will also post.

Revision history for this message
Dwayne Voelker (iamzam) wrote :
Revision history for this message
Dwayne Voelker (iamzam) wrote :
Revision history for this message
Dwayne Voelker (iamzam) wrote :
Revision history for this message
Dwayne Voelker (iamzam) wrote :
Revision history for this message
Dwayne Voelker (iamzam) wrote :
Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

Hello
This bug is already opened but i can't remember the number, for some cards:
May 2 20:18:59 ubuntu ubiquity: FATAL: Error inserting nvidia_173 (/lib/modules/2.6.38-8-generic/updates/dkms/nvidia-173.ko): No such device
You can have a working installation running the installer without download updates or third part software, better disconnect the cable if you are installing from a usb key, then after the boot install the Experimental drivers instead the nvidia drivers.
Thanks for the report and feel free to report any other bug you may find.
Thanks
Fabio

tags: added: likely-dup natty
removed: nvidia
Changed in ubuntu:
status: New → Incomplete
Revision history for this message
Dept.Técnico (Extreme Micro S.L.) (tecnicos-extreme-micro) wrote :

You can resolve the problem downloading latest nvidia drivers (NVIDIA-Linux-x86-270.41.19.run) from nvidia website and executing installer manually.

Changed in ubuntu:
status: Incomplete → New
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. This bug report has not been filed about a specific package rather just about Ubuntu in general. Examining the contents of this report it seems that this bug is probably about ubiquity. If this seems correct to you (you can get the package description by using the command 'apt-cache show ubiquity') please change the affected package to that one by clicking the expander next to Ubuntu and filing in the Package text box. Additionally, if there are no log files included in this report it'd be helpful if you were to gather them using the command 'apport-collect 775935' in a terminal after you've assigned the bug to a package.

For future reference there are bug reporting tools built in to Ubuntu that can be accessed by going to Help -> Report a Problem in the application's menu or by using the command 'ubuntu-bug' and the name of the package with which you are having a problem.

tags: added: pkg-recommended
Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

Hello
Are you encountering again this problem with the latest release Oneiric Ocelot ?
Thanks
Fabio
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

Changed in mythbuntu:
status: New → Incomplete
Changed in ubuntu:
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Mythbuntu because there has been no activity for 60 days.]

Changed in mythbuntu:
status: Incomplete → Expired
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Ubuntu because there has been no activity for 60 days.]

Changed in ubuntu:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.