Frans Pop wrote:
On Friday 05 January 2007 21:01, Roy Francis wrote:Comments/Problems: I am using the daily-build netinst image burnt onto a CDRW using cdrecord. Once the bootsplash is shown, I used installgui at boot-prompt. Booting is perfect in all respects until the framebuffer initialisation happens. A page full of DirectFB initialisation stuff is shown, then screen blanks and repeats the same thing.I used suspend (CTRL+S) to hold the screen.Nice trick that!
Gotta keep track of this!
Jan 5 23:00:40 log-output: (!) DirectFB/FBDev: No supported modes found in /etc/fb.modes and current mode not supported! Jan 5 23:00:40 log-output: (!) DirectFB/FBDev: Current mode's pixelformat: rgba 6/0, 6/0, 6/0, 0/0 (4bit)This is a known issue. See similar reports on this page: http://bugs.debian.org/rootskel
That should mean the istaller is tryying to access the 16 colours framebuffer device instead of the 16 bit fb device provided by vesafb. We need to understand why the mechanism that forces using the newt frontend when vesafb is missing did not work.
I think the kernel module for i810fb was not included with the CD image.That is correct. Currently only vesafb is supported and we don't expect to be able to support different drivers anytime soon.Could you provide the output of the following commands: # cat /proc/fb # cat /etc/directfbrc # /usr/lib/directfb-0.9.25/bin/dfbinfoTo get these most easily, boot the graphical installer with as extra parameter: DEBIAN_FRONTEND=newt.
IIRC, all those infos were recently made available also in hw-report, isn't it?
Attilio