El 22/1/26 a las 15:02, Frank Wille escribió:
mlelstv%serpens.de@localhost (Michael van Elst) wrote:
create a symlink "brcmfmac43455-sdio.Raspberry Pi 4 Model B.txt" to that file so that it is found also with the different name.
This is still necessary? I got the same autoconfiguration error after installing the 10.1 release image together with UEFI.
Yes, the UEFI code chose a different system name than RPI firmware and FDT.
Ah, I see! But are there more than these two possibilities (UEFI or FDT)? Then how about adding the link to /libdata/firmware/if_bwfm/ for the installation files, to keep people from head-scratching? :)
Hi FrankThat link would be very helpful. Without it, many people may abandon NetBSD on this popular hardware platform at the first difficulty they encounter. We need to attract new users to NetBSD, and the Raspberry Pi would be an excellent place to start. The information at https://wiki.netbsd.org/ports/evbarm/raspberry_pi/ is better than was before, but I think it is still not completely clear.(it is clear when you know what to do and have installed and upgraded it once, but for the new user it may be frustrating).
> No idea what hard resets the system. Is this a 8GB Pi 4? Or the > necessary > question for Pi crashes: is the power supply sufficient and stable? Wow... yes, this was the reason! Probably Wireless draws so much power that using it during multiuser startup resets the system. Thanks! Works now - using the official 15.3W RPi power supply.
Nice to see it is working fine with the official PS. I am also using it. Regards.