mce_usb2 ir blaster broke

[pointman87]

On 17/5-12 i did apt-get update && apt-get upgrade, after that my mce_usb2 ir blaster stopped working. Do anyone know what happened around that time, or do anyone know where to start dig?

BR Daniel

[seth]

 

What version of LMCE are you running?

Just a question, as I was not aware that the blasters ever worked.

Confused. As usual. 

Best Regards,

Seth

[pointman87]

Ha, my bad, I'm running 10.04. The blaster have worked both under 8.10 and 10.04, witch is great as the cost about a tenth of a usbuirt.

FYI i did an upgrade on my whole system today (12060626053) and still no blaster

[DragonK]

I think we ALL are interested in how you got it working in the first place??

Karel

[bushtech]

Must have Scottish blood in me. Became extremely interested when I saw this:"as the cost about a tenth of a usbuirt" 

So please tell

[jamo]

Me too. Please share... was about to re-mortgage the house for a usb-uirt.

[seth]

 
Yes this really interests me. I would need to buy 3 USB-UIRT, or use the existing IR Blasters on my MCE remotes, which I boought 4 for the price of one USB-UIRT.

Very interested!!

Best Regards,

Seth

[pointman87]

Well... For about 2 year ago i plugged it in my bedroom MD and it have worked since
I will take a photo of it and post here, that way you (Seth) can compare it to yours to see if they are similar. BUT... It doesn't work yet, it makes me so angry. Anyone know if lira updated recently? I think the problem is in lira, not in LMCE.

BR Daniel

[totallymaxed]

Well... For about 2 year ago i plugged it in my bedroom MD and it have worked since
I will take a photo of it and post here, that way you (Seth) can compare it to yours to see if they are similar. BUT... It doesn't work yet, it makes me so angry. Anyone know if lira updated recently? I think the problem is in lira, not in LMCE.

BR Daniel

Not all MCE USB Transceivers are the same. Some will work some will not dependent on chipsets/ID's etc. However if it worked before then it's either 'died' (possible but reasonably unlikely in my experience), the usb port has failed (also possible)... try the following;

Code Select Expand


lsusb <return>


and you should see a something like this;

Code Select Expand


Bus 003 Device 002: ID 1784:0001 TopSeed Technology Corp. eHome Infrared Transceiver


The following wiki article may be of help in figuring out why you mce usb transceiver is not working... or in making one that doesn't work currently work; http://wiki.linuxmce.org/index.php/Adding_a_New_MCE_Compatible_Transceiver

All the best

Andrew

[pointman87]

The problem is solved! At the same time as i upgraded my MD i added the yaVDR repo to pull the latest vdr and plugins, in the process lirc got upgraded from the yaVDR repo. I think that was the problem. I rebuild the MD and upgraded it to the latest packages without yaVDR repo, and now it works again

[Marie.O]

People who have a problem with lirc due to the yavdr repo, might want to create/edit the /etc/apt/preferences file to contain the following lines:

Code Select Expand


Package: liblircclient0
Pin: version 0.8.6-0*
Pin-Priority: 1000


From that point forward, the liblircclient library will be the correct one. I will see that I can get the correct -dev package into our repo, to work with the yavdr liblircclient as well.

[pointman87]

People who have a problem with lirc due to the yavdr repo, might want to create/edit the /etc/apt/preferences file to contain the following lines:

Code Select Expand


Package: liblircclient0
Pin: version 0.8.6-0*
Pin-Priority: 1000


From that point forward, the liblircclient library will be the correct one. I will see that I can get the correct -dev package into our repo, to work with the yavdr liblircclient as well.

Thank you Posde, i use yaVDR for vdr-1.7.22 and the newer that Linuxmce-repo StreamdevClient, since it seems to work better on my install. I had frame drops on my MDs with the older version. Maybe the Linuxmce-repo could upgrade vdr and its plugins to?

BR Daniel

[tschak909]

Can we have a resolution on this so we can close this ticket?

-Thom