[mythtv-users] getting going

Alexander Ellis saveourtivo at yahoo.com
Mon Feb 28 18:28:36 UTC 2011









________________________________

Message: 23
Date: Mon, 28 Feb 2011 00:25:58 +0000
From: Nick Morrott <knowledgejunkie at gmail.com>
Subject: Re: [mythtv-users] Getting going
To: Discussion about MythTV <mythtv-users at mythtv.org>
Message-ID:
    <AANLkTimipYiDsCdot1PmvBWd5KoCM6-b5txH7FvkwfTj at mail.gmail.com>
Content-Type: text/plain; charset=UTF-8

On 27 February 2011 21:57, Alexander Ellis <saveourtivo at yahoo.com> wrote:
> I have installed mythbuntu using a Hauppaugge nova-s-plus card.
> I can watch TV using
> mkdir ~/.mplayer
> cp channels.conf ~/.mplayer
> mplayer dvb://"BBC THREE"
> But I can't get myth to find channels

Alek,

Can you provide us with more details on how you've tried to configure
MythTV with your DVB-S card? Are you trying to scan for channels
within MythTV, or are you importing your channels.conf file?

If scanning within MythTV, you need to ensure that you have configured
the LNB (part of capture card setup) before you can successfully scan
for DVB-S channels.

Cheers,
Nick

-- 
Nick Morrott

I have run through set up from the start using defaults mostly as I don't know 
what a lot of the settings are.

I have tried setting the card as. IVTV MPEG-2 encoder and DVB DTV capture card 
(v3.x), but neither works.

I looked at the log and it says No capture cards are defined please run the 
setup program.

So maybe I need drivers or something to make myth see the card

I was trying to scan for channels which it does but doesn't find any

Alek


      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
http://www.mythtv.org/pipermail/mythtv-users/attachments/20110228/6500515b/attachment-0001.html
 

------------------------------

Message: 15
Date: Mon, 28 Feb 2011 08:58:55 +0000
From: David Watkins <watkinshome at gmail.com>
Subject: Re: [mythtv-users] getting going
To: Discussion about MythTV <mythtv-users at mythtv.org>
Message-ID:
    <AANLkTikT-w5mGQpJkSxR1KCfbLq_g92M10YggwrdpM9Y at mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1

> I have run through set up from the start using defaults mostly as I don't
> know what a lot of the settings are.
> I have tried setting the card as. IVTV MPEG-2 encoder and DVB DTV capture
> card (v3.x), but neither works.
> I looked at the log and it says No capture cards are defined please run the
> setup program.
> So maybe I need drivers or something to make myth see the card
> I was trying to scan for channels which it does but doesn't find any
> Alek

The linux equivalent of hardware drivers are kernel modules, which are
generally loaded automatically by the kernel, but may need to be
loaded by hand (or in a script) if the kernel doesn't detect the
hardware correctly.

You can tell if the kernel module has been loaded by looking in:

/var/log/messages

for entries referring to loading of dvb modules

or seeing whether the directories

/dev/dvb/adapter0/...

have been created.

If everything looks OK it's possible that you have a permissions
problem.  What access rights does the /dev/dvb/... have, and what user
are you running mytht-setup as?  Also, I believe you should make sure
that mythbackend is not running when you run mythtv-setup.




Here is /var/log/messages

Feb 28 16:00:51 al-Uk kernel: [   91.824098] Pid: 0, comm: swapper Tainted: 
P            2.6.35-25-generic #44-Ubuntu
Feb 28 16:00:51 al-Uk kernel: [   91.824102] Call Trace:
Feb 28 16:00:51 al-Uk kernel: [   91.824115]  [<c014ad42>] 
warn_slowpath_common+0x72/0xa0
Feb 28 16:00:51 al-Uk kernel: [   91.824120]  [<c050f67d>] ? 
dev_watchdog+0x1fd/0x210
Feb 28 16:00:51 al-Uk kernel: [   91.824124]  [<c050f67d>] ? 
dev_watchdog+0x1fd/0x210
Feb 28 16:00:51 al-Uk kernel: [   91.824129]  [<c014ae13>]  
warn_slowpath_fmt+0x33/0x40
Feb 28 16:00:51 al-Uk kernel: [   91.824133]  [<c050f67d>] 
dev_watchdog+0x1fd/0x210
Feb 28 16:00:51 al-Uk kernel: [   91.824142]  [<c0161e46>] ? 
insert_work+0x66/0xb0
Feb 28 16:00:51 al-Uk kernel: [   91.824150]  [<c012cf18>] ? 
default_spin_lock_flags+0x8/0x10
Feb 28 16:00:51 al-Uk kernel: [   91.824154]  [<c0162106>] ? 
__queue_work+0x36/0x50
Feb 28 16:00:51 al-Uk kernel: [   91.824159]  [<c050f480>] ? 
dev_watchdog+0x0/0x210
Feb 28 16:00:51 al-Uk kernel: [   91.824163]  [<c0157f0f>] 
call_timer_fn+0x2f/0xf0
Feb 28 16:00:51 al-Uk kernel: [   91.824167]  [<c01223eb>] ? 
lapic_next_event+0x1b/0x20
Feb 28 16:00:51 al-Uk kernel: [   91.824176]  [<c017452b>] ? 
clockevents_program_event+0x8b/0x140
Feb 28 16:00:51 al-Uk kernel: [    91.824180]  [<c0159154>] 
run_timer_softirq+0x104/0x210
Feb 28 16:00:51 al-Uk kernel: [   91.824185]  [<c0175932>] ? 
tick_dev_program_event+0x42/0x150
Feb 28 16:00:51 al-Uk kernel: [   91.824189]  [<c050f480>] ? 
dev_watchdog+0x0/0x210
Feb 28 16:00:51 al-Uk kernel: [   91.824196]  [<c015136c>] 
__do_softirq+0x9c/0x1b0
Feb 28 16:00:51 al-Uk kernel: [   91.824200]  [<c016c35e>] ? 
sched_clock_tick+0x5e/0x90
Feb 28 16:00:51 al-Uk kernel: [   91.824204]  [<c01514c5>] do_softirq+0x45/0x50
Feb 28 16:00:51 al-Uk kernel: [   91.824208]  [<c0151635>] irq_exit+0x65/0x70
Feb 28 16:00:51 al-Uk kernel: [   91.824213]  [<c05d0c5b>] 
smp_apic_timer_interrupt+0x5b/0x8a
Feb 28 16:00:51 al-Uk kernel: [   91.824219]  [<c05caa65>] 
apic_timer_interrupt+0x31/0x38
Feb 28  16:00:51 al-Uk kernel: [   91.824223]  [<c012c31a>] ? 
native_safe_halt+0xa/0x10
Feb 28 16:00:51 al-Uk kernel: [   91.824232]  [<c010a3b9>] 
default_idle+0x49/0xb0
Feb 28 16:00:51 al-Uk kernel: [   91.824236]  [<c0101fcc>] cpu_idle+0x8c/0xd0
Feb 28 16:00:51 al-Uk kernel: [   91.824242]  [<c05b3951>] rest_init+0x71/0x80
Feb 28 16:00:51 al-Uk kernel: [   91.824249]  [<c081981a>] 
start_kernel+0x36e/0x374
Feb 28 16:00:51 al-Uk kernel: [   91.824253]  [<c08199dd>] ? 
pass_all_bootoptions+0x0/0xa
Feb 28 16:00:51 al-Uk kernel: [   91.824257]  [<c08190d7>] 
i386_start_kernel+0xd7/0xdf
Feb 28 16:00:51 al-Uk kernel: [   91.824261] ---[ end trace ce0ed5923c1b2792 
]---
Feb 28 16:00:51 al-Uk kernel: [   91.824266] eth0: Transmit timeout, status 
00000004 00000000
Feb 28 16:00:51  al-Uk kernel: [   92.576871] eth0: Media Link On 100mbps 
full-duplex
Feb 28 16:00:57 al-Uk kernel: [   98.592310] eth0: Media Link Off
Feb 28 16:01:07 al-Uk kernel: [  107.824022] eth0: Transmit timeout, status 
00000004 00000000
Feb 28 16:01:07 al-Uk kernel: [  108.608911] eth0: Media Link On 100mbps 
full-duplex
al at al-Uk:~$ 

I was mistaken before looking for adapter O it is adapter zero.

Adapter 0 exists and contains...demux0  dvr0  frontend0  net0


I don't understand about access rights or running as a different user.

Setup does ask me to stop the back end before set up.


Alek


      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.mythtv.org/pipermail/mythtv-users/attachments/20110228/0a98ce57/attachment-0001.html 


More information about the mythtv-users mailing list