[linux-dvb] help with HD5000 (noobe) (sovled)

Todd nospam at tippyturtle.com
Wed Sep 28 06:33:16 CEST 2005


Thanks for the info!...and I found my problem.  It was a Noob thang.  I 
didn't run:
cd /etc/udev/devices
/bin/mkdir -p dvb/adapter0
cd dvb/adapter0
/bin/mknod audio0 c 212 1
/bin/mknod ca0 c 212 6
/bin/mknod demux0 c 212 4
/bin/mknod dvr0 c 212 5
/bin/mknod frontend0 c 212 3
/bin/mknod net0 c 212 7
/bin/mknod osd0 c 212 8
/bin/mknod video c 212 0
/bin/chmod 666 *

To Summarize:
I am running a new Technisat SkyStar2 DVB card (rev 02) which was sold to me 
as a " 5th-generation AirStar-HD5000-PCI (AirStarHD5kP)" from 
http://mythic.tv/

Vanilla 2.6.13.2 Kernel
Applied this patch to it:
http://www.digitalregime.com/patches/hd5000-cleanup.patch
ran makelinks from dvb-kernel
complied kernel and rebooted
ran MythTV-setup of v0.18
...everything ran Smooth like butter.

Thanks again everyone.
Todd

----- Original Message ----- 
From: "Ryan Olf" <ryan at efrus.com>
To: "Todd" <nospam at tippyturtle.com>
Sent: Tuesday, September 27, 2005 7:02 PM
Subject: Re: [linux-dvb] help with HD5000 (noobe)


> That message IS normal, by the way.  As long as the drivers detect the 
> correct
> frontend, as your dmesg shows, things are fine.  Those master_xfer failed
> messages happen because (it's my understanding...) the b2c2-flexcop probes
> the i2c bus to find out what frontend it's attached to, but it has to test
> the different possible frontends one at a time.  Everytime it guesses the
> wrong frontend, you get a message like that.
>
> Ryan
>
> On Tuesday 27 September 2005 04:33 pm, you wrote:
>> I left some steps out in my description.  That is what I did:
>> Kernel source linux-2.6.13.2
>> hd5000-cleanup.patch
>> ran the patch on the kernel source
>> then downloaded and installed the dvb-kernel follwing this:
>> http://linuxgazette.net/118/knaggs.html
>>
>> ...at any rate, is "b2c2-flexcop: i2c master_xfer failed" normal in my
>> dmesg?
>>
>> I will also try the other suggestion to update lgdt330x.c
>>
>> Thanks again,
>> ToddD
>>
>> ----- Original Message -----
>> From: "Mike Krufky" <mkrufky at linuxtv.org>
>> To: "Todd" <nospam at tippyturtle.com>
>> Cc: "linux-dvb" <linux-dvb at linuxtv.org>
>> Sent: Tuesday, September 27, 2005 2:50 PM
>> Subject: Re: [linux-dvb] help with HD5000 (noobe)
>>
>> > Todd wrote:
>> >> I am trying to sort out what is important to worry about and what is
>> >> not. I am running:
>> >> hd5000-cleanup.patch
>> >> Kernel source linux-2.6.13.2
>> >> Debian unstable
>> >>  In my dmesg I am seeing:
>> >> w83627hf 2-0290: Invalid sensor type 3; must be 1, 2, or 3435
>> >> b2c2-flexcop: B2C2 FlexcopII/II(b)/III digital TV receiver chip loaded
>> >> successfully
>> >> flexcop-pci: will use the HW PID filter.
>> >> flexcop-pci: card revision 2
>> >> ACPI: PCI Interrupt 0000:02:02.0[A] -> GSI 20 (level, low) -> IRQ 23
>> >> DVB: registering new adapter (FlexCop Digital TV device).
>> >> b2c2-flexcop: MAC address = 00:d0:d7:0e:6c:c0
>> >> b2c2-flexcop: i2c master_xfer failed
>> >> b2c2-flexcop: i2c master_xfer failed
>> >> b2c2-flexcop: i2c master_xfer failed
>> >> mt352_read_register: readreg error (reg=127, ret==-121)
>> >> b2c2-flexcop: i2c master_xfer failed
>> >> i2c_readbytes: i2c read error (addr 0a, err == -121)
>> >> b2c2-flexcop: found the lgdt3303 at i2c address: 0x59
>> >> DVB: registering frontend 0 (LG Electronics LGDT3303 VSB/QAM
>> >> Frontend)... b2c2-flexcop: initialization of 'Air2PC/AirStar 2 ATSC 
>> >> 3rd
>> >> generation (HD5000)' at the 'PCI' bus controlled by a 'FlexCopIIb'
>> >> complete *Are the "i2c master_xfer failed" messages a problem?  If so,
>> >> what might be causing this?  In mythTV setup when I setup the card as
>> >> DVB I get "Card Name:  Could not get card info"...and channel scanning
>> >> is a broken mess.  I am trying to figure out how far back in the error
>> >> messages to start trying to debug.*
>> >
>> > Todd-
>> >
>> > The HD5000 patch WILL NOT work against a vanilla 2.6.13.y kernel.  The
>> > reason for this is because Patrick's check-callback patch on lgdt330x
>> > hasnt been merged into the mainline kernel yet at that point.  It is,
>> > however, included in 2.6.14-rc1.
>> >
>> > Instead, I recommend that you should download dvb-kernel cvs, and apply
>> > the HD5000 patch against dvb-kernel cvs, then compile THAT against
>> > 2.6.13.y ... THAT should work for you.
>> >
>> > If you are unable to get that done, then you can try to apply the
>> > following patch against your tree... Here is the check-callback patch
>> > that I was talking about:
>> >
>> >
>> > ===================================================================
>> > RCS file:
>> > /cvs/linuxtv/dvb-kernel/linux/drivers/media/dvb/frontends/lgdt330x.c,v
>> > retrieving revision 1.8
>> > retrieving revision 1.9
>> > diff -u -r1.8 -r1.9
>> > --- dvb-kernel/linux/drivers/media/dvb/frontends/lgdt330x.c 2005/08/14
>> > 15:28:01 1.8
>> > +++ dvb-kernel/linux/drivers/media/dvb/frontends/lgdt330x.c 2005/08/14
>> > 15:31:24 1.9
>> > @@ -378,12 +378,14 @@
>> >  /* Select the requested mode */
>> >  i2c_write_demod_bytes(state, top_ctrl_cfg,
>> >        sizeof(top_ctrl_cfg));
>> > - state->config->set_ts_params(fe, 0);
>> > + if (state->config->set_ts_params)
>> > + state->config->set_ts_params(fe, 0);
>> >  state->current_modulation = param->u.vsb.modulation;
>> >  }
>> >
>> >  /* Tune to the specified frequency */
>> > - state->config->pll_set(fe, param);
>> > + if (state->config->pll_set)
>> > + state->config->pll_set(fe, param);
>> >
>> >  /* Keep track of the new frequency */
>> >  /* FIXME this is the wrong way to do this...           */
>> >
>> >
>> >
>> >
>> > Good Luck.
>> >
>> > --
>> > Michael Krufky
>>
>> _______________________________________________
>> linux-dvb mailing list
>> linux-dvb at linuxtv.org
>> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
> 




More information about the linux-dvb mailing list