Re: [mythtv-users] Hauppauge Nova-T PCI and LIRC

2005-12-06 Thread Druid 
On Tue, 2005-12-06 at 11:07 +, Graeme Hilton wrote: 
> On Tue, 6 December, 2005 10:59 am, Adrian Kladnig wrote:
> > Graeme Hilton wrote:
> >>
> >>Yay!  It's working!  I recompiled lirc with the --driver=devinput option
> >>and started lircd with the command line 'lircd --driver=dev/input
> >>--device=/dev/input/event0' then 'irxevent &'.
> >>
> >>I've remapped a few of the buttons in /home/mythtv/.lircrc so they make
> >>more sense to me and my GF.
> >>
> > I struggled for about a month with this. Eventually, I ended up
> > modifying budget-ci.c to make the remote work. I found that the Nova-t
> > doesn't use LIRC at all, the only problem being that I have to recompile
> > everytime I install a new kernel.

Like I said, took me a while to figure out. ;-)

FWIW the lirc 'hauppauge' i2c device works on my old
2.6.11-rc2-bk3-20050125153357-default kernel'd suse 9.1
so must be the latest dvb code in the kernel (which given that all I did
was install SuSE 10, didn't even bother to configure the cards and
everything worked is rather nice :-) esp in comparison to the grief with
suse 9.1 )

My bigest mistake was not trying the remote until after I'd installed
lirc and assuming it'd work the same as my previous system.

> > Your method seems so much easier, so I'll have to give it a go!
> 
> Quite simple now I know what steps to follow!  I'm still using the latest
> FC4 x86_64 kernel (2.6.13) with no modifications so no need to keep
> recompiling every few weeks/months. 

2.6.13-15-smp in my case although unless there is a real reason to, I
doubt I'll change that.

I also run lirc via the suse init script and (irexec
via .kde/Autostart), I can post a copy of the init script if you want
but I assume something similar is included in all the distro's (s)rpm's

HTH

Druid



___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

Re: [mythtv-users] Hauppauge Nova-T PCI and LIRC

2005-12-06 Thread Graeme Hilton 

On Tue, 6 December, 2005 10:59 am, Adrian Kladnig wrote:
> Graeme Hilton wrote:
>>
>>Yay!  It's working!  I recompiled lirc with the --driver=devinput option
>>and started lircd with the command line 'lircd --driver=dev/input
>>--device=/dev/input/event0' then 'irxevent &'.
>>
>>I've remapped a few of the buttons in /home/mythtv/.lircrc so they make
>>more sense to me and my GF.
>>
> I struggled for about a month with this. Eventually, I ended up
> modifying budget-ci.c to make the remote work. I found that the Nova-t
> doesn't use LIRC at all, the only problem being that I have to recompile
> everytime I install a new kernel.
>
> Your method seems so much easier, so I'll have to give it a go!

Quite simple now I know what steps to follow!  I'm still using the latest
FC4 x86_64 kernel (2.6.13) with no modifications so no need to keep
recompiling every few weeks/months.

-- 
Graeme Hilton
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

Re: [mythtv-users] Hauppauge Nova-T PCI and LIRC

2005-12-06 Thread Adrian Kladnig 

Graeme Hilton wrote:


[EMAIL PROTECTED] wrote:
 


On Sunday 04 December 2005 21:58, Graeme Hilton wrote:
I've been happily using Myth (SVN checkouts every month or so) for about
   


4 months.  My setup at the moment is as follows:

Hauppauge Nova-T DVB-T PCI (two of them)
AMD x86_64 system
Fedora Core 4 - all up to date
MythTV SVN revision 8053

Has anyone had this happen to them?  Have you managed to solve the
problem and get your Hauppauge remote fully working?
 

Yep, had me confused for a short while. The IR is recognised automatically, 
you'll find if you *don't* use lirc it'll still work (well the up/down/ok 
etc) with mythfrontend.


What you need to do is use it with the dev/input driver[1], setup lirc to use 
driver dev/input and device /dev/input/event where number> is where the events are picked up. eg mine is /dev/input/event2 , 
from the sound of it yours would be /dev/input/event

FWIW I'm running twin Nova-T's in a 2.8GHz P4 and Opensuse 10.0

I've attached my lircd.conf for the Nova-T remote as well.

HTH

David

[1] You may well have to recompile if you didn't include dev/input support 
ISTR I had to recompile but worth a try with the std rpms' first as that 
might just have been me trying different things.
   



Yay!  It's working!  I recompiled lirc with the --driver=devinput option
and started lircd with the command line 'lircd --driver=dev/input
--device=/dev/input/event0' then 'irxevent &'.

I've remapped a few of the buttons in /home/mythtv/.lircrc so they make
more sense to me and my GF.

Thanks for the hints. :)

 

I struggled for about a month with this. Eventually, I ended up 
modifying budget-ci.c to make the remote work. I found that the Nova-t 
doesn't use LIRC at all, the only problem being that I have to recompile 
everytime I install a new kernel.


Your method seems so much easier, so I'll have to give it a go!

Cheers,

Adrian.
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

Re: [mythtv-users] Hauppauge Nova-T PCI and LIRC

2005-12-05 Thread Graeme Hilton 
[EMAIL PROTECTED] wrote:
> On Sunday 04 December 2005 21:58, Graeme Hilton wrote:
> I've been happily using Myth (SVN checkouts every month or so) for about
>> 4 months.  My setup at the moment is as follows:
>>
>> Hauppauge Nova-T DVB-T PCI (two of them)
>> AMD x86_64 system
>> Fedora Core 4 - all up to date
>> MythTV SVN revision 8053
>>
>> Has anyone had this happen to them?  Have you managed to solve the
>> problem and get your Hauppauge remote fully working?
> 
> Yep, had me confused for a short while. The IR is recognised automatically, 
> you'll find if you *don't* use lirc it'll still work (well the up/down/ok 
> etc) with mythfrontend.
> 
> What you need to do is use it with the dev/input driver[1], setup lirc to use 
> driver dev/input and device /dev/input/event where  number> is where the events are picked up. eg mine is /dev/input/event2 , 
> from the sound of it yours would be /dev/input/event0
> 
> FWIW I'm running twin Nova-T's in a 2.8GHz P4 and Opensuse 10.0
> 
> I've attached my lircd.conf for the Nova-T remote as well.
> 
> HTH
> 
> David
> 
> [1] You may well have to recompile if you didn't include dev/input support 
> ISTR I had to recompile but worth a try with the std rpms' first as that 
> might just have been me trying different things.

Yay!  It's working!  I recompiled lirc with the --driver=devinput option
and started lircd with the command line 'lircd --driver=dev/input
--device=/dev/input/event0' then 'irxevent &'.

I've remapped a few of the buttons in /home/mythtv/.lircrc so they make
more sense to me and my GF.

Thanks for the hints. :)

-- 
Graeme Hilton
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

Re: [mythtv-users] Hauppauge Nova-T PCI and LIRC

2005-12-04 Thread mythtv-users 
On Sunday 04 December 2005 21:58, Graeme Hilton wrote:
> Hi all,
>
> I've been happily using Myth (SVN checkouts every month or so) for about
> 4 months.  My setup at the moment is as follows:
>
> Hauppauge Nova-T DVB-T PCI (two of them)
> AMD x86_64 system
> Fedora Core 4 - all up to date
> MythTV SVN revision 8053
>
> As a relative newbie to Linux I think I've been getting on quite well,
> but the one thing that is completely defeating me is connecting the
> Hauppauge remote control to Myth.  From the outset there are five keys
> on the remote that translated to events on the system.  I have always
> been able to use the four arrow keys and the OK button.  However, none
> of the other buttons produce any effect on the system except when I do a
> 'cat /dev/input/event0'.  Then I get something resembling line noise
> whenever I press a key on the remote.
>
> I've downloaded and compiled lirc version 0.7.3pre1.
> I configured it to use the appropriate driver for the Hauppauge TV card
> (i2C required) and turned on debugging.  On 'make install' it created
> the appropriate device node in /dev :
> srw-rw-rw-  1 root root 0 Dec  4 17:50 /dev/lircd

> Has anyone had this happen to them?  Have you managed to solve the
> problem and get your Hauppauge remote fully working?

Yep, had me confused for a short while. The IR is recognised automatically, 
you'll find if you *don't* use lirc it'll still work (well the up/down/ok 
etc) with mythfrontend.

What you need to do is use it with the dev/input driver[1], setup lirc to use 
driver dev/input and device /dev/input/event where  is where the events are picked up. eg mine is /dev/input/event2 , 
from the sound of it yours would be /dev/input/event0

FWIW I'm running twin Nova-T's in a 2.8GHz P4 and Opensuse 10.0

I've attached my lircd.conf for the Nova-T remote as well.

HTH

David

[1] You may well have to recompile if you didn't include dev/input support 
ISTR I had to recompile but worth a try with the std rpms' first as that 
might just have been me trying different things.

# Please make this file available to others
# by sending it to <[EMAIL PROTECTED]>
#
# this config file was automatically generated
# using lirc-0.7.2(devinput) on Mon Oct 31 15:29:38 2005
#
# contributed by 
#
# brand:   irrecording
# model no. of remote control: 
# devices being controlled by this remote:
#

begin remote

  name  irrecording
  bits   16
  eps30
  aeps  100

  one 0 0
  zero0 0
  pre_data_bits   16
  pre_data   0x8001
  gap  135848
  toggle_bit  0


  begin codes
  Go   0x0161
  Power0x0074
  TV   0x0179
  Videos   0x0189
  Music0x0188
  Pictures 0x016F
  Guide0x016D
  Radio0x0181
  UP   0x0067
  LEFT 0x0069
  OK   0x001C
  RIGHT0x006A
  DOWN 0x006C
  BACK/EXIT0x00AE
  MENU 0x008B
  VOLUP0x0073
  VOLDOWN  0x0072
  PREVCH   0x019C
  MUTE 0x0071
  CHANUP   0x0192
  CHANDOWN 0x0193
  REC  0x00A7
  PLAY 0x00CF
  STOP 0x0080
  REPLAY   0x00A8
  SKIP 0x00D0
  REW  0x00A5
  FF   0x00A3
  PAUSE0x0077
  10x004F
  20x0050
  30x0051
  40x004B
  50x004C
  60x004D
  70x0047
  80x0048
  90x0049
  STAR 0x0184
  00x0052
  HASH 0x0172
  RED  0x018E
  GREEN0x018F
  YELLOW   0x0190
  BLUE 0x0191
  end codes

end remote


___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

[mythtv-users] Hauppauge Nova-T PCI and LIRC

2005-12-04 Thread Graeme Hilton 
Hi all,

I've been happily using Myth (SVN checkouts every month or so) for about
4 months.  My setup at the moment is as follows:

Hauppauge Nova-T DVB-T PCI (two of them)
AMD x86_64 system
Fedora Core 4 - all up to date
MythTV SVN revision 8053

As a relative newbie to Linux I think I've been getting on quite well,
but the one thing that is completely defeating me is connecting the
Hauppauge remote control to Myth.  From the outset there are five keys
on the remote that translated to events on the system.  I have always
been able to use the four arrow keys and the OK button.  However, none
of the other buttons produce any effect on the system except when I do a
'cat /dev/input/event0'.  Then I get something resembling line noise
whenever I press a key on the remote.

I've downloaded and compiled lirc version 0.7.3pre1.
I configured it to use the appropriate driver for the Hauppauge TV card
(i2C required) and turned on debugging.  On 'make install' it created
the appropriate device node in /dev :
srw-rw-rw-  1 root root 0 Dec  4 17:50 /dev/lircd

I used a lirc.conf file with appropriate contents for the Nova-T card
(second half of this file from the lirc.org website:
)

Then I start lircd in a terminal 'lircd -n -D2'
lircd 0.7.3pre1: started server socket
lircd 0.7.3pre1: parsing remote
lircd 0.7.3pre1: creating first remote
lircd 0.7.3pre1: parsing (null) remote
lircd 0.7.3pre1: begin codes
lircd 0.7.3pre1: end codes
lircd 0.7.3pre1: end remote
lircd 0.7.3pre1: config file read
lircd 0.7.3pre1: lircd(H=) ready

lircd 0.7.3pre1: registering local client
lircd 0.7.3pre1: accepted new client on H=
lircd 0.7.3pre1: Segmentation fault

Just after the slight pause, I get IrKick flash up on my KDE desktop
telling me that the "infrared system has severed its connection".

Has anyone had this happen to them?  Have you managed to solve the
problem and get your Hauppauge remote fully working?

If not, does anyone have any ideas on what I can do next to get the
remote up and running?

Many Thanks,

-- 
Graeme Hilton
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users