[linux-dvb] Re: dvbd

[Holger Waechtler <holger@convergence.de>]

Hi,

I don't know exactly what you are using there, but this is definitely 
not the current driver from CVS. Please get a recent driver by tapping

$ cvs -d :pserver:anonymous@linuxtv.org:/cvs/linuxtv login
[press enter]
$ cvs -d :pserver:anonymous@linuxtv.org:/cvs/linuxtv co DVB
$ cd DVB
$ make

then

$ rm modules/2.4.19/kernel/drivers/media/video/dmxdev.o

and remove all other old driver files

then try as root:

$ cd driver
$ ./makedev.napi

to create the device nodes. To load the driver:

$ make insmod

Then try to tune using szap and test if you can get a lock. I don't know 
if dvbd is maintained anymore, report problems related to dvbd to the 
author.

Holger



maroi wrote:
> maybe it will help you if I paste my dmesg messages of modprobe dvb
> i2c-core.o: i2c core module
> i2c-core.o: i2c core module
> PCI: Found IRQ 12 for device 00:0a.0
> saa7146_core: saa7146 #0 @ pci 00:0a.0; rev=1; mem=0xe6002000; irq=12;
> subsys=0x13c2,0x0000.
> saa7146_core: saa7146 #0: using 2 capture buffers of 1728 KBytes each (3456
> KBytes total)
> saa7146_core: saa7146 #0: latency=32 clks; threshold=32 dwrds; burst=128
> dwrds.
> saa7146_core: 1 SAA7146 chipset(s) found.
> saa7146_core: extension 0 registered: "v4l extension"
> Linux video capture interface: v1.00
> dvb.o Technotrend/Siemens DVB driver version 0.8.2 patch 9f
> dvb0: ambiguous subsystem id (0x13c2,0x0000) on saa7146 #0.
> dvb0: probing for I2C client VES1893 @ 0x08... found.
> dvb0: DVB-S Rev. 1.3 auto-detected on saa7146 #0.
> sp5659.o i2c driver
> sp5659: MITEL SP5659 #0 detected at i2c address 0x61.
> sp5659: MITEL SP5659 #0 @ 0x61 attached to adapter saa7146 #0.
> ves1893.o i2c driver
> ves1893: VLSI VES1893 #0 detected at i2c address 0x08.
> ves1893: VLSI VES1893 #0 @ 0x08 attached to adapter saa7146 #0.
> ee24lc16.o i2c driver
> ee24lc16: Serial EEPROM #0 detected at i2c address 0x50.
> ee24lc16: Serial EEPROM #0 @ 0x50 attached to adapter saa7146 #0.
> dvb0: V4L video device registered on (81, 0).
> dvb0: V4L vbi device registered on (81, 224).
> dvb0: ARM firmware successfully loaded.
> dvb0: firmware = f0240009
> dvb0: MAC = 00 XX XX 00 XX XX
> saa7146_core: extension 1 registered: "dvb extension"
> dvb: 1 dvb(s) found!
> 
>>maroi wrote:
>>
>>>ok now I tried patch-8
>>>on modprobe dvb I see
>>>Warning: loading /lib/modules/2.4.19/kernel/drivers/media/video/dmxdev.o
>>>will taint the kernel: no license
>>
>>This is a normal message when the kernel does not detect the license
>>information from the modules. Apparently Rolf forgot to add the license
>>information defines in all modules. Not ot worry, this has no effect on
>>the working of the modules.
>>
>>
>>>2.4.19
>>
>>I am guessing here, but have you tried a 2.4.18 kernel and dvb ?
>>I know 2.4.5 had many wierd problems, and I already heard some roumors
>>about 2.4.19.
>>I'd give it a try with the stock 2.4.18 from the slack8.1 kit.
>>
>>
>>
>>>Module dvb loaded, with warnings
>>
>>module dvb should load without warning about license as it correctly
>>defines the license informaiton. Check the source.
>>
>>
>>>everything is the same but in syslog I see now more:
>>>dvbd[2662]: ioctl VIDIOCGCAP (dvbd.c, 1335): Unknown error 515 -
>>
> aborting
> 
>>Check the source, this is generated at:
>>        /* check if DVB card/driver is present at opened V4L device */
>>There is a serious problem with detecting your card here.
>>I'd start turning on debugging on the modules and dvbd.
>>
>>
>>>videodev in module with major (from the install of patch-8)
>>>alias char-major-81         videodev
>>
>>videodev from kernel (only videodev configured in the kernel at video
>>for linux) loaded correctly I assume.
>>
>>Check the changelogs between 2.4.18 and 2.4.19 that may concern i2c,
>>videodev.
>>
>>Something seems to be seriously wrong between your kernel, drivers and
>>card.
>>Have you tried to set debugging in turn with each module and load them
>>manually? especially dvb.o? and keep high debuging on dvb.o while trying
>>to load dvbd?
>>
>>Have you tried to compile and use the gVideo app to see if you can
>>receive mpeg video from the satellite? If that doesn't work with various
>>warnings, errors, there is a problem somewhere.
>>Eutelsat W3 should have at least some polish stations with high SR that
>>are visible with small dishes. If not, try Hotbird.
>>
>>What pcb revision is your card? (see card for Rev 1.5 or Rev 2.1 or
>>similar).
>>Could you please run dumpee and post the result so I can compare it with
>>mine? (I also have a Skystar 1 rev 1.5)
>>
>>--
>>ing. Andrei Boros
>>mailto:andrei@srr.ro / +40-1-303-1870
>>Centrul pt. Tehnologia Informatiei
>>Societatea Romana de Radiodifuziune
>>
> 
> 
> 
> 
> 



-- 
Info:
To unsubscribe send a mail to listar@linuxtv.org with "unsubscribe linux-dvb" as subject.