Using my own 2.4.22-3mdkcustom, everything is fine when
CONFIG_FBCON_SPLASHSCREEN is not defined.
Just defining it make the kernel fails at boot, as soon as syslog is launched.
The error message is "unable to handle null pointer dereference at virtual
adress 00000004". Just turning off syslog service is OK to prevent the
problem.
When looking at the /boot directory, the config and System.map symlinks have
been changed to point at wrong files, meaning System.map and vmlinuz doesn't
match, which should explain syslog problem. However, it doesn't explain what
changed them.
I don't have any initrd file that should contains the splash screen.
Very strange...
--
Guillaume Rousse
The least useful horse in your barn will eat the most, require shoes every
four weeks and need the vet at least once a month
-- Murphy's Horse Laws n�4
