Search the Community

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

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.

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

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, As I have often said, I am very satisfied with this LINUX implementation on the RASPI PI4 board. In the meantime, I noticed one small thing and that was somehow related to the 4GB version of my RASPI. I often had to record a KERNEL crash here; this did not happen under the 8GB version until now. But now to my actual question: How can I activate the CAMERA port under this Linux version so that I can connect a camera there? Best regards Z. Matthias

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

Hello all, I have installed the image "Armbian 23.02.0-trunk.0176 Lunar with bleeding edge Linux 6.1.6-bcm2711" on my two Raspi 4 systems. One system runs via cable and the other via WLAN. At the beginning there were some problems with the IPv6 - kernel, if "apt update" was executed. I got this problem under control with "disable ipv6".... Since then, both systems run flawlessly & without problems. With the implementation of GPIO you should fall back on an existing GPIO - version, which works in any case also under this image; also for 64bit. One small thing I would like to know very much, because on the system with the cable the WaveShare PoE - HAT is installed and I would like to monitor via software very much the FAN. Unfortunately, this does not work because the software does not see "I2C". In the Config - File, however, you see this as "enable" - What can I do here? Does anyone have an idea how I can enablen the I2C so that this works? Best regards from Germany..... Z. Matthias

Hello everybody. I've faced the issue: Armbian_22.08.7 official image (Armbian_22.08.1_Rpi4b_jammy_current_5.15.61.img) failed to boot on RPi3B plus. The same image boots fine on RPi 4B Could not get serial console output (output is empty) Older official image Armbian_22.08.1_Rpi4b_jammy_current_5.15.61.img boots on Rpi3B plus just fine. As I've found out the reason is incorrect boot partition type set for the image. Armbian_22.08.1 (boots fine) boot partition type is "c" (W95 FAT32 LBA) Armbian_22.08.7 (doesn't boot) boot partition type is "ef" (EFI) After manually changing boot partiton type to "c" (W95 FAT32 LBA) for the image Armbian_22.08.7_Rpi4b_jammy_current_5.15.74_minimal.img it begins to boot Please check fdisk output ===================== "Good" image: $ fdisk -l Armbian_22.08.1_Rpi4b_jammy_current_5.15.61.img Disk Armbian_22.08.1_Rpi4b_jammy_current_5.15.61.img: 3 GiB, 3196059648 bytes, 6242304 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x79597c7b Device Boot Start End Sectors Size Id Type Armbian_22.08.1_Rpi4b_jammy_current_5.15.61.img1 8192 532479 524288 256M c W95 FAT32 (LBA) Armbian_22.08.1_Rpi4b_jammy_current_5.15.61.img2 532480 6242303 5709824 2,7G 83 Linux ===================== "Bad" image: $ fdisk -l Armbian_22.08.7_Rpi4b_jammy_current_5.15.74_minimal.img Disk Armbian_22.08.7_Rpi4b_jammy_current_5.15.74_minimal.img: 2,5 GiB, 2680160256 bytes, 5234688 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x1d7b3f1b Device Boot Start End Sectors Size Id Type Armbian_22.08.7_Rpi4b_jammy_current_5.15.74_minimal.img1 8192 532479 524288 256M ef EFI (FAT-12/16/32) Armbian_22.08.7_Rpi4b_jammy_current_5.15.74_minimal.img2 532480 5234687 4702208 2,2G 83 Linux ===================== The same story is for manual build from the repo (Armbian 22.08.11) Image build is fine. Image doesn't boot on RPi3Bplus Boots fine on RPi4 Manual compile command is: #!/bin/bash BOARD_NAME_PARAM="rpi4b" LINUX_DISTRO_PARAM="jammy" ARMBIAN_BUILD_OPTIONS="\ BOARD=$BOARD_NAME_PARAM \ BRANCH=current \ FULL_DESKTOP=no \ BUILD_DESKTOP=no \ BUILD_MINIMAL=yes \ INSTALL_HEADERS=no \ KERNEL_ONLY=no \ KERNEL_CONFIGURE=no \ RELEASE=$LINUX_DISTRO_PARAM \ COMPRESS_OUTPUTIMAGE=\"sha,img,xz\" \ ARMBIAN_CACHE_ROOTFS_PATH=/mnt/armbian-cache/rootfs \ ARMBIAN_CACHE_TOOLCHAIN_PATH=/mnt/armbian-cache/toolchain \ " sudo ./compile.sh $ARMBIAN_BUILD_OPTIONS --------------------------- As example - please check out notice from https://github.com/pftf/RPi3 Create an SD card (or USB drive if you plan to use USB Boot) in MBR mode with a single partition of type 0x0c (FAT32 LBA) or 0x0e (FAT16 LBA). Then format this partition to FAT32. Note: Do not try to use GPT for the partition scheme or 0xef (EFI System Partition) for the type, as these are unsupported by the CPU-embedded bootloader.

Hi, I'm interested in getting a compact ARM-based processor (something like a RPI or ASUS TinkerBoard) that can output a 2560x720 output resolution. The current available documentation seems quite sparce and Google searches are littered with people having problems with establishing their chosen video resolutions so I am sceptical! Any pointers would be gratefully received. Thank You, Dave

I am only sure, that Armbian_22.11.0-trunk_Rpi4b_jammy_edge_5.19.11_xfce_desktop.img.xz works with my hardware, maybe Armbian_22.11.0-trunk_Rpi4b_jammy_current_5.15.70_xfce_desktop.img.xz too. For sure I have problems with newer Armbian_22.11.0-trunk_Rpi4b_jammy_current_5.15.73_xfce_desktop.img.xz and Armbian_22.11.0-trunk_Rpi4b_jammy_edge_5.19.15_xfce_desktop.img.xz So where can I download older versions?

Armbian_22.11.0-trunk_Rpi4b_jammy_current_5.15.73_xfce_desktop.img.xz Raspberry PI400 Viewsonic VP930 (1280x1024) I checked the sha-sum and flashed 2 times a Patriot SXDC-128GB-card. When I boot the PI400 the monitors LED changes from green (power on) to yellow (standbye) for half an hour, when I start the PI400. It looks like there is a problem with this old monitor which supports 1280x1024 only. Don't know, if the boot routine checks the monitor, but the green LED can stay for 2sec, sometimes for 30sec. BTW Xubuntu 22.04 with an SSD works fine with the same hardware.

$ cvt 3840 2160 # 3840x2160 59.98 Hz (CVT 8.29M9) hsync: 134.18 kHz; pclk: 712.75 MHz Modeline "3840x2160_60.00" 712.75 3840 4160 4576 5312 2160 2163 2168 2237 -hsync +vsync $ xrandr --output HDMI-1 --mode 3840x2160_60.00 xrandr: Configure crtc 0 failed $ xrandr --verbose Screen 0: minimum 320 x 200, current 3840 x 2160, maximum 7680 x 7680 HDMI-1 connected primary 3840x2160+0+0 (0x41) normal (normal left inverted right x axis y axis) 708mm x 399mm ... CRTC: 0 CRTCs: 0 I would like to setup 4k with a PI400. I found https://docs.armbian.com/User-Guide_Fine-Tuning/ and followed the instructions Did I something wrong, or is this simply a bug?

I con do a screenshot with scrot and a terminal, but a screenshot with the P400 and PrtScn-Key does not work. Can anybody help me please?