Menu
▾
▴
Re: hauppauge HVR-1250
|
From: Jay J. <cu...@ch...> - 2009-01-28 02:50:36
|
Offhand, based on what I saw searching with Google, this animal probably
isn't supported yet in the kernel drivers available. Read on.
Jay
At 01:08 PM 1/27/2009 -0500, Alexander Kohr wrote:
>On Jan 26, 2009, at 9:02 PM, Jay Jaeger wrote:
> "lsmod | grep lirc"
>>
>>If modules don't show up, find out why they are not loading. If they do,
>>then "dmesg | grep lirc" would almost certainly show something.
>I see
>lirc_zilog241480
>lirc_dv204081lirc_zilog
>i2c_core292169lirc_zilog,ivtv,i2c_algo_bit,mt2131,s5h1409,cx23885,nvidia,v412_common,tveeprom
OK, those are presumably what you get with the HVR-1250. However, your
output is a little garbled, perhaps the tabs got lost. Please make sure
when you cut and paste you don't lose the spaces.
It looks like you got: lirc_zilog and lirc_dev (rather than lirc_dv
which is what you entered here, presumably manually). But no lirc_pvr150,
which you seem to be trying to load, according to your later notes. That
may be the issue?
>>At 06:44 PM 1/26/2009 -0500, Alexander Kohr wrote:
>>>I have probably made a slight mess of things with all of the installs I
>>>have tried following these that or the other instrcutions trying to get
>>>it to work.
>>>
>>>Why don't we start with number 5 first as I think this is my biggest
>>>problem.
>>>
>>>>5. Do you have the correct lircd.conf and ~/.lircrc file for your
>>>>remote?
>>>Well I am not positive I have tried so many different ways of getting
>>>lirc to run that I can't be positive. Most recently I believe I have
>>>tried all 4 setup.sh options for hauppauge cards in the setup.sh for
>>>lircd & lirc 0.8.5 cvs for pvr150 tarball
>>
>>What "setup.sh" file are you referring to?
>
>the one located in lirc-0.8.5 cvs-pvr150 that comes from the tarball i
>downloaded.
That one is outside of my experience. I did compile my LIRC support for
Myth 0.20, but for the latest one I did, I just used what was delivered
with Fedora 10.
>>(Also, you have problems in the areas of 1-4, so worrying about 5 is
>>premature. Read on).
>>
>>
>>>Driver:Tv card:
>>>g: Hauppauge TV cared
>>>h. Hauppauge HVR-1300
>>>i. Hauppauge PVR-150 TV cared (new I2C layer Required)
>>>j.Hauppauge DVB-s card (ver 2.1) {currently installed with save & run
>>>configure}
>>
>>OK: What file name is this. EXACTLY?
>I am not exactly sure.
>Maybee these give some clues.
>in .setup.config
>it says LIRC_DRIVER=hauppauge_dvb
>In setup-driver.sh
>elif test "$1" = "j" ; then LIRC_DRIVER=hauppauge_dvb; DRIVER
>PARAMETER=none; DRIVER_PARAM_TYPE=none;
>
>in doing some more digging around it looks as if the file is called
>lircd.conf.hauppauge by the installer, which I believe should be correct.
Looking at http://www.lirc.org/html/table.html this one isn't listed, so I
cannot tell. Nor is it listed in my 0.8.4 documentation directory.
Also, a google for +lirc +"HVR-1250" indicates that perhaps the IR on this
card simply isn't supported yet. See
http://ubuntuforums.org/showthread.php?t=816788 and
http://lists-archives.org/video4linux/22015-hauppauge-remote.html
So, a suggestion would be to build your own serial IR receiver to handle
the remote, and not try and use the on-card IR receiver.
>>>here is the start of it.
>>>#
>>># this config file was automatically generated
>>># using lirc-0.5.5pre8 on Sun Apr 18 11:43:45 1999
>>>#
>>># contributed by Jens Leuschner
>>><<mailto:leu...@gm...>leu...@gm...>
>>>#
>>># brand: Hauppauge
>>># model:
>>># supported devices: WinTV primo; WinTV pci; WinTV radio
>>>#
>>># This config file will work with both homebrew receivers and
>>># original Hauppauge TV cards !!!
>>>#
>>>
>>>begin remote
>>>
>>> name blaster
>>> bits 32
>>> flags RAW_CODES
>>> eps 0
>>> aeps 0
>>> plead 0
>>> gap 333333
>>> repeat_bit 0
>>> begin raw_codes
>>>
>>>
>>>On Jan 24, 2009, at 8:34 AM, Jay Jaeger wrote:
>>>
>>>>I think we need more information to help you:
>>>>
>>>>1. What device files are created?
>>>>
>>>>ls -ld /dev/lirc*
>>>crw-r--r-- 1 root root 61, 0 2009-01-26 17:49 /dev/lirc
>>>prw-r--r-- 1 root root 0 2009-01-26 17:49 /dev/lircd
>>>prw-r--r-- 1 root root 0 2009-01-26 17:49 /dev/lircm
>>
>>This looks problematic -- no /dev/lirc0 (ordinarily I'd expect /dev/lirc
>>-> /dev/lirc0 rather than having /dev/lirc as a character special file
>>). Also permissions is an issue: your named pipes are only accessible by
>>root.
>I am pretty sure Ihave mae the /dev/lirc in one of my install attempts as
>it was not there. Should I rm it?
>well currently I am running all the commands while su - ed.
It would have thought it ought to get created automatically when the driver
loads.
>the instructions I am following do mention trying
> modprobe lirc_dev&& modeprobe lirc_pvr150 debug =1
>then
>lircd --device=/dev/lirc0
>
>following that i should be able to irw & see some output. However I don't.
>
>
>But for question number 2, I now see
>
>root246341012:40?00:00:00lircd --device=/dev/lirc0
>
>for Question #3
>I see
>lirc_dev: IR Remote Control driver registered, major 61
>lirc_pvr150: Unknown parameter `=1`
>lirc_pvr150: Unknown parameter `=1`
>lirc_zilog: Unknown parameter `=1`
>lirc_zilog: Unknown parameter `=1`
>lirc_dev ([-1]): open called
>lirc_dev ([-1]): open result = -ENODEV
Well it obviously didn't like the modprobe lirc_pvr150 with the debug=1
. Perhaps try it without that? Or, perhaps this guy just isn't
supported. I suspect that the last two repeating are from the client
opening the connection, but lirc_dev not knowing who to hand it off to.
>with the last two lines repeating over & over again. More will appear if i
>run irw but if I am not running irw no more will apear. It does not matter
>if I press buttons or not.
>I think the longer I leave irw running the more of the same error message
>it outputs.
>
>
>I still don't see anything in /var/log/messages
>However in /var/log/lircd I see for today.
>Jan 27 12:40:22 delayedvision.localdomain lircd: accepted new client on
>/dev/lircd
>Jan 27 12:40:22 delayedvision.localdomain lircd: could not open /dev/lirc0
>Jan 27 12:40:22 delayedvision.localdomain lircd: default_init(): No such
>device
>Jan 27 12:40:22 delayedvision.localdomain lircd: WARNING: Failed to
>initialize hardware
>Jan 27 12:40:35 delayedvision.localdomain lircd: removed client
>Jan 27 12:47:18 delayedvision.localdomain lircd: accepted new client on
>/dev/lircd
>Jan 27 12:47:18 delayedvision.localdomain lircd: could not open /dev/lirc0
>Jan 27 12:47:18 delayedvision.localdomain lircd: default_init(): No such
>device
>Jan 27 12:47:18 delayedvision.localdomain lircd: WARNING: Failed to
>initialize hardware
>Jan 27 12:47:24 delayedvision.localdomain lircd: removed client
>Jan 27 12:51:42 delayedvision.localdomain lircd: accepted new client on
>/dev/lircd
>Jan 27 12:51:42 delayedvision.localdomain lircd: could not open /dev/lirc0
>Jan 27 12:51:42 delayedvision.localdomain lircd: default_init(): No such
>device
>Jan 27 12:51:42 delayedvision.localdomain lircd: WARNING: Failed to
>initialize hardware
>Jan 27 12:51:44 delayedvision.localdomain lircd: removed client
>Jan 27 12:51:47 delayedvision.localdomain lircd: accepted new client on
>/dev/lircd
>Jan 27 12:51:47 delayedvision.localdomain lircd: could not open /dev/lirc0
>Jan 27 12:51:47 delayedvision.localdomain lircd: default_init(): No such
>device
>Jan 27 12:51:47 delayedvision.localdomain lircd: WARNING: Failed to
>initialize hardware
>Jan 27 12:51:49 delayedvision.localdomain lircd: removed client
>Jan 27 12:52:57 delayedvision.localdomain lircd: accepted new client on
>/dev/lircd
>Jan 27 12:52:57 delayedvision.localdomain lircd: could not open /dev/lirc0
>Jan 27 12:52:57 delayedvision.localdomain lircd: default_init(): No such
>device
>Jan 27 12:52:57 delayedvision.localdomain lircd: WARNING: Failed to
>initialize hardware
>Jan 27 12:52:58 delayedvision.localdomain lircd: removed client
>Jan 27 12:53:08 delayedvision.localdomain lircd: accepted new client on
>/dev/lircd
>Jan 27 12:53:08 delayedvision.localdomain lircd: could not open /dev/lirc0
>Jan 27 12:53:08 delayedvision.localdomain lircd: default_init(): No such
>device
>Jan 27 12:53:08 delayedvision.localdomain lircd: WARNING: Failed to
>initialize hardware
>Jan 27 12:53:10 delayedvision.localdomain lircd: removed client
>
>with more appearing whenever I run irw
>
>
>do you now have what you need.
Well, enough to make more sense. The drivers you are actually getting
loaded don't match up with your hardware. And, from what I can see, at
least back in July, this animal wasn't supported.
>>>>2. Is lircd running?
>>>>
>>>>ps -ef | grep lirc
>>> just the grep.
>>
>>Well, that's no good. Since lircd would run as root, that cannot be a
>>permissions problem. You should try running it from the command line to
>>see if it complains.
>>
>>>even after doing a modprobe lirc_dev debug=1 && modprobe lirc_pvr150
>>>debug =1
>>>(there does not seem to be anything for an lirc_dvbs )
>>>
>>>>
>>>>
>>>>3. What does dmesg show when the lirc driver installs -- does it
>>>>detect the remote?
>>>>
>>>>dmesg | grep lirc
>>>Nothing returned for today's install attempts.
>>
>>When you do the modprobe, you should see some messages that show up in
>>dmesg. If not, then the modules are not installing properly. Even if
>>you do the modprobe at the command line, after you do that, dmesg | grep
>>lirc should show something.
>>
>>You might try:
>>
>> lsmod | grep lirc
>>
>>That should show what lirc drivers loaded. If none, then you need to
>>find out why before going any furter.
>>
>>
>>
>>>>4. Are there any messages in /var/log/messages?
>>>>
>>>>grep lirc /var/log/messages
>>>Nothing returned
>>>Also nothing for today in /var/log/lircd
>>
>>Also not good.
>>
>>Until you deal with #1 thru #4, #5 is irrelevant.
>>
>>>thanks for any help you can provide.
>>>
>>>
>>>
>>>>
>>>>JRJ
>>>>
>>>>
>>>>At 03:31 PM 1/23/2009 -0500, Alexander Kohr wrote:
>>>>>I am having trouble getting a Hauppauge WinTv-HVR-1250 Model 1196 to
>>>>>work with LIRC on my Fedora 10 kernel 2.627.9-159.fc.x86_64
>>>>>
>>>>>I have modified/hacked the case such that the ir adapter's plug can be
>>>>>fully inserted as suggested at
>>>>><http://ubuntuforums.org/showthread.php?t=816788>http://ubuntuforums.org/showthread.php?t=816788
>>>>> .
>>>>>
>>>>>I have read and confirmed that it seems to be using the cx23885
>>>>>chipset. Back in July it would take a while for the drivers to be
>>>>>written.
>>>>>
>>>>>The most recent build of LIRC does not seem to work.
>>>>>
>>>>>I have also tried the prebuilt lirc 0.8.5 cvs for pvr150 tarball
>>>>>available at
>>>>><http://www.blushingpenguin.com/mark/blog/?p=24>http://www.blushingpenguin.com/mark/blog/?p=24
>>>>>which
>>>>>other sites would apear to lead me to believe should work for this
>>>>>card. I believe i have tried all the hauppauge options from the
>>>>>installer list.
>>>>>
>>>>>It would appear setup runs correctly and to make correctly & install
>>>>>
>>>>>However irw does not get any input.
>>>>>
>>>>>Has anyone succeeded in getting a Hauppauge WinTV-HVR-150 to work.
>>>>>
>>>>>-Alexander Kohr
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>------------------------------------------------------------------------------
>>>>>This SF.net email is sponsored by:
>>>>>SourcForge Community
>>>>>SourceForge wants to tell your story.
>>>>><http://p.sf.net/sfu/sf-spreadtheword>http://p.sf.net/sfu/sf-spreadtheword
>>
>>---
>>Jay R. Jaeger The Computer Collection
>><mailto:cu...@ch...>cu...@ch...
---
Jay R. Jaeger The Computer Collection
cu...@ch... |
