Re: RPi 4b Wifi Device
Hello Thomas, I do not know what happens and if this has something to do or not. I have seen this advice in pftf/RPi4 in GitHub: Note: Booting from USB or from ESP requires a recent-enough version of the Pi EEPROM (as well as a recent version of the UEFI firmware). If you are using the latest UEFI firmware and find that booting from USB or from ESP doesn't work, please visit https://github.com/raspberrypi/rpi-eeprom/releases to update your EEPROM. My RPi4 arrived yesterday and everything worked and booted from the SD using UEFI. Regards. Ramiro. El 23 de abril de 2024 22:12:47 CEST, "Thomas D. Dean" escribió: >On 4/23/24 08:54, Justin Parrott wrote: >> this is what i was talking about, i don't like booting an sbc from stick >> >> even if you can hit disk >> >> can net run on sbc? >> > >I can boot NetBSD 10 on an RPi 4b from an SD card . It seems to run fine. >Seems lots faster than RPi OS booted from the same type SD card. > >I can > 1. access the network > 2. ssh into the RPi > 3. build applications >on a RPi 4B running NetBSD 10 booted from an SD card. > >What I can not do is get the RPi 4b to boot NetBSD from a USB-3 flash drive. > >I can get the RPi 4b to boot RPi OS from the USB-3 flask drive. > >Tom Dean
Re: RPi 4b Wifi Device
On 4/23/24 08:54, Justin Parrott wrote: this is what i was talking about, i don't like booting an sbc from stick even if you can hit disk can net run on sbc? I can boot NetBSD 10 on an RPi 4b from an SD card . It seems to run fine. Seems lots faster than RPi OS booted from the same type SD card. I can 1. access the network 2. ssh into the RPi 3. build applications on a RPi 4B running NetBSD 10 booted from an SD card. What I can not do is get the RPi 4b to boot NetBSD from a USB-3 flash drive. I can get the RPi 4b to boot RPi OS from the USB-3 flask drive. Tom Dean
Re: RPi 4b Wifi Device
this is what i was talking about, i don't like booting an sbc from stick even if you can hit disk can net run on sbc? On Tue, Apr 23, 2024 at 11:51 AM Thomas D. Dean wrote: > On 4/20/24 15:29, Michael Cheponis wrote: > > I run an RPi 4B/8G with external USB SSD drive; I do this because my > uSD cards were getting worn out after about a year of use; I've had no > such problems with my Samsung 870 EVO nor Samsung SSD T7. > > > > I use the built-in GigE adaptor on the RPi 4B, because it's > convenient as I have wired ethernet most places. So I can't help with > WiFi. > > > > I have been running an RPi 3 from a Lexar 64B Thumb Drive since June > 2019 - no problem there, either. > > I use SanDisk Extreme Pro 128GiB flash drives in the RPi 4b USB 3 port, > sometimes with a 6" USB 3 cable. > > I can always boot RPi OS on these drives. I have never been able to boot > NetBSD 10. > > I downloaded the arm64.img, and RPi4_UEFI_Firmware_v1.35.zip. On a Linux > desktop: >dd if=arm64.img of=/dev/sda bs=1M > and, then I replace the corresponding files from > RPi4_UEFI_Firmware_v1.35.zip. >mount /de3v/sda1 /mnt >cd /mnt >unzip ~/NetBSD/RPi4_UEFI_Firmware_v1.35.zip > > When I attempt to boot, I see the color flash, then a cursor at the top > left of the screen, then the screen goes blank. > > he flash drive shows lots of accesses during this process and then shows > access flashes in groups of 3 or 4. I think this indicates an unreadable > file, I think. > > When I do the the same actions with an SD card, NetBSD boots. > > What do you do? > > Tom Dean > -- renegade6969...@gmail.com https://www.facebook.com/profile.php?id=61556020800880 https://twitter.com/Rose29283220654
Re: RPi 4b Wifi Device
On 4/20/24 15:29, Michael Cheponis wrote: > I run an RPi 4B/8G with external USB SSD drive; I do this because my uSD cards were getting worn out after about a year of use; I've had no such problems with my Samsung 870 EVO nor Samsung SSD T7. > > I use the built-in GigE adaptor on the RPi 4B, because it's convenient as I have wired ethernet most places. So I can't help with WiFi. > > I have been running an RPi 3 from a Lexar 64B Thumb Drive since June 2019 - no problem there, either. I use SanDisk Extreme Pro 128GiB flash drives in the RPi 4b USB 3 port, sometimes with a 6" USB 3 cable. I can always boot RPi OS on these drives. I have never been able to boot NetBSD 10. I downloaded the arm64.img, and RPi4_UEFI_Firmware_v1.35.zip. On a Linux desktop: dd if=arm64.img of=/dev/sda bs=1M and, then I replace the corresponding files from RPi4_UEFI_Firmware_v1.35.zip. mount /de3v/sda1 /mnt cd /mnt unzip ~/NetBSD/RPi4_UEFI_Firmware_v1.35.zip When I attempt to boot, I see the color flash, then a cursor at the top left of the screen, then the screen goes blank. he flash drive shows lots of accesses during this process and then shows access flashes in groups of 3 or 4. I think this indicates an unreadable file, I think. When I do the the same actions with an SD card, NetBSD boots. What do you do? Tom Dean
Re: RPi 4b Wifi Device
michael.chepo...@gmail.com (Michael Cheponis) writes: >I use the built-in GigE adaptor on the RPi 4B, because it's convenient as I >have wired ethernet most places. So I can't help with WiFi. Ethernet is also faster, even when the WiFi chip does 802.11ac. For Wifi on a RPI4b: With RPI-OS running iperf3 shows about 80Mbit/s. NetBSD (-current, but -10 should be similar) gets me about 40MBit/s. Wifi is connected to a SDHC controller, and handling I/O there generates quite some overhead (while iperf3 is running): PID LID USERNAME PRI STATE TIME WCPUCPU NAME COMMAND 0 118 root 123 CPU/1 1:33 39.45% 39.45% sdmmc0[system] 7467 12269 mlelstv 85 mutex/2 0:03 4.79% 4.79% - iperf3 0 3 root 222 IDLE/0 0:04 2.59% 2.59% softnet*0 [system] 0 101 root 222 IDLE/3 0:03 1.81% 1.81% softnet*3 [system] 030 root 222 IDLE/2 0:02 1.32% 1.32% softnet*2 [system] 024 root 222 IDLE/1 0:02 0.93% 0.93% softnet*1 [system] That's about 80% of one core.
Re: RPi 4b Wifi Device
I run an RPi 4B/8G with external USB SSD drive; I do this because my uSD
cards were getting worn out after about a year of use; I've had no such
problems with my Samsung 870 EVO nor Samsung SSD T7.
I use the built-in GigE adaptor on the RPi 4B, because it's convenient as I
have wired ethernet most places. So I can't help with WiFi.
I have been running an RPi 3 from a Lexar 64B Thumb Drive since June 2019 -
no problem there, either.
-Mike
-Mike
On Sat, Apr 20, 2024 at 2:04 PM Thomas D. Dean
wrote:
> On 4/20/24 13:16, Michael van Elst wrote:
> > tomd...@wavecable.com ("Thomas D. Dean") writes:
> >
> >> # wpa_cli status
> >> Selected interface 'bwfm0'
> >> 21:58:44.815: bssid=60:38:e0:db:a9:7a
> >> freq=0
> >> ssid=tddhome
> >> id=0
> >> mode=station
> >> pairwise_cipher=TKIP
> >> group_cipher=TKIP
> >> key_mgmt=WPA-PSK
> >> wpa_state=GROUP_HANDSHAKE
> >> ip_address=169.254.135.120
> >> address=e4:5f:01:da:eb:46
> >
> >> I don't understand where the inet 169.254.135.120 comes from. The router
> >> pool is 192.168.1.xxx.
> >
> > 169.254.x.x is a "link local" address. dhcpcd falls back to such an
> > address, if it doesn't get an answer from a dhcp server. Apparently
> > wpa_supplicant cannot connect to the network.
> >
> >> wpa_state=GROUP_HANDSHAKE
> >
> > says that it still tries to associate. When it's done this would
> > change to COMPLETED.
> >
>
> I have two RPi 4b's. One with NetBSD 10 on an SD card and the other with
> RPi OS on a USB flash drive. (I can not get NetBSD to boot from a flash
> drive)
>
> As far as I can tell the network configurations are the same for WIFI on
> both. I see comments on the web about NetBSD 10 problems with the bwfm
> device.
>
> I need WIFI. So, I go back to RPi OS.
>
> Thanks for all the replies.
>
> Tom Dean
>
Re: RPi 4b Wifi Device
On 4/20/24 15:29, Michael Cheponis wrote: I run an RPi 4B/8G with external USB SSD drive; I do this because my uSD cards were getting worn out after about a year of use; I've had no such problems with my Samsung 870 EVO nor Samsung SSD T7. I use the built-in GigE adaptor on the RPi 4B, because it's convenient as I have wired ethernet most places. So I can't help with WiFi. I have been running an RPi 3 from a Lexar 64B Thumb Drive since June 2019 - no problem there, either. I use SanDisk Extreme Pro 128GiB flash drives in the RPi 4b USB 3 port, sometimes with a 6" USB 3 cable. I can always boot RPi OS on these drives. I have never been able to boot NetBSD 10. I downloaded the arm64.img, and RPi4_UEFI_Firmware_v1.35.zip. On a Linux desktop: dd if=arm64.img of=/dev/sda bs=1M and, then I replace the corresponding files from RPi4_UEFI_Firmware_v1.35.zip. mount /de3v/sda1 /mnt cd /mnt unzip ~/NetBSD/RPi4_UEFI_Firmware_v1.35.zip When I attempt to boot, I see the color flash, then a cursor at the top left of the screen, then the screen goes blank. The flash drive shows lots of accesses during this process and then shows access flashes in groups of 3 or 4. I think this indicates an unreadable file, I think. When I do the the same actions with an SD card, NetBSD boots. What do you do? Tom Dean
Re: RPi 4b Wifi Device
On 4/20/24 13:16, Michael van Elst wrote:
tomd...@wavecable.com ("Thomas D. Dean") writes:
# wpa_cli status
Selected interface 'bwfm0'
21:58:44.815: bssid=60:38:e0:db:a9:7a
freq=0
ssid=tddhome
id=0
mode=station
pairwise_cipher=TKIP
group_cipher=TKIP
key_mgmt=WPA-PSK
wpa_state=GROUP_HANDSHAKE
ip_address=169.254.135.120
address=e4:5f:01:da:eb:46
I don't understand where the inet 169.254.135.120 comes from. The router
pool is 192.168.1.xxx.
169.254.x.x is a "link local" address. dhcpcd falls back to such an
address, if it doesn't get an answer from a dhcp server. Apparently
wpa_supplicant cannot connect to the network.
wpa_state=GROUP_HANDSHAKE
says that it still tries to associate. When it's done this would
change to COMPLETED.
I have two RPi 4b's. One with NetBSD 10 on an SD card and the other with
RPi OS on a USB flash drive. (I can not get NetBSD to boot from a flash
drive)
As far as I can tell the network configurations are the same for WIFI on
both. I see comments on the web about NetBSD 10 problems with the bwfm
device.
I need WIFI. So, I go back to RPi OS.
Thanks for all the replies.
Tom Dean
Re: RPi 4b Wifi Device
tomd...@wavecable.com ("Thomas D. Dean") writes:
># wpa_cli status
>Selected interface 'bwfm0'
>21:58:44.815: bssid=60:38:e0:db:a9:7a
>freq=0
>ssid=tddhome
>id=0
>mode=station
>pairwise_cipher=TKIP
>group_cipher=TKIP
>key_mgmt=WPA-PSK
>wpa_state=GROUP_HANDSHAKE
>ip_address=169.254.135.120
>address=e4:5f:01:da:eb:46
>I don't understand where the inet 169.254.135.120 comes from. The router
>pool is 192.168.1.xxx.
169.254.x.x is a "link local" address. dhcpcd falls back to such an
address, if it doesn't get an answer from a dhcp server. Apparently
wpa_supplicant cannot connect to the network.
>wpa_state=GROUP_HANDSHAKE
says that it still tries to associate. When it's done this would
change to COMPLETED.
Re: RPi 4b Wifi Device
> On Apr 20, 2024, at 1:01 AM, Thomas D. Dean wrote:
>
> On 4/19/24 18:35, Michael van Elst wrote:
>> 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/
>
> I saw that.
> dhcp is working over the wired connection.
>
> I thought I had everything configured for wifi. It just does not work.
>
> I have a cable modem <-> wifi/wired router. I have several machines
> connected. Linux and windoze, now. One RPi with NetBSD 10. Used to have some
> FreeBSD machines, but, they have been replaced.
>
> # etc/rc.d/wpa_supplicant reload
> Selected interface 'bwfm0'
> 21:58:35.931: OK
>
> # wpa_cli status
> Selected interface 'bwfm0'
> 21:58:44.815: bssid=60:38:e0:db:a9:7a
> freq=0
> ssid=tddhome
> id=0
> mode=station
> pairwise_cipher=TKIP
> group_cipher=TKIP
> key_mgmt=WPA-PSK
> wpa_state=GROUP_HANDSHAKE
> ip_address=169.254.135.120
> address=e4:5f:01:da:eb:46
>
> # ifconfig bwfm0
> bwfm0: flags=0x8843 mtu 1500
> ssid "" nwkey 65536:"","","",""
> powersave off
> address: e4:5f:01:da:eb:46
> media: IEEE802.11 autoselect (DS1 mode 11g)
> status: no network
> inet6 fe80::d7c0:41b9:46a5:a5ff%bwfm0/64 flags 0x8 scopeid 0x3
> inet 169.254.135.120/16 broadcast 169.254.255.255 flags 0x4
>
>
>
> I don't understand where the inet 169.254.135.120 comes from. The router pool
> is 192.168.1.xxx.
That's an APIPA address from block 169.254.0.0/16. dhcpcd gives the interface
an address from that block when it can't properly obtain one via DHCP, unless
instructed not to.
>
> Tom Dean
Re: RPi 4b Wifi Device
I have Authentication timeout.
# wpa_cli
> scan_results
23:27:43.451: bssid / frequency / signal level / flags /
ssid60:38:e0:db:a9:7a 2462 227 [WPA-PSK-TKIP][ESS] tddhome
...
23:27:47.736: CTRL-EVENT-SCAN-RESULTS
23:27:47.736: Trying to associate with 60:38:e0:db:a9:7a
(SSID='tddhome' freq=2462 MHz)
23:27:52.874: Associated with 60:38:e0:db:a9:7a
23:28:02.888: Authentication with 60:38:e0:db:a9:7a timed out.
23:28:02.889: CTRL-EVENT-DISCONNECTED bssid=60:38:e0:db:a9:7a
reason=3 locally_generated=1
23:28:02.889: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="tddhome"
auth_failures=1 duration=10 reason=CONN_FAILED
The linksys router uses WPA2/WPA mixed Personal. PSK is correct in
etc/wpa_supplicant.conf:
# cat /etc/wpa_supplicant.conf
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=wheel
network={
ssid="tddhome"
key_mgmt=WPA-PSK
psk="..."
}
Tom Dean
Re: RPi 4b Wifi Device
On 4/19/24 18:35, Michael van Elst wrote:
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/
I saw that.
dhcp is working over the wired connection.
I thought I had everything configured for wifi. It just does not work.
I have a cable modem <-> wifi/wired router. I have several machines
connected. Linux and windoze, now. One RPi with NetBSD 10. Used to have
some FreeBSD machines, but, they have been replaced.
# etc/rc.d/wpa_supplicant reload
Selected interface 'bwfm0'
21:58:35.931: OK
# wpa_cli status
Selected interface 'bwfm0'
21:58:44.815: bssid=60:38:e0:db:a9:7a
freq=0
ssid=tddhome
id=0
mode=station
pairwise_cipher=TKIP
group_cipher=TKIP
key_mgmt=WPA-PSK
wpa_state=GROUP_HANDSHAKE
ip_address=169.254.135.120
address=e4:5f:01:da:eb:46
# ifconfig bwfm0
bwfm0: flags=0x8843 mtu 1500
ssid "" nwkey 65536:"","","",""
powersave off
address: e4:5f:01:da:eb:46
media: IEEE802.11 autoselect (DS1 mode 11g)
status: no network
inet6 fe80::d7c0:41b9:46a5:a5ff%bwfm0/64 flags 0x8 scopeid 0x3
inet 169.254.135.120/16 broadcast 169.254.255.255 flags 0x4
I don't understand where the inet 169.254.135.120 comes from. The router
pool is 192.168.1.xxx.
Tom Dean
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: RPi 4b Wifi Device
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
RPi 4b Wifi Device
What is the wifi device in the RPi 4b? Driver? Tom Dean
