Re: RPi 4b Wifi Device
tomd...@wavecable.com ("Thomas D. Dean") writes:
>How do I setup wpa_supplicant?
That depends on what you want to do.
Here are some examples:
https://wiki.netbsd.org/tutorials/how_to_use_wpa_supplicant/
Greetings,
Re: RPi 4b Wifi Device
On 4/19/24 09:40, Michael van Elst wrote: Reason is that the platform is canonically named "raspberrypi,4-model-b" but UEFI chose "Raspberry Pi 4 Model B" instead. > pwd /home/tomdean/NetBSD > ls -l total 2154 -rw-rw-r-- 1 tomdean tomdean 272510976 Apr 18 09:40 NetBSD-10.0-evbarm-aarch64.iso drwxrwxr-x 4 tomdean tomdean 4096 Apr 18 21:12 RPi4-1.35 drwxrwxr-x 7 tomdean tomdean 4096 Apr 10 23:27 RPi4-1.37 -rw-rw-r-- 1 tomdean tomdean 433670 Apr 18 16:52 RPi4-1.37.zip -rw-rw-r-- 1 tomdean tomdean3144359 Apr 18 21:01 RPi4_UEFI_Firmware_v1.35.zip -rw-rw-r-- 1 tomdean tomdean 1582301184 Apr 3 15:02 arm64.img -rw-rw-r-- 1 tomdean tomdean 399419622 Apr 18 09:50 arm64.img.gz > grep -Rail "raspberrypi\\,4\-model-b" * RPi4-1.35/bcm2711-rpi-4-b.dtb arm64.img > grep -Rail "Raspberry\ Pi\ 4\ Model\ B" * < nothing found> I could not get NetBSD 10 to boot with the 1.37 files. With the 1.35 files, it booted and seems to work, other than WIFI. I created a link to "Raspberry Pi 4 Model B" and the error went away. How do I setup wpa_supplicant? Tom Dean
Re: RPi 4b Wifi Device
tomd...@wavecable.com ("Thomas D. Dean") writes:
>On 4/18/24 22:00, Michael van Elst wrote:
>> bwfm0: Firmware file default:brcmfmac43455-sdio.bin
>> bwfm0: Firmware file model-spec: brcmfmac43455-sdio.raspberrypi,4-model-b.bin
>> bwfm0: Found Firmware file: brcmfmac43455-sdio.raspberrypi,4-model-b.bin
>> bwfm0: NVRAM file default:brcmfmac43455-sdio.txt
>> bwfm0: NVRAM file model-spec: brcmfmac43455-sdio.raspberrypi,4-model-b.txt
>> bwfm0: Found NVRAM file: brcmfmac43455-sdio.raspberrypi,4-model-b.txt
>> bwfm0: CLM file default:brcmfmac43455-sdio.clm_blob
>> bwfm0: CLM file model-spec: brcmfmac43455-sdio.raspberrypi,4-model-b.clm_blob
>> bwfm0: Found CLM file: brcmfmac43455-sdio.raspberrypi,4-model-b.clm_blob
>I saw bwfm0: in /var/log/messages, from memory, similar to the ones listed.
>One error. autoconfiguration error: NVRAM file not available.
>The CHIPACTIVE line is missng.
This means, a firmware file isn't found, because it is searched under
a different name.
You should have:
-r--r--r-- 1 root wheel 1863 Mar 28 17:45
libdata/firmware/if_bwfm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt
and need to create a symlink like:
cd /libdata/firmware/if_bwfm
ln -s brcmfmac43455-sdio.raspberrypi,4-model-b.txt
"brcmfmac43455-sdio.Raspberry Pi 4 Model B.txt"
Reason is that the platform is canonically named "raspberrypi,4-model-b"
but UEFI chose "Raspberry Pi 4 Model B" instead.
Greetings,
Re: RPi 4b Wifi Device
On 4/18/24 22:00, Michael van Elst wrote:
tomd...@wavecable.com ("Thomas D. Dean") writes:
What is the wifi device in the RPi 4b? Driver?
It's a chip similar to the one in the older RPIs:
bwfm0: chip 0x4345 rev 6
bwfm0: Firmware file default:brcmfmac43455-sdio.bin
bwfm0: Firmware file model-spec: brcmfmac43455-sdio.raspberrypi,4-model-b.bin
bwfm0: Found Firmware file: brcmfmac43455-sdio.raspberrypi,4-model-b.bin
bwfm0: NVRAM file default:brcmfmac43455-sdio.txt
bwfm0: NVRAM file model-spec: brcmfmac43455-sdio.raspberrypi,4-model-b.txt
bwfm0: Found NVRAM file: brcmfmac43455-sdio.raspberrypi,4-model-b.txt
bwfm0: CLM file default:brcmfmac43455-sdio.clm_blob
bwfm0: CLM file model-spec: brcmfmac43455-sdio.raspberrypi,4-model-b.clm_blob
bwfm0: Found CLM file: brcmfmac43455-sdio.raspberrypi,4-model-b.clm_blob
bwfm0: CHIPACTIVE
bwfm0: flags=0x8843 mtu 1500
ssid nwkey *
powersave off
bssid ##:##:##:##:##:## chan 100
address: ##:##:##:##:##:##
media: IEEE802.11 autoselect (VHT mode 11ac)
status: active
inet6 fe80:::::%bwfm0/64 flags 0 scopeid 0x3
I saw bwfm0: in /var/log/messages, from memory, similar to the ones listed.
One error. autoconfiguration error: NVRAM file not available.
The CHIPACTIVE line is missng.
ifconfig does not show bwfm0, only genet0 and lo0.
I managed to get a wired connection (across the room at chin height...)
Networking is up. ntp set the date correctly. DNS works. I can ssh into
the system.
It has been 5 or 6 years since I ran BSD. I used Berkeley BSD and FreeBSD.
How do I get wifi started? I can start wpa_supplicant and I have a
network block in /etc/wpa_supplicant.
network={
ssid=""
psk=""
}
service wpa_supplicant onestatus shows it is running
Tom Dean
Re: Please forgive a blatant plug: I reviewed v10 for the Reg
On Fri, 19 Apr 2024 at 10:01, Riccardo Mottola wrote: > > Hi Liam. Ciao! > Nice share and thanks for taking the time to write it. Oh, thank you! I really wish there were more technology sharing between the BSDs. In the last ~2 years, I have tried Net, Open, Free, Dragonfly, Ghost, Midnight, Nomad, the Hello System, plus XigmaNAS and TrueNAS Core. (I have also installed and written about 9Front, Redox OS, Serenity OS, Genode, Arca OS, FreeDOS, RISC OS Open, RISC OS Direct, and others.) I really am trying to cover as many bases as I can here. Dragonfly has the best installer, IMHO, but of course it has many fewer options to cover. FreeBSD is the worst inasmuch as it does the least complete job. Some OpenBSD folks are angry with me because I criticise its disk partitioner. When I tell them the config I work with and they recoil and go "OMG that is _impossible!_" One of the better Linux installers is Calamares, which does not depend upon any distribution: it's an independent project. Pop OS and Elementary OS share an installer. Multiple Ubuntu remixes share variants of Ubiquity and Subiquity. Some variants of this can run in both GUI and text-driven modes. The point being: cross-platform installers that work on multiple very different distros with different packaging tools are 100% a thing. I am sure it would be possible to write a program which, when run, tests the console or terminal to determine if it can use colour and cursor controls, and if it can, which presents a cursor-key-driven-menu based UI with CUA-style controls -- but if the terminal does not, then falls back gracefully to simple numeric or letter-choice menus. Binary compatibility is not really an issue because this is an ideal kind of application of a scripting language. It would be to the advantage of all the BSDs if they worked together on this, pick the best of each OS's installer, and combined them into one. Long-term users often tell me that they do not notice the issues because they simply upgrade from one version to the next and never see the installer. Well, in that case, offer that opportunity to visitors as well: it would be to the benefit of all of the BSD family if the projects supplied pre-installed and pre-configured VM images for direct download, so that the curious could simply download an OVA file, import it into the hypervisor of their choice, and try the OS out without installing it at all. Several Linux distros do this, especially the enterprise ones which do not expect to run on bare metal. -- Liam Proven ~ Profile: https://about.me/liamproven Email: lpro...@cix.co.uk ~ gMail/gTalk/FB: lpro...@gmail.com Twitter/LinkedIn: lproven ~ Skype: liamproven IoM: (+44) 7624 277612: UK: (+44) 7939-087884 Czech [+ WhatsApp/Telegram/Signal]: (+420) 702-829-053
Re: Please forgive a blatant plug: I reviewed v10 for the Reg
Hi Liam. Liam Proven wrote: I thought this might interest folks here... Nice share and thanks for taking the time to write it. NetBSD 10 proves old tech can still kick apps and take names three decades later Proper old-school Unix, not like those lazy, decadent Linux types https://www.theregister.com/2024/04/17/30yo_netbsd_releases_v10/ Comments and feedback welcomed! I mostly agree with the article, the citations, it gives the mood back. Then it shares some personal opinions about experience. Some considerations: * About "size" and "performance". NetBSD runs well on a lot of software, in my experience the core OS is very comparable to OpenBSD, but a litte bit easier since it doesn't have the relink stuff, and base Linux. However recent linux with systemd are definitely worse. However still there is "imported userland" and then "pkgsrc". Except for raw speed in system calls, kernel management, if you install package X it will about be similar in size on different operating systems. So for sure since XFCE has gotten fatty, you get the same fat on NetBSD. Same goes for GCC which gets fatter and slower with each release :) Of course, new features are added. You start to see the size of packages installed more than the OS itself * installation experience. I like the menu-driven installer, it has the classic semi-GUI with windows and arrows, but still very usable on a serial console (handy if you install on a server!). The rough edges in my opinion are in the partitioning. I am myself bitten right now by an upgrade on a "standard x86-64 laptop". Resizing partitions, selecting, labels... that part. Of course it is complicated by all the many differences in BIOS, UEFI... OpenFirmware on mac, etc etc However, when things go smooth, e.g. on a classic BIOS-based PC where you take over the whole disk, it is very fine and convenient. Riccardo
Re: Broken Link
On Thu, Apr 18, 2024 at 09:46:30AM -0700, Thomas D. Dean wrote: > On https://wiki.netbsd.org/ports/evbarm/ > Select NetBSD/evbarm 10.0 INSTALL notes > Produces Error 404. Fixed, thanks! Martin
