On Mon, 2008-06-09 at 17:02 -0700, Michael wrote: > 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 Right now, I still have the old delay numbers in there (10 & 40 msec, 10 & 10 msec). If you can experiment and figure out delay numbers lower than 100 msec that appear to work, I'll check those in. Four delays of 100 msec is a bit long (0.4 seconds is noticeable by people) and I'd rather have shorter delays if possible. > 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: [snip] 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. ;) > 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 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 > 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. *sigh* If it's not one thing, it's two. ;) I have no experience with kdetv. Is it trying to access the /dev/video* device nodes or the /dev/dvb/adapter*/* device nodes? > > > 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? > > 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. No need to feel bad. I do it for me first. It's a hobby. :) If I can help someone else then that's just a bonus. I did win one I hope is an MCE version off of eBay. > 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. It won't initialize twice, it'll load the firmware twice. And now I think that reload won't be visible in the logs anymore because of recent changes. Let's see what debug about the tuner reveals. Regards, Andy _______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
