Bug#493901: xserver-xorg-core: X fails to start in a Xen DomU (using Xen Framebuffer)

[Olivier Tétard]

Quoting Julien Cristau [EMAIL PROTECTED]:


This is supposed to be addressed by patch 47_fbdevhw_magic_numbers.diff.


I didn't see this patch (which was disabled in 1.3.99.0-1). I  
re-enabled it and then recompiled xorg-server and it solves correctly  
this problem.


Thanks,
Olivier;

--
gpg --keyserver pgp.mit.edu --recv-keys 0x43CEA851
__
Olivier Tétard - toutoune25
site : http://toutoune25.miskin.fr/
Jabber : [EMAIL PROTECTED]
__





--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#493901: xserver-xorg-core: X fails to start in a Xen DomU (using Xen Framebuffer)

[Julien Cristau]

On Tue, Aug  5, 2008 at 21:32:03 +0200, Olivier Tétard wrote:

 Xen kernel could be compiled with framebuffer support
 (CONFIG_XEN_FRAMEBUFFER) which was introduced in Xen 3.0.4. Then, DomU
 should supports framebuffer output and should be able to get X running
 in it.
 
 I tried this but it fails with this error:
 
 ,[ /var/log/Xorg.0.log ]
 | [...]
 | (EE) FBDEV(0): FBIOPUT_VSCREENINFO succeeded but modified mode
 | (EE) FBDEV(0): mode initialization failed
 | 
 | Fatal server error:
 | AddScreen/ScreenInit failed for driver 0
 `
 
 I found a way to solves this problem by patching the xorg-server
 package with this patch[1] which comes from Novel's bugtracker[2].
 
 1. https://bugzilla.novell.com/attachment.cgi?id=161573
 2. https://bugzilla.novell.com/show_bug.cgi?id=285523
 
This is supposed to be addressed by patch 47_fbdevhw_magic_numbers.diff.
Figures.

Cheers,
Julien



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]