Author
Topic: PC as Media Director (PXE) (Read 10686 times)

Is there somewhere a good manual/wiki that describe how to setup a media director?Just bought a small and silent motherboard (MSI-E350I1-E45) for my livingroom. No harddisk, only the motherboard and a DVD reader.

In LinuxMCE, i've added a Media Director, inserted the IP and MAC. And waiting till the compilation is done.

When i now boot it PXEboot, everything boots well (in my eyes).But it ends with a login prompt? With the 'hostname': Moon352.I suspected a nice LinuxMCE orbiter screen or simular.

Did i do anything wrong? Or am I missing something?

ps for testing, i'm using a VGA connection instead of the HDMI output. But i suppose that this won't be an issue?

Remove your MD device that you have created, quick reload your router, and just plug the board in. LinuxMCE automatically sets up everything for you, i.e. you do not need to add anything manually beforehand.

I am assuming you did a network install. This is all embedded in the DVD install.

You need to undo whatever you have done and run sudo /usr/pluto/bin/Diskless_CreateTBZ.sh then when you plug your media director in it will create the specific image for that device all automagic like.

The reason I said that it seemed related to networking was "ssh: connect to host dcerouter port 22: Connection timed out" then a bunch of failures to connect to the db on the core. It is not sshing to itself... so I am confused what you are saying is happening.

And when i run /usr/pluto/bin/Di...., it results in an error after a while:

brononius: Is diskless_createtbz.sh finishing or stopping at this error?

This error will not prevent MD creation afaik. This is an error at the time of creation of the mythtv_player within the diskless image chroot creation process. The diskless image in the chroot is trying to contact the mysql server on the dcerouter, it cannot resolve the address. afaik this is normal behaviour during the image creation, at least that is what is has been doing for me and I have no issues. Again, this indicated error should not prevent the MD creation at all. I've added raspbian image generation to this script and I have tested it *many* times here for ubuntu i386 diskless image creation and I have had no issues.

If you add an MD manually it will not have it's /usr/pluto/diskless/XX directory structure created for you automatically. You can manually cause it to be created by selecting the MD in the webadmin and choosing "Rebuild Image". But this should not be necessary, the system should be detecting it automatically.

Side note to L3, diskless_createtbz.sh already creates it's own log file of it's activity and displays the name of the log file when the script starts. log_file=/var/log/pluto/Diskless_MD_Creation_$(date +%Y%m%d_%H%M%S).log

brononius: Is diskless_createtbz.sh finishing or stopping at this error?

I was a bit impatient i think.

The error 'ERROR 2003 (HY000): Can't connect to MySQL server on 'dcerouter' (110)' needed to be about 20 times on my screen, and took about 15 minutes. After that, the installation went one without errors .

The error 'ERROR 2003 (HY000): Can't connect to MySQL server on 'dcerouter' (110)' needed to be about 20 times on my screen, and took about 15 minutes. After that, the installation went one without errors .

I will look at this. It doesn't take that long to fail connecting and continue on my systems but I'll see what its doing and determine if it needs to make the connection or not.