Hi,
I haven’t used DietPi before, but I was looking for a device for my next project and the OrangePi Zero 3 fits the bill nicely. I then came across DietPi and saw it listed this board as one that they have a downloadable OS for.
If it is a listed board, does that mean it is expected to be working quite well or should I expect some things to not work?
I was wondering if Wi-Fi (and hotspot), Eth, serial pins (not serial debug), HDMI and Bluetooth works?
Thanks!
simply give it a try if you have the board
Unfortunately I don’t I was trying to make my mind up on what board to buy, but wanted to avoid buying one that didn’t have an OS that worked or all features didn’t work.
Although I just pulled the trigger on it yesterday, so just waiting on postage now! Hopefully I can get an OS that fits my needs!
My OrangePi Zero 3 runs nice as an ADSB receiver.
I have used HDMI, Ethernet and WiFi on the HW side and Docker, Docker Portainer, ADSB (Docker version) on the SW side.
So, WiFi and HotSpot should work without problems.
Maybe some other used your inquired serial pins, Bluetooth and can answer.
Thanks for the answer! This makes me more confident in my purchase!
go to see if armbian supports it. dietpi is not relevant.
What you mean isn’t relevant?
I think its community support on armbian
Dietpi copy image from armbian. That’s what i mean.
Since you ignored my last warning, to stop spreading lies like “Dietpi copy image from armbian”, I did now permanently silence you, hence you cannot post anymore on our forum. I hope this frees some time for you to work on Armbian instead of wasting your time with nonsense here.
Have you already received it? I can say that eth, WiFi (and hotspot), HDMI and bluetooth works, but haven’t tried serial pins.
In my personal experience both armbian and dietpi are quite good when they support any SBC. You gotta be pretty dumb if you think that one project is just copying the other. Have tried both and you can feel the difference.
armbian used to work pretty well for this board, but since it got automated builds some things broke and the former images are not available. For example, with 2nd october minimal image, WiFi hotspot (hostapd) didn’t work at all. The AP was created but wasn’t able to connect with any device.
However, with dietpi there’s also some problems with the WiFi driver.
You get dmesg continously spammed with “protocol 0000 is buggy, dev wlan0”, if you google it you’ll find is something old and I think solved, but I guess hasn’t been patchedf here. Still haven’t sufferend any functional problem. Also at the bootup you get this error in dmesg
[ 6.230423] wifi ini path = /lib/firmware/wifi_2355b001_1ant.ini
[ 6.257347] sprdwl:sprdwl_get_fw_info length mismatch: len_count=83, r_len=89
[ 6.257377] sprdwl:sprdwl_get_fw_info, drv_version=1, fw_version=2, compat_ver=0
[ 6.257388] sprdwl:chip_model:0x2355, chip_ver:0x0
[ 6.257395] sprdwl:fw_ver:0, fw_std:0x7f, fw_capa:0x120f7f
[ 6.257404] sprdwl:mac_addr:e0:51:d8:67:9d:38
[ 6.257412] sprdwl:credit_capa:TX_WITH_CREDIT
[ 6.257419] sprdwl:ott support:0
And I think there’s no GPU support at all as long as Kodi is not able to play smoothly a 1080p video. But it’s the case in every linux distro for this sbc (only Android distro officially supports it and if you google about it you’ll find is pretty sketchy).
Good luck with the board!
Hi @pepkov,
Do you mind me asking how you setup a hotspot? I have spent weeks trying to get it to work with Armbian and also DietPi and if the accesspoint has a password it doesn’t work. If it doesn’t have a password it does work.
nmcli connection add type wifi ifname wlan0 con-name access_point autoconnect yes ssid TEST_AP
nmcli connection modify access_point 802-11-wireless.mode ap 802-11-wireless.band bg ipv4.method shared
nmcli connection modify access_point connection.mdns 2
nmcli connection modify access_point wifi-sec.key-mgmt wpa-psk
nmcli connection modify access_point wifi-sec.psk "password"
nmcli connection up access_point
This is how I’m setting it up. These exact commands work on an OrangePi Zero LTS running Armbian.
Didn’t use nmcli.
In dietpi-confiig you have an option for WiFi to work as a hotspot with no more configuration.
They provide this video as a how-to in their documentation, it’s in german but I guess you don’t need to understand it to see how to navigate on the menus
Who is they?
@av4625 did you tried using dietpi-software to install hotspot?
You can find it in the dietpi documentation
Ok i got confused because this
Oh my fault, wanted to write dietpi hahah editing it, sorry
@pepkov Got it working that you very much!
You don’t happen to know the DietPi equivalent to enabling mDNS?
On my Zero LTS running Armbian I did this:
sudo sed -i "s/#MulticastDNS=no/MulticastDNS=yes/g" /etc/systemd/resolved.conf
But DietPi doesn’t seem to use systemd-resolved.
This would allow you to then ssh to hostname.local if connected to the hotspot for example.
Yes, it is not installed on a default setup. However, if you wish you are free to install if needed.
Another option would be using Avahi-Daemon
ID 152 | Avahi-Daemon: Hostname broadcast via mDNS (Zeroconf, Bonjour)
I setup the hotspot for connecting a Chromecast there, blocking any traffic to/from Google DNS and solving only the petitions from WiFi DNS with Pihole, so no ads on Chromecast. (On some apps)
I told you this because I’m almost sure I’m using mDNS because otherwise I couldn’t cast from the normal network to the one Chromecast is connected.
I think it’s working with avahi Daemon. If you don’t get it to work I can check again how to solve it.
If your setup is similar to mine, remember to setup a routing rule in your router to send packages in the hotspot range to the interface your pi zero is connected