On Tuesday 07 December 2004 12:11 am, Carl wrote: > Hmm.. double-checked that. Check out the lsmod output below, note that > tveeprom is loaded before tuner, and eeprom not at all. I also tried > loading it first, rather than letting ivtv auto-load it. > > Also, I assume that the "firmware not found" message has to do with finding > the firmware on the card, not in /lib/modules, but I'll try replacing those > files and see if that helps... > > Thanks! > > On Monday December 6 2004 07:41, Brian Jackson wrote: > > The 2 clues are: > > Possible causes: the tveeprom module was not loaded, or > > the eeprom kernel module was loaded before the tveeprom module > > AND > > Error locating firmware. > > > > Looks like you need to either move the eeprom module away (if it isn't > > being used), or make sure tveeprom gets loaded first. > > It also looks like your firmware went MIA. > > > > --Brian Jackson > > > > On 7:55:39 am 2004-12-06 Carl <[EMAIL PROTECTED]> wrote: > > > This is from a setup that's been working well for almost a year. > > > > > > I recently rebooted, and was no longer able to get ivtv to load. > > > This was with a kernel and ivtv module that was working great. > > > > > > Userspace packages were updated, including possibly lirc, but > > > otherwise it is the same system is was before this happened. > > > I've even rolled back a few kernel and ivtv versions. > > > > > > Before I get desperate and replace the card, can anyone see > > > anything here that might offer clues? I have no opportunity to > > > run Windows, unless someone wants to give me a PCMCIA to > > > PCI adapter... > > > > > > I tried loading tveeprom first, that didn't change anything. It > > > also didn't put any messages in the log. Any chance there is > > > an i2c issue? > > > > > > Also, these "over-current change on port 1" messages seem to > > > be from USB, but they appear when I modload ivtv, nearly in > > > the same spot each time. not sure if they did before, but I'll > > > check... > > > > > > Dec 6 02:42:25 mythtv ivtv: ==================== START INIT IVTV > > > ==================== Dec 6 02:42:25 mythtv ivtv: version 0.3.1 (x) > > > loading Dec 6 02:42:25 mythtv ivtv: Linux version: 2.6.9-gentoo-r4 > > > preempt CYRIXIII 4KSTACKS gcc-3.4 Dec 6 02:42:25 mythtv ivtv: In > > > case of problems please include the debug info Dec 6 02:42:25 mythtv > > > ivtv: between the START INIT IVTV and END INIT IVTV lines when Dec 6 > > > 02:42:25 mythtv ivtv: mailing the ivtv-devel mailinglist. Dec 6 > > > 02:42:25 mythtv ivtv: Autodetected WinTV PVR 350 card Dec 6 02:42:25 > > > mythtv ivtv: Found an iTVC15 based chip Dec 6 02:42:25 mythtv PCI: > > > Enabling device 0000:00:14.0 (0004 -> 0006) Dec 6 02:42:25 mythtv > > > ACPI: PCI interrupt 0000:00:14.0[A] -> GSI 11 (level, low) -> IRQ 11 > > > Dec 6 02:42:25 mythtv ivtv: Unreasonably low latency timer, setting to > > > 64 (was 32) Dec 6 02:42:25 mythtv ivtv: VIA PCI device: 0x0601 > > > vendor: 0x1106 Dec 6 02:42:25 mythtv ivtv: i2c client addr: 0x50 not > > > found! Dec 6 02:42:25 mythtv ivtv: Error -19 reading Hauppauge > > > eeprom. Dec 6 02:42:25 mythtv ivtv: Possible causes: the tveeprom > > > module was not loaded, or Dec 6 02:42:25 mythtv ivtv: the eeprom > > > kernel module was loaded before the tveeprom module. Dec 6 02:42:25 > > > mythtv tuner: Ignoring new-style parameters in presence of obsolete > > > ones Dec 6 02:42:25 mythtv saa7115: starting probe for adapter ivtv > > > i2c driver #0 (0x10005) Dec 6 02:42:25 mythtv saa7127: Ignoring > > > new-style parameters in presence of obsolete ones Dec 6 02:42:25 > > > mythtv saa7127: video encoder driver version V 0.3 loaded Dec 6 > > > 02:42:27 mythtv hub 2-0:1.0: over-current change on port 1 Dec 6 > > > 02:42:27 mythtv hub 2-0:1.0: over-current change on port 2 Dec 6 > > > 02:42:27 mythtv ivtv: Encoder mailbox not found Dec 6 02:42:27 > > > mythtv ivtv: Decoder mailbox not found Dec 6 02:42:27 mythtv ivtv: > > > Error locating firmware. Dec 6 02:42:27 mythtv ivtv: Error -12 on > > > initialization Dec 6 02:42:27 mythtv ivtv-iTVC15_16_mpg2_encoder_card > > > > > > : probe of 0000:00:14.0 failed with error -12
Ahh, I had this exact same problem. It turns out that tveeprom is not able to see the PVR card using the i2c bus. In my case, it was with a cheapo MSI motherboard where there were issues with the southbridge and the i2c modules. Basically, i2c wouldn't load correctly or do anything (lm_sensors didn't work, nothing from tveeprom, etc) useful. I ended up replacing the motherboard. I was sure there were problems with the board when USB started acting flaky. Sometimes it would load the drivers, sometimes it wouldn't. Anyway, it never "just" worked. Sorry, probably not what you wanted to hear, but I ended up getting a DFI board with the Nvidia chipset and sound including an RCA digital out built into the board and with no other changes, that worked. However, I just noticed that you seem to be lacking the specific i2c driver for your board. Have you tried lm_sensors yet? That's a good test of how i2c is working. If you can get sensor data from that when the various i2c drivers are loaded, then fire up tveeprom and see if you get information out. But, I'll stick with my original guess that you have a buggy version of the same chip I had. -- "Wherever the standard of freedom and independence has been or shall be unfurled, there will her heart, her benedictions, and her prayers be. But she goes not abroad in search of monsters to destroy." - John Qunicy Adams -- Pete ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ ivtv-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/ivtv-devel
