Hi Mauro,

drxk driver seems to have 2 issue with w_scan:

- dvb-t tune error while scanning ("solved" by forcing w_scan to open
dvb-t fe without autoscan)
- dvb-t scan fail

so... we should have an issue that when the driver release dvb-c
adapter drxk (or xc5000?) stay in dvb-c mode

Can you check if you can replicate my error and if Terratec H5 have same issue?

follow the test:....

I build w_scan 20111011 like you

-unplug tuner
-replug tuner

dmesg says:
[ 1030.370462] DVB: registering new adapter (em28xx #0)
[ 1030.370470] DVB: registering adapter 0 frontend 0 (DRXK DVB-C)...
[ 1030.370689] DVB: registering adapter 0 frontend 1 (DRXK DVB-T)...
[ 1030.371393] em28xx #0: Successfully loaded em28xx-dvb

- w_scan -a /dev/dvb/adapter0/frontend1  (the autodetect of adapter is disabled)

dmesg says:
[ 1117.000725] xc5000: waiting for firmware upload (dvb-fe-xc5000-1.6.114.fw)...
[ 1117.005404] xc5000: firmware read 12401 bytes.
[ 1117.005410] xc5000: firmware uploading...
[ 1117.416085] xc5000: firmware upload complete...

However, like Fedrik, I don't get errors on dmesg but w_scan ends with

 ERROR: Sorry - i couldn't get any working frequency/transponder
 Nothing to scan!!

- w_scan -a /dev/dvb/adapter0/frontend1  -I it-All
no error on dmesg...


- w_scan -f t -c IT
Leaving autodetect turned on I get
[  794.964818] drxk: Error -22 on QAMSetSymbolrate
[  794.964827] drxk: Error -22 on SetQAM
[  794.964832] drxk: Error -22 on Start
[  795.164518] drxk: Error -22 on QAMSetSymbolrate
[  795.164528] drxk: Error -22 on SetQAM
[  795.164534] drxk: Error -22 on Start

trying scan now...
 scan -f1 it-All
dmesg days
[ 2044.103987] drxk: Error -22 on Start
[ 2045.293728] drxk: Error -22 on SetQAM
[ 2045.293738] drxk: Error -22 on Start
[ 2045.431231] drxk: Error -22 on QAMSetSymbolrate
[ 2045.431241] drxk: Error -22 on SetQAM
[ 2045.431246] drxk: Error -22 on Start


regards,

Eddi
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to