Help: wrong module identification of bt878 (8chips)

Forum for questions and support relating to the 1.24.x releases only.
Locked
m1001101
Posts: 5
Joined: Tue May 18, 2010 12:42 pm

Help: wrong module identification of bt878 (8chips)

Post by m1001101 »

Hi, I've some stability problems with my debian testing surveillace, the system is:

debian testing (2.6.30-1-686)
generic bt878 (8chips) card
4X CCD cams

when I configure some types of realtime visualizations (like via web montage, zmviewer, xlib_shm) there is the same problem, after some time 1/2 hours viewer crash...

when I check dmesg find that my bt878 card is recognized by system as saa7134!

however zm work in modect without problems.

my dmesg higlights:

Code: Select all

[    5.086494] saa7130/34: v4l2 driver version 0.2.15 loaded
[    5.086543] saa7134 0000:04:08.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[    5.086550] saa7130[0]: found at 0000:04:08.0, rev: 1, irq: 16, latency: 64,
mmio: 0xfebffc00
[    5.086557] saa7134: <rant>
[    5.086558] saa7134:  Congratulations!  Your TV card vendor saved a few
[    5.086559] saa7134:  cents for a eeprom, thus your pci board has no
[    5.086560] saa7134:  subsystem ID and I can't identify it automatically
[    5.086561] saa7134: </rant>
[    5.086561] saa7134: I feel better now.  Ok, here are the good news:
[    5.086562] saa7134: You can use the card=<nr> insmod option to specify
[    5.086563] saa7134: which board do you have.  The list:

[...] long list

[    5.812696] saa7130[7]: subsystem: 1131:0000, board: UNKNOWN/GENERIC [card=0,autodetected]
[    5.812723] saa7130[7]: board init: gpio is 10000
[    5.812728] IRQ 19/saa7130[7]: IRQF_DISABLED is not guaranteed on shared IRQs
[    5.916079] saa7130[7]: Huh, no eeprom present (err=-5)?
[    5.916159] saa7130[7]: registered device video7 [v4l2]
[    5.916197] saa7130[7]: registered device vbi7

How I can to force the system to recognize right the card?
I think that the correct module is bttv with 77 card type...

Thanks for help! :wink:
m1001101
Posts: 5
Joined: Tue May 18, 2010 12:42 pm

Post by m1001101 »

For the moment found a very dirty solution :twisted:

auto-launching xlib_shm after auto-login in gnome with this simple script:

while [ 1 ]
do
sudo xlib_shm -m1 ecc...
done

so when xlib crashes self reload, and added 2 crontab to kill (and autoreload by script) xlib 5 minutes after change zm profile with zmpkg.pl.

here the command in crontab to kill xlib executed by root's cron:

kill $(ps -e |grep xlib_shm |cut -d" " -f1)


I know is a very very dirty solution to prevent xlib to close...

Many thank at someone help me to find a better solution! :D

Thanks

M
Locked