On 01/19/05 12:23, Charles Waddell wrote:
I used Jarod's instructions to install mythtv with apt-get. I do not seem to have either eeprom or tveeprom modules on the system. here is an lsmod, and all I get is static on all channels, I eliminated the physical connection as the problem as the card works under windows and the cable works on a standard tv:
Module Size Used by bttv 148497 0
Do you actually have a BTTV card?
My guess: you have
# WinTV PVR-x50 support alias char-major-81 bttv alias char-major-81-0 ivtv
when you want
# WinTV PVR-x50 support alias char-major-81 videodev alias char-major-81-0 ivtv
in your modprobe.conf. Note that even if you do have a bttv card, it's critical that you load ivtv first. I.e.:
alias char-major-81 videodev # WinTV PVR-x50 support alias char-major-81-0 ivtv # BTTV support alias char-major-81-1 bttv
And make sure ivtv is loaded first (by either positioning the BTTV card last and/or making sure you do an explicit "modprobe ivtv" before BTTV is initialized.
tveeprom 10776 0
You seem to have tveeprom, so it's probably a configuration issue inside your modprobe.conf.
... here is the ivtv section of dmesg:
Actually, just a partial... As explained in Jarod's guide, you should get the ivtv initialization information with:
tac /var/log/messages |
sed -n '/=\ \ END INIT IVTV\ \ =/,/= START INIT IVTV =/p;
/= START INIT IVTV =/q' |
tacThe reason is because many of the most important messages do not contain the string "ivtv", so "grep ivtv" doesn't work...
ivtv: i2c client addr: 0x50 not found! ivtv: Error -19 reading Hauppauge eeprom. ivtv: Possible causes: the tveeprom module was not loaded, or ivtv: the eeprom kernel module was loaded before the tveeprom module.
This is usually caused by the above mentioned configuration problem...
tuner: type set to 39 (LG NTSC (newer TAPC series)) by insmod option tuner: The type=<n> insmod option will go away soon. tuner: Please use the tuner=<n> option provided by tuner: tv aard core driver (bttv, saa7134, ...) instead.
Do *not* specify any module options with the new version of ivtv. Everything should be autodetected for you (there are only about two specific cases where you need to specify options--and they are for non-NTSC users). Therefore, make sure you modprobe.conf contains only:
# WinTV PVR-x50 support alias char-major-81 videodev alias char-major-81-0 ivtv
And take out options for tuner, saa7127, saa7115, msp3400, tveeprom, videodev, and any other module used by ivtv for which you included an option.
people with a similar issue used options tuner type = 39 or options tuner type = 47 in their modprobe.conf file but neither of these was effective on my system, without any option stating the tuner type in modprobe.conf, I cannot even modprobe ivtv.
More likely similar symptoms but caused by different problems. Regardless, there is no reason to include any options on a properly configured (NTSC) system.
Mike
------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ ivtv-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ivtv-devel
