Stack Exchange Network

Stack Exchange network consists of 175 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.

Visit Stack Exchange

New answers tagged

0

Additional information to the accepted answer: Write the Raspbian Stretch Lite image to the SD card Create a ssh empty file in the boot partition Create a wpa_supplicant.conf file in the boot partition containing: ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev update_config=1 country=FR network={ ssid="MyRouter" psk="the_password" } Boot the ...


2

See Headless Raspbian WiFi Setup in How to set up networking/WiFi Specifically Raspbian checks the contents of the boot directory for a file called wpa_supplicant.conf, and will copy the file into /etc/wpa_supplicant, replacing any existing wpa_supplicant.conf file that may be there. The file in the boot directory is then removed. This can be used to ...


1

It turns out the problem I had was the bootup option I choose. The correct option would have been to choose "Graphical Installer" (there are two install options, probably either, but I went with the graphical one). The "Run with Persistance" option was just running the OS from the CD.


0

If the rpi is not bricked the power cycling the device should help. Are you sure you are disconnecting the right eth cable? Maybe it's ON but not booting because of memory card error. Are you able to monitor the current flowing through the PoE interface? This may help you determine if the rpi is trying to boot or if it's dead.


0

What do you mean with: "I can't get out of this"? Just type exit on the command line and the terminal should close.


1

I have seen messages like unable to make backup link of "some file.svg" when trying to install software on a fat formated partition. fat does not support links so this message will come up every time something tries to set a link. May it be possible that you try to use a fat partition in any way? I have never used Raspberry Pi Desktop but as written there it ...


1

Ok I got it to work, not sure if it's the most elegant of ways but it works... Created an extra file with the following and called the file from rc.local #!/bin/bash sleep 30 cp /media/pi/drive/file.sh /home/pi sudo chmod +x /home/pi/file.sh /home/pi/file.sh not sure how long to wait but reckoned 30s is ok, it copies the file over, changes to executable ...


0

If you have a Pi3B+ USB boot is pre-programmed - there is nothing to do.


0

If you really have a Raspberry Pi 3B+ this procedure is not necessary. Simply plug in the USB stick that has been prepared with the image of your choice. The Raspberry Pi will automatically boot from USB when it does not find a bootable microSD card.


1

For booting to the command line, look here https://www.kiwi-electronics.nl/blog?journal_blog_post_id=5&lang=en There is a setting under system to change boot to CLI (command line interface) Once you are at the command line, startx should get you to the GUI, see here https://www.raspberrypi.org/forums/viewtopic.php?t=9488 You can also set it to ...


0

In addition to the advice to not use rc.local you should note that the /media is NOT automounted until the GUI starts; this is a long time after boot.


1

Please take note that using /etc/rc.local has limitations due to Compatibility with SysV. We have seen many problems here on this site using it. Following the recommendation of the developers from systemd you should avoid using it. It may be possible that the USB drive isn't mounted before executing the commands. I suggest to use a systemd unit file. Just ...


1

/etc/rc.local runs as root so you NEVER need sudo in there. It also runs with a limited environment and /etc as the current working directory. So you can't use relative file names. Use the full path for everything with no strange punctuation. md /media/pi mount /dev/sda1 /media/pi cp /media/pi/drive/file /home/pi/script chmod 755 /home/pi/script su pi /...


5

As Dirk and Ghanima stated in their answers, the service may be overwritten by future updates/upgrades of the system. But systemd has a mechanism to avoid this. You can use a drop in file. An update/upgrade will only modify the main service. The drop in file is not effected by it and will also modify the updated main service. You can simply create a drop in ...


2

As Dirk's answer pointed out the raspberrypi-net-mods.service is responsible for relocating wpa_supplicant.conf. It is located in /etc/systemd/multi-user-target.wants/. This is the actual code (see here): [Service] Type=oneshot RemainAfterExit=yes ExecStart=/bin/mv /boot/wpa_supplicant.conf /etc/wpa_supplicant/wpa_supplicant.conf ExecStartPost=/bin/chmod ...


2

It's a service. In this case it's raspberrypi-net-mods.service. systemctl status raspberrypi-net-mods.service will give status, including full path of the service file. systemctl cat raspberrypi-net-mods.service will show path and contents. Be aware that an update/upgrade could modify the service file in the future.


0

There are other places to check for startup scripts on Raspbian (assuming that is what you are using), one of them being SystemD. If you type systemctl it will list things configured for systemd. There may also be files in the older /etc/init.d folder, although these are no longer used in recent Raspbian versions. Other places scripts can be started are a ....


0

Also late to the party, but thought I'd add that this behavior (solid red and green lights/LEDs at boot time) also happens if the SD card is formatted as exFAT. exFAT is the default on Windows with SD cards over 32 Gb and also seems to be the default format for large SD cards in Tuxera's SD Card Formatter on MacOS (from sdcard.org). To work around the ...


1

Maybe it is the RPi 2+? You may try to use a RPi 3B+. It was revised and improved with boot issues so the RPi 2+ must have problems with booting. It is likely that it only occurs on SD Cards greater than 32 GB. I have heard about it but just can't find a source.


0

To give this question an answer I will quote the comment from the questioner. He was asked if he still having this problem and answered: No, I reformatted my card and it started to boot 100% of the time. I still do not know what was causing the problem.


Top 50 recent answers are included