[please note: this is my first bug report, so I apologise if I get the format a bit wrong.] When the problem occurred: I recently emerged a backlog of updates to my media server pc (it has many other jobs). Then I did an etc-update. Symptoms: Now when it has booted and autostarts mythfrontend, the keyboard does not work, except for the return key. I can't even do a magicsysreq-[s,u,b] to emergency reboot or ctrl-alt-f1 to get a console. Also, my ir remote does not work, except for the left and right cursor keys, which give reduce and increase mythtv volume respectively. This was how the remote functioned before I customised key mapping in my .lircrc file. Reproducible: Didn't try Background: It is setup to autostart mythfrontend as per: http://dev.gentoo.org/~cardoe/mythtv/autostart.html i.e. with 'autostart' use flag and this line in /etc/inittab: c8:2345:respawn:/sbin/mingetty --autologin mythtv tty8 After the updates I did an etc-update and one of the things that was changed was that something was changed from 'tty6' to 'tty10' (this is from memory and I do not know the name of the variable or the file in which it was changed, I am sorry). I think this may have something to do with the problem but I am not sure. What I have done to try to fix: Rebuilt xorg drivers Tried different versions of mythtv (both 0.22.x and 0.23.x) tried different display manager: ratpoison instead of evilwm Tried getting evilwm to open on tty11 (but it wouldn't - I don't know what I did wrong). Alternative situations where I found the keyboard to be working normally: If I start /etc/init.d/xdm (kdm) and login then su to mythtv user and run mythfrontend.
Ok, I have just discovered that stopping lircd ( #/etc/init.d/lircd stop ) will allow the keyboard to work. Since app-misck/lirc-0.8.5 seems to have been installed on March 31st, I am guessing the problem must be in my configuration (and, therefore not a bug). Rus
Fixed It!!! When I upgraded from 2.6.33 kernel to 2.6.34 i disabled some things in the kernel config, notably some encryption routines. This caused most of my modules to not be build at all. I had to reboot to a 2.6.33 kernel then recompile the 2.3.34 kernel (with the other stuff enabled) Anyway, the first thing I noticed about the problems with my broken 2.6.34 was that ir remote stopped working. This pointed me to /dev/event which had fewer entries. I tried changing /etc/conf.d/lircd to different (lower) device numbers, not realising that tvcard modules had not even been build. When I fixed the kernel I neglected to change the device name in /etc/conf.d/lircd back, then proceeded to remove vast amounts of hair from my scalp (metaphorically speaking, of course). It seems I had told lircd to suck up any output from the keyboard which is why it stopped working. Rus ps I don't know if listing this bug here helped my solve it or not, but I did solve it very soon after listing it here. So thanks!
