View unanswered posts    View active topics

All times are UTC - 6 hours





Post new topic Reply to topic  [ 67 posts ] 
Go to page Previous  1, 2, 3, 4, 5  Next

Print view Previous topic   Next topic  
Author Message
Search for:
PostPosted: Sun Oct 26, 2014 5:22 pm 
Offline
Joined: Sun Sep 05, 2004 7:06 pm
Posts: 690
I had a chance today to wipe out one of my R8.1 FE.

Installed from scratch R8.1 FE and then upgraded to R8.2 FE testing.

When I installed R8.1 it let me choose my remote so i chose snapstream_firefly. It installed automatically and chose channel 1. When the PC rebooted I checked the firefly remote it worked fine, and then installed google-chrome and xbmc, Also setup USB Logitech Speakers to work in XMBC and Myth.

When I ran the upgrade i noticed that it said something about downgrading Lirc and then kept going until the end when said R8.2 FE installed successfully. When I rebooted the sound and it worked fine in Myth TV and XBMC. However, I also noticed that my Firefly Remote was now not working at all.

In Service Menu\Linhes\Remotes I checked and it was still set to channel 1 just like in R8.1 but now it's broken. Something is fishy with Lirc I suppose. It needs some attention....


Top
 Profile  
 
PostPosted: Sun Oct 26, 2014 6:39 pm 
Offline
Joined: Fri Jul 21, 2006 11:12 pm
Posts: 1194
Location: SC
RacerX wrote:
When I ran the upgrade i noticed that it said something about downgrading Lirc and then kept going until the end when said R8.2 FE installed successfully.
Since we had to script the update anyway we dropped the epoch which caused pacman to think it is being downgraded. It really wasn't a downgrade. There were only a couple changes to LIRC between 8.1 and 8.2 and mainly it was just recompiled for the new kernel.


Top
 Profile  
 
PostPosted: Sun Oct 26, 2014 7:31 pm 
Offline
Joined: Sun Sep 05, 2004 7:06 pm
Posts: 690
Thanks for sharing your insight, Previously I was under the impression that Linhes was using the ATI Lirc Driver because the one from the Kernel didn't work. But now we have a new Kernel so the driver with the Kernel might work or it might need to be blacklisted to let the Lirc driver work. Just an idea....


Top
 Profile  
 
PostPosted: Mon Oct 27, 2014 8:28 am 
Offline
Joined: Sun Sep 05, 2004 7:06 pm
Posts: 690
In regards to the MythWelcome Shutdown in 8.2. This morning I uninstalled MythWelcome, Shutdown. Started up the PC and then reinstalled MythWelcome. Checked a show just for the test, exited myth FE. and then watched MythWelcome countdown 30 seconds and Shutdown my PC properly....first time it R8.2 :D :D :D


Top
 Profile  
 
PostPosted: Mon Oct 27, 2014 11:36 am 
Offline
Joined: Sun Sep 05, 2004 7:06 pm
Posts: 690
More on the Firefly not working, in the Lirc Log in mythweb R8.2 this is what it says

Code:
Sep 28 11:58:36 mythbox lircd: lircd(default) ready, using /var/run/lirc/lircd
Sep 28 23:10:49 mythbox lircd: accepted new client on /var/run/lirc/lircd
Sep 28 23:10:49 mythbox lircd: could not get file information for /dev/lirc0
Sep 28 23:10:49 mythbox lircd: default_init(): No such file or directory
Sep 28 23:10:49 mythbox lircd: WARNING: Failed to initialize hardware
Sep 28 23:10:51 mythbox lircd: accepted new client on /var/run/lirc/lircd
Sep 28 23:11:02 mythbox lircd: accepted new client on /var/run/lirc/lircd
Sep 28 23:11:12 mythbox lircd: accepted new client on /var/run/lirc/lircd
Sep 28 23:17:51 mythbox lircd: removed client
Sep 28 23:54:49 mythbox lircd: removed client
Sep 29 02:22:19 mythbox lircd: caught signal
Sep 29 02:58:36 mythbox lircd: lircd(default) ready, using /var/run/lirc/lircd
Sep 29 02:58:57 mythbox lircd: accepted new client on /var/run/lirc/lircd
Sep 29 02:58:57 mythbox lircd: could not get file information for /dev/lirc0
Sep 29 02:58:57 mythbox lircd: default_init(): No such file or directory
Sep 29 02:58:57 mythbox lircd: WARNING: Failed to initialize hardware
Sep 29 02:58:59 mythbox lircd: accepted new client on /var/run/lirc/lircd
Sep 29 03:43:50 mythbox lircd: caught signal


The light is lit on the firefly receiver. I tried changing the remote and rebooting and then selecting the firefly but it's not responding at all...


Top
 Profile  
 
PostPosted: Mon Oct 27, 2014 1:11 pm 
Offline
Joined: Fri Jul 21, 2006 11:12 pm
Posts: 1194
Location: SC
What does this give?
Code:
ls /dev/lirc*


Top
 Profile  
 
PostPosted: Mon Oct 27, 2014 1:24 pm 
Offline
Joined: Sun Sep 05, 2004 7:06 pm
Posts: 690
Code:
ls: cannot access /dev/lirc*: No such file or directory


Top
 Profile  
 
PostPosted: Mon Oct 27, 2014 1:35 pm 
Offline
Joined: Fri Jul 21, 2006 11:12 pm
Posts: 1194
Location: SC
/tmp/remotes.log might give a little more info. I don't know anything about the Firefly so asking about /dev/lirc may not apply.


Top
 Profile  
 
PostPosted: Mon Oct 27, 2014 2:18 pm 
Offline
Joined: Sun Sep 05, 2004 7:06 pm
Posts: 690
here is the remotes log

Quote:
[mythtv@mythbox tmp]$ cat remotes.log
Mon Oct 27 13:59:34 CDT 2014 --- run started
====== lirc modules already loaded ==========
====== lirc modules end =========


Disable in kernel remote driver
Starting remotes from /usr/bin/lircd -r -n -d /dev/lirc0 --output /var/run/lirc/lircd
lircd: lircd(default) ready, using /var/run/lirc/lircd
lircd: accepted new client on /var/run/lirc/lircd
lircd: could not get file information for /dev/lirc0
lircd: default_init(): No such file or directory
lircd: WARNING: Failed to initialize hardware
lircd: accepted new client on /var/run/lirc/lircd
lircd: accepted new client on /var/run/lirc/lircd
lircd: accepted new client on /var/run/lirc/lircd
lircd: removed client
lircd: accepted new client on /var/run/lirc/lircd
lircd: removed client
lircd: removed client
lircd: accepted new client on /var/run/lirc/lircd
lircd: removed client


Thanks for the help, Jams helped with Firefly in R8.1 to get multiple firefly's working. Historically it's odd that it's not working all.
It works perfect in R8.1. I can keep the Master FE/BE on R8.2 and keep the FE's on R8.1 for while.....


Last edited by RacerX on Mon Oct 27, 2014 2:41 pm, edited 1 time in total.


Top
 Profile  
 
PostPosted: Mon Oct 27, 2014 2:37 pm 
Offline
Joined: Fri Jul 21, 2006 11:12 pm
Posts: 1194
Location: SC
What sticks out to me is that it is trying to use /dev/lirc0 and you said you don't have /dev/lirc0. So that usually means the kernel didn't see the device and create. If you are going back to R8.1 you might take a look at /dev/lirc and the remotes.log to compare.


Top
 Profile  
 
PostPosted: Mon Oct 27, 2014 3:40 pm 
Offline
Joined: Sun Sep 05, 2004 7:06 pm
Posts: 690
I have R8.1 FE on my TV it has bit overscan so here goes

Code:
ls /dev/lirc*

lirc0


Code:
cat /tmp/remotes.log

ready using /var/run/lirc/lircd

lirc_aitusb                      13124   0
lirc_dev                          9039     lircusb
usbcore                         150398 ohci, ehci_hcd,usbhid/lircatiusb

disable in kernel remote driver
starting remote from /usr.sbin.lircd -r -n -d /dev/lirc0
--output /var/run/lirc
lircd:  (default) ready using /var/lirc/lircd
accepted new client on /var/run/lirc/lircd


just as a test, is there a command to reconfigure Lirc?


Top
 Profile  
 
PostPosted: Mon Oct 27, 2014 3:59 pm 
Offline
Joined: Fri Jul 21, 2006 11:12 pm
Posts: 1194
Location: SC
Looks like R8.2 kernel isn't creating /dev/lirc0. On 8.2 does lsusb show the firefly?


Top
 Profile  
 
PostPosted: Mon Oct 27, 2014 4:29 pm 
Offline
Joined: Sun Sep 05, 2004 7:06 pm
Posts: 690
Code:
[root@mythbox mythtv]# lsusb
Bus 002 Device 016: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 002 Device 003: ID 0cf3:3005 Atheros Communications, Inc. AR3011 Bluetooth
Bus 003 Device 019: ID 03f0:140c Hewlett-Packard
Bus 003 Device 003: ID 0bc7:0008 X10 Wireless Technology, Inc. Wireless Transceiver (ACPI-compliant)
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


Last edited by RacerX on Mon Oct 27, 2014 4:41 pm, edited 1 time in total.


Top
 Profile  
 
PostPosted: Mon Oct 27, 2014 4:38 pm 
Offline
Joined: Fri Jul 21, 2006 11:12 pm
Posts: 1194
Location: SC
RacerX wrote:
Code:
does lsusb show the firefly?
what's the command?

lsusb


Top
 Profile  
 
PostPosted: Mon Oct 27, 2014 4:46 pm 
Offline
Joined: Sun Sep 05, 2004 7:06 pm
Posts: 690
Firefly - some people using Ubuntu use X10 driver instead of ATIUSB

http://ubuntuforums.org/showthread.php?t=639123&page=5

Code:
Bus 003 Device 003: ID 0bc7:0008 X10 Wireless Technology, Inc. Wireless Transceiver (ACPI-compliant)


another thing when my R8.2 FE is off the red led on the firefly receiver is still lit, this is not normal


Top
 Profile  
 

Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 67 posts ] 
Go to page Previous  1, 2, 3, 4, 5  Next



All times are UTC - 6 hours




Who is online

Users browsing this forum: No registered users and 24 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Jump to:  
Powered by phpBB® Forum Software © phpBB Group

Theme Created By ceyhansuyu