I have tried every distro and the only ones that boot for me are the debian light and the respery pi base but with both of them i have problems while trying to install mysql or try the comand apt update do you know some solution? Initially i wanted to install ubuntu server i tried waiting as said in the release notes but doesnt let me login
Either you have a bad power supply or bad MicroSD card.
distro server links arenāt working? redirects to mcafee page
Thatās an issue with your computer/ISP.
Is there an easy way to upgrade from debian 11 to debian 12?
You can follow standard Debian upgrade instructions.
I try to configure WiFi on Base image using IWD instructions, but for some reason wlan interface does not get IPv4 address, only IPv6. Any idea of what is wrong?
IWD only configures the WiFi connection. It does not handle DHCP requests by default. If you are only getting IPv6, it is likely that your DHCP client is misconfigured or your DHCP server is misconfigured.
I think the naming convention and iso downloads are missing the new AML-A311D-CC (https://libre.computer/products/aml-a311d-cc/) Alta board?
Alta and all of our UEFI boards use +arm64 per the OP.
There is no longer a need for board specific images for all boards designed after 2017.
Iām using your instructions to configure systemd-networkd (add the 10-wlx-dhcp.network file), I expect the DHCP client to be configured correctly. Or do I need to do something else?
Raspberry pi image on same LePotato board gets IPv4 address in same Wi-Fi network, so it has nothing to do with DHCP server configuration.
It depends on whether you are using Debian 11 or Debian 12. Thereās multiple ways to configure network depending on your network manager. If you are using systemd-networkd, that should handle IP address and offload DNS to either systemd-resolved or resolvconf.
Need more information such as:
- Are you getting an IP on the interface?
- What is DNS (/etc/resolv.conf) symlinked to or is it an actual file?
As I described, Iām using IWD method from your instructions, see my post from Jun 9. The interface is getting IPv6 address, but not IPv4, and the DNS seems to be not working.
Iām using Debian 12 Base image.
I spent 2 evenings investigating the issue and managed to workaround the problem. The culprit was exactly the IWD, for some reason it renames the interface from wlxXXXXXX
to wlanX
which causes all the problems.
After some searching I found this: [SOLVED] IWD error changing net interface name device or resource busy / Applications & Desktop Environments / Arch Linux Forums
Applying this workaround fixed the thing for me when system is on MicroSD card. But when I installed the system to eMMC, the WiFi was still not working. Looks like there is some racing condition happening.
Then I investigated a bit more and found that iwctl device list
does not see the device. Then I found this: [SOLVED] IWD doesn't recognize wireless interface after boot / Networking, Server, and Protection / Arch Linux Forums
Applying this workaround as well solved the problem when running from eMMC card as well.
So, my Wi-Fi instructions are as follows:
- Download Debian 12 Base image and flash it to eMMC/SD card.
- create
/etc/systemd/network/10-wlx-dhcp.network
file with contents:
[Match]
Name=wlx*
[Network]
DHCP=yes
IgnoreCarrierLoss=3s
- create
/etc/systemd/system/iwd.service.d/override.conf
file (and directory path) with contents:
[Unit]
Before=network.target
Wants=network.target
[Service]
ExecStartPre=/usr/bin/sleep 5
ExecStart=
ExecStart=/usr/libexec/iwd --nointerfaces "wlan[0-9]"
- enable and start
iwd
service:
systemctl enable iwd
systemctl start iwd
- reboot just in case
- connect to wifi using
iwctl
:
# check the iterface name
iwctl device list
iwctl station INTERFACE_NAME scan
iwctl station INTERFACE_NAME get-networks
iwctl station INTERFACE_NAME connect SSID
Actually, this workaround works for me on LePotato and LaFrite, but still does not work on Alta.
On Alta I need to manually restart the iwd
service in order to see the interface in the iwctl device list
. I canāt make it work right after boot without any manual interaction.
We just tested the instructions as is and it works fine. There should be no workaround needed. You can check networkd with networkctl status
to see the status of networkd DHCP. Make sure you saved the file to the right place.
All boards use the same image with a different bootloader pre-flashed into the image. If it doesnāt work on one, it wonāt work on any other.