Hi there,
I''ve been trying to find out why my X server is not working with xen
and
my ati radeon driver, this is what I''ve got
uname -a
Linux netwarrior 3.2.4-debian #1 SMP Sun Mar 11 22:50:18 ART 2012 x86_64
GNU/Linux
xorg.conf
Driver "fglrx"
grub config
menuentry ''Debian GNU/Linux, with Linux 3.2.4 Debian'' --class
debian
--class gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root=''(hd0,msdos1)''
search --no-floppy --fs-uuid --set 633a6cf2-a395-4721-8c94-d18b3824e32d
echo ''Loading Linux 3.2.4-Debian ...''
linux /boot/vmlinuz-3.2.4-debian root=/dev/sda1 ro
}
--
Not working configuration
menuentry ''Debian GNU/Linux, with Linux 3.2.4 Debian and XEN
4.1.2''
--class debian --class gnu-linux --class gnu --class os --class xen {
insmod part_msdos
insmod ext2
set root=''(hd0,msdos1)''
search --no-floppy --fs-uuid --set 71003eb6-abaa-49bf-99a0-c4fd2a85d773
echo ''Loading Linux 3.2.4 Debian ...''
multiboot /boot/xen-4.gz placeholder
module /boot/vmlinuz-3.2.4-debian placeholder root=/dev/sda1 ro
---
If I boot without the hypervisor I can run X without any problem,
booting up with the hypervisor xdm halts with the following
(EE) fglrx(0): V_BIOS address 0x0 out of range
(EE) fglrx(0): Invalid video BIOS signature!
(EE) fglrx(0): GetBIOSParameter failed
(EE) fglrx(0): PreInitAdapter failed
(EE) fglrx(0): PreInit failed
(EE) Screen(s) found, but none have a usable configuration.
Fatal server error:
no screens found
----
Now I found this thread:
http://forums.opensuse.org/english/get-technical-help-here/applications/398600-get-nvidia-work-xen-kernel.html
So, based on the thread above, does it mean that there is no way I can
make it work? I thought the kernel itself was responsible for managing
the devices, not the hypervisor.
Thanks for your time and support
Hi there,
I''ve been trying to find out why my X server is not working with xen
and
my ati radeon driver, this is what I''ve got
uname -a
Linux netwarrior 3.2.4-debian #1 SMP Sun Mar 11 22:50:18 ART 2012 x86_64
GNU/Linux
xorg.conf
Driver "fglrx"
grub config
menuentry ''Debian GNU/Linux, with Linux 3.2.4 Debian'' --class
debian
--class gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root=''(hd0,msdos1)''
search --no-floppy --fs-uuid --set
633a6cf2-a395-4721-8c94-d18b3824e32d
echo ''Loading Linux 3.2.4-Debian ...''
linux /boot/vmlinuz-3.2.4-debian root=/dev/sda1 ro
}
--
Not working configuration
menuentry ''Debian GNU/Linux, with Linux 3.2.4 Debian and XEN
4.1.2''
--class debian --class gnu-linux --class gnu --class os --class xen {
insmod part_msdos
insmod ext2
set root=''(hd0,msdos1)''
search --no-floppy --fs-uuid --set
71003eb6-abaa-49bf-99a0-c4fd2a85d773
echo ''Loading Linux 3.2.4 Debian ...''
multiboot /boot/xen-4.gz placeholder
module /boot/vmlinuz-3.2.4-debian placeholder root=/dev/sda1 ro
---
If I boot without the hypervisor I can run X without any problem,
booting up with the hypervisor xdm halts with the following
(EE) fglrx(0): V_BIOS address 0x0 out of range
(EE) fglrx(0): Invalid video BIOS signature!
(EE) fglrx(0): GetBIOSParameter failed
(EE) fglrx(0): PreInitAdapter failed
(EE) fglrx(0): PreInit failed
(EE) Screen(s) found, but none have a usable configuration.
Fatal server error:
no screens found
----
Now I found this thread:
http://forums.opensuse.org/english/get-technical-help-here/applications/398600-get-nvidia-work-xen-kernel.html
So, based on the thread above, does it mean that there is no way I can
make it work? I thought the kernel itself was responsible for managing
the devices, not the hypervisor.
Thanks for your time and support