Hans Verkuil wrote:
On Thursday 15 November 2007 16:43:05 Mark Paulus wrote:
I was playing with the new drivers last night, and noticed an oddity
on my Avermedia A180 card (SAA7134 based, used for QAM256). I was
having issues getting a LOCK on one frequency. So, I booted back to
the old modules, and got a LOCK right away as expected.
The dmesg output should be the same as what I posted originally. I
have added the dmesg output from the boot that allows the card to
work as expected.
What I did was create a copy of my /lib/modules/`uname -r`.orig.
Then I installed your experimental drivers, and rebooted. I have a
link in /lib/modules, so I can rapidly switch module base and reboot,
to see the results of modules.
In addition, I have attached the output from the azap sessions.
Hi Mark,
You should probably try to use the latest v4l-dvb master repository and
see if this problem has been fixed already. If not, you should report
it to the video4linux mailinglist. The ivtv-i2c tree also has bleeding
edge versions of other drivers, so bugs are not impossible. But it's
not something ivtv introduced.
Thanks for testing!
Regards,
Hans
I have been playing with this box some more, and I think the issue I
reported about not getting a good FE_LOCK is a different problem.
I have 2 different DVB cards (Avermedia A180 & pcHDTV RT5 Lite), and
I think what is happening is that they are getting put in to
/dev/dvb/adapter[n] randomly by udev, based upon who-knows-what. The
pcHDTV doesn't seem to tune quite as well as the Avermedia card, so
depending upon which card I hit, that could determine the results I see.
(We REALLY!!! need some better udev rules for loading and fixing video
card identifiers.)
begin:vcard
fn:Mark Paulus
n:Paulus;Mark
org:MCI;Lec Interfaces / 40419
adr;dom:;;2424 Garden of the Gods Rd;Colorado Springs;CO;80919
email;internet:[EMAIL PROTECTED]
title:Mark Paulus
tel;work:719-535-5578
tel;pager:800-pagemci / 1406052
tel;home:v622-5578
version:2.1
end:vcard
_______________________________________________
ivtv-devel mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-devel
