| View previous topic :: View next topic |
| Author |
Message |
mbrehon
n00b
Joined: 10 Jun 2006
Posts: 37
Location: Colorful Colorado
|
 Posted: Thu Apr 03, 2008 6:37 pm Post subject: kernel upgrade from 2.6.19 to 2.6.24 broke lirc [solved] |
 |
|
Hi all,
I tried to upgrade my kernel last weekend in response to a dhcpcd problem, but in doing so, I may have botched something crucial for lirc. I'm only using it for a Myth FE and now it doesn't work with 2.6.24. I'll post more details later when I get home, but for now its an AthlonXP 2500+ on an nforce2 board, with a dvico usb ir remote running mostly stock x86. The custom udev rule I have for it still creates /dev/remote, but it simply does not work, even irw just gives me a blank stare in 2.6.24 while effusive in 2.6.19... When mythfrrontend starts, syslog / lircd captures that something has opened /dev/remote, and closes it at mythfrontend exit. When I boot back into 2.6.19, everything is hunky-dory. LIRC_DEVICE is set to "dvico". I don't think there are any specific kernel modules for that remote, other than generic usb stuff.
Any recommended diagnostics other than lsusb, lshw, dmesg | grep hiddev ???
thanks,
-Mark
[edit - solved] turns out I needed to adjust my udev rule to: | Code: | | SUBSYSTEM=="usb", ENV{DEVTYPE}!="usb_device", SYSFS{manufacturer}=="DVICO", SYMLINK+="remote" |
and the refined rule still works with the older kernel.
Last edited by mbrehon on Fri Apr 04, 2008 3:39 am; edited 1 time in total |
|
| Back to top |
|
 |
mbrehon
n00b
Joined: 10 Jun 2006
Posts: 37
Location: Colorful Colorado
|
| Posted: Fri Apr 04, 2008 1:23 am Post subject: |
|
|
I found one difference, so far:
in 2.6.19:
| Code: |
mark2 ~ # uname -a
Linux mark2.local.net 2.6.19-gentoo-r5 #10 PREEMPT Sat Jan 19 21:51:14 MST 2008 i686 AMD Athlon(tm) AuthenticAMD GNU/Linux
mark2 ~ # ll /dev/remote
lrwxrwxrwx 1 root root 11 Apr 3 12:26 /dev/remote -> usb/hiddev0
mark2 ~ # ll /dev/usb
total 0
crw-rw---- 1 root root 180, 96 Apr 3 12:26 hiddev0 |
in 2.6.24:
| Code: |
mark2 ~ # uname -a
Linux mark2.local.net 2.6.24-gentoo-r3 #1 PREEMPT Sun Mar 30 19:48:51 MDT 2008 i686 AMD Athlon(tm) AuthenticAMD GNU/Linux
mark2 ~ # ll /dev/remote
lrwxrwxrwx 1 root root 15 Apr 1 14:51 /dev/remote -> bus/usb/002/002
mark2 ~ # ll /dev/usb
total 0
crw-rw---- 1 root root 180, 96 Apr 1 14:51 hiddev0 |
So, whats the difference between usb/hiddev0 and bus/usb/002/002 ?
Any ideas? I'm gonna go root around in menuconfig for a while...
-Mark |
|
| Back to top |
|
|
mbrehon
n00b
Joined: 10 Jun 2006
Posts: 37
Location: Colorful Colorado
|
| Posted: Fri Apr 04, 2008 1:37 am Post subject: |
|
|
Oh yeah, my udev rule is:
| Code: | | SUBSYSTEM=="usb", SYSFS{manufacturer}=="DVICO", SYMLINK+="remote" |
So maybe I need to refine my rule to point /dev/remote back to usb/hiddev0 in 2.6.24... testing...
Sorry 'bout the stream of conciousness here, if anybody has ideas though, I'm all ears!
-Mark |
|
| Back to top |
|
|
mbrehon
n00b
Joined: 10 Jun 2006
Posts: 37
Location: Colorful Colorado
|
| Posted: Fri Apr 04, 2008 3:00 am Post subject: |
|
|
Its a udev rule problem - using /dev/usb/hiddev0 for lircd works in new kernel. Using udevinfo to export the udev db it shows two symlink "remotes", one at usb/hiddev0 (the one I want), and the other at bus/usb/002/002 (don't want). Kernel 2.6.19 binds to the former, 2.6.24 to the latter.
So, anybody know of a udev field to match whose value coincides with usb/hiddev*? |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Kernel & Hardware
