Fedora Account System
Red Hat Associate
Red Hat Customer
Created attachment 377412 [details] log of X server lunched with built-in config Description of problem: X -server can't detect modes nor with built-in config neither X -configure, when running in VirtualBox with EFI support. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Configure VirtualBox machine Linux/Fedora 2. Add FC11 live CD in media manager and link with fresh created VM 3. Mark EFI support in VM settings 4. Launch VM Actual results: After nice Fedore picture boot appearing (drawn with efifb help), instead of X login dialog appears black screen. Expected results: Appearing Graphic Login screen. Additional info: Current workaround described in http://forums.virtualbox.org/viewtopic.php?f=15&t=24456 and further reading https://www.redhat.com/archives/fedora-devel-list/2009-December/msg00367.html might be helpful.
Created attachment 377413 [details] dmesg from VM
This is mostly that we don't have the vboxvideo driver packaged, I believe.
(In reply to comment #2) > This is mostly that we don't have the vboxvideo driver packaged, I believe. Atm, vboxvideo driver uses vgabios, but of course if vboxvideo driver has been packaged it'd simplified things.
(In reply to comment #2) > This is mostly that we don't have the vboxvideo driver packaged, I believe. Adam, Could you please clarify a bit how X server fetches information on the real EFI hardware?
is there a reason you're testing with f11 and not something a bit newer? (12 or rawhide) -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
(In reply to comment #5) > is there a reason you're testing with f11 and not something a bit newer? (12 or > rawhide) fc12 has the same issue, but EFI bits in 3.1 release have got not very good ACPI support so it bit tricky to launch fc12 in VBox/EFI. > > -- > Fedora Bugzappers volunteer triage team > https://fedoraproject.org/wiki/BugZappers
if f12 has the same issue, let's update to that release then. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.
Still the case.
i thought we have vboxvideo in now? that doesn't help?
sh-4.1# grep -i vbox /tmp/X.log sh-4.1# Seems not to be autoloaded. Also I remember vboxvideo wasn't good on EFI system because it wanted to use BIOS. Which is not possible with EFI. I'm using VirtualBox-3.2-3.2.12_68302_fedora14-1.x86_64 as EFI machine.
okay...can you post the whole X log and also check if xorg-x11-drv-vboxvideo package is installed (though it ought to be)? Thanks. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Created attachment 467398 [details] X.log from /tmp Nb. I do not see vboxvideo driver in /mnt/runtime/usr/lib64/xorg/modules . Shouldn't it be there?
(In reply to comment #13) > package is installed (though it ought to be)? Thanks. No, it shouldn't be. Whole VirtualBox with all its dependencies including Xorg driver are in RPMFusion-free: Name : VirtualBox-OSE Arch : x86_64 Version : 3.2.10 Release : 1.fc15 Size : 15 M Repo : rpmfusion-free-rawhide Summary : A general-purpose full virtualizer for PC hardware URL : http://www.virtualbox.org/wiki/VirtualBox License : GPLv2 or (GPLv2 and CDDL) Popis : A general-purpose full virtualizer and emulator for 32-bit and : 64-bit x86 based PC-compatible machines. Name : VirtualBox-OSE-guest Arch : x86_64 Version : 3.2.10 Release : 1.fc15 Size : 936 k Repo : rpmfusion-free-rawhide Summary : VirtualBox-OSE Guest Additions URL : http://www.virtualbox.org/wiki/VirtualBox License : GPLv2 or (GPLv2 and CDDL) Popis : Tools that utilize kernel modules for supporting integration : with the Host, including file sharing and tracking of mouse : pointer movement and X.org X11 video and mouse driver. Name : kmod-VirtualBox-OSE Arch : x86_64 Version : 3.2.10 Release : 1.fc15 Size : 5.8 k Repo : rpmfusion-free-rawhide Summary : Metapackage which tracks in VirtualBox-OSE kernel module for : newest kernel URL : http://www.virtualbox.org/wiki/VirtualBox License : GPLv2 or CDDL Popis : This is a meta-package without payload which sole purpose is to : require the VirtualBox-OSE kernel module(s) for the newest kernel. : to make sure you get it together with a new kernel. Closing as NOTABUG (meaning, not a bug in Fedora provided packages).