Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#5079 - Lirc_i2c from lirc0.8.0.20060401-9 broken with kernel26 2.6.17.5-1
Attached to Project:
Arch Linux
Opened by Ton Peijnenburg (tpb) - Wednesday, 19 July 2006, 23:41 GMT
Opened by Ton Peijnenburg (tpb) - Wednesday, 19 July 2006, 23:41 GMT
|
DetailsLirc package lirc-0.8.0.20060401-9 and lirc-utils-0.8.0.20060401-2 with kernel26 2.6.17.5-1 are broken for lirc_i2c. I discovered this for my set-up using Hauppauge PVR 250 card in combination with MythTV which had worked for earlier configurations. I do not know latest stable combination of lirc (prior to split) and kernel26, I only know it was in May. I follow updates at least every week.
Main symptom: /dev/lirc0 was not created when loading lirc_i2c. In the messages, only lirc_dev: IR Remote Control driver registered, at major 61 was reported; lirc_i2c: chip found @ 0x18 (Hauppauge IR) lirc_dev: lirc_register_plugin: sample_rate: 10 were absent. Lircd could be loaded, but running irw crashed the deamon. Repair for now done by compiling and installing lirc-0.7.2 with the kernel mentioned. Please note: lirc installs lirc_i2c.ko and lirc_dev.ko in /lib/modules/2.6.17-ARCH/misc/ while the lirc package installs the modules in /lib/modules/2.6.17-ARCH/kernel/drivers/misc/. |
This task depends upon
Comment by Ton Peijnenburg (tpb) -
Thursday, 20 July 2006, 12:56 GMT
I'm sorry; repair was done not with lirc-0.7.2, but with svn head checked out late last week.
Comment by Tobias Powalowski (tpowa) -
Tuesday, 01 August 2006, 13:20 GMT
isn't this solved now with new lirc package?
Comment by Ton Peijnenburg (tpb) -
Wednesday, 02 August 2006, 02:18 GMT
I have upgraded and it is indeed solved. Thank you.