[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-users] radeon/radeonhd issues with xen domU
I have been trying to export my ATI HD4350 graphics card to a domU. The device is blocked in Dom0 using pciback along with a few other devices and is visible in DomU. All other pci devices work fine. I first tried the radeonhd driver version 1.2.5. The tail end of the Xorg.0.log showed the following errors: (--) RADEONHD(0): Detected an RV710 on an unidentified card (II) RADEONHD(0): Mapped IO @ 0xfdee0000 to 0xb7a8b000 (size 0x00010000) (II) RADEONHD(0): PCIE Card Detected (EE) RADEONHD(0): Cannot allocate 0 bytes of memory for BIOS image (II) RADEONHD(0): Query for AtomBIOS Init: failed (**) RADEONHD(0): Using AtomBIOS for All (EE) RADEONHD(0): No AtomBIOS image found but required for AtomBIOS based mode setting (II) RADEONHD(0): Query for AtomBIOS Teardown: failed (II) UnloadModule: "radeonhd" (EE) Screen(s) found, but none have a usable configuration. Fatal server error: no screens found When starting X, the display would flash 3 times. I tried using the radeon driver, and received the following error in the Xorg log: (--) RADEONHD(0): Detected an RV710 on an unidentified card (II) RADEONHD(0): Mapped IO @ 0xfdee0000 to 0xb7a8b000 (size 0x00010000) (II) RADEONHD(0): PCIE Card Detected (EE) RADEONHD(0): Cannot allocate 0 bytes of memory for BIOS image (II) RADEONHD(0): Query for AtomBIOS Init: failed (**) RADEONHD(0): Using AtomBIOS for All (EE) RADEONHD(0): No AtomBIOS image found but required for AtomBIOS based mode setting (II) RADEONHD(0): Query for AtomBIOS Teardown: failed (II) UnloadModule: "radeonhd" (EE) Screen(s) found, but none have a usable configuration. Fatal server error: no screens found Strangely enough, installing the proprietary drivers from ATI will allow DomU and X to start up and some applications will function but utilities like flgrxinfo will error out. The end result was not stable. Has anyone been able to get this to work? Any hints or ideas? I am finding mixed information on the 'export video card to DomU' issue. Some people are claiming success, some say it is not possible. Any help would be much appreciated. General info about my system: DomU kernel version (matches Dom0): Linux version 2.6.26-2-xen-686 (Debian 2.6.26-19lenny2) (dannf@xxxxxxxxxx) (gcc version 4.1.3 20080704 (prerelease) (Debian 4.1.2-25)) #1 SMP Wed Nov 4 23:23:33 UTC 2009 DomU cmdline: root=/dev/xvda1 ro console=hvc0 swiotlb=force quiet xorg.conf: # xorg.conf (X.Org X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the xorg.conf manual page. # (Type "man xorg.conf" at the shell prompt.) # # This file is automatically updated on xserver-xorg package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xorg # package. # # If you have edited this file but would like it to be automatically updated # again, run the following command: # sudo dpkg-reconfigure -phigh xserver-xorg Section "InputDevice" Identifier "Generic Keyboard" Driver "kbd" Option "XkbRules" "xorg" Option "XkbModel" "pc104" Option "XkbLayout" "us" EndSection Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" EndSection Section "Device" Identifier "ATI" Driver "radeonhd" BusID "PCI:0:1:0" EndSection #Section "Monitor" # Identifier "Configured Monitor" #EndSection Section "Screen" Identifier "Default Screen" # Monitor "Configured Monitor" EndSection _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |