This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] Getting X to work on XEN unstable / xenolinux 2.4.26

To: xen-devel@xxxxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Getting X to work on XEN unstable / xenolinux 2.4.26
From: Richard Ta-Min <tamin@xxxxxxxxxxxxxxx>
Date: Thu, 15 Jul 2004 23:56:49 -0400 (EDT)
Delivery-date: Fri, 16 Jul 2004 07:38:57 +0100
Envelope-to: steven.hand@xxxxxxxxxxxx
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx

I have recently messaged about not being able to use my marvell yukon 
ethernet card with XEN 1.2. I have switched to XEN unstable / xenolinux 
2.4.26 and now my ethernet card works fine. Many thanks to Dr Ian Pratt 
and Dr Keir Fraser for their quick response.

I am now trying to get X to work. My video card is ATI Radeon 9200. To get 
it to work properly even under regular linux I had to install a property 
FGLRX driver from ATI. When I try to 'startx' from xenolinux 2.4.26 
domain0 I get the following error.

Fatal server error:
Caught signal 11.  Server aborting

That segmentation fault is probably because the FGLRX driver does not work 
under XEN.

Next, I try to 'startx' again but this time with a basic 
/etc/X11/XF86Config file.
This is a basic XF86Config file that tries to use a generic VESA driver. 
This is the driver I used to load under regular linux before I installed 
the property FGLRX driver from ATI and for most purposes it works fine on 
regular linux.

I get the following error under xenolinux 2.4.26.  

(EE) VESA(0): unknown type(0xffffffff)=0xff
(II) VESA(0): EAX=0x00004f00, EBX=0x00000000, ECX=0x00000000, 
(II) VESA(0): ESP=0x00000ffa, EBP=0x00000000, ESI=0x00000000, 
(II) VESA(0): CS=0xc000, SS=0x0100, DS=0x0040, ES=0x0000, FS=0x0000, 
(II) VESA(0): EIP=0x00001cf4, EFLAGS=0x00003200
(II) VESA(0): code at 0x000c1cf4:
 fb fc 80 fc a0 0f 84 a5 f4 80 fc 4f 0f 84 e0 2e
 2e ff 36 9e 11 1e 06 66 60 50 0f b6 c4 d1 e0 3d
(II) stack at 0x00001ffa:
 00 06 00 00 00 32
(II) VESA(0): VESA BIOS not detected
(II) UnloadModule: "vesa"
(II) UnloadModule: "int10"
(II) Unloading /usr/X11R6/lib/modules/linux/libint10.a
(II) UnloadModule: "vbe"
(II) Unloading /usr/X11R6/lib/modules/libvbe.a
(EE) Screen(s) found, but none have a usable configuration.

Fatal server error:
no screens found

Is there any way to get FGLRX driver to work under Xen or if not to get 
the generic VESA driver to work so that I can have an X session.


This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
Xen-devel mailing list