Journal tqft's Journal: Help please, modprobe.conf question 5
I am trying to get my tv card working.
It is a reasonably fresh debian wheezy install with xfce on top.
The modprobe.conf, boot error message and hardware report are at the paste
http://pastebin.com/ajgL2gqy
It is like the syntax of modprobe is incorrect but nothing I can find says it isn't
Looking through here http://linuxtv.org/wiki/index.php/Cx88_devices_%28cx2388x%29 and the referenced source docs
I have even trawled through various bug systems for this.
It did work under the old Ubuntu 10.10 setup (and earlier).
Anyone got a clue that might help me find the right path (I had oath typed and that is also appropriate).
If you load it by hand does it work? (Score:2)
If you just run modprobe cx88 card=64 does it work?
I'm not sure your pciid is card=64. This guy [ubuntuforums.org] got his 14f1:8800 "kind of" working with =45 or =59 and specifying a separate tuner=, but I think that's an older version of the driver. Other people talk about using cx88-dvb with it, but maybe that loads after cx88 (I haven't messed with video capture since getting a bt878 WinTV card to work about 10 years ago).
Re: (Score:1)
pci id (?) from lshw
*-multimedia:0 UNCLAIMED
description: Multimedia video controller
product: CX23880/1/2/3 PCI Video and Audio Decoder
Re: (Score:2)
It looks like there is no cx88 module at all [cateee.net]. This page here [ubuntuforums.org] says it should be cx88xx which makes the modprobe.conf line options cx88xx card=xx but I'm still not convinced 64 is the right card (was it working as =64 in Ubuntu?). According to the 3.3 kernel card list [mjmwired.net] 64 is for DViCO FusionHDTV DVB-T PRO, with PCI ID of 18ac:db30. The PCI id I was looking at came from the first dump:
Re: (Score:1)
4th time trying to write this response. Laptop & ubuntu power management not happy.
Ran depmod and seemed to make a small difference but no luck.
I tried some different card numbers with options cx88-dvb & cx88xx in modprobe.conf and just using modprobe, no luck and it definitely isn't 56 which panicked the kernel on boot when it was in modprobe.conf
Am trying to open my old setup backup to see if I saved modprobe.conf to see what I used and I also tried searching t see if I had posted it online somew
Re: (Score:1)
Update: still not working but a different error message. On boot starts spamming the log with a whinge about "fallback" and so on. The change - easiest way to check the kernel option settings was compile one and have a look with make xconfig on the way thru compiled without really changing anything. Suspect it is not seeing the firmware in the way it expects. I have seen this error before or something similar.
Might try re-installing the firmware (linux firmware non-free) after a purge, then depmod, upda