[Sussex] (no subject)

[Steve Dobson]

Paul

On Wed, Sep 28, 2005 at 08:40:59AM +0100, Paul Graydon wrote:
> I think I'm going to go insane..

You are - you forgot to put a subject in your posting - very bad!

> I've been bashing my head against a
> brick wall trying to get a DVB Linux box going. After frustrations with
> RHEL4, which my boss preferred me to use so that we standardised on
> site, I managed to agree with him that I'd switch to Slackware, a distro
> I'm a lot more comfortable in, and can generally trust to do things in
> the proper way rather than the RedHat way. Redhat just seems to adopt
> its own approaches to standards, and I just spent ages trying to work my
> way around circular dependences.
> 
> Anyway, made some good progress with this box now I'm under Slackware.
> Custom compiled kernel is setup just to use the drivers for this system,
> including that for the pair of AVermedia DVB-T 771 cards I've got
> installed.
> 
> But I seem to be hitting a brick wall.  Mythtv, nor the linuxtv-dvb-apps
> seem able to see / talk to the dvb device.
> 
> By default, the system tries to create the devices in the root of /dev,
> in the style /dev/dvb0.frontend0. I came across that on my box I setup
> at home and after digging up a good guide on udev editing, corrected it
> to point at the /dev/dvb/adaptor0/frontend0 that the linuxtv-dvb-apps
> and mythtv seem to want. That works fine at home.  This box seems to be
> happy to use similar rules, and has created the devices where I asked,
> but still the system won't talk to it.
> 
> To try and be helpful the following is the output from dmesg:
> 
> Linux version 2.6.13 (root at dvb) (gcc version 3.3.6) #3 SMP Tue Sep 27

Is this an SMP kernel for a single processor machine?  Why?

It looks like you are running udev?  You have got the /dev device mountted?
I know it's a stupid question, but sometimes it is the little thinks that
are missed.

> bttv: driver version 0.9.16 loaded
> bttv: using 8 buffers with 2080k (520 pages) each for capture
> bttv: Bt8xx card found (0).
> ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 21 (level, low) -> IRQ 20
> bttv0: Bt878 (rev 17) at 0000:01:00.0, irq: 20, latency: 32, mmio:
> 0xdeafe000
> bttv0: detected: AVermedia AverTV DVB-T 771 [card=123], PCI subsystem ID is 1461:0771
> bttv0: using: AVerMedia AVerTV DVB-T 771 [card=123,autodetected]
> bttv0: gpio: en=00000000, out=00000000 in=00f8ff0f [init]
> bttv0: using tuner=4
> bttv0: registered device video0
> bttv0: registered device vbi0
> bttv0: PLL: 28636363 => 35468950 .. ok
> bttv0: add subdevice "remote0"
> bttv0: add subdevice "dvb0"
> bttv: Bt8xx card found (1).
> ACPI: PCI Interrupt 0000:01:01.0[A] -> GSI 22 (level, low) -> IRQ 21
> bttv1: Bt878 (rev 17) at 0000:01:01.0, irq: 21, latency: 32, mmio: 0xdeafc000
> bttv1: detected: AVermedia AverTV DVB-T 771 [card=123], PCI subsystem ID is 1461:0771
> bttv1: using: AVerMedia AVerTV DVB-T 771 [card=123,autodetected]
> bttv1: gpio: en=00000000, out=00000000 in=00f8ff0f [init]
> bttv1: using tuner=4
> bttv1: registered device video1
> bttv1: registered device vbi1
> bttv1: PLL: 28636363 => 35468950 .. ok
> bttv1: add subdevice "remote1"
> bttv1: add subdevice "dvb1"
> bt878: AUDIO driver version 0.0.0 loaded
> bt878: Bt878 AUDIO function found (0).
<snip>
> DVB: registering new adapter (bttv0).
> DVB: registering frontend 0 (Zarlink MT352 DVB-T)...
> DVB: registering new adapter (bttv1).
> DVB: registering frontend 1 (Zarlink MT352 DVB-T)...
 
> the output from lsmod looks like this:
> Module Size Used by
> dvb_bt8xx 11268 0
> tuner 37928 0
> bttv 157520 2 dvb_bt8xx,bt878
> video_buf 18820 1 bttv
> btcx_risc 5000 1 bttv
> tveeprom 11536 1 bttv
> evdev 8320 0

> 
> 
> Also.. udevinfo -a -q path -n /dev/dvb/adaptor0/frontend0 tells me
> "/class/dvb/dvb0.frontend0"
> and a subsequent udevinfo -a -p /sys/class/dvb/dvb0.frontend0 tells me
> device '/sys/class/dvb/dvb0.frontend0' has major:minor 212:3
> looking at class device '/sys/class/dvb/dvb0.frontend0':
> SUBSYSTEM=="dvb"
> SYSFS{dev}=="212:3"
> 
> so it seems to me that /dev/dvb/adaptor0/frontend0 is pointing to the
> right device on the system.  When I run mythtv it tells me it can't see
> any dvb cards, and when I run the scan utility from linuxtv-dvb-apps I
> get the following error message:
> 
> root at dvb:~/dvb/linuxtv-dvb-apps-1.1.0/util/scan# ./scan
> dvb-t/uk-PontopPike
> scanning dvb-t/uk-PontopPike
> using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
> main:1882: FATAL: failed to open '/dev/dvb/adapter0/frontend0': 2 No
> such file or directory

Have you tried Knoppmyth?  http://www.mysettopbox.tv/knoppmyth.html
Assuming that your hardware is supported by it then it would be a 
good way to find out what modules are loaded.

Steve


-- 
[It is] best to confuse only one issue at a time.
		-- K&R
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://mailman.lug.org.uk/pipermail/sussex/attachments/20050928/004355a4/attachment.pgp