Search the Community
Showing results for tags 'rpi4b'.
-
For Armbian-24.11.0 RPi ubuntu noble based builds wlan interface is missing Issue is present in Rpi3 B plus, RPi4 for current (kernel 6.6.x) and edge (kernel 6.10.x) armbian builds OS info ================ pi@rpi4b:~$ cat /etc/os-release PRETTY_NAME="Armbian-unofficial 24.11.0-trunk noble" NAME="Ubuntu" VERSION_ID="24.04" VERSION="24.04 LTS (Noble Numbat)" VERSION_CODENAME=noble ID=ubuntu ID_LIKE=debian HOME_URL="https://duckduckgo.com/" SUPPORT_URL="https://community.armbian.com/" BUG_REPORT_URL="https://armbian.atlassian.net/" PRIVACY_POLICY_URL="https://duckduckgo.com/" UBUNTU_CODENAME=noble LOGO="armbian-logo" ARMBIAN_PRETTY_NAME="Armbian-unofficial 24.11.0-trunk noble" pi@rpi4b:~$ uname -a Linux rpi4b 6.10.10-edge-bcm2711 #1 SMP PREEMPT Fri Sep 13 15:35:16 UTC 2024 aarch64 aarch64 aarch64 GNU/Linux ================ wlan interface is missing (at all): =============== pi@rpi4b:~$ ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host noprefixroute valid_lft forever preferred_lft forever 2: end0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether d8:3a:dd:8e:79:9a brd ff:ff:ff:ff:ff:ff inet 192.168.1.139/24 metric 100 brd 192.168.1.255 scope global dynamic end0 valid_lft 25034sec preferred_lft 25034sec inet6 fe80::da3a:ddff:fe8e:799a/64 scope link valid_lft forever preferred_lft forever =============== The reason is incorrect firmware files format inside /lib/firmware. Firmware files are zstd packed (has *.zst extensons). Broadcom driver is unable to load such files =================== pi@rpi4b:~$ dmesg|grep -i brcmfmac [ 4.387851] brcmfmac: F1 signature read @0x18000000=0x15264345 [ 4.395645] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6 [ 4.403229] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.bin failed with error -2 [ 4.403347] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.bin failed with error -2 [ 5.407124] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50 =================== Files from /lib/firmware: ============================ ls -l /lib/firmware/brcm | egrep "raspberrypi,4-model-b" lrwxrwxrwx 1 root root 17 Sep 21 22:27 BCM4345C0.raspberrypi,4-model-b.hcd.zst -> BCM4345C0.hcd.zst lrwxrwxrwx 1 root root 35 Sep 21 22:27 brcmfmac43455-sdio.raspberrypi,4-model-b.bin.zst -> ../cypress/cyfmac43455-sdio.bin.zst lrwxrwxrwx 1 root root 40 Sep 21 22:27 brcmfmac43455-sdio.raspberrypi,4-model-b.clm_blob.zst -> ../cypress/cyfmac43455-sdio.clm_blob.zst lrwxrwxrwx 1 root root 26 Sep 21 22:27 brcmfmac43455-sdio.raspberrypi,4-model-b.txt.zst -> brcmfmac43455-sdio.txt.zst ls -l /lib/firmware/cypress | egrep "cyfmac43455*" lrwxrwxrwx 1 root root 38 Sep 21 22:27 cyfmac43455-sdio.bin.zst -> /etc/alternatives/cyfmac43455-sdio.bin -rw-r--r-- 1 root root 1261 Apr 11 00:46 cyfmac43455-sdio.clm_blob.zst -rw-r--r-- 1 root root 384405 Apr 11 00:46 cyfmac43455-sdio-minimal.bin.zst -rw-r--r-- 1 root root 453440 Apr 11 00:46 cyfmac43455-sdio-standard.bin.zst ls -l /etc/alternatives/cyfmac43455-sdio.bin lrwxrwxrwx 1 root root 55 Apr 11 00:46 /etc/alternatives/cyfmac43455-sdio.bin -> /lib/firmware/cypress/cyfmac43455-sdio-standard.bin.zst ============================ To fix this issue following steps have to be done: 1) install zstd package 2) unpack *.zst files inside /lib/firmware using unzstd 3) recreate all symlinks inside /lib/firmware from symlink_src(*.zst) => to symlink_dst(*.zst) to (no *.zst) 4) recreate /etc/alternatives/cyfmac43455-sdio.bin symlink /etc/alternatives/cyfmac43455-sdio.bin -> -> /lib/firmware/cypress/cyfmac43455-sdio-standard.bin.zst to /etc/alternatives/cyfmac43455-sdio.bin -> -> /lib/firmware/cypress/cyfmac43455-sdio-standard.bin The recipe is proven to be working - wlan interface is back. Tested for Rpi3 B plus, RPi4 current (kernel 6.6.x) and edge (kernel 6.10.x) armbian builds
-
Today I imaged 'Armbian_24.8.0-trunk.542_Rpi4b_noble_current_6.6.44_gnome_desktop.img' on to an SD card and then put it in my Raspberry Pi 4 GB. It booted up first time no issues and I went through the setup flow. I am using wired ethernet and was able to reach it remotely immediately. I installed all the updates. When I do "sudo shutdown -h -r now" on the command line (either via SSH or locally in the terminal) it does not reboot. The device stops responding to pings and no longer has HDMI output. If I power cycle the board once, it does not boot up. On the second power cycle it boots up. This seems really odd. Is this some known issue with the raspberry pi 4 ?
-
Hi All, I wanted to add some dtoverlay lines to the pi's config.txt which was in /boot/firmware/config.txt and I notice the folder is empty ? WTF the pi is running ok - how can this be ?
-
Hello guys! Probably some of you know me as the MadEDoctor from Youtube. For those of you who don't know my channel and don't know what I am doing at the moment - Long story short I got my hands on a 16GB RAM chip that should be compatible with the Raspberry Pi 4 hardware. But there is a problem I am facing... That is I am unable to boot any OS different from VMware (arm version) and RISC OS (that is pretty much useless). When I try to boot Raspbian for example - It shows the rainbow square and then gets stuck on a completely black screen and it draws around 500mA... I contacted Jeff Geerling with the hope he could help with this project. He wrote a post on the official RPi forum. As it seems the engineers of the Pi just don't want to help and even worse are lying that the hardware doesn't support 16GB of RAM... Then one guy in the comments suggested I write here and ask for help... and here I am I will be pretty thankful if somebody could help me with this project. Here I provide datasheets for both the 16GB chip I got and the 8GB OEM one so you can compare them. 8GB - Micron D9ZCL | MT53E2G32D4NQ-046 WT:A :https://www.farnell.com/datasheets/3681594.pdf 16GB - Micron D8CBG | MT53E4G32D8CY-046 WT:C :https://4donline.ihs.com/images/VipMasterIC/IC/MICT/MICT-S-A0017462930/MICT-S-A0017465122-1.pdf?hkey=52A5661711E402568146F3353EA87419 And this is the video where I show what I have done to this point: https://youtu.be/vtym0TAWNto
-
Hey all... Looking to put something a LOT more lightweight than RaspiOS (and not-modern-desktoppy at all, please) on my Pi4Bs. Found out about armbian from the Wikipedia page and downloaded the Jammy CLI image, but I can't get either gitlab or github to talk to me for downloading either of the recommended imagers; gitlab just gives me a blank page (no HTMl at all, per Firefox "view source") and github outright refuses connections. If it's important I do not have accounts on either system, and am loath to create same, although I could if necessary. I don't have Internet at home so I'm doing this from a Win10 PC at my public library; it's running the current Firefox (122.0). (My Pis will also live offline; I don't currently have a portable screen/mouse/KB to haul down here to do online installs, so I know I'll be stuck with only whatever's already in your images, for now anyway.) Can I just dd the image to a new/blank uSD card (Sandisk class 10, A1)? I'm fully capable of verifying the result, been admining UNIX systems since the 80s and Linux since 0.99pl6 or so... (I'll surely have more questions about making any resulting system work without internet connectivity, but first things first.)
-
Hello, I am planning to create a Kubernetes cluster from 5 Raspberry PI and one of the alternatives mentioned in tags, 9 hosts in total. I want to mount and customize the installation images with ssh keys, static IP address, etc, and to skip the initial script offered at login by the CLI images. Can you point me to the right piece of documentation? Thank you, Stefanita Vilcu
- 2 replies
-
- Radxa ROCK 3A
- Raspberry Pi 4B
-
(and 2 more)
Tagged with:
-
Hello, I have a bunch of boards (rpi4b, rpi5, orangepi5, orangepi5-plus, nanopct6, rock3a, rock5b, vim4) in a Kubernetes cluster using Cilium. Cilium requires CONF_SCHEDSTATS=y in the kernel, which is dependent on CONFIG_DEBUG_KERNEL=y but... in build/lib/functions/compilation/armbian-kernel.sh we have # DONE: Disable: debug option kernel_config_set_n DEBUG_KERNEL # Armbian doesn't know how to package a debug kernel. Which invalidates the option I enabled during ./compile.sh BOARD=... BRANCH=... kernel-config Except for the VIM4, with DEBUG_KERNEL enabled in build/config/sources/families/meson-s4t7.conf Is there a way to enable DEBUG_KERNEL for the rest of the boards? Thank you! Stefanita Vilcu
-
I have a RasPi 4b, I'm trying to understand how the device tree is modified so I can use the methodology eventually for a board that has a CM4 on it. So from a virgin clone of the build repo: ./compile.sh BOARD=rpi4b BRANCH=edge RELEASE=bookworm BUILD_MINIMAL=yes KERNEL_CONFIGURE=no KERNEL_GIT=full install image on SD card and boot the device, go through Armbian-setup. All well and good, then varify device tree used for the boot: cat /proc/device-tree/model gets me a: Raspberry Pi 4 Model B Rev 1.5 OK so now lets modify the device tree: ./compile.sh BOARD=rpi4b BRANCH=edge RELEASE=bookworm BUILD_MINIMAL=yes KERNEL_CONFIGURE=no KERNEL_GIT=full kernel-patch When the build pauses, we open another terminal and change the device tree file (note in the build log below I had modified all the CM4 device tree files): sudo nano ./arch/arm/boot/dts/broadcom/bcm2711-rpi-4-b.dts Only change is to modify the model line with a marker, like my initials, new line is: model = "Raspberry Pi 4 Model B AJW"; close editor, and hit enter to restart the build, then copy resulting patch file to: userpatches/kernel/archive/bcm2711-6.7/0010-simple-device-tree.patch rebuild as before, then burn new image to SD card and retest the device tree model, but no change is apparent. So how do you change the device tree for a RasPi 4? log-build-e9849e69-98be-4710-b3be-e05a30285a44.log
-
I need to get an armbian focal image for the Rpi4b. I've checked in https://archive.armbian.com and it only shows the current jammy variant. If anyone could tell me where I can download the deprecated images, it would be much appreciated.
-
Hi friends, I use armbian for long time, but these days I change my borad to RaspberryPi 4B. However I can not get kernel startup serial output from RPI as usual on the board. Does anyone has more information about that? What I want to do is a atonomy driving experiment environment. And I don't have monitor or keyboard attach to it. I will patch preempt_RT to get the RT linux kernel, so it's difficult for me to pull the RPI out of the test bench everytime and put back after setting the ssh or something everytime I flash new kernel or image. The armbian version I use is Armbian_23.11.1_Rpi4b_jammy_current_6.1.64.img Thanks in advance.
-
Hi All, as all my other boards run armbian I thought it only right that my raspberry 4b should run it, has anyone here successfuly installed Armbian on one ? I don't want to use Bookworm as it has Audio problems - my main use of the pi is to host Logitech media server running squeezelite TIA
-
Is there some shell script file inside /boot directory that gets called on system startup? Alternatively, is there any way to make such a script run by modifying only files inside /boot (like some config setting)?
-
Hi, I recently noticed that after updating to 24.02 the package "linux-libc-dev" did not receive a update. I have checked the current armbian archives and couldn't find anything for any arch. Just to be sure i've also built armbian 24.5 images for bananapi (noticed this on a bananapi board) and rpi4b (as a well supported board) and no linux-libc-dev[...].deb was built. It seems that with the buildsystem change the files packages/armbian/mkdebian and packages/armbian/builddeb were retired (commit e98c66b, v23.11.1) which previously handled building the kernel packages and included linux-libc-dev. Unfortunately linux-libc-dev is a dependency for libc6-dev and in turn also linux-headers... To build such a package i think one would have to add the function to lib/functions/compilation/kernel-debs.sh, similar to the way linux-dtb is built and add it to artifact_map_packages in lib/functions/artifacts/artifact-kernel.sh to be built in the process. Does anyone agree with this observation? I'm not sure as I am pretty new to the armbian build system... Is anyone aware of this and working on it? Thanks, valium
-
The versioning within Armbian seems to be inconsistent. On a up to date RPi4 The login message states that it is running Armbian 23.11.1: Welcome to Armbian 23.11.1 Jammy with Linux 6.6.18-current-bcm2711 /etc/os-release is listing both 22.04 and 24.2.1: PRETTY_NAME="Armbian 24.2.1 jammy" VERSION_ID="22.04" VERSION="22.04.4 LTS (Jammy Jellyfish)" ARMBIAN_PRETTY_NAME="Armbian 24.2.1 jammy" /etc/armbian-release says it is 23.11.1: VERSION=23.11.1 REVISION=23.11.1 So these are three different versions, making it confusing. Any idea what is going on here?
-
Searches suggest a USB reset script will fix but that says nothing found. It comes up after unplugging and replugging the dongle. Already configured with "nmcli c add type ethernet ifname enx00e04c68080d con-name HiQSDR autoconnect yes save yes ip4 192.168.2.196/24" After boot, nothing in lsusb for it and dmesg -T does not show it. Bus 001 Device 014: ID 0bda:8152 Realtek Semiconductor Corp. RTL8152 Fast Ethernet Adapter Things tried:- root@rpi4b:~# cat /etc/os-release PRETTY_NAME="Armbian 24.2.1 jammy" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04.3 LTS (Jammy Jellyfish)" VERSION_CODENAME=jammy ID=ubuntu ID_LIKE=debian HOME_URL="https://www.armbian.com" SUPPORT_URL="https://forum.armbian.com" BUG_REPORT_URL="https://www.armbian.com/bugs" PRIVACY_POLICY_URL="https://www.armbian.com" UBUNTU_CODENAME=jammy ARMBIAN_PRETTY_NAME="Armbian 24.2.1 jammy" root@rpi4b:~# cat /etc/udev/rules.d/40-modeswitch.rules # Copyright (C) 2009-2014 Stephan Raue (stephan@openelec.tv) ACTION!="add|change", GOTO="end_modeswitch" KERNEL!="sr[0-9]*", GOTO="end_modeswitch" SUBSYSTEM!="block", GOTO="end_modeswitch" root@rpi4b:~# vcgencmd bootloader_config [all] BOOT_UART=0 WAKE_ON_GPIO=1 POWER_OFF_ON_HALT=0 # Realtek RTL8152 chipset USB lan NIC # initial cdrom mode 0bda:8152, lan mode 0bda:8153 ATTRS{idVendor}=="0bda", ATTRS{idProduct}=="8152", RUN+="/tmp/setupusblanadapter.sh" LABEL="end_modeswitch" https://forums.raspberrypi.com/viewtopic.php?t=336517 doesn't help --- didn't try installing the suggested firmware root@rpi4b:~# raspi-config nonint do_boot_rom E1 /usr/bin/raspi-config: 1506: [: Illegal number: BOOTLOADER: up to date CURRENT: Thu May 11 06:26:03 AM UTC 2023 (1683786363) LATEST: Thu May 11 06:26:03 AM UTC 2023 (1683786363) RELEASE: stable (/lib/firmware/raspberrypi/bootloader-2711/stable) Use raspi-config to change the release. VL805_FW: Dedicated VL805 EEPROM VL805: up to date CURRENT: 000138c0 LATEST: 000138c0
-
I'm trying to get to the point where I can read time from the DS3231 RTC module on a Raspberry Pi 4. From what I understand, I first need to activate i2c bus, then load the kernel module that would work with the clock itself. So far i2cdetect tool fails to detect anything. There are no i2c-* devices in /dev either. I've read about "Hardware" option in armbian-config, but it's not showing up in the menu. I've also read that it's a matter of adding a device tree overlay. Does that apply for RPI4? The folder structure in /boot seems different from what documentation and several threads describe for other boards. What would be the steps for activating i2c bus on RPI4?
-
Hello Armbian Community, I am running Armbian on a Raspberry Pi 4 with a RAID 1 setup for my root filesystem. I've come across a warning in a guide for RaspiOS (link below) suggesting that firmware upgrades could disrupt the RAID setup. Robert Alexa's Guide on GitHub Given this, I have a few questions about handling Armbian kernel updates in a similar RAID configuration: How are kernel updates managed in Armbian when using RAID for the root filesystem, and are there any known issues similar to the one described in the guide? What precautions should I take when applying apt upgrade to ensure that my RAID remains bootable? Is the initramfs update process during Armbian kernel upgrades RAID-aware, or are there manual steps required to maintain RAID integrity? Does Armbian have specific guidance or documentation on managing RAID setups through system updates? Any advice, documentation references, or user experiences you could share would be incredibly helpful, especially to avoid any interruptions to my RAID system following updates. Thank you in advance!
-
So, i have a rpi4b, i was installing LightDM. and when I started the service I rebooted and it said lightdM failed to start. So, how do i enter a shell Like ZSH. When LightDM failed and I can not enter by normal means.
-
I'm attempting an install to the eMMC on a CM4 (mounted on an Axzez Interceptor) using armbian-install. I've booted Armbian 23.5 Jammy CLI from USB, and armbian-install runs fine, (boot from eMMC, system on eMMC) After transferring the rootfs I get the "Cleaning up ... Almost done." message, and then the following: Error while creating U-Boot loader image with mkimage Error: no u-boot package found, exiting I've run a full update / upgrade and installed armbian-config with no change. What's missing here?
-
I noticed there's a community overlay module that adds a "first boot" script which, among other things, allows you to connect to wifi without ever connecting a monitor or keyboard. But, this overlap doesn't seem to come with the current raspberry pi 4b image (Armbian_23.5.1_Rpi4b_jammy_current_6.1.29.img). I tried downloading the build script, but I don't see an option to enable overlays in that either. Is this supported at this time? Also, I know I could just use raspbian if I want this feature, but I'm hoping to work with armbian because I want my build process to be reproducible on other boards.
-
Using release Armbian_23.5.1_Rpi4b_jammy_current_6.1.29 on a Raspberry Pi 4b. From a clean install: $ sudo apt update $ sudo apt upgrade $ sudo apt install podman $ podman run --rm docker.io/library/hello-world Error: command required for rootless mode with multiple IDs: exec: "newuidmap": executable file not found in $PATH Podman runs fine with sudo, so for now I can use that as a workaround, but it would be nice to run rootless containers for dev environments. There is a related issue on the official podman repo, but the solutions there don't seem to apply to armbian. https://github.com/containers/podman/issues/9271
-
Where can I get the kernel headers for rpi4b for 5.15.92-bcm2711? sudo armbian-config does not get it
-
im on a fresh install of armbian cinnamon for the rpi4. i can not seem to get bluetooth working. there seems to be no bluetooth module loaded by kernel maybe? i tried to enable it using armbian-config, but it doesn't get activated by systemctl even when enabled. any ideas?
-
The `hardware` menu is missing on the current build - so been trying to manually install spidev module. I did add the following lines to armbianEnv.txt but I don't see anything yet in /dev/spi* overlays=spi-spidev param_spidev_spi_bus=0
-
Hello all, according to the hints on the ARMBIAN homepage the image "Armbian_23.02.0-trunk_Rpi4b_lunar_edge_6.1.5.img" should work with the Raspi 3. Unfortunately it does not work properly, the system does not want to boot with it.... The name of the image says that it was generated for Raspi4, but -as I said- the homepage says that this image would also be compatible for the other Raspberry systems mentioned there. Can anyone tell me what the reason could be, because I would love to use this ingenious image for the Raspi 3. Best regards from Berlin Z. Matthias