On Sun, 2008-06-29 at 21:04 -0700, Michael wrote: > > > > 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. > > > > > 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?
Unfortunately you are correct. I'd suggest a binary search. I'd also start with the recovery from reset delay values first. In fact, I just added reset recovery delay in cx18-i2c.c that was missing. Please see the latest change to http://linuxtv.org/hg/~awalls/cx18-i2c . > > > > 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... It worked on the second load with the tveeprom debug enabled. You can look in /var/log/messages (or wherever your syslogd puts a copy of the messages) for the timestamps if you are ever uncertain. > > >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. For the case where you see the valid EEPROM message, it would be useful. If it's too big for the list, send a compressed archive in an off-list mail to me. > > 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. In all your output I never see any messages about tuner, tuner-simple, tdaxxxx, teaxxxx, or any other tuner module. Since these things are connected to the I2C bus, messages about them are relevant. You need the analog tuner to do analog TV captures using /dev/video0 and listen to radio using /dev/radio0 and /dev/video24. So my question is are tuner modules being built and loaded? Or is the tuner driver code built into you kernel (which would be a mismatch for the latest module code from linuxtv.org)? > 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? The cs5345 module is loaded and working, so all you really need is to make sure the analog tuner modules are loaded and working. I haven't seen any tuner module related output in the logs you've sent, so I can only assume they are not actually loaded. You can try $ ivtv-radio -f 107.3 to see if FM radio works or not. The example above tries to tune to 107.3 MHz, using /dev/radio0 and using "apaly" to play the PCM audio coming from /dev/video24 (IIRC). The absence of tuner-simple.ko on your system also makes me wonder if the build process is actually building and installing the tuner modules when you build the copy of the repository you get from linuxtv.org. Can you confirm if they are? Regards, Andy _______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
