> > > > Heres the dmesg, after applying the patch, changing the #if 0 to #if > > > > 1 in cx18-firmware file, updating both mdelays, msecs_asserted, and > > > > msecs_recovery. It only appeared to initialize once, however, no > > > > invalid EEPROM's anywhere to be seen. > > > > > > OK. I've set up a repository with i2c changes to cx18 that work here: > > > > > > http://linuxtv.org/hg/~awalls/cx18-i2c/ > > > > > > or grab the total archive here: > > > > > > http://linuxtv.org/hg/~awalls/cx18-i2c/archive/tip.tar.bz2 > > > > > Okay, so using the archives from here, I do not have to patch it, correct? > > Right now (as of a minute or so ago) that repository is up to date with > the master v4l-dvb repo (except for an additional IR blaster reset > patch). The master repo and this repo have the I2C reset logic in it > using timeouts of 10 & 40 msecs spec'ed in cx18-cards.c and 10 & 10 msec > specified in cx18-i2c.c. As I recall you upped those numbers all to 100 > msec to get things working - you will likely have change those delay > numbers, but that's it. > > What I'd really like is the smallest numbers that get things working for > you (EEPROM recognized properly). Making someone wait for 0.4 seconds > for every HVR-1600 card they want to initialize is a little long.ell, > you may still have to > > For the purpose of this email, everything is at 100. I'll try small numbers here soon, once I get the chance. Theres no other, "simpler" way then to re-compile it every time with the updated numbers, correct? > > > > > No need to use "modprobe tveeprom debug=1" anymore, if you can always > > > load the EEPROM now - unless you like seeing the full dump of EEPROM > > > bytes. ;) > > > > > Thats works. So, run this instead? > > > > modprobe -r cx18 > > modprobe cx18 cardtype=1 tuner=43 radio=1 ntsc=M > > If your EEPROM gets recognized properly, you need only use > > # modprobe -r cx18 > # modprobe cx18 >
I'm not sure if this is bad news or not... but, when I simply ran modprobe -rcx18 then modprobe cx18, I received invalid EEPROM. So, I ran modprobe -r cx18, modprobe tveeprom debug=1, modprobe cx18 cardtype=1 tuner=43 radio=1 ntsc=M, and heres dmesg. I'm not sure if this is the tveeprom debug, or if it actually loaded the second time... cx18: Start initialization, version 1.0.0 cx18-0: Initializing card #0 cx18-0: Autodetected Hauppauge card cx18-0: cx23418 revision 01010000 (B) tveeprom 0-0050: Encountered bad packet header [00]. Corrupt or not a Hauppauge eeprom. cx18-0: Invalid EEPROM cx18-0: VBI is not yet supported cs5345 0-004c: chip found @ 0x98 (cx18 i2c driver #0-0) cx18-0: Disabled encoder IDX device videodev: "" has no release callback. Please fix your driver for proper sysfs support, see http://lwn.net/Articles/36850/ cx18-0: Registered device video0 for encoder MPEG (2 MB) DVB: registering new adapter (cx18). MXL5005S: Attached at address 0x63 DVB: registering frontend 0 (Samsung S5H1409 QAM/8VSB Frontend)... cx18-0: DVB Frontend registered videodev: "" has no release callback. Please fix your driver for proper sysfs support, see http://lwn.net/Articles/36850/ cx18-0: Registered device video32 for encoder YUV (2 MB) videodev: "" has no release callback. Please fix your driver for proper sysfs support, see http://lwn.net/Articles/36850/ cx18-0: Registered device video24 for encoder PCM audio (1 MB) videodev: "" has no release callback. Please fix your driver for proper sysfs support, see http://lwn.net/Articles/36850/ cx18-0: Registered device radio-64 for encoder radio cx18-0: Initialized card #0: Hauppauge HVR-1600 cx18: End initialization cx18-0: unregister DVB cx18-0: Removed Hauppauge HVR-1600, card #0 Linux video capture interface: v2.00 cx18: Start initialization, version 1.0.0 cx18-0: Initializing card #0 cx18-0: User specified Hauppauge HVR-1600 card cx18-0: cx23418 revision 01010000 (B) tveeprom 0-0050: full 256-byte eeprom dump: tveeprom 0-0050: 00: 00 70 00 44 74 00 00 00 84 09 00 04 20 77 00 40 tveeprom 0-0050: 10: 3c 6e 2d f0 73 05 26 00 84 08 00 06 2d 23 01 00 tveeprom 0-0050: 20: 96 58 8d 72 07 70 73 09 1f 36 73 0a 08 74 73 0b tveeprom 0-0050: 30: 4f 30 72 0e 01 72 10 01 72 11 00 79 25 00 00 00 tveeprom 0-0050: 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 tveeprom 0-0050: 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 tveeprom 0-0050: 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 tveeprom 0-0050: 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 tveeprom 0-0050: 80: 00 00 00 00 84 09 00 04 20 77 00 40 3c 6e 2d f0 tveeprom 0-0050: 90: 73 05 26 00 84 08 00 06 2d 23 01 00 96 58 8d 72 tveeprom 0-0050: a0: 07 70 73 09 1f 36 73 0a 08 74 73 0b 4f 30 72 0e tveeprom 0-0050: b0: 01 72 10 01 72 11 00 79 25 00 00 00 00 00 00 00 tveeprom 0-0050: c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 tveeprom 0-0050: d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 tveeprom 0-0050: e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 tveeprom 0-0050: f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 tveeprom 0-0050: Tag [04] + 8 bytes: 20 77 00 40 3c 6e 2d f0 tveeprom 0-0050: Tag [05] + 2 bytes: 26 00 tveeprom 0-0050: Tag [06] + 7 bytes: 2d 23 01 00 96 58 8d tveeprom 0-0050: Tag [07] + 1 bytes: 70 tveeprom 0-0050: Tag [09] + 2 bytes: 1f 36 tveeprom 0-0050: Tag [0a] + 2 bytes: 08 74 tveeprom 0-0050: Tag [0b] + 2 bytes: 4f 30 tveeprom 0-0050: Tag [0e] + 1 bytes: 01 tveeprom 0-0050: Tag [10] + 1 bytes: 01 tveeprom 0-0050: Not sure what to do with tag [10] tveeprom 0-0050: Tag [11] + 1 bytes: 00 tveeprom 0-0050: Not sure what to do with tag [11] tveeprom 0-0050: Hauppauge model 74541, rev C5B6, serial# 2977340 tveeprom 0-0050: MAC address is 00-0D-FE-2D-6E-3C tveeprom 0-0050: tuner model is Philips FM1236 MK5 (idx 116, type 43) tveeprom 0-0050: TV standards NTSC(M) (eeprom 0x08) tveeprom 0-0050: audio processor is CX23418 (idx 38) tveeprom 0-0050: decoder processor is CX23418 (idx 31) tveeprom 0-0050: has radio, has no IR receiver, has no IR transmitter cx18-0: Autodetected Hauppauge HVR-1600 cx18-0: VBI is not yet supported cs5345 0-004c: chip found @ 0x98 (cx18 i2c driver #0-0) cx18-0: Disabled encoder IDX device videodev: "" has no release callback. Please fix your driver for proper sysfs support, see http://lwn.net/Articles/36850/ cx18-0: Registered device video0 for encoder MPEG (2 MB) DVB: registering new adapter (cx18). MXL5005S: Attached at address 0x63 DVB: registering frontend 0 (Samsung S5H1409 QAM/8VSB Frontend)... cx18-0: DVB Frontend registered videodev: "" has no release callback. Please fix your driver for proper sysfs support, see http://lwn.net/Articles/36850/ cx18-0: Registered device video32 for encoder YUV (2 MB) videodev: "" has no release callback. Please fix your driver for proper sysfs support, see http://lwn.net/Articles/36850/ cx18-0: Registered device video24 for encoder PCM audio (1 MB) videodev: "" has no release callback. Please fix your driver for proper sysfs support, see http://lwn.net/Articles/36850/ cx18-0: Registered device radio-64 for encoder radio cx18-0: Initialized card #0: Hauppauge HVR-1600 cx18: End initialization > > >From the EEPROM data, the driver learns the rest. > > > > Still no tuner init here. :( > > > > > > I'm looking into how to possibly reset the analog tuner properly. > > > > > > You may want to add some lines to your /etc/modprobe.conf to turn on > > > some tuner debug > > > > > > options tuner debug=1 show_i2c=1 > > > options tuner-simple debug=1 > > > > > > > Okay, I added it. > > That should add some messages about tuner load in dmesg > or /var/log/messages, I'd like to see what they say when you run the > modprobe for the cx18 module. > I'm not sure if this will be useful or not with a possible invalid eeprom? If it is, I'll gladly provide it... it just takes me what seems like 10 minutes to scroll through it and highlight it, so if it isn't useful at this point and time, I just don't want to provide useless information. > > This is the next hurdle I want to get over: getting your analog tuner up > and running. I think you might be missing modules for some reason. > > What distro do you use? > PCLinuxOS 2007. > > On your system do you have a tuner-simple.ko module installed > under /lib/modules somewhere? > No, not from what I see. > > I don't have my HVR-1600 MCE board in my system right now, but I have a > non-MCE HVR-1600 and another cx23418 board. Here's what my module > listing looks like: > > $ /sbin/lsmod > Module Size Used by > [...] > tea5767 14596 0 > tda9887 18692 1 > tda8290 21764 0 > mxl5005s 42244 1 > s5h1409 17284 1 > tuner_simple 21396 2 > tuner_types 25472 1 tuner_simple > cs5345 11908 0 > tuner 33484 0 > cx18 90048 0 > dvb_core 82772 1 cx18 > compat_ioctl32 16128 1 cx18 > videodev 41344 3 tuner,cx18,compat_ioctl32 > v4l1_compat 20996 1 videodev > cx2341x 19332 1 cx18 > v4l2_common 18560 4 cs5345,tuner,cx18,cx2341x > tveeprom 21636 1 cx18 > [...] > > > > > > > I tried this: > > > > > > v4l2-ctl -d /dev/video0 -i1 > > > > > > However, I haven't found a view it yet. > > > > > > > > > > "-i1" is the first SVideo input. So you get nothing when you have and > > > > > SVideo source hooked up to the card and use > > > > > > > > > > $ mplayer -cache 8192 /dev/video0 > > > > > > > > > > ? > > > > > > > > > MPlayer 1.0rc2-4.1.1 (C) 2000-2007 MPlayer Team > > > > CPU: AMD Sempron(tm) Processor 3400+ (Family: 15, Model: 47, Stepping: > > > > 2) > > > > CPUflags: MMX: 1 MMX2: 1 3DNow: 1 3DNow2: 1 SSE: 1 SSE2: 1 > > > > Compiled with runtime CPU detection. > > > > > > > > Playing /dev/video0. > > > > Cache fill: 0.00% (0 bytes > > > > > > > > It sorta seems to freeze at this point... nothing happens. (A stream > > > > is > > > coming in, I made sure of that first.) > > > > > > That's really odd. That would mean the CX23418 is outputting any data > > > at all. > > > > > > Do you get a file of size zero when you do this > > > > > > $ cat /dev/video0 > foo.mpg > > > > > > or does it actually have something in it? > > > > > Do you get a file of size zero when you do this repository? And if so, > > do I need to apply any patches, or change the source code at all? (For > > example, increasing the mdelays and such.) > > No changes are needed. This is a diagnostic step to see if the encoder > was outputting anything at all. > > The above cat command copies the mpeg stream to a file. After you > interrupt the command with Ctrl-C, the file should have something in it > (MPEG data). If the file has size 0 (no bytes at all), that means > nothing came out of the encoder. > > > > > > > > > You're welcome. I'm trying to buy a version of the HVR-1600 that you > > > > > have (74551) off of ebay, to see if I can reproduce the problem first > > > > > hand. (Plus I'll have two digital tuners then!) > > > > I did win one I hope is an MCE version off of eBay. > > > > > Do you by chance know the full product name? (Such was 1183WB?) > > No, but it's a Model 74551 and its an MCE board because it has FM radio > and no IR blaster chip. So it must be an 1101 or 1183. > The only difference, from what I looking at, is 1183 comes with a remote, whereas 1101 does not. > > tveeprom 2-0050: Hauppauge model 74551, rev C1A3, serial# 1845764 > tveeprom 2-0050: MAC address is 00-0D-FE-1C-2A-04 > tveeprom 2-0050: tuner model is TCL MFNM05-4 (idx 103, type 43) > tveeprom 2-0050: TV standards NTSC(M) (eeprom 0x08) > tveeprom 2-0050: audio processor is CX23418 (idx 38) > tveeprom 2-0050: decoder processor is CX23418 (idx 31) > tveeprom 2-0050: has radio, has no IR receiver, has no IR transmitter > cx18-1: Autodetected Hauppauge HVR-1600 > > > Of course I had no I2C problems with this board or my 74041 non-MCE > HVR-1600. So I could not reproduce your problem with it. > > For reference your EEPROM said this: > > > tveeprom 0-0050: Hauppauge model 74541, rev C5B6, serial# 2977340 > > tveeprom 0-0050: MAC address is 00-0D-FE-2D-6E-3C > > tveeprom 0-0050: tuner model is Philips FM1236 MK5 (idx 116, type 43) > > tveeprom 0-0050: TV standards NTSC(M) (eeprom 0x08) > > tveeprom 0-0050: audio processor is CX23418 (idx 38) > > tveeprom 0-0050: decoder processor is CX23418 (idx 31) > > tveeprom 0-0050: has radio, has no IR receiver, has no IR transmitter > > cx18-0: Autodetected Hauppauge HVR-1600 > > So our cards have different tuners but the same tuner type number: 43. > (Many of these analog tuners are clones or rebrands of each other or > their designs use the same chips and are very similar.) > Thanks again for the help. Also, would by chance the radio work? I know we've never played with this, but with the lack of video support required, wouldn't it be pretty basic, thus working if only a few features of the card are? _______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
