> > > So you didn't increase the mdelay()'s in the bottom of cx18-i2c.c, > > > right? > > > > > No, I didn't change the values. > > > > > > If you didn't, given that the analog tuner didn't get recognized in any > > > of your output, you may want to put some larger values in them. You can > > > try 100 in each of them. If that works to get the analog tuner > > > initialized, we can work our way down to shorter values. > > > > > Do you want me to try changing both to 100, or leave the first one at 10, > > as > we did last time? > > Try changing both. What we are trying to do is reset the analog tuner. > These is no harm in holding reset lines asserted for longer than the > minimum interval or waiting too long for the tuner to recover and become > ready. If the delays are too short, then the reset of the device might > not happen properly. > Ok, will do. Results posted below. > > > > > > > You may also want to increase the "msecs_asserted" and "msecs_recovery" > > > values in cx18-cards.c. Try 100 in all of them. If that works to get > > > the eeprom read properly on the first try, we can work our way down to > > > shorter values. > > > > > > > > Try this with the reset3 patch you sent, correct? > > Yes. Again there's no harm in having reset of device take longer than > it needs too and waiting around. If the delays aren't long enough, a > device might not actually get reset. > > > > > What should work for you is: > > > > > > 1. analog capture from line in (S-Video or Composite) > > > 2. digital video scan and captures (ATSC QAM or 8VSB). > > > > > > So give it a try! :) > > > > > > > > > > In a previous email, you said to try this for a digital scan: > > scandvb -A 1 -v -a 0 > > /usr/share/dvb-apps/atsc/us-ATSC-center-frequencies-8VSB > > > However, I never was able to have that command work. > > scandvb is a Fedora/RedHat rename of a DVB utility command. I'm not an > expert in the DVB utilities, so feel free to google around and figure > out what you need to do to perform scans. > I'll try to find something about that tonight. The QAM usually picks up an amazing picture for me. > > My command above was specifically to look for over the air 8VSB > terrestrial ATSC broadcasts in the US. Cable uses QAM. If you're not > in the US, OTA 8VSB isn't likely to be in your area. > I am in the US, so I use QAM on the digital tuner.
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. 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 Also as a sidenote, kdetv no longer recognizes my card, as it did yesterday. > > > I then tried using kdetv to scan, however, it wasn't able to pick up any > digital channels. (I know using WinTV in XP, I pick up a few QAM.) > > So you have cable if you get QAM. Brandon Jenkins reported on the > linux-dvb list that something had changed recently with the new mxl5005s > driver that the dvb portion cx18 relies on. With the old mxl500x > module, on a scan he found many more QAM channels than he did with the > mxl5005s driver module. I can't test/debug QAM at the moment, as I > don't have cable TV nor do I have a datasheet for the MXL5005. > > If you already know the QAM channel frequencies and services you receive > in Windows, with some work, you could create a channels.conf file and > tune to the channels anyway. Again, I'm not the expert here. > > > > Also according to kdetv, VBI decoder isn't running. I'm not sure if > > thats > important or not, but it effects a few settings that I can edit in the > program. > > VBI is in work. The cx23418 chip's encoding engine seems to stall > transfers when we ask it for VBI, so we need to get that resolved first. > Ok, that would make sense. > > > 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.) > > > Thanks again for the help! > > 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 lost the first auction, and was just outbid on the second. :( > I have to say, don't buy this card just to help me. I'd feel really bad. But if you do decide to purchase it for any other reason, I bought mine off of NewEgg. It came really fast. However, I'm sure it's a little more then what your going to pay on eBay. http://www.newegg.com/Product/Product.aspx?Item=N82E16815116010 The remote works great in Linux (better then it works in XP) if you follow the instructions: http://www.mypclinuxos.com/forum/index.php?topic=1887.0 I'm sure you'll need to modify the installation to fit your distro. I haven't tried to set up the IR Blaster, but I just found a topic by the same person. I'm going to try that now. (I could not get this working in XP, but I guess thats what happens when your force a Vista remote onto XP. But that MS's OS for yah.) Thanks again! It seems like we're closer, after knocking out EEPROM, but the card doesn't initialize twice, like you said it should. Weird. _______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
