LinHES Forums http://forum.linhes.org/ |
|
KnoppMyth doesn't like my PVR-150 card! What do I do? http://forum.linhes.org/viewtopic.php?f=2&t=9065 |
Page 1 of 1 |
Author: | sneeley [ Sat Mar 18, 2006 7:01 pm ] |
Post subject: | KnoppMyth doesn't like my PVR-150 card! What do I do? |
I just tried installing KnoppMyth R5 Beta 7 and I'm getting error message from the IVTV module. I had the same problems with KnoppMyth A30.2. I'm banging my head against the wall and about to give up. Could someone please help me out? I'm a newbie and don't know what to try. ivtv: ==================== START INIT IVTV ==================== ivtv: version 0.4.3 (tagged release) loading ivtv: Linux version: 2.6.15-chw-2 SMP preempt 586 gcc-3.3 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 WinTV PVR 150 card (cx23416 based) ACPI: PCI Interrupt 0000:00:08.0[Q]: no GSI ivtv0: Unreasonably low latency timer, setting to 64 (was 48) ivtv0 warning: i2c client addr: 0x50 not found for command 0x0! ivtv0: Error -19 reading Hauppauge eeprom. ivtv0: Possible causes: the tveeprom module was not loaded, or ivtv0: the eeprom kernel module was loaded before the tveeprom module. ivtv0 warning: i2c client addr: 0x44 not found for command 0xc008561c! ivtv0: Could not detect tuner standard, defaulting to NTSC. ivtv0: loaded v4l-cx2341x-enc.fw firmware (262144 bytes) ivtv0 warning: Encoder mailbox not found ivtv0 warning: Decoder mailbox not found ivtv0: Error locating firmware. ivtv0: Error -12 on initialization ivtv: probe of 0000:00:08.0 failed with error -12 ivtv: ==================== END INIT IVTV ==================== |
Author: | mapper [ Sat Mar 18, 2006 7:28 pm ] |
Post subject: | |
Not sure this will help (old post) but problems with Hauppage and eeprom are not new: http://mysettopbox.tv/phpBB2/viewtopic.php?p=31403&sid=195c2b9d9d39a551db54de64f05908aa Not to rain on your parade but for the benefit of other PVR-150 users (mind you there are different models out there), I have had no problems upgrading to R5B7 (from 30.2) with my PVR-150: Code: --
tveeprom 1-0050: Hauppauge model 26032, rev C199, serial# 8209161 tveeprom 1-0050: tuner model is TCL 2002N 5H (idx 99, type 50) tveeprom 1-0050: TV standards NTSC(M) (eeprom 0x08) tveeprom 1-0050: audio processor is CX25841 (idx 35) tveeprom 1-0050: decoder processor is CX25841 (idx 28) tveeprom 1-0050: has no radio, has 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 1-0061: type set to 50 (TCL 2002N) ivtv0: Initialized WinTV PVR 150, card #0 -- |
Author: | tjc [ Sat Mar 18, 2006 8:23 pm ] |
Post subject: | |
sneeley, try shutting down cold and leaving the system sit for at least 30 seconds before rebooting. |
Author: | sneeley [ Sun Mar 19, 2006 10:12 am ] |
Post subject: | |
OK, I left the machine off all night with the power cable disconnected. That did not help. I also followed the other suggestion of removing eeprom.ko, and that did not help. Someone on the IVTV mailing list suggested that I disable ACPI in bios. After trying that, I get a message about a buggy MP table. Would anyone know how to fix the buggy MP table error? ivtv: ==================== START INIT IVTV ==================== ivtv: version 0.4.3 (tagged release) loading ivtv: Linux version: 2.6.15-chw-2 SMP preempt 586 gcc-3.3 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 WinTV PVR 150 card (cx23416 based) PCI: No IRQ known for interrupt pin A of device 0000:00:08.0. Probably buggy MP table. ivtv0: Unreasonably low latency timer, setting to 64 (was 32) ivtv0 warning: i2c client addr: 0x50 not found for command 0x0! ivtv0: Error -19 reading Hauppauge eeprom. ivtv0: Possible causes: the tveeprom module was not loaded, or ivtv0: the eeprom kernel module was loaded before the tveeprom module. ivtv0 warning: i2c client addr: 0x44 not found for command 0xc008561c! ivtv0: Could not detect tuner standard, defaulting to NTSC. ivtv0: loaded v4l-cx2341x-enc.fw firmware (262144 bytes) ivtv0 warning: Encoder mailbox not found ivtv0 warning: Decoder mailbox not found ivtv0: Error locating firmware. ivtv0: Error -12 on initialization ivtv: probe of 0000:00:08.0 failed with error -12 ivtv: ==================== END INIT IVTV ==================== lspci -vvvxxx -s 00:80.0: 0000:00:08.0 Multimedia video controller: Internext Compression Inc iTVC16 (CX23416) MPEG-2 Encoder (rev 01) Subsystem: Hauppauge computer works Inc.: Unknown device 8003 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR+ Latency: 64 (32000ns min, 2000ns max), Cache Line Size: 0x08 (32 bytes) Interrupt: pin A routed to IRQ 0 Region 0: Memory at 20000000 (32-bit, prefetchable) [size=64M] Capabilities: [44] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 00: 44 44 16 00 06 00 10 82 01 00 00 04 08 40 00 00 10: 08 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 70 00 03 80 30: 00 00 00 00 44 00 00 00 00 00 00 00 ff 01 80 08 40: ff ef 00 00 01 00 02 00 00 00 00 00 00 00 00 00 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Please help! Thanks. - Sean |
Author: | tjc [ Sun Mar 19, 2006 11:20 am ] |
Post subject: | |
There's another recent thread around here around about misidentified PVR cards. The fix requires making a simple patch and recompiling the ivtv driver. http://mysettopbox.tv/phpBB2/viewtopic.php?t=9068 Sadly the info provided is pretty fuzzy, I'll take a look at the source file in question and see if I can make it as clear as the "drunk monkey" instructions on the http://www.knoppmythwiki.org/index.php?page=CompileIvtv page. The other possibility is that there's something wrong with your Motherboard, BIOS settings, or the PVR card. |
Author: | sneeley [ Sun Mar 19, 2006 1:42 pm ] |
Post subject: | |
That sounds like it could be it... I'll give this a try and report back. tjc wrote: There's another recent thread around here around about misidentified PVR cards. The fix requires making a simple patch and recompiling the ivtv driver.
http://mysettopbox.tv/phpBB2/viewtopic.php?t=9068 Sadly the info provided is pretty fuzzy, I'll take a look at the source file in question and see if I can make it as clear as the "drunk monkey" instructions on the http://www.knoppmythwiki.org/index.php?page=CompileIvtv page. The other possibility is that there's something wrong with your Motherboard, BIOS settings, or the PVR card. |
Author: | tjc [ Sun Mar 19, 2006 3:01 pm ] |
Post subject: | |
OK, This is utterly untested, caveat utor and all that. I can not recommend following these directions, they're just something to try if you're up for some hacking. Here is a context diff of what I think he's doing: Code: root@black2:/usr/src/ivtv-0.4.3/driver# diff -c ivtv-cards.c~ ivtv-cards.c *** ivtv-cards.c~ Tue Jan 10 16:08:55 2006 --- ivtv-cards.c Sun Mar 19 15:51:26 2006 *************** *** 399,404 **** --- 399,405 ---- {PCI_DEVICE_ID_IVTV16, IVTV_PCI_ID_HAUPPAUGE, 0xc801}, {PCI_DEVICE_ID_IVTV16, IVTV_PCI_ID_HAUPPAUGE, 0x0801}, {PCI_DEVICE_ID_IVTV16, IVTV_PCI_ID_HAUPPAUGE, 0x0009}, + {PCI_DEVICE_ID_IVTV16, IVTV_PCI_ID_HAUPPAUGE, 0x0003}, // Alternate Hauppauge vendor IDs {PCI_DEVICE_ID_IVTV16, 0x0270, 0x0801}, {PCI_DEVICE_ID_IVTV16, 0x4070, 0x8801}, *************** *** 411,417 **** {PCI_DEVICE_ID_IVTV15, IVTV_PCI_ID_HAUPPAUGE, 0x4801}, {PCI_DEVICE_ID_IVTV16, IVTV_PCI_ID_HAUPPAUGE, 0x4801}, {PCI_DEVICE_ID_IVTV16, IVTV_PCI_ID_HAUPPAUGE, 0x4803}, - {PCI_DEVICE_ID_IVTV16, IVTV_PCI_ID_HAUPPAUGE, 0x0003}, {0, 0, 0} }; --- 412,417 ---- Here are the approximate steps to take, again I pulled these straight out of the air, haven't tested them and don't make any claims on whether they'll work or not. If you don't know how to read/use a context diff this is probably NOT something you want to try: Code: cd /usr/src
tar zxvf ivtv-0.4.3.tar.gz cd /usr/src/ivtv-0.4.3/driver # Make the change shown above cd /usr/src/ivtv-0.4.3 make make install reboot OBTW - This isn't really an installation question anymore, and you really don't want Cecil purging it on that basis... A word to the wise... |
Author: | sneeley [ Mon Mar 20, 2006 10:15 pm ] |
Post subject: | Problem solved |
Thanks for all of the help on this one guys. I finally resolved the problem. Just for fun I slapped another drive in and loaded Windows XP onto it to see if the PVR-150 would work in windows. Sure enough, there were problems there too. Windows recognized the card, but gave me problems with the driver install. When I finally forced windows to install the drivers, I got an "Error code 10" device failed to start error in the windows device manager. I decided to yank out the only other card in my system, my AGP video card and then rebooted. And what do you know... the PVR-150 started working correctly! I then went into BIOS and adjusted various settings dealing with IRQs, and disabled the onboard modem and anything else that wasn't being used, and was eventually able to put back in the AGP card without a conflict. I wish I knew exactly which BIOS setting did the trick. Can anyone explain this? Anyway, I'm very happy that it is working now!!!! |
Author: | andrewsw [ Sat Apr 01, 2006 9:45 pm ] |
Post subject: | |
huh. so I've had a smoothly working r5a16 for a while and suddenly one day, bang error -19 on my pvr-350 card. my 150 still works fine. no changes, or updates at all. ugh. works one day and not the next. hardware failure maybe? I found one thread on google: http://poptix.net/ivtv/Dec-2004/msg00234.html that references (down at the bottom) flaky i2c bus, which is really scary as its a less than year old mobo. any insights? |
Page 1 of 1 | All times are UTC - 6 hours |
Powered by phpBB® Forum Software © phpBB Group http://www.phpbb.com/ |