Mike's Blog

Okay, I already went through the install, but did not get any response from the snapstream firefly remote I’m using. The problem has to do with Fedora deprecating lirc_atiusb and now using atilibusb instead.

I tried a few things and now yum upgrade or yum anything won’t even work. It hangs on “Loaded plugins: refresh-packagekit”

I tried a few things to fix that, but can’t fix it. I’m starting a new installation and this time I am documenting everything I do.

1. Doing fresh installation
   1. Did all default options.
2. Fished install and rebooted. Remove DVD so it doesn’t boot to it again.
3. Go through “Welcome” setup screens.
   1. Choose defaults.
   2. Click on “Setup MythTV” which launches the new web browser based installation options.
   3. Choose “A Master backend with frontend” from the dropdown and then choose “process selections”
   4. Under “MythTV User Creation” change the mythtv password and enable the SUDO checkbox option.
4. Turn off the default firewall with this command (to allow remote control with Vino)
   1. chkconfig iptables off
5. Enable remote desktop control with Vino by getting to the desktop (exit mythtv) and then click on the top and clicking at the top “System->Preferences->Internet and network->Remote Desktop”

   

6. Uncheck the option to allow connection and set up the security option to prompt for a password:

   

7. Then you can use uvnc or any other vnc viewer to remote control the desktop using “ip-address:0″ for the connection string (replace “ip-address” with the ip address of the mythdora machine). Yeah!!!
8. Run “yum upgrade mythdora” from the commandline after first booting into it after configuring mythTV for the first time.
   1. I ran “yum upgrade” before finding a page on mythdora.org that said to do “yum upgrade mythdora”. “Yum upgrade” upgrades everything. So, I’ll wait and see what happens. It is normal for it to take a long time before it comes up with the prompt for you to enter “y/n” to proceed with the upgrades that are available.
   2. There were 420 upgrades when I ran it:

      

      It sat for quite a while on “Running Transaction Test” and then again on “Running Transaction”

   3. Then it had 800 transactions to run:

      

    

   Okay, I went through the whole install again because I posted some things to the forum and had the following exchange:

    

   Snapstream firefly

   Submitted by mbrinson on January 24, 2010 – 7:45am.

   I’m having the same problem, but mine is a firefly RF unit. Worked great under MD5.

   I’ve spent hours searching and trying different things, but no joy.

   My model of receiver is R1000-1.

   The thing that’s strange is that when I go to edit /etc/sysconfig/lirc the file is there, but it is completely empty. I tried adding the “–driver=atilibusb” line to it but I get an error when restarting the lircd service: /etc/sysconfig/lirc: line 1: –driver=atilibusb: command not found

   I was very surprised to find that the file /etc/lircd.conf contained a line saying that it was generated by lirc-0.7(lirc_atiusb) or something like that. I have since overwritten the file with the one from here -> http://www.mythtv.org/wiki/Snapstream_Firefly that is generated by lirc-0.8.4a(atilibusb).

   Still when I run lsmod there is no entry for “lirc_atiusb” or for “atilibusb” as I’ve read in other posts should be the case.

   This is a completely fresh installation of MD10.21. I choose all of the default options and chose my remote from the list of options in the browser-based setup. From everyone else’s posts it’s supposed to just work with the defaults so I was surprised that with the default install I was finding the older version in /etc/lircd.conf

   I ran “yum upgrade” after the first run of mythtv and it all seemed to run fine. I got upgraded to .22 for mythtv but I still can not get anything for my remote. I changed the batteries in the remote so they are fresh but I get nothing when running irw and when I try irrecord I get

   “irrecord: could not get file information for /dev/lirc

   irrecord: default_init(): No such file or directory

   irrecord: could not init hardware (lircd running ? –> close it, check permissions)”

   Anyone have any thoughts?

   Thank you so much! Obviously the WAF is very low right now.

    

   What are the contents of
   Submitted by pisani on January 24, 2010 – 8:21am.
   What are the contents of your /etc/sysconfig/lirc file?
   I believe it should read something like this: “LIRCD_OPTIONS=’-H atilibusb’”
   You can also check to make atilibusb is compiled in (if yum upgrade changed your lirc version) at the commandline with lirc -H –help.
   Ryan

    

   My /etc/sysconfig/lirc file

   Submitted by mbrinson on January 24, 2010 – 8:35am.

   My /etc/sysconfig/lirc file is completely empty.

   I ran the lirc -H command and I got “bash: lirc: command not found”

    

   Sorry, I realized it needs

   Submitted by mbrinson on January 24, 2010 – 8:38am.

   Sorry, I realized it needs to be lircd for the command.

   Here’s what I got:

   lircd -H –device=atilibusb

   Driver `–device=atilibusb’ not supported.

   Supported drivers:

   accent

   alsa_usb

   asusdh

   atilibusb

   audio

   audio_alsa

   bte

   bw6130

   commandir

   creative

   creative_infracd

   default

   devinput

   dsp

   dvico

   ea65

   i2cuser

   irlink

   irman

   livedrive_midi

   livedrive_seq

   logitech

   macmini

   mp3anywhere

   mplay

   mouseremote

   mouseremote_ps2

   null

   pcmak

   pinsys

   pixelview

   samsung

   sb0540

   silitek

   tira

   udp

   uirt2

   uirt2_raw

   usb_uirt_raw

   usbx

    

   Okay, obviously I don’t know

   Submitted by mbrinson on January 24, 2010 – 8:48am.

   Okay, obviously I don’t know what I’m doing. Go easy on me.

   I finally found the right syntax and here is the result:

   “lircd -H atilibusb”

   lircd: there seems to already be a lircd process with pid 2024

   lircd: otherwise delete stale lockfile /var/run/lircd.pid

   So I stopped the lircd with “/sbin/service lirc stop” and then ran “lircd -H atilibusb” and then I ran irw and it WORKS!!

   So why wouldn’t this work by default since I used all the default install options for MD10.21?

   More importantly, where do I add this so that it autostarts and is running correctly?

   Thank you so much!!! You are the best!!!!

    

   When you did you install,
   Submitted by pisani on January 24, 2010 – 9:40am.
   When you did you install, did you check the mythdora-updates repo to be active during the install? I think we made a fix for this after the release, and you’d have had to upgraded the mythdora rpm or checked it to update in the installer basically.
   If you missed enabling mythdora-updates it wouldn’t have had the proper fixes when you ran through the setup.
   Also, you could have re-run the infrared device configuration from the mythdora-settings menus.
   Ryan

    

   Thanks for the reply Ryan.

   Submitted by mbrinson on January 24, 2010 – 9:46am.

   Thanks for the reply Ryan. I was afraid to enable any other packages. When you say to enable the mythdora-updates you mean to check that additional repository during the install right?

   I checked a few additional repositories the first time I installed and it said I had some conflicts or something and then I had to re-run the install from the beginning as it errored out with some kind of a bug message.

   I want to be sure I’ve got it set up as stable as possible so if that’s what I need to do then I will re-run the installation from the start and wipe everything out again.

   Thanks again!

    

   No. You don’t need to wipe
   Submitted by pisani on January 24, 2010 – 10:38am.
   No. You don’t need to wipe anything. I was just asking if you did that step or not, which would explain why it didn’t work the first time.
   You should run this from the command line as root however:
   yum upgrade mythdora
   To upgrade to the stable mythdora rpm.
   Ryan

    

   Just to follow up for anyone

   new

   Submitted by mbrinson on January 25, 2010 – 10:34pm.

   Just to follow up for anyone else going down the same road. I went ahead and reinstalled from scratch again and enabled the mythdora-updates package to see if the remote would work by default. It still did not work.

   The key to getting it to work is to copy the updated /etc/lircd.conf file from this wiki page -> http://www.mythtv.org/wiki/Snapstream_Firefly
   

   After copying that into the lircd.conf file then it did work without me having to add the “LIRCD_OPTIONS=’-H atilibusb’” line to the /etc/sysconfig/lirc file. So choosing to enable the mythdora-updates repository must have allowed it to add that line, but somehow it does not enable the correct /etc/lircd.conf file to be included by default.

   Thanks again for the help pisani. You guys are just incredible.

    

   Pasted from http://www.mythdora.com/?q=node/4263#comment-20040
   

    

For errors with “yum install” hanging on “Loaded plugins: refresh-packagekit” the way I was able to get it moving on again was to deactivate a couple of repositories. I went through the gui interface

and unchecked Fedora 10 – i386, Fedora 10 – i386 – Updates, and Livna for Fedora Core 10 – i386 – Base

Then it started working again.

Here’s a cool addon that should be installed for music visualizations:

ProjectM in Fedora 10/11

With Fedora 10 and 11, ProjectM seems to work through libvisual with MythMusic. There’s no need to do any mods, standard Fedora packages (libvisual, libvisual-plugins, projectM-libvisual) seem to work fine!

Pasted from http://www.mythtv.org/wiki/ProjectM

Just “yum install