Hot answers tagged

4

Based on your answer that there wasn't a boot partition, your report that the display doesn't work, and an experiment that I've just conducted, I suspect that UNetbootin doesn't do a proper job of installing Raspbian. Since you're just getting started, please try this: Get a copy of balenaEtcher and use it to re-flash your microSD card. Try the boot ...


4

Get yourself a copy of PINN that will let you pick any one of a multitude of operating systems to multi-boot on your RPi. You should be able to fit LibreElec, OSMC, Retropie and Raspbian on a 32GB or 64GB SDcard. https://github.com/procount/pinn


3

You can connect the RasPi with an ethernet cable to the computer. Depending on the operating system on the computer a network connection may work out of the box. You can setup a WiFi access point on the RasPi and connect to it from the computer. How to do it you can look at Setting up a Raspberry Pi as an access point - the easy way. You can use bluetooth to ...


2

I don't know what tutorial do you follow. I don't had a look at it, tl;dr. But it cannot belong to Raspberry Pi 4B because that model does not support booting from other devices than an SD Card yet. At Raspberry Pi boot modes you can find: Note: The Raspberry Pi 4B does not use the bootcode.bin file - instead the bootloader is located in an on-board ...


2

You could use cron for this. To schedule a cron job, you will use the crontab utility. Start by reading the man pages for cron and crontab. You could also search the Internet for information resources, and find something similar to this guide. Once you have the gist (general idea) of this, try this from the command line of your RPi: crontab -e This ...


2

inittab was a part of SysVinit, which was replaced by systemd. Serial getty is a service now, and it can disabled or stopped like this: sudo systemctl stop serial-getty@ttyAMA0.service sudo systemctl disable serial-getty@ttyAMA0.service For more information, take a look at this thread in the rpi forum. https://www.raspberrypi.org/forums/viewtopic.php?t=...


2

For those who prefer a solution involving only scripts dropped into the FAT32 boot partition, here is how to do that. [Edit: The files are now available in a project pi-boot-script.] As mentioned in other answers, it involves the command-line arguments with which the Linux kernel is started. Those arguments are in /boot/cmdline.txt. I have tested this on ...


2

There are probably a few ways to do this, but what I've done in the past is to first set up an auto-login service for the user account that would run the application: sudo nano /etc/systemd/system/autologin@.service [Service] ExecStart=-/sbin/agetty --autologin app_user %I $TERM Then in the user .profile, start an X session: [[ -z $DISPLAY && $...


2

Assuming you have correctly written your image on your SD card, here is schematic about how zeroconf work (as specified by @tpack) if you want contact your raspberry with raspberry.local name. Maybe this can help you better understand. Normally if the OS is correctly written and started RPi must obtain an ip addr on her ethernet interface when you plug your ...


1

You are trying to use an old tutorial for an obsolete OS. You appear to have installed an (unspecified) Raspbian using an unusual tool, which appears to be designed to create bootable drives from an ISO image. I suggest you install a current Raspbian using one of the recommended tools. You can enable ssh headlessly as described in How to set up networking/...


1

I'm convinced that your problems stem from the fact that regular autologin methods rely on a real tty being available, while your guest system will have none (it will only have /dev/console which kind of emulates a terminal using stream redirection and the like, depending on the --console parameter of nspawnd). You don't seem to be able to start an X server ...


1

The tutorial you reference only enables ssh it does not enable the avahi-daemon (zeroconf) which is what you need if you want to connect via a hostname instead of an IP address. So you'll need the IP address in order to ssh to the pi. Since you are on Linux Mint, try installing nmap and then scanning your network to find the pi. Substitute the appropriate ...


1

I suggest you get a USB to UART dongle and set up your RPi to produce boot messages to serial port. This usually involves editing cmdline.txt to make sure there is a serial console (console=serial0,115200) and there's no quiet parameter. You should be able to collect boot messages on a laptop using Putty or a similar terminal program. Get this working ...


1

I was facing the same problem with the Raspberry pi 4 but without the touch screen. When I studied and searched I found that OS was corrupted or was not compatible to run with the Raspberry pi due to the wrong alteration. I think you are also facing a similar issue. Please follow this link: https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=258526 ...


1

You tried several methods to start chromium in kiosk mode on boot. Using /etc/rc.local is not a good idea because it is deprecated. It 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. Using ~/.bashrc will not work ...


1

The usual (or works for me) method for booting off an external disk with a pi 4 is: Start with a SD based system and an empty external drive (probably /dev/sda)... Run fdisk, delete all partitions on /dev/sda. Create a new primary linux partition. Save and exit. run sudo mkfs.ext4 /dev/sda1 sudo mkdir /media/disk sudo mount /dev/sda1 /media/disk sudo rsync -...


1

If there is any error while running this on startup, you can’t see the error message. To check this, press ctrl+alt+F1. Here you can check the output of background processes. You can return to graphical display by ctrl+alt+F7. This is the way you can ensure whether there is any error while running the code or not. Now come to your solution, if there is any ...


1

It is known that the Raspberry Pi 3B had problems that the Foundation tried to fix but could still make problems. You can try to use Special bootcode.bin-only boot mode or extend the time for which it waits for the mass storage device to initialize. Look at Raspberry Pi boot modes how to do it and for further information about troubleshooting.


Only top voted, non community-wiki answers of a minimum length are eligible