thanks for the reply, using ivtv-tune gives the same results as ptune + myth. "ivtv-tune -c 5 -t us-cable", Channel 5 (77.25 Mhz) Signal Detected comes up, but it is the content from what should be channel 95. No other channels come in at all, it is as if the frequency->channel mapping is all wrong. I think the only reason that I get anything here is because there is a point of convergence between whatever channel->frequency map my tuner is stuck on the frequencies actually in use here (Comcast cable, US).
I can still manually find the channels by using ivtvctl --set-freq=xxx by specifying the values in (in what I thought was Hz, but I looking again don't think thats quite it). I have found many more channels since my last email and I can reach every channel my TV can with enough frequency hunting, so everything is functioning, just not tuning properly. Is this a general bug in us-cable ntsc land with 0.5.1? or am I the only one seeing it? (aka: still something wrong with my box) ShadowRage wrote: > dont use setfreq unless you plan on putting in the value in mhz > > first ivtv-tune --help > > and use ivtv-tune -c channel -f freqmap (freqmap can be listed via the > -L option) > > On Sun, 2006-01-22 at 20:05 -0500, Bob Wessen wrote: > >> more progress, but still no solution >> >> using "dd if=/dev/video0 of=/dev/video16" and tuning manually with >> "ivtvctl --set-freq=xxx" I can tune the card to channels and have them >> come in correctly. Using ptune.pl and myth still do not work. >> >> For example: >> >> ivtvctl --set-freq=1024 (lucky random value I started with) tunes the >> card to the correct channel 5 (ntsc-cable). Adding 100 to that tunes me >> to Channel 6, I'm not sure what the actual Hz between channels should >> be, but adding 100 gave a quality picture, where bumping it up or down >> 20 after that made the picture start ghosting. >> >> This doesn't work for all channels, but I have this so far: >> channel 3 = 760 >> channel 4 = 860 >> channel 5 = 1024 >> channel 6 = 1124 >> channel 95 = 1250 ??? >> >> Does this give anyone smarter than I any idea what is messed up? Is the >> tuner being detected wrong? Is there a frequency to channel mapping >> somewhere I can edit? >> >> >> Bob Wessen wrote: >> >>> In an effort to resolve the issues I've had with 0.4-0.4.2 I upgraded to >>> kernel 2.6.15 and therefore upgraded to ivtv-0.5.1 (think this is >>> necessary from reading the docs) >>> >>> All is going much better, no more errors reported in dmesg when loading >>> ivtv and all the modules needed are there and registering properly as >>> far as I can tell. >>> >>> I configured the kernel to build everything related to v4l + dvb as >>> modules. They are installed as expected in >>> /lib/modules/2.6.15-gentoo-r1/kernel/drivers/media/ + the ivtv modules >>> are installed in /lib/modules/2.6.15-gentoo-r1/ivtv/. The only modules >>> in the ivtv directory are ivtv.ko + ivtv-fb.ko, I am using all other >>> modules from the 2.6.15 kernel. >>> >>> I can send video from video0 -> video16 and get a picture, although it >>> is all static. >>> >>> My problem is now all channels come through as static except one >>> channel. The signal for this channel can be found by tuning to channel >>> 5 (both using ptune/mplayer or mythtv), but the content of the signal is >>> not channel 5, it is a home shopping channel, that is normally found >>> somewhere in the channel 50-100 range. >>> >>> The only errors of any type I can come up with are related to building >>> the 0.5.1 driver, it complains: >>> >>> make -C /lib/modules/2.6.15-gentoo-r1/build M=/root/ivtv-0.5.1/driver >>> modules >>> make[1]: Entering directory `/usr/src/linux-2.6.15-gentoo-r1' >>> Building modules, stage 2. >>> MODPOST >>> *** Warning: "tveeprom_hauppauge_analog" >>> [/root/ivtv-0.5.1/driver/ivtv.ko] undefined! >>> *** Warning: "tveeprom_read" [/root/ivtv-0.5.1/driver/ivtv.ko] undefined! >>> make[1]: Leaving directory `/usr/src/linux-2.6.15-gentoo-r1' >>> >>> (yes, I'm running as root till I can get this all working and the source >>> isn't in the most logical place, but it works) >>> >>> This is supposedly related to the version of v4l in the kernel according >>> to the wiki (but even in 2.6.15?). I tried the instructions on the wiki >>> for getting the cvs version of v4l, doing a make distclean and tried >>> again. This did not help. >>> >>> I'm making progress but once again stuck, google doesn't have any ideas, >>> and I've seen scattered thoughts on similar problems on the mailing >>> lists, but nothing seems to help. Anyone have any suggestions as to >>> where to go next or experience with this problem? >>> >>> _______________________________________________ >>> ivtv-users mailing list >>> [email protected] >>> http://ivtvdriver.org/mailman/listinfo/ivtv-users >>> >>> >> _______________________________________________ >> ivtv-users mailing list >> [email protected] >> http://ivtvdriver.org/mailman/listinfo/ivtv-users >> > > > _______________________________________________ > ivtv-users mailing list > [email protected] > http://ivtvdriver.org/mailman/listinfo/ivtv-users > _______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
