I’m adding my info even though Waddlesplash has marked the iprowifi4965 driver as “OK” because my computer will either connect to my WPA2 access point the first time or try to connect and fail four or five times before finally connecting.
Failed auto-join is a known issue. As for the repeated failures, that’s probably DHCP, also a known issue. So the driver is probably working fine, at least.
I just remembered I have a netbook with a defective LCD output that still has a working HDMI output and it’s identical to a model I still use. Could you use that if I sent it to you?
Unfortunately I probably won’t have any time to look at it
Actually I think @mmu_man made some potentially relevant fixes lately, but I dunno if it was enough to get those devices to work. (I think he has a similar netbook.)
Mine are Dell Inspiron Mini 10 - they were quite popular back in their day, although they’re 32-bit only with 1GB RAM soldered on the same card the CPU is soldered on, which is connected in a slot on the motherboard. So the upgrade to 2GB RAM was more expensive than worth the trouble, and now they’re rare. But its size and the fact that it’s still good for basic communication makes it quite comfortable and useful compared to any phone, as long as you know what software to put on it.
Wireless device ralinkwifi shows up in Networking preferences. Can’t connect, no wireless networks found. My other laptops, other wireless devices connect fine w/R1/Beta1. FreeBSD shows driver working since 2013. Wifi on this laptop is working in OpenBSD, sorry, I don’t run FreeBSD at this time, working on it soon.
You should open a ticket for that describing exactly happens when you try to connect and the relevant syslog passages.
As the above shows, the driver knows your chipset and is loaded.