Re: fso-console-image problems

[Mr Dash Four <mr.dash.four@googlemail.com>]

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


> The framebuffer console was disabled in the kernel because it could make the 
> phone freeze when Xorg stopped...
>   
Should I refrain from attempting what JaMa suggested then?

On a separate note, I just checked my "fso-consol-image" inittab file 
and the last statement there is indeed as JaMa suggested: 
"1:2345:respawn:/sbin/getty 38400 tty1"

I am attaching the complete inittab file (hope the mailing list daemon 
won't mind!). I tried running at level 3 (changed the 5 in 
id:5:initdefault: to 3), but no luck there either - the same 
black-and-white stripes screen and that is it...

# /etc/inittab: init(8) configuration.
# $Id: inittab,v 1.91 2002/01/25 13:35:21 miquels Exp $

# The default runlevel.
id:5:initdefault:

# Boot-time system configuration/initialization script.
# This is run first except when booting in emergency (-b) mode.
si::sysinit:/etc/init.d/rcS

# What to do in single-user mode.
~~:S:wait:/sbin/sulogin

# /etc/init.d executes the S and K scripts upon change
# of runlevel.
#
# Runlevel 0 is halt.
# Runlevel 1 is single-user.
# Runlevels 2-5 are multi-user.
# Runlevel 6 is reboot.

l0:0:wait:/etc/init.d/rc 0
l1:1:wait:/etc/init.d/rc 1
l2:2:wait:/etc/init.d/rc 2
l3:3:wait:/etc/init.d/rc 3
l4:4:wait:/etc/init.d/rc 4
l5:5:wait:/etc/init.d/rc 5
l6:6:wait:/etc/init.d/rc 6
# Normally not reached, but fallthrough in case of emergency.
z6:6:respawn:/sbin/sulogin
# /sbin/getty invocations for the runlevels.
#
# The "id" field MUST be the same as the last
# characters of the device (after "tty").
#
# Format:
#  <id>:<runlevels>:<action>:<process>
#

1:2345:respawn:/sbin/getty 38400 tty1