Jump to content

Search the Community

Showing results for tags 'rpi4b'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Armbian
    • Armbian project administration
  • Community
    • Announcements
    • SBC News
    • Framework and userspace feature requests
    • Off-topic
  • Using Armbian
    • Beginners
    • Software, Applications, Userspace
    • Advanced users - Development
  • Standard support
    • Amlogic meson
    • Allwinner sunxi
    • Rockchip
    • Other families
  • Community maintained / Staging
    • TV boxes
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families
  • Support

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Matrix


Mastodon


IRC


Website URL


XMPP/Jabber


Skype


Github


Discord


Location


Interests

  1. 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
  2. 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)?
  3. 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?
  4. 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!
  5. 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.
  6. 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?
  7. 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.
  8. 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
  9. Where can I get the kernel headers for rpi4b for 5.15.92-bcm2711? sudo armbian-config does not get it
  10. 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
  11. 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.
  12. 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?
  13. 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
  14. 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
  15. 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
  16. 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
  17. 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
  18. 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.
  19. 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
  20. 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?
  21. 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?
  22. 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.
  23. $ 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?
  24. Texto original em português BR Ola. Tentei gravar uma imagem do armbian para Raspberry Pi num pendrive de 8 gb e testar no Rpi 4 de 2gb que uso exclusivamente para testes e estudo mas o “Raspberry Pi Imager” que tenho no Rpi 4 de 4 gb não permitiu alegando falta de espaço no pendrive. Gravei num SDCard de 16 gb, testei e achei o sistema excelente, então resolvi: 1- Desinstalar alguns aplicativos para diminuir o tamanho. 2- Com consulta na web, usar o comando dd e criar uma nova imagem. 3- Continuando com ajuda da web, diminuir o tamanho da imagem criada anteriormente para eliminar o espaço vazio dessa imagem. 4- Gravar essa nova imagem no pendrive. Tudo funcionou perfeitamente mas não consegui descobrir como fazer a configuração automática inicial para expansão da segunda partição, criação de senha Linguagem de uso, etc . . . Aqui mesmo descobri o comando para expandir automaticamente a partição, também sei que com o comando sudo passwd posso criar/modificar uma senha mas seria possível reativar essa configuração do primeiro boot? Essa configuração do primeiro boot e um script? Desde ja, muito obrigado pela atenção e ajuda. Translated by uncle google to english Hello. I tried to record an image of the armbian for Raspberry Pi on an 8 gb flash drive and test it on the 2gb Rpi 4 that I use exclusively for testing and study but the “Raspberry Pi Imager” that I have on the 4 gb Rpi 4 did not allow it, claiming lack of space on the pen drive. Recorded on a 16 gb SDCard, tested and found the system excellent, so I decided: 1- Uninstall some apps to decrease the size. 2- With web query, use the dd command and create a new image. 3- Continuing with the help of the web, reduce the size of the previously created image to eliminate the empty space of this image. 4- Write this new image to the pendrive. Everything worked perfectly but I couldn't figure out how to do the initial auto-configuration for expanding the second partition, creating password Usage language, etc. . . Here I discovered the command to automatically expand the partition, I also know that with the command sudo passwd I can create/modify a password but would it be possible to reactivate this configuration on the first boot? Is this first boot configuration a script? Thanks in advance for your attention and help. Translated by uncle google to english
  25. Hi all; Recently i installed a armbian and seems to be all ok less the global memory detection. I don't know by but the system have only detect 256 Mb. from total amount of 512Mb. (/proc/meminfo). Of course, i proved another OS and detet all memory so i know that's not a hardware problem. Is there any trick on kernel or something misconfigurated?
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines