Does anyone have experience running Asahi on a home server? Does the silicon’s power efficiency when running macOS translate to Asahi?
I’d also be really curious to hear if there are any gotchas and/or reliability issues. For example, features such as hardware video decoding do not seem to be supported (yet).
Note that the order of the lines in /etc/pam.d/sudo matters.
Add the "auth sufficient pam_tid.so" line below the pam_smartcard.so line as shown in the article for this to work correctly.
I just found out the hard way that this feature is only supported on iPhone XS and later (seemingly any device with at least an A12 chip): https://support.apple.com/en-us/HT212630
We had lots of issues with USB3 cameras interfering with (RTK-) GPS receivers for a drone project [0]. When mounted on the drone, the receiver would just not get a fix, even in seemingly perfect conditions, i.e. unobstructed view of the sky, far away from buildings, no clouds, etc. One day, I randomly unplugged the cameras and suddenly the receiver started working. I repeatedly plugged and unplugged the USB3 hub just to make sure I'm not crazy. The GPS receiver would go from no fix at all to centimeter-level accuracy every time I unplugged.
We then used a spectrum analyzer to better understand the extent of the interference, tried shielding as described in the whitepaper, as well as separating the components physically as much as 30cm -- all without success. The only solution that worked was to replace the USB3 cables with USB2 cables and acquiring images at a lower frame rate.
I don't even want to know how many people have been affected by these issues over the years. USB3 devices should come with a warning sticker on the box.
I've bought AirPods Pro in early November right after they were released. From my personal experience, the background firmware updates have had a very noticeable effect. I can attest to the perceived weakening of ANC (as opposed to the initial firmware) the article mentions.
One firmware update has even rendered one of my AirPods Pro practically unusable due to a strange clicking noise that would occur whenever I was walking/running with ANC enabled, likely due to accelerations acting upon it. I was convinced it was a hardware fault and was ready to return them until another firmware update fixed the problem (until now at least).
A popular library that has unfortunately not transitioned to Python 3 yet is rospy (which is part of the larger ROS ecosystem for robotics). It is the last framework that prevents me to fully embrace Python 3 for my everyday work. I sincerely hope the robotics community will eventually port rospy (and other ROS-related libraries) to Python 3.
I am, however, very happy to see that ROS2 (the next iteration of ROS) uses Python 3 by default.
I'm in the same boat. It bothers me that my only option will be to rewrite in Python 3. Unless they provide a very clear migration path, I'm far more likely to just remove ROS entirely, unfortunately.
