RPi Advanced Setup - Revision history

Mathben: /* Formatting the SD card via the mkcard.txt script */

2013-04-19T20:04:40Z

‎Formatting the SD card via the mkcard.txt script

Pioneer: /* Finding hardware and setting up */

2013-04-13T19:37:44Z

‎Finding hardware and setting up

Kamikava: /* Finding hardware and setting up */

2013-03-22T14:50:23Z

‎Finding hardware and setting up

BlueChip: loader.bin no longer supplied as a part of the official RPi firmware distribution

2012-11-23T02:10:20Z

loader.bin no longer supplied as a part of the official RPi firmware distribution

Byteme: /* Setting up for remote access / headless operation */

2012-11-17T17:15:58Z

‎Setting up for remote access / headless operation

Byteme: /* Setting up for remote access / headless operation */

2012-11-17T17:14:41Z

‎Setting up for remote access / headless operation

Mahjongg: /* Additional files supplied by the foundation */

2012-10-29T09:36:21Z

‎Additional files supplied by the foundation

Mahjongg: /* Additional files supplied by the foundation */

2012-10-29T09:35:14Z

‎Additional files supplied by the foundation

Mahjongg: /* Additional files supplied by the foundation */ added info about new split system.

2012-10-29T09:34:03Z

‎Additional files supplied by the foundation: added info about new split system.

Shuckle at 08:40, 28 August 2012

2012-08-28T08:40:46Z

@@ Line 41: / Line 41: @@
 == Formatting the SD card via the mkcard.txt script ==
-# Download '''mkcard.txt''' from ???.
+# Download '''mkcard.txt''' from http://downloads.angstrom-distribution.org/demo/beaglebone/mkcard.txt
 # <code>$ chmod +x mkcard.txt</code>
-# <code>$ ./mkcard.txt /dev/sd</code>''x'', Where ''x'' is the letter of the card.  You can find this by inserting your card and then running <code> dmesg | tail</code>.  You should see the messages about the device being mounted in the log.  Mine mounts as '''sdc'''.
+# <code>$ ./mkcard.txt /dev/sd</code>''X'', Where ''X'' is the letter of the card.  You can find this by inserting your card and then running <code> dmesg | tail</code>.  You should see the messages about the device being mounted in the log.  Mine mounts as '''sdc'''.
 Once run, your card should be formatted.
 == Formatting the SD card via fdisk "Expert mode" ==

@@ Line 25: / Line 25: @@
 You'll likely also want a USB mouse, a case, and a USB Hub (a necessity for Model A). A powered USB Hub will reduce the demand on the RPi. To connect to the Internet, you'll need either an Ethernet/LAN cable (Model B) or a USB WiFi adaptor (either model).  See [[RPi VerifiedPeripherals]] for more information on supported peripherals.
-All this basic verified hardware is available from both [http://modmypi.com ModMyPi's Raspberry Pi Shop] and [http://thepihut.com/ Pi Hut's Raspberry Pi Store]
+All this basic verified hardware is available from both [http://thepihut.com/ Pi Hut's Raspberry Pi Store]  and [http://modmypi.com ModMyPi's Raspberry Pi Shop]
 When setting up, it is advisable to connect the power after everything else is ready. ''See [[RPi_Hardware_Basic_Setup#Connecting_Together]].''

@@ Line 21: / Line 21: @@
 ''Main article: see [[RPi Hardware Basic Setup]]''
-You'll need to [[RPi Beginners#SD_card_setup | copy an image]] to a [[RPi_VerifiedPeripherals#SD_cards | suitable SD card]] (or [[RPi Beginners#Advanced_SD_card_setup | make your own image]]).  You'll also need a USB keyboard, TV/Monitor (with HDMI/DVI/Composite/SCART input), and power supply (USB charger or a USB port from a powered USB Hub or another computer). All of which can be found over at the Pi Huts' [http://thepihut.com/ Raspberry Pi Store]
+You'll need to [[RPi Beginners#SD_card_setup | copy an image]] to a [[RPi_VerifiedPeripherals#SD_cards | suitable SD card]] (or [[RPi Beginners#Advanced_SD_card_setup | make your own image]]).  You'll also need a USB keyboard, TV/Monitor (with HDMI/DVI/Composite/SCART input), and power supply (USB charger or a USB port from a powered USB Hub or another computer).
 You'll likely also want a USB mouse, a case, and a USB Hub (a necessity for Model A). A powered USB Hub will reduce the demand on the RPi. To connect to the Internet, you'll need either an Ethernet/LAN cable (Model B) or a USB WiFi adaptor (either model).  See [[RPi VerifiedPeripherals]] for more information on supported peripherals.
 When setting up, it is advisable to connect the power after everything else is ready. ''See [[RPi_Hardware_Basic_Setup#Connecting_Together]].''

@@ Line 209: / Line 209: @@
 The boot partition must contain the following files, get them from one of the official images:(bootable/fat32 partition)
 * bootcode.bin : 2nd stage bootloader, starts with SDRAM disabled
-* loader.bin : 3rd stage bootloader, starts with SDRAM enabled
+* <del>loader.bin : 3rd stage bootloader, starts with SDRAM enabled</del>
 * start.elf: The GPU binary firmware image, provided by the foundation.
 * kernel.img: The OS kernel to load on the ARM processor.  Normally this is Linux - see instructions for [[RPi Kernel Compilation |compiling a kernel]].

@@ Line 321: / Line 321: @@
 # '''Create a configfile for Avahi''' at '''/etc/avahi/services/multiple.service'''. I did this with the following command:<pre>sudo pico /etc/avahi/services/multiple.service</pre>The contents of this file should be something like the following, courtesy of '''aXon''' on the [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=29&t=7795&p=94439&hilit=avahi#p94439 Rasperry Pi forums]:<pre><?xml version="1.0" standalone='no'?>&#10;<!DOCTYPE service-group SYSTEM "avahi-service.dtd">&#10;<service-group>&#10;        <name replace-wildcards="yes">%h</name>&#10;        <service>&#10;                <type>_device-info._tcp</type>&#10;                <port>0</port>&#10;                <txt-record>model=RackMac</txt-record>&#10;        </service>&#10;        <service>&#10;                <type>_ssh._tcp</type>&#10;                <port>22</port>&#10;        </service>&#10;</service-group></pre>
 # '''Apply the new configuration''' with:<pre>sudo /etc/init.d/avahi-daemon restart</pre>The Pi should now be addressable from other machines as '''raspberrypi.local''', for example: <pre>ssh pi@raspberrypi.local</pre>
-#''' Get Wind/blows to play nice with avahi'''<br>If you've done the first steps correctly and you open up Putty and you try to address your pi as raspberrypi.local, it will tell you:<br>[[File:Puttyerroravahi.png]]<br>::This happens for a very good reason: your Windows PC can't interpret the udp-datagrams avahi sends and most firewalls don't even allow them to get read. So you'll have to do a couple of things extra to get it working.
+#''' Get Wind/blows to play nice with avahi'''<br>If you've done the first steps correctly and you open up Putty and you try to address your pi as raspberrypi.local, it will tell you:<br>[[File:Puttyerroravahi.png]]<br>This happens for a very good reason: your Windows PC can't interpret the udp-datagrams avahi sends and most firewalls don't even allow them to get read. So you'll have to do a couple of things extra to get it working.
 # '''Get Bonjour for Windows'''<br> http://support.apple.com/kb/DL999 Just install it, quick next next next next procedure will suffice. Now your computer is able to interpret the UDP datagrams which are multicasted by the pi. But we're not out of the woods just yet, if you try to ping to your raspberry pi:<br><pre>C:\Windows\System32>ping raspberrypi.local&#10;Ping-request cannot find host raspberrypi.local.&#10;Check the name and try again.</pre>

@@ Line 229: / Line 229: @@
 the file called start.elf actually determines how much of the available 256MB of memory is assigned to the GPU, but previously each start.elf file gave a fixed split size.
-The other splits were simply very similar files with a different filename, which were copied over the one called start.elf that is actually used, the others had names like arm192_start.elf and such.
+The other splits were simply very similar files with a different filename, which were copied over the one called start.elf that was actually to be used, the others had names like arm192_start.elf and such.
 * arm128_start.elf : 128M ARM, 128M GPU split (use this for heavy 3D work, possibly also required for some video decoding)

@@ Line 226: / Line 226: @@
 * kernel_emergency.img : kernel with busybox rootfs.  You can use this to repair the main linux partition using e2fsck if the linux partition gets corrupted.
-Before the introduction of the 512MB Raspberry PI additional GPU firmware images were delivered, to be, copied over start.elf to use them:
+Before the introduction of the 512MB Raspberry PI additional GPU firmware images (start.elf files) were delivered, to be copied over start.elf to use them:
 the file called start.elf actually determines how much of the available 256MB of memory is assigned to the GPU, but previously each start.elf file gave a fixed split size.

@@ Line 235: / Line 235: @@
 * arm192_start.elf : 192M ARM, 64M GPU split (this is the default)
 * arm224_start.elf : 224M ARM, 32M GPU split (use this for Linux only with no 3D or video processing.  Its enough for the 1080p framebuffer, but not much else)
 Note that actually there is no "default" split, the nature of the software determines what is the most suitable split. So a "distro" that is very heavy multimedia oriented will normally use the 128/128MB split as the GPU needs a lot of RAM, but a generic desktop distro will probably use the 64/192 MB split, and a game that doesn't use the GPU will probably use the 32/224MB split.