The patches below to rootskel and rootskel-gtk combine your original patch
and the later one and also keep the bulk of the work where it belongs:
in rootskel-gtk.
Please check.
Index: rootskel-gtk/src/lib/debian-installer.d/Makefile
Attilio Fiandrotti wrote:
Today i had the chance to test the g-i on my friend's laptop, who
yesterday reported g-i crash and swapped fb0 fb1 devices (actually he
owns a GeForce 6200 Go)
I repeated the test using the very same ISO as yesterday and, this time,
vesa was correctly mapped fb0 and
reassign 401685 rootskel
retitle 401685 GTK frontend should be started on x86 iff fb0 is vesa
thanks
Attilio Fiandrotti wrote:
Otavio Salvador wrote:
Attilio Fiandrotti <[EMAIL PROTECTED]> writes:
The attached patch takes care of adding to DirectFB configuration file
(/etc/directfbrc) a lin
Processing commands for [EMAIL PROTECTED]:
> reassign 401685 rootskel
Bug#401685: DirectFB should always use the vesa fb device on i386
Bug#401681: DirectFB should always use the vesa fb device on i386
Bug reassigned from package `rootskel-gtk' to `rootskel'.
> retitle 401685 GTK
Otavio Salvador wrote:
Attilio Fiandrotti <[EMAIL PROTECTED]> writes:
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).
Nice patch. Works fine here. (but it worked before too
Attilio Fiandrotti <[EMAIL PROTECTED]> writes:
> 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).
Nice patch. Works fine here. (but it worked before too, so no
regressions to
package: rootskel-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
7 matches
Mail list logo
