Ubuntu
nvidia-kernel-common package

X doesn't load at all when nvidia-glx-new is used

Bug #136585 reported by Thomas Winwood
4
Affects Status Importance Assigned to Milestone
nvidia-kernel-common (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

If I'm using the nv driver to load X I have no trouble. If I try and use the nvidia driver from nvidia-glx-new X doesn't load at all - it doesn't even leave an Xorg.0.log file which might tell me something.

Due to bug #136582 I also have no way to get at a terminal, so I'm basically stuck without any form of diagnostic messages. I'm hoping someone else can help more and possibly get this fixed.

Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

Thomas:
There isn't really enough information here to diagnose your problem - you would really have to temporarily disable spash in the grub boot menu so you can get working consoles. I'll take a random stab and assume you have an 8000 series card and say I think you're seeing Bug #98641 .

Revision history for this message
Thomas Winwood (thomas-cleverpun) wrote :

I thought that too, but manually adding libwfb from the nVidia driver didn't fix it. Also, reports from bug #98641 don't prevent X from running at all - they get an Xorg.0.log file. I do have an 8xxx-series card though.

Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

Thomas:
Does disabling usplash/booting to recovery mode show you a terminal?

Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

(you can use sudo telinit 5 to try and ascend to X)

Revision history for this message
Thomas Winwood (thomas-cleverpun) wrote :

Recovery mode gets me a terminal.

Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

When in recovery mode does logging in and using sudo telinit 5 get you any further?

Revision history for this message
Thomas Winwood (thomas-cleverpun) wrote :

I don't know, and I'm not using Ubuntu now (found a different distro which doesn't present driver problems) so I'm not in a position to find out. My hope in making the bug was that someone else would have already experienced the bug and be able to say "hey yeah, I know that problem, this is what I did".

Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

That's definitely fair enough. Unfortunately there isn't enough information here to take this bug further. Probably the only thing that can be done is for this report to be resolved invalid unless more information can be added to diagnose it...

(If you're looking for speedy help it's probably better to file support requests over on https://answers.launchpad.net/ or use on of the methods mentioned on http://www.ubuntu.com/support/communitysupport )

Revision history for this message
Andreas Moog (ampelbein) wrote : Closing this Bug since there was no Information provided

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on the current status, under the Status column, and change
the Status back to "New". Thanks again!

 status invalid
 subscribe

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkiv8QYACgkQ06FgkPZwicSlEgCgt/5GJp4Rfc/lEZvKK5gxkoC0
hv0AoLFdQ7Y6K5lAEN30c4q8DWHVZhMm
=dt09
-----END PGP SIGNATURE-----

Changed in nvidia-kernel-common:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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