fosstodon.org is one of the many independent Mastodon servers you can use to participate in the fediverse.
Fosstodon is an invite only Mastodon instance that is open to those who are interested in technology; particularly free & open source software. If you wish to join, contact us for an invite.

Administered by:

Server stats:

8.8K
active users

#BridgeOS

0 posts0 participants0 posts today
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://floss.social/@jbqueru" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>jbqueru</span></a></span> Also I hope for <a href="https://infosec.space/tags/RISCv" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RISCv</span></a> to be the <a href="https://infosec.space/tags/ISA" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ISA</span></a> of the future for long-term <a href="https://infosec.space/tags/OpenSourceHardware" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenSourceHardware</span></a> and support.</p><p><a href="https://infosec.space/tags/ARM64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ARM64</span></a> - just like <a href="https://infosec.space/tags/amd64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>amd64</span></a> - is <em>yet another proprietary ISA</em> and almost all devices with it in terms of <a href="https://infosec.space/tags/Laptops" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Laptops</span></a> have <a href="https://infosec.space/tags/AntiRepairDesign" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AntiRepairDesign</span></a> like <a href="https://infosec.space/tags/Apple" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Apple</span></a>'s <a href="https://infosec.space/tags/MacBook" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>MacBook</span></a>|s that self-destroy their <a href="https://infosec.space/tags/SSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SSD</span></a>|s which also contains it's <a href="https://infosec.space/tags/EFI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>EFI</span></a> / <em>"<a href="https://infosec.space/tags/BridgeOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BridgeOS</span></a>"</em>, <a href="https://www.youtube.com/watch?v=RYG4VMqatEY" rel="nofollow noopener" target="_blank">making machines with fried SSDs <em>'braindead'</em>…</a></p><p>And yes, <a href="https://infosec.space/tags/RAM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RAM</span></a> to also fails and making it not fully replaceable and upgradeable is inherently bad and I'm still mad at <span class="h-card" translate="no"><a href="https://fosstodon.org/@frameworkcomputer" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>frameworkcomputer</span></a></span> for their botched <a href="https://infosec.space/tags/FrameworkDesktop" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FrameworkDesktop</span></a> <a href="https://infosec.space/tags/PC" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PC</span></a>!</p><ul><li>Cuz it's neither necessary nor beneficial for a <a href="https://infosec.space/tags/Desktop" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Desktop</span></a> PC, unlike with the <a href="https://infosec.space/tags/Framework12" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Framework12</span></a> where the <a href="https://infosec.space/tags/SoC" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SoC</span></a> used only supports single channel and a single SODIMM so it makes sense for them to take that into account.</li></ul>
IPSW Downloads<p><a href="https://mas.to/tags/bridgeOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>bridgeOS</span></a> 9.5 (22P5072) has been released for 16 devices <a href="https://ipsw.me/9.5" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">ipsw.me/9.5</span><span class="invisible"></span></a></p>
IPSW Downloads<p><a href="https://mas.to/tags/bridgeOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>bridgeOS</span></a> 9.4 (22P4248) has been released for 16 devices <a href="https://ipsw.me/9.4" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">ipsw.me/9.4</span><span class="invisible"></span></a></p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://kitty.haus/users/lamp" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>lamp</span></a></span> yes and no.</p><p>Yes, <a href="https://infosec.space/tags/Apple" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Apple</span></a> <em>will</em> <a href="https://infosec.space/tags/EoL" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>EoL</span></a> the <a href="https://infosec.space/tags/Intel" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Intel</span></a>-based <em>"Cheesegrater"</em> <a href="https://infosec.space/tags/MacPro" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>MacPro</span></a> by 2029-2030 as per their preannounced platform lifecycle of 10 years.</p><p>No, because <a href="https://infosec.space/tags/Apple" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Apple</span></a>'s <a href="https://infosec.space/tags/ARMv8" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ARMv8</span></a>.1-A - based <a href="https://infosec.space/tags/SoC" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SoC</span></a>'s are heavily modified in that they require a feckton of <em>custom chips</em> solely for the purpose of <a href="https://infosec.space/tags/ReducedLifecycle" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ReducedLifecycle</span></a> and making repairs harder if not impossible to facilitate...</p><p>Unlike their <a href="https://infosec.space/tags/amd64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>amd64</span></a> / <a href="https://infosec.space/tags/EM64T" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>EM64T</span></a> - predecessors they don't have a dedicaded <a href="https://infosec.space/tags/EFI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>EFI</span></a> chip with "<a href="https://infosec.space/tags/BridgeOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BridgeOS</span></a>" aka. <a href="https://infosec.space/tags/AEFI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AEFI</span></a> aka. <em><a href="https://infosec.space/tags/macOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>macOS</span></a> - <a href="https://infosec.space/tags/Recovery" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Recovery</span></a></em> on but use the <em>exact same</em> <a href="https://infosec.space/tags/Flash" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Flash</span></a> chips that are <a href="https://infosec.space/tags/RAID0" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RAID0</span></a> as <a href="https://infosec.space/tags/SSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SSD</span></a>, and since those are custom with their own controllers ( <a href="https://www.youtube.com/watch?v=MANlo9fV9yI" rel="nofollow noopener" target="_blank">based off info</a> from <span class="h-card" translate="no"><a href="https://social.treehouse.systems/@marcan" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>marcan</span></a></span> ) - basically every chip is it's own NVMe <em>but proprietary</em>...<br>And <em>when</em> (not <em>if</em>) they (inevitably) die (due to exceeding TBW lifecycle or <a href="https://www.youtube.com/watch?v=7cNg_ifibCQ" rel="nofollow noopener" target="_blank">terrible engineering frying them with 12V on a 2,7V rail</a> ), the entire system is braindead.</p><p>And that is not <a href="https://www.youtube.com/watch?v=0qbrLiGY4Cg" rel="nofollow noopener" target="_blank">by accident</a> but rather <a href="https://www.youtube.com/watch?v=RYG4VMqatEY" rel="nofollow noopener" target="_blank">intentional</a>...</p>
Nicd :unverified:<p>I have a problem with my work <a href="https://fosstodon.org/tags/MBP" class="mention hashtag" rel="tag">#<span>MBP</span></a> crashing when being connected to a monitor from sleep. I looked at the error report and noticed:</p><p>&gt; Darwin Kernel Version 22.3.0: Thu Jan 5 20:17:53 PST 2023; root:xnu-8792.81.2~1/RELEASE_ARM64_T8010</p><p>Curious, this is an Intel Mac, why is it saying ARM64…<br />Turns out it&#39;s the <a href="https://fosstodon.org/tags/bridgeOS" class="mention hashtag" rel="tag">#<span>bridgeOS</span></a> in the <a href="https://fosstodon.org/tags/TouchBar" class="mention hashtag" rel="tag">#<span>TouchBar</span></a> that is crashing and it&#39;s taking down the entire computer. 😐 So not only is the touch bar user hostile, it&#39;s now also leading to panics of the entire machine.</p>
heise online (inoffiziell)Der Konzern räumt ein, dass es auf Intel-Macs mit T2-Chip zu Bootproblemen nach Installation von macOS 12 kommen kann. Ein BridgeOS-Update hilft nicht allen. <br><a href="https://www.heise.de/news/Bricking-nach-Upgrade-auf-Monterey-Apple-reicht-neue-Firmware-nach-6257400.html" rel="nofollow noopener" target="_blank">Bricking nach Upgrade auf Monterey: Apple reicht neue Firmware nach</a><br>