| LinHES Forums http://forum.linhes.org/ |
|
| lirc_pvr150: ivtv i2c driver #0: no devices found [Fixed] http://forum.linhes.org/viewtopic.php?f=2&t=13412 |
Page 1 of 1 |
| Author: | diblasio [ Wed Jan 10, 2007 9:35 am ] |
| Post subject: | lirc_pvr150: ivtv i2c driver #0: no devices found [Fixed] |
Everything was working fine, and after a reboot I get this message Code: lirc_pvr150: ivtv i2c driver #0: no devices found along with an unresponsive remote. Here's my part of my dmesg Code: lirc_dev: IR Remote Control driver registered, at major 61 This is on R5D1
ivtv: ==================== START INIT IVTV ==================== ivtv: version 0.7.0 (tagged release) loading ivtv: Linux version: 2.6.17-chw-8 SMP preempt mod_unload 586 gcc-3.4 ivtv: In case of problems please include the debug info between ivtv: the START INIT IVTV and END INIT IVTV lines, along with ivtv: any module options, when mailing the ivtv-users mailinglist. ivtv0: Autodetected Hauppauge WinTV PVR-150 card (cx23416 based) ACPI: PCI Interrupt Link [APC4] enabled at IRQ 19 ACPI: PCI Interrupt 0000:01:07.0[A] -> Link [APC4] -> GSI 19 (level, high) -> IRQ 19 ivtv0: Unreasonably low latency timer, setting to 64 (was 32) tuner 2-0061: chip found @ 0xc2 (ivtv i2c driver #0) cx25840 2-0044: cx25843-23 found @ 0x88 (ivtv i2c driver #0) eth0: no IPv6 routers present cx25840 2-0044: loaded v4l-cx25840.fw firmware (16382 bytes) wm8775 2-001b: chip found @ 0x36 (ivtv i2c driver #0) tveeprom 2-0050: Hauppauge model 26582, rev F0B2, serial# 10077039 tveeprom 2-0050: tuner model is TCL M2523_5N_E (idx 112, type 4) tveeprom 2-0050: TV standards NTSC(M) (eeprom 0x08) tveeprom 2-0050: audio processor is CX25843 (idx 37) tveeprom 2-0050: decoder processor is CX25843 (idx 30) tveeprom 2-0050: has no radio, has no IR remote ivtv0: loaded v4l-cx2341x-enc.fw firmware (262144 bytes) ivtv0: Encoder revision: 0x02050032 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 2-0061: type set to 50 (TCL 2002N) ivtv0: Initialized Hauppauge WinTV PVR-150, card #0 ivtv: ====================== NEXT CARD ====================== ivtv1: Autodetected Hauppauge WinTV PVR-150 card (cx23416 based) ACPI: PCI Interrupt Link [APC1] enabled at IRQ 16 ACPI: PCI Interrupt 0000:01:08.0[A] -> Link [APC1] -> GSI 16 (level, high) -> IRQ 20 ivtv1: Unreasonably low latency timer, setting to 64 (was 32) tuner 3-0061: chip found @ 0xc2 (ivtv i2c driver #1) cx25840 3-0044: cx25841-23 found @ 0x88 (ivtv i2c driver #1) cx25840 3-0044: loaded v4l-cx25840.fw firmware (16382 bytes) wm8775 3-001b: chip found @ 0x36 (ivtv i2c driver #1) tveeprom 3-0050: Hauppauge model 26132, rev G1B2, serial# 9544219 tveeprom 3-0050: tuner model is TCL M2523_5N_E (idx 112, type 4) tveeprom 3-0050: TV standards NTSC(M) (eeprom 0x08) tveeprom 3-0050: audio processor is CX25841 (idx 35) tveeprom 3-0050: decoder processor is CX25841 (idx 28) tveeprom 3-0050: has no radio, has IR remote ivtv1: loaded v4l-cx2341x-enc.fw firmware (262144 bytes) ivtv1: Encoder revision: 0x02050032 ivtv1: Allocate DMA encoder MPEG stream: 128 x 32768 buffers (4096KB total) ivtv1: Allocate DMA encoder YUV stream: 194 x 10800 buffers (2048KB total) ivtv1: Allocate DMA encoder VBI stream: 120 x 17472 buffers (2048KB total) ivtv1: Allocate DMA encoder PCM audio stream: 455 x 4608 buffers (2048KB total) tuner 3-0061: type set to 50 (TCL 2002N) ivtv1: Initialized Hauppauge WinTV PVR-150, card #1 ivtv: ==================== END INIT IVTV ==================== lirc_pvr150: ivtv i2c driver #0: no devices found lirc_pvr150: ivtv i2c driver #1: no devices found |
|
| Author: | diblasio [ Wed Jan 10, 2007 9:52 am ] |
| Post subject: | |
Nevermind. I shutdown the box and unplugged it. On reboot it was magically fixed. Very strange. |
|
| Author: | Guierrmo [ Sat Jan 13, 2007 1:11 am ] |
| Post subject: | |
Isn't that annoying? I've never had this happen before. Until now, I banged my head on the floor for 2 hours until I saw your post, I can't believe I had to unplug the damn thing before it would recognize again. |
|
| Author: | tzoom84 [ Sun Sep 21, 2008 11:28 am ] |
| Post subject: | |
Yep. SAME thing with me. I thought it was silly to have to literally unplug the thing. But it turns out after much troubleshooting, this simple solution worked for me too (after a power outage) |
|
| Author: | tjc [ Sun Sep 21, 2008 12:37 pm ] |
| Post subject: | |
diblasio wrote: Nevermind. I shutdown the box and unplugged it. On reboot it was magically fixed. Very strange.
Probably a case of the firmware getting munged. Powering the box down cold for a minute to clear the firmware is a pretty standard thing to try for really bizarre symptoms. Between one thing and another I probably end up doing it about twice a year. <shrug> |
|
| Page 1 of 1 | All times are UTC - 6 hours |
| Powered by phpBB® Forum Software © phpBB Group http://www.phpbb.com/ |
|