Mailing List Archive

HDPVR and lirc problem after Upgrade to 0.28
I was forced into rebuilding my myth box as the boot drive failed. I
decided to upgrade at the same time. I was on Mythbuntu 10.04 with Myth
0.25 and now using Mythbuntu 16.04 w myth 0.28. The new boot disk is an
SSD so it is booting much faster now. Maybe too fast for something??

So I have 2 problems that may actually be the same problem.

1st problem: Bootup is showing USB errors (for the hdpvr) and seems to
hang for a while before it times out and moves on.
2nd problem: Remote and Blaster are not working (maybe lirc not
configured right?)

At bootup it takes a long time and I see USB 2-2 errors on the screen.
Here is what dmesg shows about USB 2-2
jim@docbuntu:~$ dmesg | grep "usb 2" | more
[ 1.807395] usb 2-2: new high-speed USB device number 2 using ehci-pci
[ 7.103590] usb 2-2: device descriptor read/64, error -110
[ 22.720177] usb 2-2: device descriptor read/64, error -110
[ 22.948195] usb 2-2: new high-speed USB device number 3 using ehci-pci
[ 28.096390] usb 2-2: device descriptor read/64, error -110
[ 43.712978] usb 2-2: device descriptor read/64, error -110
[ 43.940995] usb 2-2: new high-speed USB device number 4 using ehci-pci
[ 49.225494] usb 2-2: device descriptor read/8, error -110
[ 54.601669] usb 2-2: device descriptor read/8, error -110
[ 54.829402] usb 2-2: new high-speed USB device number 5 using ehci-pci
[ 59.977969] usb 2-2: device descriptor read/8, error -110
[ 65.354144] usb 2-2: device descriptor read/8, error -110
[10283.423621] usb 2-2: new high-speed USB device number 6 using ehci-pci
[10283.599246] usb 2-2: New USB device found, idVendor=2040, idProduct=4902
[10283.599248] usb 2-2: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[10283.599249] usb 2-2: Product: Hauppauge HD PVR
[10283.599250] usb 2-2: Manufacturer: AMBA
[10283.599251] usb 2-2: SerialNumber: 00A459E5
jim@docbuntu:~$

In MCC under Infrared I have "Steamzap PC Remote" selected and "Enable
an IR Transmitter" with "MS Windows Media Center V2 (usb):Dish Receiver"
selected. Pretty sure this is how the old system was set.

I'm using a generic USB mceusb receiver and blaster unit that worked
fine previously. Here it is listed in dmesg
jim@docbuntu:~$ dmesg | grep "usb 3" | more
[ 2.115397] usb 3-3: new full-speed USB device number 2 using ohci-pci
[ 2.304460] usb 3-3: New USB device found, idVendor=0471, idProduct=0815
[ 2.304463] usb 3-3: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[ 2.304464] usb 3-3: Product: eHome Infrared Transceiver
[ 2.304465] usb 3-3: Manufacturer: Philips
[ 2.304466] usb 3-3: SerialNumber: PH00HS4J
[ 68.985959] mceusb 3-3:1.0: Registered Philips eHome Infrared
Transceiver with mce emulator interface version 1
[ 68.985960] mceusb 3-3:1.0: 2 tx ports (0x3 cabled) and 2 rx sensors
(0x1 active)
jim@docbuntu:~$

I'm certain the issue is not with the hdpvr. I changed the channel
change script to /bin/true and myth will record from it. Just not the
right channels.

When I test the channel change script I get this:

jim@docbuntu:~$ cd /etc/lirc
jim@docbuntu:/etc/lirc$ ls -l
total 32
-rwxr-xr-x 1 root root 2062 Aug 17 22:04 chan_changer
-rw-r--r-- 1 root root 1453 Aug 20 09:17 hardware.conf
-rw-r--r-- 1 root root 1370 Aug 18 11:13 hardware.conf.jbm
-rw-r--r-- 1 root root 1470 Aug 20 09:17 hardware.conf.old
-rw-r--r-- 1 root root 695 Aug 20 09:17 lircd.conf
-rw-r--r-- 1 root root 644 Aug 20 09:16 lircd.conf.dpkg-old
-rw-r--r-- 1 root root 539 Aug 18 11:09 lircd.conf.jbm
-rw-r--r-- 1 root root 121 Jan 27 2016 lircmd.conf
jim@docbuntu:/etc/lirc$ ./chan_changer 105
irsend: command failed: SEND_ONCE dish1 select
irsend: transmission failed
irsend: command failed: SEND_ONCE dish1 up
irsend: transmission failed
irsend: command failed: SEND_ONCE dish1 guide
irsend: transmission failed
irsend: command failed: SEND_ONCE dish1 1
irsend: transmission failed
irsend: command failed: SEND_ONCE dish1 0
irsend: transmission failed
irsend: command failed: SEND_ONCE dish1 5
irsend: transmission failed
irsend: command failed: SEND_ONCE dish1 SELECT
irsend: transmission failed
irsend: command failed: SEND_ONCE dish1 SELECT
irsend: transmission failed
jim@docbuntu:/etc/lirc$

I'm not sure where to go from here. I've read the instructions here
https://www.mythtv.org/wiki/Hauppauge_HD-PVR but it all seems to be for
much older Myth and kernels.

Any suggestions on getting this working?

Jim
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: HDPVR and lirc problem after Upgrade to 0.28 [ In reply to ]
On 8/20/2017 1:39 PM, Jim wrote:
> I was forced into rebuilding my myth box as the boot drive failed. I
> decided to upgrade at the same time. I was on Mythbuntu 10.04 with
> Myth 0.25 and now using Mythbuntu 16.04 w myth 0.29. The new boot disk
> is an SSD so it is booting much faster now. Maybe too fast for
> something??
>
>
Can anyone assist with getting an HDPVR working under Mythbuntu 16.04?
I need to get the channel changer blaster working so it can change
channels on the STB.

Jim

_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: HDPVR and lirc problem after Upgrade to 0.28 [ In reply to ]
On 8/29/2017 11:47 AM, Jim wrote:
> On 8/20/2017 1:39 PM, Jim wrote:
>> I was forced into rebuilding my myth box as the boot drive failed. I
>> decided to upgrade at the same time. I was on Mythbuntu 10.04 with
>> Myth 0.25 and now using Mythbuntu 16.04 w myth 0.29. The new boot
>> disk is an SSD so it is booting much faster now. Maybe too fast for
>> something??
>>
>>
> Can anyone assist with getting an HDPVR working under Mythbuntu 16.04?
> I need to get the channel changer blaster working so it can change
> channels on the STB.
>
> Jim
>
>
A Mythbuntu 16.04 reinstall and most everything is working now.
Oddly if I set MCC to use the Blaster with Dish, the remote and blaster
do not work. If I turn that off in MCC it all works. I guess that's
because it is "in kernel" now?

A big thanks to all who work on this project. I had actually considered
moving to a Dish provided DVR during my "crisis". Now I am so glad I didn't.

Jim
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org