Ambassador Replied in thread
Administered by:
#amd64
0 posts0 participants0 posts today
Replied in thread
@krutonium @landley I mean, Ideally @OS1337 would be come a simpler and better alternative to #LinuxFromScratch or #YoctoLinux / #YoctoProject when it comes to getting started on a device.
- Ideally #SBC manufacturers would at least release the #drivers (if they can't be assed to #mainline them into #Linux) and #ReproduceableBuilds with build scripts to make them go brrr...
Cuz #RaspberryPi de-facto monopolized non-#amd64 / non-#ix86 - #SBCs because they actually give a shit and publish #documentation!
- So whilst they certainly don't support other OSes than #RaspberryPiOS, they don't just tell folks like @geerlingguy to not pester them with questions in their Forums.
Replied in thread
- I really appreciate your efforts and espechally #documentation as it makes it so much easier...
There's a reason I only considered architectures to build @OS1337 against that are "obtainable" and I'll prioritize those that I have in my possession and that can be cheaply acquired, which as of writing are about 12 build targets across 5 distinct ISAs ( #i486 and up, #amd64, #ARMv5r11, #ARMv7, #ppc64) , with only 1 (#i486SX) being currently in focus and the next one being the #Pi0 / #Pi0W who's code will run (abeit not performant) on the #Pi0W2 as well...
- All 3 #PiZero|s can be had for like €100 in total with shipping and SD-Cards so it's on-par with a useable #amd64 machine like a #ThinClient with proper SSD and RAM...
Also unlike any other #SBC manufacturer @raspberry_pi / #RaspberryPi actually write proper #documentation and not just fart out some random bootable image file and tell users to feck off!
GitHubOS1337/docu/ideas/architectures.tsv at main · OS-1337/OS1337OS/1337 Project . Contribute to OS-1337/OS1337 development by creating an account on GitHub.
Replied in thread
@meluzzy @wyatt @link And I think it's important to understand that not everyone wants to have an engineering-sample - level of access to the insides.
- The reason #RaspberryPi's are so popular is because they offer a easy, well documented platform to get shit done, and if I had to setup some cheap #PC classroom (with no access to #surplus / #refurbisher|s nor need to use #amd64 architecture-only software and -devices) I'd propably buy #Pi500 kits and matching screens.
Replied in thread
@rl_dane @OS1337 well, MDA as in the standard that every PC graphics card since the #MDA still supports - not just VGA…
- For #Terminals the 25th (rarely "0th") line is used to display status information in lieu of "lock lights" or other indicators so unlike on a #PC it's not useable there...
Obviously one can set / customize the default Terminal Output Size in the #Kernel configs at build, but #80x25 (or at least #80x24) should be supported everywhere.
- Actual
MDAdisplays are expensive collectibles and in lieu of that I'd rather configure the 1st serial port (tty0aka.COM1) to spit out a9600/8/N/1#console when #VGA or similar video output doesn't exist.
But even the shittiest GPU will do MDA without drivers on #ix86 & #amd64 because that's some #BIOS routine command and part of the backwards compatibility of every single 2D/graphics chip I've heard of that isn's a mere 3D accelerator with 2D passhtrough…
en.wikipedia.orgIBM Monochrome Display Adapter - Wikipedia
New computing setup...
Thanks to @geerlingguy for addressing the elephant in the room.
@RaspberryPi dominates the #SBC market because they know how to write #documentation and build #drivers that get accepted into #mainline #Linux kernel.
- The best specs and hardware is useless if it needs intimate knowledge on how to roll one's own kernel. And oftentimes one doesn't even get proper drivers and reproduceable build instructions but just some "vomited" out bootable images to
ddonto a microSD!
That's why my #BananPi Zero M2 is still unused to this day: It's way too inconvenient and whilst I do want to support it someday, it's just not a good start when the 1st #RasperryPi's documentation to this day is still the bare minimum and vendors can't be assed to do that.
@a1ba unsarcastically, I like that.
But then again I'm a sucker for non-#AMD / #Intel #ix86 / #amd64 #CPU|s and non-#AMD / #Intel / #nvidia / #3dfx (wallet sez so!) #GPU|s.
Like some #Transmeta / #VIA / #Vortex86 / #Cyrix / #Xiaoxin CPU with like a #SiliconMotion / #ASPEED / #Matrox / #S3 GPU added to it.
Won't run Crysis, but will run @OS1337!
@jbqueru OFC and in terms of #RISCv vs. #ARM it won't be competitive for quite some time as ARM includes a lot of #proprietary and #patented #PowerSaving technologies that are just not available outside of said closed ISA.
@jbqueru Also I hope for #RISCv to be the #ISA of the future for long-term #OpenSourceHardware and support.
#ARM64 - just like #amd64 - is yet another proprietary ISA and almost all devices with it in terms of #Laptops have #AntiRepairDesign like #Apple's #MacBook|s that self-destroy their #SSD|s which also contains it's #EFI / "#BridgeOS", making machines with fried SSDs 'braindead'…
And yes, #RAM to also fails and making it not fully replaceable and upgradeable is inherently bad and I'm still mad at @frameworkcomputer for their botched #FrameworkDesktop #PC!
- Cuz it's neither necessary nor beneficial for a #Desktop PC, unlike with the #Framework12 where the #SoC used only supports single channel and a single SODIMM so it makes sense for them to take that into account.
Replied in thread
@pauliehedron @BrodieOnLinux I daily drive a #hp #t620 as a mini server, because in #Germany power is expensive af and I want something cheap (€30 used), quiet (fanless!) and having #amd64 durig the #PiShortage.
- And yes, it'll even run @tails_live / @tails / #Tails and @torproject / #Tor if you are patient with it ir chug in a 2nd 4GB RAM stick in it.
@JessTheUnstill @bohwaz @punkfairie @ajsadauskas @tomiahonen @fuchsiii Exactly...
Coincidentially, that's why #Android (and #iOS) doesn't let users have #root access because billions of devices owned by mostly "#TechIlliterates" that hardly get #SecurityUpdates would be an even bigger risk if they didn't boot a locked-down #ROM image, thus only allowing for #malware in user-privilegued userspace!
- I'd even go so far that I'd wish for @torproject to basically merge fmr. #FirefoxOS / #KaiOS & @tails_live / @tails / #Tails to build a #privacy-focussed #ROM for #Smartphones and #Tablets i.e. "#TailsMobile" or sth.
Cuz having a mobile OS that shoves everything through #Tor and only allows #userspace-Apps in the form modern web technologies would be a big #security and #privacy gain.
Replied in thread
Replied in thread
@riley @frameworkcomputer heard of it, sadly I need #amd64 hardware.
@vetgaming @linuxmint It's just a necessity, according to @fuchsiii, as it's just not feasible longterm to collect rarer-and-rarer #VintageComputing hardware and rely on non-enforcement of copyright on #Abandonware.
- Plus whilst #Valve isn't antragonistic to #Proton / #DXVK repackagings, not relying on them is kinda important, as this setup also helps with otger applications that ain't strictly games or in setups that one may not want to be on the internet.
It makes #TheSims and #FightingIsMagic just work on anything that is #amd64 and has enough resources to throw at it.
Replied in thread
@MaliciousCarp consider some #fanless #amd64 #ThinClient instead....
- The work great as mini-servers, can accept quite a lot of RAM and usually have at meast USB 3.0 & M.2 B-Key slots...
Replied in thread
Replied in thread
@derf @Lili wegen #Stromkosten nutz' ich alte #fanless #ThinClients wie #hp t520.
- Sind auch #AMD64.
- können problemlos bis zu 2x 4GB DDR3-SODIMMs fressen.
- ne 2240 M.2 B-Key SSD passt auch rein.
- USB 3.0 und GBit-NIC reivhen für 08/15-#NAS...
- Hat genug Luft als #Downloadknecht alla #ytdlp...