Search the Community

I had to freeze my device on Kernel 6.1.92 & Bullseye to remain operational. Now trying to update/upgrade to Kernel 6.6.nn I run into following probs: 1) Using Armbian-config defreeze and subsequently switch to kernel 6.6.nn works OK 4me, but subsequent apt-get update/upgrade throws me back to kernel 6.1.104. Armbian-config has changed significantly w/ No other Kernel available. 2) Using Armbian-config defreeze, only and going directly to apt-get update/upgrade throws me back to kernel 6.1.104 as well and from Bullseye back to Buster! Its a mess! Will this eventually be corrected and when? RGDS

Hello! I'm tryiing to make iBeacon scan service. But can't make Bluetooth work on OPi0+2H5. I'm using "Armbian_20.02.1_Orangepizeroplus2-h5_bionic_current_5.4.20_minimal.img" as OS, but no hci devices in system after start. I reded many topics from this forum and nothig helps me. Can't start BT Is BlueTooth part work on this board? Can I use it? I need only "lescan" functional....

Hi all, I need to customize the /etc/fstab during the build to mount a mtd partition and also to override some mountpoints with tmpfs in order to reduce wearing on mmc. So, have added the following lines to customize-image.sh: cat <<EOT >> /etc/fstab # Reduce SD wearing by storing log files into ram (no need as overlayroot is used to freeze all the rootfs) tmpfs /tmp tmpfs defaults,noatime,nosuid,nodev 0 0 tmpfs /run tmpfs defaults,noatime,nosuid,nodev 0 0 tmpfs /var/tmp tmpfs defaults,noatime,nosuid,nodev 0 0 tmpfs /var/log tmpfs defaults,noatime,nosuid,nodev,noexec 0 0 tmpfs /var/lib/logrotate tmpfs defaults,noatime,nosuid,nodev,noexec,size=1m,mode=0755 0 0 tmpfs /var/lib/sudo tmpfs defaults,noatime,nosuid,nodev,noexec,size=1m,mode=0700 0 0 # MTD EEPROM memory dev/mtdblock0 /mnt/mtd jffs2 ro,relatime 0 0 EOT However changes in /etc/fstab are overridden somewhere over the build process, and this is the resulting /etc/fstab: UUID=c8167755-b557-4288-9109-9108bc48dd94 / btrfs defaults,noatime,commit=600 0 1 UUID=27ac6cc6-eff3-4736-a7bd-5517e3b150c0 /boot ext4 defaults,commit=600,errors=remount-ro 0 2 tmpfs /tmp tmpfs defaults,nosuid 0 0 Is there a way to safely patch the /etc/fstab file? Thanks very much! Andrea

Hi guys, I downloaded Armbian 24.2.1 Jammy CLI (Armbian_24.2.1_Orangepizeroplus_jammy_current_6.6.16.img.xz) for the Orange Pi Zero Plus and it's not booting. Boot log below: U-Boot SPL 2024.01-armbian (Feb 09 2024 - 19:21:37 +0000) DRAM: 512 MiB Trying to boot from MMC1 NOTICE: BL31: v2.9(debug):armbian NOTICE: BL31: Built : 19:20:27, Feb 9 2024 NOTICE: BL31: Detected Allwinner H5 SoC (1718) NOTICE: BL31: Found U-Boot DTB at 0x20a4ef0, model: Xunlong Orange Pi Zero Plus INFO: ARM GICv2 driver initialized INFO: Configuring SPC Controller NOTICE: PMIC: Assuming H5 reference regulator design INFO: BL31: Platform setup done INFO: BL31: Initializing runtime services INFO: BL31: cortex_a53: CPU workaround for 855873 was applied INFO: BL31: cortex_a53: CPU workaround for 1530924 was applied SCP/INF: Crust v0.6.10000 INFO: PSCI: Suspend is available via SCPI INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x4a000000 INFO: SPSR = 0x3c9 U-Boot 2024.01-armbian (Feb 09 2024 - 19:21:37 +0000) Allwinner Technology CPU: Allwinner H5 (SUN50I) Model: Xunlong Orange Pi Zero Plus DRAM: 512 MiB Core: 67 devices, 20 uclasses, devicetree: separate WDT: Not starting watchdog@1c20ca0 MMC: mmc@1c0f000: 0, mmc@1c10000: 1 Loading Environment from FAT... MMC: no card present ** Bad device specification mmc 0 ** In: serial,usbkbd Out: serial,vidconsole Err: serial,vidconsole Net: eth0: ethernet@1c30000 MMC: no card present ** Bad device specification mmc 0 ** Couldn't find partition mmc 0 MMC: no card present ** Bad device specification mmc 0 ** Couldn't find partition mmc 0 starting USB... Bus usb@1c1a000: sun4i_usb_phy phy@1c19400: External vbus detected, not enabling our own vbus USB EHCI 1.00 Bus usb@1c1a400: USB OHCI 1.0 Bus usb@1c1b000: USB EHCI 1.00 Bus usb@1c1b400: USB OHCI 1.0 scanning bus usb@1c1a000 for devices... 1 USB Device(s) found scanning bus usb@1c1a400 for devices... 1 USB Device(s) found scanning bus usb@1c1b000 for devices... 1 USB Device(s) found scanning bus usb@1c1b400 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Autoboot in 1 seconds, press <Space> to stop MMC: no card present Device 0: unknown device ethernet@1c30000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! missing environment variable: pxeuuid Retrieving file: pxelinux.cfg/01-02-01-a6-4a-c9-69 ethernet@1c30000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Retrieving file: pxelinux.cfg/00000000 ethernet@1c30000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Retrieving file: pxelinux.cfg/0000000 ethernet@1c30000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Retrieving file: pxelinux.cfg/000000 ethernet@1c30000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Retrieving file: pxelinux.cfg/00000 ethernet@1c30000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Retrieving file: pxelinux.cfg/0000 ethernet@1c30000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Retrieving file: pxelinux.cfg/000 ethernet@1c30000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Retrieving file: pxelinux.cfg/00 ethernet@1c30000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Retrieving file: pxelinux.cfg/0 ethernet@1c30000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Retrieving file: pxelinux.cfg/default-arm-sunxi-sunxi ethernet@1c30000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Retrieving file: pxelinux.cfg/default-arm-sunxi ethernet@1c30000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Retrieving file: pxelinux.cfg/default-arm ethernet@1c30000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Retrieving file: pxelinux.cfg/default ethernet@1c30000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Config file not found ethernet@1c30000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! ethernet@1c30000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! => %

Hello, Like it happened to @Grogorio in 2016, I need to introduce a boot delay on my OrangePi Zero Plus (Armbian 23.02.2 Focal) to allow time for other network elements in my setup to boot. As per what I have read somewhere, this can done by adding a 'boot_delay=n' line in /boot/config.txt, however I don't see this file in Armbian; I've also tried to add the line, but it does not seems to be working. Furthermore, the max delay that can be setup there is 10 seconds, but I need a longer delay. Can someone help? TIA

I've change OpiZero's cpu from H2+ to H5, and made linux5.4.65 image with the option of "Orangepiplus (H5)" of the Build-Package which described in the Orangepi manual. After the linux startup, the output of command DMESG shows "sunxi-mmc 1c10000.mmc: Cannot do DMA to address 0x00008000514a3870", and TRACE as follows: [ 212.402793] xradio_wlan: version magic '5.15.27-station SMP preempt mod_unload aarch64' should be '5.4.65-sunxi64 SMP mod_unload aarch64' [ 248.019893] xradio_wlan: loading out-of-tree module taints kernel. [ 248.024327] xradio_wlan: module verification failed: signature and/or required key missing - tainting kernel [ 248.027506] xradio: XR819 device discovered [ 248.030479] sunxi-mmc 1c10000.mmc: Cannot do DMA to address 0x0000800051e83870 [ 248.030507] sunxi-mmc 1c10000.mmc: overflow 0x0000800051e83870+8 of DMA mask ffffffff bus mask 0 [ 248.030538] ------------[ cut here ]------------ [ 248.030572] WARNING: CPU: 2 PID: 1513 at kernel/dma/direct.c:35 report_addr+0x38/0xa0 [ 248.030578] Modules linked in: xradio_wlan(OE+) zstd rtl8xxxu rtl8192cu rtl_usb rtl8192c_common rtlwifi mac80211 cfg80211 libarc4 snd_soc_simple_card snd_soc_simple_card_utils sun8i_codec_analog sun8i_adda_pr_regmap sun4i_i2s sun4i_gpadc_iio sun4i_tcon sun8i_tcon_top sun8i_mixer cpufreq_dt zram sch_fq_codel usb_f_acm u_serial g_serial libcomposite ip_tables x_tables autofs4 fixed gpio_regulator [ 248.030691] CPU: 2 PID: 1513 Comm: insmod Tainted: G OE 5.4.65-sunxi64 #2.2.2 [ 248.030697] Hardware name: Xunlong Orange Pi Zero Plus (2pw5, Linux-Kernel Device Tree) (DT) [ 248.030707] pstate: 80000005 (Nzcv daif -PAN -UAO) [ 248.030720] pc : report_addr+0x38/0xa0 [ 248.030731] lr : report_addr+0x98/0xa0 [ 248.030736] sp : ffff800011e833c0 [ 248.030741] x29: ffff800011e833c0 x28: ffff800011e83dd0 [ 248.030752] x27: 0000000000000000 x26: ffff800011e836e8 [ 248.030763] x25: ffff800011e83600 x24: 0000000000000000 [ 248.030773] x23: 0000000000000002 x22: ffff000036706810 [ 248.030782] x21: 0000000000000008 x20: ffff000035ccf000 [ 248.030793] x19: ffff000036706810 x18: 0000000000000020 [ 248.030802] x17: 00000000000012b0 x16: 00000000000012a0 [ 248.030812] x15: ffff800011085000 x14: 6b73616d20414d44 [ 248.030822] x13: 20666f20382b3037 x12: 3833386531353030 [ 248.030832] x11: 3038303030307830 x10: 0000000000000000 [ 248.030842] x9 : 0000000000000003 x8 : 00000000000001b4 [ 248.030851] x7 : 0000000000000001 x6 : 0000000000000001 [ 248.030861] x5 : 0000000000000000 x4 : 0000000000000001 [ 248.030870] x3 : 0000000000000006 x2 : 6eac74d7450f9a00 [ 248.030879] x1 : 6eac74d7450f9a00 x0 : 0000000000000000 [ 248.030889] Call trace: [ 248.030903] report_addr+0x38/0xa0 [ 248.030914] dma_direct_map_page+0x110/0x130 [ 248.030924] dma_direct_map_sg+0x78/0xe0 [ 248.030939] sunxi_mmc_request+0x70/0x4f0 [ 248.030952] __mmc_start_request+0x64/0x130 [ 248.030962] mmc_start_request+0x90/0xb8 [ 248.030973] mmc_wait_for_req+0x6c/0x100 [ 248.030985] mmc_io_rw_extended+0x250/0x2a8 [ 248.030996] sdio_io_rw_ext_helper+0x18c/0x230 [ 248.031007] sdio_memcpy_fromio+0x1c/0x28 [ 248.031072] sdio_data_read+0x1c/0x28 [xradio_wlan] [ 248.031118] __xradio_read+0x28/0x40 [xradio_wlan] [ 248.031166] xradio_reg_read+0x3c/0x60 [xradio_wlan] [ 248.031214] xradio_load_firmware+0x34/0xe18 [xradio_wlan] [ 248.031261] xradio_core_init+0x130/0x460 [xradio_wlan] [ 248.031308] sdio_probe+0x130/0x164 [xradio_wlan] [ 248.031321] sdio_bus_probe+0x12c/0x198 [ 248.031337] really_probe+0xdc/0x430 [ 248.031348] driver_probe_device+0xdc/0x130 [ 248.031358] device_driver_attach+0x6c/0x78 [ 248.031367] __driver_attach+0x9c/0x168 [ 248.031376] bus_for_each_dev+0x6c/0xc0 [ 248.031385] driver_attach+0x20/0x28 [ 248.031394] bus_add_driver+0x138/0x218 [ 248.031404] driver_register+0x60/0x110 [ 248.031414] sdio_register_driver+0x24/0x30 [ 248.031463] xradio_sdio_register+0x14/0x20 [xradio_wlan] [ 248.031510] xradio_core_entry+0xc/0x1000 [xradio_wlan] [ 248.031523] do_one_initcall+0x50/0x1a8 [ 248.031537] do_init_module+0x50/0x1f0 [ 248.031547] load_module+0x1f68/0x2510 [ 248.031558] __do_sys_finit_module+0xac/0x110 [ 248.031568] __arm64_sys_finit_module+0x1c/0x28 [ 248.031583] el0_svc_common.constprop.0+0x68/0x160 [ 248.031594] el0_svc_handler+0x20/0x80 [ 248.031603] el0_svc+0x8/0x1fc [ 248.031610] ---[ end trace d07a211fb8606773 ]--- [ 248.031628] sunxi-mmc 1c10000.mmc: dma_map_sg failed [ 248.031637] sunxi-mmc 1c10000.mmc: map DMA failed [ 248.031662] xradio WRN: FWIO: can't read config register, err=-12. [ 248.043881] xradio PM-DEV: xradio_pm_release root@orangepizeroplus:/home/orangepi# rmmod xradio_wlan.ko rmmod: ERROR: Module xradio_wlan is in use root@orangepizeroplus:/home/orangepi# can give me some hints of clues to solve the problem ? thx.

I have an Orange pi 5 (could not find this in the tags list). I have created the Armbian micro sd card successfully I believe. However when I run this I get a long list of command line entries. I complete the enter password/user name entries then I end up at the following command root@orangepi5~# Then everything stops, no desktop just this command. Is it possible to get to the desktop by typing something into this command. As I understand it you should get one single chance to get to the desktop on first run, I apparently have not got this one chance. I believe I am trapped in the command line with no way at all to escape to the desktop. I will be polite and say I find this setup to be strange to say the least. I have successfully used the Orange pi OS on the Orange pi 5, It just went straight to the desktop as it should. Also I have used Raspbian on my raspberry pi 4, again the first run went straight to the desktop. If it is possible to go to a desktop with a normal GUI how do I do this please. Any help would be much appreciated.

The internet is full of reports, that USB devices get disconnected at random after some time. Camera or disc-drives, keyboards etc. For me it was a GPS device. The solution is described here https://hamwaves.com/usb.autosuspend/en/ and here https://www.kernel.org/doc/Documentation/usb/power-management.txt

I cut/paste a related information exchange I had w/ Kent from the gpiod mailing list. The arbian-monitor output is in the attached file. >>>>>>>> I wired a GPIO Pin to GND. Upon the cmd: sudo gpiomon -r -n1 -Bpull-up <chip> <offset> the program exits immediately with 1 event, although there was never a rising edge due to the fix wire to GND. Is this a feature or a bug, and is it reproducible? < Not a feature and not reproducible for me on a Raspberry Pi4 with the setup you describe, so probably a bug specific to your hardware platform, whatever that may be. If it is 100% reproduceable for you, and assuming it is an initialisation issue so you only get the one spurious event, how about using -n2 as a workaround ? Cheers, Kent. > It appears 2b reproduceable 100% on my OrangePi zero+ (Allwinner H5) and using -n2 does the trick, but isn't gpiod not supposed to work on all commercial HW platforms and related kernels, rather then only on RPI?? < gpiod will work on any platform with a supporting kernel. How well depends on the underlying hardware and driver. The RPi4 was merely a counter-example demonstrating that your issue is not universal, using hardware I happen to have readily available. Cheers, Kent. > So if I understand you right, gpiod works on sort of a logical level, while the HW dependend part depends of the kernel driver implementation of the specific HW? < libgpiod is a userspace library and tools to access GPIO lines via the Linux GPIO character device. The actual interfacing to the hardware is performed by the kernel and appropriate drivers for your hardware. As your problem does not exhibit on other hardware, the root cause of your problem probably lies in the driver for your hardware, not in libgpiod nor the gpiolib subsystem of the kernel. But you would need to debug it further to be sure. Cheers, Kent. * Event should be more correct than Interrupt. I made some trial to understand if it is reproduceable, but I have difficulties defining, when it happens. After RESET there is no spurious event. The spurious event appears to happen, when the line was moved: RESET, gpiomon -r -n1 -Bpull-up 1 6 => No event, -> pull line up /down, => event (as expected), gpiomon -r -n1 -Bpull-up 1 6 => false event There might be an issue w/ pending interrupts, when the line is bouncing when pulled up/down. The 2nd gpiodmon cmd might catch one of the pending interrupts. (Just an idea). This would hint to an initialisation problem, that pending line states are not preempted, before the int is attached. If I just let the line go up (by pull-up) and leave it "1", I get continuous false events on every gpiomon... cmd, just like "level interrupts" Kent Gibson and I performed checks independently on our RPIs and we both can confirm that the problem does no occur on the RPI: Linux raspberrypi 5.10.63-v7+ #1459 SMP Wed Oct 6 16:41:10 BST 2021 armv7l GNU/Linux armbian-monitor-U.txt

http://ix.io/3XOk I attach the video of the bug in armbian-config. I tried editing the environment.txt file and enabling w1-gpio and pin but it doesn't work. the device connected is a temperature sensor that has always worked for the past 4 years is a ds18b20 (https://forum.armbian.com/topic/8095-orangepi-zero-not-working-with-1-wire/) Screen record from 2022-05-15 10.33.29.webm

Orange pi zero plus 'shutdown -r now' shuts down, won't reboot within 20 minutes. Have to power cycle. reboot worked initially. I installed a few bits and firefox. Not sure what triggered it. In other reports I read kernel upgrades. Could it do a lengthy fsck during boot? 64 GB SD-card/file system. Would some (red or green) LED shine? It's all dark.