Summary: After upgrading to 1.5.1 F2 does not switch modes during boot. 1. During boot F2 does not switch to verbose mode. In 4 boots I could switch to verbose only once but even then I was unable to switch back to silent mode. 2. F2 works fine during shutdown. 3. Following a request from bug 188578, I added "profile" to the grub boot line, found the line "18.78: comm set event dev /dev/input/event0" but there is no file/dir with the name "/sys/class/input/event8/device/name". Only the dir "/sys/class/input/event8/device".
(In reply to comment #0) ... > 1. During boot F2 does not switch to verbose mode. > In 4 boots I could switch to verbose only once but even then I was unable to > switch back to silent mode. I tried a few boots and it seems that F2 can change to verbose mode if pressed immediately after the message "Booting the system ..." appears, i.e. after it replaces the "Initializing the kernel" one. 1 second later and F2 didn't go into verbose mode. When entering into verbose mode, I was unable to go back to silent mode again. May be this helps ...
(In reply to comment #0) ... > 3. Following a request from bug 188578, I added "profile" to the grub boot > line, found the line "18.78: comm set event dev /dev/input/event0" but there is > no file/dir with the name "/sys/class/input/event8/device/name". Only the dir > "/sys/class/input/event8/device". Of course I meant "/sys/class/input/event0/device/name". I just copied the line from bug 188578 and forgot to change 8 to 0. Sorry ...
Try w/ 1.5.1.1 please.
(In reply to comment #3) > Try w/ 1.5.1.1 please. > Didn't change anything. Exactly the same symptoms ... I booted twice and I could also confirm what I posted in comment #1. Since 1.5.1.1 is not yet in the tree, I copied ebuild 1.5.1 to 1.5.1-r1 (overlay). In this one I replaced GENTOOSPLASH="splashutils-gentoo-1.0.6" by GENTOOSPLASH="splashutils-gentoo-1.0.7". Then the usual procedure ... ebuild ... digest and emerge.
(In reply to comment #4) > Since 1.5.1.1 is not yet in the tree Sure it is, emerge --sync please and try with the official ebuilds, not some home-made one. :)
(In reply to comment #5) > (In reply to comment #4) > > Since 1.5.1.1 is not yet in the tree > > Sure it is, emerge --sync please and try with the official ebuilds, not some > home-made one. :) > OK! Now it is in the tree ... F2 still does not work however ... Same reported symptoms. Just in case I previously unmerged splashutils and then emerged splashutils 1.5.1.1.
Hmmm.
Could you please paste the output of: for i in /sys/class/input/input*/name ; do echo -n "$i: " ; cat $i ; done
(In reply to comment #8) > Could you please paste the output of: > > for i in /sys/class/input/input*/name ; do echo -n "$i: " ; cat $i ; done > /sys/class/input/input0/name: AT Translated Set 2 keyboard /sys/class/input/input1/name: Logitech USB Receiver /sys/class/input/input2/name: Power Button (FF) /sys/class/input/input3/name: Power Button (CM) /sys/class/input/input4/name: Lid Switch /sys/class/input/input5/name: PC Speaker /sys/class/input/input6/name: SynPS/2 Synaptics TouchPad
Looks like event0 is the correct device for your keyboard. Please attach your /lib/splash/cache/profile file (reboot with 'profile' in the splash settings to make sure the file is freshly generated). Do you have the event device driver built into the kernel, or are you using it as a module?
(In reply to comment #10) > Looks like event0 is the correct device for your keyboard. Please attach your > /lib/splash/cache/profile file (reboot with 'profile' in the splash settings to > make sure the file is freshly generated). > > Do you have the event device driver built into the kernel, or are you using it > as a module? > As a module (evdev).
Created attachment 130119 [details] The profile as requested
Hmm, perhaps try compiling evdev into the kernel -- I guess this will fix the problem. Two more things: - which version of baselayout are you using? - try running splash_manager -c replay -t <whatever_theme_you're_using> after booting with the 'profile' option, and check whether the F2 key works then.
(In reply to comment #13) > Hmm, perhaps try compiling evdev into the kernel -- I guess this will fix the > problem. > I'll try that later ... > Two more things: > - which version of baselayout are you using? 1.12.9-r2 > - try running splash_manager -c replay -t <whatever_theme_you're_using> > after booting with the 'profile' option, and check whether the F2 key > works then. Yes, it works. It also works when shutting down, as I wrote before.
... > > Hmm, perhaps try compiling evdev into the kernel -- I guess this will fix the > > problem. > > > I'll try that later ... Just one more thing ... With splashutils 1.4.3: F2 works fine, even with evdev module.
(In reply to comment #14) > (In reply to comment #13) > > Hmm, perhaps try compiling evdev into the kernel -- I guess this will fix the > > problem. > > > I'll try that later ... > Yes. Building evdev into the kernel, F2 works as expected.
(In reply to comment #15) > With splashutils 1.4.3: F2 works fine, even with evdev module. Have you actually tried downgrading to 1.4.3 after you noticed that F2 doesn't work in 1.5?
(In reply to comment #17) > (In reply to comment #15) > > > With splashutils 1.4.3: F2 works fine, even with evdev module. > > Have you actually tried downgrading to 1.4.3 after you noticed that F2 doesn't > work in 1.5? > Hmm, I see what you mean ... I did it a few of minutes ago and the situation now is as follows for 1.4.3: 1. I can *always* switch into verbose mode. I cannot go back to silent mode again. 2. During shutdown F2 works as expected. What happened in the meanwhile? Well I performed a two weekly major upgrade of my gentoo from 2007-9-3 to 2007-9-5.
The usual suspects here would be udev and baselayout. Have you upgraded any of these two during the last weeks? (please check your emerge.log)
(In reply to comment #19) > The usual suspects here would be udev and baselayout. Have you upgraded any of > these two during the last weeks? (please check your emerge.log) > They were both updated on Aug-21. None of them was updated on last update. Notice, however, that F2 is in general used to go into verbose mode to check for eventual problems after a crash or a system hang. I have an average of 1 per day of these events because my wireless/USB connection hangs. I need to reboot to regain communications and I use F2 when it happens to see if everything is right. As I said, 1.4.3 always permits to go into verbose mode and I don't need to go back to silent mode where 1.4.3 now fails. So I can not say exactly when this became broken. The current versions are udev-114 and baselayout-1.12.9-r2.
OK, I was able to reproduce the problem and fix it. The fix will be included in the next version of splashutils. Thanks for helping track it down :) As to why the evdev module doesn't work anymore -- my guess is that for some reason udev isn't loading it/isn't loading it fast enough. For evdev to be of any use to fbsplash, it has to be loaded before the fbsplash daemon is started.
OK, this should be fixed in 1.5.2.
