<div><span class="gmail_quote">On 10/17/05, <b class="gmail_sendername">Mike Frisch</b> <<a href="mailto:mfrisch@isurfer.ca">mfrisch@isurfer.ca</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I've got the IVTV and DVB-S to co-exist, but when I attempt to load the<br>air2pc module, I get the following:<br><br>--- cut here ---<br><br>[4294707.062000] drivers/media/dvb/b2c2/skystar2.c: FlexCopIIB(rev.195)<br>chip found
<br>[4294707.062000] drivers/media/dvb/b2c2/skystar2.c: the chip has 38<br>hardware filters<br>[4294707.187000] driver_initialize MAC address = 00:d0:d7:30:1a:ed:00:00<br>[4294707.187000] DVB: registering new adapter (SkyStar2).
<br>[4294707.218000] flexcop_i2c_func<br>[4294707.404000] i2c_readbytes: i2c read error (addr 0a, err == -121)<br>[4294707.793000] mt312_read: ret == -121<br>[4294707.793000] skystar2: A frontend driver was not found for device
<br>13d0/2103 subsystem 13d0/2103<br>[4294707.913000] b2c2-flexcop: B2C2 FlexcopII/II(b)/III digital TV<br>receiver chip loaded successfully<br><br>--- cut here ---<br><br>If it matters, I am using tveeprom from my kernel (
2.6.12-9-386) on<br>Ubuntu.<br><br>Anybody have a similar setup and can shed some light?</blockquote><div><br>
</div></div>Similar setup, yes - IVTV, HD-3000 using DVB, and Air2PC (HD-5000 version).<br>
<br>
Besides the DVB differences, I see one more which I think could be the
problem. I have moved up to 2.6.13 kernel, after which I followed
the HOWTO on <a href="http://www.hd5000.com">www.hd5000.com</a>. If I remember, there was one post a
long time ago from someone who had patched a 2.6.12 kernel, but the
work was beyond my feeling of peace-of-mind. That's why I waited
for the new driver that works with 2.6.13.<br>
<br>
After following the HOWTO, I rebuilt IVTV, NVRAM-WAKEUP, LIRC, and
booted the system. As you are doing, I found that I had to
discard the tveeprom module from the IVTV package and put the kernel's
back in place.<br>
<br>
Following that episode, I plugged in the HD-5000 card and was
disappointed to see KUDZU configure it as an ethernet card. KUDZU
pretty much hosed my /etc/modprobe.conf file, which I had old versions
of. After a few more re-boots, and reconstructing
/etc/modprobe.conf, KUDZU stopped pausing and modifying
/etc/modprobe.conf.<br>
<br>
The system now boots without pausing, cleanly, automatically per the
recording schedule, and the three tuners (PVR-350, HD-3000, HD-5000)
are all working well. The tveeprom situation is still a problem,
but so far, has only caused one standard-definition program from being
completely recorded. It was the Pilot Episode of "Freddie" - so
there was no real loss! But I am hopeful that the IVTV developers
will resolve the differences between the two versions of tveeprom, soon.<br>
<br>
-- <br>
MM<br>
<br>