I'm also getting a blank screen when trying to switch to ttys other than
the one used for my display manager.
--
Can't access tty
https://bugs.launchpad.net/bugs/301737
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
I removed the splash kernel option at boot, but I still get a black
screen on every tty. Any ideas?
Also, I'm running beta drivers now (185.19).
--
Can't access tty
https://bugs.launchpad.net/bugs/301737
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I am experiencing a similar issue. No ttys upon ctrl+alt+f1-f6, just a
blank screen. This is several months after the fix would have been
implemented. ubuntu jaunty 9.04 Nvidia GeForce 9300M GS
TTY access would be nice to install the new nvidia drivers.
--
Can't access tty
Which new nvidia drivers? And are they not already in a PPA? 185.18.14
is in several PPAs, and appears to still be the latest available.
If you boot without usplash, do you still have the same problem? That
fixed it for many of us during the time it was broken. I have never
turned usplash
Nvidia driver: 180.60
I'll try turning off usplash. I'm going to go find out how. Is the bug
in usplash being worked on?
--
Can't access tty
https://bugs.launchpad.net/bugs/301737
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Today tty works again for me ;)
Probably this fix:
usplash (0.5.26) jaunty; urgency=low
* Fix various compiler warnings.
* debian/splash-functions: Kill usplash more gracefully in splash_stop;
introduces new SPLASH_ORIG_CONSOLE environment variable which can be
checked by other init scripts
Thanks for testing - yes, Colin Watson spotted a bug in both gdm and
usplash that was causing this, so I got the package choice totally wrong
;)
** Changed in: usplash (Ubuntu)
Sourcepackagename: linux = usplash
Status: Triaged = Fix Released
--
Can't access tty
I had the same issue. Removing the usplash option from grub fixed it.
--
Can't access tty
https://bugs.launchpad.net/bugs/301737
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.ubuntu.com
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
Can't access tty
https://bugs.launchpad.net/bugs/301737
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.ubuntu.com
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
Assignee: (unassigned) = Ubuntu Kernel Team (ubuntu-kernel-team)
Status: Confirmed = Triaged
--
Can't access tty
https://bugs.launchpad.net/bugs/301737
You received this bug notification because you are a member of
See also Bug 301359, which I have marked as a duplicate of this one
(even though it was earlier) since this one has had more discussion. I
had attached the requisite lscpi, dmesg, and xorg.conf files, as well as
noting that the bug appears with both the nv and nvidia (177) drivers.
** Changed
the problem goes away without usplash. I'd like you to be able to
confirm this too.
Yes, Chris. I confirm that the virtual terminals work again after
simply removing splash from the kernel boot parameters using the edit
feature of GRUB. Hope that helps to nail the culprit down, and in the
TBH, this could be a kernel, usplash or Xorg issue. I don't think it is
video driver related as we all use different video drivers. Up until
today, Jaunty has been using the Intrepid kernel (and this problem
doesn't exist in Intrepid), so I'm starting to think it's not a kernel
problem. Usplash
I am having similar issues as the previous commenter (garbled orange
screen as opposed to black screen), but with a different video chipset,
an ATI Radeon Mobility U1. The ctrl-alt-f(1-6) combinations give me
nothing but a garbled screen, and I have to use ctrl-alt-f7 to get back
to X.
--
Can't
Addendum to previous comment: I am on Jaunty, with the 2.6.27-7-generic
kernel.
--
Can't access tty
https://bugs.launchpad.net/bugs/301737
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
don't know if it's the same bug.
fully updated jaunty, ctrl-alt-f1,f2,whatever while being in X shows a black
screen, no login prompt.
pressing ctrl-alt-f7 I'm back in X, everything fine.
just not being able to access text consoles (1-6) from X.
nvidia geforce 6200
--
Can't access tty
Thank you for taking the time to report this bug and help make Ubuntu
better. I don't think this is an upstart issue. It will more likely be a
kernel or graphics driver issue. I will tentatively re-assign it to the
kernel for now. Do you have to reboot the machine after experiencing
this, or can
Ok... its broken also for several others, discussed within U-Fs Jaunty
forum.
7 is OK because I must install nVidias 180 driver from recovery and a
root console when tty is broken
Going to attach outputs.
--
Can't access tty
https://bugs.launchpad.net/bugs/301737
You received this bug
How come you added an upstart task again?
** Changed in: upstart (Ubuntu)
Status: New = Invalid
--
Can't access tty
https://bugs.launchpad.net/bugs/301737
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
[EMAIL PROTECTED]:~$ uname -a
Linux plun 2.6.27-7-generic #1 SMP Fri Oct 24 06:42:44 UTC 2008 i686 GNU/Linux
** Attachment added: lsmod.log
http://launchpadlibrarian.net/19943059/lsmod.log
--
Can't access tty
https://bugs.launchpad.net/bugs/301737
You received this bug notification because
** Attachment added: dmesg.log
http://launchpadlibrarian.net/19943072/dmesg.log
--
Can't access tty
https://bugs.launchpad.net/bugs/301737
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Attachment added: lspci-vvnn.log
http://launchpadlibrarian.net/19943078/lspci-vvnn.log
--
Can't access tty
https://bugs.launchpad.net/bugs/301737
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
How come you added an upstart task again?
Sorry about that just clicked. It was a red box... ;)
--
Can't access tty
https://bugs.launchpad.net/bugs/301737
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Right, I can recreate this in VMWare, and the problem goes away without
usplash. I'd like you to be able to confirm this too.
The machine doesn't actually lock up. I'm changing VT by SSH'ing in to
the guest and issuing chvt 1. Once I've done this, I see a garbled
screen in the guest (which
OK ;) ... Magic SysRq works at least. Alt-SysRq-b
Must install ssh-server within this box.
And start my putty machine and test ;)
and remove splash
** Attachment added: Xorg.0.log
http://launchpadlibrarian.net/19943363/Xorg.0.log
--
Can't access tty
nosplash is OK.
Connection trouble with Putty did a clean install a week ago.. OK to my
server so
something is wrong with the Jauntybox. testing more.
--
Can't access tty
https://bugs.launchpad.net/bugs/301737
You received this bug notification because you are a member of Ubuntu
Bugs,
SSH ok... connected directly to WAN ;)(instead of router)
but I get this...
[EMAIL PROTECTED]:~$ chvt 1
Couldnt get a file descriptor referring to the console
Ctrl-Alt-F7 works sometimes. ???F1 F6 never.
--
Can't access tty
https://bugs.launchpad.net/bugs/301737
You
** Summary changed:
- Can't acess tty
+ Can't access tty
--
Can't access tty
https://bugs.launchpad.net/bugs/301737
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.ubuntu.com
28 matches
Mail list logo
