2

You can have a look at the script itself on your system. raspi-config is a bash script and you can look at it with any text / code editor. The file is at /usr/bin/raspi-config Or have a look at it in the Raspberry Pu github repo: https://github.com/RPi-Distro/raspi-config/blob/master/raspi-config


2

If there's no kernel=zImage line in /boot/config.txt then your system will load kernel.img, kernel7.img or kernel7l.img (depending on the model). So the simple fix is to make kernel=zImage into a comment. You can do that on Windows or with the NOOBS recovery console. #kernel=zImage and it will boot normally (as long as you've got the original kernel ...


2

Why not create a service? [Unit] Description=Change hostname from sd ConditionPathExists=/boot/hostname Before=dhcpcd.service [Service] Type=oneshot ExecStartPre=/bin/bash -c 'CURRENT_HOSTNAME=$(/bin/cat /etc/hostname | /usr/bin/tr -d "\t\n\r");NEW_HOSTNAME=$(/bin/cat /boot/hostname | /usr/bin/tr -d "\t\n\r");/bin/sed -i "s/127.0.1.1.*$CURRENT_HOSTNAME/127....


1

Make sure that hdmi_force_hotplug= is either 0 or commented out. You shouldn't need anything else, just don't plug in HDMI and it'll boot to composite mode.


1

The Foundation documentation is @ config.txt This is quite comprehensive, and more up-to-date than some references. Most of the documentation in /boot/overlays has no counterpart in raspi-config and is more related to Device Tree options. As Androo has mentioned some raspi-config options e.g. serial console are changed in cmdline.txt. If you are interested ...


1

7 years later, I was having the same issue, and the solution that worked for me was "Method 2" from https://www.raspberrypi-spy.co.uk/2014/04/how-to-change-the-command-line-font-size/. In short, I did sudo nano /etc/default/console-setup and updated the FONTFACE and FONTSIZE fields to the size I wanted: FONTFACE="Terminus" FONTSIZE="16x32" Then I saved ...


1

Filenames that start with a period (aka. dotfiles) are considered "hidden", and aren't displayed by default by commonplace tools which respect this convention. Historically, configuration stuff is usually dotfiled. However, the intention is not that you not be able to find or access them (that is done with permissions), nor does it imply they aren't human ...


1

This post is full of mis-information. There should NOT be a line "console=ttyAMA0,115200" You should't have to disable Bluetooth, but if you must do it properly. There are no differences in default serial (or any of the GPIO functions) between Pi4 and earlier 40 pin models with WiFi. Downloading random software is risky - it is difficult to see what it ...


1

You cannot just tie Chip Select (CS) to ground. In SPI the CS pin not only tells the receiving device to listen but also synchronizes the communication. SCK sends pulses to separate each bit. But after powering on the slave IC might be in an undefined state regarding the communication to know it is not in the middle of a message. Thus requires a transition ...


1

Looks like you're using the physical pin numbers. All RPF documentation, settings and software (such as dtoverlay, gpiozero, etc) work with the BCM numbers. You can find these at pinout and elsewhere.


1

I have it working..... Rpi 4 2Gb raspbian lite in config.txt dtparam=i2c_arm=on dtoverlay=i2c-gpio,bus=4,i2c_gpio_sda=17,i2c_gpio_scl=27 dtoverlay=i2c-gpio,i2c_gpio_sda=23,i2c_gpio_scl=24 note no bus parm needed for bus 1, if you set bus parm (bus=3) i2cdetect -y 3 will show the slow info but not your device{s) i2cdetect -y 1 will


1

There is a known issue described on instructables about the buses ordering during the definition in the config.txt file. Never use bus 0 and 2, it is use for other things in the board like EPROM on hats etc For the April 2019 Raspbian release: You should always start with the highest bus (Bus 4 in case of two buses) in your config.txt and ...


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