As was stated in his first post: > I included > "alias tveeprom tveeprom-ivtv" in my modprobe.conf. I have also tried > using IVTV-0.2.0-rc3e with the same results.
And he's been down the road of deleting all tveeprom's in kernel dir except for ivtv version. So we're trying to see what the state of his modules are. I should have asked him to send output of find /lib/modules/`uname -r` -name "tveeprom*" -ls find /lib/modules/`uname -r` -name "msp3400*" -ls find /lib/modules/`uname -r` -name "ivtv*" -ls On Mon, 31 Jan 2005 20:03:54 -0700, Dan Bartels <[EMAIL PROTECTED]> wrote: > Have you tried adding "alias tveeprom tveeprom-ivtv" as mentioned elsewhen > in this forum? > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Jason Weinstein > Sent: Monday, January 31, 2005 5:50 PM > To: [email protected] > Subject: Re: [ivtv-devel] Cannot resolve "Error -19 reading Hauppauge > eeprom" whenever pcHDTV is installed > > All the *.ko's I removed were replaced once I did make install to > ivtv. I only removed them this time around to be absolutely sure that > those files would be replaced by the ones ivtv installs. I never > thought doing so was necessary, but I after the first install didn't > work I wante to cover all the bases... > > Ok, here's all the ivtv stuff in modules.conf: > > alias char-major-81 videodev > alias char-major-81-0 ivtv > options ivtv ivtv_debug=10 tuner=2 > options msp3400 once=1 simple=1 > add below ivtv msp3400 saa7115 tuner > > I did commented out these three lines that had been automatically > generated during Debian install/config: > > # alias char-major-81 bttv > # post-install bttv insmod tuner > # post-remove bttv rmmod tuner > > I don't think it was necessary to comment out the last two lines, but > once again I just wanted to be sure. > > tveeprom, saa7115, saa7127, and msp3400 all leave the following in > dmesg :"Ignoring new-style parameters is presence of obsolete ones". > I've removed the paremeters for msp3400 from modules.conf and still > get that message. I don't know where some parameters for the other > modules other than in modules.conf. > > Just to be complete, I'm including the ivtv section from dmesg and > lsmod after doing modprobe ivtv. > > Much thanks! > > ivtv: ==================== START INIT IVTV ==================== > ivtv: version 0.2.0 (rc3e) loading > ivtv: Linux version: 2.6.8 PENTIUM4 gcc-3.3 > ivtv: In case of problems please include the debug info > ivtv: between the START INIT IVTV and END INIT IVTV lines when > ivtv: mailing the ivtv-devel mailinglist. > ivtv: Autodetected WinTV PVR 350 card > ivtv: Found an iTVC15 based chip > ivtv: XXX PCI device: 0x0651 vendor: 0x1039 > tveeprom: Ignoring new-style parameters in presence of obsolete ones > 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. > saa7115: Ignoring new-style parameters in presence of obsolete ones > saa7115: starting probe for adapter ivtv i2c driver #0 (0x10005) > saa7127: Ignoring new-style parameters in presence of obsolete ones > saa7127: video encoder driver version V 0.3 loaded > msp3400: Ignoring new-style parameters in presence of obsolete ones > ivtv: Encoder revision: 0x02040024 > ivtv: Encoder Firmware is buggy, use version 0x02040011 > ivtv: Decoder revision: 0x02020023 > ivtv: Configuring WinTV PVR 350 card with 9 streams > ivtv: Create DMA stream 0 using 256 16384 byte buffers 4194304 kbytes total > ivtv: Registered v4l2 device, streamtype 0 minor 0 > ivtv: Create DMA stream 1 > ivtv: Registered v4l2 device, streamtype 1 minor 32 > ivtv: Create stream 2 using 40 52224 byte buffers 2097152 kbytes total > ivtv: Registered v4l2 device, streamtype 2 minor 224 > ivtv: Create DMA stream 3 using 455 4608 byte buffers 2097152 kbytes total > ivtv: Registered v4l2 device, streamtype 3 minor 24 > ivtv: Create stream 4 > ivtv: Registered v4l2 device, streamtype 4 minor 64 > ivtv: Create DMA stream 5 using 16 65536 byte buffers 1048576 kbytes total > ivtv: Registered v4l2 device, streamtype 5 minor 16 > ivtv: Create stream 6 using 1024 2048 byte buffers 262144 kbytes total > ivtv: Registered v4l2 device, streamtype 6 minor 228 > ivtv: Create stream 7 > ivtv: Registered v4l2 device, streamtype 7 minor 232 > ivtv: Create DMA stream 8 > ivtv: Registered v4l2 device, streamtype 8 minor 48 > ivtv: Could not detect tuner standard, defaulting to NTSC. > ivtv: i2c client addr: 0x61 not found! > ivtv: Setting audio matrix to input 3, output 1 > ivtv: i2c client addr: 0x40 not found! > ivtv: Switching standard to NTSC. > ivtv: i2c client addr: 0x61 not found! > ivtv: i2c client addr: 0x40 not found! > ivtv: i2c client addr: 0x21 not found! > ivtv: i2c client addr: 0x44 not found! > ivtv: ivtv_enc_thread: pid = 1903, itv = 0xce8fcfa0 > ivtv: ivtv_dec_thread: pid = 1904, itv = 0xce8fcfa0 > ivtv: Initialized WinTV PVR 350, card #0 > ivtv: ==================== END INIT IVTV ==================== > > ----------------------- > > saa7127 12936 0 > ivtv 812196 0 > tuner 18832 0 > msp3400 28196 0 > saa7115 12932 0 > tveeprom 11936 0 > v4l1_compat 13700 0 > v4l2_common 5120 0 > i2c_algo_bit 9096 1 ivtv > i2c_core 18576 6 > saa7127,tuner,msp3400,saa7115,tveeprom,i2c_algo_bit > md5 3712 1 > ipv6 224260 19 > appletalk 29108 20 > psnap 2948 1 appletalk > llc 5524 1 psnap > 8250 17376 0 > serial_core 18176 1 8250 > af_packet 15880 2 > b44 18052 0 > xfs 505976 1 > videodev 7168 1 ivtv > ide_cd 37536 0 > cdrom 36508 1 ide_cd > genrtc 7796 0 > > On Mon, 31 Jan 2005 17:25:17 -0500, Alan Gonzalez > <[EMAIL PROTECTED]> wrote: > > On Mon, 31 Jan 2005 14:02:18 -0800, Jason Weinstein <[EMAIL PROTECTED]> > wrote: > > > So I'm still stuck with the -19 reading Hauppauge eeprom problem. I > > > did a fresh install of Debian "Sarge" and compiled/installed the 2.6.8 > > > kernel making sure i2c and v4l were set up to installed as modules. > > > > > > If they existed in /lib/modules/2.6.8/kernel/drivers, I removed > > > msp3400.ko, saa7115.ko, saa7127.ko, and tveeprom.ko. I also removed > > > eeprom.ko to be sure it would never load. > > > > > > > The modules in conflict are msp3400 and tveeprom. I don't believe you > > should be touching the other modules you removed. > > > > > > > I then compiled/installed ivtv-0.2.0-rc3e, did modprobe ivtv, and in > > > dmesg I still get: > > > > > > ==================== START INIT IVTV ==================== > > > ivtv: version 0.2.0 (rc3e) loading > > > ivtv: Linux version: 2.6.8 PENTIUM4 gcc-3.3 > > > ivtv: In case of problems please include the debug info > > > ivtv: between the START INIT IVTV and END INIT IVTV lines when > > > ivtv: mailing the ivtv-devel mailinglist. > > > ivtv: Autodetected WinTV PVR 350 card > > > ivtv: Found an iTVC15 based chip > > > ivtv: XXX PCI device: 0x0651 vendor: 0x1039 > > > tveeprom: Ignoring new-style parameters in presence of obsolete ones > > > 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. > > > > > > I have checked and a tveeprom-ivtv does not exist. I tried adding > > > CFLAGS += -DNEW_I2C to Makefile2.6. When I modprobe i2c-algo-bit I do > > > not get anything in dmesg. Modprobing tveeprom only gives me "Ignoring > > > new-style parameters in presence of obsolete ones." I also don't get > > > anything in dmesg doing Modprobe tuner. > > > > Well, this just means you are giving some arguments in the > > modprobe.conf that aren't needed. > > > > I don't believe you've sent the contents of modprobe.conf to the list. > > Can you do that (again if this is a repeat) > > > > > > ------------------------------------------------------- > > 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 > > > > ------------------------------------------------------- > 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 > > ------------------------------------------------------- > 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 > ------------------------------------------------------- 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
