This new version of splashutils fixed some issues. Thanks a lot !! I have two remaining problems: 1. F2 doesn't switch back to silent when booting (even though i have evdev compiled in kernel). It does work though when shuting down - very odd. 2. At the middle of the boot (I think it's the console font service stage), the background image of the silent mode turns blank. The progress bar comes back automatically, but for the background to be displayed again, I need to go to verbose and back to silent. I'm using vesafb-tng, and livecd-2005.0 theme.
Ad 1. Please insert: for i in /sys/class/input/event* ; do echo -n "$i: " ; cat $i/device/driver/description ; done in line 170 in /sbin/splash-functions.sh, just before: local t=$(grep -si keyboard /sys/class/input/event*/device/driver/description | grep -o 'event[0-9]\+') Then, after you reboot, watch the initscripts messages (you'll have to switch to verbose) and see whether: /sys/class/input/event0: AT and PS/2 keyboard driver /sys/class/input/event1: PS/2 mouse driver are listed somewhere among them. Ad 2. Please have a look at http://dev.gentoo.org/~spock/projects/gensplash/troubleshooting.php#black and try removing any tty:x settings you have on your kernel command line.
OK, the system I tried to check the evdev thing, doesn't have an event1, only event0, even though it's got a usb mouse connected. I'll try that on my other computer too now. About the other thing, I removed tty:x from the kernel line, but the problem still exists. I'm not sure I understood what to do according to the troubleshooting you linked me too...
heh, sorry - I don't know what I was thinking about. The keyboard is the needed one. when I shutdown I get: /sys/class/input/event0: AT and PS/2 keyboard driver /sys/class/input/event1: cat /sys/class/input/event1/device/driver/description: no such file or directory When I boot up, I only get the first line (event0), probably because the usb drivers are not yet modprobed. But then what do I need the mouse for? Is it not the keyboard that I need?
Yup, it's the keyboard that is required, splashutils doesn't use the mouse for anything. Could you please try upgrading to 1.1.9.5 to see whether the problem still exists with this new version of splashutils?
spock, I will upgrade to 1.1.9.5 and report back here. In the meanwhile I have another problem. I removed the tty:8 from kernel line and it appears now it uses tty 12, which is the same one as syslog-ng's default. When the logger's service starts it corrupts the screen.
Oh, that shouldn't be a problem, as you can always use another tty for the silent splash screen. How about tty:13 instead of tty:8?
Both problems (ie. the keyboard input device thing, and the tty collision with syslog-ng) should be fixed once and for all in 1.1.9.6, so I'm closing the bug. In case they aren't, please comment/reopen :)
