It seems that the only concern is that your power supply, if it's not a decent, reliable supply capable of 2A+ of clean output power, might not be able to power the Pi sufficiently, resulting in crashes or frequent rainbows.
All that max_usb_current=1 does is to set GPIO38 high, which in turn turns on a FET, which connects a second 39K ...
The answer to your question title has been hard to word better than gregeric explained:
dwc_otg is the driver that has been heavily patched to squeeze most performance & function in host mode on the Pi: the fiq stuff etc. So heavily patched that, despite the name, it only does host mode & not OTG.
dwc2 is an upstream driver which can do the OTG host/...
I think others here have done a good job answering:
Is it even worth switching from ARMv7 to ARMv8
Various software cited to require ARMv8 includes CockroachDB, MongoDB (if accessing >2 GB), the Dolphin emulator, and OpenMW. However, likewise you'll lose out on other features or programs that may be less-supported with a 64-bit kernel (e.g. gaming with ...
I used the following to calibrate my display https://github.com/ukscone/set_overscan
I found this on http://www.raspberrypi.org/forums/viewtopic.php?p=305797&sid=4fe5fc284854fe3723841f79ea2c6546#p305797
Is it even worth switching from ARMv7 to ARMv8?
Not unless you are running a kernel and OS userland compiled for ARMv8; there are at least a few such things for the Pi 3 around, including Fedora. For some hints about why there still isn't a special version of Raspbian, see here:
Raspbian moving to 64-bit mode
Otherwise, I think the only relevance is in ...
CMA dynamically allocates memory to the GPU as required. When the amount of free memory available to the GPU falls below the 'low water mark' (cma_lwm), CMA will attempt to re-allocate some of the memory currently available to the ARM to be instead reserved for the GPU. You can think of this as 'minimum free memory' for the GPU.
If the GPU later frees up ...
It is not possible to set the device hostname through config.txt. A full list of commands can be found on the Raspberry Pi Foundation's website.
You mention that you're creating a custom image. In this case, I believe the best practice would be to write the assigned hostname to /etc/hostname during the card creation process. It does require ...
You can use setfont from a terminal to set the current console font to one of the fonts found in /usr/share/consolefonts/. You don't need to specify the full path or the .psf.gz suffix. Just something like:
will do the trick. You can play around until you find a font you like, and then to make it systemwide and default, you can ...
I had the same problem. Everyone owns an HDMI TV except me (well, I do now). I found the following information only after a long long search. No one seems to be talking about it, so the wider community is not aware.
Display Mode Selection: By default, NOOBS will output over HDMI at your display's preferred resolution, even if no HDMI display is connected. ...
I've just tested this on my Pi3 with 5 inch touchscreen - both work - with and without the '='.
hdmi_cvt=800 480 60 6 0 0 0
hdmi_cvt 800 480 60 6 0 0 0
What finally helped was the following:
I dumped the EDID-file with tvservice -d edid_dump.bin
I edited this file with LIGHTWARE-EDID-editor (part of a demo suite).
What I actually needed to change was little: In the CEA part of the file, I needed to specify that the device was HDMI-compliant (HDMI/HDMI options), and under CEA/Audio data, I needed to add ...
Answer to QUESTION 1 (Read Comments section down below question)
The config.txt is read from the FAT32 partition!!! The config.txt I added has no effect indeed. It can't. Read Comment section below.
devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620,ptmxmode=000)
root@raspberrypi2:/# fdisk -l
Disk /dev/mmcblk0: 7948 MB, 7948206080 ...
I understand this is an old question, but happens that I knew how this is working trying to fix a similar problem (more on this later on).
Yes you can boot again from the sdcard, even with the (permanent) OTP bit set, simply because that bit says to the Pi to look further for the bootcode, after checking onto the sdcard, scanning also USB devices etc.
Thanks to the forums over on raspberrypi.org I was able to find out the answer to this, so I am sharing it here for future reference...
ANSWER: The 128M of GPU RAM is still being reserved because I have the Raspberry Pi Camera enabled. The camera requires a minimum of 128M of GPU RAM to be held aside in order to function properly. This overrides the ...
For me to set raspberry_pi raspbian(jessie) video resolution as 1280x1024, from 655x500(some very large and disturbing display resolution) I have made following changes in my /boot/config.txt file.
PS : These are the only values in my /boot/config.txt
On the Pi1 there was a L2 cache which was primerally intended for use by the VPU but could also optionally be used by the arm core. IIRC in the intial firmware the arm didn't use this cache but with later firmware it used it by default.
On the Pi2 the arm cluster has it's own l2 cache so there is no reason for it to use the L2 cache intended for the GPU.
Okay, from your comments on the other answer, it looks like you want to change the hostname of Raspberry Pi image without actually booting it. This should be trivial.
We want to modify the /etc/hostname in the second partition, so we will find its location in the image using fdisk.
fdisk -l image.img
Where image.img is your image file. Look under the ...
You probably need to use sudo:
sudo chmod a+w config.txt
You don't say much about the file (who owns it?) or which user you're running the command as, but I guess you're probably logged in as a normal user and the file is owned by someone else (root?). Hence you don't have permission to change the permissions.
Using sudo runs the command as ...
The Raspberry Pi 3 Model B starts at 1.2Ghz regardless of what /boot/config.txt says. Here are the results of my clock speed files on my Pi 3 with config.txt not edited from a fresh card:
sudo cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq
When not under load:
sudo cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq
The permitted over voltage values are given in
CPU/GPU core voltage adjustment. [-16,8] equates to [0.8V,1.4V] with
0.025V steps; in other words, specifying -16 will give 0.8V as the GPU/core voltage, and specifying 8 will give 1.4V. The default value
is 0 (1.2V). Values ...
Setting the governor to "performance" should mean the processor runs at the maximum frequency set in config.txt, or the default if there isn't one. Note that this is generally pointless except in unusual contexts, since when required gearing up to a higher frequency happens much faster than is humanly perceivable.
I have read that using a raspberry pi B+ ...
/boot mounted as read-only
mount | grep /boot
if the the output is
/dev/mmcblk0p1 on /boot type vfat (ro,relatime, ... ,errors=remount-ro)
it is mounted read-only (see the ro). You can remount it with the following command:
sudo mount -o remount,rw /boot
Sometimes there are errors on the boot-filesystem which triggers the system to mount it read-...
As of today, it seems Fedora and Archlinux are well supported.
If you go the Arch way, this will help you build the image (for me on linux / rpi3 it was make linux) and this will help you start wifi.
In case you need to be sure which raspberry you have, use this guide.
Also arm_control=0x200 is deprecated and arm_64bit should be used instead in /boot/...
You could automate the action suggested above with a script.
if /opt/vc/bin/tvservice -s | grep 'NTSC\|PAL'; then
echo $(hostname) is running Composite
echo $(hostname) is running hdmi
Replace the echo lines with the desired adjustments
Try adjusting the left and right margins using the fbset command:
fbset -left xxx -right yyyy
Where xxx is the left margin in pixels and yyy is the right margin in pixels.
fbset -left 0 -right 0
Should set the left and right margins to zero
I have used this command to change the screen resolution on my Pi using a Motorola Lapdock as my HDMI display.
The only option I know of in config.txt capable of corrupting an SD card is overclocking. You do not use overclocking so I will provide some other steps for improving SD card lifespan.
Put some subdirectories of /var in a ram drive. The following example would allocate /var/log up to 100M of RAM, but will only use the size of the files in /var/log, if put ...
I changed the config.txt located at /boot, including the following statement:
I also had to change overscan_left and overscan_right.
I used the method of trial and error to find the right numbers for the overscan.