What works
←Older revision
Revision as of 21:53, 13 August 2014
(2 intermediate revisions by one user not shown)
Line 22:
Line 22:
===Setup Steps===
===Setup Steps===
*On the Core:
*On the Core:
−
**Install the default pxe kernel package for the Raspberry Pi. (https://dl.dropboxusercontent.com/u/118201886/linux-image-default-raspbian-wheezy_3.10-3-rpi-
lmce2_all
.deb)
+
**Install the default pxe kernel package for the Raspberry Pi. (https://dl.dropboxusercontent.com/u/118201886/linux-image-default-raspbian-wheezy_3.10-3-rpi-
lmce1_all
.deb)
**edit /usr/pluto/bin/Diskless_CreateTBZ.sh to enable "raspbian_armhf" as a TARGET_TYPE
**edit /usr/pluto/bin/Diskless_CreateTBZ.sh to enable "raspbian_armhf" as a TARGET_TYPE
**run /usr/pluto/bin/Diskless_CreateTBZ.sh to create a raspbian tarball
**run /usr/pluto/bin/Diskless_CreateTBZ.sh to create a raspbian tarball
Line 33:
Line 33:
*Power up the Raspberry Pi.
*Power up the Raspberry Pi.
*On first boot the u-boot bootloader will start, it will grab the default pxe kernel/initrd.
*On first boot the u-boot bootloader will start, it will grab the default pxe kernel/initrd.
−
There is a kernel bug that can try to load nfs prior to the network driver. If you encounter a kernel panic then reboot the pi and try again. This will only happen during these first few boots.
*Raspberry Pi will display "Announced ourselves to the router" and the core will run Diskless_Setup to prepare the MD.
*Raspberry Pi will display "Announced ourselves to the router" and the core will run Diskless_Setup to prepare the MD.
*The Raspberry Pi will reboot once Diskless_Setup completes properly.
*The Raspberry Pi will reboot once Diskless_Setup completes properly.
+
*You should go to an existing orbiter and 'Reload the Router' after this point. You will be prompted to do so eventually on the moonPi, if you have not already done so.
*On second boot the bootloader on the sdcard will be updated to the version the MD image is using.
*On second boot the bootloader on the sdcard will be updated to the version the MD image is using.
*The Raspberry Pi will reboot.
*The Raspberry Pi will reboot.
−
*On third boot
you
will be presented with
a terminal login
.
+
*On third boot
LinuxMCE will slowly come to life. Please be patient. You
will be presented with
the Setup Wizard before too long
.
+
===What works===
===What works===
* Embedded phone works on rPi. <del>You'll have to delete /etc/asound.conf. You'll have to set audio to HDMI in webadmin -> Wizard -> Media Director for simplephone to switch to HDMI output.</del>
* Embedded phone works on rPi. <del>You'll have to delete /etc/asound.conf. You'll have to set audio to HDMI in webadmin -> Wizard -> Media Director for simplephone to switch to HDMI output.</del>
+
*omx player (very alpha) may play audio and video after a router reload.
===What does not work===
===What does not work===
−
* Audio playback: xine-player always wants to initialize video, even for audio MP3 files. It fails because it can't initialize 'xv' or 'xshm' video driver.
+
* Video
Overlays
−
* Video
playback: omxplayer integration is in pipeline
+
*
MythTV
−
*
*delete xine player, mplayer, mythtv player devices from your new media director.
+
*
Everything else
.
.. ;
)
−
*
*rm /etc/asound
.
conf
+
−
**omx player (very alpha
)
may play audio and video after a router reload.
+