| Author |
Message |
|
renfield33
|
 Posted: Tue Nov 08, 2005 10:38 pm |
|
|
Joined: Tue Nov 08, 2005 10:51 am
Posts: 13
|
that is what my /dev shows for lirc
Code: spencer@mythtv:~$ ls -al /dev/lirc*
crw-r--r-- 1 root root 61, 0 Sep 25 03:01 /dev/lirc
crw-r--r-- 1 root root 61, 1 Oct 1 04:02 /dev/lirc1
srw-rw-rw- 1 root root 0 Nov 8 14:42 /dev/lircd
prw-r--r-- 1 root root 0 Jul 30 2004 /dev/lircm
if i grep dmesg for lirc null returns
|
|
| Top |
|
 |
|
tjc
|
Posted: Tue Nov 08, 2005 10:38 pm |
|
|
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location:
Arlington, MA
|
|
How about the IVTV block in the dmesg log?
|
|
| Top |
|
|
|
renfield33
|
Posted: Tue Nov 08, 2005 10:47 pm |
|
|
Joined: Tue Nov 08, 2005 10:51 am
Posts: 13
|
Code: Linux video capture interface: v1.00
ivtv: ==================== START INIT IVTV ====================
ivtv: version 0.4.0 (tagged release) loading
ivtv: Linux version: 2.6.13.2-chw-3 SMP preempt 586 gcc-3.3
ivtv: In case of problems please include the debug info
ivtv: between the START INIT IVTV and END INIT IVTV lines when
ivtv: mailing the ivtv-devel mailinglist.
ivtv0: Autodetected WinTV PVR 150 card (iTVC16 based)
ACPI: PCI Interrupt 0000:00:0e.0[A] -> GSI 17 (level, low) -> IRQ 18
ivtv0: Unreasonably low latency timer, setting to 64 (was 32)
tuner (ivtv): chip found at addr 0xc2 i2c-bus ivtv i2c driver #0
ivtv0: i2c attach to card #0 ok [client=(tuner unset), addr=61]
tveeprom: ivtv version
tveeprom: Hauppauge: model = 26032, rev = C199, serial# = 8181593
tveeprom: tuner = TCL 2002N 5H (idx = 99, type = 50)
tveeprom: tuner fmt = NTSC(M) (eeprom = 0x08, v4l2 = 0x00001000)
tveeprom: audio processor = CX25841 (type = 23)
tveeprom: decoder processor = CX25841 (type = 1c)
ivtv0: i2c attach to card #0 ok [client=tveeprom, addr=50]
cx25840 0-0044: cx25841-23 found @ 0x88 (ivtv i2c driver #0)
cx25840 0-0044: loaded /lib/modules/HcwMakoA.ROM firmware (14264 bytes)
ivtv0: i2c attach to card #0 ok [client=cx25840, addr=44]
wm8775 0-001b: chip found @ 0x36 (ivtv i2c driver #0)
ivtv0: i2c attach to card #0 ok [client=wm8775, addr=1b]
ivtv0: loading /lib/modules/ivtv-fw-enc.bin
ivtv0: Encoder revision: 0x02040011
ivtv0: Allocate DMA encoder MPEG stream: 128 x 32768 buffers (4096KB total)
ivtv0: Allocate DMA encoder YUV stream: 194 x 10800 buffers (2048KB total)
ivtv0: Allocate DMA encoder VBI stream: 120 x 17472 buffers (2048KB total)
ivtv0: Allocate DMA encoder PCM audio stream: 455 x 4608 buffers (2048KB total)
tuner: type set to 50 (TCL 2002N) by ivtv i2c driver #0
ivtv0: Initialized WinTV PVR 150, card #0
ivtv: ==================== END INIT IVTV ====================
|
|
| Top |
|
|
|
Thomas Reynolds
|
Posted: Wed Nov 09, 2005 7:03 am |
|
|
Joined: Mon Nov 07, 2005 7:22 pm
Posts: 8
|
Code: ivtv: ==================== START INIT IVTV ====================
ivtv: version 0.4.0 (tagged release) loading
ivtv: Linux version: 2.6.13.2-chw-3 SMP preempt 586 gcc-3.3
ivtv: In case of problems please include the debug info
ivtv: between the START INIT IVTV and END INIT IVTV lines when
ivtv: mailing the ivtv-devel mailinglist.
ivtv0: Autodetected WinTV PVR 150 card (iTVC16 based)
tuner (ivtv): chip found at addr 0xc2 i2c-bus ivtv i2c driver #0
ivtv0: i2c attach to card #0 ok [client=(tuner unset), addr=61]
tveeprom: ivtv version
ivtv0: i2c attach to card #0 ok [client=tveeprom, addr=50]
cx25840 1-0044: cx25843-23 found @ 0x88 (ivtv i2c driver #0)
ivtv0: i2c attach to card #0 ok [client=cx25840, addr=44]
wm8775 1-001b: chip found @ 0x36 (ivtv i2c driver #0)
ivtv0: i2c attach to card #0 ok [client=wm8775, addr=1b]
ivtv0: loading /lib/modules/ivtv-fw-enc.bin
ivtv0: Encoder revision: 0x02040011
ivtv0: Allocate DMA encoder MPEG stream: 128 x 32768 buffers (4096KB total)
ivtv0: Allocate DMA encoder YUV stream: 194 x 10800 buffers (2048KB total)
ivtv0: Allocate DMA encoder VBI stream: 120 x 17472 buffers (2048KB total)
ivtv0: Allocate DMA encoder PCM audio stream: 455 x 4608 buffers (2048KB total)
tuner: type set to 50 (TCL 2002N) by ivtv i2c driver #0
ivtv0: Initialized WinTV PVR 150, card #0
ivtv: ==================== END INIT IVTV ====================
|
|
| Top |
|
|
|
tjc
|
Posted: Wed Nov 09, 2005 8:09 am |
|
|
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location:
Arlington, MA
|
|
Have you looked at the instructions for using the PVR-150 remote and IR blaster someone posted in the forums? There was some good information on this stuff there even if you don't care about the blaster part...
|
|
| Top |
|
|
|
renfield33
|
Posted: Wed Nov 09, 2005 12:56 pm |
|
|
Joined: Tue Nov 08, 2005 10:51 am
Posts: 13
|
|
yeah, i'm using ivtv 0.4.0... looks like he backed down to 0.3.8 for IR receiver issues...
i'll give it it a try.
|
|
| Top |
|
|
|
renfield33
|
Posted: Wed Nov 09, 2005 1:38 pm |
|
|
Joined: Tue Nov 08, 2005 10:51 am
Posts: 13
|
|
yeah... i gave that tutorial a try to no avail. on irw it let 2 codes through, then nothing else.
|
|
| Top |
|
|
|
zetoune
|
Posted: Thu Nov 10, 2005 12:45 pm |
|
|
Joined: Sun Oct 16, 2005 12:15 pm
Posts: 288
|
|
I'm using R5A22 and a winTV 150 non MCE with IR receiver and transmitter.
And it did work out of the box. During installation, I had to specified my remote.
I chose Hauppage WinTV150 receiver and transmitter. Not Hauppauge Silver.
I think it's option 4.
I want to reassign some keys.
|
|
| Top |
|
|
|
renfield33
|
Posted: Thu Nov 10, 2005 5:03 pm |
|
|
Joined: Tue Nov 08, 2005 10:51 am
Posts: 13
|
ok... i get this... then it dies.
Code: Last login: Thu Nov 10 17:49:08 2005 from 192.168.0.27
spencer@mythtv:~$ irw
0000000000001794 00 Up Hauppauge_350
0000000000001794 01 Up Hauppauge_350
0000000000001794 02 Up Hauppauge_350
0000000000001794 03 Up Hauppauge_350
0000000000001794 04 Up Hauppauge_350
0000000000001795 00 Down Hauppauge_350
0000000000001795 01 Down Hauppauge_350
0000000000001795 02 Down Hauppauge_350
0000000000001795 03 Down Hauppauge_350
0000000000001795 04 Down Hauppauge_350
0000000000001794 00 Up Hauppauge_350
0000000000001794 01 Up Hauppauge_350
0000000000001794 02 Up Hauppauge_350
0000000000001794 03 Up Hauppauge_350
0000000000001794 04 Up Hauppauge_350
|
|
| Top |
|
|
|
Thomas Reynolds
|
Posted: Thu Nov 10, 2005 7:08 pm |
|
|
Joined: Mon Nov 07, 2005 7:22 pm
Posts: 8
|
|
Well I.... Installed the card on my XP machine and verified that the remote is working with no problems so it's not the hardware, or batteries or connection to the card.
I then grabbed the PVR-150 and threw it in an old HP Vectra I had laying around, which had NOTHING incommon with the Myth box I built. Installed using the i586 modules, then started over with the i686 modules. Neither install yielded a working remote.
I am up in arms at this point. The box does EVERYTHING I need it to do, is stable as a rock but I can't throw it in the living room using just a keyboard and a 30 foot extension cable.
|
|
| Top |
|
|
|
tjc
|
Posted: Thu Nov 10, 2005 10:15 pm |
|
|
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location:
Arlington, MA
|
Sorry Thomas, things got a little confusing here, since it seems like everytime I asked _you_ a question renfield33 was answering it. Hang on for a second while we try to take care of that.
Renfield33, please stop confusing things here in this thread! You've got different hardware and different issues. For the remainder of this thread, or at least until we get Thomas's issue resolved, please don't interupt unless we ask for you by name or you have a suggestion for Thomas. I'm more than happy to help you too, but I can't do both in the same thread at the same time. If you can't wait, please start another thread and summarize what we''ve already determined.
OK, onwards...
1) We've verified the hardware. This is a very good starting point.
2) From the logs you posted i think this is the key error:
Quote: /var/log/kern.log:Nov 8 00:47:18 mythtv kernel: lirc_dev: IR Remote Control driver registered, at major 61
/var/log/kern.log:Nov 8 00:47:18 mythtv kernel: lirc_pvr150: ivtv i2c driver #0: no devices found
3) According to the dmesg section you posted you're loading the encoder firmware successfully, but if memory serves the PVR-150 has a seperate chunk of firmware for the enhanced IR remote receiver and blaster. Hang on while I search for details on that...
Starting here - http://ivtvdriver.org/index.php/Firmware
On this page - http://ivtvdriver.org/index.php/Firmware_versions note that a different version of the firmware is recommended for use with the PVR-150 and the newer versions of the IVTV driver. Make sure you've got that and we can continue from there...
|
|
| Top |
|
|
|
Thomas Reynolds
|
Posted: Fri Nov 11, 2005 9:23 pm |
|
|
Joined: Mon Nov 07, 2005 7:22 pm
Posts: 8
|
|
Well off the Installation CD I copied:
HcwMakoA.ROM to /lib/modules/
and
HcwFalcn.rom to /lib/modules/ivtv-fw-enc.bin
I assume you just copy them in there and reboot and it will start using those? I rebooted and it still did not work. I wonder if IVTV or the Kernel or something has to take note of the different firmware I have just installed?
|
|
| Top |
|
|
|
ed3120
|
Posted: Sat Dec 10, 2005 3:01 pm |
|
|
Joined: Sun Dec 04, 2005 1:44 pm
Posts: 403
Location:
Central NJ
|
|
I have a similar problem. My PVR-150 remote works fine and then stops working out of nowhere. Then, out of nowhere, it starts working again. When it isn't working, in IRW I get:
lirc_pvr150: i2c_master_send failed with -14
lirc_pvr150: polling the ir receiver chip failed, trying reset
|
|
| Top |
|
|
|
j0ly
|
Posted: Fri Dec 16, 2005 9:12 am |
|
|
Joined: Sat Feb 05, 2005 3:26 pm
Posts: 121
Location:
Calgary, Alberta - Canada!
|
|
Hey guys,
Thought i would post as i did the orig. walkthrough that r22 and r26 is based on. I built a machine for a buddy of mine, using r22 and had the same problems. Seems (for some reason!?!?!) that doing a modprobe lirc_i2c brings the remote back to life. try it out after a clean reboot.
- Scott
|
|
| Top |
|
|
|
j0ly
|
Posted: Wed Dec 21, 2005 5:57 pm |
|
|
Joined: Sat Feb 05, 2005 3:26 pm
Posts: 121
Location:
Calgary, Alberta - Canada!
|
|
Thought i would post a quick update on the situation, I have upgraded my myth setup in the house to r26 now, and am facing the same problem as you guys... i am now going to try to figure this out over the next few days (holiday time from work), if you guys have found anything out, please post it here.
Thanks
|
|
| Top |
|
|
View unanswered posts
View active topics
KnoppMyth 
Print view
Previous topic Next topic 
LinHES Home
Board index
FAQ
Search
Login 
Register