Re: problems setting up dvbd

[Danijel Pajur <dpajur@irb.hr>]

> > I get a dvb0 interface using ip 192.168.4.1. That is the first strange
> > thing,
>
> Nope, thats fine.

Ok, I switched it back to 192.168.4.1.

my interfaces now look like this:
dvb0      Link encap:Ethernet  HWaddr 00:02:A1:35:80:ED
          inet addr:192.168.4.1  Bcast:192.168.4.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100

eth0      Link encap:Ethernet  HWaddr 00:D0:B7:BD:42:1C
          inet addr:161.53.128.237  Bcast:161.53.128.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:29423 errors:0 dropped:0 overruns:0 frame:0
          TX packets:20070 errors:0 dropped:0 overruns:0 carrier:0
          collisions:219 txqueuelen:100
          Interrupt:11

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16192  Metric:1
          RX packets:12 errors:0 dropped:0 overruns:0 frame:0
          TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0

> > Since the modules report no errors I can only assume that the problem
lies
> > in dvbd and it's configuration.
>
> Did you echo 0 > /proc/sys/net/ipv4/conf/dvb0/rp_filter ?

yup.

and heres what the modules report upon insertion (could be something wrong
there?)
Oct  6 23:40:50 dptest kernel: i2c-core.o: i2c core module
Oct  6 23:41:12 dptest kernel: saa7146_init_one()
Oct  6 23:41:12 dptest kernel: i2c-core.o: adapter saa7146(1) registered as
adap
ter 0.

Oct  6 23:42:23 dptest kernel: Linux video capture interface: v1.00
Oct  6 23:42:32 dptest kernel: i2c-core.o: driver dvbi2c registered.
Oct  6 23:42:34 dptest kernel: outcommand error 1
Oct  6 23:42:34 dptest kernel: commandrequest error
Oct  6 23:42:34 dptest kernel: dvb: firmware = 9ef8ce3e
Oct  6 23:42:34 dptest kernel: dvb: MAC = 00 d0 5c 00 3b 65
Oct  6 23:42:34 dptest kernel: dvb: attach_adapter
Oct  6 23:49:29 dptest kernel: outcommand error 1
Oct  6 23:49:30 dptest kernel: outcommand error 1
Oct  6 23:49:30 dptest kernel: commandrequest error
Oct  6 23:57:16 dptest kernel: outcommand error 1
Oct  6 23:57:21 dptest last message repeated 5 times

these outcommand and commandrequest errors could mean something's wrong but
I can't tell.
also, the MAC address differs on what dvb0 reports and what the kernel
reports (i've supplied both here).. is there a problem there? and how to
force the dvb module to use the correct MAC address for dvb0?

> > One thing I noticed is that they all report sync=127 (best) which is a
bit
> > strange..
>
> Why? What sync do you have? Why is your error report so unspecific? How
> do you think we should be able to help you without appropiate error
> description? 'Does not work' is not helpful.

ok I'll try to be more informative..

under windows the signal level was about 50% on all transponders except for
103 where it was 100%. so i expected sync (if that is a measurement of
signal quality) to be in the 60's for other transponders and 127 for
transponder 103. turns out it's 127 for all of them, that made me think
there might be something wrong.

here is my latest dvbd.conf: (should be on transponder 103)
power 1
symbolrate 27500000
frequency 12461000
ttk 1
diseqc 0
AFC 0
polarisation 1
filter_0 512

actually now that i've recompiled everything and used 0.7 modules instead of
0.7.1 I'm getting a sync of 1-7, heres an example:
Fsync = 0, Freq = 2040000000, Sync = 1 Afc = 6015625 Agc = 223 Nest = 36096
Vber
Fsync = 0, Freq = 2040000000, Sync = 1 Afc = 6015625 Agc = 223 Nest = 36608
Vber
Fsync = 0, Freq = 2040000000, Sync = 1 Afc = 5843750 Agc = 239 Nest = 36608
Vber
Fsync = 0, Freq = 2040000000, Sync = 1 Afc = 5843750 Agc = 191 Nest = 36608
Vber
Fsync = 0, Freq = 2040000000, Sync = 1 Afc = 5843750 Agc = 207 Nest = 36352
Vber
Fsync = 0, Freq = 2040000000, Sync = 1 Afc = 5671875 Agc = 255 Nest = 36352
Vber
Fsync = 0, Freq = 2040000000, Sync = 1 Afc = 5671875 Agc = 223 Nest = 36096
Vber
Fsync = 0, Freq = 2040000000, Sync = 1 Afc = 5500000 Agc = 255 Nest = 35584
Vber
Fsync = 0, Freq = 2040000000, Sync = 1 Afc = 5500000 Agc = 271 Nest = 35328
Vber
Fsync = 0, Freq = 2040000000, Sync = 1 Afc = 5500000 Agc = 255 Nest = 35584
Vber
Fsync = 0, Freq = 2040000000, Sync = 1 Afc = 5328125 Agc = 239 Nest = 35328
Vber
 = 1048575

that doesnt make much sense.. it's half past 10pm, i don't expect there
could be any interference at this time and the weather's clear. last time i
tried at about 5-6pm i got sync 127 with all transponders..

but i'm most worried about the kernel errors reported after inserting
modules. (outcommand and commandrequest)

> > dvbd.conf seems like the most likely suspect, it's undocumented
>
> Having a config file with comments on each option isn't exactly the same
> as undocumented.

well I guess i'm one of those people who like to know what the directives do
and what the complete syntax is.
just getting it to work would be enough for me for now :) actually found a
commented dvbd.conf file in one of the other packages (dvbrouter i think).

> > Do i need filter_2 or just filter_0 ?
>
> 0 is just fine, thats the reason why all other filters are commented out
> in the example config. Start thinking!

ok i'm back to just filter_0.. didn't seem to help but there's any other
info i can supply please let me know.