[mythtv-users] FC6 x86_64 and DVB SAA7134
Nathan Faust
nfaust at merchantwarehouse.com
Mon Jun 18 21:44:26 UTC 2007
What about MD5sum your firmware file and compare those numbers?
I know I'm running Ubuntu 7.04, but I have:
Linux 2.6.20-16-generic #2 SMP Thu Jun 7 19:00:28 UTC 2007 x86_64
GNU/Linux
ls -l /lib/firmware/dvb-fe-nxt2004.fw
-rw-r--r-- 1 root root 9584 Apr 20 08:08 /lib/firmware/dvb-fe-nxt2004.fw
md5sum -b /lib/firmware/dvb-fe-nxt2004.fw
2a7e38d3ebc392264f840dcb89e08829 */lib/firmware/dvb-fe-nxt2004.fw
-----Original Message-----
From: mythtv-users-bounces at mythtv.org
[mailto:mythtv-users-bounces at mythtv.org] On Behalf Of Jake Thompson
Sent: Monday, June 18, 2007 4:43 PM
To: Discussion about mythtv
Subject: Re: [mythtv-users] FC6 x86_64 and DVB SAA7134
-rw-r--r-- 1 root root 9584 Dec 20 22:53 dvb-fe-nxt2004.fw
On 6/18/07, Christian Burger <christian.burger at abtg.net > wrote:
Ahh, I am understanding the problem a little better now. I'm
currently running @ 2.6.21-1.3194.fc7 but have ran at every available
kernel revision between FC4 and now. It's never been an issue for me.
What does your firmware look like? When I ls -l mine it shows.
Maybe you have an older revision firmware?
-rw-r--r-- 1 root root 9584 2006-03-28 21:40 dvb-fe-nxt2004.fw
________________________________
From: Jake Thompson [mailto:jake at jakethompson.com]
Sent: Monday, June 18, 2007 3:31 PM
To: christian.burger at abtg.net
Cc: mythtv-users at mythtv.org
Subject: Re: [mythtv-users] FC6 x86_64 and DVB SAA7134
The problem here is that it all works with on kernel rev, but
not another.
I have a channels.conf file that is known good, I am using
channels that have been working for months. If I reboot to the older
kernel, then it will work. I don't see anything that mentions a chnage
to this driver between kernel revs, but I may have missed something.
Here is some output:
dmesg:
> saa7133[0]: found at 0000:01: 07.0, rev: 240, irq: 17,
latency: 32, mmio:
> 0xfdfff000
> saa7133[0]: subsystem: 17de:7350, board: Kworld ATSC110
> [card=90,autodetected]
> saa7133[0]: board init: gpio is 100
> saa7133[0]: i2c eeprom 00: de 17 50 73 ff ff ff ff ff ff ff ff
ff ff ff ff
> saa7133[0]: i2c eeprom 10: ff ff ff ff ff ff ff ff ff ff ff ff
ff ff ff ff
> saa7133[0]: i2c eeprom 20: ff ff ff ff ff ff ff ff ff ff ff ff
ff ff ff ff
> saa7133[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff
ff ff ff ff
> saa7133[0]: i2c eeprom 40: ff ff ff ff ff ff ff ff ff ff ff ff
ff ff ff ff
> saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff
ff ff ff ff
> saa7133[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff
ff ff ff ff
> saa7133[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff
ff ff ff ff
> saa7133[0]: registered device video1 [v4l2]
> saa7133[0]: registered device vbi1
> nxt200x: NXT2004 Detected
> DVB: registering new adapter (saa7133[0])
> DVB: registering frontend 0 (Nextwave NXT200X VSB/QAM
frontend)...
> nxt2004: Waiting for firmware upload (dvb-fe-nxt2004.fw)...
> nxt2004: Waiting for firmware upload(2)...
> nxt2004: Firmware upload complete
>
>
> lsmode | grep saa
> saa7134_dvb 25484 0
> dvb_pll 25348 2 saa7134_dvb
> saa7134 148564 1 saa7134_dvb
> ir_kbd_i2c 18576 1 saa7134
> video_buf_dvb 15748 1 saa7134_dvb
> tda1004x 24068 1 saa7134_dvb
> video_buf 35204 6 saa7134_dvb,saa7134,video_buf
> _dvb,cx8800,cx88xx,bttv
> ir_common 45572 4 saa7134,ir_kbd_i2c,cx88xx,bttv
> compat_ioctl32 17152 3 saa7134,cx8800,bttv
> videodev 36864 5
saa7134,cx8800,cx88xx,bttv,ivtv
> v4l2_common 28288
11
>
saa7134,cx8800,cx88xx,bttv,compat_ioctl32,wm8775,cx25840,tuner,ivtv,cx23
41x,videodev
>
> v4l1_compat 20356 4 saa7134,bttv,ivtv,videodev
> i2c_core 32833 18
>
nxt200x,saa7134_dvb,dvb_pll,saa7134,ir_kbd_i2c,tda1004x,i2c_ec,cx88xx,bt
tv,lirc_i2c,wm8775,cx25840,tuner,ivtv,i2c_algo_bit,tveeprom,i2c_nforce2,
nvidia
On 6/18/07, Christian Burger < christian.burger at abtg.net
<mailto:christian.burger at abtg.net> > wrote:
>
> Message: 12
> Date: Mon, 18 Jun 2007 10:33:11 -0400
> From: "Jake Thompson" < jake-lists at jakethompson.com>
> Subject: [mythtv-users] FC6 x86_64 and DVB SAA7134
> To: "Discussion about mythtv" < mythtv-users at mythtv.org
<mailto:mythtv-users at mythtv.org> >
> Message-ID:
>
<9db3f8e70706180733m79be6898hd4714a567494308b at mail.gmail.com >
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi All,
> I think I may have already posted this, but I am going to try
to give more
> information. I am at a loss for who/where to go to next.
>
>
> I have a FC6 x86_64 machine running the latest kernel
2.6.20-1.2952.fc6, I
> also have the 2.6.20-1.2933.fc6 kernel installed, since this
is the last
> kernel that worked.
>
>
> The problem is I can no lock on channels. This is using
QAM256. If I
> tune
> to a channel that I know works, it shows the signal strength
bouncing
> between 93%and99% but never gains a lock. If I tune to a
channel that I
> know does not work, I get a 99% signal strength and the normal
channel
> lock. So the only difference I see is the "bouncing". On the
2933 kernel
> I
> do not see this, I get a 99% and the channel locks and
displays properly.
>
> This has happened since the 2933 kernel and assumed I had
messed something
> up, but now it has been 2-3 kernel revs and it seems to be a
pattern now.
>
> This is loading the saa7134_dvb driver
>
> Anyone have a similar setup, or does anyone have a suggestion
where else I
> could go for information?
>
> Hardware:
> AMD x86_64
> KWorld ATSC 110 (saa7134_dvb)
> Hauppauge PVR 150 (ivtv, working fine)
>
> Thanks,
> Jake
I have a similar setup using a AverMedia M180 (if my memory is
correct). If
the channel is encrypted you could see these results. When you
do a channel
scan in mythtv-setup are you using cable high freq? Have you
done a channel
scan using atscscan. I do believe there is some info on the
wiki. Anywho
if there is anything I can help with let me know.
More information about the mythtv-users
mailing list