Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: MythTV: Users

streamzap remote RECENT info?

 

 

MythTV users RSS feed   Index | Next | Previous | View Threaded


greg at gregandeva

Aug 31, 2005, 9:11 PM

Post #1 of 7 (4488 views)
Permalink
streamzap remote RECENT info?

I've been searching around the net, and there are threads about
Streamzaps, but all of them mention having to apply patches to the
kernel or to the lirc source. Versions mentioned to which patches
actually apply are much older than what I have. I've got kernel
2.6.12-1.1376_FC3 and lirc 0.7.2 sources (which come with a
lirc_streamzap module). Is it possible to get the Streamzap to work with
this software or should I just give up and buy something else? Right now
this is the ONLY thing stopping me from deploying an otherwise well-
working front end in the TV room which might get the WAF above 0.
Without a working remote, it's useless in the TV room, and she hates
watching TV in the computer room on the monitor (no comfy couches in
here :-)

I can get the lirc_streamzap module loaded, I have a lircd.conf file
that supposedly works with this thing:

# this config file was automatically generated
# using lirc-0.7.1-CVS(serial) on Fri Feb 4 23:20:56 2005
#
# contributed by Christoph Bartelmus
#
# brand: Streamzap
# model no. of remote control: PC Remote
# devices being controlled by this remote: USB receiver
#

I can start up lircd, and connect to it with irw, and when I press
buttons, I see the red light on the receiver blinking, but irw has no
output at all.

If it's too much trouble to get the Streamzap to work, what other kind
of IR receiver and remote would be better for Myth with the lirc and
kernel versions that I have? I could use a USB, serial, or parallel
device as long as it will work with Linux/Myth without a lot of time and
frustration.

Thanks,
--Greg


debian-list at blueturtles

Sep 4, 2005, 4:22 AM

Post #2 of 7 (4392 views)
Permalink
Re: streamzap remote RECENT info? [In reply to]

>
> I can start up lircd, and connect to it with irw, and when I press
> buttons, I see the red light on the receiver blinking, but irw has no
> output at all.
> If it's too much trouble to get the Streamzap to work, what other kind
> of IR receiver and remote would be better for Myth with the lirc and
> kernel versions that I have? I could use a USB, serial, or parallel
> device as long as it will work with Linux/Myth without a lot of time and
> frustration.
>
> Thanks,
> --Greg
>
>
>
>
I've had it working with debian kernel 2.6.11 / 2.6.12 & vanilla 2.6.13.
Please post your modprobe lirc_streamzap dmesg
What lirc device files do you have?

Cheers

Ben

>
>
>
>
>

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


greg at gregandeva

Sep 5, 2005, 7:41 PM

Post #3 of 7 (4388 views)
Permalink
Re: streamzap remote RECENT info? [In reply to]

On Sun, 2005-09-04 at 21:22 +1000, Ben wrote:

> Please post your modprobe lirc_streamzap dmesg

First I see:

lirc_dev: no version for "struct_module" found: kernel tainted.
lirc_dev: IR Remote Control driver registered, at major 61
lirc_streamzap[-1]: Streamzap, Inc. Streamzap Remote Control on usb3:3
attached
lirc_dev: lirc_register_plugin: sample_rate: 0
usbcore: registered new driver lirc_streamzap
lirc_streamzap $Revision: 1.12 $ registered

But later I see:


usb_unlink_urb() is deprecated for synchronous unlinks. Use B()
instead.
Badness in usb_unlink_urb at drivers/usb/core/urb.c:461 (Tainted:
PF )
[<c02c7d30>] usb_unlink_urb+0x98/0x9a
[<dc9d1ddb>] irctl_close+0x77/0xe3 [lirc_dev]
[<c01785d7>] __fput+0xdc/0x10a
[<c0176d13>] filp_close+0x3f/0x6f
[<c010394d>] syscall_call+0x7/0xb




> What lirc device files do you have?

# ls -l /dev/lirc*
crw------- 1 root root 61, 0 Sep 5 12:56 /dev/lirc0
srw-rw-rw- 1 root root 0 Sep 5 19:41 /dev/lircd

I run "lircd -d /dev/lirc0" followed by "irw" that produces no output.

On the other hand, if I run "irrecord -d /dev/lirc0 /tmp/out", then I do
get a response from irrecord, which suggests there is a problem with
my /etc/lircd.conf file. The file I'm using is the one I got from
lirc.org though:

# this config file was automatically generated
# using lirc-0.7.1-CVS(serial) on Fri Feb 4 23:20:56 2005
#
# contributed by Christoph Bartelmus
#
# brand: Streamzap
# model no. of remote control: PC Remote
# devices being controlled by this remote: USB receiver

Since would appear that Chris s one of the main developers for lirc, I
would presume this file has been well tested with a Streamzap remote and
this module. From that, my best guess is that I've got a new style
remote, that needs it's own lircd.conf file.

To that end, I tried running "irrecord" to produce a lircd.conf file.
When I did that, and then ran "irw", every button showed up as the first
one declared ("OK" in this case). I will need to play with irrecord more
before I make any conclusions, but it's clear that the stock lircd.conf
file does not work with my remote.

--Greg


debian-list at blueturtles

Sep 5, 2005, 10:13 PM

Post #4 of 7 (4375 views)
Permalink
Re: streamzap remote RECENT info? [In reply to]

Greg Woods wrote:

> On Sun, 2005-09-04 at 21:22 +1000, Ben wrote:
>
>
>
>> Please post your modprobe lirc_streamzap dmesg
>>
>
>
> First I see:
>
> lirc_dev: no version for "struct_module" found: kernel tainted.
> lirc_dev: IR Remote Control driver registered, at major 61
> lirc_streamzap[-1]: Streamzap, Inc. Streamzap Remote Control on usb3:3
> attached
> lirc_dev: lirc_register_plugin: sample_rate: 0
> usbcore: registered new driver lirc_streamzap
> lirc_streamzap $Revision: 1.12 $ registered
>
> But later I see:
>
>
> usb_unlink_urb() is deprecated for synchronous unlinks. Use B()
> instead.
> Badness in usb_unlink_urb at drivers/usb/core/urb.c:461 (Tainted:
> PF )
> [<c02c7d30>] usb_unlink_urb+0x98/0x9a
> [<dc9d1ddb>] irctl_close+0x77/0xe3 [lirc_dev]
> [<c01785d7>] __fput+0xdc/0x10a
> [<c0176d13>] filp_close+0x3f/0x6f
> [<c010394d>] syscall_call+0x7/0xb
>
>
Yes, I saw this too when I unplugged the usb receiver

> The file I'm using is the one I got from
> lirc.org though:
>
> # this config file was automatically generated
> # using lirc-0.7.1-CVS(serial) on Fri Feb 4 23:20:56 2005
> #
> # contributed by Christoph Bartelmus
> #
> # brand: Streamzap
> # model no. of remote control: PC Remote
> # devices being controlled by this remote: USB receiver
>
>
Yes same file I have here

> Since would appear that Chris s one of the main developers for lirc, I
> would presume this file has been well tested with a Streamzap remote and
> this module. From that, my best guess is that I've got a new style
> remote, that needs it's own lircd.conf file.
>
> To that end, I tried running "irrecord" to produce a lircd.conf file.
> When I did that, and then ran "irw", every button showed up as the first
> one declared ("OK" in this case).

When I use irw I then get a syslog message (assuming you used syslog
log compile option) showing a connection
# cat /var/log/syslog | grep lirc
Sep 6 10:07:30 localhost kernel: lirc_dev: IR Remote Control driver
registered, at major 61
Sep 6 10:07:30 localhost kernel: lirc_streamzap: no version for
"lirc_unregister_plugin" found: kernel tainted.
Sep 6 10:07:30 localhost kernel: lirc_streamzap[-1]: Streamzap, Inc.
Streamzap Remote Control on usb1:2 attached
Sep 6 10:07:30 localhost kernel: lirc_dev: lirc_register_plugin:
sample_rate: 0
Sep 6 10:07:30 localhost kernel: usbcore: registered new driver
lirc_streamzap
Sep 6 10:07:30 localhost kernel: lirc_streamzap $Revision: 1.12 $
registered
Sep 6 10:07:31 localhost lircd-0.7.2[4710]: lircd(streamzap) ready
Sep 6 10:07:31 localhost lircd-0.7.2[4710]: accepted new client on
/dev/lircd
Sep 6 10:07:51 localhost lircd-0.7.2[4710]: accepted new client on
/dev/lircd
Sep 6 13:25:07 localhost lircd-0.7.2[4710]: accepted new client on
/dev/lircd
Sep 6 13:28:05 localhost lircd-0.7.2[4710]: removed client
Sep 6 13:30:50 localhost lircd-0.7.2[4710]: accepted new client on
/dev/lircd
Sep 6 13:35:44 localhost lircd-0.7.2[4710]: removed client
Sep 6 13:36:11 localhost lircd-0.7.2[4710]: accepted new client on
/dev/lircd
Sep 6 13:40:45 localhost lircd-0.7.2[4710]: removed client


After running irw I see:
Sep 6 14:25:29 localhost lircd-0.7.2[4710]: accepted new client on
/dev/lircd
Sep 6 14:25:30 localhost lircd-0.7.2[4710]: removed client


Do you see the connection attempt with irw? Do you see any other lirc
errors

> I will need to play with irrecord more
> before I make any conclusions, but it's clear that the stock
> lircd.conffile does not work with my remote.
>
>
Mine works with this file. IIRC irecord bypasses the daemon, irw doesn't
Let us know how you progress.

Cheers Ben
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


greg at gregandeva

Sep 6, 2005, 7:25 AM

Post #5 of 7 (4395 views)
Permalink
Re: streamzap remote RECENT info? [In reply to]

Thank you for the information.

On Tue, 2005-09-06 at 15:13 +1000, Ben wrote:

> Let us know how you progress.

Will do, but I have a busy week so it may be a few days before I have
time to get back to this again.

--Greg


evilbarney at gmail

Sep 18, 2005, 6:26 PM

Post #6 of 7 (4356 views)
Permalink
Re: streamzap remote RECENT info? [In reply to]

Greg,
I've fought with my streamzap and myth for a long time. I was unable to get
it to work properly with FC3, but just now got it working with FC4. not sure
if this is what you need, but I could not find a howto like this anywhere,
so I will post it. maybe it will work for you, or someone else.
My steps--
1. followed Jarrod Guid for FC4 including doing the Yum for lirc dirvers.
when done, IRW will not work nor lircd start up (not even sure if this step
is needed)
2. Get kernel source for FC4. I did a "yum install kernel-devel" This
downloaded the lasted FC4 2.6 kernel source. note that I did already
upgraded the kernel with "yum upgrade" per jarrods before.
3. went and downloaded the lirc-0.7.2 source from lirc.org <http://lirc.org>.
unzipped it and changed into that directory
4. ran "./setup.sh" this opened up a shell gui install dialog box. inside
there, I choose "usb devices, then streamzap" not sure if that is the path,
but if you go under "other devices" or usb, you will find the one for
streamzap
5. then inside the same gui, I choose to save and run config
6. config ran with no errors. before I got the source, it would give me a no
source found error. note that some text talks about making symlinks to where
you kernel source lives if not found but installed. I did not have to do
this with FC4 and the yum kernel source install.
7. then, as prompted, I ran make, then when that was done, I ran "make
install" the compile ran without errors
8.. I then edited /etc/modprobe.conf. I added the last line of "alias
char-major-61 lirc_streamzap" I'm not sure if the install did that step for
me, but either way it needs to be there.
9. then I started up the licrd demaon by doing "/sbin/service lircd start" I
got one green "OK" sometimes to check, I will stop and start the service
again to make sure it shuts down right
10. under the lirc-0.7.2 install folder, I cd to the tools folder and ran
irw. can't remember if I had to chmod it to run first (chmod 755 irw if you
do). at that point, I could hit keys on the streamzap remote and see inputs
in the shell. I hit control C to exit
11. the last step was to add the lircrc config file to your home directories
so it works with mythtv. if you search this forum, there are good posts for
pre-built streamzap lircrc files. find one you like, download it and place
it in "/home/<user>/.mythtv/lircrc .. note that the file name for the config
is lircrc with no extensions. I also had to put the same config under
"/root/.mythtv/lircrc" because I run my frontend under root sometimes.
from there, it all works fine. I might need to change some of the settings
in lircrc, or put the config file in some other places so it works well with
mplayer, but looks like there are good postings here to help with that.
hope this helps.
-EB


kuphal at dls

Sep 18, 2005, 7:00 PM

Post #7 of 7 (4320 views)
Permalink
Re: streamzap remote RECENT info? [In reply to]

Evil Barney wrote:

> Greg,
>
> I've fought with my streamzap and myth for a long time. I was unable
> to get it to work properly with FC3, but just now got it working with
> FC4. not sure if this is what you need, but I could not find a howto
> like this anywhere, so I will post it. maybe it will work for you, or
> someone else.
>
> My steps--
>
> 1. followed Jarrod Guid for FC4 including doing the Yum for lirc
> dirvers. when done, IRW will not work nor lircd start up (not even
> sure if this step is needed)
> 2. Get kernel source for FC4. I did a "yum install kernel-devel"
> This downloaded the lasted FC4 2.6 kernel source. note that I did
> already upgraded the kernel with "yum upgrade" per jarrods before.
> 3. went and downloaded the lirc-0.7.2 source from lirc.org
> <http://lirc.org>. unzipped it and changed into that directory
> 4. ran "./setup.sh" this opened up a shell gui install dialog box.
> inside there, I choose "usb devices, then streamzap" not sure if that
> is the path, but if you go under "other devices" or usb, you will find
> the one for streamzap
> 5. then inside the same gui, I choose to save and run config
> 6. config ran with no errors. before I got the source, it would give
> me a no source found error. note that some text talks about making
> symlinks to where you kernel source lives if not found but installed.
> I did not have to do this with FC4 and the yum kernel source install.
> 7. then, as prompted, I ran make, then when that was done, I ran
> "make install" the compile ran without errors
> 8.. I then edited /etc/modprobe.conf. I added the last line of "alias
> char-major-61 lirc_streamzap" I'm not sure if the install did that
> step for me, but either way it needs to be there.
> 9. then I started up the licrd demaon by doing "/sbin/service lircd
> start" I got one green "OK" sometimes to check, I will stop and
> start the service again to make sure it shuts down right
> 10. under the lirc-0.7.2 install folder, I cd to the tools folder and
> ran irw. can't remember if I had to chmod it to run first (chmod 755
> irw if you do). at that point, I could hit keys on the streamzap
> remote and see inputs in the shell. I hit control C to exit
> 11. the last step was to add the lircrc config file to your home
> directories so it works with mythtv. if you search this forum, there
> are good posts for pre-built streamzap lircrc files. find one you
> like, download it and place it in "/home/<user>/.mythtv/lircrc .. note
> that the file name for the config is lircrc with no extensions. I
> also had to put the same config under "/root/.mythtv/lircrc" because I
> run my frontend under root sometimes.
>
> from there, it all works fine. I might need to change some of the
> settings in lircrc, or put the config file in some other places so it
> works well with mplayer, but looks like there are good postings here
> to help with that.
>
> hope this helps.

That's interesting. I just tried last night moving my main frontend
from RH9 with a streamzap to FC4 and everything was fine until I started
using the remote and it would lock the box up hard after about 10-15
remote button presses. I was using the same configuration files from my
existing installation and even tried backing down to 0.7.1 with the same
results...

Kevin
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

MythTV users RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.