Difference between revisions of "Sandy Bridge"

From LinuxMCE
Jump to: navigation, search
(initial notes on using Sandybridge based stuff)
 
(Full rewrite after new (successful) tests.)
Line 1: Line 1:
This page contains some notes regarding getting a Sandy Bridge based MD working.
+
Lots of newer mainboards have the Intel Sandy Bridge chipset. There is no out of the box support for it under 1004.
 +
== Add repos, install kernel backport and upgrade ==
 +
The following steps help rectify the problem by utilizing some backport ppas (Shamelessly copied from http://www.subcritical.org/running_ubuntu_lts_on_sandy_bridge/)
 +
apt-add-repository ppa:kernel-ppa/ppa
 +
apt-add-repository ppa:glasen/intel-driver
 +
# the next wasn't needed for my MSI Sandy Bridget board
 +
# apt-add-repository ppa:f-hackenberger/x220-intel-mesa
 +
 +
apt-get update
 +
apt-get install -y linux-image-generic-pae-lts-backport-natty
 +
apt-get dist-upgrade -y
  
After doing a 1004 MD setup, I've changed all Ubuntu Lucid URLs in sources.list to natty and apt-get dist-upgraded, until I no longer had anything missing. Make sure to change the softlink in /tftroot on the core to point to the newest vmlinuz and initrd in the diskless dir.
+
After doing that the backported kernel gets installed, as well as installed packages updated.
 +
== Fixing softlinks and access rights for MDs ==
 +
Changing dcerouter's /tftpboot/<id of MD>/vmlinuz and initrd.img softlinks to the newly installed files, as well as chmod +r those newly installed files, the next boot of the MD resulted in a successful AV Wizard run, as well as VDR HD playback of MPEG4 encoded live TV.
  
The main reason for going natty is the support for the graphics chipset out of the box in natty. BUT, starting the system resulted in not much success. Many times I'd see stuff like:
+
Failing to change the symlinks will result in the MD still using the old kernel.
intel(0): [drm] failed to set drm interface version.
+
  
Playing a bit around the solution was to remove the xserver-xorg-video-vesa and xserver-xorg-video-fbdev - after that X and the Orbiter came up in all their glory.
+
Failing to change the access rights will result in a read error upon PXE boot.

Revision as of 18:49, 18 April 2012

Lots of newer mainboards have the Intel Sandy Bridge chipset. There is no out of the box support for it under 1004.

Add repos, install kernel backport and upgrade

The following steps help rectify the problem by utilizing some backport ppas (Shamelessly copied from http://www.subcritical.org/running_ubuntu_lts_on_sandy_bridge/)

apt-add-repository ppa:kernel-ppa/ppa
apt-add-repository ppa:glasen/intel-driver
# the next wasn't needed for my MSI Sandy Bridget board 
# apt-add-repository ppa:f-hackenberger/x220-intel-mesa 

apt-get update
apt-get install -y linux-image-generic-pae-lts-backport-natty
apt-get dist-upgrade -y

After doing that the backported kernel gets installed, as well as installed packages updated.

Fixing softlinks and access rights for MDs

Changing dcerouter's /tftpboot/<id of MD>/vmlinuz and initrd.img softlinks to the newly installed files, as well as chmod +r those newly installed files, the next boot of the MD resulted in a successful AV Wizard run, as well as VDR HD playback of MPEG4 encoded live TV.

Failing to change the symlinks will result in the MD still using the old kernel.

Failing to change the access rights will result in a read error upon PXE boot.