Apple’s EFI embeds an older version of wpa supplicant, possibly you are trying to connect to a network with a newer encryption standard like WPA3. I don’t that’s too unreasonable for a 15 year old computer
Thanks for the explanation! Makes sense. Unreasonable? To me, no. Makes complete sense given the age. BUT it doesn't support, IMO, "Apple is the opposite of planned obsolescence". Yes, tech nerds can do tech nerd things to make it work...that's not a "plan".
I apologize if that came off harsh. I feel like your comment had a different angle/context than where I took it. Apologies if so.
Microsoft hate is easy to come by on HN (I get it), so I don't like seeing a Apple's coincidental victories magnified in one of the few areas Microsoft does well as a feature.
Things stopping to function perfectly because operating environment has changed drastically over a significant period of time is pretty much the polar opposite of planned obsolescence.
Even devices that don't suffer from planned obsolescence can and do become obsolete.
That’s not planned obsolescence. Your home network migrated to a new key exchange protocol that didn’t exist in 2011. That’s on you our your router manufacturer.
I can't remember now -- I have a WPA3 network, and I also have a WPA2 network, and an IOT network. I agree it would be reasonable for WPA3 to not work, but I'm pretty sure I was trying WPA2. Regardless, it's something I ran into.
If a device only supports 2.4Ghz, wouldn't it only see the 2.4 option? Just having a network available that the device's radios can't even see shouldn't break anything. (I'm personally leaning towards WPA3 being the problem)
It is possible that the tech exists, but isn't yet at a point that it can be easily mass-produced, which means "spy cables" may actually be available, from Q-types.
> Why is Safari allowed to send me notifications begging the user to boot it up and try the new features?
For what it's worth I've been using macOS (and OS X) for 14 years, and you only get the notification once after a fresh install and you can click close and it's gone forever, sure Linux is better on this front, but I don't want to spend my whole life tinkering my os until it works. It's still a hell of a lot better than Microsoft consistently shoving Edge down your throat.
Excellent. I haven't gone through them yet, but if you've any similar pointers for QEMU, please share.
My rough understanding is that it's the user-space emulation part of a virtualization solution. I.e., when the kernel traps the virtualized process, saying 'nope, you can't do that here', the control falls back to user space handler in QEMU saying, 'hey, the kernel said I can't do that there; can you sort this out?'. And this back-and-forth games keeps happening during the lifetime of the virtualized process.
Raspbian works perfectly fine. Most of those other operating systems don’t really have the best GPIO support which is where Raspberry Pi shines. I’d just get a cheap mini pc if I wanted to run something else.
Except the RPi is smaller, lighter, lower power and more efficient than most mini PCs. It also has a bunch of unique addon boards, many (most?) of which don't really use GPIOs, but a standard communication interface like PCIe/USB/serial/SPI/I2C.
No mini PC can beat most things about the Pi, apart from performance and compatibility, the latter of which is fully the fault of the manufacturer.
I've deployed my fair share of both and SBCs are still a very widely useful middle ground. Being able to use existing Linux tools instead of limited or nonexistent embedded libraries is a huge benefit. Most things to do with sound or video, for example, are totally infeasible with microcontrollers. A mini PC is noticably bigger and you need to add a microcontroller over USB if you need absolutely any real world interaction (even something as simple as sensing ambient light to adjust brightness).
My new favourite tool for these situations is the Radxa X4, which is the exact dimensions of a RPi, but with an Intel x86 CPU and an onboard microcontroller to drive GPIOs.
