[mythtv-users] Which device is which

[Brian Wood]

On Feb 15, 2006, at 6:31 PM, Michael Haan wrote:

> On 2/15/06, Brian Wood <beww at beww.org> wrote:
>
> On Feb 15, 2006, at 6:04 PM, Michael Haan wrote:
>
>> On 2/15/06, Brian Wood < beww at beww.org> wrote:
>>
>> On Feb 15, 2006, at 5:47 PM, Michael Haan wrote:
>>
>>> On 2/15/06, Nick Rout < nick at rout.co.nz> wrote:
>>>
>>> On Tue, 14 Feb 2006 22:38:12 -0700
>>> James Dastrup wrote:
>>>
>>> > On Tue, 2006-02-14 at 21:32 -0500, Michael Haan wrote:
>>> > > On 2/14/06, Nick Rout < nick at rout.co.nz > wrote:
>>> > >
>>> > >         On Tue, 14 Feb 2006 21:09:27 -0500
>>> > >         Michael Haan wrote:
>>> > >
>>> > >         > I've got a pvr-350, and HD3000 and a DVICO Fusion5  
>>> Lite, but
>>> > >         I'm having a hard time telling which device is being  
>>> loaded
>>> > >         where, specifically the HD3000 and the pvr-350.   
>>> Attached is
>>> > >         my dmesg output - can anyone help?
>>> > >
>>> > >
>>> > >         I don't know what a dvico fusion is, but the drivers  
>>> i can see
>>> > >         seem to load in the order:
>>> > >
>>> > >         bttv
>>> > >         ivtv - thats the pvr 350
>>> > >         hd3000 (whatever driver that actually is0
>>> > >
>>> > >         so the devices should appear at /dev/video0, /dev/ 
>>> video1 etc,
>>> > >         or they might be /dev/video/0 /dev/video/1 etc
>>> > >
>>> > >
>>> > >
>>> > >         --
>>> > >         Nick Rout <nick at rout.co.nz >
>>> > >
>>> > >
>>> > > Ok, and the dvb devices on the Fusion and the HD3000?  There  
>>> seems to
>>> > > be only /dev/dvb0/adapter0/frontend0...
>>> > > _______________________________________________
>>> >
>>> > Not sure where you got the "hd3000" module from. I would  
>>> suggest using
>>> > the built-in kernel driver for the pcHDTV-3000. You need at  
>>> least kernel
>>> > ver 2.6.12 and the module you load is called "cx88-dvb".  It  
>>> will show
>>> > up as /dev/dvb/adapter0, and any other cards that use the same  
>>> driver
>>> > will show up as /dev/dvb/adapter1, /dev/dvb/adapter2, etc.
>>> >
>>>
>>> OK I have just demonstrated my profound ignorance of these  
>>> particular devices. Please move on, nothing to see here :-)
>>>
>>>
>>> --
>>>
>>> Here is the output of my lsmod, sorted:
>>>
>>>
>>> cx22702                40389  1 cx88_dvb
>>> cx8800                 71373  0
>>> cx8802                 47173  1 cx88_dvb
>>> cx88_dvb               46429  0
>>> cx88xx                103265  3 cx8800,cx88_dvb,cx8802
>>
>> I notice you have both the cx8800 and cx88_dvb loaded. I read  
>> something that said you were supposed to unload cx8800 before  
>> loading cx88_dvb, and I thought that might have something to do  
>> with my problems with QAM
>>
>> Do you have an hd3000 card working in digital mode with this  
>> module config?
>>
>> _______________________________________________
>> mythtv-users mailing list
>> mythtv-users at mythtv.org
>> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>>
>>
>>
>>
>> Nope, not yet (well, it did before).  I can unload it manually,  
>> but I'm not sure how to make that permanent - I tried make  
>> menuconfig, but it bombed.  Also, not sure why it's being loaded  
>> (cx8800).  Thanks for chiming in, though - helps to get to the  
>> bottom of this.
>
> Do you have your /usr/src/linux symlink pointing to the correct  
> source directory, and did you run "makemenuconfig" from that  
> directory  ??
>
> You could rmmod the module with a line in rc.local (if your distro  
> runs that way). I'm not really sure that it is causing me problems  
> though, azap gives me proper results and I can play the stream with  
> mplayer, I just get "too many packet" errors and azap loses lock at  
> times while playing, but never otherwise.
>
> It looks to me as if I have both an analog and a digital source for  
> the hd3000 card (/dev/ideox and /dev/dvb/adapterx), which everyone  
> seems to say you can't do.
>
> But too many other things to work out, getting the hd card working  
> is a low priority right now, as I have 3 other cap cards working OK.
>
> But on the original subject here, a very careful reading of your  
> bootup messages should reveal which card is which.
>
> No, I tried to cd to /usr/src/linux and it doesn't exist.  Then I  
> tried yum install linux-src and got an error.  I know its probably  
> kernel-src or something like that, but the point is yum is broken,  
> and I can't seem to see what kernel mods I'm loading.  FWIW, my  
> kernel comes from ATRPMS.

Sounds like there is a problem with yum, which I'm sure will be  
resolved soon.

/usr/src/linux should be a symlink that points to something like /usr/ 
src/[linux-your-kernel-version], this allows you to select the kernel  
source tree that you want to use, and allows programs that need  
access to the source tree to get there without having to know the  
specific version that you are using.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mythtv.org/pipermail/mythtv-users/attachments/20060215/f81c2ee6/attachment.htm