Jump to content


  • Posts

  • Joined

  • Last visited

Recent Profile Visitors

2909 profile views
  1. `{ managed, AP}` indicates these are mutually exclusive. You cannot simultaneously have managed (aka STA) mode and AP mode operating at the same time. `total <= 3` means you can have at most (managed OR AP) AND (P2P-client or P2P-GO) AND (P2P-device).
  2. The build instructions `README` suggest it's possible to build an image using Github actions. So, I created a new repository and created the following file under `.github/workflows/orangepizero3_build.yml` name: Build Orange Pi Zero 3 server image on: workflow_dispatch: jobs: build-armbian: runs-on: ubuntu-latest steps: - uses: armbian/build@main with: armbian_token: "${{ secrets.GITHUB_TOKEN }}" # GitHub token armbian_release: "bookworm" # userspace armbian_target: "build" # build=image, kernel=kernel armbian_board: "orangepizero3" # build target armbian_ui: "server" But when I tried to run this action, I received this error: Error: Could not find file '/home/runner/work/_actions/_temp_52217267-7314-4a20-996d-95b7097793e8/_staging/armbian-build-de030c7/patch/kernel/rockchip-rk3588-collabora/dt/rk3588-nanopc-cm3588-nas.dts'. Am I doing something wrong? Is there some aspect to building an image using Github Actions I'm missing?
  3. What exactly have you tried so far? How are you determining it's not working? What kind of SD card are you using, and how are you installing Armbian on it? What are you using for a power supply and USB cable for power? What's the behavior of the status LEDs? Are you using a keyboard and monitor, or are you connecting to the board via SSH? Have you tried attaching a serial cable to it and reading the output over a serial terminal?
  4. The "create access point" utility in `armbian-config` has several bugs that prevent it from working, due to changes in the default installation since it was written: - hostapd does not install a default configuration file at `/etc/hostapd.conf` - hostapd is installed masked by default - dnsmasq fails to start because systemd-resolvd launches first as the default DNS resolver I can write patches to fix this utility, but I'm wondering if it will ultimately be worth it. I noticed this access point utility doesn't exist in the `armbian-configng` repository. Is that because Armbian is dropping this utility, or no one has gotten around to it yet? (There's not even a placeholder for it.) What's the status of `armbian-configng` anyhow? Will it eventually replace `armbian-config`?
  5. I don't think the Orange Pi Zero 3 supports w1-gpio. The only 1-wire overlay that I know of is for H5-equipped boards.
  6. Yes, that appears to be correct. I couldn't figure out why the UART on the p26 pin header wasn't working. Found your post and tried ttyS1 instead. Working beautifully now. Thanks 🙂.
  7. It looks that way to me. It has 'orangepi-config' and 'orangepimonitor' commands that look and behave exactly like the Armbian equivalents. I'd feel a little more comfortable downloading the images from Armbian's torrents, though, than a server in China....
  8. I installed Orange Pi's version of Ubuntu Bionic server with kernel 5.34.27 mentioned in the tweet refered to by @gounthar above on a Orange Pi Zero LTS V1.5 board, and it has indeed fixed the temperature reporting problem. The onboard wifi is working flawlessly, too.
  9. I haven't tried setting up AP mode using the unmodified driver, but I was able to get a hotspot set up on Orange Pi PC Plus and Orange Pi Plus 2E by enabling concurrent mode in the wifi driver and recompiling it. This will give you two wifi interfaces, one of which can be used as an AP. The advantage of doing this is it allows you to use the board as a wifi repeater if you want, or to make it easier to set it up as an IoT device. However, it also cuts the transmission rate in half, since the wifi module is concurrently switching between STA and AP modes. Let me know if you're interested and I'll write up how I did it.
  10. Bluetooth works for me, but only if I completely power off and do a cold boot. It doesn't work on a warm restart. Note that firmware updates currently will overwrite these changes, so be careful when doing an apt-get update && apt-get upgrade.
  11. This got wifi working for me (but broke bluetooth ): $ cd /lib/firmware/brcm $ sudo mv brcmfmac4356-sdio.bin brcmfmac4356-sdio.bin.old $ sudo mv brcmfmac4356-sdio.txt brcmfmac4356-sdio.txt.old copy drivers from this post to ~/Downloads: $ sudo cp ~/Downloads/brcmfmac4356-sdio.* . $ sudo chmod g+w brcmfmac4356-sdio.bin $ sudo chmod g+w brcmfmac4356-sdio.txt then reboot
  12. Thanks for your help. 1. I would be happy to submit a patch, but I'm not sure you want it--concurrent mode cuts wifi transfer speed in half, because the radio is continually switching between two modes. Would that be acceptable to the project? 2. Thanks for the tip. I'll look into dkms. 3. Not my prefered choice, but that's always a fallback...
  13. I apologize for asking such a basic question. I have recompiled the wifi module on an Orange Pi PC+ to operate in concurrent mode so it can act in both station and AP mode at the same time, allowing it to be a wifi repeater. The problem is, this feature is lost on every kernel upgrade, requiring me to recompile the module each time I upgrade the kernel. The kernel module driver often changes slightly between kernel versions, and I have to track down and fix new bugs in the source code that prevent it from compiling when concurrent mode is enabled. I'm happy with how the wifi module performs now, but don't want to lose the ability to get needed kernel updates in the future. Is there any way I can keep the wifi module I have now without losing the ability to upgrade the rest of the kernel?
  14. Thanks for the advice. I just updated the kernel, and am in the process of installing the new (dev) source and header files. I also did an `apt update`, and see that now the linux image for the "next" branch is back to 4.19.57! $ apt-cache search linux-image | grep next-sunxi linux-image-next-sunxi - Linux kernel, version 4.19.57-sunxi So the problem has apparently been fixed. :-)
  15. I'm trying to add concurrent mode to the wifi driver on an Orange Pi PC Plus running the latest stable distribution of Armbian, but running into an "invalid module format" error due to the kernel version not matching the source version I'm using to recompile the wifi driver. I installed both the source and header files from armbian-config. The kernel version is 4.19.59 according to uname -r. This apparently is the linux-image-next-sunxi image, according to `apt-cache search linux-image | grep 4.19.59`. However, the source for the next-sunxi branch in the repository is 4.19.57, not 4.19.59, as `apt-cache search linux-source | grep next-sunxi` gives: linux-source-4.19.57-next-sunxi - This package provides the source code for the Linux kernel 4.19.57 `apt-cache search linux-source | grep 4.19.59` returns no results. How do I get the 4.19.59 source version? Would it be safe to upgrade to the dev branch (v 5.1.0), since both the kernel and source there are the same version? FWIW, here's my sources.list: deb http://httpredir.debian.org/debian buster main contrib non-free #deb-src http://httpredir.debian.org/debian buster main contrib non-free deb http://httpredir.debian.org/debian buster-updates main contrib non-free #deb-src http://httpredir.debian.org/debian buster-updates main contrib non-free deb http://httpredir.debian.org/debian buster-backports main contrib non-free #deb-src http://httpredir.debian.org/debian buster-backports main contrib non-free deb http://security.debian.org/ buster/updates main contrib non-free #deb-src http://security.debian.org/ buster/updates main contrib non-free
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines