Skip to contentSkip to conversation

lirc and Linux 2.6.11

DISCUSSION Shaun Jackman 3 participants 3 messages Apr 21, 2005 – Apr 23, 2005

lore
Share & tools
lore
#0 lore raw

I was using lirc 0.7.0 with Linux 2.6.8.1. Upon upgrading to Linux 2.6.11, I recompiled the lirc 0.7.0 hauppauge (lirc_i2c) modules for the new kernel. This did not work. I then tried compiling the lirc 0.7.1 modules for the new kernel. This didn't work either. The error message lircd gives is...

Apr 21 14:57:29 quince lircd 0.7.1: lircd(hauppauge) ready
Apr 21 14:57:52 quince lircd 0.7.1: accepted new client on /dev/lircd
Apr 21 14:57:52 quince lircd 0.7.1: could not open /dev/lirc0
Apr 21 14:57:52 quince lircd 0.7.1: default_init(): No such device
Apr 21 14:57:52 quince lircd 0.7.1: caught signal

I've also asked the lirc mailing list this question, but has anyone else run into this trouble with lirc and Linux 2.6.11?

Please cc me in your reply. Thanks,
Shaun

#1 lore raw
Quoted 6 lines · Shaun Jackman

I was using lirc 0.7.0 with Linux 2.6.8.1. Upon upgrading to Linux 2.6.11, I recompiled the lirc 0.7.0 hauppauge (lirc_i2c) modules for the new kernel. This did not work. I then tried compiling the lirc 0.7.1 modules for the new kernel. This didn't work either. The error message lircd gives is...

Quoted 8 lines
Apr 21 14:57:29 quince lircd 0.7.1: lircd(hauppauge) ready
Apr 21 14:57:52 quince lircd 0.7.1: accepted new client on /dev/lircd
Apr 21 14:57:52 quince lircd 0.7.1: could not open /dev/lirc0
Apr 21 14:57:52 quince lircd 0.7.1: default_init(): No such device
Apr 21 14:57:52 quince lircd 0.7.1: caught signal

I've also asked the lirc mailing list this question, but has anyone else run into this trouble with lirc and Linux 2.6.11?

As the lirc developers have no intention of ever merging with the mainline kernel code, you will have to ask all lirc questions to them, we can not help you out at all, sorry.

thanks,

greg k-h

#2 lore raw
In reply to Shaun Jackman
Quoted 6 lines · Shaun Jackman

I was using lirc 0.7.0 with Linux 2.6.8.1. Upon upgrading to Linux 2.6.11, I recompiled the lirc 0.7.0 hauppauge (lirc_i2c) modules for the new kernel. This did not work. I then tried compiling the lirc 0.7.1 modules for the new kernel. This didn't work either. The error message lircd gives is...

Quoted 9 lines
Apr 21 14:57:29 quince lircd 0.7.1: lircd(hauppauge) ready
Apr 21 14:57:52 quince lircd 0.7.1: accepted new client on /dev/lircd
Apr 21 14:57:52 quince lircd 0.7.1: could not open /dev/lirc0
Apr 21 14:57:52 quince lircd 0.7.1: default_init(): No such device
Apr 21 14:57:52 quince lircd 0.7.1: caught signal

I've also asked the lirc mailing list this question, but has anyone else run into this trouble with lirc and Linux 2.6.11?

lirc works fine here. Try rebooting, the makefile mknods some arbitrary device nodes even if you're running devfs or udev, and in my experience they are broken. If you reboot it usually fixes them. I'm using lirc_i2c with my wintv remote, which I guess is the same as you.

Signature · 8 lines
Cheers,
Alistair.

personal:   alistair()devzero!co!uk
university: s0348365()sms!ed!ac!uk
student:    CS/CSim Undergraduate
contact:    1F2 55 South Clerk Street,
            Edinburgh. EH8 9PP.