Wolfram Quester wrote:
Hi, On Thu, Dec 01, 2005 at 05:59:11PM +0100, Attilio Fiandrotti wrote:Wolfram Quester wrote:Plese tell me how I can help to debug this issue. I will retry the graphical installer from time to time and follow up on this bug-report.Hi i suggest you to try booting with install video=ofonly DEBIAN_FRONTEND=newtthe installer should boot in text mode: if the boot process goes fine up to the moment the classic textual installation screen appears, then switch to VT2 and doexport DEBIAN_FRONTEND=gtk export MALLOC_CHECK_=1 debian-installera more detailed error message should be available if the graphical installer fails again.did that, it told me "MALLOC: using debug hooks", but nothing new. The error screen was too short to read, but starting it repeatedly I could only see the same as reported above. No entry in syslog. It does not create /var/log/X{org,Free86}.log. This would be nice to have in such cases, wouldn't it?
the g-i do not makes use of an X server, but instead it uses DirectFrameBuffer (see www.directframebuffer.org ), so no /var/log/X* is available. you can start the g-i in text mode and, after the newt frontend is loaded, switch to VT2 and type
echo 'debug' >/etc/directfbrc export DEBIAN_FRONTEND=gtk export MALLOC_CHECK_=1 debian-installer and see if DFB produces more output that before. when you start the
Permissions in /dev/fb look unsuspicious to me: ls -l /dev/fb* lrwxrwxrwx 1 root root 4 Dec 1 15:17 /dev/fb0 -> fb/0 /dev/fb: crw-rw---- 1 root root 0 Dec 1 15:17 /dev/fb/0 ls -ld /dev/fb drwxr-xr-x 2 root root 60 Dec 1 15:17 /dev/fb
they seem correct, in fact the DFB system start up (blue screen with "drop" cursor) as expected and only after it crashes. Since i've not PPC HW to test the g-i installer on i've forwarded your mail to directfb-dev@directfb.org, the mailing list for developing DFB.
I hope they can help us. (of course, thanks for testing the g-i! :) ciao Attilio