On 2013-03-25 10:48, Gerd Hoffmann wrote: > On 03/25/13 10:32, Jan Kiszka wrote: >> On 2013-03-25 10:10, Gerd Hoffmann wrote: >>> On 03/25/13 09:40, Jan Kiszka wrote: >>>> On 2013-03-25 09:39, Gerd Hoffmann wrote: >>>>> Hi, >>>>> >>>>>>> Any hints in the X server log? >>>>>> >>>>>> "vmwlegacy(0): Weight given (565) is inconsistent with the >>>>>> depth (24)" >>>>> >>>>> Weight hints depth 16 indeed. What depth used the server to >>>>> run at? 16 or 24? >>>> >>>> 24 >>> >>> As expected. Puzzling where the 565 weight comes from ... >>> >>> Can you apply the attached patch, enable vmware_* + >>> displaysurface_* tracepoints + send a log? >> >> [shrinking CC list at this chance] > > Hmm, no displaysurface_* tracepoints?
Setting up a full trace was a bit too unhandy (it still lacks some ad-hoc configuration). If you need it, I'll redo. > >> read: index 1, value 0x0 read: index 2, value 0x320 read: index 3, >> value 0x258 > > 800x600 > >> read: index 7, value 0x20 > > 4 bytes per pixel > >> read: index 9, value 0xf800 read: index 10, value 0x7e0 read: index >> 11, value 0x1f > > 16bpp r/g/b masks. Hmm. > > No attempt to initialize the display (set res etc). Maybe because the > x11 server driver errors out early. > > The 800x600 video mode was probably set from vgabios. That doesn't > explain the inconsistency though. > > Do you boot with vesafb enabled? Which video mode? Probably 800x600? > What depth? I'm booting with vga=0x314. Jan
signature.asc
Description: OpenPGP digital signature
