[gentoo-catalyst] mkxf86config: Virtualbox experience

[gentoo-catalyst] mkxf86config: Virtualbox experience

[Pongracz Istvan]

Hi,

I use virtualbox/qemu to test the livecds.
I know, I will not really popular, but I expected that, if mkxf86 could
not detect the video card, it left empty the driver, instead of vesa
driver. Their video card name is a really strange name.

Is that possible to make the default driver to "vesa", instead of ""?
And I have no patch for this, sorry.

I try to help this project with my experience to achieve a
better-than-any-other livecd, so, sorry for my mails.
And I know, to make a criticism is easier than make a solution from
scratch, so, I do not need warn about it. I try to ask good questions
which could be constructive :)

Cheers, 
István


-- 
BSA. Mert megérdemlitek.
Open Source. Mert megérdemlem.
--
BSA. They value it.
Open Source. The value. It.
--
http://www.osbusiness.hu

-- 
gentoo-catalyst@lists.gentoo.org mailing list

Re: [gentoo-catalyst] mkxf86config: Virtualbox experience

[Andrew Gaffney]

Pongracz Istvan wrote:
> Hi,
> 
> I use virtualbox/qemu to test the livecds.
> I know, I will not really popular, but I expected that, if mkxf86 could
> not detect the video card, it left empty the driver, instead of vesa
> driver. Their video card name is a really strange name.
> 
> Is that possible to make the default driver to "vesa", instead of ""?

It should already do this. Are you sure you have x11-drivers/xf86-video-vesa on 
your CD? I believe it checks to make sure the driver exists before sticking it 
in the xorg.conf.

-- 
Andrew Gaffney                                 http://dev.gentoo.org/~agaffney/
Gentoo Linux Developer             Catalyst/Installer + x86 release coordinator
-- 
gentoo-catalyst@lists.gentoo.org mailing list

Re: [gentoo-catalyst] mkxf86config: Virtualbox experience

[Pongracz Istvan]

2008. 02. 26, kedd keltezéssel 07.33-kor Andrew Gaffney ezt írta:
> Pongracz Istvan wrote:
> > Hi,
> > 
> > I use virtualbox/qemu to test the livecds.
> > I know, I will not really popular, but I expected that, if mkxf86 could
> > not detect the video card, it left empty the driver, instead of vesa
> > driver. Their video card name is a really strange name.
> > 
> > Is that possible to make the default driver to "vesa", instead of ""?
> 
> It should already do this. Are you sure you have x11-drivers/xf86-video-vesa on 
> your CD? I believe it checks to make sure the driver exists before sticking it 
> in the xorg.conf.


Hi,

Yes, I am sure, because usually I simply write the "vesa" inside the
xorg.conf to the relevant section and X starts smoothly, without problem
and I am able to use X.

Videocard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter

Video is InnoTek Systemberatung GmbH VirtualBox Graphics Adapter, using
Xorg Server


This is without installing virtualbox-additions to the livecd.

The only problem with this, vesa is not the default card in this
specific case.

Cheers,
István


-- 
BSA. Mert megérdemlitek.
Open Source. Mert megérdemlem.
--
BSA. They value it.
Open Source. The value. It.
--
http://www.osbusiness.hu

-- 
gentoo-catalyst@lists.gentoo.org mailing list

Re: [gentoo-catalyst] mkxf86config: Virtualbox experience

[lurker]

[-- Attachment #1: Type: text/plain, Size: 1549 bytes --]

On 26/02/08 14:59, Pongracz Istvan wrote:
> 2008. 02. 26, kedd keltezéssel 07.33-kor Andrew Gaffney ezt írta:
>> Pongracz Istvan wrote:
>>> Hi,
>>>
>>> I use virtualbox/qemu to test the livecds.
>>> I know, I will not really popular, but I expected that, if mkxf86 could
>>> not detect the video card, it left empty the driver, instead of vesa
>>> driver. Their video card name is a really strange name.
>>>
>>> Is that possible to make the default driver to "vesa", instead of ""?
>> It should already do this. Are you sure you have x11-drivers/xf86-video-vesa on 
>> your CD? I believe it checks to make sure the driver exists before sticking it 
>> in the xorg.conf.
> 
> 
> Hi,
> 
> Yes, I am sure, because usually I simply write the "vesa" inside the
> xorg.conf to the relevant section and X starts smoothly, without problem
> and I am able to use X.

I've attached two patches that I apply when running fsscript. I believe
that the xorg.conf.in.patch is most essential, as it adds a second video
card as vesa and screen with default resolution settings as a sort of
fallback.

Beware that they might be outdated for your version of mkxf86config.

> Videocard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter
> 
> Video is InnoTek Systemberatung GmbH VirtualBox Graphics Adapter, using
> Xorg Server
> 
> 
> This is without installing virtualbox-additions to the livecd.
> 
> The only problem with this, vesa is not the default card in this
> specific case.
> 
> Cheers,
> István
> 
> 


[-- Attachment #2: xorg.conf.in.patch --]
[-- Type: text/plain, Size: 1493 bytes --]

--- etc/X11/xorg.conf.in.orig	2007-09-19 10:38:43.000000000 -0500
+++ etc/X11/xorg.conf.in	2007-09-20 10:55:46.000000000 -0500
@@ -1,6 +1,7 @@
 Section "ServerLayout"
-	Identifier	"X.Org Configured"
+	Identifier	"Automatically Configured"
 	Screen	0	"Screen0" 0 0
+	Screen	0	"ScreenVesa" 0 0
 	InputDevice	"Keyboard0" "CoreKeyboard"
 	InputDevice	"PS/2 Mouse" "AlwaysCore"
 #	InputDevice	"Serial Mouse" "AlwaysCore"
@@ -85,6 +86,7 @@
 	Driver	"kbd"
 	Option	"CoreKeyboard"
 	Option	"XkbRules" "xorg"
+	Option	"XkbLayout" "us"
 	Option	"XkbModel" "pc105"
 #	Option	"XkbOptions" "grp:toggle,grp_led:scroll"
 	Option	"XkbVariant" ",winkeys"
@@ -163,6 +165,11 @@
 #	BusID       "PCI:1:0:0"
 EndSection
 
+Section "Device"
+	Identifier  "CardVesa"
+	Driver      "vesa"
+EndSection
+
 Section "Screen"
 	Identifier	"Screen0"
 	Device	"Card0"
@@ -198,6 +205,41 @@
 	EndSubSection
 EndSection
 
+Section "Screen"
+	Identifier	"ScreenVesa"
+	Device	"CardVesa"
+	Monitor	"Monitor0"
+	DefaultColorDepth 24
+	SubSection "Display"
+		Depth	1
+		@@MODES@@
+	EndSubSection
+	SubSection "Display"
+		Depth	4
+		@@MODES@@
+	EndSubSection
+	SubSection "Display"
+		Depth	8
+		@@MODES@@
+	EndSubSection
+	SubSection "Display"
+		Depth	15
+		@@MODES@@
+	EndSubSection
+	SubSection "Display"
+		Depth	16
+		@@MODES@@
+	EndSubSection
+	SubSection "Display"
+		Depth	24
+		@@MODES@@
+	EndSubSection
+	SubSection "Display"
+		Depth	32
+		@@MODES@@
+	EndSubSection
+EndSection
+
 Section "DRI"
 	Mode 0666
 EndSection

[-- Attachment #3: mkxf86config.sh.patch --]
[-- Type: text/plain, Size: 1251 bytes --]

--- usr/sbin/mkxf86config.sh.orig	2007-05-24 15:25:55.000000000 -0500
+++ usr/sbin/mkxf86config.sh	2007-06-01 07:03:47.000000000 -0500
@@ -98,6 +98,16 @@
 	esac
 fi
 
+# Pick a default if no module is defined or it does not exist
+DRIVER_PATH="/usr/lib/xorg/modules/drivers"
+if [ -z "${XMODULE}" -o ! -e "${DRIVER_PATH}/${XMODULE}_drv.so" ]; then
+	if [ -e "/dev/fb" -a -e "${DRIVER_PATH}/fbdev_drv.so" ]; then
+		XMODULE="fbdev"
+	elif [ -e "${DRIVER_PATH}/vesa_drv.so" ]; then
+		XMODULE="vesa"
+	fi
+fi
+
 # We used to use ddcxinfo-knoppix for monitor information, now we will just let
 # X choose for itself.  This will probably break older machines.
 # You can uncomment the following to re-enable dccxinfo-knoppix, but this only
@@ -250,7 +260,7 @@
     -e 's|@@XMODULE@@|'"${XMODULE}"'|g;'"${VMWARE}""${VPC}""${SERIALMOUSE}""${USBMOUSE}""${PSMOUSE}""${SWCURSOR}""${WHEEL}""${SYNMOUSE}""${MOUSEDRIVER}" \
     -e 's|@@SYNDEV@@|'"${SYNDEV}"'|g' \
     -e 's|@@MODES@@|'"${MODES}"'|g;'"${DEPTH}" \
-    -e 's|"XkbLayout" *"[^"]*"|"XkbLayout" "'"${XKEYBOARD}"'"|g;'"${DEADKEYS}" \
+    ${XKEYBOARD:+-e 's|"XkbLayout" *"[^"]*"|"XkbLayout" "'"${XKEYBOARD}"'"|g;'"${DEADKEYS}"} \
     /etc/X11/xorg.conf.in >/etc/X11/xorg.conf
 
 if [ -n "${DPMS}" ]

Re: [gentoo-catalyst] mkxf86config: Virtualbox experience

[Pongracz Istvan]

Thank you for your help!!

I will migrate to my system soon.

Cheers,
István


-- 
BSA. Mert megérdemlitek.
Open Source. Mert megérdemlem.
--
BSA. They value it.
Open Source. The value. It.
--
http://www.osbusiness.hu

-- 
gentoo-catalyst@lists.gentoo.org mailing list

Re: [gentoo-catalyst] mkxf86config: Virtualbox experience

[Chris Gianelloni]

On Tue, 2008-02-26 at 11:24 +0100, Pongracz Istvan wrote:
> Is that possible to make the default driver to "vesa", instead of ""?

This is a discussion forum.  If you have feature requests, file a bug
report.

> And I have no patch for this, sorry.

Well, patches are about the only way you're going to get many of these
things changed, especially since I sometimes have a hard time following
what you're asking.  Patches are simple and are quite explicit about
what changes you want/intend.

-- 
Chris Gianelloni
Release Engineering Strategic Lead
Games Developer
-- 
gentoo-catalyst@lists.gentoo.org mailing list

Re: [gentoo-catalyst] mkxf86config: Virtualbox experience

[Chris Gianelloni]

On Wed, 2008-02-27 at 12:39 +0100, lurker wrote:
> I've attached two patches that I apply when running fsscript. I believe
> that the xorg.conf.in.patch is most essential, as it adds a second video
> card as vesa and screen with default resolution settings as a sort of
> fallback.

The patches look pretty good, but you cannot enable VESA by default,
especially since mkxf86config works on more than amd64/x86 and only
amd64/x86 have VESA.

> Beware that they might be outdated for your version of mkxf86config.

-- 
Chris Gianelloni
Release Engineering Strategic Lead
Games Developer
-- 
gentoo-catalyst@lists.gentoo.org mailing list

Re: [gentoo-catalyst] mkxf86config: Virtualbox experience

[lurker]

On 27/02/08 19:36, Chris Gianelloni wrote:
> On Wed, 2008-02-27 at 12:39 +0100, lurker wrote:
>> I've attached two patches that I apply when running fsscript. I believe
>> that the xorg.conf.in.patch is most essential, as it adds a second video
>> card as vesa and screen with default resolution settings as a sort of
>> fallback.
> 
> The patches look pretty good, but you cannot enable VESA by default,
> especially since mkxf86config works on more than amd64/x86 and only
> amd64/x86 have VESA.

Yup, but I only use this for an x86 project of mine. Feel free to add
the parts you like to the ebuild in portage if you see any worth in it.



-- 
gentoo-catalyst@lists.gentoo.org mailing list