Difference between revisions of "Generic PC"
Perspectoff (Talk | contribs) |
Perspectoff (Talk | contribs) |
||
| Line 8: | Line 8: | ||
<strong>Hardware</strong> | <strong>Hardware</strong> | ||
| − | + | Basic Hardware Requirements: Processor, RAM | |
| − | + | ||
| − | + | For use of the Media Director PC in a HomeTheater PC setting, a Celeron processor with 512Mb RAM is usually sufficient. | |
| − | For use of the Media Director PC in a HomeTheater PC setting, a Celeron processor with 512Mb RAM is usually | + | |
| − | + | Any generic PC can be used as an MD. There are a couple of recommendations, however. Most important is that the PC is quiet (i.e. quiet fans or no fans) yet has a low heat emission. Since it will be next to your TV, you don't want noisy fans disturbing your TV-watching. | |
| − | + | The PC used should be able to support PXE, so that it can boot over the LAN network from the tftp (Core) server. LinuxMCE allows either the PC used as a Media Directors to boot its own installation of LinuxMCE or to boot from the LAN network from the Core. A network boot is easiest, however. Obviously, the PC would then have to be network boot capable (as are most modern PCs). | |
| + | |||
| + | The video adapter used in the Media Director PC can also be an issue. I tried to setup MD with an S3 Trio 64+ video card but without luck -- during the bootup of the Media Director PC, when X started up, the monitor turned off. After replacing the video adapter card (an nVidia card is usually recommended), it worked correctly. | ||
| − | |||
| − | + | <strong>Setup of the Media Director</strong> | |
| − | + | It is easiest to allow the PC which will serve as the Media Director to start from a network boot, as mentioned above, from the Core server. Make sure the BIOS is set for network boot. That way, every time you turn on your Media Director PC, it will boot from the Core server on the network automatically. | |
| + | |||
| + | The first time you connect a Media Director PC to the network, the LinuxMCE Core should auto detect it. You will then see the network boot commence on the screen of the machine you are adding. After a short time you will see a message in yellow text, stating that this machine has been "announced" on the Core. Go to the Orbiter with the 'Add Media Director' screen displayed and you will see a screen asking if you would like to add your PC as a Media Director. If you choose "Add as Generic PC" (which currently is the only device type choice) then LinuxMCE will start the process of adding your PC. The process of adding a PC to LinuxMCE takes at least 20 mins., depending on the speed of your Core, whatever other tasks it is performing at the time, and your network LAN speed. | ||
| + | |||
| + | The alternative manual process, which is described below, should no longer be required. In fact, it can cause problems with the auto detection process, so is not recommended. The auto-detection process is always looking for new hardware, and it can get confused when a new Media Director machine is added manually. | ||
| + | |||
| + | Manual Setup of a Media Director | ||
| + | |||
| + | Add a new MD in the LinuxMCE-admin site: Go to Wizard --> Devices --> Media Directors. On the MD page press the button 'Add device'. In the new window chose 'Generic PC as MD' and press the button 'Add device'. After that you will see a message about preparation a data for new device. It can take 2-4 minutes. When setup procedure of the MD is finished you'll see a message on all active Orbiters that new device is configured and ready to use. The field 'IP Address' should contain IP address given by DHCP server. This IP will be assigned to PC when it starts to boot. Type MAC Address of your PC in the field 'MAC Address' (it'll be displayed when PC tries to boot from network). Now it's time to prepare ISO for new diskless MD. To do that just press the button 'Setup Diskless Media Directors' and wait till operation will finish (you'll see a log output to the web page): | ||
<div align="center"> | <div align="center"> | ||
| Line 28: | Line 35: | ||
([http://www.flickr.com/photos/stepanov/135424562/ click to enlarge]) | ([http://www.flickr.com/photos/stepanov/135424562/ click to enlarge]) | ||
</div> | </div> | ||
| − | Quick reload the router and boot MD. In my case (I have 64bit Core/Hybrid and 32bit MD) it took about 2 hours. | + | Quick reload the router and boot MD. In my case (I have a 64bit Core/Hybrid and a 32bit MD) it took about 2 hours. |
<strong>Troubleshooting</strong> | <strong>Troubleshooting</strong> | ||
<u>Problem:</u> Diskless MD cannot find ISO. | <u>Problem:</u> Diskless MD cannot find ISO. | ||
| − | <u>Solution:</u> It's possible that DHCP | + | <u>Solution:</u> It's possible that the Core DHCP assigns an IP address which is different from the IP address listed in the MD properties. Change the IP manually (you can find the assigned IP in the /var/log/pluto/PlutoDHCP.newlog), then press 'Setup Diskless' button. Wait while the setup finishes and for the quick reload of the router. |
<u>Problem:</u> Display of MD goes down after boot. | <u>Problem:</u> Display of MD goes down after boot. | ||
| − | <u>Solution:</u> Something wrong with MD video adapter. As I mentioned above I had the same problem with S3 Trio 64+. When I replaced it | + | <u>Solution:</u> Something is likely wrong with your MD video adapter card. As I mentioned above I had the same problem with my S3 Trio 64+ card. When I replaced it (nVidia recommended) the on-screen Orbiter for the MD loaded successful. |
Revision as of 01:17, 25 April 2008
Preface
When you use LinuxMCE and you have more than one entertainment area in your home, you have to setup a separate Media Director (MD) for each area. The main function of a Media Director (MD) is both the management of multimedia content (such as Live TV, DVD, and photos) and the display of that content on the TV. An MD has a built-in onScreen Orbiter. You can control your home using it, if you connect a monitor with touch-screen to it. (However, I'm not sure if it is possible to watch TV and display the Orbiter at the same time.)
Hardware
Basic Hardware Requirements: Processor, RAM
For use of the Media Director PC in a HomeTheater PC setting, a Celeron processor with 512Mb RAM is usually sufficient.
Any generic PC can be used as an MD. There are a couple of recommendations, however. Most important is that the PC is quiet (i.e. quiet fans or no fans) yet has a low heat emission. Since it will be next to your TV, you don't want noisy fans disturbing your TV-watching.
The PC used should be able to support PXE, so that it can boot over the LAN network from the tftp (Core) server. LinuxMCE allows either the PC used as a Media Directors to boot its own installation of LinuxMCE or to boot from the LAN network from the Core. A network boot is easiest, however. Obviously, the PC would then have to be network boot capable (as are most modern PCs).
The video adapter used in the Media Director PC can also be an issue. I tried to setup MD with an S3 Trio 64+ video card but without luck -- during the bootup of the Media Director PC, when X started up, the monitor turned off. After replacing the video adapter card (an nVidia card is usually recommended), it worked correctly.
Setup of the Media Director
It is easiest to allow the PC which will serve as the Media Director to start from a network boot, as mentioned above, from the Core server. Make sure the BIOS is set for network boot. That way, every time you turn on your Media Director PC, it will boot from the Core server on the network automatically.
The first time you connect a Media Director PC to the network, the LinuxMCE Core should auto detect it. You will then see the network boot commence on the screen of the machine you are adding. After a short time you will see a message in yellow text, stating that this machine has been "announced" on the Core. Go to the Orbiter with the 'Add Media Director' screen displayed and you will see a screen asking if you would like to add your PC as a Media Director. If you choose "Add as Generic PC" (which currently is the only device type choice) then LinuxMCE will start the process of adding your PC. The process of adding a PC to LinuxMCE takes at least 20 mins., depending on the speed of your Core, whatever other tasks it is performing at the time, and your network LAN speed.
The alternative manual process, which is described below, should no longer be required. In fact, it can cause problems with the auto detection process, so is not recommended. The auto-detection process is always looking for new hardware, and it can get confused when a new Media Director machine is added manually.
Manual Setup of a Media Director
Add a new MD in the LinuxMCE-admin site: Go to Wizard --> Devices --> Media Directors. On the MD page press the button 'Add device'. In the new window chose 'Generic PC as MD' and press the button 'Add device'. After that you will see a message about preparation a data for new device. It can take 2-4 minutes. When setup procedure of the MD is finished you'll see a message on all active Orbiters that new device is configured and ready to use. The field 'IP Address' should contain IP address given by DHCP server. This IP will be assigned to PC when it starts to boot. Type MAC Address of your PC in the field 'MAC Address' (it'll be displayed when PC tries to boot from network). Now it's time to prepare ISO for new diskless MD. To do that just press the button 'Setup Diskless Media Directors' and wait till operation will finish (you'll see a log output to the web page):
Quick reload the router and boot MD. In my case (I have a 64bit Core/Hybrid and a 32bit MD) it took about 2 hours.
Troubleshooting
Problem: Diskless MD cannot find ISO. Solution: It's possible that the Core DHCP assigns an IP address which is different from the IP address listed in the MD properties. Change the IP manually (you can find the assigned IP in the /var/log/pluto/PlutoDHCP.newlog), then press 'Setup Diskless' button. Wait while the setup finishes and for the quick reload of the router.
Problem: Display of MD goes down after boot. Solution: Something is likely wrong with your MD video adapter card. As I mentioned above I had the same problem with my S3 Trio 64+ card. When I replaced it (nVidia recommended) the on-screen Orbiter for the MD loaded successful.
