[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#401681: marked as done (DirectFB should always use the vesa fb device on i386)

Your message dated Fri, 28 Feb 2014 20:47:10 +0100
with message-id <20140228194710.GA28582@mraw.org>
and subject line Re: Bug#400898: More informations needed to fix this bug
has caused the Debian Bug report #400898,
regarding DirectFB should always use the vesa fb device on i386
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
400898: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=400898
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
package: rotskel-gtk
severity: normal
tags: patch

At boot time, on i386, "video=vesa" is passed to the kernel to start the
framebuffer device /dev/fb0 via vesafb driver (built into the kernel).
Later in the boot process, the vga16fb module is loaded, and a second
framebuffer device, /dev/fb1 is created, but sometimes, why i don't
know, the fb devices minor numbers end up swapped.
By default DirectFB accesses the first available fb device (/dev/fb0)
and as 4 bit modes provided by vga16 are not supported, it fails
initializing.
The attached patch takes care of adding to DirectFB configuration file
(/etc/directfbrc) a line indicating what fb device has to be used (the
one provided by vesafb).
A miniiso [1] including this patch is available for testing.

Attilio Fiandrotti

[1] https://debian.polito.it/downloads/mini_vesafbonly.iso

Index: src/lib/debian-installer.d/S61choose-fb-device-x86
===================================================================
--- src/lib/debian-installer.d/S61choose-fb-device-x86	(revisione 0)
+++ src/lib/debian-installer.d/S61choose-fb-device-x86	(revisione 0)
@@ -0,0 +1,7 @@
+#This script takes care of making DirectFB use the vesa fb device, as other
+#fb devices may exist
+
+if [ "$DEBIAN_FRONTEND" = gtk ] ; then
+	FB_INDEX=$(grep -i vesa /proc/fb | cut -d " " -f 1 )
+	echo "fbdev=/dev/fb"$FB_INDEX >> /etc/directfbrc
+fi
Index: src/lib/debian-installer.d/Makefile
===================================================================
--- src/lib/debian-installer.d/Makefile	(revisione 43160)
+++ src/lib/debian-installer.d/Makefile	(copia locale)
@@ -20,7 +20,8 @@
 
 ifneq (,$(filter i386 amd64,$(DEB_HOST_ARCH_CPU)))
    files += \
-	S61mouse-support-x86
+	S61mouse-support-x86\
+	S61choose-fb-device-x86
 endif
 ifneq (,$(filter powerpc,$(DEB_HOST_ARCH_CPU)))
    files += \

--- End Message ---
--- Begin Message --- 
Attilio Fiandrotti <attilio.fiandrotti@gmail.com> (2006-12-10):
> It looks like vesafb was unable to start on your Geforce, hence no
> /dev/fb0 was provided: we aready experience that for Inlel 82810 and
> S3ViRGE DX.
> Another user reported fb0 (vesa) and fb1 (vga 16 colours) being
> swapped on a grforce go 6200, but he was later unable to reroduce
> the swap.
> I prepared a patch that disables the graphical frontend in the case
> vesafb cannot be started at boot time and this iso [1] includes the
> patch.
> The patch should detect lack of vesafb fb device and falback to the
> classical textual installer, could you please test and report
> whether it works or not?

We haven't heard back from the submitter in a very long while, the
kernel development pace is very high, so I'm going to assume this bug
hasn't bitten anyone in a while. Closing accordingly.

Mraw,
KiBi.

Attachment: signature.asc
Description: Digital signature


--- End Message ---
Reply to: