Please help me install w_scan for my DVICO PCI card

Making progress - re booted a few times and now the card is detected and performs a scan.
The scan returns no channels - so I am presuming I now need to instal an initial scan file.

dmesg now looks like this
 10.255923] Linux video capture interface: v2.00
[ 10.274057] synaptics was reset on resume, see synaptics_resume_reset if you have trouble on resume
[ 10.411315] cx88/0: cx2388x v4l2 driver version 0.0.7 loaded
[ 10.411393] cx8800 0000:02:02.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 10.412983] cx88[0]: subsystem: 18ac:db40, board: DViCO FusionHDTV DVB-T Hybrid [card=46,autodetected], frontend(s): 1
[ 10.412990] cx88[0]: TV tuner type 72, Radio tuner type -1
[ 10.423280] cx88/2: cx2388x MPEG-TS Driver Manager version 0.0.7 loaded
[ 10.496666] cx2388x alsa driver version 0.0.7 loaded
[ 10.561409] Intel ICH 0000:00:1f.5: PCI INT B -> GSI 17 (level, low) -> IRQ 17
[ 10.561519] Intel ICH 0000:00:1f.5: setting latency timer to 64
[ 10.574860] tuner 0-0061: chip found @ 0xc2 (cx88[0])
[ 10.698187] tuner-simple 0-0061: creating new instance
[ 10.698195] tuner-simple 0-0061: type set to 72 (Thomson FE6600)
[ 10.699018] cx88[0]/0: found at 0000:02:02.0, rev: 5, irq: 17, latency: 32, mmio: 0xfb000000
[ 10.699188] cx88[0]/0: registered device video0 [v4l2]
[ 10.699247] cx88[0]/0: registered device vbi0
[ 10.701081] cx88[0]/2: cx2388x 8802 Driver Manager
[ 10.701110] cx88-mpeg driver manager 0000:02:02.2: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 10.701128] cx88[0]/2: found at 0000:02:02.2, rev: 5, irq: 17, latency: 32, mmio: 0xfd000000
[ 10.701477] cx88_audio 0000:02:02.1: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 10.701526] cx88[0]/1: CX88x/0: ALSA support for cx2388x boards
[ 10.741624] psmouse serio1: ID: 10 00 64<4>logips2pp: Detected unknown logitech mouse model 89
[ 10.847905] cx88/2: cx2388x dvb driver version 0.0.7 loaded
[ 10.847911] cx88/2: registering cx8802 driver, type: dvb access: shared
[ 10.847917] cx88[0]/2: subsystem: 18ac:db40, board: DViCO FusionHDTV DVB-T Hybrid [card=46]
[ 10.847923] cx88[0]/2: cx2388x based DVB/ATSC card
[ 10.847927] cx8802_alloc_frontends() allocating 1 frontend(s)
[ 10.899619] tuner-simple 0-0061: attaching existing instance
[ 10.899624] tuner-simple 0-0061: type set to 72 (Thomson FE6600)
[ 10.900580] DVB: registering new adapter (cx88[0])
[ 10.900585] DVB: registering adapter 0 frontend 0 (Zarlink ZL10353 DVB-T)...

I have located the generic inital scan file for my province on the TV wiki and copied this in several places where the applications will find them, but now I am having the same problem as before and the card is not detected.

Can anybody help me follow this instruction from dmesg output excerpt

[ 11.134556] cx88[0]: Your board has no valid PCI Subsystem ID and thus can't
[ 11.134560] cx88[0]: be autodetected. Please pass card=<n> insmod option to
[ 11.134562] cx88[0]: workaround that. Redirect complaints to the vendor of
[ 11.134564] cx88[0]: the TV card. Best regards,
[ 11.134565] cx88[0]: -- tux
[ 11.134573] cx88[0]: Here is a list of valid choices for the card=<n> insmod option:
**I have deleted a few lines to save space
[ 11.134738] cx88[0]: card=46 -> DViCO FusionHDTV DVB-T Hybrid

The correct syntax is $ insmod [filename] [argument]
What filename?

Hamish

A miracle!

I restart the computer and get the following dmesg output with subsystem id for the correct card

cx88[0]: subsystem: 18ac:db40, board: DViCO FusionHDTV DVB-T Hybrid [card=46,autodetected], frontend(s): 1
[ 11.144502] cx88[0]: TV tuner type 72, Radio tuner type -1
[ 11.150828] cx88/2: cx2388x MPEG-TS Driver Manager version 0.0.6 loaded
[ 11.237008] cx2388x alsa driver version 0.0.6 loaded
[ 11.288163] tuner' 0-0061: chip found @ 0xc2 (cx88[0])
[ 11.351030] Intel ICH 0000:00:1f.5: PCI INT B -> GSI 17 (level, low) -> IRQ 17
[ 11.351129] Intel ICH 0000:00:1f.5: setting latency timer to 64
[ 11.403954] tuner-simple 0-0061: creating new instance
[ 11.403963] tuner-simple 0-0061: type set to 72 (Thomson FE6600)
[ 11.404826] cx88[0]/0: found at 0000:02:02.0, rev: 5, irq: 17, latency: 32, mmio: 0xfb000000
[ 11.405001] cx88[0]/0: registered device video0 [v4l2]
[ 11.405049] cx88[0]/0: registered device vbi0
[ 11.406120] cx88[0]/2: cx2388x 8802 Driver Manager
[ 11.406142] cx88-mpeg driver manager 0000:02:02.2: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 11.406155] cx88[0]/2: found at 0000:02:02.2, rev: 5, irq: 17, latency: 32, mmio: 0xfd000000
[ 11.406178] cx8802_probe() allocating 1 frontend(s)
[ 11.406293] cx88_audio 0000:02:02.1: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 11.406338] cx88[0]/1: CX88x/0: ALSA support for cx2388x boards
[ 11.424733] cx88/2: cx2388x dvb driver version 0.0.6 loaded
[ 11.424740] cx88/2: registering cx8802 driver, type: dvb access: shared
[ 11.424747] cx88[0]/2: subsystem: 18ac:db40, board: DViCO FusionHDTV DVB-T Hybrid [card=46]
[ 11.424753] cx88[0]/2: cx2388x based DVB/ATSC card
[ 11.513374] tuner-simple 0-0061: attaching existing instance
[ 11.513379] tuner-simple 0-0061: type set to 72 (Thomson FE6600)
[ 11.514320] DVB: registering new adapter (cx88[0])
[ 11.514324] DVB: registering adapter 0 frontend 0 (Zarlink ZL10353 DVB-T)...
[ 11.572795] input: ImExPS/2 Logitech Explorer Mouse as /devices/platform/i8042/serio1/input/input5

However when I start Me-TV and scan for channels by location, the scan produces no channels and then Me Tv produces an error message saying "There are no available DVB tuner devices."

By the way, if this does not work, I think the answer to the previous question is
$ sudo modprobe cx88xx card=46
According to the insmod man page, it is outdated so use modprobe instead.

$ dmesg | grep tuner
produces this output to the command line - it looks as though the card is detected but the tuner isn't or something?

[ 11.164601] cx88[0]: TV tuner type -1, Radio tuner type -1
[ 11.404087] tuner' 0-0042: chip found @ 0x84 (cx88[0])
[ 11.415117] tuner' 0-0043: chip found @ 0x86 (cx88[0])
[ 11.418005] tuner' 0-004a: chip found @ 0x94 (cx88[0])
[ 11.420871] tuner' 0-004b: chip found @ 0x96 (cx88[0])
[ 11.431287] tuner' 0-0060: chip found @ 0xc0 (cx88[0])
[ 11.431505] tuner' 0-0061: chip found @ 0xc2 (cx88[0])
[ 11.431702] tuner' 0-0062: chip found @ 0xc4 (cx88[0])
[ 11.431907] tuner' 0-0063: chip found @ 0xc6 (cx88[0])
[ 11.432121] tuner' 0-0064: chip found @ 0xc8 (cx88[0])
[ 11.432318] tuner' 0-0065: chip found @ 0xca (cx88[0])
[ 11.432516] tuner' 0-0066: chip found @ 0xcc (cx88[0])
[ 11.432715] tuner' 0-0067: chip found @ 0xce (cx88[0])
[ 11.432915] tuner' 0-0068: chip found @ 0xd0 (cx88[0])
[ 11.433118] tuner' 0-0069: chip found @ 0xd2 (cx88[0])
[ 11.433322] tuner' 0-006a: chip found @ 0xd4 (cx88[0])
[ 11.433523] tuner' 0-006c: chip found @ 0xd8 (cx88[0])
[ 11.433724] tuner' 0-006d: chip found @ 0xda (cx88[0])
[ 11.433926] tuner' 0-006e: chip found @ 0xdc (cx88[0])
[ 11.475118] tuner' 0-0060: tuner type not set

* What version of Me TV are you using?
* What DVB standard are you using? (A/T/S/C)
* What's under /dev/dvb/adapter0/* ?

Thanks for answer Michael

me-tv 0.7.16
DVB-T (Australia)
/dev/dvb/adapter0/demux0, dvr0 ,frontend0, net0

Hamish

Mate, use the stable release, Me TV 1.0.0. For Jaunty, you can get it from:

* PPA (prefered): https://launchpad.net/~me-tv-development/+archive/ppa
* deb: http://launchpad.net/me-tv/stable/1.0.0/+download/me-tv_1.0.0-0ubuntu1~jaunty1_i386.deb

Why?

* Me TV 1.0.0 is the most stable version available and has only one known bug after being released 2 months ago
* The newer package depends on the "dvb-apps" package which is where you are supposed to get you initial tuning files from, install and see the difference.

Now, if you've got a frontend0 and Me TV is saying "There are no available DVB tuner devices." then the tuner is probably already being used by another application. Please make sure that this is not the case

OK have me-tv 1.0.0

still getting same message "no available DVB tuner"
tried restarting
$ dmesg
reveals the card is not autodetecting anymore, even if I use
$ sudo modprobe cx88xx card=46

How do I check the device is not active in another application?

/dev/dvb ... has vanished
Thanks again for your help

If /dev/dvb is not there then you are truly having hardware/driver issues. You'll need to resolve those before Me TV will work.

Sorry, My mistake, /dev/dvb/adapter0 contains 4 files - demux0, dvr0, frontend0 and net0

I see what you mean about me-tv 1.0.0 detects device no problem

I have checked with a regular TV and I have a strong signal.

Now I need an initial scan file for me-tv
the generic ones provided in dvb-apps do not work
the western australian one from http://www.linuxtv.org/wiki/index.php/Western_Australia does not work
tuner appears to be working, but there is a blank output from following
me@ava:~$ w_scan -ft -x >> /home/ava/chanel
w_scan version 20081106
Info: using DVB adapter auto detection.
   Found DVB-T frontend. Using adapter /dev/dvb/adapter0/frontend0
-_-_-_-_ Getting frontend capabilities-_-_-_-_
frontend Zarlink ZL10353 DVB-T supports
INVERSION_AUTO
QAM_AUTO
TRANSMISSION_MODE_AUTO
GUARD_INTERVAL_AUTO
HIERARCHY_AUTO
FEC_AUTO
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
177500:
184500:
191500:
198500:
205500:
212500:
219500:
226500:
474000:
482000:
490000:
498000:
506000:
514000:
522000:
530000:
538000:
546000:
554000:
562000:
570000:
578000:
586000:
594000:
602000:
610000:
618000:
626000:
634000:
642000:
650000:
658000:
666000:
674000:
682000:
690000:
698000:
706000:
714000:
722000:
730000:
738000:
746000:
754000:
762000:
770000:
778000:
786000:
794000:
802000:
810000:
818000:
826000:
834000:
842000:
850000:
858000:
ERROR: Sorry - i couldn't get any working frequency/transponder
 Nothing to scan!!
dumping lists (0 services)
Done.

Correction

The generic western australian scan file from the linux wiki is in a different format from that found in /dvb-apps/util/scan/dvb-t/au-TOWN therefore me-tv give the eror message "UNABLE TO PROCESS A LINE IN THAT FILE" or something like that

I am manually re-typing some of that format to see if me-tv will scan them.

I am afraid that little trick did not work either, me-tv produced the same error message
"me-tv could not process a line in the initial tuning file"
I am located in the central west, 500km from Perth, so the frequencies are probably the siimilar to Perth but that file does not work either, I have tried a random assortment of Australian files which appear to make a scan work in me-tv but do not produce working transponder frequencies.

Finally found a sensible guide to w_scan
I think I have been using the wrong command format to generate an initial scan file.
http://ubuntuforums.org/showthread.php?t=1153366&highlight=w_scan
mentions w_scan project
http://edafe.org/vdr/w_scan/
I will try the examples of w_scan format to make my local file.
and the repository
https://launchpad.net/ubuntu/+source.../+build/872551

$ dmesg | grep -i dvb
might give more clues
also going to try different format for command w_scan
w_scan -c AU -x initial-tuning-data.txt

Interesting
The version of w_scan I have been using is 20081106 much older than specified on wirbel blog at
http://edafe.org/vdr/w_scan/
this version does not recognize the -c option for country so I think the fault is with the age of the package.
Now I wish I were a touch more confident in compiling from his instructions.

I managed to download, extract the latest w_scan package
I can follow some of the instructions on the following web page http://edafe.org/vdr/w_scan/
but when I get to
 root@ubuntu:/usr/local/src# cd w_scan
w_scan exists in that location, but the command to change directory does not work.
If I check with the GUI, the properties for that file says "link (broken) (inode/symlink)"

I am completely stumped and I believe it is because I need to log in as root user, but I do not know the password.
obviously I do not know what I am doing and I am very frightened.
But I really want the TV card to work, and I believe I need the scan file from this program.

Trying a new Query as this is miles from where I started - moderator feel welcome to delete.