If I read the comments correctly, it appears that the issue is fixed in
recent Ubuntu releases
** Changed in: Ubuntu
Status: New => Fix Released
--
[edgy] TTY blank whith 'vga=791' and strange keyboard behaviour
https://bugs.launchpad.net/bugs/63137
You received this bug notification beca
I did a bit more troubleshooting.
When I boot with a "recovery mode" kernel, for example:
kernel /vmlinuz-2.6.17-10-386 root=/dev/md1 ro single
the problem does not appear.
When I boot with a fresh compiled plain vanilla kernel, straight from
kernel.org, the problem is also there. This
Here it is /var/log/syslog.
Note that I extracted a part of the file and divided it with a gap: as
you see, the first part is related to the boot with the vga=791
parameter, the second one is related to a normal boot.
** Attachment added: "/var/log/syslog"
http://librarian.launchpad.net/455893
** Attachment added: "/var/log/Xorg.0.log"
http://librarian.launchpad.net/4558945/Xorg.0.log
--
[edgy] TTY blank whith 'vga=791' and strange keyboard behaviour
https://launchpad.net/bugs/63137
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo
Ok. If it only appears when parameter is passed, there at least seems to
be a relation. Are there errors or failures reported in the logfiles
/var/log/syslog and/or /var/log/Xorg.0.log? Is an error on bootup
reported, when starting with framebuffer, but without quiet (or even
without quiet and spla
Ok, I confirm the keyboard's bug.
When no "vga=791" (or any other) is passed to the kernel at boot, all is good
and I can type normally (though I have an incorrect frame buffer resolution).
When that parameter is passed, after I got KDE running, if I open a terminal
and type a character, this is
> Well, I'll try again, didn't find that bug.
You couldn't, because it was already marked as "Fix Commited".
> didn't find something fitting better.
If you have questions concerning setup issues, try out this:
https://launchpad.net/support . You of course can also start a forum thread.
> sorry
>> The issue with the framebuffer should be fixed with new
>> usplash-version, which is already available in repositories. (was:
>> bug #61718)
Well, I'll try again, didn't find that bug.
>> Note: "vga=791" is setting up a fb with 1024x768, so it can't
>> display an 1280x800 usplash correctly.
The issue with the framebuffer should be fixed with new usplash-version,
which is already available in repositories. (was: bug #61718)
Note: "vga=791" is setting up a fb with 1024x768, so it can't display an
1280x800 usplash correctly.
Concerning the keyboard issue: is it exactly the same like th
