On Wed, Aug 31, 2005 Johann Hanne wrote: > I've used a 2.6.3 kernel with the kraxel-patchset (bytesex.org) for a very > long time, and it always worked fine with my "BMK MPEX Tuner" card (saa7134 > card number 23, saa6752hs chip on board). The v4l-device was at /dev/video0 > and the Transport-Stream device was at /dev/video1. Not I've updated my > kernel to 2.6.13 and the TS device is gone. The saa6752hs driver still gets > autoloaded when I do "modprobe saa7134 card=23", but it doesn't seem to > register a device. (I've also created the video1 device node manually, but > this results in a "No such device" error when trying to access it). Is there > a patch which fixes this? ... > 2.6.13 output: > Linux video capture interface: v1.00 > saa7130/34: v4l2 driver version 0.2.14 loaded > PCI: setting IRQ 5 as level-triggered > PCI: Assigned IRQ 5 for device 0000:03:05.0 > saa7134[0]: found at 0000:03:05.0, rev: 1, irq: 5, latency: 64, mmio: > 0xf7800000 > saa7134[0]: subsystem: 1131:6752, board: BMK MPEX Tuner [card=23,insmod > option] > saa7134[0]: board init: gpio is 10000 > saa7134[0]: i2c eeprom 00: 31 11 52 67 06 80 00 01 00 00 00 00 00 00 01 00 > saa7134[0]: i2c eeprom 10: 00 ff c2 0f ff ff ff ff ff ff ff ff ff ff ff ff > saa7134[0]: i2c eeprom 20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff > saa7134[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff > : chip found @ 0xc0 (saa7134[0]) > : All bytes are equal. It is not a TEA5767 > tuner 0-0060: type set to 5 (Philips PAL_BG (FI1216 and compatibles)) > saa6752hs: chip found @ 0x40 > saa7134[0]: registered device video0 [v4l2] > saa7134[0]: registered device vbi0 > > Any ideas??
Try to load saa7134-empress manually. The original code to autoload it led to deadlocks with newer modul-init-tools, but the new autoload code doesn't seem to work. HTH, Johannes _______________________________________________ mpeg2 mailing list mpeg2@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/mpeg2
