Jim Jowski wrote: > I've been a slakware user for almost 9 years and been running the 2.6.10 > kernel for a week or so. Now the fun starts. I can 'modprobe bttv > i2c_hw=1 card=0x71' and 'modprobe dvb-bt8xx' and lsmod gives the following: > > Module Size Used by > dvb_bt8xx 8068 0 > dvb_core 71464 1 dvb_bt8xx > nxt6000 6404 1 dvb_bt8xx > mt352 5124 1 dvb_bt8xx > dst 12040 1 dvb_bt8xx > bt878 8504 2 dvb_bt8xx,dst > sp887x 7044 1 dvb_bt8xx > tuner 20260 0 > bttv 141648 2 dvb_bt8xx,bt878 > video_buf 16900 1 bttv > firmware_class 7296 3 dvb_bt8xx,sp887x,bttv > i2c_algo_bit 8840 1 bttv > v4l2_common 4864 1 bttv > btcx_risc 3976 1 bttv > i2c_core 17680 8 dvb_bt8xx,nxt6000,mt352,dst,sp887x,tuner,bttv,i2c_algo_bit > videodev 7296 1 bttv > > When I try to lock onto a known good signal with szap I get this: > './szap -l 5150 -i' > reading channels from file '/root/.szap/channels.conf' > > >>> ank > zapping to 1 'ank': > sat 0, frequency = 3880 MHz H, symbolrate 25187000, vpid = 0x0110, apid > = 0x0111using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' > opening frontend failed: No such device or address Have you created the /dev/dvb entries.. ? If you are using udev, you need to create a udev script... Somebody could possibly help you out on that, as i don't use udev.. > > I looked in the /sys directory and there looks like a recursive linking > of drivers to a higher level directory on the bttv branch. That doesn't > seem right. :^) I'm at a loss for why the thing won't lock on. Does > anyone have a good how-to that I can look at? I've looked at the docs in > the /usr/src directory and udev throws me. I'm also betting that this is > easier than I'm trying to make is so if I can get the process down to a > "Follow this checklist, step by step", I'll post it. > If you are happy with the stock drivers, use them else recompile the kernel with the latest drivers.. The reason being the driver got through many changes compared to the stock drivers in 2.6.10.. For documentation take a look at linuxtv.org, the top level documentation link points directly to the docs in CVS. Manu
