Search the Community

Hello, I have Orange Pi One Plus with the kernel 5.15.80 of Armbian 22.11.1 and work well. , but after upgrading to 23.8.1 kernel 6.1.47 the network interfaces stop working at all. Even I try the 23.05.1, 23.05.6 all have same error which because the kernel is 6.1.x. Currenly I limited the internet access without the the network. May I know how to fix it in the console or someone can help to generate the 23.11.1 image for fixed this error. Thanks The error message like as below in the console terminal. [ 9.899195] dwmac-sun8i 5020000.ethernet eth0: __stmmac_open: Cannot attach to PHY (error: -19) The spec of the system: dmesg | grep eth0 [ 36.352751] dwmac-sun8i 5020000.ethernet eth0: Register MEM_TYPE_PAGE_POOL RxQ-0 [ 36.353587] dwmac-sun8i 5020000.ethernet eth0: __stmmac_open: Cannot attach to PHY (error: -19) uname -a Linux orangepioneplus 6.1.47-current-sunxi64 #3 SMP Wed Aug 23 15:52:42 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux ip address 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 valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 02:01:e7:xx:xx:xx brd ff:ff:ff:ff:ff:ff

Few years ago I setup armbian with 5.4.85 kernel. now try to update from instructions: sudo apt update sudo apt upgrade sudo armbian-config System->Other and got "No other kernels available!" Googling this error didn't help, and worst that I can't now install kernel headers Is there some update to current kernel (5.15) from bash? or linux build in common

I have this small 64bit H6 orange pi and SSD connected via USB, runs "Armbian 22.11.4 Jammy". Now I am trying to move /home and /tmp to the USB mounted drive to save RAM and move lots of writes from an SD card to a bigger and more capable external SSD. I uninstalled overlayfs, disabled tmp.mount and whatever there was with "tmp" in the service name. aik@hass:~$ cat /etc/fstab UUID=ecc7fb6d-12ab-41b9-b11a-c2c9b78e3bd1 / ext4 defaults,noatime 0 1 /dev/sda2 none swap defaults 0 0 /dev/sda3 /mnt/sda ext4 defaults,sync 0 0 /dev/sda4 /tmp ext4 defaults,sync 0 0 aik@hass:~$ cat /proc/cmdline root=UUID=ecc7fb6d-12ab-41b9-b11a-c2c9b78e3bd1 rootwait rootfstype=ext4 console=ttyS0,115200 console=tty1 consoleblank=0 loglevel=1 ubootpart=167303c8-01 usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u cgroup_enable=memory swapaccount=1 aik@hass:~$ systemctl | grep sda sys-devices-platform-soc-5311000.usb-usb2-2\x2d1-2\x2d1:1.0-host0-target0:0:0-0:0:0:0-block-sda-sda1.device loaded active plugged 106X EFI\x20System\x20Partition sys-devices-platform-soc-5311000.usb-usb2-2\x2d1-2\x2d1:1.0-host0-target0:0:0-0:0:0:0-block-sda-sda2.device loaded active plugged 106X 2 sys-devices-platform-soc-5311000.usb-usb2-2\x2d1-2\x2d1:1.0-host0-target0:0:0-0:0:0:0-block-sda-sda3.device loaded active plugged 106X 3 sys-devices-platform-soc-5311000.usb-usb2-2\x2d1-2\x2d1:1.0-host0-target0:0:0-0:0:0:0-block-sda-sda4.device loaded active plugged 106X 4 sys-devices-platform-soc-5311000.usb-usb2-2\x2d1-2\x2d1:1.0-host0-target0:0:0-0:0:0:0-block-sda.device loaded active plugged 106X mnt-sda.mount loaded active mounted /mnt/sda dev-sda2.swap loaded active active /dev/sda2 aik@hass:~$ systemctl | grep tmp ● tmp.mount masked active mounted tmp.mount Now there are 2 problems with this: 1. the root is mounted as readonly right after booting. There are no reported errors of any kind, just readonly. Remounting `/` with `rw` fixes it and it stays so for days. 2. /tmp from the above is never mounted at the boot time, have to `mount /tmp` manually but the other two mountpoints do mount. So there must be some leftover from my removal of tmpfs's /tmp, what is it? I am lacking lots of systemd knowledge, it is soooo arrogant 😞 Also, /boot/armbianEnv.txt has `usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u` which is added to the cmdline above, what is this about? The `sda` from `fstab` is `2537:1066 Norelsys NS1066`. Thanks,

I have several OpiOne Plus boards. They differ by the date of manufacture (let's say 1st batch and 2nd batch) 1st batch: Works with kernel 5.10.x but does not boot kernel 5.15.x. Red light is on, power meter shows very little consumption, ethernet does not go up. Switching to last available 5.10.x kernel resolves the situation. 2nd batch: Successfully work with both 5.10.x and work with 5.15.x. Green light is on, power meter shows adequate consumption, board works. I'm pretty sure, that no more "new" opi one plus will appear at Xunlong shop and this issue won't be fixed in visible future. But well.. How I can "freeze" kernel update and I guess, uboot update also ? Just to prevent accidental updating of boards from "1st batch" ? Thanks in advance for the answer.

Download section for Orange PI One Plus ( https://www.armbian.com/orange-pi-one-plus/ ) appears to be malformed / cut-off somehow at second image (Jammy XFCE) where content ends after "h" from "SHA hash ..." line. I checked out download sections for few other boards of interest to me and they all appear to be fine 🤔

Hello, I have a Orange Pi One Plus. It has an onboard mic. No matter what i do i cannot record sound from it. Please help, how can i record sound from onboard microphone? marko@orangepioneplus:~$ cat /etc/armbian-release # PLEASE DO NOT EDIT THIS FILE BOARD=orangepioneplus BOARD_NAME="Orange Pi One+" BOARDFAMILY=sun50iw6 BUILD_REPOSITORY_URL=https://github.com/armbian/build BUILD_REPOSITORY_COMMIT=d485420c00 VERSION=22.08.1 LINUXFAMILY=sunxi64 ARCH=arm64 IMAGE_TYPE=stable BOARD_TYPE=conf INITRD_ARCH=arm64 KERNEL_IMAGE_TYPE=stable marko@orangepioneplus:~$ uname -a Linux orangepioneplus 5.15.63-sunxi64 #22.08.1 SMP Tue Aug 30 07:11:56 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux marko@orangepioneplus:~$ arecord -l **** List of CAPTURE Hardware Devices **** marko@orangepioneplus:~$

Hello, I'm sort of an "educated noob" on Linux, meaning I understand about 1/2 of the postings in forums like this one. And I seem to have a problem. I am using Armbian Buster on an Orange Pi One Plus. After the most recent (to me) batch of updates, the machine will no longer boot. The error is: "Gave up waiting for root file system device." This occurs after numerous instances of "Running /scripts/local-block", (which does not seem to exist), and is followed by "ALERT! UUID=[valid UUID] does not exist. Dropping to a shell!" The "shell" it pro-ports to drop into is mythical, I assume because no keyboard driver has even been established. The computer is completely unresponsive. He's dead, Jim. The only thing I can do is recover from backup, which dates back almost a year (I know, I know,...), so any re-application of updates now involves a basket of 150 packages. (I do not remember how recent the "killer" update may have been.) I have recovered multiple times, trying this-and-that from old postings on the Net. The lack of any more recent similar postings makes me think this problem is unique to me, but I don't know why. There are no RAIDs involved. I do not use encryption. The UUIDs match across /boot/armbianEnv.txt, /etc/fstab, and the error message. I have multiple instances of the Orange Pi hardware; they all exhibit the same problem. Multiple uSD cards; same problem still. And at least two different machine identities share this grief. I simply cannot apply any updates since my backups were taken, without killing things. What I CAN do is apply the updates, avoid restarting, and then make some kind of repair, if only I knew what that repair was! The system runs fine until it's asked to shut down and restart. Any guidance regarding where and how to look for a solution would be appreciated.

Hi, I am unable to build any images for orangepi SOCs specifically orangepilite, orangepilite2 and one plus. Always returned error halfeway. Following is a sample of log when I compile image for orange pi lite. Please me some guidance on how to resolve this. My steps: run sudo compile.sh -- "Do no tchnage the kernel..." --> "orangepilite"--> either current or legacy --> either "buster" -->"Image with console inter..." -->"Standard image with ..."compilation.log