Xen project Mailing List

On Thu, Jun 26, 2014 at 8:15 PM, Brian Menges <bmenges@xxxxxxxxxx> wrote:

So I added back in swiotlb=force and redid grub and also removed from the blacklist fglrx_updates. Now when I try and startx, a CPU gets pegged @ 100%, and nothing still on the display.

Basically I'm never getting a display, even on boot of the vm.

- Brian Menges
Principal Engineer, DevOps
GoGrid | ServePath | ColoServe | UpStream Networks

-----Original Message-----

From: xen-users-bounces@xxxxxxxxxxxxx [mailto:xen-users-bounces@xxxxxxxxxxxxx] On Behalf Of Brian Menges
Sent: Thursday, June 26, 2014 19:05
To: Daniel Shub
Cc: xen-users@xxxxxxxxxxxxx
Subject: Re: [Xen-users] Help with VGA passthrough

Even starting the system in TEXT mode, the display doesn't show. But running 'startx' does result in some lovely errors:

http://pastebin.com/VbWhXe19

/var/log/Xorg.0.log (18:39) is the most interesting.

[ Â 839.985] (WW) fglrx(0): Kernel Module version does *not* match driver.
[ Â 839.985] (EE) fglrx(0): incompatible kernel module detected - HW accelerated OpenGL will not work
[ Â 839.986] (EE)
[ Â 839.986] (EE) Backtrace:
[ Â 839.986] (EE) 0: /usr/bin/X (xorg_backtrace+0x34) [0x7f38121971e4]
[ Â 839.986] (EE) 1: /usr/bin/X (0x7f3811fe0000+0x1bb0e9) [0x7f381219b0e9]
[ Â 839.986] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f3811306000+0xfcb0) [0x7f3811315cb0]
[ Â 839.986] (EE) 3: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/modules/drivers/fglrx_drv.so (swlDrmFreeSurfaces+0x42) [0x7f380e5c73b2]
[ Â 839.986] (EE) 4: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/modules/drivers/fglrx_drv.so (xdl_xs114_atiddxDriCloseScreen+0x14d) [0x7f380e58e47d]
[ Â 839.986] (EE) 5: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/modules/drivers/fglrx_drv.so (xdl_xs114_atiddxDriScreenInit+0x8eb) [0x7f380e58db1b]
[ Â 839.987] (EE) 6: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/modules/drivers/fglrx_drv.so (xdl_xs114_atiddxScreenInit+0xf82) [0x7f380e587572]
[ Â 839.987] (EE) 7: /usr/bin/X (AddScreen+0x8a) [0x7f3812035f8a]
[ Â 839.987] (EE) 8: /usr/bin/X (InitOutput+0x3e8) [0x7f3812079ac8]
[ Â 839.987] (EE) 9: /usr/bin/X (0x7f3811fe0000+0x4422d) [0x7f381202422d]
[ Â 839.987] (EE) 10: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xed) [0x7f380ff7b76d]
[ Â 839.987] (EE) 11: /usr/bin/X (0x7f3811fe0000+0x447c1) [0x7f38120247c1]
[ Â 839.987] (EE)
[ Â 839.987] (EE) Segmentation fault at address 0x8a0
[ Â 839.987] (EE)
Fatal server error:
[ Â 839.987] (EE) Caught signal 11 (Segmentation fault). Server aborting
[ Â 839.987] (EE)
[ Â 839.987] (EE)
Please consult the The X.Org Foundation support
Â Â Â Â Âat http://wiki.x.org
Âfor help.
[ Â 839.987] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ Â 839.987] (EE)
[ Â 839.995] (EE) Server terminated with error (1). Closing log file.

This runtime I did boot with the following options:
text iommu=soft

Previously, the options were:
quiet splash iommu=soft swiotlb=force

Per http://wiki.xen.org/wiki/Xen_PCI_Passthrough I should only need one of the two settings between iommu=soft or swiotlb=force, however not necessarily both.

- Brian Menges
Principal Engineer, DevOps
GoGrid | ServePath | ColoServe | UpStream Networks

-----Original Message-----
From: Daniel Shub [mailto:Daniel.Shub@xxxxxxxxxxxxxxxx]
Sent: Thursday, June 26, 2014 15:07
To: Brian Menges
Cc: xen-users@xxxxxxxxxxxxx
Subject: Re: [Xen-users] Help with VGA passthrough

What do you mean by a terminal window? Are you on tty7? Can you switch through the tty's? You might want to step back and instead of automatically launching lightdm, just try and get a tty over vnc without X and then start X and see what happens. It seems like you have passed the device through correctly.

> On 26 Jun 2014, at 17:53, "Brian Menges" <bmenges@xxxxxxxxxx> wrote:
>
> Yeah, definitely running.
>
> root Â Â Â 991 Â0.0 Â0.0 279164 Â3900 ? Â Â Â ÂSsl Â09:31 Â 0:00 lightdm
> root Â Â Â1020 99.6 Â0.1 Â68520 Â7964 tty7 Â Â Rs+ Â09:31 Â 4:48 Â\_ /usr/bin/X :0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7
>
> Chewing on an entire CPU ... which it seems that at some point my machine locks up.
>
> When I loaded VNC and attached into the console there... all I get is a terminal window, not the unity desktop. If I close it... nothing is startable.
>
> - Brian Menges
> Principal Engineer, DevOps
> GoGrid | ServePath | ColoServe | UpStream Networks
>
> -----Original Message-----
> From: xen-users-bounces@xxxxxxxxxxxxx
> [mailto:xen-users-bounces@xxxxxxxxxxxxx] On Behalf Of Gordan Bobic
> Sent: Thursday, June 26, 2014 09:18
> To: xen-users@xxxxxxxxxxxxx
> Subject: Re: [Xen-users] Help with VGA passthrough
>
> At a glance, I don't see an obvious problem in that log.
>
> Is you can ssh in can you check if Xorg is actually running?
>
>> On 2014-06-26 17:00, Brian Menges wrote:
>> Looks like it isn't using the driver correctly?
>> -----
>> [ Â Â 9.758]
>> X.Org X Server 1.14.5
>> Release Date: 2013-12-12
>> [ Â Â 9.758] X Protocol Version 11, Revision 0
>> [ Â Â 9.758] Build Operating System: Linux 2.6.42-37-generic x86_64
>> Ubuntu
>> [ Â Â 9.758] Current Operating System: Linux bmenges-linux3
>> 3.11.0-23-generic #40~precise1-Ubuntu SMP Wed Jun 4 22:06:36 UTC 2014
>> x86_64
>> [ Â Â 9.758] Kernel command line:
>> BOOT_IMAGE=/boot/vmlinuz-3.11.0-23-generic
>> root=UUID=784a946b-24ff-4fc7-b527-f5e822b17abd ro quiet splash
>> iommu=soft swiotlb=force vt.handoff=7
>> [ Â Â 9.758] Build Date: 06 January 2014 Â01:37:48PM
>> [ Â Â 9.758] xorg-server 2:1.14.5-1ubuntu2~saucy1~precise2 (For
>> technical support please see http://www.ubuntu.com/support)
>> [ Â Â 9.758] Current version of pixman: 0.30.2
>> [ Â Â 9.758] Â ÂBefore reporting problems, check http://wiki.x.org
>> Â Â Â Âto make sure that you have the latest version.
>> [ Â Â 9.758] Markers: (--) probed, (**) from config file, (==) default
>> setting,
>> Â Â Â Â(++) from command line, (!!) notice, (II) informational,
>> Â Â Â Â(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
>> [ Â Â 9.758] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Jun 26
>> 08:15:53 2014
>> [ Â Â 9.803] (==) Using config file: "/etc/X11/xorg.conf"
>> [ Â Â 9.803] (==) Using system config directory
>> "/usr/share/X11/xorg.conf.d"
>> [ Â Â 9.893] (==) ServerLayout "aticonfig Layout"
>> [ Â Â 9.893] (**) |-->Screen "aticonfig-Screen[0]-0" (0)
>> [ Â Â 9.893] (**) | Â |-->Monitor "aticonfig-Monitor[0]-0"
>> [ Â Â 9.905] (**) | Â |-->Device "aticonfig-Device[0]-0"
>> [ Â Â 9.905] (==) Automatically adding devices
>> [ Â Â 9.905] (==) Automatically enabling devices
>> [ Â Â 9.905] (==) Automatically adding GPU devices
>> [ Â Â 9.944] (WW) The directory "/usr/share/fonts/X11/cyrillic" does
>> not exist.
>> [ Â Â 9.944] Â ÂEntry deleted from font path.
>> [ Â Â 9.944] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not
>> exist.
>> [ Â Â 9.944] Â ÂEntry deleted from font path.
>> [ Â Â 9.944] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not
>> exist.
>> [ Â Â 9.944] Â ÂEntry deleted from font path.
>> [ Â Â 9.960] (WW) The directory "/usr/share/fonts/X11/100dpi" does not
>> exist.
>> [ Â Â 9.960] Â ÂEntry deleted from font path.
>> [ Â Â 9.960] (WW) The directory "/usr/share/fonts/X11/75dpi" does not
>> exist.
>> [ Â Â 9.960] Â ÂEntry deleted from font path.
>> [ Â Â 9.960] (==) FontPath set to:
>> Â Â Â Â/usr/share/fonts/X11/misc,
>> Â Â Â Â/usr/share/fonts/X11/Type1,
>> Â Â Â Âbuilt-ins
>> [ Â Â 9.960] (==) ModulePath set to
>> "/usr/lib/x86_64-linux-gnu/xorg/extra-modules,/usr/lib/xorg/extra-modules,/usr/lib/xorg/modules"
>> [ Â Â 9.960] (II) The server relies on udev to provide the list of
>> input devices.
>> Â Â Â ÂIf no devices become available, reconfigure udev or disable
>> AutoAddDevices.
>> [ Â Â 9.966] (II) Loader magic: 0x7f6ad345fc20
>> [ Â Â 9.966] (II) Module ABI versions:
>> [ Â Â 9.966] Â ÂX.Org ANSI C Emulation: 0.4
>> [ Â Â 9.966] Â ÂX.Org Video Driver: 14.1
>> [ Â Â 9.966] Â ÂX.Org XInput driver : 19.1
>> [ Â Â 9.966] Â ÂX.Org Server Extension : 7.0
>> [ Â Â 9.973] (--) PCI:*(0:0:2:0) 1013:00b8:5853:0001 rev 0, Mem @
>> 0xf0000000/33554432, 0xf3044000/4096
>> [ Â Â 9.973] (--) PCI: (0:0:5:0) 1002:6779:1682:3207 rev 0, Mem @
>> 0xe0000000/268435456, 0xf3000000/131072, I/O @ 0x0000c200/256, BIOS @
>> 0x????????/131072
>> [ Â Â 9.973] (II) Open ACPI successful (/var/run/acpid.socket)
>> [ Â Â 9.976] Initializing built-in extension Generic Event Extension
>> [ Â Â 9.976] Initializing built-in extension SHAPE
>> [ Â Â 9.976] Initializing built-in extension MIT-SHM
>> [ Â Â 9.976] Initializing built-in extension XInputExtension
>> [ Â Â 9.976] Initializing built-in extension XTEST
>> [ Â Â 9.976] Initializing built-in extension BIG-REQUESTS
>> [ Â Â 9.976] Initializing built-in extension SYNC
>> [ Â Â 9.976] Initializing built-in extension XKEYBOARD
>> [ Â Â 9.976] Initializing built-in extension XC-MISC
>> [ Â Â 9.976] Initializing built-in extension SECURITY
>> [ Â Â 9.976] Initializing built-in extension XINERAMA
>> [ Â Â 9.976] Initializing built-in extension XFIXES
>> [ Â Â 9.976] Initializing built-in extension RENDER
>> [ Â Â 9.976] Initializing built-in extension RANDR
>> [ Â Â 9.976] Initializing built-in extension COMPOSITE
>> [ Â Â 9.976] Initializing built-in extension DAMAGE
>> [ Â Â 9.976] Initializing built-in extension MIT-SCREEN-SAVER
>> [ Â Â 9.976] Initializing built-in extension DOUBLE-BUFFER
>> [ Â Â 9.976] Initializing built-in extension RECORD
>> [ Â Â 9.976] Initializing built-in extension DPMS
>> [ Â Â 9.976] Initializing built-in extension X-Resource
>> [ Â Â 9.976] Initializing built-in extension XVideo
>> [ Â Â 9.976] Initializing built-in extension XVideo-MotionCompensation
>> [ Â Â 9.976] Initializing built-in extension XFree86-VidModeExtension
>> [ Â Â 9.976] Initializing built-in extension XFree86-DGA
>> [ Â Â 9.976] Initializing built-in extension XFree86-DRI
>> [ Â Â 9.976] Initializing built-in extension DRI2
>> [ Â Â 9.976] (II) "glx" will be loaded. This was enabled by default
>> and also specified in the config file.
>> [ Â Â 9.976] (II) LoadModule: "glx"
>> [ Â Â10.098] (II) Loading
>> /usr/lib/x86_64-linux-gnu/xorg/extra-modules/modules/extensions/libglx.so
>> [ Â Â10.157] (II) Module glx: vendor="Advanced Micro Devices, Inc."
>> [ Â Â10.157] Â Âcompiled for 6.9.0, module version = 1.0.0
>> [ Â Â10.157] Loading extension GLX
>> [ Â Â10.157] (II) LoadModule: "fglrx"
>> [ Â Â10.215] (II) Loading
>> /usr/lib/x86_64-linux-gnu/xorg/extra-modules/modules/drivers/fglrx_drv.so
>> [ Â Â10.912] (II) Module fglrx: vendor="FireGL - AMD Technologies Inc."
>> [ Â Â10.912] Â Âcompiled for 1.4.99.906, module version = 13.25.5
>> [ Â Â10.912] Â ÂModule class: X.Org Video Driver
>> [ Â Â10.913] (II) Loading sub module "fglrxdrm"
>> [ Â Â10.913] (II) LoadModule: "fglrxdrm"
>> [ Â Â10.925] (II) Loading
>> /usr/lib/x86_64-linux-gnu/xorg/extra-modules/modules/linux/libfglrxdrm.so
>> [ Â Â10.947] (II) Module fglrxdrm: vendor="FireGL - AMD Technologies
>> Inc."
>> [ Â Â10.947] Â Âcompiled for 1.4.99.906, module version = 13.25.5
>> [ Â Â10.947] (II) AMD Proprietary Linux Driver Version
>> Identifier:13.25.5
>> [ Â Â10.947] (II) AMD Proprietary Linux Driver Release Identifier:
>> 13.251
>> [ Â Â10.947] (II) AMD Proprietary Linux Driver Build Date: Dec Â6 2013
>> 15:19:03
>> [ Â Â10.947] (++) using VT number 7
>>
>> [ Â Â10.947] (WW) Falling back to old probe method for fglrx
>> [ Â Â11.149] (II) Loading PCS database from /etc/ati/amdpcsdb
>> /etc/ati/amdpcsdb.default
>> [ Â Â11.152] ukiDynamicMajor: found major device number 250
>> [ Â Â11.152] ukiDynamicMajor: found major device number 250
>> [ Â Â11.152] ukiOpenByBusid: Searching for BusID PCI:0:5:0
>> [ Â Â11.152] ukiOpenDevice: node name is /dev/ati/card0
>> [ Â Â11.152] ukiOpenDevice: open result is 10, (OK)
>> -----
>>
>> - Brian Menges
>> Principal Engineer, DevOps
>> GoGrid | ServePath | ColoServe | UpStream Networks
>>
>> -----Original Message-----
>> From: xen-users-bounces@xxxxxxxxxxxxx
>> [mailto:xen-users-bounces@xxxxxxxxxxxxx] On Behalf Of Gordan Bobic
>> Sent: Thursday, June 26, 2014 08:43
>> To: xen-users@xxxxxxxxxxxxx
>> Subject: Re: [Xen-users] Help with VGA passthrough
>>
>>> On 2014-06-26 16:20, Brian Menges wrote:
>>> [root@xs ~]# lsmod | grep pciback
>>> [root@xs ~]# echo $?
>>> 1
>>> [root@xs ~]# modprobe pciback
>>> FATAL: Module pciback not found.
>>
>> Try:
>> modprobe xen-pciback
>>
>>> Xenserver 6.2 appears to be a CentOS 5.x (maybe 5.6) box.
>>
>> Ah - my bad. It must be Xenserver 7 that is based on EL6.
>>
>>> I installed the proprietary drivers in an Ubuntu 12.04 LTS VM, and
>>> it won't get past the splash screen (xencenter display) now after
>>> gpu assignment (console or gui). The Ubuntu drivers appear to do
>>> nothing;
>>> however:
>>>
>>> $ dmesg | grep -E '(fglrx|ATI|radeon|pci)'
>>> [ Â Â0.188377] PCI: Using host bridge windows from ACPI; if necessary,
>>> use "pci=nocrs" and report a bug
>>> [ Â Â0.251997] pci_bus 0000:00: root bus resource [bus 00-ff]
>>> [ Â Â0.252000] pci_bus 0000:00: root bus resource [io Â0x0000-0x0cf7]
>>> [ Â Â0.252000] pci_bus 0000:00: root bus resource [io Â0x0d00-0xffff]
>>> [ Â Â0.252000] pci_bus 0000:00: root bus resource [mem
>>> 0x000a0000-0x000bffff]
>>> [ Â Â0.252000] pci_bus 0000:00: root bus resource [mem
>>> 0xe0000000-0xfbffffff]
>>> [ Â Â0.252062] pci 0000:00:00.0: [8086:1237] type 00 class 0x060000
>>> [ Â Â0.253138] pci 0000:00:01.0: [8086:7000] type 00 class 0x060100
>>> [ Â Â0.254100] pci 0000:00:01.1: [8086:7010] type 00 class 0x010180
>>> [ Â Â0.254730] pci 0000:00:01.1: reg 0x20: [io Â0xc320-0xc32f]
>>> [ Â Â0.255652] pci 0000:00:01.2: [8086:7020] type 00 class 0x0c0300
>>> [ Â Â0.256222] pci 0000:00:01.2: reg 0x20: [io Â0xc300-0xc31f]
>>> [ Â Â0.257100] pci 0000:00:01.3: [8086:7113] type 00 class 0x068000
>>> [ Â Â0.257833] pci 0000:00:01.3: quirk: [io Â0x1f40-0x1f7f] claimed by
>>> PIIX4 ACPI
>>> [ Â Â0.258529] pci 0000:00:02.0: [1013:00b8] type 00 class 0x030000
>>> [ Â Â0.258684] pci 0000:00:02.0: reg 0x10: [mem 0xf0000000-0xf1ffffff
>>> pref]
>>> [ Â Â0.258799] pci 0000:00:02.0: reg 0x14: [mem 0xf3044000-0xf3044fff]
>>> [ Â Â0.259758] pci 0000:00:03.0: [5853:0001] type 00 class 0x010000
>>> [ Â Â0.259970] pci 0000:00:03.0: reg 0x10: [io Â0xc000-0xc0ff]
>>> [ Â Â0.260101] pci 0000:00:03.0: reg 0x14: [mem 0xf2000000-0xf2ffffff
>>> pref]
>>> [ Â Â0.261722] pci 0000:00:05.0: [1002:6779] type 00 class 0x030000
>>> [ Â Â0.268018] pci 0000:00:05.0: reg 0x10: [mem 0xe0000000-0xefffffff
>>> 64bit pref]
>>> [ Â Â0.276017] pci 0000:00:05.0: reg 0x18: [mem 0xf3000000-0xf301ffff
>>> 64bit]
>>> [ Â Â0.284008] pci 0000:00:05.0: reg 0x20: [io Â0xc200-0xc2ff]
>>> [ Â Â0.300024] pci 0000:00:05.0: reg 0x30: [mem 0xf3020000-0xf303ffff
>>> pref]
>>> [ Â Â0.301115] pci 0000:00:05.0: supports D1 D2
>>> [ Â Â0.301887] pci 0000:00:06.0: [1002:aa98] type 00 class 0x040300
>>> [ Â Â0.302169] pci 0000:00:06.0: reg 0x10: [mem 0xf3040000-0xf3043fff
>>> 64bit]
>>> [ Â Â0.303969] pci 0000:00:06.0: supports D1 D2
>>> [ Â Â0.332081] PCI: pci_cache_line_size set to 64 bytes
>>> [ Â Â1.309926] pci_bus 0000:00: resource 4 [io Â0x0000-0x0cf7]
>>> [ Â Â1.309930] pci_bus 0000:00: resource 5 [io Â0x0d00-0xffff]
>>> [ Â Â1.309933] pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff]
>>> [ Â Â1.309935] pci_bus 0000:00: resource 7 [mem 0xe0000000-0xfbffffff]
>>> [ Â Â1.310908] pci 0000:00:00.0: Limiting direct PCI/PCI transfers
>>> [ Â Â1.310954] pci 0000:00:01.0: PIIX3: Enabling Passive Release
>>> [ Â Â1.311000] pci 0000:00:01.0: Activating ISA DMA hang workarounds
>>> [ Â Â1.312047] pci 0000:00:02.0: Boot video device
>>> [ Â Â1.312215] pci 0000:00:05.0: Boot video device
>>> [ Â Â1.534735] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
>>> [ Â Â1.534744] pciehp: PCI Express Hot Plug Controller Driver version:
>>> 0.4
>>> [ Â Â1.576902] ehci-pci: EHCI PCI platform driver
>>> [ Â Â1.576942] ohci-pci: OHCI PCI platform driver
>>> [ Â Â1.692123] xenbus_probe_frontend: Device with no driver:
>>> device/pci/0
>>> [ Â Â6.180380] fglrx: module license 'Proprietary. (C) 2002 - ATI
>>> Technologies, Starnberg, GERMANY' taints kernel.
>>> [ Â Â6.185911] fglrx: module verification failed: signature and/or
>>> required key missing - tainting kernel
>>> [ Â Â6.193979] <6>[fglrx] Maximum main memory to use for locked dma
>>> buffers: 7247 MBytes.
>>> [ Â Â6.194094] <6>[fglrx] Â vendor: 1002 device: 6779 count: 1
>>> [ Â Â6.194835] <6>[fglrx] ioport: bar 4, base 0xc200, size: 0x100
>>> [ Â Â6.195932] <6>[fglrx] Kernel PAT support is enabled
>>> [ Â Â6.195960] <6>[fglrx] module loaded - fglrx 14.10.2 [May Â5 2014]
>>> with 1 minors
>>> [ Â Â6.753214] input: QEMU 0.10.2 QEMU USB Tablet as
>>> /devices/pci0000:00/0000:00:01.2/usb1/1-2/1-2:1.0/input/input3
>>> [ Â Â6.764783] input: HD-Audio Generic HDMI/DP,pcm=3 as
>>> /devices/pci0000:00/0000:00:06.0/sound/card0/input4
>>> [ Â 11.494543] <6>[fglrx] Firegl kernel thread PID: 1260
>>> [ Â 11.494773] <6>[fglrx] Firegl kernel thread PID: 1261
>>> [ Â 11.495004] <6>[fglrx] Firegl kernel thread PID: 1262
>>> [ Â 11.495154] <6>[fglrx] IRQ 78 Enabled
>>> [ Â 11.541569] <6>[fglrx] Reserved FB block: Shared offset:0,
>>> size:1000000
>>> [ Â 11.541571] <6>[fglrx] Reserved FB block: Unshared offset:f838000,
>>> size:4000
>>> [ Â 11.541572] <6>[fglrx] Reserved FB block: Unshared offset:f83c000,
>>> size:4c4000
>>> [ Â 11.541573] <6>[fglrx] Reserved FB block: Unshared offset:7fff4000,
>>> size:c000
>>>
>>> So my last boot I got in via SSH, however the displays aren't working.
>>> I first tried the HDMI (HDMI - HDMI) display then the DVI (DVI ->
>>> DisplayPort) display and my monitor isn't showing anything.
>>> Wodnering what I'm missing to get this display up and running.
>>
>> So it looks like fglrx loads successfully and finds the hardware. So
>> far so good. Can you check what your Xorg log says?
>>
>> Gordan
>>
>> _______________________________________________
>> Xen-users mailing list
>> Xen-users@xxxxxxxxxxxxx
>> http://lists.xen.org/xen-users
>>
>> ________________________________
>>
>> The information contained in this message, and any attachments, may
>> contain confidential and legally privileged material. It is solely
>> for the use of the person or entity to which it is addressed. Any
>> review, retransmission, dissemination, or action taken in reliance
>> upon this information by persons or entities other than the intended
>> recipient is prohibited. If you receive this in error, please contact
>> the sender and delete the material from any computer.
>>
>> _______________________________________________
>> Xen-users mailing list
>> Xen-users@xxxxxxxxxxxxx
>> http://lists.xen.org/xen-users
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxx
> http://lists.xen.org/xen-users
>
> ________________________________
>
> The information contained in this message, and any attachments, may contain confidential and legally privileged material. It is solely for the use of the person or entity to which it is addressed. Any review, retransmission, dissemination, or action taken in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you receive this in error, please contact the sender and delete the material from any computer.
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxx
> http://lists.xen.org/xen-users
This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it. Â Please do not use, copy or disclose the information contained in this message or in any attachment. ÂAny views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham.

This message has been checked for viruses but the contents of an attachment may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation.

________________________________

The information contained in this message, and any attachments, may contain confidential and legally privileged material. It is solely for the use of the person or entity to which it is addressed. Any review, retransmission, dissemination, or action taken in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you receive this in error, please contact the sender and delete the material from any computer.

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users

________________________________

The information contained in this message, and any attachments, may contain confidential and legally privileged material. It is solely for the use of the person or entity to which it is addressed. Any review, retransmission, dissemination, or action taken in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you receive this in error, please contact the sender and delete the material from any computer.

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users