I'm using vesafb (having 80x25 VT on 24" screen is quite ugly) and nvidia 
binary drivers.
If I don't get blue/white lines during startup, then Enter is working fine.
If I see blue/white lines (but they are flickering, looks like something else 
is trying to clear the screen), then there is Enter key problem. Tested few 
times, hopefully this is the correct pattern. In this situation I see:

before SysRq+K: /usr/bin/X :0 -nr -verbose -auth 
/var/run/gdm/auth-for-gdm/uXADGb/database -noliste tcp vt7
after  SysRq+K: /usr/bin/X :0 -br -verbose -auth 
/var/run/gdm/auth-for-gdm/uXADGb/database -noliste tcp vt7

/proc/fb: 0 EFI VGA

I tried to replace vesafb with vga16fb (which I assume is the default
one used) and removed gfxpayload from grub boot entry. I saw nice
white/blue line growing at the bottom edge of screen, but it took
approx. one minute to fill the whole line with white color and nothing
happened. After pressing SysRq+K I got rescue shell, so I put vesafb
back.

-- 
Pressing <Enter> causes X to freeze
https://bugs.launchpad.net/bugs/516412
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
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to