<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><br class="Apple-interchange-newline">
</div>
<br><div><div>On Dec 14, 2009, at 5:44 PM, Adam Jackson wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>On Fri, 2009-12-11 at 17:14 -0500, Peter Jones wrote:<br><blockquote type="cite">On 12/11/2009 02:41 PM, Adam Williamson wrote:<br></blockquote><blockquote type="cite"><blockquote type="cite">On Thu, 2009-12-10 at 08:57 +0100, Matěj Cepl wrote:<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">File a bug please, attaching your xorg.conf, Xorg.0.log and output of<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">the dmesg command (all from inside of VB virtual machine, of course).<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">...aaaand (oh boy, I love it when a plan comes together) mark it as<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">blocking F13Beta , because I reckon this breaks beta criterion #4:<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><a href="https://fedoraproject.org/wiki/Fedora_13_Beta_Release_Criteria">https://fedoraproject.org/wiki/Fedora_13_Beta_Release_Criteria</a><br></blockquote></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">I like the sentiment here, but I'm not sure this is really in the<br></blockquote><blockquote type="cite">spirit of the criteria - Vasily, as I understand it, is still in the<br></blockquote><blockquote type="cite">process of implementing the support for UEFI on VirtualBox.<br></blockquote><br>There's at least two issues here.<br><br>One is that we're not shipping the native X driver for vbox video yet.<br>Last I checked this was because it's hidden away in the vbox source, and<br>didn't build against whatever X server we were shipping, and that vbox<br>upstream didn't _want_ it shipped externally yet because they hadn't<br>finalized the interface.<br><br></div></blockquote><div><br></div>Right, looks like it isn't good time to package vboxvideo.<br><br><blockquote type="cite"><div>The other is that the kernel doesn't seem to be binding an efifb device<br>to it,</div></blockquote><div><br></div><div>Kernel uses efifb, and progress bar with logo drawn in the center looks nice and correct. </div><br><blockquote type="cite"><div> and/or that it is and X is not noticing that and thus loads vesa<br>instead of fbdev.<br></div></blockquote><div><br></div><div>X detects fbdev right (at least X -configure creates xorg.conf with right driver), but it couldn't detect modes (resolution) </div><div>using fbdev, thus X loads vesa to somehow fill the gaps imho. </div><div><br></div><div>#0 fbdev_open (scrnIndex=<value optimized out>, dev=0x1501fc "/dev/fb0", namep=0x0) at fbdevhw.c:412</div><div>#1 0x0014fc80 in fbdevHWProbe (pPci=0x0, device=0x0, namep=0x0) at fbdevhw.c:442</div><div>#2 0x00c5e4b5 in FBDevProbe (drv=0x8236b00, flags=<value optimized out>) at fbdev.c:394</div><div>#3 0x080a7c4e in xf86CallDriverProbe (drv=0x8236b00, detect_only=0) at xf86Init.c:663</div><div>#4 0x080a92fe in InitOutput (pScreenInfo=0x8212500, argc=1, argv=0xbfd96fc4) at xf86Init.c:939</div><div>#5 0x0806ba2b in main (argc=1, argv=0xbfd96fc4, envp=0xbfd96fcc) at main.c:315 </div><div><br></div><div>fbdev_open with (,namep = 0x0,) doesn't call ioctl(/* /dev/fb0*/,FBIOGET_FSCREENINFO,), which might returns required information:</div><div><span class="Apple-style-span" style="font-family: Sans, Verdana, sans-serif; font-size: small; line-height: 18px; -webkit-border-horizontal-spacing: 2px; -webkit-border-vertical-spacing: 2px; "><pre style="overflow-x: auto; overflow-y: auto; ">(gdb) call ioctl(fd,0x4602,(void*)(&fix))
$2 = 0
(gdb) p fix
$3 = {id = "EFI VGA\0\0\0\0\0\0\0\0", smem_start = 0x80000000 <Address 0x80000000 out of bounds>, smem_len = 6291456, type = 0,
type_aux = 0, visual = 2, xpanstep = 0, ypanstep = 0, ywrapstep = 0, line_length = 4096, mmio_start = 0x0, mmio_len = 0, accel = 0,
reserved = {0, 0, 0}}</pre></span></div>ioctl(/* /dev/fb0*/,FBIOGET_FSCREENINFO,) called from fbdev_open with (,namep != 0x0,), but I am not sure how fbdevHWProbe(,namep != 0x0,) will affect probing algorithm and X working :) .</div><div><blockquote type="cite"><div><br>- ajax<br>-- <br>fedora-devel-list mailing list<br><a href="mailto:fedora-devel-list@redhat.com">fedora-devel-list@redhat.com</a><br>https://www.redhat.com/mailman/listinfo/fedora-devel-list</div></blockquote></div><br></body></html>