Building vgabios from source as described above added the missing modes
for me too. But still the vga driver does not work properly - it builds
the screen very slowly line by line and takes 20 seconds or more just
for the login-screen.
After some hours I gave up on vga and switched to the
** Changed in: vgabios (Ubuntu)
Assignee: Dustin Kirkland (kirkland) = morleyfl (morleyfl)
** Changed in: vgabios (Ubuntu Lucid)
Assignee: Dustin Kirkland (kirkland) = morleyfl (morleyfl)
--
You received this bug notification because you are a member of qemu-
devel-ml, which is
vgabios-0.6c-2ubuntu1 does not fix the bug for me.
Building vgabios.bin from qemu-kvm-0.12.4.tar.gz sources helps.
--
kvm with -vga std is broken since karmic
https://bugs.launchpad.net/bugs/513273
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed
Compared with the vgabios.bin supplied by upstream in qemu-
kvm-0.12.4.tar.gz, the current Lucid vgabios regresses support for a
number of vga modes (e.g. 1920x1200).
--
kvm with -vga std is broken since karmic
https://bugs.launchpad.net/bugs/513273
You received this bug notification because you
Still getting BUG: kvm_dirty_pages_log_enable_slot: invalid parameters
with -vga std-parameter on lucid.
I would suggest to set the bug-status to confirmed instead of fix-released.
---
dpkg -l |egrep -e kvm|vgabios
ii kvm
um. Can't you just take approach used in Debian, namely, to provide the
sources for the bios files and compile them at build time? That is
somewhat ugly, but at least it works...
--
kvm with -vga std is broken since karmic
https://bugs.launchpad.net/bugs/513273
You received this bug
Forgot to mention that I'm also getting constantly the error message:
BUG: kvm_dirty_pages_log_enable_slot: invalid parameters
BUG: kvm_dirty_pages_log_disable_slot: invalid parameters
BUG: kvm_dirty_pages_log_enable_slot: invalid parameters
BUG: kvm_dirty_pages_log_disable_slot: invalid
I'm using qemu-kvm 0.12.3 with -vga std and with res like 1680x1050,
1440x900 and a few other it crashes/quits immediately with message
Could not open SDL display. It happens for me both when switching with
ctrl-alt-f or with cmd line option -full-screen. With 1024x768 for
example it does not
