Howto use the driver

bbackx · **Joined:** 12 Mar 2008, 09:26 **Posts:** 89

First of all a reminder: the driver is still under development and not yet officially announced. Everything you do is at your own risk and not me or Digital Everywhere or anybody else can be hold responsible if you mess up your system.
It's all at your own risk.

The howto can be found here.
As I state at the end, you can have problems with the graphic and audio drivers when booting your custom kernel. I'll try to figure that out asap. If somebody else knows the solution, please share it (because I'm really busy for the moment and don't know when I'll find the time to look after it).

vertiger · **Joined:** 02 May 2008, 23:19 **Posts:** 4

tried your howto - it had worked so far (i do not use your irda.patch because the file is broken)

but i have encountered another problem:
kaffeine thinks my DVB-C device is a DVB-S
no scanning possible

Code:

root@dualHead:~# w_scan -a 0 -f c
w_scan version 20080105
-_-_-_-_ Getting frontend capabilities-_-_-_-_ 
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_ 
ERROR: Sorry - i couldn't get any working frequency/transponder
 Nothing to scan!!
dumping lists (0 services)
Done.
root@dualHead:~# dmesg | grep fire
[    0.000000] Linux version 2.6.26-rc2-firesat (root@dualHead) (gcc version 4.2.3 (Ubuntu 4.2.3-2ubuntu7)) #1 SMP Thu May 15 20:52:24 CEST 2008
[   21.670161] firesat_probe: loading device
[   21.768593] firesat_probe: subunit count = 1
[  296.457474] firesat_ca_io_open!
[  296.457495] firesat_ca_io_release!
[  300.300589] firesat_start_feed (pid 17)
[  300.300589] firesat_channel_allocate
[  300.300589] firesat_channel_allocate: channel 0: active = 0, pid = 0x0
[  300.840296] firesat_start_feed (pid 16)
[  300.840302] firesat_channel_allocate
[  300.840305] firesat_channel_allocate: channel 0: active = 1, pid = 0x11
[  300.840307] firesat_channel_allocate: channel 1: active = 0, pid = 0x0
[  306.039201] firesat_stop_feed (pid 17)
[  364.359047] firesat_stop_feed (pid 16)
root@dualHead:~# dmesg | grep DVB
[   21.868572] AVCIdentifySubunit: found DVB/C
[   21.868578] DVB: registering new adapter (<NULL>)
[   21.868665] DVB: registering frontend 0 ()...
[  115.932820] DVB: frontend 0 frequency limits undefined - fix the driver
[  164.754574] DVB: frontend 0 frequency limits undefined - fix the driver
[  190.385683] DVB: frontend 0 frequency limits undefined - fix the driver
[  190.794497] DVB: frontend 0 frequency limits undefined - fix the driver
[  296.457474] DVB: frontend 0 frequency limits undefined - fix the driver
[  296.756466] DVB: frontend 0 frequency limits undefined - fix the driver
[  557.718461] DVB: frontend 0 frequency limits undefined - fix the driver
[  823.180298] DVB: frontend 0 frequency limits undefined - fix the driver
root@dualHead:~# 

bbackx · **Joined:** 12 Mar 2008, 09:26 **Posts:** 89

I'll have a look at the patch asap, thanks for pointing out (last-minute addition).

About the other problem:
Very strange that kaffeine thinks it's a DVB-C device

I'll have a look at it when I can, but I'm really busy now.
My final year thesis is due in 2 weeks, so I hope you understand that has my attention now. I'll see when/if I find some time...

MindFlayer · **Posted:** 17 May 2008, 15:38

I've got exactly the same problem as vertiger. I'm beginning to wonder if the driver is DVB-S only as driver name "firesat" implies...

bbackx · **Joined:** 12 Mar 2008, 09:26 **Posts:** 89

MindFlayer wrote:

I've got exactly the same problem as vertiger. I'm beginning to wonder if the driver is DVB-S only as driver name "firesat" implies...

It looks like that right now, but it's definitely not meant to be like that. The final driver will support all the devices, but I'm unable to test them (DVB-C not even available where I live).
From the errors you get, it seems a minor issue ("frequency limits undefined"). I'll see if I can find some time to look at it.

forester · **Joined:** 17 May 2008, 22:02 **Posts:** 3

Just got my hands on a FloppyDTV DVB-C and was eager to try things out.

Patched a linux vanilla 2.6.26-rc2 and things worked fine.

My DVB-C also got reported as a DVB-S device, seems the dvb_frontend_info wasn't propagated when calling firesat_frontend_attach.

Attaching a quick hack to make things work better.
But mind, I haven't yet been able to tune any transponder so this might just be a beginners-mistake-patch.

Hope you get some time to look into these stuff later after you finished your thesis.

http://www.connyandersson.se/tmp/dvb-fi ... -fix.patch

Regards
Conny Andersson

bbackx · **Joined:** 12 Mar 2008, 09:26 **Posts:** 89

I'm currently looking at device definition as part of my thesis. DVB-S2 devices are defined as DVB-S, but this has a totally different cause, one not so easy to fix

It is my intention to keep working/helping on the development of the driver after my thesis is done and June is already sort off holiday for the moment, so time should be no problem then

bbackx · **Joined:** 12 Mar 2008, 09:26 **Posts:** 89

Ok, thesis is done.

I've had a look at the code, and min- and max-frequency are defined. This means the following error is a strange one:

Code:

DVB: frontend 0 frequency limits undefined - fix the driver

I've completely changed the device recognition code, because it didn't support the DVB-S2 devices.
I'll first create a patch for this and see if it's any help.
DVB-S2 devices will probably work, but only in DVB-S mode (for DVB-S2 support, we have to change to multiproto, something other developers are looking at).

forester · **Joined:** 17 May 2008, 22:02 **Posts:** 3

Congratulations on getting your thesis done!

Since I own a DVB-C card I have been reading through your source code alot trying to understand why I cant get any streams from my card.

Using dvbsnoop I seem to get LOCK when tuning to a specific frequency. Do you have any specifications on these cards. Im thinking mostly about the vendor specific commands in avc_api.c?

Im also curious about the frequency. If I do an AVCTunerStatus(firesat, &info) the frequency reported must be multiplied with 16000 in order to be correct. Is this just a result from storing the frequency in 3 instead of 4 byte or is there some problems with AVCTuner_DSD and DVB-C cards?

I would be glad if I could help you to get your driver to work on DVB-C cards too.

Cheers
Conny Andersson

bbackx · **Joined:** 12 Mar 2008, 09:26 **Posts:** 89

Thanks

Beginning of July I'll know if everything went fine (doesn't look like there will be any problems, fortunately).

I'll ask the tech specs of the DVB-C and -T receivers. The Code you see in AVCTuner_DSD and so is mostly written by Andreas about 4 years ago, it was working fine for my DVB-S-receiver, so I didn't expect it to give problems with C or T either.
If they give me the specs, I'll check the code for changes (I signed an NDA, so I can't give you any technical specs though).

I also promised a patch, but I ran in some problems (trying to get DVB-S on the DVB-S2 devices to work). I'm working on it, but it'll be done when... it's done

Howto use the driver

Who is online