| View previous topic :: View next topic |
| Author |
Message |
alshain
Apprentice
Joined: 02 Aug 2002
Posts: 202
Location: London, UK
|
 Posted: Thu Feb 19, 2004 8:50 am Post subject: bttv wierdness with 2.6.3 |
 |
|
Hello all,
I've just upgraded from 2.6.2-gentoo to 2.6.3-gentoo and my tuner card has stopped working. More precisely I'm getting the following message when I try and watch anything:
tuner: Huh? tv_set is NULL?
bttv0: skipped frame. no signal? high irq latency? [main=3013000,o_vbi=3013018,o_field=1a3b6000,rc=1a3b601c]
bttv0: skipped frame. no signal? high irq latency? [main=3013000,o_vbi=3013018,o_field=1a3b6000,rc=1a3b601c]
bttv0: skipped frame. no signal? high irq latency? [main=3013000,o_vbi=3013018,o_field=1a3b6000,rc=1a3b601c]
I've got a bt878 card and I've always had to specify the tuner type in order for it to be recognised with the type=1 parameter. This gives me:
tuner: chip found @ 0xc2
tuner: type forced to 1 (Philips PAL_I (FI1246 and compatibles)) [insmod]
which is fine - I get this message with both 2.6.2 and 2.6.3.
I've done a search on that 'tuner: Huh? tv_set is NULL?' message but found nothing appropriate. Has anyone else encountered this?
Andrew |
|
| Back to top |
|
 |
alshain
Apprentice
Joined: 02 Aug 2002
Posts: 202
Location: London, UK
|
| Posted: Thu Feb 19, 2004 9:06 am Post subject: Re: bttv wierdness with 2.6.3 |
|
|
| alshain wrote: | Hello all,
I've just upgraded from 2.6.2-gentoo to 2.6.3-gentoo and my tuner card has stopped working. More precisely I'm getting the following message when I try and watch anything:
tuner: Huh? tv_set is NULL?
bttv0: skipped frame. no signal? high irq latency? [main=3013000,o_vbi=3013018,o_field=1a3b6000,rc=1a3b601c]
bttv0: skipped frame. no signal? high irq latency? [main=3013000,o_vbi=3013018,o_field=1a3b6000,rc=1a3b601c]
bttv0: skipped frame. no signal? high irq latency? [main=3013000,o_vbi=3013018,o_field=1a3b6000,rc=1a3b601c]
|
Well, I diff'ed the tuner.c from the two kernels and the only difference was:
1044d1043
< t->type = type;
so I removed this line from the lastest version and now my card works again. 
Maybe I should report this to the video4linux bods!
Andrew |
|
| Back to top |
|
|
ronmon
Veteran
Joined: 15 Apr 2002
Posts: 1043
Location: Key West, FL
|
| Posted: Thu Feb 19, 2004 1:59 pm Post subject: |
|
|
I concur that your fix works. Mine wouldn't run either, until I removed that line and rebuilt the module.
In 2.6.3-mm1 it looked a bit different, though. It was line 998:
|
|
| Back to top |
|
|
Techie2000
Guru
Joined: 16 May 2002
Posts: 344
|
| Posted: Thu Feb 19, 2004 11:32 pm Post subject: |
|
|
I'm using 2.6.3-mm1 and my bttv card works fine.
_________________
"And I'm right. I'm always right, but in this case I'm just a bit more right than I usually am." - Linus Torvalds |
|
| Back to top |
|
|
Schnitz
n00b
Joined: 21 Feb 2004
Posts: 1
|
| Posted: Sat Feb 21, 2004 1:56 pm Post subject: |
|
|
| Same here, your patch fixed it for me. |
|
| Back to top |
|
|
dan2003
Apprentice
Joined: 11 May 2003
Posts: 258
Location: somewhere near london, UK
|
| Posted: Wed Feb 25, 2004 3:10 pm Post subject: |
|
|
I wish i could say the same. I tried this and it casues the module to oops. The following from dmesg.
| Code: | Linux video capture interface: v1.00
bttv: driver version 0.9.12 loaded
bttv: using 8 buffers with 2080k (520 pages) each for capture
bttv: Host bridge needs ETBF enabled.
bttv: Bt8xx card found (0).
PCI: Found IRQ 11 for device 0000:00:0c.0
bttv0: Bt848 (rev 17) at 0000:00:0c.0, irq: 11, latency: 32, mmio: 0xe2000000
bttv0: using: *** UNKNOWN/GENERIC *** [card=0,autodetected]
bttv0: enabling ETBF (430FX/VP3 compatibilty)
bttv0: gpio: en=00000000, out=00000000 in=00fffffb [init]
bttv0: detected by eeprom: Hauppauge (bt848) [card=2]
bttv0: Hauppauge eeprom: model=1024, tuner=Philips FR1216MF MK2 (3), radio=no
bttv0: using tuner=3
bttv0: i2c: checking for MSP34xx @ 0x80... not found
bttv0: i2c: checking for TDA9875 @ 0xb0... not found
bttv0: i2c: checking for TDA7432 @ 0x8a... not found
tvaudio: TV audio decoder + audio/video mux driver
tvaudio: known chips: tda9840,tda9873h,tda9874h/a,tda9850,tda9855,tea6300,tea6420,tda8425,pic16c54 (PV951),ta8874z
tuner: chip found @ 0xc2
tuner: type set to -1 (<NULL>)
Unable to handle kernel NULL pointer dereference at virtual address 0000006c
printing eip:
c01e429f
*pde = 00000000
Oops: 0000 [#1]
CPU: 0
EIP: 0060:[<c01e429f>] Not tainted
EFLAGS: 00010246
EIP is at strlcpy+0x1f/0x70
eax: 00000000 ebx: cfd4b8a0 ecx: ffffffff edx: 0000006c
esi: 00000032 edi: 0000006c ebp: d0f1b2a4 esp: cf8dfe7c
ds: 007b es: 007b ss: 0068
Process modprobe (pid: 3254, threadinfo=cf8de000 task=cf59e6e0)
Stack: cfd4b8a0 cc8de200 d0f1b480 d0ee0612 cc8de2d0 0000006c 00000032 cfd4b8a0
cc8de200 d0ee0898 cc8de200 00000003 00002468 cc8de2c8 cc8de200 d0f1b2d0
d0ebec17 cc8de200 40047401 d0f1b480 d0f1b400 d0f1b2a0 cc8de200 d0f1b2a4
Call Trace:
[<d0ee0612>] set_type+0x92/0xc0 [tuner]
[<d0ee0898>] tuner_command+0x98/0x230 [tuner]
[<d0ebec17>] i2c_clients_command+0xd7/0x100 [i2c_core]
[<d0f096cc>] attach_inform+0x3c/0xa0 [bttv]
[<d0ebe8a6>] i2c_attach_client+0x116/0x160 [i2c_core]
[<d0ee06f8>] tuner_attach+0xb8/0x120 [tuner]
[<d0ebf116>] i2c_probe+0x256/0x310 [i2c_core]
[<d0ee07b0>] tuner_probe+0x50/0x60 [tuner]
[<d0ee0640>] tuner_attach+0x0/0x120 [tuner]
[<d0ebe50c>] i2c_add_driver+0xbc/0xf0 [i2c_core]
[<d0ee0a3f>] tuner_init_module+0xf/0x20 [tuner]
[<c01338f3>] sys_init_module+0x133/0x230
[<c010b28f>] syscall_call+0x7/0xb
Code: f2 ae f7 d1 49 85 f6 89 cb 74 28 39 f1 8d 46 ff 8b 7c 24 10
<6>bttv0: registered device video0
bttv0: registered device vbi0
|
I'm running 2.6.3-gentoo-r1 and comented out line 998
| Code: | if (type >= TUNERS)
return;
//t->type = type;
printk("tuner: type set to %d (%s)\n", t->type,tuners[t->type].name);
strlcpy(c->name, tuners[t->type].name, sizeof(c->name));
|
Maybe there's some difference with this from the mm sources |
|
| Back to top |
|
|
ShaneFalco
n00b
Joined: 25 Feb 2004
Posts: 1
|
| Posted: Wed Feb 25, 2004 3:51 pm Post subject: Different solution |
|
|
Hi everybody, this is my first post...
i used to have the same problem, but i solved loading only the bttv module without "tuner" parameter... guess it does some sort of autodetection now...
hope this helps someone who doesn't want to manually edit the sources...
at least that worked for me...  |
|
| Back to top |
|
|
MasterX
Veteran
Joined: 26 Jun 2003
Posts: 1165
|
| Posted: Wed Feb 25, 2004 4:59 pm Post subject: |
|
|
I had the same problem with 2.6.3 kernel. I did not bother to check what is wrong with tuner.c, I just reboot and load 2.6.1 kernel 
There are some good news, however. bttv 0.9.13 is out. I hope 2.6.4 kernel has the new version.
About the skip frames thing I have them since 2.6.0 kernel. I do not know why, but I learned to live with them. Again, I hope bttv 0.9.13 is taking care of it. |
|
| Back to top |
|
|
dtessier
n00b
Joined: 23 Jan 2003
Posts: 67
Location: Mission Viejo, CA
|
| Posted: Wed Feb 25, 2004 7:30 pm Post subject: |
|
|
| dan2003 wrote: | I'm running 2.6.3-gentoo-r1 and comented out line 998
| Code: | if (type >= TUNERS)
return;
//t->type = type;
printk("tuner: type set to %d (%s)\n", t->type,tuners[t->type].name);
strlcpy(c->name, tuners[t->type].name, sizeof(c->name));
|
Maybe there's some difference with this from the mm sources |
Haha! I ran into the same problem yesterday. You commented out the wrong line! Line 1044 is the want you want to comment out. They're both the same, so it is an easy mistake to make.
_________________
Dan |
|
| Back to top |
|
|
alshain
Apprentice
Joined: 02 Aug 2002
Posts: 202
Location: London, UK
|
| Posted: Wed Feb 25, 2004 8:10 pm Post subject: Re: Different solution |
|
|
| ShaneFalco wrote: | Hi everybody, this is my first post...
i used to have the same problem, but i solved loading only the bttv module without "tuner" parameter... guess it does some sort of autodetection now...
hope this helps someone who doesn't want to manually edit the sources...
at least that worked for me... |
Hi there,
Do you mean you didn't use any options when modprobing the tuner module or you didn't use the tuner module at all?
Either way I think the new code is trying to be too clever. The tuner module has never successfully detected my tuner and I don't think bttv can detect my card either. Previously I could happily override things but I think that extra line confuses it (speaking from my vast ignorance of C++).
Mental note - buy compatible hardware instead of the cheapest whilst thinking 'oh, I'll get it to work somehow'. 
Andrew |
|
| Back to top |
|
|
alshain
Apprentice
Joined: 02 Aug 2002
Posts: 202
Location: London, UK
|
| Posted: Wed Feb 25, 2004 8:13 pm Post subject: |
|
|
| MasterX wrote: | | About the skip frames thing I have them since 2.6.0 kernel. I do not know why, but I learned to live with them. Again, I hope bttv 0.9.13 is taking care of it. |
Ah, I thought I was seeing things! I've tried ignoring it but I keep thinking that if only I was in Windows then this would be smooth! As you say, fingers crossed for the next version.
Andrew |
|
| Back to top |
|
|
kamikaze_gerbil
n00b
Joined: 08 Feb 2003
Posts: 71
Location: Vancouver, Canada
|
| Posted: Sun Mar 07, 2004 6:42 am Post subject: |
|
|
| ronmon wrote: | I concur that your fix works. Mine wouldn't run either, until I removed that line and rebuilt the module.
In 2.6.3-mm1 it looked a bit different, though. It was line 998:
|
Holy crap! That fixed it for me! Thanks! |
|
| Back to top |
|
|
MasterX
Veteran
Joined: 26 Jun 2003
Posts: 1165
|
| Posted: Sun Mar 07, 2004 5:43 pm Post subject: |
|
|
If you have 2.6.3 kernel there is a patch you can apply (go to Google and search for bttv, and then click on home-->patch-->2.6.3). I did that and tuner works fine.
Also, bttv 0.9.13 is out, but I do not know if it will be included in 2.6.4 kernel. If it is not, I think there will be a patch. |
|
| Back to top |
|
|
VeSCeRa
Tux's lil' helper
Joined: 11 Apr 2004
Posts: 111
|
| Posted: Wed Apr 14, 2004 4:39 pm Post subject: |
|
|
so the same thing happened to me
kernel 2.6.3-gentoo-r1
buti am sure that in my previous gentoo installation last week these tuner module was working correctly then in this install i wanted to have the lm_sensors support and added support for some i2c modules and than this thing happened.
and i have solved it by your way comenting that line ( this solution seems that it has nothing to do with the thing i wrote above )
when i was using 2.4.22 kernel i also had some problems with lm_sensors and bttv and applied a patch for them but i cant remember much of it
anyway thanks for your beautiful help |
|
| Back to top |
|
|
|
Multimedia
