Public bug reported:
I am running Kubuntu 8.10 on a Sony Vaio with a nvidia geforce go 6200.
Any time after loading the drivers that I try to use a TTY (or when shutting
down) there is a blank screen.
The TTY is still there, and responsive, but I cannot see it.
I had it with driver version 177
Can it be reassigned rather than marked invalid?
--
Cannot get back to a terminal after X has started
https://bugs.launchpad.net/bugs/225130
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.u
Geforce 6600 (or 6800) Go.
And non-free driver.
All I can see is that the option I set in modprobe would need to be
default.
--
Cannot get back to a terminal after X has started
https://bugs.launchpad.net/bugs/225130
You received this bug notification because you are a member of Ubuntu
Bugs, wh
This solved the problem for me:
I edited /etc/modprobe.d/options
I added this line: NVreg_UseVBios=0
Then I rebooted. After rebooting, it was working again, does this solve it for
you too?
--
Cannot get back to a terminal after X has started
https://bugs.launchpad.net/bugs/225130
You received
This solved the problem for me:
I edited /etc/modprobe.d/options
I added this line: NVreg_UseVBios=0
I then rebooted.
This was the ONLY thing that made any difference.
--
Blank TTYS with Geforce Go 6200 and nvidia drivers.
https://bugs.launchpad.net/bugs/315722
You received this bug notificat
Public bug reported:
I'm using a fresh install of Kubuntu 8.04 (Hardy).
If I stop KDM from starting automatically I can use a console login
perfectly, however, if I try to use one once X has started, I get a
blank screen.
I've tried the following methods to get to a console.
- ctrl+alt+F(1-6)
-
Also, if I login from a console (after stopping KDM from starting
automatically) and then I log out, I also get a blank screen rather than
the console again.
--
Cannot get back to a terminal after X has started
https://bugs.launchpad.net/bugs/225130
You received this bug notification because you
Same problem here. initially attempted an upgrade install, which failed
spectacularly.
then attempted a clean install, same failure.
am now DD'ing over the drive in hopes that a clean boot sector will fix
the problem.
i'm irked this bug hasn't been fixed, considering the time lapsed since
it's i