Mastodon

1 post1 participant0 posts today

Marcin Cieślak<a href="https://bsd.network/@vinishor" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@vinishor</a> great post, one of my last projects for <a href="https://mastodon.social/tags/Sparc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Sparc</a> is to prepare a minimal Solaris setup for them. I was booting them over the network (“boot net” from the ok prompt) and using Jumpstart to automatically install Solaris on them.<a href="https://mastodon.social/tags/OpenFirmware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenFirmware</a> is an intersection system on its own, you can build your own from the source from <a href="https://github.com/MitchBradley/openfirmware" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/MitchBradley/openfirmware</a>Thanks <a href="https://masto.ai/@simondassow" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@simondassow</a> for boosting this!

Kevin Karhan :verified:<a href="https://mstdn.io/@wolf480pl" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@wolf480pl</a> <a href="https://social.treehouse.systems/@cas" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@cas</a> I just assume they don't want to have to deal with a <a href="https://infosec.space/@kkarhan/114465885276391701" rel="nofollow noopener noreferrer" target="_blank">gazillion of undocumented SBCs</a> that may only get 1 person to once push code that gets accepted, but then "orphaned" and break over time as they may not be willing to build & test every new kernel before release just to enshure it ain't broken!<ul><li>Espechally since <a href="https://infosec.space/tags/ARM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ARM</a> doesn't have just a <code>bootcode.bin</code> and <a href="https://infosec.space/tags/UEFI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UEFI</a> to boot from, but half a dozen different mechanisms ranging from fixed sector location and -sizes for the <code>initramfs</code> to <a href="https://infosec.space/tags/uBOOT" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#uBOOT</a> & <a href="https://infosec.space/tags/LinuxBoot" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LinuxBoot</a>, <a href="https://infosec.space/tags/Coreboot" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Coreboot</a> and potentially even <a href="https://infosec.space/tags/OpenFirmware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenFirmware</a>-style <a href="https://infosec.space/tags/bootcode" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#bootcode</a>... </li></ul>It's absolute chaos and one of the reasons I didn't even try to build <a href="https://infosec.space/@OS1337" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@OS1337</a> for the <a href="https://infosec.space/tags/Pi0W" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Pi0W</a> as of today...

argv minus one<a href="https://mastodon.sdf.org/tags/BIOS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BIOS</a> / <a href="https://mastodon.sdf.org/tags/OpenFirmware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenFirmware</a> in the '90s stored settings (boot order, etc) in battery-powered SRAM. If the battery died, all such settings were lost as soon as the computer was powered off.I wonder if any BIOS developers ever considered storing this information in a partition on the hard drive itself? No worries about the battery then.<a href="https://mastodon.sdf.org/tags/retrocomputing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#retrocomputing</a>

Thor A. HoplandIsn't it about time we start rallying against <a href="https://snabelen.no/tags/proprietary" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#proprietary</a> <a href="https://snabelen.no/tags/firmware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#firmware</a> already? From every <a href="https://snabelen.no/tags/EV" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#EV</a> and <a href="https://snabelen.no/tags/car" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#car</a> being a glorified <a href="https://snabelen.no/tags/telemetry" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#telemetry</a> machine, to every chip out there basically harboring <a href="https://snabelen.no/tags/SecretSauce" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SecretSauce</a> with the "trust me bro" guarantee attached. Neither <a href="https://snabelen.no/tags/US" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#US</a> interests, <a href="https://snabelen.no/tags/Chinese" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Chinese</a> interests or private interests should hold so much power. No one should. All firmware; I repeat, ALL FIRMWARE should be <a href="https://snabelen.no/tags/OpenFirmware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenFirmware</a>. The firmware isn't open? <a href="https://snabelen.no/tags/Ban" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Ban</a> the <a href="https://snabelen.no/tags/product" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#product</a> outright.<a href="https://www.tarlogic.com/news/backdoor-esp32-chip-infect-ot-devices/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.tarlogic.com/news/backdoor-esp32-chip-infect-ot-devices/</a>

Thor A. HoplandGasp. I hope that it were true, but my heart has been broken by disappointment before (*cough*<a href="https://snabelen.no/tags/librem" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#librem</a>*cough*). But I digress.Can somebody give me a damn <a href="https://snabelen.no/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> phone with <a href="https://snabelen.no/tags/openfirmware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#openfirmware</a>, <a href="https://snabelen.no/tags/gnome" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gnome</a> or <a href="https://snabelen.no/tags/plasma" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#plasma</a> mobile, a decent camera, mic and screen with enough processing, memory and storage to meet with modern self hosting in mind.Indeed, who can deliver me my dream phone? I'd be ever so happy to know about it.Liberux – Privacy, Security, Freedom <a href="https://liberux.net/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://liberux.net/</a>

Thor A. HoplandIt's CRAY-Z how each and every auto manufacturer in the world is tracking your every movement right now. From auto manufacturers in the <a href="https://snabelen.no/tags/US" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#US</a>, <a href="https://snabelen.no/tags/Europe" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Europe</a> and <a href="https://snabelen.no/tags/Asia" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Asia</a>, what we're seeing is basically a result of "secret sauce" once more. The fact is that the only thing that will save us is <a href="https://snabelen.no/tags/OpenSource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenSource</a> and <a href="https://snabelen.no/tags/OpenFirmware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenFirmware</a>, because as always the vendor does not deserve blind trust, because they will abuse it.VW Is Recording Your EVERY Movement <a href="https://youtube.com/watch?v=yt_LWoj7Sjc" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://youtube.com/watch?v=yt_LWoj7Sjc</a>

Pixel PurritoPeriodic reminder that <a href="https://oldbytes.space/tags/OpenFirmware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenFirmware</a> works on x86 as well: <a href="https://www.openfirmware.org/Open_Firmware" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.openfirmware.org/Open_Firmware</a> — that's where device trees come from, and maybe we would have been better off using it instead of UEFI or U-Boot, which I personally find quite janky.

Marcin Cieślak<a href="https://metalhead.club/@lkundrak" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@lkundrak</a> Yes, that's me. I am not sure I knew what I was doing, but it was fun! I love <a href="https://mastodon.social/tags/openfirmware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#openfirmware</a>

SiddeFantastic! <a href="https://bitbang.social/tags/TotallyNormalComputing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TotallyNormalComputing</a> Booting <a href="https://bitbang.social/tags/MacOS9" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#MacOS9</a> Installer from USB, and without even touching <a href="https://bitbang.social/tags/OpenFirmware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenFirmware</a>. I really like the community for this kind of service! 'Mac OS 9.2.2 "boot kit" for booting your G3/G4 from an USB stick' by that-ben on Macintosh Repository just works out of the box! On a <a href="https://bitbang.social/tags/powerpc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#powerpc</a> <a href="https://bitbang.social/tags/G3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#G3</a> <a href="https://bitbang.social/tags/ibook" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ibook</a> with USB1.And it was kinda fast to boot and install too. My <a href="https://bitbang.social/tags/Powerbook" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Powerbook</a> got some company now!.<a href="https://bitbang.social/tags/Apple" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Apple</a> <a href="https://bitbang.social/tags/Macintosh" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Macintosh</a> <a href="https://bitbang.social/tags/PPC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PPC</a> <a href="https://bitbang.social/tags/VintageMac" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#VintageMac</a> <a href="https://bitbang.social/tags/retrocomputing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#retrocomputing</a>

AGRO TURBO.EXE SATAN 🇺🇦🇨🇿weekend timewaster <a href="https://metalhead.club/tags/OpenBoot" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenBoot</a> <a href="https://metalhead.club/tags/OpenFirmware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenFirmware</a> <a href="https://metalhead.club/tags/Forth" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Forth</a>

dorotaC<a href="https://fosstodon.org/@yakkoj" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@yakkoj</a> <a href="https://fosstodon.org/tags/OpenFirmware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenFirmware</a> was the most pleasant boot environment I ever used. I could figure out how to boot things, which is not exactly true today with an EFI shell. And that was on real hardware, too.<a href="https://fosstodon.org/tags/ultrasparc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ultrasparc</a>

Thor A. HoplandWell holy hell. <a href="https://snabelen.no/tags/SecureBoot" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SecureBoot</a> doesn't work when you got a firmware rootkit? Say it ain't so...!Tell me again why <a href="https://snabelen.no/tags/OpenFirmware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenFirmware</a> is a bad idea again?The <a href="https://snabelen.no/tags/SecretSauce" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SecretSauce</a> fallacy keeps getting pummelled in the face, decade after decade.

Profoundly NerdyHey <a href="https://bitbang.social/tags/mac" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#mac</a> nerds: does <a href="https://bitbang.social/tags/openfirmware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#openfirmware</a> <a href="https://bitbang.social/tags/Forth" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Forth</a> cell size very according the the word size of the <a href="https://bitbang.social/tags/PowerPC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PowerPC</a> processor? That is, is the cell size 32 bits on a G3 and 64 bits on a G5? <a href="https://bitbang.social/tags/retrocomputing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#retrocomputing</a> <a href="https://bitbang.social/tags/osx" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#osx</a> <a href="https://bitbang.social/tags/macos" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#macos</a> <a href="https://bitbang.social/tags/ppc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ppc</a>Also is there an OpenFirmware "Bible" that goes deeper than Mac OS X Internals by Amit Singh?

Patrick GeorgiSo I finally plugged in the <a href="https://retro.social/tags/retrocomputing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#retrocomputing</a> <a href="https://retro.social/tags/PPC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PPC</a> Mac G4, and it booted into MacOS X 10.4.11, the newest release that supports the hardware. Browsing the web is practically impossible because it only supports ancient cipher suites that web servers refuse to work with, for good reason. What else is there to do?I guess the most useful environment on the system as is, is <a href="https://retro.social/tags/OpenFirmware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenFirmware</a>. (If I continue like that, IEEE1275 will be the majority firmware in this office)

Legume<a href="https://mastodon.ar.al/@aral" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@aral</a> Reading the product page, the open source coreboot firmware and open warranty caught my eye. You can take apart the tablet, replace parts, and change the operating system without voiding the warranty... nice!<a href="https://lentil.social/tags/openwarranty" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#openwarranty</a> <a href="https://lentil.social/tags/openfirmware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#openfirmware</a>

Thor A. HoplandNo human made system can stand the test of time, no matter how many times you may patch it - word to US legislature.Regarding <a href="https://snabelen.no/tags/hardware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#hardware</a>, it's time to demand <a href="https://snabelen.no/tags/openfirmware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#openfirmware</a> from <a href="https://snabelen.no/tags/manufacturers" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#manufacturers</a>. It might mean giving extra playing cards to <a href="https://snabelen.no/tags/hackers" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#hackers</a>, but they can already read <a href="https://snabelen.no/tags/assembly" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#assembly</a> and have no problem <a href="https://snabelen.no/tags/decompiling" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#decompiling</a> or <a href="https://snabelen.no/tags/debugging" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#debugging</a> their way to <a href="https://snabelen.no/tags/vulnerabilities" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#vulnerabilities</a>.It's a good idea to start with all <a href="https://snabelen.no/tags/x86" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#x86</a> chips that are <a href="https://snabelen.no/tags/EOL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#EOL</a>, which should be refurbished with open firmware.<a href="https://www.bleepingcomputer.com/news/security/new-spectre-v2-attack-impacts-linux-systems-on-intel-cpus/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.bleepingcomputer.com/news/security/new-spectre-v2-attack-impacts-linux-systems-on-intel-cpus/</a>

adriI want to share a useful link and a couple of real screenshots with <a href="https://mastodon.social/tags/openfirmware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#openfirmware</a> commands and words, just in case someone needs it.<a href="http://mac-classic.com/articles/open-firmware-basics/" rel="nofollow noopener noreferrer" translate="no" target="_blank">http://mac-classic.com/articles/open-firmware-basics/</a>Oh, and if it doesn’t seem to boot into it, try with the right option/alt key 🙂

Jose Morales<a href="https://bitbang.social/@profoundlynerdy" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@profoundlynerdy</a> Well given that <a href="https://universeodon.com/tags/openfirmware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#openfirmware</a> is available, it could be a starting point for an UEFI replacement… also, <a href="https://universeodon.com/tags/CForth" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CForth</a> from Mitch Bradley is based on the work done on OpenFirmare, it would be a great starting point. Major opportunity could be the SBC market, but there are plenty of challenges there with Binary Blobs for the GPU’s… would love to see that happen!

Profoundly NerdyI admire what <a href="https://bitbang.social/tags/OpenFirmware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenFirmware</a> did on the <a href="https://bitbang.social/tags/PPC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PPC</a> <a href="https://bitbang.social/tags/Mac" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Mac</a>. It was compact and focused while being modern and extensible.I think <a href="https://bitbang.social/tags/UEFI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UEFI</a> is bloated. All code has bugs, larger code bases have more of them than smaller code bases.I know OpenFirmware still technically exists but it seems dormant. Is there any real benefit to writing a <a href="https://bitbang.social/tags/BIOS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BIOS</a> implementation in <a href="https://bitbang.social/tags/Forth" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Forth</a> that is similarly scriptable?

ErtainI'm surprised that there's very little open <a href="https://mast.linuxgamecast.com/tags/firmware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#firmware</a> for common office <a href="https://mast.linuxgamecast.com/tags/printers" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#printers</a>. I know the printers (even among brands and lines of products) are heterogeneous. But there's has got to be some <a href="https://mast.linuxgamecast.com/tags/hardware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#hardware</a> <a href="https://mast.linuxgamecast.com/tags/hacker" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#hacker</a> who's tried writing open firmware for <a href="https://mast.linuxgamecast.com/tags/HP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HP</a>, <a href="https://mast.linuxgamecast.com/tags/Canon" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Canon</a>, and Brother printers. <a href="https://mast.linuxgamecast.com/tags/OpenFirmware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenFirmware</a>

Recent searches

Search options

Administered by:

Server stats:

#openfirmware