RaspberryPi - Revision history

Phenigma at 19:53, 27 March 2018

2018-03-27T19:53:37Z

←Older revision		Revision as of 19:53, 27 March 2018
Line 3:		Line 3:
	[[Category: Barebones]]		[[Category: Barebones]]
	qMDs are still a thing of myth, although seen occasionally in the wild they are elusive and not easily tamed. ;)		qMDs are still a thing of myth, although seen occasionally in the wild they are elusive and not easily tamed. ;)

			Note: The Raspberry Pi 3 B+ is not yet compatible with LMCE.

	=Device Specification=		=Device Specification=

Marie.o: /* Requirements */

2017-04-11T18:42:24Z

Requirements

←Older revision		Revision as of 18:42, 11 April 2017
Line 47:		Line 47:
	** The Raspberry Pi will detect the boot resolution of your display and adjust itself accordingly.		** The Raspberry Pi will detect the boot resolution of your display and adjust itself accordingly.
	** If resolution has changed since the last boot the orbiter will be regenerated.		** If resolution has changed since the last boot the orbiter will be regenerated.
	* You may wish to have a usb keyboard or mouse for orbiter interaction. USB-UIRT/MCE Remote is also possible.		* You may wish to have a usb keyboard or mouse for orbiter interaction. USB-UIRT/MCE Remote is also possible. HDMI-CEC works as well, if your TV or connected amp supports it.

	==Setup Steps==		==Setup Steps==

Phenigma at 18:28, 23 September 2016

2016-09-23T18:28:57Z

←Older revision		Revision as of 18:28, 23 September 2016
Line 51:		Line 51:
	==Setup Steps==		==Setup Steps==
	*On the Core:		*On the Core:
	**Install the [http://download.linuxmce.org/linux-image-default-raspbian-jessie_4.4.15-v7+-~~lmce4_all~~.deb default netboot kernel package] for a Raspberry PiB 1/2/3 MD. This image will permit you to select from multiple possible RPi Device Templates. These include: RPi MD (DT#2216).		**Install the [http://download.linuxmce.org/linux-image-default-raspbian-jessie_4.4.17-v7+-lmce5_all.deb default netboot kernel package] for a Raspberry PiB 1/2/3 MD. This image will permit you to select from multiple possible RPi Device Templates. These include: RPi MD (DT#2216).
	*edit /usr/pluto/bin/Diskless_CreateTBZ.sh and enable "raspbian_armhf" as the only* TARGET_TYPE, be sure to comment (use a #) any other TARGET_TYPE lines so that only this one is enabled.		*edit /usr/pluto/bin/Diskless_CreateTBZ.sh and enable "raspbian_armhf" as the only* TARGET_TYPE, be sure to comment (use a #) any other TARGET_TYPE lines so that only this one is enabled.
	**run /usr/pluto/bin/Diskless_CreateTBZ.sh to create a raspbian tarball file on your core.		**run /usr/pluto/bin/Diskless_CreateTBZ.sh to create a raspbian tarball file on your core.

Phenigma at 23:06, 20 September 2016

2016-09-20T23:06:52Z

←Older revision		Revision as of 23:06, 20 September 2016
Line 57:		Line 57:
	*On the RPiB client:		*On the RPiB client:
	**Enable the usb-boot OTP programmable bit (this blows an e-fuse than cannot be undone) which allows the firmware to attempt usb or network booting from then on.		**Enable the usb-boot OTP programmable bit (this blows an e-fuse than cannot be undone) which allows the firmware to attempt usb or network booting from then on.
	***Download this pre-configured image for LinuxMCE: [http://~~download~~.linuxmce.org/rpi-sdcard_2016-09-20-netboot-lmce.zip LinuxMCE RPi netboot setup image]		***Download this pre-configured image for LinuxMCE: [http://www.linuxmce.org/rpi-sdcard_2016-09-20-netboot-lmce.zip LinuxMCE RPi netboot setup image]
	***Un-zip the image and install the resulting image onto an SD card, using dd on linux or win32diskimager on windows		***Un-zip the image and install the resulting image onto an SD card, using dd on linux or win32diskimager on windows
	***Ensure the RPi is connected to the internal lan of your core and boot the RPi.		***Ensure the RPi is connected to the internal lan of your core and boot the RPi.

Phenigma at 23:03, 20 September 2016

2016-09-20T23:03:50Z

←Older revision		Revision as of 23:03, 20 September 2016
Line 42:		Line 42:
	* Your core must be LinuxMCE 1204 or higher.		* Your core must be LinuxMCE 1204 or higher.
	* The Raspberry Pi must be a Model B Version 1, 2 or 3. The Model A and the RPi Version 1 are not supported.		* The Raspberry Pi must be a Model B Version 1, 2 or 3. The Model A and the RPi Version 1 are not supported.
	* The recommended device is the RPi3. The RPiB1/2 will need an sdcard inserted to use these ~~pxe~~ methods. The RPi3 does not need any inserted medium to boot (once configured).		* The recommended device is the RPi3. The RPiB1/2 will need an sdcard inserted to use these netboot methods. The RPi3 does not need any inserted medium to boot (once configured).
	* The Raspberry Pi must be ~~plugged into~~ the internal side of your LinuxMCE core's network to act as a media director.		* The Raspberry Pi must be connected to the internal side of your LinuxMCE core's network to act as a media director.
	* The Raspberry Pi must be plugged in using the HDMI connector. Set an S (for Analog Stereo) or H (for HDMI) for the Audio Settings for the MD in webadmin.		* The Raspberry Pi must be plugged in using the HDMI connector. Set an S (for Analog Stereo) or H (for HDMI) for the Audio Settings for the MD in webadmin.
	** The Raspberry Pi will detect the boot resolution of your display and adjust itself accordingly.		** The Raspberry Pi will detect the boot resolution of your display and adjust itself accordingly.
Line 51:		Line 51:
	==Setup Steps==		==Setup Steps==
	*On the Core:		*On the Core:
	**Install the [http://download.linuxmce.org/linux-image-default-raspbian-jessie_4.4.15-v7+-lmce4_all.deb default ~~PXE~~ kernel package] for a Raspberry PiB 1/2/3 MD. This image will permit you to select from multiple possible RPi Device Templates. These include: RPi MD (DT#2216).		**Install the [http://download.linuxmce.org/linux-image-default-raspbian-jessie_4.4.15-v7+-lmce4_all.deb default netboot kernel package] for a Raspberry PiB 1/2/3 MD. This image will permit you to select from multiple possible RPi Device Templates. These include: RPi MD (DT#2216).
	*edit /usr/pluto/bin/Diskless_CreateTBZ.sh and enable "raspbian_armhf" as the only* TARGET_TYPE, be sure to comment (use a #) any other TARGET_TYPE lines so that only this one is enabled.		*edit /usr/pluto/bin/Diskless_CreateTBZ.sh and enable "raspbian_armhf" as the only* TARGET_TYPE, be sure to comment (use a #) any other TARGET_TYPE lines so that only this one is enabled.
	**run /usr/pluto/bin/Diskless_CreateTBZ.sh to create a raspbian tarball file on your core.		**run /usr/pluto/bin/Diskless_CreateTBZ.sh to create a raspbian tarball file on your core.

	*On the RPiB client:		*On the RPiB client:
	**Enable the usb-boot OTP programmable bit (this blows an e-fuse than cannot be undone) which allows the firmware to attempt usb or ~~pxe~~ booting from then on.		**Enable the usb-boot OTP programmable bit (this blows an e-fuse than cannot be undone) which allows the firmware to attempt usb or network booting from then on.
	***Download ~~the lite version of Rasbian from here~~: ~~https~~://~~www~~.~~raspberrypi~~.org/~~downloads/raspbian/~~		***Download this pre-configured image for LinuxMCE: [http://download.linuxmce.org/rpi-sdcard_2016-09-20-netboot-lmce.zip LinuxMCE RPi netboot setup image]
	***login with name: 'raspberry' pwd: 'pi'		***Un-zip the image and install the resulting image onto an SD card, using dd on linux or win32diskimager on windows
	***Add the line 'program_usb_boot_mode=1' to config.~~txt in the boot partition. (/boot)~~		***Ensure the RPi is connected to the internal lan of your core and boot the RPi.
	***~~Boot~~ the ~~RPi~~ and ~~run 'apt-get~~ install ~~rpi-update' followed by 'BRANCH=next rpi-update'~~		***Boot the RPi and it will program the OTP bit for USB and Network booting
	***~~Boot~~ the RPi ~~once with the new bootloader~~ to ~~set~~ the ~~OTP programmable bit.~~		***The rpi will clean the sdcard and automatically reboot to begin the network boot and discovery process.
	***Run: 'vcgencmd otp_dump \| grep 17:', the ~~output should be '17:3020000a' to verify the OTP is programmed~~.
	****TODO: make a card, if someone wants to provide an sdcard that does the ~~initial OTP programming I'd appreciate~~ it.
	***If you are booting an RPiB1/2 you will ~~need an sdcard with a bootcode.bin file from~~ the ~~rpi kernel 'next' branch on it. This should be the only file on the card.~~
	***~~Create this card (if you need it) by removing all files in the boot partition of~~ the sdcard ~~except for 'bootcode.bin'~~
	****TODO: make a card, if someone wants to ~~provide an sdcard I'd appreciate it~~.
	***If you are booting an RPiB3 you can remove the sdcard used to set the OTP bit and boot without any attached media.		***If you are booting an RPiB3 you can remove the sdcard used to set the OTP bit and boot without any attached media.
			**On first boot you may be prompted on existing orbiters to choose a device type MD/qMD/SqueezeOnly, do so. (qMD is not working yet)
			**The device will automatically be created, you will need to reload your router.
	**AVWizard will not appear.		**AVWizard will not appear.
	**You should see the setup wizard and be asked to configure your new MD.		**You should see the setup wizard and be asked to configure your new MD.
Line 82:		Line 79:
	*Download the rpi uSD card image ([http://download.linuxmce.org/lmce-disked-md-rpi2-jessie.tar.xz raspbian jessie (recommended)] (Updated: 2016-04-29)		*Download the rpi uSD card image ([http://download.linuxmce.org/lmce-disked-md-rpi2-jessie.tar.xz raspbian jessie (recommended)] (Updated: 2016-04-29)
	*untar the compressed file (e.g. tar -xvJf lmce-disked-md-rpi2-jessie.tar.xz)		*untar the compressed file (e.g. tar -xvJf lmce-disked-md-rpi2-jessie.tar.xz)
	*Install the resulting image onto an SD card, using dd on linux ( e.g. sudo dd bs=4M if=2015-12-23-raspbian-jessie.img of=/dev/sdb [make sure device name is correct!]) or ~~win32diskimage~~ on windows		*Install the resulting image onto an SD card, using dd on linux ( e.g. sudo dd bs=4M if=2015-12-23-raspbian-jessie.img of=/dev/sdb [make sure device name is correct!]) or win32diskimager on windows
	*Ensure the RPi is connected to the internal lan of your core and boot the RPi. Wifi is not currently supported on the RPiB 3.		*Ensure the RPi is connected to the internal lan of your core and boot the RPi. Wifi is not currently supported on the RPiB 3.
	*You may be prompted on existing orbiters to choose a device type MD/qMD/SqueezeOnly, do so. (qMD is not working yet)		*You may be prompted on existing orbiters to choose a device type MD/qMD/SqueezeOnly, do so. (qMD is not working yet)

Phenigma at 18:04, 16 September 2016

2016-09-16T18:04:01Z

←Older revision		Revision as of 18:04, 16 September 2016
Line 56:		Line 56:

	*On the RPiB client:		*On the RPiB client:
	**Enable the usb-boot OTP programmable bit (this blows an e-fuse than cannot be undone) which allows the firmware to attempt usb or pxe booting from then on. ~~See~~ the ~~foundation~~'~~s tutorial on how~~ to ~~do this~~.		**Enable the usb-boot OTP programmable bit (this blows an e-fuse than cannot be undone) which allows the firmware to attempt usb or pxe booting from then on.
	***TODO: make a card, if someone wants to provide an sdcard that does the initial OTP programming I'd appreciate it.		***Download the lite version of Rasbian from here: https://www.raspberrypi.org/downloads/raspbian/
			***login with name: 'raspberry' pwd: 'pi'
			***Add the line 'program_usb_boot_mode=1' to config.txt in the boot partition. (/boot)
			***Boot the RPi and run 'apt-get install rpi-update' followed by 'BRANCH=next rpi-update'
			***Boot the RPi once with the new bootloader to set the OTP programmable bit.
			***Run: 'vcgencmd otp_dump \| grep 17:', the output should be '17:3020000a' to verify the OTP is programmed.
			****TODO: make a card, if someone wants to provide an sdcard that does the initial OTP programming I'd appreciate it.
	***If you are booting an RPiB1/2 you will need an sdcard with a bootcode.bin file from the rpi kernel 'next' branch on it. This should be the only file on the card.		***If you are booting an RPiB1/2 you will need an sdcard with a bootcode.bin file from the rpi kernel 'next' branch on it. This should be the only file on the card.
			***Create this card (if you need it) by removing all files in the boot partition of the sdcard except for 'bootcode.bin'
	****TODO: make a card, if someone wants to provide an sdcard I'd appreciate it.		****TODO: make a card, if someone wants to provide an sdcard I'd appreciate it.
	***If you are booting an RPiB3 you can remove the sdcard used to set the OTP bit and boot without any attached media.		***If you are booting an RPiB3 you can remove the sdcard used to set the OTP bit and boot without any attached media.

Phenigma at 04:54, 24 August 2016

2016-08-24T04:54:35Z

←Older revision		Revision as of 04:54, 24 August 2016
Line 56:		Line 56:

	*On the RPiB client:		*On the RPiB client:
	Enable the usb-boot OTP programmable bit (this blows an e-fuse than cannot be undone) which allows the firmware to attempt usb or pxe booting from then on. See the foundation's tutorial on how to do this. *TODO: make a card, if someone wants to provide an sdcard that does the initial OTP programming I'd appreciate it.		**Enable the usb-boot OTP programmable bit (this blows an e-fuse than cannot be undone) which allows the firmware to attempt usb or pxe booting from then on. See the foundation's tutorial on how to do this.
	**If you are booting an RPiB1/2 you will need an sdcard with a bootcode.bin file from the rpi kernel 'next' branch on it. This should be the only file on the card.		***TODO: make a card, if someone wants to provide an sdcard that does the initial OTP programming I'd appreciate it.
	***TODO: make a card, if someone wants to provide an sdcard I'd appreciate it.		***If you are booting an RPiB1/2 you will need an sdcard with a bootcode.bin file from the rpi kernel 'next' branch on it. This should be the only file on the card.
	**If you are booting an RPiB3 you can remove the sdcard used to set the OTP bit and boot without any attached media.		****TODO: make a card, if someone wants to provide an sdcard I'd appreciate it.
			***If you are booting an RPiB3 you can remove the sdcard used to set the OTP bit and boot without any attached media.
			**AVWizard will not appear.
			**You should see the setup wizard and be asked to configure your new MD.
			**The new RPi moonpi should continue installing and eventually present you with a UI1 OnScreen Orbiter.

			Please report bugs with very specific (package date/svn, etc) information in a ticket.

	=RPiB Disked Media Director=		=RPiB Disked Media Director=

Phenigma at 18:02, 10 August 2016

2016-08-10T18:02:29Z

←Older revision		Revision as of 18:02, 10 August 2016
Line 15:		Line 15:

	==Manual Settings==		==Manual Settings==
	*Overscan - currently only able to change by manually editing the config.txt file on the sdcard. (See [http://elinux.org/RPiconfig http://elinux.org/RPiconfig])		*Overscan - currently only able to change by manually editing the config.txt file on the sdcard from a u-boot-ed moonpi or in /boot on all other booted moonpis. (See [http://elinux.org/RPiconfig http://elinux.org/RPiconfig])
	*Overscan compensation - currently only able to change by manually editing the config.txt file on the sdcard. In /sdcard/config.txt from a booted ~~moonpi~~. (See [http://elinux.org/RPiconfig http://elinux.org/RPiconfig])		*Overscan compensation - currently only able to change by manually editing the config.txt file on the sdcard. In /sdcard/config.txt from a u-boot-ed moonpi, or in /boot on all other booted moonpis. (See [http://elinux.org/RPiconfig http://elinux.org/RPiconfig])
	*Orbiter will automatically regenerate following a reboot ~~and detecting~~ a new display resolution.		*Orbiter will automatically regenerate following a reboot if a new display resolution is detected.
	*Audio settings are adjusted in webadmin. Go to Wizard - Devices - Media Directors, scroll to the Media Director you want to alter and select Advanced on the right side. In the Device Data section, set one of the following parameters in the Audio settings field:		*Audio settings are adjusted in webadmin. Go to Wizard - Devices - Media Directors, scroll to the Media Director you want to alter and select Advanced on the right side. In the Device Data section, set one of the following parameters in the Audio settings field:
	S = Stereo		S = Stereo

Phenigma: /* Requirements */

2016-08-10T17:59:40Z

Requirements

←Older revision		Revision as of 17:59, 10 August 2016
Line 40:		Line 40:
	=RPiB Diskless Media Director=		=RPiB Diskless Media Director=
	==Requirements==		==Requirements==
	* Your core must be LinuxMCE ~~1404~~ or higher.		* Your core must be LinuxMCE 1204 or higher.
	* The Raspberry Pi must be a Model B Version 1, 2 or 3. The Model A and the RPi Version 1 are not supported.		* The Raspberry Pi must be a Model B Version 1, 2 or 3. The Model A and the RPi Version 1 are not supported.
	* The recommended device is the RPi3. The RPiB1/2 will need an sdcard inserted to use these pxe methods. The RPi3 does not need any inserted medium to boot (once configured).		* The recommended device is the RPi3. The RPiB1/2 will need an sdcard inserted to use these pxe methods. The RPi3 does not need any inserted medium to boot (once configured).

Phenigma at 06:16, 10 August 2016

2016-08-10T06:16:24Z

←Older revision		Revision as of 06:16, 10 August 2016
Line 58:		Line 58:
	Enable the usb-boot OTP programmable bit (this blows an e-fuse than cannot be undone) which allows the firmware to attempt usb or pxe booting from then on. See the foundation's tutorial on how to do this. *TODO: make a card, if someone wants to provide an sdcard that does the initial OTP programming I'd appreciate it.		Enable the usb-boot OTP programmable bit (this blows an e-fuse than cannot be undone) which allows the firmware to attempt usb or pxe booting from then on. See the foundation's tutorial on how to do this. *TODO: make a card, if someone wants to provide an sdcard that does the initial OTP programming I'd appreciate it.
	**If you are booting an RPiB1/2 you will need an sdcard with a bootcode.bin file from the rpi kernel 'next' branch on it. This should be the only file on the card.		**If you are booting an RPiB1/2 you will need an sdcard with a bootcode.bin file from the rpi kernel 'next' branch on it. This should be the only file on the card.
	***TODO: make a card, if someone wants to provide an sdcard ~~that does the initial OTP programming~~ I'd appreciate it.		***TODO: make a card, if someone wants to provide an sdcard I'd appreciate it.
	**If you are booting an RPiB3 you can remove the sdcard used to set the OTP bit and boot without any attached media.		**If you are booting an RPiB3 you can remove the sdcard used to set the OTP bit and boot without any attached media.