eLinux.org - User contributions [en]

User:Gus3

2012-12-12T19:26:50Z

Gus3: adding VFP support to libm on Slackware ARM

Got my RPi on 2012-April-19. Currently running the customized Debian image, since I know a little more about Debian than the other supported distros (Arch, Fedora).

== Slackware on the Pi ==

One of my project ideas will be to get [http://www.armedslack.org/ Slackware ARM] running on the RPi. I would think that the Debian kernel and modules, with Slackware ARM userspace, could be hacked together to work, but that's only an uneducated guess. Slackware ARM currently has three installer images, for the three supported platforms; I eagerly await the fourth, Raspberry Pi.

=== 2012-05-02, late evening ===

I have a Slackware ARM setup that crashes in /etc/rc.d/rc.S. But at least that means /sbin/init is running from the flash card. Yay!

=== 2012-05-03 ===

It turns out the SD card and my desktop's reader have some kind of conflict, and e2fsck's clean-up sent many critical libraries to /lost+found/. Another file that disappeared was /etc/fstab. Not good. My netbook's card reader works OK with the card, so I'm re-installing the libraries now. We'll see what else got clobbered, but the libraries are the most important thing to repair.

=== 2012-05-08 ===

It works! My basic idea above (Debian kernel, Slackware ARM userspace), using the packages outlined [http://wiki.linuxquestions.org/wiki/Slackware-Minimal_Install here], has given me an RPi that works on the network. The installation is 291M (in a 1.5G partition), with DHCP, without X.

Now, to clean it up and find a way to get it online. Suggestions welcome for hosting/distribution; I can't host it myself.

=== 2012-05-21 ===

A rather sad discovery: The Raspberry Pi has a built-in FPU, but Slackware ARM isn't built for it. The math library (libm) has only a few instances of FPU instructions, and they appear to be for FPU state management, not computation. I don't know how much this slows down the overall system. A lot of programs link in libm, even some which I doubt actually use it (e.g. vim). The first package I should (attempt to) recompile is glibc, which might get an overall speed gain.

=== 2012-12-12 ===

I did finally figure out how to rebuild glibc on Slackware, including Slackware ARM. Adding VFP support to glibc and libm is documented [https://mindplusplus.wordpress.com/2012/11/20/howto-rebuild-glibc-on-slackware-arm-14-0-for-the-raspberry-pi/ here].

== Cooling systems for the Pi ==

I've done a few little experiments with auxiliary cooling for the Raspberry Pi. You can read the report [http://mindplusplus.wordpress.com/2012/05/14/the-raspberry-pi-my-first-hardware-experiment/ here].

== Reviewing the RPi ==

I've had the Raspberry Pi for a month, so I thought it time to review it [http://mindplusplus.wordpress.com/2012/05/23/the-raspberry-pi-a-review/ here].

Talk:R-Pi Troubleshooting

2012-09-04T17:40:44Z

Gus3:

== New Power/startup issue ==

I'm seeing a symptom not yet described on the page.

The Red PWR led is on. The (normally) green led for OK is not, except for a tiny green dot in the center of the led.
Or is this point 1.2?

In my case the board does not boot at all (no video, no flickering leds). According to Farnell there might be an issue with a recent series of boards that all seem to have this behaviour. But this still needs to be confirmed.

I still have to test some other distro's and SD cards to exclude a few failure modes.

== SD image ==

I (Ian) created the New Power/startup issue (above) by putting the image into the partition instead of the whole device
ie I did:
dd bs=1M if=~/debian6-19-04-2012/debian6-19-04-2012.img of=/dev/sdd1

it should be
dd bs=1M if=~/debian6-19-04-2012/debian6-19-04-2012.img of=/dev/sdd

== DVI Interference occuring after firmware upgrade ==

Hi, I just got my raspberry Pi today and was playing with it fine on the firmware that came with the image download with clear picture and no interference with both the standard config.txt and with overscan disabled, but when updating to the newer firmware with Hexxeh's rpi-update command, the interference issue described on this page started occurring (although with red dots rather than green like the picture). It did go away when setting the config_hdmi_boost to 4 - but it might help others to note that this could be caused by a firmware update, and not necessarily mean that something is broken. Although, I do find it strange if the "defaults" were changed as it causes this problem. [[User:Adammw|Adammw]] 09:53, 14 June 2012 (UTC)

== Need links to solutions for common problems ==

For example I've got this one. I figured out on my own that the keyboard is tripping it up. But what can I do about it ? It's as vanilla a cheap Chinese USB keyboard as can be had!

'''Kernel Panic on boot'''
Text appears on screen, but then hangs with debug messages. This can be caused by USB devices such as keyboards. Try again with nothing in the USB.

--[[User:Dreamgear|Dreamgear]] 01:18, 23 June 2012 (UTC)

== New bootloader worked for me ==

I downloaded the new bootcode file https://github.com/raspberrypi/firmware/blob/234c19de7cbaaf4997671d61df20a05759066295/boot/bootcode.bin referenced in the article. This made my RaspBerry Pi boot up. I have a model B board, a SanDisk SHDC 4 GB card (specific model unknown), and used the latest squeeze image from the downloads page (debian6-19-04-2012.img)
----

Same for me, same SD card, worked only with the new bootcode.bin, otherwise the red led would not blink nor was there any video signal.

== Why is arm240_start.elf a better choice? ==

From the text: "the arm224_start.elf is usually the wrong choice." In keeping with the educational goals of the Raspberry Pi, I think an explanation of this statement would be beneficial.

User talk:BradyDl

2012-06-25T13:43:32Z

Gus3: Spam account

== Spam alert ==

The history of this page will show a spam link and vacuous comments. I (gus3) have removed the spam link. Appropriate action by the editors will be appreciated.

RPiconfig

2012-06-19T02:16:27Z

Gus3: a couple minor typos

[[Category: RaspberryPi]]

The Raspberry Pi config.txt file is read by the GPU before the ARM core is initialised. It can be used to set various system configuration parameters.

This file is an optional file on the boot partition. It would normally be accessible as /boot/config.txt from Linux.

To edit the configuration file, see the instructions at [[R-Pi_ConfigurationFile]].

=File format=

The format is "property=value". value is an integer. You may specify only one option per line. Comments may be added by starting a line with the '#' character.

Here is an example file
'''# Set stdv mode to PAL (as used in Europe)
sdtv_mode=2
# Force the monitor to HDMI mode so that sound will be sent over HDMI cable
hdmi_drive=2
# Set monitor mode to DMT
hdmi_group=2
# Set monitor resolution to 1024x768 XGA 60Hz (HDMI_DMT_XGA_60)
hdmi_mode=16
# Make display smaller to stop text spilling off the screen
overscan_left=20
overscan_right=12
overscan_top=10
overscan_bottom=10'''

=Video mode configuration=
==Video mode options==
'''sdtv_mode''' defines the TV standard for composite output (default=0)
sdtv_mode=0 Normal NTSC
sdtv_mode=1 Japanese version of NTSC – no pedestal
sdtv_mode=2 Normal PAL
sdtv_mode=3 Brazilian version of PAL – 525/60 rather than 625/50, different subcarrier

'''sdtv_aspect''' defines the aspect ratio for composite output (default=1)
sdtv_aspect=1 4:3
sdtv_aspect=2 14:9
sdtv_aspect=3 16:9

'''hdmi_safe''' Use "safe mode" settings to try to boot with maximum hdmi compatibility.
(this does: hdmi_force_hotplug=1, hdmi_boost=4, hdmi_group=1, hdmi_mode=1, disable_overscan=0)

'''hdmi_force_hotplug''' overrides the normal selection of composite if no HDMI is detected
hdmi_force_hotplug=1 Use HDMI mode even if no HDMI monitor is detected

'''hdmi_drive''' chooses between HDMI and DVI modes
hdmi_drive= 1 Normal DVI mode (No sound)
hdmi_drive= 2 Normal HDMI mode (Sound will be sent if supported and enabled)

'''hdmi_group''' defines the HDMI type (default=1)

[rgh] I think values are 0 and 1 really, and the default 0 for CEA - at least with the latest firmware as of May 25th 2012.

hdmi_group=1 CEA
hdmi_group=2 DMT

'''hdmi_mode''' defines screen resolution in CEA or DMT format

'''These values are valid if hdmi_group=1 (CEA)'''
hdmi_mode=1 VGA
hdmi_mode=2 480p 60Hz
hdmi_mode=3 480p 60Hz H
hdmi_mode=4 720p 60Hz
hdmi_mode=5 1080i 60Hz
hdmi_mode=6 480i 60Hz
hdmi_mode=7 480i 60Hz H
hdmi_mode=8 240p 60Hz
hdmi_mode=9 240p 60Hz H
hdmi_mode=10 480i 60Hz 4x
hdmi_mode=11 480i 60Hz 4x H
hdmi_mode=12 240p 60Hz 4x
hdmi_mode=13 240p 60Hz 4x H
hdmi_mode=14 480p 60Hz 2x
hdmi_mode=15 480p 60Hz 2x H
hdmi_mode=16 1080p 60Hz
hdmi_mode=17 576p 50Hz
hdmi_mode=18 576p 50Hz H
hdmi_mode=19 720p 50Hz
hdmi_mode=20 1080i 50Hz
hdmi_mode=21 576i 50Hz
hdmi_mode=22 576i 50Hz H
hdmi_mode=23 288p 50Hz
hdmi_mode=24 288p 50Hz H
hdmi_mode=25 576i 50Hz 4x
hdmi_mode=26 576i 50Hz 4x H
hdmi_mode=27 288p 50Hz 4x
hdmi_mode=28 288p 50Hz 4x H
hdmi_mode=29 576p 50Hz 2x
hdmi_mode=30 576p 50Hz 2x H
hdmi_mode=31 1080p 50Hz
hdmi_mode=32 1080p 24Hz
hdmi_mode=33 1080p 25Hz
hdmi_mode=34 1080p 30Hz
hdmi_mode=35 480p 60Hz 4x
hdmi_mode=36 480p 60Hz 4xH
hdmi_mode=37 576p 50Hz 4x
hdmi_mode=38 576p 50Hz 4x H
hdmi_mode=39 1080i 50Hz reduced blanking
hdmi_mode=40 1080i 100Hz
hdmi_mode=41 720p 100Hz
hdmi_mode=42 576p 100Hz
hdmi_mode=43 576p 100Hz H
hdmi_mode=44 576i 100Hz
hdmi_mode=45 576i 100Hz H
hdmi_mode=46 1080i 120Hz
hdmi_mode=47 720p 120Hz
hdmi_mode=48 480p 120Hz
hdmi_mode=49 480p 120Hz H
hdmi_mode=50 480i 120Hz
hdmi_mode=51 480i 120Hz H
hdmi_mode=52 576p 200Hz
hdmi_mode=53 576p 200Hz H
hdmi_mode=54 576i 200Hz
hdmi_mode=55 576i 200Hz H
hdmi_mode=56 480p 240Hz
hdmi_mode=57 480p 240Hz H
hdmi_mode=58 480i 240Hz
hdmi_mode=59 480i 240Hz H
H means 16:9 variant (of a normally 4:3 mode).
2x means pixel doubled (i.e. higher clock rate, with each pixel repeated twice)
4x means pixel quadrupled (i.e. higher clock rate, with each pixel repeated four times)

'''These values are valid if hdmi_group=2 (DMT)'''
hdmi_mode=1 640x350 85Hz
hdmi_mode=2 640x400 85Hz
hdmi_mode=3 720x400 85Hz
hdmi_mode=4 640x480 60Hz
hdmi_mode=5 640x480 72Hz
hdmi_mode=6 640x480 75Hz
hdmi_mode=7 640x480 85Hz
hdmi_mode=8 800x600 56Hz
hdmi_mode=9 800x600 60Hz
hdmi_mode=10 800x600 72Hz
hdmi_mode=11 800x600 75Hz
hdmi_mode=12 800x600 85Hz
hdmi_mode=13 800x600 120Hz
hdmi_mode=14 848x480 60Hz
hdmi_mode=15 1024x768 43Hz DO NOT USE
hdmi_mode=16 1024x768 60Hz
hdmi_mode=17 1024x768 70Hz
hdmi_mode=18 1024x768 75Hz
hdmi_mode=19 1024x768 85Hz
hdmi_mode=20 1024x768 120Hz
hdmi_mode=21 1152x864 75Hz
hdmi_mode=22 1280x768 reduced blanking
hdmi_mode=23 1280x768 60Hz
hdmi_mode=24 1280x768 75Hz
hdmi_mode=25 1280x768 85Hz
hdmi_mode=26 1280x768 120Hz reduced blanking
hdmi_mode=27 1280x800 reduced blanking
hdmi_mode=28 1280x800 60Hz
hdmi_mode=29 1280x800 75Hz
hdmi_mode=30 1280x800 85Hz
hdmi_mode=31 1280x800 120Hz reduced blanking
hdmi_mode=32 1280x960 60Hz
hdmi_mode=33 1280x960 85Hz
hdmi_mode=34 1280x960 120Hz reduced blanking
hdmi_mode=35 1280x1024 60Hz
hdmi_mode=36 1280x1024 75Hz
hdmi_mode=37 1280x1024 85Hz
hdmi_mode=38 1280x1024 120Hz reduced blanking
hdmi_mode=39 1360x768 60Hz
hdmi_mode=40 1360x768 120Hz reduced blanking
hdmi_mode=41 1400x1050 reduced blanking
hdmi_mode=42 1400x1050 60Hz
hdmi_mode=43 1400x1050 75Hz
hdmi_mode=44 1400x1050 85Hz
hdmi_mode=45 1400x1050 120Hz reduced blanking
hdmi_mode=46 1440x900 reduced blanking
hdmi_mode=47 1440x900 60Hz
hdmi_mode=48 1440x900 75Hz
hdmi_mode=49 1440x900 85Hz
hdmi_mode=50 1440x900 120Hz reduced blanking
hdmi_mode=51 1600x1200 60Hz
hdmi_mode=52 1600x1200 65Hz
hdmi_mode=53 1600x1200 70Hz
hdmi_mode=54 1600x1200 75Hz
hdmi_mode=55 1600x1200 85Hz
hdmi_mode=56 1600x1200 120Hz reduced blanking
hdmi_mode=57 1680x1050 reduced blanking
hdmi_mode=58 1680x1050 60Hz
hdmi_mode=59 1680x1050 75Hz
hdmi_mode=60 1680x1050 85Hz
hdmi_mode=61 1680x1050 120Hz reduced blanking
hdmi_mode=62 1792x1344 60Hz
hdmi_mode=63 1792x1344 75Hz
hdmi_mode=64 1792x1344 120Hz reduced blanking
hdmi_mode=65 1856x1392 60Hz
hdmi_mode=66 1856x1392 75Hz
hdmi_mode=67 1856x1392 120Hz reduced blanking
hdmi_mode=68 1920x1200 reduced blanking
hdmi_mode=69 1920x1200 60Hz
hdmi_mode=70 1920x1200 75Hz
hdmi_mode=71 1920x1200 85Hz
hdmi_mode=72 1920x1200 120Hz reduced blanking
hdmi_mode=73 1920x1440 60Hz
hdmi_mode=74 1920x1440 75Hz
hdmi_mode=75 1920x1440 120Hz reduced blanking
hdmi_mode=76 2560x1600 reduced blanking
hdmi_mode=77 2560x1600 60Hz
hdmi_mode=78 2560x1600 75Hz
hdmi_mode=79 2560x1600 85Hz
hdmi_mode=80 2560x1600 120Hz reduced blanking
hdmi_mode=81 1366x768 60Hz
hdmi_mode=82 1080p 60Hz
hdmi_mode=83 1600x900 reduced blanking
hdmi_mode=84 2048x1152 reduced blanking
hdmi_mode=85 720p 60Hz
hdmi_mode=86 1366x768 reduced blanking

'''overscan_left''' number of pixels to skip on left

'''overscan_right''' number of pixels to skip on right

'''overscan_top''' number of pixels to skip on top

'''overscan_bottom''' number of pixels to skip on bottom

'''framebuffer_width''' console framebuffer width in pixels. Default is display width minus overscan.

'''framebuffer_height''' console framebuffer height in pixels. Default is display height minus overscan.

'''framebuffer_depth''' console framebuffer depth in bits per pixel. Default is 16. 8bit is valid, but default RGB palette makes an unreadable screen. 24bit looks better but has corruption issues as of 20120615. 32bit has no corruption issues but needs framebuffer_ignore_alpha=1 and shows the wrong colors as of 20120615.

'''framebuffer_ignore_alpha''' set to 1 to disable alpha channel. Helps with 32bit.

'''test_mode''' enable test sound/image during boot for manufacturing test.

'''disable_l2cache''' disable arm access to GPU's L2 cache. Needs corresponding L2 disabled kernel. Default is 0.

'''disable_overscan''' set to 1 to disable overscan.

'''hdmi_force_hotplug''' Make RPi ignore hotplug signal from display and assume it is asserted.

'''config_hdmi_boost''' configure the signal strength of the HDMI interface. Default is 0. Try 4 if you have interference issues with hdmi. 7 is the maximum.

==Which values are valid for my monitor?==
Your HDMI monitor may support only a limited set of formats. To find out which formats are supported, use the following method.

*Set the output format to VGA 60Hz (hdmi_group=1 hdmi_mode=1) and boot up the Raspberry Pi
*Enter the following command to give a list of CEA supported modes
'''/opt/vc/bin/tvservice -m CEA'''
*Enter the following command to give a list of DMT supported modes
'''/opt/vc/bin/tvservice -m DMT'''
*Enter the following command to show your current state
'''/opt/vc/bin/tvservice -s'''

=Boot options=
'''disable_commandline_tags''' Stops start.elf from filling in ATAGS (memory from 0x100) before launching kernel

'''cmdline''' (string) Command line parameters. Can be used instead of cmdline.txt file

'''kernel''' (string) Alternative name to use when loading kernel.

'''kernel_address''' address to load kernel.img file at

'''ramfsfile''' (string) ramfs file to load

'''device_tree_address''' address to load device_tree at

'''init_uart_baud''' initial uart baud rate. Default 115200

'''init_uart_clock''' initial uart clock. Default 3000000

'''init_emmc_clock''' initial emmc clock. Default 50000000 (50mhz default. increasing this can speedup your SD-card)

'''boot_delay''' Waits for given number of seconds in start.elf before loading kernel.img.

=Overclocking configuration=
'''WARNING:''' Setting any of the parameters which over volt your Raspberry Pi will set a permanent bit within the SOC and your warranty is void. So If you care about the warranty do not adjust voltage.

Also at your own risk you can try [[RPi_config_for_your_TV|overscan settings]] from our wiki. These were [http://www.raspberrypi.org/forum/features-and-requests/should-we-make-a-wiki-page-for-overscan-settings posted] on the forum and are not confimed to work.
==Overclocking options==

{| cellpadding="2"
!Option !! Description
|-
!align="right"|arm_freq
| frequency of ARM in MHz. Default 700.
|-
!align="right"|gpu_freq
| Sets core_freq, h264_freq, isp_freq, v3d_freq together.
|-
!align="right"|core_freq
| frequency of GPU processor core in MHz. Default 250.
|-
!align="right"|h264_freq
| frequency of hardware video block in MHz. Default 250.
|-
!align="right"|isp_freq
| frequency of image sensor pipeline block in MHz. Default 250.
|-
!align="right"|v3d_freq
| frequency of 3D block in MHz. Default 250.
|-
!align="right"|sdram_freq
| frequency of SDRAM in MHz. Default 400.
|-
!align="right"|over_voltage
| ARM/GPU core voltage adjust. [-16,8] equates to [0.8V,1.4V] with 0.025V steps. Default 0 (1.2V) <ref name=voltages>What this means is that you can specify -16 and expect about 0.8V as the GPU/core voltage. This is 0.4V below the normal value of 1.2. If you specify 16, you'd get 0.4V ABOVE the normal value of 1.2V, or 1.6V. The fact that someone carefully specified "8" and "1.4V" as the upper limit in the examples leads me to think that it is likely to shorten the life of your raspberry pi significantly if you would specify values above "8". So: don't specify values above zero, but if you do, don't go above 8.</ref>
|-
!align="right"|over_voltage_sdram
| Sets over_voltage_sdram_c, over_voltage_sdram_i, over_voltage_sdram_p together
|-
!align="right"|over_voltage_sdram_c
| SDRAM controller voltage adjust. [-16,8] equates to [0.8V,1.4V] with 0.025V steps. Default 0 (1.2V) <ref name=voltages />
|-
!align="right"|over_voltage_sdram_i
| SDRAM I/O voltage adjust. [-16,8] equates to [0.8V,1.4V] with 0.025V steps. Default 0 (1.2V)<ref name=voltages />
|-
!align="right"|over_voltage_sdram_p
| SDRAM phy voltage adjust. [-16,8] equates to [0.8V,1.4V] with 0.025V steps. Default 0 (1.2V)<ref name=voltages />
|}

==Tested values==
The following table shows some successfull attempts of overclocking. These settings may not work on every device and can shorten the life of the Broadcom SoC. '''Warranty will be voided if overvoltage is used.'''
{| border="1"
! arm_freq !! gpu_freq !! core_freq !! h264_freq !! isp_freq !! v3d_freq !! sdram_freq !! over_voltage !! over_voltage_sdram
|-
|900 ||250 || || || || ||500 || ||
|-
|900 ||350 || || || || || || ||
|-
|930 ||350 || || || || ||500 || ||
|-
|1000 || ||500 || || || ||500 ||6 ||
|}

= Notes =
<references>

User talk:AdelaidaxlJefferson

2012-06-17T10:44:20Z

Gus3: spam user?

I prefer anything in specifically tattoos. I just really like the lots of designs that you can
create. While they genuinely hurt they're something you may possibly envy the moment and for all. So long as you go for a brilliant pattern then you undoubtedly really should arrange for life to indicate your existing tattoos out of.

My page: [http://wiki.fiatlux.tk/w/index.php?title=Discussion_utilisateur:TvpXIv tattoos are awesome]

== Spam? ==

The above shows all the characteristics of a spam account. Only one contribution, and it's off-topic for the site.

RPiconfig

2012-06-15T02:19:45Z

Gus3: /* Video mode options */

[[Category: RaspberryPi]]

The Raspberry Pi config.txt file is read by the GPU before the ARM core is initialised. It can be used to set various system configuration parameters.

This file is an optional file on the boot partition. It would normally be accessible as /boot/config.txt from Linux.

To edit the configuration file, see the instructions at [[R-Pi_ConfigurationFile]].

=File format=

The format is "property=value". value is an integer. You may specify only one option per line. Comments may be added by starting a line with the '#' character.

Here is an example file
'''# Set stdv mode to PAL (as used in Europe)
sdtv_mode=2
# Force the monitor to HDMI mode so that sound will be sent over HDMI cable
hdmi_drive=2
# Set monitor mode to DMT
hdmi_group=2
# Set monitor resolution to 1024x768 XGA 60Hz (HDMI_DMT_XGA_60)
hdmi_mode=16
# Make display smaller to stop text spilling off the screen
overscan_left=20
overscan_right=12
overscan_top=10
overscan_bottom=10'''

=Video mode configuration=
==Video mode options==
'''sdtv_mode''' defines the TV standard for composite output (default=0)
sdtv_mode=0 Normal NTSC
sdtv_mode=1 Japanese version of NTSC – no pedestal
sdtv_mode=2 Normal PAL
sdtv_mode=3 Brazilian version of PAL – 525/60 rather than 625/50, different subcarrier

'''sdtv_aspect''' defines the aspect ratio for composite output (default=1)
sdtv_aspect=1 4:3
sdtv_aspect=2 14:9
sdtv_aspect=3 16:9

'''hdmi_safe''' Use "safe mode" settings to try to boot with maximum hdmi compatability.
(this does: hdmi_force_hotplug=1, hdmi_boost=4, hdmi_group=1, hdmi_mode=1, disable_overscan=0)

'''hdmi_force_hotplug''' overrides the normal selection of composite if no HDMI is detected
hdmi_force_hotplug=1 Use HDMI mode even if no HDMI monitor is detected

'''hdmi_drive''' chooses between HDMI and DVI modes
hdmi_drive= 1 Normal DVI mode (No sound)
hdmi_drive= 2 Normal HDMI mode (Sound will be sent if supported and enabled)

'''hdmi_group''' defines the HDMI type (default=1)

[rgh] I think values are 0 and 1 really, and the default 0 for CEA - at least with the latest firmware as of May 25th 2012.

hdmi_group=1 CEA
hdmi_group=2 DMT

'''hdmi_mode''' defines screen resolution in CEA or DMT format

'''These values are valid if hdmi_group=1 (CEA)'''
hdmi_mode=1 VGA
hdmi_mode=2 480p 60Hz
hdmi_mode=3 480p 60Hz H
hdmi_mode=4 720p 60Hz
hdmi_mode=5 1080i 60Hz
hdmi_mode=6 480i 60Hz
hdmi_mode=7 480i 60Hz H
hdmi_mode=8 240p 60Hz
hdmi_mode=9 240p 60Hz H
hdmi_mode=10 480i 60Hz 4x
hdmi_mode=11 480i 60Hz 4x H
hdmi_mode=12 240p 60Hz 4x
hdmi_mode=13 240p 60Hz 4x H
hdmi_mode=14 480p 60Hz 2x
hdmi_mode=15 480p 60Hz 2x H
hdmi_mode=16 1080p 60Hz
hdmi_mode=17 576p 50Hz
hdmi_mode=18 576p 50Hz H
hdmi_mode=19 720p 50Hz
hdmi_mode=20 1080i 50Hz
hdmi_mode=21 576i 50Hz
hdmi_mode=22 576i 50Hz H
hdmi_mode=23 288p 50Hz
hdmi_mode=24 288p 50Hz H
hdmi_mode=25 576i 50Hz 4x
hdmi_mode=26 576i 50Hz 4x H
hdmi_mode=27 288p 50Hz 4x
hdmi_mode=28 288p 50Hz 4x H
hdmi_mode=29 576p 50Hz 2x
hdmi_mode=30 576p 50Hz 2x H
hdmi_mode=31 1080p 50Hz
hdmi_mode=32 1080p 24Hz
hdmi_mode=33 1080p 25Hz
hdmi_mode=34 1080p 30Hz
hdmi_mode=35 480p 60Hz 4x
hdmi_mode=36 480p 60Hz 4xH
hdmi_mode=37 576p 50Hz 4x
hdmi_mode=38 576p 50Hz 4x H
hdmi_mode=39 1080i 50Hz reduced blanking
hdmi_mode=40 1080i 100Hz
hdmi_mode=41 720p 100Hz
hdmi_mode=42 576p 100Hz
hdmi_mode=43 576p 100Hz H
hdmi_mode=44 576i 100Hz
hdmi_mode=45 576i 100Hz H
hdmi_mode=46 1080i 120Hz
hdmi_mode=47 720p 120Hz
hdmi_mode=48 480p 120Hz
hdmi_mode=49 480p 120Hz H
hdmi_mode=50 480i 120Hz
hdmi_mode=51 480i 120Hz H
hdmi_mode=52 576p 200Hz
hdmi_mode=53 576p 200Hz H
hdmi_mode=54 576i 200Hz
hdmi_mode=55 576i 200Hz H
hdmi_mode=56 480p 240Hz
hdmi_mode=57 480p 240Hz H
hdmi_mode=58 480i 240Hz
hdmi_mode=59 480i 240Hz H
H means 16:9 variant (of a normally 4:3 mode).
2x means pixel doubled (i.e. highter clock rate, with each pixel repeated twice)
4x means pixel quadrupled (i.e. higher clock rate, with each pixel repeated four times)

'''These values are valid if hdmi_group=2 (DMT)'''
hdmi_mode=1 640x350 85Hz
hdmi_mode=2 640x400 85Hz
hdmi_mode=3 720x400 85Hz
hdmi_mode=4 640x480 60Hz
hdmi_mode=5 640x480 72Hz
hdmi_mode=6 640x480 75Hz
hdmi_mode=7 640x480 85Hz
hdmi_mode=8 800x600 56Hz
hdmi_mode=9 800x600 60Hz
hdmi_mode=10 800x600 72Hz
hdmi_mode=11 800x600 75Hz
hdmi_mode=12 800x600 85Hz
hdmi_mode=13 800x600 120Hz
hdmi_mode=14 848x480 60Hz
hdmi_mode=15 1024x768 43Hz DO NOT USE
hdmi_mode=16 1024x768 60Hz
hdmi_mode=17 1024x768 70Hz
hdmi_mode=18 1024x768 75Hz
hdmi_mode=19 1024x768 85Hz
hdmi_mode=20 1024x768 120Hz
hdmi_mode=21 1152x864 75Hz
hdmi_mode=22 1280x768 reduced blanking
hdmi_mode=23 1280x768 60Hz
hdmi_mode=24 1280x768 75Hz
hdmi_mode=25 1280x768 85Hz
hdmi_mode=26 1280x768 120Hz reduced blanking
hdmi_mode=27 1280x800 reduced blanking
hdmi_mode=28 1280x800 60Hz
hdmi_mode=29 1280x800 75Hz
hdmi_mode=30 1280x800 85Hz
hdmi_mode=31 1280x800 120Hz reduced blanking
hdmi_mode=32 1280x960 60Hz
hdmi_mode=33 1280x960 85Hz
hdmi_mode=34 1280x960 120Hz reduced blanking
hdmi_mode=35 1280x1024 60Hz
hdmi_mode=36 1280x1024 75Hz
hdmi_mode=37 1280x1024 85Hz
hdmi_mode=38 1280x1024 120Hz reduced blanking
hdmi_mode=39 1360x768 60Hz
hdmi_mode=40 1360x768 120Hz reduced blanking
hdmi_mode=41 1400x1050 reduced blanking
hdmi_mode=42 1400x1050 60Hz
hdmi_mode=43 1400x1050 75Hz
hdmi_mode=44 1400x1050 85Hz
hdmi_mode=45 1400x1050 120Hz reduced blanking
hdmi_mode=46 1440x900 reduced blanking
hdmi_mode=47 1440x900 60Hz
hdmi_mode=48 1440x900 75Hz
hdmi_mode=49 1440x900 85Hz
hdmi_mode=50 1440x900 120Hz reduced blanking
hdmi_mode=51 1600x1200 60Hz
hdmi_mode=52 1600x1200 65Hz
hdmi_mode=53 1600x1200 70Hz
hdmi_mode=54 1600x1200 75Hz
hdmi_mode=55 1600x1200 85Hz
hdmi_mode=56 1600x1200 120Hz reduced blanking
hdmi_mode=57 1680x1050 reduced blanking
hdmi_mode=58 1680x1050 60Hz
hdmi_mode=59 1680x1050 75Hz
hdmi_mode=60 1680x1050 85Hz
hdmi_mode=61 1680x1050 120Hz reduced blanking
hdmi_mode=62 1792x1344 60Hz
hdmi_mode=63 1792x1344 75Hz
hdmi_mode=64 1792x1344 120Hz reduced blanking
hdmi_mode=65 1856x1392 60Hz
hdmi_mode=66 1856x1392 75Hz
hdmi_mode=67 1856x1392 120Hz reduced blanking
hdmi_mode=68 1920x1200 reduced blanking
hdmi_mode=69 1920x1200 60Hz
hdmi_mode=70 1920x1200 75Hz
hdmi_mode=71 1920x1200 85Hz
hdmi_mode=72 1920x1200 120Hz reduced blanking
hdmi_mode=73 1920x1440 60Hz
hdmi_mode=74 1920x1440 75Hz
hdmi_mode=75 1920x1440 120Hz reduced blanking
hdmi_mode=76 2560x1600 reduced blanking
hdmi_mode=77 2560x1600 60Hz
hdmi_mode=78 2560x1600 75Hz
hdmi_mode=79 2560x1600 85Hz
hdmi_mode=80 2560x1600 120Hz reduced blanking
hdmi_mode=81 1366x768 60Hz
hdmi_mode=82 1080p 60Hz
hdmi_mode=83 1600x900 reduced blanking
hdmi_mode=84 2048x1152 reduced blanking
hdmi_mode=85 720p 60Hz
hdmi_mode=86 1366x768 reduced blanking

'''overscan_left''' number of pixels to skip on left

'''overscan_right''' number of pixels to skip on right

'''overscan_top''' number of pixels to skip on top

'''overscan_bottom''' number of pixels to skip on bottom

'''framebuffer_width''' console framebuffer width in pixels. Default is display width minus overscan.

'''framebuffer_height''' console framebuffer height in pixels. Default is display height minus overscan.

'''framebuffer_depth''' console framebuffer depth in bits per pixel. Default is 16. 24bit looks better but has issues as of 20120615. 8bit is valid, but default RGB palette makes an unreadable screen.

'''test_mode''' enable test sound/image during boot for manufacturing test.

'''disable_l2cache''' disable arm access to GPU's L2 cache. Needs corresponding L2 disabled kernel. Default is 0.

'''disable_overscan''' set to 1 to disable overscan.

'''hdmi_force_hotplug''' Make RPi ignore hotplug signal from display and assume it is asserted.

'''config_hdmi_boost''' configure the signal strength of the HDMI interface. Default is 0. Try 4 if you have interference issues with hdmi. 7 is the maximum.

==Which values are valid for my monitor?==
Your HDMI monitor may support only a limited set of formats. To find out which formats are supported, use the following method.

*Set the output format to VGA 60Hz (hdmi_group=1 hdmi_mode=1) and boot up the Raspberry Pi
*Enter the following command to give a list of CEA supported modes
'''/opt/vc/bin/tvservice -m CEA'''
*Enter the following command to give a list of DMT supported modes
'''/opt/vc/bin/tvservice -m DMT'''
*Enter the following command to show your current state
'''/opt/vc/bin/tvservice -s'''

=Boot options=
'''disable_commandline_tags''' Stops start.elf from filling in ATAGS (memory from 0x100) before launching kernel

'''cmdline''' (string) Command line parameters. Can be used instead of cmdline.txt file

'''kernel''' (string) Alternative name to use when loading kernel.

'''kernel_address''' address to load kernel.img file at

'''ramfsfile''' (string) ramfs file to load

'''device_tree_address''' address to load device_tree at

'''init_uart_baud''' initial uart baud rate. Default 115200

'''init_uart_clock''' initial uart clock. Default 3000000

'''init_emmc_clock''' initial emmc clock. Default 80000000 (80mhz default. increasing this will speedup your SD-card)

=Overclocking configuration=
'''WARNING:''' Setting any of the parameters which over volt your Raspberry Pi will set a permanent bit within the SOC and your warranty is void. So If you care about the warranty do not adjust voltage.

Also at your own risk you can try [[RPi_config_for_your_TV|overscan settings]] from our wiki. These were [http://www.raspberrypi.org/forum/features-and-requests/should-we-make-a-wiki-page-for-overscan-settings posted] on the forum and are not confimed to work.
==Overclocking options==

{| cellpadding="2"
!Option !! Description
|-
!align="right"|arm_freq
| frequency of ARM in MHz. Default 700.
|-
!align="right"|gpu_freq
| Sets core_freq, h264_freq, isp_freq, v3d_freq together.
|-
!align="right"|core_freq
| frequency of GPU processor core in MHz. Default 250.
|-
!align="right"|h264_freq
| frequency of hardware video block in MHz. Default 250.
|-
!align="right"|isp_freq
| frequency of image sensor pipeline block in MHz. Default 250.
|-
!align="right"|v3d_freq
| frequency of 3D block in MHz. Default 250.
|-
!align="right"|sdram_freq
| frequency of SDRAM in MHz. Default 400.
|-
!align="right"|over_voltage
| ARM/GPU core voltage adjust. [-16,8] equates to [0.8V,1.4V] with 0.025V steps. Default 0 (1.2V) <ref name=voltages>What this means is that you can specify -16 and expect about 0.8V as the GPU/core voltage. This is 0.4V below the normal value of 1.2. If you specify 16, you'd get 0.4V ABOVE the normal value of 1.2V, or 1.6V. The fact that someone carefully specified "8" and "1.4V" as the upper limit in the examples leads me to think that it is likely to shorten the life of your raspberry pi significantly if you would specify values above "8". So: don't specify values above zero, but if you do, don't go above 8.</ref>
|-
!align="right"|over_voltage_sdram
| Sets over_voltage_sdram_c, over_voltage_sdram_i, over_voltage_sdram_p together
|-
!align="right"|over_voltage_sdram_c
| SDRAM controller voltage adjust. [-16,8] equates to [0.8V,1.4V] with 0.025V steps. Default 0 (1.2V) <ref name=voltages />
|-
!align="right"|over_voltage_sdram_i
| SDRAM I/O voltage adjust. [-16,8] equates to [0.8V,1.4V] with 0.025V steps. Default 0 (1.2V)<ref name=voltages />
|-
!align="right"|over_voltage_sdram_p
| SDRAM phy voltage adjust. [-16,8] equates to [0.8V,1.4V] with 0.025V steps. Default 0 (1.2V)<ref name=voltages />
|}

==Tested values==
The following table shows some successfull attempts of overclocking. These settings may not work on every device and can shorten the life of the Broadcom SoC. '''Warranty will be voided if overvoltage is used.'''
{| border="1"
! arm_freq !! gpu_freq !! core_freq !! h264_freq !! isp_freq !! v3d_freq !! sdram_freq !! over_voltage !! over_voltage_sdram
|-
|900 ||250 || || || || ||500 || ||
|-
|900 ||350 || || || || || || ||
|-
|930 ||350 || || || || ||500 || ||
|-
|1000 || ||500 || || || ||500 ||6 ||
|}

= Notes =
<references>

Talk:RPi Easy SD Card Setup

2012-05-28T14:37:53Z

Gus3: Answered, and wiki formatted.

== Question about deleting the swap partition ==

Steps 4 and 6 under section "'''Copying an image to the SD Card in Linux (command line)'''" assume that the OS will automount the USB SDCard reader. This is not the case with the current release of Debian that's listed on the [http://www.raspberrypi.org/downloads RPi downloads page]. (debian6-19-04-2012) Using the df command with this release does not provide the user with the needed information.
I do not (yet) know enough about Linux to provide easy, more reliable instructions. I was able to determine the correct device name by using "tail -f /var/log/messages" and watching for any mention of "sda" or similar while plugging/unplugging the USB SDCard reader.
--[[User:GG Crew|GG Crew]] 20:33, 16 May 2012 (UTC)

The steps currently listed under [[RPi_Easy_SD_Card_Setup#Manually_resizing_the_SD_card_on_Raspberry_Pi|Manually resizing the SD card on Raspberry Pi]] instruct the user to delete the swap partition (in order to expand the main partition), but never recreate a new swap partition. For a device as limited on RAM as the RPi, this does not seem like a good idea. Hopefully someone with more knowledge than me can update the directions, or explain why we don't need a swap partition. --[[User:GG Crew|GG Crew]] 07:21, 28 May 2012 (UTC)

: Having swap space on SSD/Flash isn't a good idea except for testing purposes. Prolonged swapping reduces the MTBF of the unit dramatically. If you're going to go to the trouble of adjusting partitions, it isn't unreasonable to move any needed swap space to some other (safer, or sacrificial) device. [[User:Gus3|Gus3]] 14:37, 28 May 2012 (UTC)

RPiconfig

2012-05-28T14:28:39Z

Gus3: Wikified an internal link.

[[Category: RaspberryPi]]

The Raspberry Pi config.txt file is read by the GPU before the ARM core is initialised. It can be used to set various system configuration parameters.

This file is an optional file on the boot partition. It would normally be accessible as /boot/config.txt from Linux.

To edit the configuration file, see the instructions at [[R-Pi_ConfigurationFile]].

=File format=

The format is "property=value". value is an integer. You may specify only one option per line. Comments may be added by starting a line with the '#' character.

Here is an example file
'''# Set stdv mode to PAL (as used in Europe)
sdtv_mode=2
# Force the monitor to HDMI mode so that sound will be sent over HDMI cable
hdmi_drive=2
# Set monitor mode to DMT
hdmi_group=2
# Set monitor resolution to 1024x768 XGA 60Hz (HDMI_DMT_XGA_60)
hdmi_mode=0x10
# Make display smaller to stop text spilling off the screen
overscan_left=20
overscan_right=12
overscan_top=10
overscan_bottom=10'''

=Video mode configuration=
==Video mode options==
'''sdtv_mode''' defines the TV standard for composite output (default=0)
sdtv_mode=0 Normal NTSC
sdtv_mode=1 Japanese version of NTSC – no pedestal
sdtv_mode=2 Normal PAL
sdtv_mode=3 Brazilian version of PAL – 525/60 rather than 625/50, different subcarrier

'''sdtv_aspect''' defines the aspect ratio for composite output (default=1)
sdtv_aspect=1 4:3
sdtv_aspect=2 14:9
sdtv_aspect=3 16:9

'''hdmi_drive''' chooses between HDMI and DVI modes
hdmi_drive= 1 Normal DVI mode (No sound)
hdmi_drive= 2 Normal HDMI mode (Sound will be sent if supported and enabled)

'''hdmi_group''' defines the HDMI type (default=1)

[rgh] I think values are 0 and 1 really, and the default 0 for CEA - at least with the latest firmware as of May 25th 2012.

hdmi_group=1 CEA
hdmi_group=2 DMT

'''hdmi_mode''' defines screen resolution in CEA or DMT format

'''These values are valid if hdmi_group=1 (CEA)'''
hdmi_mode=1 VGA
hdmi_mode=2 480p 60Hz
hdmi_mode=3 480p 60Hz H
hdmi_mode=4 720p 60Hz
hdmi_mode=5 1080i 60Hz
hdmi_mode=6 480i 60Hz
hdmi_mode=7 480i 60Hz H
hdmi_mode=8 240p 60Hz
hdmi_mode=9 240p 60Hz H
hdmi_mode=10 480i 60Hz 4x
hdmi_mode=11 480i 60Hz 4x H
hdmi_mode=12 240p 60Hz 4x
hdmi_mode=13 240p 60Hz 4x H
hdmi_mode=14 480p 60Hz 2x
hdmi_mode=15 480p 60Hz 2x H
hdmi_mode=16 1080p 60Hz
hdmi_mode=17 576p 50Hz
hdmi_mode=18 576p 50Hz H
hdmi_mode=19 720p 50Hz
hdmi_mode=20 1080i 50Hz
hdmi_mode=21 576i 50Hz
hdmi_mode=22 576i 50Hz H
hdmi_mode=23 288p 50Hz
hdmi_mode=24 288p 50Hz H
hdmi_mode=25 576i 50Hz 4x
hdmi_mode=26 576i 50Hz 4x H
hdmi_mode=27 288p 50Hz 4x
hdmi_mode=28 288p 50Hz 4x H
hdmi_mode=29 576p 50Hz 2x
hdmi_mode=30 576p 50Hz 2x H
hdmi_mode=31 1080p 50Hz
hdmi_mode=32 1080p 24Hz
hdmi_mode=33 1080p 25Hz
hdmi_mode=34 1080p 30Hz
hdmi_mode=35 480p 60Hz 4x
hdmi_mode=36 480p 60Hz 4xH
hdmi_mode=37 576p 50Hz 4x
hdmi_mode=38 576p 50Hz 4x H
hdmi_mode=39 1080i 50Hz reduced blanking
hdmi_mode=40 1080i 100Hz
hdmi_mode=41 720p 100Hz
hdmi_mode=42 576p 100Hz
hdmi_mode=43 576p 100Hz H
hdmi_mode=44 576i 100Hz
hdmi_mode=45 576i 100Hz H
hdmi_mode=46 1080i 120Hz
hdmi_mode=47 720p 120Hz
hdmi_mode=48 480p 120Hz
hdmi_mode=49 480p 120Hz H
hdmi_mode=50 480i 120Hz
hdmi_mode=51 480i 120Hz H
hdmi_mode=52 576p 200Hz
hdmi_mode=53 576p 200Hz H
hdmi_mode=54 576i 200Hz
hdmi_mode=55 576i 200Hz H
hdmi_mode=56 480p 240Hz
hdmi_mode=57 480p 240Hz H
hdmi_mode=58 480i 240Hz
hdmi_mode=59 480i 240Hz H
H means 16:9 variant (of a normally 4:3 mode).
2x means pixel doubled (i.e. highter clock rate, with each pixel repeated twice)
4x means pixel quadrupled (i.e. higher clock rate, with each pixel repeated four times)

'''These values are valid if hdmi_group=2 (DMT)'''
hdmi_mode=1 640x350 85Hz
hdmi_mode=2 640x400 85Hz
hdmi_mode=3 720x400 85Hz
hdmi_mode=4 640x480 60Hz
hdmi_mode=5 640x480 72Hz
hdmi_mode=6 640x480 75Hz
hdmi_mode=7 640x480 85Hz
hdmi_mode=8 800x600 56Hz
hdmi_mode=9 800x600 60Hz
hdmi_mode=10 800x600 72Hz
hdmi_mode=11 800x600 75Hz
hdmi_mode=12 800x600 85Hz
hdmi_mode=13 800x600 120Hz
hdmi_mode=14 848x480 60Hz
hdmi_mode=15 1024x768 43Hz DO NOT USE
hdmi_mode=16 1024x768 60Hz
hdmi_mode=17 1024x768 70Hz
hdmi_mode=18 1024x768 75Hz
hdmi_mode=19 1024x768 85Hz
hdmi_mode=20 1024x768 120Hz
hdmi_mode=21 1152x864 75Hz
hdmi_mode=22 1280x768 reduced blanking
hdmi_mode=23 1280x768 60Hz
hdmi_mode=24 1280x768 75Hz
hdmi_mode=25 1280x768 85Hz
hdmi_mode=26 1280x768 120Hz reduced blanking
hdmi_mode=27 1280x800 reduced blanking
hdmi_mode=28 1280x800 60Hz
hdmi_mode=29 1280x800 75Hz
hdmi_mode=30 1280x800 85Hz
hdmi_mode=31 1280x800 120Hz reduced blanking
hdmi_mode=32 1280x960 60Hz
hdmi_mode=33 1280x960 85Hz
hdmi_mode=34 1280x960 120Hz reduced blanking
hdmi_mode=35 1280x1024 60Hz
hdmi_mode=36 1280x1024 75Hz
hdmi_mode=37 1280x1024 85Hz
hdmi_mode=38 1280x1024 120Hz reduced blanking
hdmi_mode=39 1360x768 60Hz
hdmi_mode=40 1360x768 120Hz reduced blanking
hdmi_mode=41 1400x1050 reduced blanking
hdmi_mode=42 1400x1050 60Hz
hdmi_mode=43 1400x1050 75Hz
hdmi_mode=44 1400x1050 85Hz
hdmi_mode=45 1400x1050 120Hz reduced blanking
hdmi_mode=46 1440x900 reduced blanking
hdmi_mode=47 1440x900 60Hz
hdmi_mode=48 1440x900 75Hz
hdmi_mode=49 1440x900 85Hz
hdmi_mode=50 1440x900 120Hz reduced blanking
hdmi_mode=51 1600x1200 60Hz
hdmi_mode=52 1600x1200 65Hz
hdmi_mode=53 1600x1200 70Hz
hdmi_mode=54 1600x1200 75Hz
hdmi_mode=55 1600x1200 85Hz
hdmi_mode=56 1600x1200 120Hz reduced blanking
hdmi_mode=57 1680x1050 reduced blanking
hdmi_mode=58 1680x1050 60Hz
hdmi_mode=59 1680x1050 75Hz
hdmi_mode=60 1680x1050 85Hz
hdmi_mode=61 1680x1050 120Hz reduced blanking
hdmi_mode=62 1792x1344 60Hz
hdmi_mode=63 1792x1344 75Hz
hdmi_mode=64 1792x1344 120Hz reduced blanking
hdmi_mode=65 1856x1392 60Hz
hdmi_mode=66 1856x1392 75Hz
hdmi_mode=67 1856x1392 120Hz reduced blanking
hdmi_mode=68 1920x1200 reduced blanking
hdmi_mode=69 1920x1200 60Hz
hdmi_mode=70 1920x1200 75Hz
hdmi_mode=71 1920x1200 85Hz
hdmi_mode=72 1920x1200 120Hz reduced blanking
hdmi_mode=73 1920x1440 60Hz
hdmi_mode=74 1920x1440 75Hz
hdmi_mode=75 1920x1440 120Hz reduced blanking
hdmi_mode=76 2560x1600 reduced blanking
hdmi_mode=77 2560x1600 60Hz
hdmi_mode=78 2560x1600 75Hz
hdmi_mode=79 2560x1600 85Hz
hdmi_mode=80 2560x1600 120Hz reduced blanking
hdmi_mode=81 1366x768 60Hz
hdmi_mode=82 1080p 60Hz
hdmi_mode=83 1600x900 reduced blanking
hdmi_mode=84 2048x1152 reduced blanking
hdmi_mode=85 720p 60Hz
hdmi_mode=86 1366x768 reduced blanking

'''overscan_left''' number of pixels to skip on left

'''overscan_right''' number of pixels to skip on right

'''overscan_top''' number of pixels to skip on top

'''overscan_bottom''' number of pixels to skip on bottom

'''framebuffer_width''' console framebuffer width in pixels. Default matches display.

'''framebuffer_height''' console framebuffer height in pixels. Default matches display.

'''test_mode''' enable test sound/image during boot for manufacturing test.

'''disable_l2cache''' disable arm access to GPU's L2 cache. Needs corresponding L2 disabled kernel. Default is 0.

'''disable_overscan''' set to 1 to disable overscan.

'''hdmi_force_hotplug''' Make RPi ignore hotplug signal from display and assume it is asserted.

'''config_hdmi_boost''' configure the signal strength of the HDMI interface. Default is 0. Try 4 if you have interference issues with hdmi. 7 is the maximum.

==Which values are valid for my monitor?==
Your HDMI monitor may support only a limited set of formats. To find out which formats are supported, use the following method.

*Set the output format to VGA 60Hz (hdmi_group=1 hdmi_mode=1) and boot up the Raspberry Pi
*Enter the following command to give a list of CEA supported modes
'''/opt/vc/bin/tvservice -m CEA'''
*Enter the following command to give a list of DMT supported modes
'''/opt/vc/bin/tvservice -m DMT'''
*Enter the following command to show your current state
'''/opt/vc/bin/tvservice -s'''

=Boot options=
'''disable_commandline_tags''' Stops start.elf from filling in ATAGS (memory from 0x100) before launching kernel

'''cmdline''' (string) Command line parameters. Can be used instead of cmdline.txt file

'''kernel''' (string) Alternative name to use when loading kernel.

'''kernel_address''' address to load kernel.img file at

'''ramfsfile''' (string) ramfs file to load

'''device_tree_address''' address to load device_tree at

'''init_uart_baud''' initial uart baud rate. Default 115200

'''init_uart_clock''' initial uart clock. Default 3000000

'''init_emmc_clock''' initial emmc clock. Default 80000000

=Overclocking configuration=
'''WARNING:''' Setting any of the parameters which over volt your Raspberry Pi will set a permanent bit within the SOC and your warranty is void. So If you care about the warranty do not adjust voltage.

Also at your own risk you can try [[RPi_config_for_your_TV|overscan settings]] from our wiki. These were [http://www.raspberrypi.org/forum/features-and-requests/should-we-make-a-wiki-page-for-overscan-settings posted] on the forum and are not confimed to work.
==Overclocking options==

{| cellpadding="2"
!Option !! Description
|-
!align="right"|arm_freq
| frequency of ARM in MHz. Default 700.
|-
!align="right"|gpu_freq
| Sets core_freq, h264_freq, isp_freq, v3d_freq together.
|-
!align="right"|core_freq
| frequency of GPU processor core in MHz. Default 250.
|-
!align="right"|h264_freq
| frequency of hardware video block in MHz. Default 250.
|-
!align="right"|isp_freq
| frequency of image sensor pipeline block in MHz. Default 250.
|-
!align="right"|v3d_freq
| frequency of 3D block in MHz. Default 250.
|-
!align="right"|sdram_freq
| frequency of SDRAM in MHz. Default 400.
|-
!align="right"|over_voltage
| ARM/GPU core voltage adjust. [-16,8] equates to [0.8V,1.4V] with 0.25V steps. Default 0 (1.2V) <ref name=voltages>What this means is that you can specify -16 and expect about 0.8V as the GPU/core voltage. This is 0.4V below the normal value of 1.2. If you specify 16, you'd get 0.4V ABOVE the normal value of 1.2V, or 1.6V. The fact that someone carefully specified "8" and "1.4V" as the upper limit in the examples leads me to think that it is likely to shorten the life of your raspberry pi significantly if you would specify values above "8". So: don't specify values above zero, but if you do, don't go above 8.</ref>
|-
!align="right"|over_voltage_sdram
| Sets over_voltage_sdram_c, over_voltage_sdram_i, over_voltage_sdram_p together
|-
!align="right"|over_voltage_sdram_c
| SDRAM controller voltage adjust. [-16,8] equates to [0.8V,1.4V] with 0.25V steps. Default 0 (1.2V) <ref name=voltages />
|-
!align="right"|over_voltage_sdram_i
| SDRAM I/O voltage adjust. [-16,8] equates to [0.8V,1.4V] with 0.25V steps. Default 0 (1.2V)<ref name=voltages />
|-
!align="right"|over_voltage_sdram_p
| SDRAM phy voltage adjust. [-16,8] equates to [0.8V,1.4V] with 0.25V steps. Default 0 (1.2V)<ref name=voltages />
|}

==Tested values==
The following table shows some successfull attempts of overclocking. These settings may not work on every device and can shorten the life of the Broadcom SoC. '''Warranty will be voided if overvoltage is used.'''
{| border="1"
! arm_freq
! gpu_freq
! core_freq
! h264_freq
! isp_freq
! v3d_freq
! sdram_freq
! over_voltage
! over_voltage_sdram
|-
|900
|250
|
|
|
|
|500
|
|
|-
|900
|350
|
|
|
|
|
|
|
|-
|1000
|
|
|
|
|
|
|6
|
|}

= Notes =
<references>

RPiconfig

2012-05-28T14:22:22Z

Gus3: De-dup a line

[[Category: RaspberryPi]]

The Raspberry Pi config.txt file is read by the GPU before the ARM core is initialised. It can be used to set various system configuration parameters.

This file is an optional file on the boot partition. It would normally be accessible as /boot/config.txt from Linux.

To edit the configuration file, see the instructions at [[R-Pi_ConfigurationFile]].

=File format=

The format is "property=value". value is an integer. You may specify only one option per line. Comments may be added by starting a line with the '#' character.

Here is an example file
'''# Set stdv mode to PAL (as used in Europe)
sdtv_mode=2
# Force the monitor to HDMI mode so that sound will be sent over HDMI cable
hdmi_drive=2
# Set monitor mode to DMT
hdmi_group=2
# Set monitor resolution to 1024x768 XGA 60Hz (HDMI_DMT_XGA_60)
hdmi_mode=0x10
# Make display smaller to stop text spilling off the screen
overscan_left=20
overscan_right=12
overscan_top=10
overscan_bottom=10'''

=Video mode configuration=
==Video mode options==
'''sdtv_mode''' defines the TV standard for composite output (default=0)
sdtv_mode=0 Normal NTSC
sdtv_mode=1 Japanese version of NTSC – no pedestal
sdtv_mode=2 Normal PAL
sdtv_mode=3 Brazilian version of PAL – 525/60 rather than 625/50, different subcarrier

'''sdtv_aspect''' defines the aspect ratio for composite output (default=1)
sdtv_aspect=1 4:3
sdtv_aspect=2 14:9
sdtv_aspect=3 16:9

'''hdmi_drive''' chooses between HDMI and DVI modes
hdmi_drive= 1 Normal DVI mode (No sound)
hdmi_drive= 2 Normal HDMI mode (Sound will be sent if supported and enabled)

'''hdmi_group''' defines the HDMI type (default=1)

[rgh] I think values are 0 and 1 really, and the default 0 for CEA - at least with the latest firmware as of May 25th 2012.

hdmi_group=1 CEA
hdmi_group=2 DMT

'''hdmi_mode''' defines screen resolution in CEA or DMT format

'''These values are valid if hdmi_group=1 (CEA)'''
hdmi_mode=1 VGA
hdmi_mode=2 480p 60Hz
hdmi_mode=3 480p 60Hz H
hdmi_mode=4 720p 60Hz
hdmi_mode=5 1080i 60Hz
hdmi_mode=6 480i 60Hz
hdmi_mode=7 480i 60Hz H
hdmi_mode=8 240p 60Hz
hdmi_mode=9 240p 60Hz H
hdmi_mode=10 480i 60Hz 4x
hdmi_mode=11 480i 60Hz 4x H
hdmi_mode=12 240p 60Hz 4x
hdmi_mode=13 240p 60Hz 4x H
hdmi_mode=14 480p 60Hz 2x
hdmi_mode=15 480p 60Hz 2x H
hdmi_mode=16 1080p 60Hz
hdmi_mode=17 576p 50Hz
hdmi_mode=18 576p 50Hz H
hdmi_mode=19 720p 50Hz
hdmi_mode=20 1080i 50Hz
hdmi_mode=21 576i 50Hz
hdmi_mode=22 576i 50Hz H
hdmi_mode=23 288p 50Hz
hdmi_mode=24 288p 50Hz H
hdmi_mode=25 576i 50Hz 4x
hdmi_mode=26 576i 50Hz 4x H
hdmi_mode=27 288p 50Hz 4x
hdmi_mode=28 288p 50Hz 4x H
hdmi_mode=29 576p 50Hz 2x
hdmi_mode=30 576p 50Hz 2x H
hdmi_mode=31 1080p 50Hz
hdmi_mode=32 1080p 24Hz
hdmi_mode=33 1080p 25Hz
hdmi_mode=34 1080p 30Hz
hdmi_mode=35 480p 60Hz 4x
hdmi_mode=36 480p 60Hz 4xH
hdmi_mode=37 576p 50Hz 4x
hdmi_mode=38 576p 50Hz 4x H
hdmi_mode=39 1080i 50Hz reduced blanking
hdmi_mode=40 1080i 100Hz
hdmi_mode=41 720p 100Hz
hdmi_mode=42 576p 100Hz
hdmi_mode=43 576p 100Hz H
hdmi_mode=44 576i 100Hz
hdmi_mode=45 576i 100Hz H
hdmi_mode=46 1080i 120Hz
hdmi_mode=47 720p 120Hz
hdmi_mode=48 480p 120Hz
hdmi_mode=49 480p 120Hz H
hdmi_mode=50 480i 120Hz
hdmi_mode=51 480i 120Hz H
hdmi_mode=52 576p 200Hz
hdmi_mode=53 576p 200Hz H
hdmi_mode=54 576i 200Hz
hdmi_mode=55 576i 200Hz H
hdmi_mode=56 480p 240Hz
hdmi_mode=57 480p 240Hz H
hdmi_mode=58 480i 240Hz
hdmi_mode=59 480i 240Hz H
H means 16:9 variant (of a normally 4:3 mode).
2x means pixel doubled (i.e. highter clock rate, with each pixel repeated twice)
4x means pixel quadrupled (i.e. higher clock rate, with each pixel repeated four times)

'''These values are valid if hdmi_group=2 (DMT)'''
hdmi_mode=1 640x350 85Hz
hdmi_mode=2 640x400 85Hz
hdmi_mode=3 720x400 85Hz
hdmi_mode=4 640x480 60Hz
hdmi_mode=5 640x480 72Hz
hdmi_mode=6 640x480 75Hz
hdmi_mode=7 640x480 85Hz
hdmi_mode=8 800x600 56Hz
hdmi_mode=9 800x600 60Hz
hdmi_mode=10 800x600 72Hz
hdmi_mode=11 800x600 75Hz
hdmi_mode=12 800x600 85Hz
hdmi_mode=13 800x600 120Hz
hdmi_mode=14 848x480 60Hz
hdmi_mode=15 1024x768 43Hz DO NOT USE
hdmi_mode=16 1024x768 60Hz
hdmi_mode=17 1024x768 70Hz
hdmi_mode=18 1024x768 75Hz
hdmi_mode=19 1024x768 85Hz
hdmi_mode=20 1024x768 120Hz
hdmi_mode=21 1152x864 75Hz
hdmi_mode=22 1280x768 reduced blanking
hdmi_mode=23 1280x768 60Hz
hdmi_mode=24 1280x768 75Hz
hdmi_mode=25 1280x768 85Hz
hdmi_mode=26 1280x768 120Hz reduced blanking
hdmi_mode=27 1280x800 reduced blanking
hdmi_mode=28 1280x800 60Hz
hdmi_mode=29 1280x800 75Hz
hdmi_mode=30 1280x800 85Hz
hdmi_mode=31 1280x800 120Hz reduced blanking
hdmi_mode=32 1280x960 60Hz
hdmi_mode=33 1280x960 85Hz
hdmi_mode=34 1280x960 120Hz reduced blanking
hdmi_mode=35 1280x1024 60Hz
hdmi_mode=36 1280x1024 75Hz
hdmi_mode=37 1280x1024 85Hz
hdmi_mode=38 1280x1024 120Hz reduced blanking
hdmi_mode=39 1360x768 60Hz
hdmi_mode=40 1360x768 120Hz reduced blanking
hdmi_mode=41 1400x1050 reduced blanking
hdmi_mode=42 1400x1050 60Hz
hdmi_mode=43 1400x1050 75Hz
hdmi_mode=44 1400x1050 85Hz
hdmi_mode=45 1400x1050 120Hz reduced blanking
hdmi_mode=46 1440x900 reduced blanking
hdmi_mode=47 1440x900 60Hz
hdmi_mode=48 1440x900 75Hz
hdmi_mode=49 1440x900 85Hz
hdmi_mode=50 1440x900 120Hz reduced blanking
hdmi_mode=51 1600x1200 60Hz
hdmi_mode=52 1600x1200 65Hz
hdmi_mode=53 1600x1200 70Hz
hdmi_mode=54 1600x1200 75Hz
hdmi_mode=55 1600x1200 85Hz
hdmi_mode=56 1600x1200 120Hz reduced blanking
hdmi_mode=57 1680x1050 reduced blanking
hdmi_mode=58 1680x1050 60Hz
hdmi_mode=59 1680x1050 75Hz
hdmi_mode=60 1680x1050 85Hz
hdmi_mode=61 1680x1050 120Hz reduced blanking
hdmi_mode=62 1792x1344 60Hz
hdmi_mode=63 1792x1344 75Hz
hdmi_mode=64 1792x1344 120Hz reduced blanking
hdmi_mode=65 1856x1392 60Hz
hdmi_mode=66 1856x1392 75Hz
hdmi_mode=67 1856x1392 120Hz reduced blanking
hdmi_mode=68 1920x1200 reduced blanking
hdmi_mode=69 1920x1200 60Hz
hdmi_mode=70 1920x1200 75Hz
hdmi_mode=71 1920x1200 85Hz
hdmi_mode=72 1920x1200 120Hz reduced blanking
hdmi_mode=73 1920x1440 60Hz
hdmi_mode=74 1920x1440 75Hz
hdmi_mode=75 1920x1440 120Hz reduced blanking
hdmi_mode=76 2560x1600 reduced blanking
hdmi_mode=77 2560x1600 60Hz
hdmi_mode=78 2560x1600 75Hz
hdmi_mode=79 2560x1600 85Hz
hdmi_mode=80 2560x1600 120Hz reduced blanking
hdmi_mode=81 1366x768 60Hz
hdmi_mode=82 1080p 60Hz
hdmi_mode=83 1600x900 reduced blanking
hdmi_mode=84 2048x1152 reduced blanking
hdmi_mode=85 720p 60Hz
hdmi_mode=86 1366x768 reduced blanking

'''overscan_left''' number of pixels to skip on left

'''overscan_right''' number of pixels to skip on right

'''overscan_top''' number of pixels to skip on top

'''overscan_bottom''' number of pixels to skip on bottom

'''framebuffer_width''' console framebuffer width in pixels. Default matches display.

'''framebuffer_height''' console framebuffer height in pixels. Default matches display.

'''test_mode''' enable test sound/image during boot for manufacturing test.

'''disable_l2cache''' disable arm access to GPU's L2 cache. Needs corresponding L2 disabled kernel. Default is 0.

'''disable_overscan''' set to 1 to disable overscan.

'''hdmi_force_hotplug''' Make RPi ignore hotplug signal from display and assume it is asserted.

'''config_hdmi_boost''' configure the signal strength of the HDMI interface. Default is 0. Try 4 if you have interference issues with hdmi. 7 is the maximum.

==Which values are valid for my monitor?==
Your HDMI monitor may support only a limited set of formats. To find out which formats are supported, use the following method.

*Set the output format to VGA 60Hz (hdmi_group=1 hdmi_mode=1) and boot up the Raspberry Pi
*Enter the following command to give a list of CEA supported modes
'''/opt/vc/bin/tvservice -m CEA'''
*Enter the following command to give a list of DMT supported modes
'''/opt/vc/bin/tvservice -m DMT'''
*Enter the following command to show your current state
'''/opt/vc/bin/tvservice -s'''

=Boot options=
'''disable_commandline_tags''' Stops start.elf from filling in ATAGS (memory from 0x100) before launching kernel

'''cmdline''' (string) Command line parameters. Can be used instead of cmdline.txt file

'''kernel''' (string) Alternative name to use when loading kernel.

'''kernel_address''' address to load kernel.img file at

'''ramfsfile''' (string) ramfs file to load

'''device_tree_address''' address to load device_tree at

'''init_uart_baud''' initial uart baud rate. Default 115200

'''init_uart_clock''' initial uart clock. Default 3000000

'''init_emmc_clock''' initial emmc clock. Default 80000000

=Overclocking configuration=
'''WARNING:''' Setting any of the parameters which over volt your Raspberry Pi will set a permanent bit within the SOC and your warranty is void. So If you care about the warranty do not adjust voltage.

Also at your own risk you can try [http://elinux.org/RPi_config_for_your_TV overscan settings] from our wiki. These were [http://www.raspberrypi.org/forum/features-and-requests/should-we-make-a-wiki-page-for-overscan-settings posted] on the forum and are not confimed to work.
==Overclocking options==

{| cellpadding="2"
!Option !! Description
|-
!align="right"|arm_freq
| frequency of ARM in MHz. Default 700.
|-
!align="right"|gpu_freq
| Sets core_freq, h264_freq, isp_freq, v3d_freq together.
|-
!align="right"|core_freq
| frequency of GPU processor core in MHz. Default 250.
|-
!align="right"|h264_freq
| frequency of hardware video block in MHz. Default 250.
|-
!align="right"|isp_freq
| frequency of image sensor pipeline block in MHz. Default 250.
|-
!align="right"|v3d_freq
| frequency of 3D block in MHz. Default 250.
|-
!align="right"|sdram_freq
| frequency of SDRAM in MHz. Default 400.
|-
!align="right"|over_voltage
| ARM/GPU core voltage adjust. [-16,8] equates to [0.8V,1.4V] with 0.25V steps. Default 0 (1.2V) <ref name=voltages>What this means is that you can specify -16 and expect about 0.8V as the GPU/core voltage. This is 0.4V below the normal value of 1.2. If you specify 16, you'd get 0.4V ABOVE the normal value of 1.2V, or 1.6V. The fact that someone carefully specified "8" and "1.4V" as the upper limit in the examples leads me to think that it is likely to shorten the life of your raspberry pi significantly if you would specify values above "8". So: don't specify values above zero, but if you do, don't go above 8.</ref>
|-
!align="right"|over_voltage_sdram
| Sets over_voltage_sdram_c, over_voltage_sdram_i, over_voltage_sdram_p together
|-
!align="right"|over_voltage_sdram_c
| SDRAM controller voltage adjust. [-16,8] equates to [0.8V,1.4V] with 0.25V steps. Default 0 (1.2V) <ref name=voltages />
|-
!align="right"|over_voltage_sdram_i
| SDRAM I/O voltage adjust. [-16,8] equates to [0.8V,1.4V] with 0.25V steps. Default 0 (1.2V)<ref name=voltages />
|-
!align="right"|over_voltage_sdram_p
| SDRAM phy voltage adjust. [-16,8] equates to [0.8V,1.4V] with 0.25V steps. Default 0 (1.2V)<ref name=voltages />
|}

==Tested values==
The following table shows some successfull attempts of overclocking. These settings may not work on every device and can shorten the life of the Broadcom SoC. '''Warranty will be voided if overvoltage is used.'''
{| border="1"
! arm_freq
! gpu_freq
! core_freq
! h264_freq
! isp_freq
! v3d_freq
! sdram_freq
! over_voltage
! over_voltage_sdram
|-
|900
|250
|
|
|
|
|500
|
|
|-
|900
|350
|
|
|
|
|
|
|
|-
|1000
|
|
|
|
|
|
|6
|
|}

= Notes =
<references>

User:Gus3

2012-05-24T13:58:58Z

Gus3: adding my own review

Got my RPi on 2012-April-19. Currently running the customized Debian image, since I know a little more about Debian than the other supported distros (Arch, Fedora).

== Slackware on the Pi ==

One of my project ideas will be to get [http://www.armedslack.org/ Slackware ARM] running on the RPi. I would think that the Debian kernel and modules, with Slackware ARM userspace, could be hacked together to work, but that's only an uneducated guess. Slackware ARM currently has three installer images, for the three supported platforms; I eagerly await the fourth, Raspberry Pi.

=== 2012-05-02, late evening ===

I have a Slackware ARM setup that crashes in /etc/rc.d/rc.S. But at least that means /sbin/init is running from the flash card. Yay!

=== 2012-05-03 ===

It turns out the SD card and my desktop's reader have some kind of conflict, and e2fsck's clean-up sent many critical libraries to /lost+found/. Another file that disappeared was /etc/fstab. Not good. My netbook's card reader works OK with the card, so I'm re-installing the libraries now. We'll see what else got clobbered, but the libraries are the most important thing to repair.

=== 2012-05-08 ===

It works! My basic idea above (Debian kernel, Slackware ARM userspace), using the packages outlined [http://wiki.linuxquestions.org/wiki/Slackware-Minimal_Install here], has given me an RPi that works on the network. The installation is 291M (in a 1.5G partition), with DHCP, without X.

Now, to clean it up and find a way to get it online. Suggestions welcome for hosting/distribution; I can't host it myself.

=== 2012-05-21 ===

A rather sad discovery: The Raspberry Pi has a built-in FPU, but Slackware ARM isn't built for it. The math library (libm) has only a few instances of FPU instructions, and they appear to be for FPU state management, not computation. I don't know how much this slows down the overall system. A lot of programs link in libm, even some which I doubt actually use it (e.g. vim). The first package I should (attempt to) recompile is glibc, which might get an overall speed gain.

== Cooling systems for the Pi ==

I've done a few little experiments with auxiliary cooling for the Raspberry Pi. You can read the report [http://mindplusplus.wordpress.com/2012/05/14/the-raspberry-pi-my-first-hardware-experiment/ here].

== Reviewing the RPi ==

I've had the Raspberry Pi for a month, so I thought it time to review it [http://mindplusplus.wordpress.com/2012/05/23/the-raspberry-pi-a-review/ here].

User:Gus3

2012-05-21T04:41:10Z

Gus3: RPi has FPU, but stock Slackware ARM doesn't support it. :(

Got my RPi on 2012-April-19. Currently running the customized Debian image, since I know a little more about Debian than the other supported distros (Arch, Fedora).

== Slackware on the Pi ==

One of my project ideas will be to get [http://www.armedslack.org/ Slackware ARM] running on the RPi. I would think that the Debian kernel and modules, with Slackware ARM userspace, could be hacked together to work, but that's only an uneducated guess. Slackware ARM currently has three installer images, for the three supported platforms; I eagerly await the fourth, Raspberry Pi.

=== 2012-05-02, late evening ===

I have a Slackware ARM setup that crashes in /etc/rc.d/rc.S. But at least that means /sbin/init is running from the flash card. Yay!

=== 2012-05-03 ===

It turns out the SD card and my desktop's reader have some kind of conflict, and e2fsck's clean-up sent many critical libraries to /lost+found/. Another file that disappeared was /etc/fstab. Not good. My netbook's card reader works OK with the card, so I'm re-installing the libraries now. We'll see what else got clobbered, but the libraries are the most important thing to repair.

=== 2012-05-08 ===

It works! My basic idea above (Debian kernel, Slackware ARM userspace), using the packages outlined [http://wiki.linuxquestions.org/wiki/Slackware-Minimal_Install here], has given me an RPi that works on the network. The installation is 291M (in a 1.5G partition), with DHCP, without X.

Now, to clean it up and find a way to get it online. Suggestions welcome for hosting/distribution; I can't host it myself.

=== 2012-05-21 ===

A rather sad discovery: The Raspberry Pi has a built-in FPU, but Slackware ARM isn't built for it. The math library (libm) has only a few instances of FPU instructions, and they appear to be for FPU state management, not computation. I don't know how much this slows down the overall system. A lot of programs link in libm, even some which I doubt actually use it (e.g. vim). The first package I should (attempt to) recompile is glibc, which might get an overall speed gain.

== Cooling systems for the Pi ==

I've done a few little experiments with auxiliary cooling for the Raspberry Pi. You can read the report [http://mindplusplus.wordpress.com/2012/05/14/the-raspberry-pi-my-first-hardware-experiment/ here].

R-Pi ConfigurationFile

2012-05-17T23:22:56Z

Gus3: sensible link

How to edit the boot configuration file for Raspberry Pi

=A quick overview=

While booting up, the Raspberry Pi reads some configuration parameters from the SD card.
These parameters are stored in a file named [[RPi_config.txt|config.txt]]. This file is within the part of the SD card which
is visible to Windows PCs. Therefore, you can edit this configuration file from a Windows PC, from a Mac,
from a Linux PC, or from within the Raspberry Pi itself.

This configuration file contains instructions which are necessary to setup the display.
If you have severe problems with the display, you will need to connect the SD card to a PC so that
you can edit the configuration file. If the display is working but you wish to make minor adjustments,
you may find it more convenient to edit the file from within the Raspberry Pi itself.

=How to edit from a Windows PC=
This method is most useful if you cannot see anything on the display of the Raspberry Pi.

*Shut down your Raspberry Pi, remove the power and remove the SD card.

*Put the SD card in your PC's card reader and wait for the folder to open automatically.

*If the folder does not open automatically, open "My Computer" and then open the drive marked "SD".

*Look to see if there is a file called config (or possibly config.txt).

*If this file exists, open it with Notepad. If not, create the file with Notepad.
(One way to do this, in XP, is to right-click where you see the other files, select New and then Text document.
Then change "New Text Document" to "config").

*Open config.txt using Notepad, and add the necessary configuration parameters.

*Save the file (menu item File, Save)

*Exit Notepad

*In Windows Explorer, go to "My Computer". Right-click on the SD card and select "Safely Remove".

*Remove the SD card from the PC and insert it in the Raspberry Pi.

=How to edit from the Raspberry Pi=

*Reboot the Raspberry Pi and enter your username and password.

*To edit the configuration file, enter the command
sudo nano /boot/config.txt

*Type in the necessary configuration parameters

*Save the edited file
Press Control-x
Press y
Press [enter]

*After exiting the editor, restart using the command
sudo reboot

=An example configuration file=

This example show how to reduce the size of the display to prevent text spilling off the edge of the screen.

<pre>

overscan_left=20

overscan_right=20

overscan_top=20

overscan_bottom=20

</pre>

User:Gus3

2012-05-14T22:56:47Z

Gus3: Cooling the RPi

RPi Distributions

2012-05-14T14:42:22Z

Gus3: typo

[[Category: Linux]]
[[Category:ARM Development Boards]]
[[Category: Broadcom]]
[[Category: Development Boards]]
[[Category: RaspberryPi]]
[[Category: Education]]
{{Template:RPi_Software}}

=Available Distributions=

{| class="wikitable" style="text-align: center; width: 750px; height: 200px;"
|+ Operational Systems for Raspberry Pi models A and B
|-
!
! [http://archlinuxarm.org/ Arch Linux ARM]
! [http://www.debian.org/ports/arm/ Debian ARM]
! [http://fedoraproject.org/wiki/Architectures/ARM Fedora Remix]
! [http://wiki.meego.com/User:Vgrade#Raspberry_Pi Meego MER + XBMC]
! [http://en.wikipedia.org/wiki/RISC_OS Risc OS]
! [http://openelec.tv/component/k2/item/235-openelec-on-raspberry-pi-our-first-arm-device-supported OpenELEC + XBMC]
! [http://www.raspbian.org/ Raspbian]
! [http://wiki.qt-project.org/QtonPi QtonPi]
|-
! Latest version
| 29/04/2012
| Squeeze
(19/04/2012)
| F14 Remix R1
|
|
|
| Wheezy
| F14 Remix R1
|-
! First version
| 01/03/2012
| Squeeze
(16/02/2012)
| F14 Remix R1
|
|
|
| Wheezy
| F14 Remix R1
|-
! Type
| Linux
| Linux
| Linux
| Linux (embedded)
| ARM RISC OS
| Linux (embedded)
| Linux (hard float)
|-
! License
| [http://www.opensource.org/licenses/gpl-2.0.php OSI GPLv2]
| [http://www.debian.org/legal/licenses/ Core: OSI, mixed]
(GPLv2, BSD, etc)
| [http://fedoraproject.org/wiki/Licensing:Main OSI, mixed]
(GPLv2, BSD, etc)
| [http://www.opensource.org/licenses/index.html OSI, mixed]
(GPLv2, BSD, etc)
| [http://www.riscosopen.org/content/documents/ssfaq Shared Source]
| [http://www.opensource.org/licenses/index.html OSI, mixed]
(GPLv2, BSD, etc)
| [http://www.debian.org/legal/licenses/ Core: OSI, mixed]
(GPLv2, BSD, etc)
|-
! Memory footprint
|
|
|
| ~34 MiB + XBMC
|
| 80 MiB (inc. XBMC)
|
|-
! Image/Installer
| [http://downloads.raspberrypi.org/download.php?file=/images/archlinuxarm/archlinuxarm-29-04-2012/archlinuxarm-29-04-2012.zip raw image]
| [http://downloads.raspberrypi.org/images/debian/6/debian6-19-04-2012/debian6-19-04-2012.zip raw image]
| Fedora RPM: [http://files.velocix.com/c1410/fedora/installer/fedora/fedora-arm-installer-1.0.0-1.fc16.noarch.rpm installer] 
Windows Zip: [http://files.velocix.com/c1410/fedora/installer/windows/fedora-arm-installer-1.0.0.zip installer] 
Other Linux: [http://files.velocix.com/c1410/fedora/installer/source/faii-1.0.0.tar.gz Python script]
|
|
| [http://openelec.tv/component/k2/item/241-openelec-meets-raspberry-pi-part-1 build instructions] 
[http://openelec.tv/component/k2/item/242-openelec-meets-raspberry-pi-part-2 install instructions]
| [http://distribution.hexxeh.net/raspbian/raspbian-r2.zip pi image] 
[http://debian.raspbian.com/qemu/ qemu image]
| [http://downloads.raspberrypi.org/images/qtonpi/qtonpi-0.02/qtonpi-0.2.tar.bz2 qt 5 sdk + sdcard image]
|-
! Packages
| [http://archlinuxarm.org/arm/ {{formatnum:4416}}]?
| [http://packages.debian.org/stable/allpackages {{formatnum:20000}}+]
| [http://dl.fedoraproject.org/pub/fedora-secondary/releases/14/Everything/arm/os/Packages/ {{formatnum:16464}}]?
| [http://gitweb.merproject.org/gitweb/ ~{{formatnum:320}}] (core)
|
| ~140
| [http://www.raspberrypi.org/forum/projects-and-collaboration-general/debian-hard-float-armhf-for-rpi/page-20#p74383 {{formatnum:25000}}+]
|-
! Default login
| Username: root Password: root
| Username: pi Password: raspberry
| Username: root Password: fedoraarm
|
|
|
| Username: root Password: hexxeh
| Username: root Password: rootme Username: qtonpi Password: qtonpi
|}

==Fedora Remix==

As announced on February 20, 2012 [http://www.raspberrypi.org/archives/676]: [http://cdot.senecac.on.ca/raspberrypi Raspberry Pi Fedora Remix 14], developed by [http://senecacollege.ca Seneca College], is the recommended distribution for newcomers to Raspberry Pi and day-to-day use. Pre-loaded SD cards with this distribution are planned to be available at some point after the initial launch through the Raspberry Pi Store.

Eben says (regarding default distribution): "Either Ubuntu or Fedora; the main point in Fedora’s favour is their ongoing support for ARMv6 architectures."

[http://fedoraproject.org/wiki/Architectures/ARM http://fedoraproject.org/wiki/Architectures/ARM]

As of October 15 2011: the Raspberry Pi alpha board boots Fedora F13 (armv5tel) to a character-mode login prompt in about 23 seconds, taking 14-17MB of memory. XFCE and LXDE graphical environments are both available (but more work on the X drivers is needed). F15-ARM will be tested as its release date approaches in November. A 1-minute video is available at [http://www.raspberrypi.org/?p=254]. Video about Seneca College and Fedora on Raspberry Pi: [http://www.raspberrypi.org/archives/298]

'''Link''': to Raspberry Pi Fedora Remix wiki pages [http://zenit.senecac.on.ca/wiki/index.php/Raspberry_Pi_Fedora_Remix]

==== What is the Raspberry Pi Fedora Remix? ====

The Remix is a distribution comprised of software packages from the Fedora ARM project, plus a small number of additional packages that are modified from the Fedora versions or which cannot be included in Fedora due to licensing issues – in particular, the libraries for accessing the VideoCore GPU on the Raspberry Pi.

The SD card image for the Remix includes a little over 640 packages, providing both text-mode and graphical interfaces (LXDE/XFCE) with an assortment of programming languages, applications, system tools, and services for both environments. There are over 16,000 software packages available from the Fedora ARM repositories which can be easily installed using the Internet to customize your system to meet your needs and interests (again, using either command-line or graphical tools).

Some of the highlights of the software included in the SD card image:

* Programming languages: python, perl, ruby, bash
* Version control: git
* System administration tools (command line and/or graphical) for configuring various aspects of the system including the network, date/time, users, and printers
* Command-line and graphical tools for installing/removing/updating software
ssh (secure remote login) and printer services
* Graphical applications: word processing (AbiWord), spreadsheets (Gnumeric), image editing (GIMP), and web browsing (Firefox)
* Editors for programming: vim (text mode) and gedit with plugins for file management, terminal, and python console (graphical mode)

==== The Kernel ====

The Kernel provided in the Remix image is the Raspberry Pi 3.1.9 kernel from GitHub, with a combined Fedora/Raspberry Pi configuration file. This configuration includes the devices in the System-on-a-Chip, modular support for most USB devices and optional network features, and kernel features expected by Fedora packages, including IPv6.

==== Raspberry Pi Libraries ====

The Raspberry Pi proprietary libraries, headers, and utilities, included in /opt/vc in the Debian image, are installed into regular system locations in the Fedora Remix image (/usr/lib for libraries, /usr/include for headers, and /usr/bin and /usr/sbin for utilities). This reflects the fact that these files are part of the core distribution and not a third-party add-one.

The source code for the demonstration multimedia apps is contained in the /usr/share/vc-demo-source directory. Instructions for compiling and using these apps is on the Raspberry Pi Fedora Remix wiki documentation (see link, below).

==== Repositories ====

The kernel, GPU firmware, start-up scripts, and proprietary libraries/headers/demo source are all provided by RPM packages. This software, along with all of the Fedora packages, can be installed/removed/reinstalled/updated from online software repositories. This means that if new GPU firmware or multimedia libraries become available, they can be installed with a simple update command (“yum update”) or a mouse click on the graphical software updater.

The Remix is distributed as four separate pieces, carried by three separate mirror networks:

* The SD card image files are being mirrored by the Raspberry Pi community’s mirror network.
* The Velocix content delivery network is mirroring the installer program plus the Raspberry Pi-specific remix package repositories.
* The Fedora mirror network is mirroring the Fedora ARM package repositories.
Many thanks to Liam Fraser and the sites comprising the three mirror networks.

==== The Future of the Raspberry Pi Fedora Remix ====

From Chris Tyler ([http://zenit.senecac.on.ca/wiki/index.php/Main_Page Seneca College], part of the [http://fedoraproject.org/ Fedora Project]) on 8th March 2012 :

"The Fedora ARM project is hard at work building Fedora 17, which we hope to release concurrently with the PC versions in May. This should be the most complete Fedora ARM release produced to date.

Students in the SBR600 course at Seneca College are working to on an improved version of the Remix incorporating files from Fedora ARM 17, and this will also be released in May.

The Fedora ARM project has the goal of achieving primary architecture status during the Fedora 18 development cycle — which means that, from that point on, the ARM build of Fedora will receive the same priority and be released on the same schedule as the PC (x86) versions.

As this project progresses, we anticipate moving most of the Raspberry Pi-specific software packages into the main Fedora ARM project, except where prevented by licensing issues."

==== More Information ====

Release notes, information on where/how to get help or to get involved, FAQ about the Remix, and more are on the Seneca CDOT wiki at http://cdot.senecac.on.ca/raspberrypi.

==== A Quick Word on Trademarks ====

Important note from Chris Tyler :

"This software distribution is counted as a “Fedora Remix” in the terminology of the Fedora project because it contains software not found in the Fedora package collection. Please do not refer to the Remix as “Fedora” or use the Fedora infinity logo or wordmark in conjunction with the remix – please refer to it as a “Fedora Remix” and use the secondary mark in accordance with the [http://fedoraproject.org/wiki/Legal:Trademark_guidelines Fedora Trademark Guidelines]. (Note that we have specific approval to use the Secondary Mark with a modified colour scheme to match the Raspberry Pi logo)."

==Debian (Squeeze)==

[http://www.debian.org/ports/arm/ http://www.debian.org/ports/arm/]

[http://www.debian.org/ Debian] was the default distribution on the Alpha boards. Boot time depends on width & speed of SD-card. Alpha board boot into Debian prompt (no GUI) was timed taking about 34 seconds.

The Debian distro for Raspberry Pi is the Cambridge reference filesystem, which is a fully functional Debian Squeeze installation containing LXDE (desktop) and Midori (browser); development tools; and sample code for accessing the multimedia functionality on the device.

==Arch==

[http://archlinuxarm.org Arch Linux ARM] is based on [http://www.archlinux.org/ Arch Linux], which aims for simplicity and full control to the end user. It provides a lightweight base structure that allows you to shape the system to your needs. For this reason, the Arch Linux ARM image for the Raspberry Pi does not come with a graphical user interface, though you can easily install one yourself. Please note that this distribution may not be suitable for beginners.

Arch Linux ARM is on a rolling-release cycle that can be updated daily through small packages instead of huge updates every few months.

More information is available at http://archlinuxarm.org

==Raspbian==

Raspberry Pi + Debian = [http://www.raspbian.org Raspbian]. A project to create a hard float port of Debian Wheezy armhf for the Raspberry Pi. The intent of Raspbian is to bring to the Raspberry Pi user 10,000s of pre-built Debian packages specifically tuned for optimal performance on the Raspberry Pi hardware. The project is still in it's early phases, but the major push to rebuild nearly all Debian packages for the Raspberry Pi is expected to be completed by the end of May, 2012. After that, efforts will focus on making Raspbian the easiest to use, most stable and best performing Linux distribution available for the Raspberry Pi.

More information is available at http://www.raspbian.org

=Announced distributions=

The following distributions have been announced and may have been publicly demonstrated but distributions are not generally available quite yet.

==Gentoo==

Gentoo Linux is a computer operating system built on top of the Linux kernel and based on the Portage package management system. It is distributed as free and open source software. Unlike a conventional software distribution, the user compiles the source code locally according to their chosen configuration. There are normally no precompiled binaries for software although for convenience some software packages (such as Mozilla Firefox and LibreOffice) are also available as precompiled binaries for various architectures where compiling would otherwise be very time consuming.

Discuss: [http://www.raspberrypi.org/forum/?mingleforumaction=viewtopic&t=462 http://www.raspberrypi.org/forum/?mingleforumaction=viewtopic&t=462]

==KidsRuby==

KidsRuby is what it sounds like – a Ruby for kids – and it’s running beautifully on the Raspberry Pi. This is exactly the sort of application we want to see on the device, and we’re really pleased to see it up and running. It looks like there will be some optimisation for speed before we launch, but what’s there already is very useable.

R.Pi blog entry: [http://www.raspberrypi.org/2011/09/kidsruby-on-raspberry-pi-another-video-demo/ http://www.raspberrypi.org/2011/09/kidsruby-on-raspberry-pi-another-video-demo/]
More info & Video: [http://confreaks.net/videos/637-gogaruco2011-kidsruby-think-of-the-children?player=html5 http://confreaks.net/videos/637-gogaruco2011-kidsruby-think-of-the-children?player=html5]

==Meego MER & XBMC==

The MeeGo MER project provides a Linux-based, open source software platform for the next generation of computing devices. The MeeGo MER software platform is designed to give developers the broadest range of device segments to target for their applications, including netbooks, handheld computing and communications devices, in-vehicle infotainment devices, smart TVs, tablets and more – all using a uniform set of APIs based on Qt. XBMC is an award-winning free and open source (GPL) software media player and entertainment hub for digital media. Meego TV 1.2 uses XBMC as a reference GUI (that is, a starting point for creating a custom GUI).

* [http://www.madeo.co.uk/?p=783 http://www.madeo.co.uk/?p=783]
* [http://www.madeo.co.uk/?page_id=605 http://www.madeo.co.uk/?page_id=605]
* [http://wiki.meego.com/User:Vgrade#Raspberry_Pi http://wiki.meego.com/User:Vgrade#Raspberry_Pi]
* [http://wiki.merproject.org/wiki/Community_Workspace/RaspberryPi http://wiki.merproject.org/wiki/Community_Workspace/RaspberryPi]
* [https://github.com/xbmc/xbmc-rbp https://github.com/xbmc/xbmc-rbp]

==OpenELEC==

OpenELEC is an embedded operating system built specifically to run [http://www.xbmc.org XBMC], the open source entertainment media hub. The idea behind OpenELEC is to allow people to use their Home Theatre PC (HTPC) like any other device you might have attached to your TV, like a DVD player or Sky box. Instead of having to manage a full operating system, configure it and install the packages required to turn it into a hybrid media center, OpenELEC is designed to be simple to install, manage and use, making it more like running a set-top box than a full-blown computer.

*[http://www.openelec.tv OpenELEC Mainsite]
*In February 2012, OpenELEC.tv announced their [http://openelec.tv/component/k2/item/235-openelec-on-raspberry-pi-our-first-arm-device-supported ARM port for Raspberry Pi]
*[http://openelec.tv/forum/90-miscellaneous/11763-raspberry-pi OpenELEC forum] thread
*[http://www.raspberrypi.org/forum/general-discussion/openelec RaspberryPi forum] thread
*[http://elinux.org/Rpi_openELEC Raspberry Pi build instructions for OpenELEC]

==Puppy==

[http://puppylinux.org/wikka/PARM Puppy] is the number one small Linux. [http://en.wikipedia.org/wiki/Puppy_Linux Puppy Linux] is going back to his roots. Designed to run from 256MB ram. Making every bit count. Join the [http://www.murga-linux.com/puppy/viewtopic.php?p=526#526 Puppy geek adventure] for 2012. Woof Woof

==RISC OS==

RISC OS is a fast and lightweight computer operating system designed in Cambridge, England by [http://en.wikipedia.org/wiki/Acorn_Computers Acorn]. First released in 1987, its origins can be traced back to the original team that developed the ARM microprocessor. RISC OS includes [http://en.wikipedia.org/wiki/BBC_BASIC BBC BASIC] which was primarily conceived to teach programming skills as part of the BBC computer literacy project.

*[http://www.riscosopen.org/ RISC OS Open] (ROOL) has released the sources. Community members have ported the OS to the BeagleBoard and similar hardware
*In November 2011, RISCOScode.com announced that [http://www.riscoscode.com/Pages/Item0113.html RISC OS will be available as an alternative OS] for Raspberry Pi from launch
*[http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&t=919 RaspberryPi forum] thread
*[http://www.riscosopen.org/forum/forums/5/topics/783 ROOL forum] thread

==Bodhi Linux==
Bodhi Linux is a small Linux distribution using the Enlightenment window manager and the ARM build is based on Debian.
*[http://forums.bodhilinux.com/index.php?/topic/2472-what-about-the-raspberry-pi/ what-about-the-raspberry-pi] Forum thread
*[http://jeffhoogland.blogspot.com/2011/11/bodhi-linux-arm-repository-online.html bodhi-linux-arm-repository-online] Developer Blog
*[http://jeffhoogland.blogspot.com/2011/11/one-year-with-bodhi-linux.html one-year-with-bodhi-linux ] Developer Blog

=Other Distributions=

These are other popular distributions that are often asked about for Raspberry Pi but are not available.

==Android==

[http://www.arm.com/community/software-enablement/google/solution-center-android/index.php http://www.arm.com/community/software-enablement/google/solution-center-android/index.php]

Discuss: [http://www.raspberrypi.org/forum/?mingleforumaction=viewtopic&t=144 http://www.raspberrypi.org/forum/?mingleforumaction=viewtopic&t=144]

==GeeXboX ARM==

GeeXboX is a free and Open Source Media-Center purposed Linux distribution for embedded devices and desktop computers. GeeXboX is not an application, it’s a full-featured OS, that one can boot as a LiveCD, from a USB key, an SD/MMC card or install on its regular HDD. The GeeXboX distribution is lightweight and designed for one single goal: embed all major multimedia applications as to turn your computer into an HTPC.

[http://www.geexbox.org/category/arm/ http://www.geexbox.org/category/arm/]

==Ubuntu==

[http://www.ubuntu.com/ Ubuntu] was initially planned to be the default distribution, but the current version of Ubuntu only supports ARMv7 onwards, not the ARMv6 architecture used by the Raspberry Pi's processor. Therefore Ubuntu does not work on Raspberry Pi, and there is no further information about this changing in the near future.

A bug report on this subject was submitted to Ubuntu's bug tracker. The responses to that bug include an unofficial viewpoint from a Canonical employee, outlining the amount of work required to support ARMv6 (and therefore, potentially, Raspberry Pi). See [https://bugs.launchpad.net/ubuntu/+bug/848154 Bug 848154]

[https://wiki.ubuntu.com/ARM https://wiki.ubuntu.com/ARM]

=Development environments=

Instead of just using a compiler and editor, you can use a complete image to create "development tool chains" which integrate compiler, build system, packaging tools etc. in one tool chain.

==OpenEmbedded==

OpenEmbedded is a build framework and cross-compile environment for embedded Linux.

http://openembedded.org/

==QEMU==

A detailed tutorial by emercer: [http://cronicasredux.blogspot.com/2011/09/installing-and-running-debian-armel-on.html http://cronicasredux.blogspot.com/2011/09/installing-and-running-debian-armel-on.html]

Discuss:
* [http://www.raspberrypi.org/forum/projects-and-collaboration-general/emulating-a-raspi-on-windows http://www.raspberrypi.org/forum/projects-and-collaboration-general/emulating-a-raspi-on-windows]

==Scratchbox==

Scratchbox is a cross-compilation toolkit designed to make embedded Linux application development easier. It also provides a full set of tools to integrate and cross-compile an entire Linux distribution. To find out what it can do, take a look at some of the [http://www.scratchbox.org/documentation/ documentation].

[http://www.scratchbox.org/ http://www.scratchbox.org/]

There is now an Oracle Virtualbox VM image with a scratchbox2 install inside.

''More details and discuss: [http://www.raspberrypi.org/forum/?mingleforumaction=viewtopic&t=454 http://www.raspberrypi.org/forum/?mingleforumaction=viewtopic&t=454]''

==Eclipse==

==Mamona==

==EMBINUX==

{{Template:Raspberry Pi}}

User talk:BLT111

2012-05-12T10:23:22Z

Gus3: spam link alert

Hey guys !! The name is JANINE SHIELDS. I have a house in Plymouth.
Iam 33. Iam taking admission in The Clean Military School which
has a branch in Ocala. Iam planning to become a Civil engineer.
I like to do Bonsai. My father name is Jonathon and he is a
Innkeeper. My mom is a Confectioner.

My page: [http://www.buylovetoys.com grown-up adult toys,]

----

Don't click that.

[[User:Gus3|Gus3]]

RPi Kernel Compilation

2012-05-10T23:28:25Z

Gus3: clarifying a git clone invocation

{{Template:RPi_Software}}

= Overview =

First, you are going to get and build the linux kernel and its modules using a suitable compiler (a "cross-compiler" if you aren't building it on the same hardware you will be running it on) and then you are going to create a kernel image from the uncompressed kernel (Image) to place on the sd, along with the modules you build alongside it.

See below for the various guides to get and compile a suitable kernel for your RPi, and then create a kernel.img according to the steps at the end.

= Raspberry PI kernel compilation =

You can compile the kernel on the board itself, but because of the limited resources it will take a lot of time. Alternatively you can crosscompile the kernel on another machine running Linux, Windows or OS X.

== Compiling on the Raspberry pi itself ==

=== Arch Linux ===

==== getting the compiler ====
You will need GIT to clone the kernel source tree from GitHub, compiler (gcc) and GNU Make:
pacman -S git gcc make

(NOTE: git might be omitted if you decide to download sources in compressed format; this is far faster)

==== getting the sources ====

create a directory where you can work on the raspberry pi software. I called mine "raspberrypi". Then clone the git repository.

mkdir raspberrypi
cd raspberrypi
git clone https://github.com/raspberrypi/linux.git
(NOTE: git might fail due to memory constraints; in this case creation of swap file might help. Be warned - this takes ages! To omit the revision history and reduce the download, you can add "--depth 1" to the end of the git clone command.)

Alternatively, download ZIP or TAR.GZ version of the sources from:
https://github.com/raspberrypi/linux/downloads
unpack and enter the extracted directory (this is your kernel directory - its sources to be precise)

==== configuring the kernel ====
Next, the kernel options are configured. Either copy the cut down Raspberry Pi .config file from the kernel source configs directory:
cp arch/arm/configs/bcmrpi_cutdown_defconfig .config

Or alternatively, to use the configuration from a currently running Raspberry Pi image, connect to the target and extract the .config file. Then copy the resultant .config file into the Linux kernel source root directory:
zcat /proc/config.gz > .config
cp .config <path to linux source root directory>

If needed - manual/additional configuration:
make menuconfig

==== compile the kernel ====
make

(NOTE: this will take around 6h; You might find GNU Screen useful)

==== build kernel.img so your RPi can boot from it ====

Finally you need to build a kernel.img for your Pi to boot from. For this, you need the mkimage tool from the raspberrypi github repository:

git clone https://github.com/raspberrypi/tools

Alternatively, download 'imagetool-uncompressed.py' from (this takes far less time and resources):
https://github.com/raspberrypi/tools/blob/master/mkimage/imagetool-uncompressed.py

Before you can use this script you need Python v2 to be installed:
pacman -S python2

Once all above is set up you should have the following files (checklist):
* in the kernel folder you compiled a file: linux/arch/arm/boot/Image
* python2 executable (it should be located by default in /usr/bin/python2)
* imagetool-uncompressed.py script

If this is a case (you have all the above) convert your kernel image with the script:

python2 imagetool-uncompressed.py path/to/linux/arch/arm/boot/Image

This will create a file called kernel.img. Transfer this file into /boot directory (make sure the existing kernel.img in /boot directory gets replaced).

The last thing is to install kernel modules. To do this navigate to your kernel folder and execute:
make modules_install

This will install all compiled modules into /lib/modules and possibly some additional files into /lib/firmware folders.

Reboot your RPi and pray :)
reboot

TODO: verify & consolidate

== Cross compiling on a foreign machine==

=== Ubuntu Linux ===

==== getting the compiler ====

On Ubuntu Oneiric getting the arm cross compiler can be as easy as:

sudo apt-get install gcc-4.6-arm-linux-gnueabi
sudo apt-get install git #jhauser14905 -- might as well state the obvious, you need git installed!

(TODO: Is this the right one? More packages required? I did this a while ago! TODO: Other distributions?)

==== getting the sources ====

create a directory where you can work on the raspberry pi software. I called mine "raspberrypi". Then clone the git repository.

mkdir raspberrypi
cd raspberrypi
git clone https://github.com/raspberrypi/linux.git
cd linux

jhauser14905: on 2012-01-28, with all package updates applied, i had to add the following symlink in order to get the make commands to work. otherwise they would error out

sudo ln -s /usr/bin/arm-linux-gnueabi-gcc-4.6 /usr/bin/arm-linux-gnueabi-gcc

==== compiling ====

Next, the kernel options are configured. Either copy the cut down Raspberry Pi .config file from the kernel source configs directory:
cp arch/arm/configs/bcmrpi_cutdown_defconfig .config

Or alternatively, to use the configuration from a currently running Raspberry Pi image, connect to the target and extract the .config file. Then copy the resultant .config file into the Linux kernel source root directory:
zcat /proc/config.gz > .config
cp .config <path to linux source root directory>

Configure the kernel with the copied .config file by running oldconfig:
make ARCH=arm CROSS_COMPILE=/usr/bin/arm-linux-gnueabi- oldconfig

Then build the kernel:
make ARCH=arm CROSS_COMPILE=/usr/bin/arm-linux-gnueabi- -k

You can use the "-j" flag to improve compilation time. If you have a dual core machine you can use "-j 3", for a quad core machine you can use "-j 6", and so on.

If you get the error messages that arm-linux-gnueabi-gcc cannot be found when running make, run the following command:

sudo ln -s /usr/bin/arm-linux-gnueabi-gcc-4.6 /usr/bin/arm-linux-gnueabi-gcc

this creates a symbolic link to the 4.6 gcc binary

=== Gentoo Linux ===

==== getting the compiler ====

Build the cross toolchain:
crossdev -S -v -t arm-unknown-linux-gnueabi

theBuell: on 2012-05-06, cross -S -v -A gnueabi arm works just fine

This command should create a cross-toolchain using the latest stable versions of the required packages. If it fails, you can specify exact versions by removing the "-S" flag and adding the "--b", "--g", "--k" and "--l" flags. For the exact usage refer to the crossdev manpage. A good starting point for figuring out the right versions are those which are stable for the arm architecture.

==== getting the sources ====

create a directory where you can work on the raspberry pi software. I called mine "raspberrypi". Then clone the git repository.

mkdir raspberrypi
cd raspberrypi
git clone https://github.com/raspberrypi/linux.git
cd linux

==== compiling ====

Next you have to configure the kernel:
cp arch/arm/configs/bcmrpi_cutdown_defconfig .config
make ARCH=arm CROSS_COMPILE=/usr/bin/arm-linux-gnueabi- oldconfig

Then building the kernel:
make ARCH=arm CROSS_COMPILE=/usr/bin/arm-linux-gnueabi- -k

You can use the "-j" flag to improve compilation time. If you have a dual core machine you can use "-j 3", for a quad core machine you can use "-j 6", and so on.

=== Arch Linux ===

==== getting the compiler ====
You will need GIT to clone the kernel source tree from GitHub:
pacman -S git

Build the cross toolchain:
arm-linux-gnueabi-gcc is on the AUR. If you use yaourt:

yaourt -S arm-linux-gnueabi-gcc

Yaourt is recommended as it will build all dependencies.

==== getting the sources ====

create a directory where you can work on the raspberry pi software. I called mine "raspberrypi". Then clone the git repository.

mkdir raspberrypi
cd raspberrypi
git clone https://github.com/raspberrypi/linux.git
cd linux

==== compiling ====

Next you have to configure the kernel:
cp arch/arm/configs/bcmrpi_cutdown_defconfig .config
make ARCH=arm CROSS_COMPILE=/usr/bin/arm-linux-gnueabi- oldconfig

Then building the kernel:
make ARCH=arm CROSS_COMPILE=/usr/bin/arm-linux-gnueabi- -k

You can use the "-j" flag to improve compilation time. If you have a dual core machine you can use "-j 3", for a quad core machine you can use "-j 6", and so on.

=== Windows ===

TODO

=== OS X ===

==== getting the compiler ====
Ensure latest Xcode and command line tools are installed from [http://developer.apple.com/downloads Apple Developer Connection] then
Downoad and install an GNU ARM toolchain such as [http://www.yagarto.de/#downloadmac yagarto]

Another option is the MacPorts arm-none-eabi-*:

port install arm-none-eabi-binutils

==== getting the sources ====

create a directory where you can work on the raspberry pi software. I called mine "raspberrypi". Then clone the git repository.

mkdir raspberrypi
cd raspberrypi
git clone https://github.com/raspberrypi/linux.git
cd linux

==== compiling ====

Next you have to configure the kernel: (the running kernel config can be found in <code>/proc/config.gz</code> on your RPi)
cp arch/arm/configs/bcmrpi_cutdown_defconfig .config
make ARCH=arm CROSS_COMPILE=/path/to/yagarto/bin/arm-none-eabi- oldconfig

or if you used the MacPorts
make ARCH=arm CROSS_COMPILE=/opt/local/bin/arm-none-eabi- oldconfig

Then building the kernel:
make ARCH=arm CROSS_COMPILE=/path/to/yagarto/bin/arm-none-eabi- -k

or if you used the MacPorts
make ARCH=arm CROSS_COMPILE=/opt/local/bin/arm-none-eabi- -k

You can use the "-j" flag to improve compilation time. If you have a dual core machine you can use "-j 3", for a quad core machine you can use "-j 6", and so on. (Don't use these for the oldconfig option because it messes up the input and output).

'''If you get an error message that elf.h is missing'''

install [http://guide.macports.org/#installing macports]
install libelf and symlink to /usr/libelf:
sudo port install libelf && sudo ln -s /opt/local/include/libelf /usr/include/libelf
copy [http://opensource.apple.com/source/dtrace/dtrace-48/sys/elf.h?txt elf.h] and [http://opensource.apple.com/source/dtrace/dtrace-48/sys/elftypes.h?txt elftypes.h] to /usr/include

Edit elf.h and add
#define R_386_NONE 0
#define R_386_32 1
#define R_386_PC32 2
#define R_ARM_NONE 0
#define R_ARM_PC24 1
#define R_ARM_ABS32 2
#define R_MIPS_NONE 0
#define R_MIPS_16 1
#define R_MIPS_32 2
#define R_MIPS_REL32 3
#define R_MIPS_26 4
#define R_MIPS_HI16 5
#define R_MIPS_LO16 6

= Final step: Making the 'kernel.img' for your Pi =

Finally you need to build a kernel.img for your Pi to boot from. For this, you need the mkimage tool from the raspberrypi github repository:

git clone https://github.com/raspberrypi/tools

In tools/mkimage, you'll find a python script called 'imagetool-uncompressed.py':

usage : imagetool-uncompressed.py <kernel image>

After building your linux kernel, you'll find the kernel image you require in 'arch/arm/boot/Image' of the linux directory. Convert your kernel image with the script:

python imagetool-uncompressed.py path/to/linux/arch/arm/boot/Image

Then you have to transfer this img file to the /boot directory and install the compiled modules. Unfortunately the compiled modules are not in a single place, there are two options of installing them.

Boot your RaspberryPi and mount the <code>linux</code> directory over the network using sshfs:
cd /mnt
mkdir linux
mount <user>@<host>:<path/to/linux>
cd linux
make modules_install

If that is not an option, you can also install the modules into a temporary folder:
mkdir /tmp/modules
make ARCH=arm modules_install INSTALL_MOD_PATH=/tmp/modules

Now you have to copy the contents of that directory to /lib/modules on the SD card.

Once you've done those two steps, you are ready to put the SD card in and try booting your new system!

{{Template:Raspberry Pi}}
[[Category: RaspberryPi]]

User:Gus3

2012-05-09T00:06:46Z

Gus3: Slackware on the Raspberry Pi: It works!

User:Gus3

2012-05-04T01:52:27Z

Gus3: Status update

RaspberryPi Laptop

2012-05-04T01:45:01Z

Gus3: /* Suggestions! Leave suggestions here! */

===Updates===
Yup! Our first update! We originally thought that we needed to get a loan to get the project going or go to kickstarter (After Finished Prototype) ,But It turns out that somebody has volunteered to be a potential investor if the prototype works! Thanks to Raiyan Memon for volunteering! You will not be dissapointed!
=====Suggestions! Leave suggestions here!=====

Suggestions from [[User:Gus3|Gus3]]:
* multiple system options (Debian, Arch, Fedora, Bodhi, perhaps others, perhaps non-Linux)
* send a stated percentage back to the Raspberry Pi Foundation

User:Gus3

2012-05-03T03:59:06Z

Gus3: Slackware on RPi update

Got my RPi on 2012-April-19. Currently running the customized Debian image, since I know a little more about Debian than the other supported distros (Arch, Fedora).

One of my project ideas will be to get [http://www.armedslack.org/ Slackware ARM] running on the RPi. I would think that the Debian kernel and modules, with Slackware ARM userspace, could be hacked together to work, but that's only an uneducated guess. Slackware ARM currently has three installer images, for the three supported platforms; I eagerly await the fourth, Raspberry Pi.

Status update 2012-05-02, late evening: I have a Slackware ARM setup that crashes in /etc/rc.d/rc.S. But at least that means /sbin/init is running from the flash card. Yay!

Talk:RPi Kernel Compilation

2012-04-30T23:57:12Z

Gus3: Created page with "This page could use a re-organization. Currently, most of the page is concerned with cross-platform compilation, with a lot of duplication in the kernel build step. I propose a b..."

This page could use a re-organization. Currently, most of the page is concerned with cross-platform compilation, with a lot of duplication in the kernel build step. I propose a breakdown thus:

* Overview
* Getting the toolchain for cross-compilation (if needed)
* Configuring the kernel
: with special emphasis on built-in vs. modular drivers
* Building the kernel
* Installing the kernel

Another possibility is to give cross-compilation its own page, to cover toolchain acquisition for different host platforms. Given that the RPi isn't the only embedded to use ARM CPU's, such a page could serve the same purpose for [[Processors#ARM|several ARM platforms]]. (For that matter, each CPU on such a page could have its own section on toolchain acquisition.) Then, the "kernel compilation" page could deal more succinctly with process of configuring and building the kernel for the RPi platform.

[[User:Gus3|Gus3]]

User:Gus3

2012-04-30T02:34:06Z

Gus3:

Got my RPi on 2012-April-19. Currently running the customized Debian image, since I know a little more about Debian than the other supported distros (Arch, Fedora).

One of my project ideas will be to get [http://www.armedslack.org/ ArmedSlack] running on the RPi. I would think that the Debian kernel and modules, with ArmedSlack userspace, could be hacked together to work, but that's only an uneducated guess. ArmedSlack currently has three installer images, for the three supported platforms; I eagerly await the fourth, Raspberry Pi.

Mandatory Access Control Comparison

2012-04-30T02:24:01Z

Gus3: Typo

Table Of Contents:

This page has information about Mandatory Access Control (MAC) solutions, which is of interest to CE Linux Forum members,
because MAC provide strong access control for CE device which has rich resources to be managed.

== Comparison of MAC solution ==

{| border="1" cellspacing="0" cellpadding="5"
|-bgcolor="#80c0d0"
!_
![http://www.lids.org/ LIDS]
![http://tomoyo.sourceforge.jp/ TOMOYO]
![http://rsbac.org/ RSBAC]
![http://selinux.sourceforge.net/ SELinux]
![http://en.opensuse.org/AppArmor App Armor]
|-
| Security Model
| MAC(inode), TPE(1.2),TDE(1.2)
| MAC(path)
| MAC, RC, ACL, FF, UM, PM, DAZ, JAIL
| MAC(label), TE,RBAC,MLC,MCS
| MAC(path)
|-
| Type
| LSM (2.6), patch (2.4)
| patch
| patch
| LSM
| LSM
|-
| Current version (2.6)
| 2.2.2 for 2.6.14 (LSM)
| 1.1.3 for 2.6.11-17
| 1.2.7 for 2.6.16
| in mainline
| 2.6.X (LSM)
|-
| Current version (2.4)
| 1.2.2 for 2.4.30
| 1.1.3 for 2.4.20 - 32
| 1.2.7 for 2.4.32
| obsolete
| ?
|-
| Policy learn mode
| /lids/lids.ini
| CCS=0 /root/security/profile0.txt || /etc/selinux/config
| rsbac_softmode
|
|-
| disable option
| lids=0
|
|
| selinux=0
|
|-
| Policy location
| /etc/lids/
| /root/security/
| ?
| /etc/selinux
| ?
|-
| Distributions
|
|
| Hardened Gentoo
| Redhat, Fedora Core, Hardened Gentoo
| Open Suse
|-
| (by 3rd party)
| Fedora core, Debian
| Fedora core, Debian
| Debian
| Suse, Ubuntu
| Slackware
|}

== Benchmark ==
MEN WORKING

Hardware : Sharp Zaurus C860,
CPU :[[XScale]] 400MHz,
Memory : --MB,
OS : Openzaurus 3.5.4.1 + OPIE 1.2

=== Sizing ===

Kernel 2.6.16 (linux-openzaurus-2.6.16-r40, Static build)
{| border="1" cellspacing="0" cellpadding="5"
|-bgcolor="#80c0d0"
|
| Normal
| LIDS
| TOMOYO
| RSBAC
| [[SELinux]]
|-
| Kernel size (Image)
| 2487744
| 2554880
| 2541808
| 2974224
| ?
|-
| Kernel size (zImage)
| 1181660
| 1205324
| 1207288
| 1351432
| ?
|-
| image size overhead
| 0
| 67136
| 54064
| 486480
| ?
|-
| policy size
| 0
|-
| memory consumption
| 0
|}

=== Lmbench ===

Processor, Process, Local communication latencies
{| border="1" cellspacing="0" cellpadding="5"
|-bgcolor="#80c0d0"
|
| Normal
| LIDS
| TOMOYO
| RSBAC
| [[SELinux]]
|-
| null call
| 0.46
| 0.46
| 0.46
|-
| null I/O
| 1.77
| 1.97 (11%)
| 1.77
|-
| stat
| 12.7
| 15.7 (24%)
| 12.8 (1%)
|-
| open/close
| 18.7
| 22.5 (20%)
| 59 (216%)
|-
| select TCP
| 91.3
| 91.6
| 91.3
|-
| sig inst
| 2.89
| 2.83 (-2%)
| 2.84 (-2%)
|-
| sig hndl
| 7.58
| 7.66 (1%)
| 9.25 (22%)
|-
| fork
| 3795
| 3808
| 3757 (-1%)
|-
| execve
| 13000
| 13000
| 15000 (15%)
|-
| sh
| 36000
| 37000 (3%)
| 41000 (14%)
|-
| ctxsw
| 175
| 186.3 (7%)
| 177.2
|-
| pipe
| 356.9
| 375.6 (5%)
| 358.1
|-
| AF_UNIX
| 674
| 718 (7%)
| 723 (7%)
|-
| UDP
| 747.5
| 776.3 (4%)
| 765.1 (2%)
|-
| RPC/UDP
| 969.1
| 1013 (5%)
| 1193 (23%)
|-
| TCP
| 957.3
| 1004 (5%)
| 964.6 (1%)
|-
| RPC/TCP
| 1332
| 1380 (4%)
| 1353 (2%)
|-
| TCP connect
| 2302
| 2379 (3%)
| 2357 (2%)
|-
| 0KB create
| 461
| 605.7 (31%)
| 669.8 (45%)
|-
| 0KB delete
| 232.5
| 267.1 (15%)
| 329.5 (42%)
|-
| 10KB create
| 5128.2
| 5234.6 (2%)
| 5235.6 (2%)
|-
| 10KB delete
| 298.8
| 349.8 (17%)
| 415.1 (39%)
|-
| Mmap latency
| -
| -
| -
|-
| Prot Fault
| 1.72
| 1.71
| 0.61 (-64%)
|-
| Page Fault
| 92
| 92
| 86 (-7%)
|}

=== Unixbench ===
{| border="1" cellspacing="0" cellpadding="5"
|-bgcolor="#80c0d0"
|
| Normal
| LIDS
| TOMOYO
| RSBAC
| [[SELinux]]
|-
| execl
| 89.3 lps
| 84.6
| 59.5
|-
| file read 1KB
| 53974.0 KBps
| 52176
| 53505
|-
| file write 1KB
| 328.0 KBps
| 321
| 376
|-
| file copy 1KB
| 288.0 KBps
| 199
| 311
|-
| file read 256B
| 34766.0 KBps
| 33831
| 34742
|-
| file write 256B
| 133.0 KBps
| 121
| 138
|-
| file copy 256B
| 126.0 KBps
| 121
| 121
|-
| file read 4KB
| 69148.0 KBps
| 67961
| 68851
|-
| file write 4KB
| 1417.0 KBps
| 1417
| 1333
|-
| file copy 4KB
| 1268.0 KBps
| 1237
| 1249
|-
| pipe
| 112917.5 lps
| 108924
| 112137
|-
| pipe switching
| 2655.4 lps
| 2559.6
| 2700
|-
| process creation
| 272.9 lps
| 367.8
| 276.4
|-
| system call
| 269446.2 lps
| 267748
| 268823.9
|-
| shell scripts (1)
| 82.2 lpm
| 77.6
| 58.6
|-
| shell scripts (8)
| 5.3 lpm
| 5.6
| 5.4
|-
| shell scripts (16)
| 2.0 lpm
| 0
| 2
|}

== Summary ==
{| border="1" cellspacing="0" cellpadding="5"
|-bgcolor="#80c0d0"
|
| LIDS
| TOMOYO
| RSBAC
| [[SELinux]]
| App Armor
|-
| build (kenrel) (easy:5 - 1:hard)
| 4
| 4
| 3
| 5
| ?
|-
| build (userland) (easy:5 - 1:hard)
| 4
| 4
| 3
| ?
| ?
|-
| image size
| 2%
| 2%
| 15%
| 3%
| ?
|-
| performance
|
|
|
|
| ?
|-
| policy lean mode (good:5 - 1:poor)
| 4
| 5
| ?
| 3
| ?
|-
| symlink
| by wrapper
| support(alias)
|
|
| ?
|-
| filesystem JFFS2
| ok
| ok
|
|
| ok?
|}

== Other resources ==

Access Control Comparison Table
http://gentoo-wiki.com/Access_Control_Comparison_Table

[[Category:Security]]

User:Gus3

2012-04-29T01:13:55Z

Gus3: Intro

Got my RPi on 2012-April-19. Currently running the customized Debian image, since I know a little more about Debian than the other supported distros (Arch, Fedora).