Ok, I've had a bit more of a look at everything, and have found the
following:
modprobe tuner gives the following dmesg output:
Linux video capture interface: v1.00
i2c-core.o: i2c core module
saa7130/34: v4l2 driver version 0.1.4 loaded
PCI: Found IRQ 10 for device 02:03.0
saa7134[0]: found at 02:03.0, rev: 1, irq: 10, latency: 32, mmio: 0xdf001000
saa7134[0]: subsystem: 1131:0000, board: LifeView FlyVIDEO3000
i2c-core.o: adapter saa7134[0] registered as adapter 0.
saa7134[0]: i2c eeprom read error #1 rc=-5
saa7134[0]/video: DCSDT: no signal
i2c-core.o: driver i2c TV tuner driver registered.
tuner: probing saa7134[0] i2c adapter [id=0x90000]
tuner: chip found @ 0xc2
i2c-core.o: client [Philips PAL] registered to adapter [saa7134[0]](pos. 0).
saa7134[0]/video: DCSDT: no signal
saa7134[0]: registered device video0
saa7134[0]: registered device vbi0
saa7134[0]: registered device radio0
saa7134[0]: registered device dsp4
saa7134[0]: registered device mixer2
I'm a bit worried about the eeprom read error and the DCSDT: no signal
messages. Does anyone know what these actually mean? I'm in Australia
- it is a PAL BG card.
lspci gives:
02:03.0 Multimedia controller: Philips Semiconductors: Unknown device
7134 (rev 01)
cat /proc/pci gives:
Bus 2, device 3, function 0:
Multimedia controller: PCI device 1131:7134 (Philips Semiconductors)
(rev 1).
IRQ 10.
Master Capable. Latency=32. Min Gnt=15.Max Lat=38.
Non-prefetchable 32 bit memory at 0xdf001000 [0xdf0013ff].
How do I set the debug=1 option? I tried modprobe saa7134 debug=1, but
that didn't work.
Robert
Robert Reid wrote:
Hi all,
Sorry about the list of dumb questions that is about to follow.....
I have a Flyvideo 3000 card, and I've downloaded and installed Gerd's
saa7134 driver, on a 2.4.19-pre1 kernel. The saa7134 modules
modprobed fine, but now what do I do?
If I run in xawtv, I can't find any tuned in channels. Scan TV
doesn't find any channels.
I'm guessing that somehow the tuner isn't working, but I really don't
know. What do I do next?
Thanks,
Robert
