A while ago, Gerd did some changes to the audio carried scan detection. This finally fixed my problems with audio carrier. I don't really remember when this was, but I have it with kernel 2.5.65 and patches from www.bytesex.org/patches/2.5 working perfectly. When I load the module, this is what I get: saa7134: no version magic, tainting kernel. saa7130/34: v4l2 driver version 0.2.7 loaded saa7134[0]: found at 00:0c.0, rev: 1, irq: 19, latency: 32, mmio: 0xdc000000 saa7134[0]: subsystem: 153b:1143, board: Terratec Cinergy 600 TV [card=11,autodetected] i2c-dev.o: Registered 'saa7134[0]' as minor 0 saa7134[0]: i2c eeprom 00: 3b 15 43 11 ff ff ff ff ff ff ff ff ff ff ff ff saa7134[0]: i2c eeprom 10: ff ff ff ff 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 tuner: no version magic, tainting kernel. tuner: probing saa7134[0] i2c adapter [id=0x90000] tuner: chip found @ 0xc0 tuner: type set to 5 (Philips PAL_BG (FI1216 and compatibles)) Module tuner cannot be unloaded due to unsafe usage in include/linux/module.h:457 saa7134[0]: registered device video0 [v4l2] saa7134[0]: registered device vbi0 saa7134[0]: registered device radio0 But with kernel 2.5.67 (and still with appropriate pathces from www.bytesex.org/patches/2.5) the carrier scan seems to be worse than ever :( The same with 2.5.68 and patch. 2.5.67 reports 0.2.7 but .68 says 0.2.8. Should I test a 2.4.x kernel, and see if the same problem is there? Best regards, Stian
