Re: PVR-150 and Imon on Ubuntu 7.10

[Andreas D. <an...@gm...>]

is iMon not an USB receiver? then mode2 would not show anything... but irw 
should...
Andreas

Am Sonntag, 16. Dezember 2007 23:27 schrieb Kjetil Kjernsmo:
> Hi all!
>
> I've just gotten a Antec Fusion V2 Silver box with a Hauppauge PVR-150
> (not the PVR-150MCE and not the HVR-1600 either). I have done a fresh
> install of Mythbuntu 7.10 on the box. This comes with lirc 0.8.2 and
> Ivtv 1.0.2. It should also imply that I have two IR receivers, one iMon
> and one on the PVR-150. However, I have so far seen no events from any
> of the remotes in the house.
>
> I (think I) want the PVR-150 working as a second IR device.
>
> It seems the iMon is detected trivially, and a /dev/lirc0 is there, but
> using mode2 on it returns no events. The PVR-150 card is also detected,
> but it looks like it isn't detected as a IR receiver.
>
> There is quite a lot of documentation on the web that is about the
> PVR-150 specifically, but it seems to be about the IR Blaster
> capability, and while I want that to work at some point, it is
> low-priority, first I just want my remote to work. I'm very confused as
> to how much I need to do to get the receive capability working. For
> example, do I need to patch as described in
> http://www.blushingpenguin.com/mark/blog/?p=24
> for IR receiving? Do I need the lirc_pvr150 module? And if I do, have
> these things allready been applied to the mythbuntu packages, so I
> don't need to do it myself?
>
> Since I first want only IR receiver, one could argue that I should stick
> to the iMon. I got the VFD working easy enough, and I want to use the
> volume knob. But, OTOH, there weren't a remote bundled with the
> chassis, only with the PVR-150 (probably the one described as the grey
> one), and at some point I want the blaster too. Then, this was pointed
> out to me:
> http://sourceforge.net/mailarchive/forum.php?thread_name=9CB5A76200029E439A
>44D2E52901D6A41741D9%40waldorf.Muppnet.local&forum_name=lirc-list so it
> sounds like what I actually should do is to use lirc_imon for the VFD and
> volume knob and the PVR-150 for the remote. Is this a
> reasonable conclusion to draw?
>
> With this in mind, I started to work with
> https://help.ubuntu.com/community/Install_Lirc_Gutsy#head-ea6e7f9c9047fe42f
>9d8507e931378f0382038c9 in combination with
> http://www.mythtv.org/wiki/index.php/Volume_Knob_on_Antec_Fusion
>
> I didn't get very far though. First, I don't know how to get the
> idVendor for the udev stuff and secondly, when I tried to modify the
> hardware.conf (also adding lirc_pvr150) and /etc/init.d/lirc, all I got
> was something like this:
> lircd/etc/init.d/lirc: 147: -d: not found
>
> There are a few two many unknows for me here, if I should try to get the
> PVR-150 remote working and leave the iMon for VFD and volume knob, how
> I should make the PVR-150 a second lirc device, and then how much of
> the patching Mythbuntu has allready done and how much that needs to be
> done for blasting vs just receiving.
>
> For reference, I paste some excerpts from my dmesg:
> [   26.261862] lirc_dev: IR Remote Control driver registered, at major
> 61
> [...]
> [   26.285581] ivtv:  ==================== START INIT IVTV
> ====================
> [   26.285585] ivtv:  version 1.0.0 (2.6.22-14-generic SMP mod_unload )
> loading
> [
> 26.287745]
> /build/buildd/linux-ubuntu-modules-2.6.22-2.6.22/debian/build/build-generic
>/media/lirc/lirc_imon/lirc_imon.c: Driver for Soundgraph iMON MultiMedian
> IR/VFD, v0.3
> [
> 26.287751]
> /build/buildd/linux-ubuntu-modules-2.6.22-2.6.22/debian/build/build-generic
>/media/lirc/lirc_imon/lirc_imon.c: Venky Raju <de...@ve...>
> [
> 26.287791]
> /build/buildd/linux-ubuntu-modules-2.6.22-2.6.22/debian/build/build-generic
>/media/lirc/lirc_imon/lirc_imon.c: imon_probe: found IMON device
> [   26.287799] lirc_dev: lirc_register_plugin: sample_rate: 0
> [
> 26.287832]
> /build/buildd/linux-ubuntu-modules-2.6.22-2.6.22/debian/build/build-generic
>/media/lirc/lirc_imon/lirc_imon.c: imon_probe: Registered iMON plugin
> (minor:0)
> [
> 26.287880]
> /build/buildd/linux-ubuntu-modules-2.6.22-2.6.22/debian/build/build-generic
>/media/lirc/lirc_imon/lirc_imon.c: imon_probe: iMON device on usb<5:2>
> initialized
> [   26.287895] usbcore: registered new interface driver lirc_imon
> [   26.695707] hda: TSSTcorp CDDVDW SH-S202H, ATAPI CD/DVD-ROM drive
> [   27.371086] hda: drive side 80-wire cable detection failed, limiting
> max speed to UDMA33
> [   27.371089] hda: selected mode 0x42
> [   27.371346] ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> [   27.375106] ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 18 (level,
> low) -> IRQ 18
> [   27.375113] PCI: Setting latency timer of device 0000:01:00.0 to 64
> [   27.375252] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  100.14.19
> Wed Sep 12 14:08:38 PDT 2007
> [   27.376181] ivtv0: Autodetected Hauppauge card (cx23416 based)
> [   27.376726] ACPI: PCI Interrupt 0000:02:07.0[A] -> GSI 21 (level,
> low) -> IRQ 21
> [   27.376739] ivtv0: Unreasonably low latency timer, setting to 64 (was
> 32)
> [   27.415380] hda: ATAPI 48X DVD-ROM DVD-R-RAM CD-R/RW drive, 2048kB
> Cache, UDMA(33)
> [   27.415391] Uniform CD-ROM driver Revision: 3.20
> [   28.052017] ivtv0: loaded v4l-cx2341x-enc.fw firmware
> (-139637027191888 bytes)
> [   28.269821] ivtv0: Encoder revision: 0x02050032
> [   28.269823] ivtv0: Recommended firmware version is 0x02060039.
> [   28.327970] tveeprom 1-0050: Hauppauge model 26154, rev E1B3, serial#
> 10270774
> [   28.327975] tveeprom 1-0050: tuner model is TCL M2523_3DB_E (idx 113,
> type 55)
> [   28.327978] tveeprom 1-0050: TV standards PAL(B/G) PAL(D/D1/K)
> (eeprom 0x44)
> [   28.327981] tveeprom 1-0050: audio processor is CX25843 (idx 37)
> [   28.327983] tveeprom 1-0050: decoder processor is CX25843 (idx 30)
> [   28.327985] tveeprom 1-0050: has no radio, has IR receiver, has IR
> transmitter
> [   28.327987] ivtv0: Autodetected Hauppauge WinTV PVR-150
> [   28.327989] ivtv0: reopen i2c bus for IR-blaster support
> [   28.455326] tuner 1-0061: chip found @ 0xc2 (ivtv i2c driver #0)
> [   28.733380] cx25840 1-0044: cx25843-24 found @ 0x88 (ivtv i2c driver
> #0)
> [   34.575525] cx25840 1-0044: loaded v4l-cx25840.fw firmware (16382
> bytes)
> [   34.721654] wm8775 1-001b: chip found @ 0x36 (ivtv i2c driver #0)
> [   34.799875] tuner 1-0061: type set to 55 (TCL 2002MB)
> [   35.189834] ivtv0: Registered device video0 for encoder MPEG (4 MB)
> [   35.189991] ivtv0: Registered device video32 for encoder YUV (2 MB)
> [   35.190130] ivtv0: Registered device vbi0 for encoder VBI (1 MB)
> [   35.190182] ivtv0: Registered device video24 for encoder PCM audio (1
> MB)
> [   35.232232] ivtv0: Initialized Hauppauge WinTV PVR-150, card #0
> [   35.232248] ivtv:  ====================  END INIT IVTV
> ====================
>
> I pasted my full dmesg a few days ago on IRC: http://pastebin.ca/813952
> There has been only minor changes since then, I think.
>
> I find it particularly interesting and relevant that it says
> [   28.327985] tveeprom 1-0050: has no radio, has IR receiver, has IR
> transmitter
>
> so, the kernel ought to know that there is an IR receiver there.
>
> This may be interesting too, I guess:
> root@tigger:~> cat /proc/bus/input/devices | grep Name
> N: Name="Macintosh mouse button emulation"
> N: Name="PC Speaker"
> N: Name="Logitech USB-PS/2 Optical Mouse"
> N: Name="Power Button (FF)"
> N: Name="Power Button (CM)"
>
> so, it doesn't look like I have a suitable input device.
>
> I'm fairly stuck here, so any advice that could get me proceeding would
> be greatly appreciated.
>
> Cheers,
>
> Kjetil
>
> -------------------------------------------------------------------------
> SF.Net email is sponsored by:
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services
> for just about anything Open Source.
> http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplac
>e