4
I had a customer who was using many raspberry pi 2. Those were booting from the sd card. 2-3 years ago he started having issues with corrupted sd cards.
I then decided to change the boot location from the sd card to the usb stick. The pro was that even if a usb stick failed, you wouldn't have to dismantle the machine to get access to the sd card. You just ...
3
using /etc/fstab is the proper way of doing this.
if you do not want your system to depend on the drive on startup in case the usb drive is missing you have to set the relevant parameter / options
from man fstab
nofail do not report errors for this device if it does not
exist.
so your fstab should have an entry like this:...
2
I continued my research and found an answer that works for me. There is a DiscoverableTimeout on /etc/bluetooth/main.conf which is, by default, set to 300s.
I just add DiscoverableTimeout = 0 on this configuration files.
2
Once you get to the end of the wizard, it will not reappear when your Pi is booted.
If you do want to use it again for some reason, just run it manually by typing
sudo piwiz
2
Debian is able to upgrade to a new version but it is not an easy task for the upgrade procedure. It has to decide how to upgrade options you have modified and/or set. If it doesn't know it will ask you what to do. Usually it will present the old configuration as default but it may not be always the best decision. This also implies that you will not get ...
2
For other people looking for this issue - solution in my case was hidden in video configuration file. When using the HDMI to VGA converter boot configuration file (/boot/config.txt) must contain proper entry of hdmi_group and hdmi_mode in order to work with every startup.
2
To manage to start programs you should use systemd Unit files. Because we don't know anything about your specific needs I can only give a general idea. Here is a very simple template you can use to start to solve your problem. Create a new service with:
rpi ~$ sudo systemctl --full --force edit yourstartup.service
In the empty editor insert these ...
1
As you can see at the Release notes on date: 2019-06-20 that this is supporting Buster. Versions before will not do it. You can try to "copy" modules, driver and firmware from that version to the Alpine Linux distribution as you already tried, but I don't believe that you will have much access. We have seen similar with Ubuntu on upgrade to RPi 3B+. I'm ...
1
On recent versions of Raspbian, you can use a cron job for this.
Run crontab -e and select your favorite editor when prompted, then add the following to the bottom of the file:
@reboot /path/to/executable
1
A rather straightforward approach would be:
flash your original (old, no modifications) image to a spare SD card
diff between the no-modification image and your current image
flash the new image (again, no modifications) to the spare SD card
apply the changes you've done to the old image to the new image with patch
If you don't have the above-mentioned ...
1
Supplying 5.5V to a Pi should not cause damage, although it is inadvisable. See https://raspberrypi.stackexchange.com/a/99653/8697
Test the voltage on Pin 1 (3.3V) - if this is absent the Pi is dead. NOTE be careful to avoid accidentally shorting 3.3V to any other pin - this is invariably fatal!
PS Measuring anything on a Pi with a multimeter on the ...
1
So you doesn't have power on the 3.3V.
You may have made a shortcut, and fried the 3.3 power supply regulator. One way of trying to be sure of that (and verify the CPU), would be to power the board with an external 3.3V power supply (of good quality)
So remove all the wire who may have started the problem, and try to boot the board this way…
If the power ...
1
I'm assuming your using Raspbian Stretch with Desktop or Raspbian Buster with Desktop.
Edit the autostart file using:
sudo leafpad /etc/xdg/lxsession/LXDE-pi/autostart
Autostart file should look similar to:
@lxpanel --profile LXDE-pi
@pcmanfm --desktop --profile LXDE-pi
@xscreensaver -no-splash
point-rpi
Add your 4 Python programs to the end using @...
1
The assumption that the pi-zero can boot from USB seems wrong. I can't find back the source that gave this idea. It might still be possible with some tricks (custom bootcode.bin on an sd and remove that after the boot process of the cd is finished) but it will all be to complex to build. So I decided to find another way to create a proper air-gapped key ...
Only top voted, non community-wiki answers of a minimum length are eligible
