Hello, You need to pre search for devices before you buy or you will run into this. A device driver needs the code and the fw sometimes it's not the code but the fw luckily OpenBSD has fw_uodate which does an awesome job. But if you want to use any BSD you need to either do a approps for supported HW or create your own driver just how it is. You can't buy a new pre built computer and not have something not be supported mostly being wifi not to mention WiFi is limited to 2.4 so what's the point and this isnt the projects fault buy companies that don't have docs for drivers the BSDs are awesome for a server but they aren't good desktops and this to be fair includes Linux the whole what's makes a desktop a desktop is plugging something in and it works if you have to mess with it and install firmwares due to people wanting free software well this happens. WiFi 7 came out but most drivers only support g and g these days is not good enough.
Another issue is tech speed we just got the pi5 and this only works on Linux cause the devs only care about it so what's the point in calling it open if the manu only bounds it devs to one set of software ? This is mostly why I'm starting to move away from OSS and go back to Mac os and Windows as it just works (TM) Chris Sent from Proton Mail Android -------- Original Message -------- On 5/4/24 3:11 PM, Peter N. M. Hansteen <pe...@bsdly.net> wrote: > On Sat, May 04, 2024 at 03:01:54PM -0300, Gustavo Rios wrote: > > I have just installed OpenBSD in my brand new notebook. It is a dell > > notebook that came with just a wifi NIC. How do i discover the name o my > > wifi nic ? > > ifconfig with no arguments should list all network interfaces the kernel has > recognized. > > There is a catch, though. For wifi interfaces it is likely that the interface > can not be configured until the device's firmware is installed. > > If that is the situation, a common workaround is to use some device that > *is* configurable (most USB Ethernet dongles I have encountered Just Work), > configure that, then run fw_update. Once the firmware is in place, the rest > should be straightforward. > > Good luck! > > - Peter > > > -- > Peter N. M. Hansteen, member of the first RFC 1149 implementation team > https://bsdly.blogspot.com/ https://www.bsdly.net/ https://www.nuug.no/ > "Remember to set the evil bit on all malicious network traffic" > delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds. > >
