2012-06-13, 02:04
I spent quite a bit of time getting the system up and running. My goal was to setup XBMC Eden with an internal SSD on a LAN. Hopefully this will help others with setup problems. Thanks to the following guide which I adapted to this setup: Shuttle XS35GT: Installing XBMC 10.0 Live (Dharma)
And to the XBMC forums which provided the missing pieces!
1 - Hardware Needed
2 - Additional Hardware required for install
3 - Software Needed
4 - Assemble the hardware
5 - Install Latest Bios on Shuttle XS35GTV2
6 - Setup XBMC Eden on the USB Drive
7 - Bios Settings to change
8 - Install XBMCBuntu Eden
9 - Enable HDMI Audio
After XBMC has booted:
10 - Enable Suspend/Wake from remote
In section seven we have have already enabled wake on S3 in the bios. So we just need to install the right packages and configure rc.local
11 - Fix video skip/freeze problem every few minutes
This is caused by the wireless libraries, took me ages to figure it out. As I am using a LAN only I just disabled them using the blacklist:
12 - Fix for remote not responding when XBMC screen darkens
I had a problem whereby everytime the screen darkened (in the menu system or when a video was paused) the remote would stop working and light on the IR Receiver would stay on permanently. If I then pressed a key on the keyboard or changed the output source on the TV it would come back.
I was setting up two shuttles, one for upstairs and the other for downstairs. It turns out that one of the TVs was the problem (or is affected more often). The TV upstairs will work most of the time without issues and the one downstairs will have the problem all the time. I don't really understand how HDMI can affect the IR receiver but this is definitely what happens. I have swapped the units a number of times and the results are always the same. Both TVs are Philips, upstairs I have a 32PFL3605H/12 (works most of the time) and downstairs I have a 42PFL5603D/12 (does not work). The workaround I use currently is to change the output source on the TV to get the remote to respond again.
For anyone else who has this problem there is a permanent workaround. You can stop using LIRC and use the linux kernel (ir-keytable) to process remote signals as keyboard presses (I've verified that this always works so LIRC appears to have a part to play with the issue). There are many guides around on how to this if you want to go down this road but be warned setting this up will take some time.
If anyone knows why LIRC or my IR Receiver (SMK RXX6000-0141E) seems to be incompatible with my TV I'd be interested to find out. Maybe it's just a strange bug...
13 - Fix for gigabit networking issue
http://forum.xbmc.org/showthread.php?tid...pid1060878
This should not longer be a problem from Eden onwards as the correct driver should be included in the kernel.
14 - Known Issues
That's it!
And to the XBMC forums which provided the missing pieces!
- Hardware Needed
- Additional Hardware required for install
- Software Needed
- Assemble the hardware
- Install Latest Bios on Shuttle XS35GTV2
- Setup XBMC Eden on the USB Drive
- Bios Settings to change
- Install XBMCBuntu Eden
- Enable HDMI Audio
- Enable Suspend/Wake from remote
- Fix video skip/freeze problem every few minutes
- Fix for remote not responding when XBMC screen darkens (not really a fix yet!)
- Fix for gigabit networking issue
- Known Issues
1 - Hardware Needed
- 1x Shuttle XS35GTV2
- 1x Hauppauge Media Centre Control Kit
- 1x Crucial M4 64GB SSD
- 1x Crucial 4GB 204 PIN SODIMM DDR3 PC3-8500 CL7
- 1x HDMI Cable
2 - Additional Hardware required for install
- 1x USB keyboard
- 1x USB drive
3 - Software Needed
4 - Assemble the hardware
- Open the shuttle as per the instruction manual and install the memory and SSD, close once complete
- Connect the shuttle to your TV using the HDMI cable
- Attach the IR receiver to the USB port just above the capped VGA cable
- Attach the keyboard to the shuttle (any USB port)
- Attach an ethernet cable to the shuttle
- Connect the power to the shuttle
5 - Install Latest Bios on Shuttle XS35GTV2
- Format the USB memory stick as a FAT32 device using Windows or whatever
- Use UNetBootin to install FREEDOS 1.0 to the USB memory stick
- Copy the ‘Dos’ directory from the bios zip file onto the USB memory stick
- Plug the keyboard and the USB Drive into the XS35GTV2
- Start the shuttle and hit "del" when prompted to enter the bios
- Choose the USB Drive as the primary boot device in the "boot" menu and save and exit the bios (This will then boot to the USB Drive)
- Select FREEDOS Live (don’t accept the default which is to install to hard drive)
- From the DOS command line, type ‘C:’ and hit enter key, and then cd into the ‘Dos’ directory where the BIOS files are (e.g. cd Dos)
- Type ‘flash’ and hit enter
- Be sure to wait until the flashing of the BIOS has completed (don’t interrupt it or the XS35GTV2 is probably toast)
6 - Setup XBMC Eden on the USB Drive
- Format the USB memory stick as a FAT32 device using Windows or whatever
- Use UNetBootin to install the disk image for XBMCBuntu (xbmcbuntu-11.0.iso) to the USB Drive
- Insert the USB Drive back into the shuttle
7 - Bios Settings to change
- Start the shuttle and hit "del" when prompted to enter the bios
- Main menu: Configure Sata as AHCI
- Advanced Menu: Change "USB Device Wakeup From S3" to enabled (this is needed for Wake from Suspend later on)
- Boot Menu: Select the USB Drive as the primary boot device and the SSD as the secondary
- Save and exit the BIOS (this will start the XBMCBuntu installation)
8 - Install XBMCBuntu Eden
- Select XBMC install from the UNetBootin grub menu that appears
- Follow the menus that appear, you'll be asked to specify, country, language, keyboard type etc.
- Once you reach the drive/partition setup screens just choose "Use whole drive".
- On the user create screen I created a user called "xbmc" with the same as the password
- When the installation finishes, remove the USB drive and hit continue to reboot. Done!
9 - Enable HDMI Audio
After XBMC has booted:
- Ctrl+Alt+F1 to switch to a terminal and log in with the user/pass you created in the install
- Run the "alsamixer"command
- Hit F6 to select the soundcard in use and select "HDA NVidia"
- Hit "m" to unmute the s/pdif output (You'll see 00 appear in the centre of the screen)
- "Esc" to exit
- Run "aplay -l", You'll see output like this, take a note of the card number and device number for the NVidia card:
Code:**** List of PLAYBACK Hardware Devices ****
card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0 - Ctrl+Alt+F7 to switch back to XBMC
- Go to "System->System->Audio output"
- Choose HDMI as the Audio Output, and whatever speaker config you have (I left this as 2.0)
- Select "Custom" for Audio output device and enter "plughw:1,3" for the Custom audio device (the 1,3 represents the card 1 device 3 from step 6)
- Select "Custom" for Passthrough output device and enter "plughw:1,3" for the Custom passthrough device (the 1,3 represents the card 1 device 3 from step 6)
- Done!
10 - Enable Suspend/Wake from remote
In section seven we have have already enabled wake on S3 in the bios. So we just need to install the right packages and configure rc.local
- Ctrl+Alt+F1 to switch to a terminal and log in with the user/pass you created in the install
- Run the following command to install the required packages:
Code:sudo apt-get install policykit-1 upower acpi-support
- Run the following command to get the IR device ID:
Code:dmesg | grep "mceusb [0-9]-[0-9]" | awk '{print $4}' | awk -F: '{print $1}'
- Take a note of the output of the previous command, it should be in the format [0-9]-[0-9], in my case it was 5-2
- Now edit rc.local
Code:sudo vi /etc/rc.local
- Insert the following lines before the "exit 0" line (take care to substitute the result from the previous command on the last line):
Code:#
# Enable wakeup on the USB Ports
#
# I move the HTPC around a lot so I just enable all ports for wakeup
#
echo USB0 > /proc/acpi/wakeup
echo USB1 > /proc/acpi/wakeup
echo USB2 > /proc/acpi/wakeup
echo USB3 > /proc/acpi/wakeup
#
# Next we need to enable the IR receiver as a wake device
#
sh -c 'echo enabled' > /sys/bus/usb/devices/5-2/power/wakeup
- Save the file. Done!
- Ctrl+Alt+F7 to switch back to XBMC
11 - Fix video skip/freeze problem every few minutes
This is caused by the wireless libraries, took me ages to figure it out. As I am using a LAN only I just disabled them using the blacklist:
- Ctrl+Alt+F1 to switch to a terminal and log in with the user/pass you created in the install
- Now create a balcklist file fot the wifi
Code:sudo vi /etc/modprobe.d/blacklist-wifi.conf
- And add the following content:
Code:# The wifi can cuase problems with Video playback. I don't use it so scrap it
blacklist rtl8192ce
blacklist rtl8192c_common - Save the file. Done!
- Ctrl+Alt+F7 to switch back to XBMC
12 - Fix for remote not responding when XBMC screen darkens
I had a problem whereby everytime the screen darkened (in the menu system or when a video was paused) the remote would stop working and light on the IR Receiver would stay on permanently. If I then pressed a key on the keyboard or changed the output source on the TV it would come back.
I was setting up two shuttles, one for upstairs and the other for downstairs. It turns out that one of the TVs was the problem (or is affected more often). The TV upstairs will work most of the time without issues and the one downstairs will have the problem all the time. I don't really understand how HDMI can affect the IR receiver but this is definitely what happens. I have swapped the units a number of times and the results are always the same. Both TVs are Philips, upstairs I have a 32PFL3605H/12 (works most of the time) and downstairs I have a 42PFL5603D/12 (does not work). The workaround I use currently is to change the output source on the TV to get the remote to respond again.
For anyone else who has this problem there is a permanent workaround. You can stop using LIRC and use the linux kernel (ir-keytable) to process remote signals as keyboard presses (I've verified that this always works so LIRC appears to have a part to play with the issue). There are many guides around on how to this if you want to go down this road but be warned setting this up will take some time.
If anyone knows why LIRC or my IR Receiver (SMK RXX6000-0141E) seems to be incompatible with my TV I'd be interested to find out. Maybe it's just a strange bug...
13 - Fix for gigabit networking issue
http://forum.xbmc.org/showthread.php?tid...pid1060878
This should not longer be a problem from Eden onwards as the correct driver should be included in the kernel.
14 - Known Issues
- No sound on menus - Don't really mind, if someones know how to fix this let me and I'll update the guide but we might just have to wait for the new audio engine in V12!
That's it!