Debian image available?

Quad / mCore-H616
21

Easy!
Create a file anywhere an executable can run such as /usr/bin/connect_network

sudo nano /usr/bin/connect_network
# or
sudo vi /usr/bin/connect_network

in the file:

#!/bin/bash
sleep 20
nmcli dev wifi connect NETWORK_NAME password NETWORK_PASSWORD

then configure cron to run it at boot with:
crontab -e and adding the following line at the end of the file:

@reboot sh /usr/bin/connect_network

Note: this will also add the command connect_network anywhere in your system, so make sure not to overwrite another command

1 Like
23

For anyone looking for a Debian minimal install for the MQ-Quad, I’ve created an image containing the following changes from the stock image:

✓ Debian 12
✓ APT Sources Reconfigured to Stock
✓ Updated All Packages
✓ Removed All Desktop Apps
✓ Removed Library Bloat
✓ Removed OrangePi Apps
✓ Image Size 1GB when installed to disk
✓ Default username reflects MangoPi instead of OrangePi
✓ Everything you would expect from a standard "Debian Minimal Install"
Default Login Info 
Username:      pi
Password:      frontesque
Root Password: frontesque
Hostname:      mango
Download Link

https://emerald.frontesque.me/ui/mangopi-quad-minimal.html

PLEASE NOTE: This image DOES NOT automatically resize itself. You may need to resize it manually if you wish to fill your entire SD card with usable storage unless your image flasher does this automatically.
(This is the same as the stock, mangopi-provided image)

24

Thanks, I’ve uploaded it and will give it a try. Thanks for putting in the work. In the interest of making these boards more supportable in perpetuity, I’d still like to build a base image from scratch.

Happy New Year!
Tony

25

I had a look at this, and it is very similar to the upgrade I performed on what is apparently the only available bootable image. It is still running a bullseye kernel:

bracka@MangoPi:~$ hostnamectl
Static hostname: MangoPi
Icon name: computer
Machine ID: 72220208b82d41a89e94c2e17deeba01
Boot ID: 144b3305e0be4adbabec81e2008ff454
Operating System: Debian GNU/Linux 12 (bookworm)
Kernel: Linux 5.16.17-sun50iw9
Architecture: arm64

I just installed full bookworm on an Orange Pi and this is what we should be reporting:

bracka@chinook:~$ hostnamectl
Static hostname: chinook
Icon name: computer
Machine ID: e1af5f93623b43d58c0567fea31978a8
Boot ID: e16a05ae186b47a493531cbcbf29c951
Operating System: Debian GNU/Linux 12 (bookworm)
Kernel: Linux 6.1.31-sun50iw9
Architecture: arm64

The product page has a source repository that I have also uploaded, so at least we are covered from that point of view. The last time I tried it, the OrangePi image would not boot, complaining about the memory controller. I may try a full build, but it looks pretty complex given that we aren’t privy to any source control.

Incidentally, mode of failure using a straight Orange Pi bookworm image. It looks like the boot loader is the first thing that’s messed up.

U-Boot SPL 2021.07-orangepi (Sep 07 2023 - 17:38:50 +0800)
DRAM:This DRAM setup is currently not supported.

resetting …

This is the one from the MangoPi supplied image that works:

U-Boot SPL 2021.10-orangepi (Oct 05 2022 - 14:25:44 +0800)
pmic id is 0x4b
DRAM: 1024 MiB
Trying to boot from MMC1
NOTICE: BL31: v2.7(debug):ea7aee20
NOTICE: BL31: Built : 04:47:26, Oct 3 2022
NOTICE: BL31: Detected Allwinner H616 SoC (1823)
NOTICE: BL31: Found U-Boot DTB at 0x4a082610, model: OrangePi Zero2
INFO: ARM GICv2 driver initialized
INFO: Configuring SPC Controller
INFO: PMIC: Probing AXP305 on RSB
ERROR: RSB: set run-time address: 0x10003
INFO: Could not init RSB: -65539
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
INFO: PSCI: Suspend is unavailable
INFO: BL31: Preparing for EL3 exit to normal world
INFO: Entry point address = 0x4a000000
INFO: SPSR = 0x3c9
INFO: Changed devicetree.

I am going to see if I can figure out how to move this over. I will be starting a new thread to follow the conversion to a bootable bookworm image. Setting up a build is non-trivial as it wants a very specific build machine.

Regards,
Tony