Manu,Hi Jamie & Manu,
please keep going. I realize it is frustrating to be amongst the first to use all this, what with cvs, compiling etc. etc.
It will be some time before other users can take the benefits of early bug reports and frustrating build processes such as you've been through, but there is no other way to do this.
The ultimate goal is have distributions automatically configure and install applications so that everyone can benefit.
Nov 3 12:51:08 Orbit01 kernel: dst_check_ci: unable to recognize DST-MOT or ST-MOT
OK. The driver was looking for M-zero-T not M-OH-T.
I've placed the correction in cvs.
You are also able to override default values with module options for the DST now.
I think, from what you say, you may need to override the flags as either dst_type_flags=0 or dst_type_flags=4
If this works, can you let me know and I'll fix the version for others.
Jamie
--------------------------------------------------------------------
The README.bt8xx has these described towards the end. Repeated here:
The DST module takes a couple of useful parameters, in case the dst drivers fails to detect your type of card correctly.
dst_type takes values 0 (satellite), 1 (terrestial TV), 2 (cable).
dst_type_flags takes bit combined values: 1 = new tuner type packets. You can use this if your card is detected and you have debug and you continually see the tuner packets not working (make sure not a basic problem like dish alignment etc.)
2 = TS 204. If your card tunes OK, but the picture is terrible,
seemingly breaking up in one half continually, and crc fails a lot, then this is worth a try (or trying to turn off)
4 = has symdiv. Some cards, mostly without new tuner packets, require a symbol division algorithm. Doesn't apply to terrestial TV.
You can also specify a value to have the autodetected values turned off (e.g. 0). The autodected values are determined bythe cards 'response string' which you can see in your logs e.g.
dst_check_ci: recognize DST-MOT
or
dst_check_ci: unable to recognize DSTXCI or STXCI
Last night I tried to get the DST working as well. I've got a VP-1020 DVB-S card. This is my first time playing with kernel modules, so please check my sanity/order-of-operations:
1. Downloaded and configured linux-2.6.0-test9 kernel
2. Did a CVS checkout of dvb-kernel
3. Ran the "makelinks.sh" script and pointed it at my kernel
4. Ran "make xconfig" and selected pretty much everything in the video4linux / DVB section (specifically enabled DST).
5. Compiled the kernel with "make bzImage ; make modules ; make modules_install"
6. Configured grub with a menu option to select the new kernel
7. Booted into the new kernel.
How does that sound? Am I missing any steps?
Where I'm at right now is if I try "modprobe bttv", it'll hang my system.
If I follow the instructions in the dvb-kernel's README.bt8xx, I see that I'm supposed to make a little "insmod" script. So, I copied build-2.4/insmod-bt8xx.sh to insmod-dst.sh, and edited it to select the DST drivers, but when I try to run it with ./insmod-dst.sh start, I get:
Inserting DVB modules into kernelinsmod: can't read 'videodev.o': No such file or directory
insmod: can't read 'bttv.o': No such file or directory
insmod: can't read 'dvb-core.o': No such file or directory
insmod: can't read 'v4l1-compat.o': No such file or directory
insmod: can't read 'v4l2-common.o': No such file or directory
insmod: can't read 'video-buf.o': No such file or directory
insmod: can't read 'dst.o': No such file or directory
insmod: can't read 'bt878.o': No such file or directory
insmod: can't read 'dvb-bt8xx.o': No such file or directory
Do I need to be in the /usr/src/linux-2.6.0-test9/... directory tree to run this script? Am I missing something?
Thanks, Grant
-- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
