Menu
▾
▴
Re: irw Not Responding
|
From: <moo...@fr...> - 2007-01-30 20:25:55
|
cat /dev/lirc doesn't seem to work: DVR:~ # cat /dev/lirc cat: /dev/lirc: Device or resource busy A bit of additional information. lsmod shows: DVR:~ # lsmod | grep lirc lirc_i2c 12292 2 lirc_dev 16788 1 lirc_i2c i2c_core 26049 14 =20 saa7127,i2c_ec,cx88xx,bttv,lirc_i2c,wm8775,cx25 840,msp3400,saa7115,tuner,ivtv,i2c_algo_bit,i2c_i801,tveeprom What does the info on the right of each line mean? In particular what =20 caught my eye was on the i2c_core line which has saa7127. This module =20 was not included in the 2.6.19 kernel =20 (http://www.mail-archive.com/ivt...@iv.../msg05482.html) =20 so after the boot is complete I modprobe saa7127 by hand to get TV Out =20 working on my PVR350 card. Does lirc have a dependency on saa7127 =20 being already installed? I load lirc in /etc/modprobe.conf following =20 instructions, but I really don't know what the --ignore-install on the =20 install line is doing: DVR:~ # cat /etc/modprobe.conf alias char-major-61 lirc_i2c remove snd-intel8x0 { /usr/sbin/alsactl store 0 >/dev/null 2>&1 || : ; =20 }; /sbin/ modprobe -r --ignore-remove snd-intel8x0 options snd-mpu401 index=3D1 remove snd-mpu401 { /usr/sbin/alsactl store 1 >/dev/null 2>&1 || : ; =20 }; /sbin/mo dprobe -r --ignore-remove snd-mpu401 # ivtv modules setup alias char-major-81 videodev alias char-major-81-0 ivtv alias char-major-81-1 ivtv alias char-major-81-2 ivtv install ivtv /sbin/modprobe --ignore-install ivtv; /sbin/modprobe ivtv-fb install lirc_i2c /sbin/modprobe ivtv; /sbin/modprobe --ignore-install lirc_i= 2c alias eth0 3c59x alias snd-card-0 snd-intel8x0 options snd-card-0 index=3D0 Lastly, dmesg shows: ivtv0: Autodetected Hauppauge WinTV PVR-350 tuner 3-0043: chip found @ 0x86 (ivtv i2c driver #0) tda9887 3-0043: tda988[5/6/7] found @ 0x43 (tuner) tuner 3-0061: chip found @ 0xc2 (ivtv i2c driver #0) saa7115 3-0021: saa7115 found (1f7115d0e100000) @ 0x42 (ivtv i2c driver #0) msp3400 3-0040: MSP4448G-B3 found @ 0x80 (ivtv i2c driver #0) msp3400 3-0040: MSP4448G-B3 supports radio, mode is autodetect and autoselec= t i2c_adapter i2c-3: Client creation failed at 0x44 (-1) Should I worry about the i2c_adapter client creation failure? Is that a clu= e? Thanks. Quoting Graeme McClinton <gra...@gm...>: > Try "cat /dev/lirc" then press some remote buttons. If the receiver is > receiving, then you will see junk on the screen. > > At least, that's what happens when I do it > > On 1/30/07, moo...@fr... <moo...@fr...> wrote: >> >> I need some pointers to how to diagnose my problem. I'm running >> MythTV with a Hauppauge remote. I had everything working, then >> changed out my motherboard and updated the kernel from 2.6.18-1 to >> 2.6.19-1, now irw doesn't respond to the remote. Here are the steps >> I've taken to attempt to identify the problem: >> >> * I triple checked the IR receiver cable to ensure it was plugged into >> the card and changed the remote batteries (hey, I've overlooked dumber >> things before). >> >> * Verified the kernel version I'm running >> DVR:~ # uname -r >> 2.6.19-1.2895.fc6 >> >> * Checked atrpms (which is where I initially loaded lirc from) amongst >> others to see if there were any missing updates. >> DVR:~ # yum -y install lirc-kmdl-2.6.19-1.2895.fc6 >> Loading "installonlyn" plugin >> Setting up Install Process >> Setting up repositories >> Reading repository metadata in from local files >> Parsing package install arguments >> Nothing to do >> >> * Verified that lirc_i2c is being loaded >> DVR:~ # modprobe -l | grep lirc >> /lib/modules/2.6.19-1.2895.fc6/updates/drivers/lirc/lirc_streamzap.ko >> /lib/modules/2.6.19-1.2895.fc6/updates/drivers/lirc/lirc_dev.ko >> /lib/modules/2.6.19-1.2895.fc6/updates/drivers/lirc/lirc_sasem.ko >> /lib/modules/2.6.19-1.2895.fc6/updates/drivers/lirc/lirc_mceusb.ko >> /lib/modules/2.6.19-1.2895.fc6/updates/drivers/lirc/lirc_gpio.ko >> /lib/modules/2.6.19-1.2895.fc6/updates/drivers/lirc/lirc_serial.ko >> /lib/modules/2.6.19-1.2895.fc6/updates/drivers/lirc/lirc_mceusb2.ko >> /lib/modules/2.6.19-1.2895.fc6/updates/drivers/lirc/lirc_cmdir.ko >> /lib/modules/2.6.19-1.2895.fc6/updates/drivers/lirc/lirc_atiusb.ko >> /lib/modules/2.6.19-1.2895.fc6/updates/drivers/lirc/lirc_sir.ko >> /lib/modules/2.6.19-1.2895.fc6/updates/drivers/lirc/lirc_bt829.ko >> /lib/modules/2.6.19-1.2895.fc6/updates/drivers/lirc/lirc_i2c.ko >> /lib/modules/2.6.19-1.2895.fc6/updates/drivers/lirc/lirc_imon.ko >> /lib/modules/2.6.19-1.2895.fc6/updates/drivers/lirc/lirc_igorplugusb.ko >> /lib/modules/2.6.19-1.2895.fc6/updates/drivers/lirc/lirc_it87.ko >> >> * Verified lircd is running >> DVR:~ # ps -elf | grep lirc >> 1 S root 1469 1 0 75 0 - 0 - Jan29 ? >> 00:06:32 [lirc >> _dev] >> 1 S root 2860 1 0 78 0 - 753 - Jan29 ? >> 00:00:00 lircd >> >> 0 R root 5979 5946 0 78 0 - 971 - 10:10 pts/0 >> 00:00:00 grep >> lirc >> >> * Finally, startup irw and push a few remote buttons. Nothing... >> DVR:~ # irw >> >> >> Ideas? >> >> >> ------------------------------------------------------------------------- |
