Hello, > On Tue, Jan 24, 2006 at 08:15:12AM +0200, Guillem Jover wrote: > > Can you try with vgabios 0.5d-1 from testing or unstable? > > > > If it works I'll update the versioned dependency.
> Just tried it, vgabios 0.5d-1 works. Thanks. Sorry for the extra traffic I am generating here, but my report concerning vgabios package is erroneus. The problem I desribed is not related to vgabios at all, but to bochsbios package instead. I did some testing and found that loadvm problem depends on _PC_ bios version used when VM state was _saved_ (that fact made me report a false positive about vgabios 0.5d-1 since I used old VM state image). Results table: package version | rombios.c rev# | status -----------------------------------+----------------+--------------- bochsbios 2.1.1+20041109-3 | 1.121 | works, no APM bios.bin from qemu 0.7.8 upstream | 1.130 | works bios.bin from qemu 0.8.0 upstream | 1.130 | works bochsbios 2.2.5-1 | 1.158 | doesn't work Revision numbers come from the hexdump'ed binary bios images. There are quite a bit of changes between revision 1.130 of rombios.c, the version of bios.bin qemu author chosen to distribute, and 1.158, the version from the latest release of Bochs: http://cvs.sourceforge.net/viewcvs.py/bochs/bochs/bios/rombios.c?r1=1.158&r2=1.130 Could this be a reason for display corruption? Anyway I think someone more confident with the subject should make such decision. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
