Topics - rocketlynx

There are many topics on this subject. Many are old and reference several versions of LinuxMCE. This one is in regard to 8.10, as of this writing.

I successfully installed squeezeslave on my core. I know it is successfully installed because I received no errors upon installation and I can access it from outside of my LinuxMCE network by going to http://192.168.0.191:9000 which is the static IP assigned by my router to the core. I can stream music and radio stations from my Window and Mac PCs on my LAN.

Here's the problem...

When I did this part, direct from the Wiki:

Quote

Setting Up LinuxMCE

Next step, manually add the squeezeslave to linuxmce as a squeezebox using the mac address you gave it. The squeezebox player can be assigned to a room/entertainment area without an MD, in fact this would be a typical installation.Select Device

Select Device->A/V Equipment Select SqueezeBox Player from the dropdown options Assign it to a room and entertainment area. Regen your orbiters and reload the router.

Restart the core to make sure it's starting automatically, to run it manually just run the line made in the rc.local

Nothing showed up on the Orbiters under Media or anywhere else. I assumed it was suppose to install a button for a squeezebox player, however, the wiki is not detailed as to what I should expect.

When I installed Hulu it added a button which brings up the Hulu player. What should have occurred? So the squeezeslave is installed and can be accessed from outside the system by other PCs but what about sending media from within LinuxMCE?

I've just updated my 0810 server to 2011-05-30 24012, and I don't seem to have the Flickr screensaver anymore. On my core's orbiter I went to Pictures-->flickr-->my-cores-hard-drive, and I can see the pictures that have been downloaded and exist.

If I select "Play All", this is the error I get on the core's orbiter: "I cannot play this media. Perhaps there is not a valid device in this entertainment area capable of playing it."

My Music and Videos still play correctly but when the Media Director's Orbiter goes to screensaver mode, the screen is just black.

I have edited my sources.list file and did not receive any errors with "sudo apt-get update" or "sudo apt-get upgrade".

After a successful update of the latest 810-Beta-2 release, my Core/Hybrid can still see and play all of my Media (ripped DVD Movies and Music) stored on my (2) 1.5TB drives in my Core, however, after updating my Diskless MD in my Family Room, all works the same except, it no longer can play Movies or Music. It sees all of the media, including the artwork and info, however, when I select any Movie or Music file, it never starts and sometimes I can catch an error in the upper left of the display that says "file not found". I've checked and the libdvdcss2 and w32codecs are still installed. I can even insert a DVD movie or a music CD into the CD-DVD R/W drive in the Media Director and the movie or CD will play correctly as before which proves it's not a libdvdcss or w32codecs problem.

I've tried rebuilding the MD from the Admin and it did not work, I then tried rebuilding the Diskless image on the core and deleting and recreating the MD from scratch and I ended up with the same problem, a Media Directory that can see everything, even my cameras, but still can see all of my Media, just can't start or play anything.

If anyone has had the same problem or has a solution, short of reinstalling the entire Core and system, please help.

After a successful Clean 8.10 - Alpha2.37 Internet install, everything OK as far as the Core is concerned, even a Windows Vista Orbiter working correctly. I then wanted to create my MDs that were working with my previous 8.10 - Alpha2.37 installation without any problems. Upon the first MD's connecting to the DCERouter, the creation ended with a blue screen (of death) and a message that the AVWizard, "Failed to setup X".

A second time yielded the same results. I tried a second Media Director and it also gave the same results. After checking the /etc/X11 directories for the diskless MDs, I found that both had No xorg.conf files created. I watched carefully as each MD tried to reboot from the core and at some point the MD wanted to download and install packages that had to do with the nVidia drivers necessary for each MDs on-motherboard nVidia 8300 display chipset.

Messages going to fast to write all information correctly, I saw time out failures from "archive.ubuntu.org, deb.linux.org, etc., all dealing, apparently with the glx-180-pluto-nvidia-video-drivers necessary form the diskless MDs.

These same drivers downloaded and installed correctly for the core just yesterday.

Is the source list for the diskless creation of MDs incorrect or different from the core's basic install script source list? These same MDs have been working and installable from my previous Alpha2.37 system of which had been built on about Alpha2.19 and constantly upgraded to and included Alpha2.37. Never a problem before!

The only reason for the re-install was to utilize a new much larger and much needed OS hard drive, rather than the small one the system was originally installed on.

All of the hardware is the same. The core's PC is the same! The MDs are the same! The only thing that is different is LinuxMCE's current installation files or Ubuntu's installation repos and archives but I believe there must be a bad source list for the MD creation default image.

Does anybody have a referrence, correct source list for the MDs, or is the problem somewhere else?

i am told that all of the startup script issues have been fixed in svn and will be in the next beta release.

Possy fixed the scripts and they are now part of the internet-only installation. There is still a small bug with the photo screen saver, but everything else seems to work REALLY well! I wiped my core again and used the download installer then unchecked the photo screensaver from the media director software edit screen, used the nvidia-glx-190 drivers, and an xorg.conf that includes the busid of my video card; now mostly everything is peachy.

Thanks Possy!

First of all, I'm not picking on the above author's quote I'm just using it as an example. I've been using LinuxMCE since January of this year. The question I have because I don't really know how the routine "commited the fix to SVN" or "Will be in the next release" really works, when there is a real confusing/crippling error introduced into an already correctly running module with a scheduled alpha2 release, can an interim release such as, Alpha2.36.1 be released to fix the one or two majors problems introduced by it's predecessor?

To be a little more clear, I see many new LinuxMCE users stumbling with simple problems that seasoned LinuxMCE veterans understand work-arounds, and can live with the issue until the next scheduled Alpha2 release, but the newer users fight with them on each Core reboot or new installation hickups, on a regular basis. Examples: the Core's double Orbiter launch, and now, other launch script errors.

On these problems, it seemed that there was a recognition and fix at some point in time but had to wait until the next scheduled release maybe one, two or three weeks later. This discourages many new users from continuing their pursuit of involvment with LinuxMCE and I believe the more people we can keep encourged and joining the ranks as continued users can help to provide more contributions to better the system for the long haul.

Now, don't get me wrong, this is not a complaint, and I'm not meaning to release many small snafus or hickups all of the time, I completely understand "Open Source Software" and that LinuxMCE is a "Constantly evolving feature-rich program", I'm only referring to the most annoying or serious of them such as the previously mentioned "Orbiter will be closed" message and the "installation script problems", these are the ones that really put a damper on the shining light features of LinuxMCE.

In Summation: Can a serious problem introduced in a release that is a real necessary core function , that worked correctly previous to this release, and is detrimental to "booting" the Core Computer correctly or for the basic installation of the basic core functions, be released in a (for example:) Alpha2.36.1 or in the next scheduled release, bumping the others one more release down?

Don't Slam me for this, I only want an answer and to understand the process for what determines the critical from the non-critical releases.

OK, I have not reinstalled my Core. I've only upgraded to the latest 8.10 update, alpha2.37. Everything on the system seemed ok until I tried to setup a new MD.

First I was trying to set up a new ASUS 330 ION board. It announced itself to the router, assigned a permanent IP and device number and then I kept getting the message "Diskless Setup failed" after approximately 15 to 20 minutes after the the "Running Diskless_Setup.sh" began on the new MD. Each time I tried, it created a MD in WebAdmin and an Orbiter was assigned. If I rebooted, the process just repeated itself.

I just thought it was a snafu with the new ION board I was trying. I then tried to setup another new MD using a another new ASUS M3N78-EM exactly like one I already have a have been using for quite a while, and the same thing happened. I rebooted reloaded the router and retried and got the same error. I rebooted the Core and got the same problem. This exact MOBO was no problem on 810 many updates before so I know it must be an update that stuck it to me.

I've just got rid of the 'Orbiter will be closed" crap with the last update and thought things were good on the core and now this. Has the core's diskless default image been damaged with a recent update?

Good Morning from Houston, Texas. Hi Folks, I'm Charles Triola (rocketlynx) on the Forum, and I'm setting up my HADesigner for Orbiter Mods and General Support. I've had experience over the years on program design, web design and general menu layouts using HTML, PHP and some "C" so I want to get myself familiar with HADesigner as fast as I can. I've gone through the wiki pages, forum posts and videos, but I'm having trouble right at the start, mysql connecting.

First, I'm using my laptop running 32bit Vista. Has this been successfully done on Vista or do I need XP. My Laptop is on the Core's Internal LAN, it sees the Windows PC and I see the DCERouter. I have an assigned IP of 192.168.80.247 from the DCERouter on the Vista PC.

Upon clicking the Test Button, I get a "MYODBCConfig" popup window with the info: Request Returned With SQL_ERROR.In looking at the Diagonostics window, I get a message: [MySQL][ODBC 3.5.1 Driver]Access denied for user 'charles'@'192.168.80.247' (using password: YES)

I know I'm close because if I change the Server name from dcerouter or the database name from pluto_main, I get different errors and right now, I must be hitting the MySQL server and am just being denied access.

Is the wiki correct for LinuxMCE 8.10-Alpha2-Latest? Is ther anyone with any suggestions?

For some time now, for many of us, the Core Media Director's Orbiter has been a real "Pain in the you know what" and, so far, no one seems to have a handle on it.

I don't need the Core's Orbiter because my Core sits in a closet, not connected to anything more than a VGA monitor, not needing the Media Director's functions. I've asked this question before and got no responses.

How do I modify the start procedure to start the Core ONLY! The Alpha2.36 stated under one of it's updates, (lmce-launch-manager (298,299)) "Fixing startup mode for running core only", so, How do you do it?

First off, Thanks to all who have helped me in the past with LinuxMCE. This is not to be taken as a Wiki bashing, just an attempt to clarify, get my Squeezeslave working and maybe to correct the wiki if necessary.

1. I'm running LinuxMCE 810 Alpha2.31 on a Pentium IV Core

2. Everything else seems to be working fine

3. I have successfully added a second sound card in a PCI slot (non-interfering with the Core MB's Sound)

4. I have verified the second sound card with alsamixer - OK and lspci - OK

5. I am using the binary from squeezeslave-0.9-65-lnx26-alsa-display-i686.tar.gz

6. I have followed the wiki and forum posts as much as I can - This is where the problems began

I put the squeezeslave binary in "/usr/local/bin" as per the wiki. Here's my /etc/rc.local file:

Quote

#!/bin/sh -e## rc.local## This script is executed at the end of each multiuser runlevel.# Make sure that the script will "exit 0" on success or any other# value on error.## In order to enable or disable this script just change the execution# bits.## By default this script does nothing./usr/local/bin/squeezeslave -m 00:00:00:00:00:01 -o 1 -s -r &exit 0

Next, I set up LinuxMCE as per the wiki. I now have a slimserver device #106 under the Core, and a child device #105, the Squeezebox Player. The Squeezebox Player has the IP of the core, "192.168.80.1" and the matching MAC ID of "00:00:00:00:00:01".

The slimserver has NO IP address nor a MAC ID, as it was not mentioned to enter that in the wiki or the forum posts.

The next thing I did was create and customize the startup script "/etc/init.d/squeezeslave". Here is the customized area:

Quote

# PATH should only include /usr/* if it runs after the mountnfs.sh scriptPATH=/usr/sbin:/usr/bin:/sbin:/binDESC="Squeezeslave dameon"NAME=squeezeslaveDAEMON= /usr/local/bin/squeezeslaveDAEMON_ARGS="-o 1 -m 00:00:00:00:00:01 -r 3 -s 192.168.80.1"PIDFILE=/var/run/$NAME.pidSCRIPTNAME=/etc/init.d/$NAME

I then made the script executable with "chmod +x /etc/init.d/squeezeslave". No sudo at the beginning of the command because I'm already logged in as superuser in the Konsola. I verified tha the script is now executable - OK,

This is where it all went South - I tried the following with the following results:

This product, of which is available from HACS http://www.hacs.com, has been talked about and referenced in several different posts on the Forum but never addressed directly so I'm throwing it up to see if it sticks.

It appears that the integration of this product and it's use was a custom template and configuration file contributed by Bulek for LinuxMCE 710 that may not be included in LinuxMCE 810-Alpha2 because I've looked through the Alpha2 templates and I can't seem to locate it. Is this the case?

Also, are there any Orbiter Screenshots of how the ESS speaker zones are accessed and the 11 volume levels are selected from the Orbiter?

I guess the main question is: How much is the HACS ESS system implemented in LinuxMCE. If you use a local volume control at the zone the speakers are located in, and raise or lower the volume manually, is there feedback to the Orbiter to see the current volume level for that zone as changed by hand at the speaker location (stated - 11 levels of volume per zone).

Since this product is a bit on the expensive side, I can't just invest $400.00 to $600.00 bucks (because of the number of zones I need) to play with it. I would like to know if it is fully integrated or, at least, something that I can finish up on the integration and implementation of myself if it leans closer to the most probable side.

The screenshots would help if someone already has this installed and working, and can be taken from an Orbiter, displaying the ESS Speaker Zone Controls.

I would like to open up this topic to get feedback regarding an installation of Squeezeslave on a dedicated or conveniently located Media Director rather than an instance of Squeezeslave located in the Core. The reason I'm asking these questions is because I'm getting rather selfish with my 810 Alpha2-Latest (alpha2.29) running quite reliably and hate to start experimenting on the Core of which, at times, can break a otherwise daily, functioning, system that the family is using.

Setting a spare computer up as a diskless Media Director to test and run Squeezeslave is much more easy and appealing considering the above statement.

If Squeezeslave can be sucessfull on a MD vs. on the Core, does this relieve the Core of unnecessary duties and processing responsibilities since the MD is now servicing Squeezeslave processes?

Does the Media Director still need two sound cards, an additional one for each instance of Squeezeslave?

Understanding that the MD is doing the Squeezeslave processing, is there still a lot of harddrive activity on the Core due to the fact that the MD is Diskless, and then, does this become senseless, meaning that it might as well remain installed on the Core?

Also, there is only a Wiki page for Squeezeslave on the Core and not one for Squeezeslave on a Media Director, is that to say this is how it should be done or should there be another wiki for On-The-MD?

I know this may be redundant for some that have been there before, but I am just trying to centralize this information for those that are considering Squeezeslave for the first time, and want a clear understanding of what the options are before starting.

After reinstalling LinuxMCE 810 Alpha2-Latest on my Core, in LinuxMCE Admin, "Admin --> Files & Media --> Media Files Sync" does not list my existing (sdb1) data drive containing my Media previously ripped, so that editing/updating of Media can be done. The Audio and Video files (CDs and Movies) are still present and can be accessed from any Orbiter and played on all Media Directors as before, however, since the drive no longer shows up in "Admin --> Files & Media --> Media Files Sync", they cannot be accessed to correct cover art and titles and obtaining missing information from Amazon and IMDB as previously done.

The drive, "ST31500341AS (sdb1)-CORE", is listed under : "Admin --> Show Device Tree --> My Devices --> Core", which brings up the template #1790, as it did before.

How can this be corrected? Is this possibly a new Alpha2-latest bug surfacing, or is this to be expected when reinstalling the Core/Hybrid and re-attaching an existing data drive with media from another installation?

I was running LinuxMCE 810 Alpha2.24 prior and reinstalled the core with the latest, Alpha2.26.

First off, I have read the wiki topic: Squeezeslave on the core, http://wiki.linuxmce.org/index.php/Squeezeslave_on_the_core and I have searched the forum for these definitive answers. But I would like to completely understand the correct answers before implementing this on my working Core. In other words, I have no problem manually installing and getting it to work using the information from the Wiki and the Forum but I would like to know with my Core's present version: LinuxMCE Alpha2.25 if it has been done or shouldn't be done because it is an Alpha version and not 710, which is stable.

Here are the questions:

Is Squeezeslave a totally standalone software implementation of Squeezebox, not needing anything else but an additional sound card for each instance?

Has this ever been tried or successfully acheived on LinuxMCE 810 Alpha2 or just recommended for LinuxMCE 710, stable?

Using an extra LinuxMCE compatible PCI sound card, is there anything that should be done before or after installation and rebooting the Core to keep the new, second, PCI sound card from interfearing with the first (primary) sound card?

This may have been answered by the first question. For clarification, the Wiki link for downloading Squeezeslave: http://sourceforge.net/projects/softsqueeze/files/ takes you to a page under Softsqueeze. Is Squeezeslave part of, comes with, or needing Softsqueeze to operate on the Core?

Again, I would not have asked these questions if I would have found the answers in the Wiki or Forum.

In order for anyone to support me, I will try to give as much detail as I possibly can.

I have an 810 Alpha2-Latest Core that apparently has a Core Boot Drive (sda1) that has become corrupt while working. The system has been up and working without any problems for about 2 months. It is running Alpha2.24, up until now, without any glitches.

I went to my windows vista orbiter and up popped "A new Hard Drive has been found, do you want to use it?" Seeing that it was referring to my Core's primary hard drive (sda1), I knew something was screwed up. I then went to the core and the onscreen orbiter was displaying the same message and running painfully, painfully slow. Not knowing the consequences of any relpy, I selected on the orbiter, Admin, restart the core and after the orbiter took it's slow running self it said restarting the Core. After the Core shut down and restarted there was the A/V Wizard. Oh Crap, now I knew I was in trouble.

The Core now has NO Orbiter, that can be found, and just a blank screen with an arrow cursor after Kubuntu 810 starts and LinuxMCE begins to Init. No Media Directors, Windows Orbiters or my WebDT 366 can properly and completely boot from the core. There are NO Internal Network problems causing this (verified). DCERouter is running because my primary Diskless Media Director sees the Core and begins to boot all the way to Orbiter time and then ends up with the same blank screen with an arrow cursor.

Before going to the blank screen w/cursor, I managed to catch the media director finishing it's boot from the core, quickly saying, Error - Unable to connect to the MYSQL server. Evidently the Diskless Image, on the Core, can be found or the MD would not have gotten that far.

The only clue I have as to what possibly might have happened is my family was watching a movies on the MD and told me that a Blue-Screen Message popped up and said, the disk drive was full or getting full. I wasn't home so I do not have more precise error message info.

I need to try and trap the Core while booting and get to a console or KDE Desktop, to see what's going on with the Core's Boot Drive (sda1).

How do I let Kubuntu boot and stop LinuxMCE from starting on the Core? Are there any control key combinations I can use?

Any help would be greatly appreciated as I'm trying to avoid a complete re-installation as I have several camera logs on the primary drive, and the loss of about 190 DVD movies on (sdb1), a 1.5T drive, would be catastropic.