#amd64
@keao well, @fuchsiii is certainly a fan and unless you constantly edit RAW & non-ProRes all day long, it's a #fanless machine that just wörks!
Consistently getting double-digit hoirs of runtime even when torturing it is basically unmatched at either weight, price and/or performance to the point that many say this is the beginning of the end of #amd64 / #ix86(-64)...
Because any competitior that beats it in any of the categories fails at the other two...
That being said #AIX and the #RS6000 is as far away from a #consumer #PC as #zArchitecture, #DB2 and a lot of other #IBM products...
After all #Services make #Software,
Software makes #Operating Systems,
#OperatingSystems make #Hardware.
Otherwise noone would deal with #AMD64 and everyone would've transitioned to #ARM64 or even #RiscV #128Bit ages ago...
https://www.youtube.com/watch?v=XzhCGSE7KKw&t=4017s
@ncommander It reminds me of some stuff like the #PoweMacintosh 6100/66 "DOS-Compatible" that #LGR reviewed ( https://www.youtube.com/watch?v=9UclHrIIaYA ) and the #Apple2 #PDS card that #8BitGuy took a look at ( https://www.youtube.com/watch?v=tvZ43JqrvXA ) ...
I wounder if we'll see something with #amd64-based #Atom / #Celeron / #COREi chips similar to the NUC Extreme Kits for #Linux #PC's once the mainstream goes #ARM64 or even #RiscV-128...
Added these symlinks.
#glibc needs some "convincing" to install *everything* to /usr, but it works.
It solves the issue on #aarch64 and #i386 (which both install the program interpreter to /lib by default).
It does NOT solve the issue on #amd64, where the program interpreter is installed to /lib64, but *something* during #GCC build insists on finding it in /usr/lib instead. 🤯
Trying a hack with a hardlink now (after learning that glibc's ldconfig just deletes symlinks to the program interpreter).
Finally, my #Linux-native #GNU toolchain for #FreeBSD's #Linuxulator works for C and C++ on #aarch64, #amd64 and #i386 🥳
I guess that's a good time to actually announce the ongoing project!
https://lists.freebsd.org/archives/freebsd-ports/2023-August/004263.html
I just installed #devuan5 on one of my #amd64 PCs and fired up #Emacs, and for some reason I held down the Windows/Super key before pressing the space bar. To my surprise it brought up a mini-buffer replicating the #LXDE menu.
Is that something new in #Emacs 29 or has that been there longer and I just never noticed it? Because it makes apps like #rofi and #dmenu kinda irrelevant. =^.^=
@aurora sadly every competitior just vomits out some boards with shit to nonexistent documentation.
You might - if you don't need #ARM64 but could also use #ix86 / #amd64 - choose some #ThinClient like a #hp #T620 which can be had for as little as €30 with power supply, optional stand, 4GD DDR3L-SODIMM and 8GB M.2 B-Key SSD.
@SebastienK that claim doesn't hold water considering the unfixable mess of #AMD64 / #ix86 and the unfixable #bloat that is #UEFI.
Instead they literally made an #Outlook-#Clone as #EFI-App!
https://gekk.info/articles/hp-quickweb.htm
@profoundlynerdy ASM probably lacks a library system by virtue of having a truly gargantuan number of combinations of architectures, chipsets, revisions, errata, peripherals, and other details to factor in/consider, all of which tend to matter when ASM is your best and/or only option. Even acquiring all of the necessary hardware would be expensive and arduous, much less testing and maintaining the library across all those targets.
C also has some of those concerns, but to a lesser degree. There may not be a "package manager" for C, but there are typically standard libraries available for most of the common targets. And higher level languages typically have orders of magnitude fewer combinations of factors to deal with, which makes having a packaging ecosystem a more attractive prospect with less overall burden.
#asm #AssemblyLanguage #Programming #amd64 #x86 #mos6502 #mips #riscv #ppc #m68k #RetroComputing
@benaryorg @fuchsiii Yeah...
Those #amd64 chonkers really make room temp go brrr...
@ariadne Eeyuppp!
There's a reason #Transmeta literally did design their chips to emulate #amd64 & #ix86 with an architecture that isn't an #ISA a OS can even directly utilize.
That being said, I'm confident that #ARM / #ARM64 will be a stepping stone till #RISCV is mature enough to become mainstream (i.e. 20 Years) and cheap $10 #FPGAs allow running one at a performance that is on-par to then current #AppleSilicon SoCs and faster than any current-day #AMD64 can be.
@m0xee @kirby @memefolder 1/10, cuz I could at least accept an #ix86 / #amd64 #SBC as a "coprocessor" / "accelerator" card.
Like that #Oddware Card on some #PowerPC #Macs...
https://www.youtube.com/watch?v=9UclHrIIaYA
To run legacy Software and Hardware...
I signed up for the #IBM #zDevelopmentTest environment trial - I can only imagine how many layers of #virtualization are happening right now as my sandboxed browser is connected to a virtual #Win10 looking box, to configure a virtual #zOS machine on a remote virutal #Linux machine- Curious how it compares to the actual #ADCD /zOS experience on bare #amd64
@ActionRetro How about #BunsenLabs #Linux on the #T61?
Because that'll run awesome...
https://www.bunsenlabs.org/
Sadly unless your T61 has a #Core2Duo upgraded it won't run #amd64 / #64bit distros, so you won't be able to use @tails / #Tails on it...
https://tails.boum.org
Otherwise do it like @fuchsiii and upgrade the #T61 beyond reasonable specs with something like a 2TB SSD and use it as #WindowsXP or #Windows7 #retro machine...
Nutzt hier jemand Proxmox auf einem AMD64 System und kann mir sagen ob es möglich ist eine Virtuelle Maschine darauf mit ARM zu betreiben, oder ist dies rein technisch und logisch nicht möglich?
#proxmox #amd64 #arm #virtualisierung
I've spent a couple of hours now and am quite lost on trying to debug an amd64 assembly program under FreeBSD.
I ported it from Linux to OpenBSD. Then made the relevant adaptions to the system calls for FreeBSD, and when I try to run it it just exits.
But if I run it under truss(1) to verify the system calls it works fine(*1). I've not been able to figure out why it works under truss, but not when run directly.
I've reviewed the source, double checked all the system calls, and tried single stepping for about an hour (it's a vm for a tiny virtual cpu; it's not practical to single step indefinitely). I'm a little constrained since I'm not very familiar with lldb, and I can't get gdb to run at present (*2).
If anyone has any suggestions on what to try, I'd appreciate them.
(*1) there is an issue with the command line processing, but I bypassed that until the rest is working.
(*2) I updated my packages yesterday and installed gdb, but running it gives only "ld-elf.so.1: Undefined symbol "rl_eof_found" referenced from COPY relocation in /usr/local/bin/gdb"
(*3) a source snapshot w/makefile is at https://forth.works/temp/konilo-freebsd.tar.gz if anyone has time to take a look.
@marcan It's different market nieches or at least use-cases.
@fuchsiii won't do modern retro gaming and stuff on a #fanless #ARM64 #MacBookAir and in return that #MacBook just works as silent daily driver for office and productivity.
Only #TechIlliterates do absurd comparisons like racing 50cm³ two-stroke scooter made in GDR against a 15kW electric motorcycle.
And #AMD64's roots are as old as the #M541 engine of the former...
@B_Whitewind so if I gonna have to pay triple digits for a @Raspberry_Pi #Pi0 I might just get a shitty #amd64 - #SPBC in a #fanless case instead and enjoy native #USB #boot support...
It's really irritating...
https://www.youtube.com/watch?v=33hj9ImDyyI
@lunareclipse I mean I'd expect performance of that smartphone to be on-par with a @Raspberry_Pi #Pi3B with no added heatsink fitted to it...
So unless you want to make it a #clickfarm #bot #phone, it's less hassle to just get a somewhat recent #ThinClient and abuse that as a low-powered server.
I have one of them and at €0,62/kWh, a 2W SoC is the most reasonable option to use either @ubuntu / #UbuntuServer or any other #linux.
Plus, it's a regular-ass #amd64 system.
https://www.youtube.com/watch?v=XHtxzCWsDe4
Almost finished pass 1 of auto test framework for 4 #NetBSD10 BETA install architectures.
#i386
939 test programs:
10302 passed
0 failed test cases.
60 expected failed
656 skipped
#amd64
944:
10510 passed
12 failed test cases.
76 expected failed
559 skipped
#arm32 (pi0)
930:
9255 passed
21 failed test cases.
55 expected failed
662 skipped
#arm64 (pi4)
931:
9424 passed
1 failed test cases.
59 expected failed
689 skipped
@alilly it's called #amd64 because "#Intel64" / #EMT64 literally is based iff a #licensing deal with #AMD.
#ix64 refers to the #Itanium architecture that predictably and rightfully flopped!
https://www.youtube.com/watch?v=3oxrybkd7Mo
I am thinking if I should rename the 64-bit versions of @chapati #autoupdate.
Currently it's named #x86_64 but I think many people would understand #AMD64 better? What do you think?
Has anyone managed to run the #Listmonk mailing list app on a #RaspberryPi (which has an #arm64 chip)? The binary releases for linux are only for #amd64.
Or does anyone know of good alternatives for self-hosted mailing list that do work on the pi?
English translation of toot by Mathias Hasselmann
@taschenorakel
DE
Choosing the strings #amd64 and #arm64 as the name of two completely different architectures can only be thought up by someone who doesn't care about #dyslexia and similar limitations.
@thatguyoverthere@shitposter.club @thatguyoverthere@xmrposter.club tbh, my setup scripts mostly aim at automating manual installs.
Currently it only supports #Ubuntu 22.04 LTS and is only tested on #amd64, but since the script structure aims to do just a simple dialog selection screen and run one #bash script after the other, it's completely portable to any #distro that runs #bash if one adds matching apps and repos to it.
TIL you can force a platform in a Dockerfile via e.g.:
`FROM --platform=linux/amd64 debian:11-slim`
The same flag can be passed on the CLI, e.g.:
`docker run --platform=linux/amd64 -it debian:11-slim`
Needed that to get me out of a problem where the Terraform apt repo only includes amd64 sources (no ARM - so no Mac M1/M2).
But maybe that's just me, as I'm convinced #JavaScript was a fundamentally bad decision - only topped by worse decisions like #Windows and #ix86 / #amd64 if we go by @stman and others...
@lcruggeri @juliank @Raspberry_Pi
#ARM suffers by the fact that it's only being used in areas where #ix86 / #AMD64 are too expensive and/or inefficient...
Goal:
Untangle my computer use from any commercial/capitalist presets...
https://xkcd.com/743/
https://mastodon.social/@mcc/109683380376727036
For 2023 a #LibreComputer AML-S905X-CC (#LePotato) (2GB) is my personal base level hardware platform
Anything I develop/make has to be usable on the current base level hardware platform
https://toadwater.net/Permacomputing.html
"A useful frame of mind is thinking about your computer as offline first. You work with your computer and occasionally have network access. This usually means having data locally and occasionally synchronizing it with others."
#LocalFirst #OfflineFirst
#FrugalComputing #SustanableComputing #NetZeroComputing
Expect to run zsh, X11, openbox(?), Emacs, terminal, neomutt, newsboat, mastodon?, tor, i2p?
Test if Gnome is usable... ? xfce? CDE? is GnuStep still active? no desktop?
Get used to do #Email, #UseNet, #Gopher, #IRC, #RSS in #terminal or #Emacs
Use #Emacs and #TeΧ to write (dead tree) letters and missives (PDF?)
Maybe do more in #RawText?
Do callender things again on paper/pencil, #43folders, Whiteboard, etc.. physical things
Expand use of Gopher, Gemini, IndieWeb?
IM.. #XMPP via Dino? +OMEMO
Find a sustainable open source alternative for keybase? Or develop a distributed alternative using tor or i2p? Trust via FOAF?
Develop in #Pascal, #Lisp, #Ruby, #Haskell, #Scheme, #Forth :D
Keep repositories in #mercurial,
maybe source hut?
Find an #anonymous #pseudonymous hosting solution... shell account?... like rawtext.club, tildeverse.org, sdf.org .. ...my own?
Get a low power #amd64 box? bc too many FOSS projects are still not platform independent & x86 only v.v
Optimize to run many VMs?
Maybe can run #android in VM and run banking, insurance, and other apps there? Otherwise maybe get an used M1 mac and run the #iOS apps? perhaps some <100 euro android phones will do as well? otherwise get an iPad mini and use that for the next 5-6 yrs
Maybe set up a #FileServer (#NAS?) maybe even network boot? and perhaps even a #Postgresql database? Is having SQL DB available on the local network going to be useful? What about other databases?
#DigitalCampfires (#Tumblr? Blogs?)
https://maggieappleton.com/garden-history
https://tomcritchlow.com/2018/10/10/of-gardens-and-wikis/
https://wiki.c2.com/?WikiGardener
https://joelhooks.com/digital-garden
Bring #DigitalGardens to the "#TheDarkNet" and set up basecamp there, #tor onion services, a p2p chat/IM app, etc.. also explore #i2p and see how to simplify using it.
#DigitalHome?
(Tilde?)
Get back into #AI (but forget Artificial Intelligence, Artificial Innocence?) I want Augmented Intelligencekm
Explore as many other fun projects as well ... Who knows, I might like them and use them more often...
eg: #Guix #FreeBSD #OpenBSD #NetBSD #Minix #RiscV #Plan9 (#9Front) #RedoxOS #SmallTalk (#Pharo) #GoLang #RetroComputing #System7 #RiscOS #HaikuOS #Forth #Microcontrollers #68K #MIPS #PowerPC #HomeBrewComputer
——
Схороню шпаргалку...
x86-64 psABI Reference
x86-64 baseline All x86-64 CPUs CMOV, CMPXCHG8B, FPU, FXSR, MMX, FXSR, SCE, SSE, SSE2
x86-64-v2 circa 2009 Nehalem / Jaguar CMPXCHG16B, LAHF-SAHF, POPCNT, SSE3, SSE4.1, SSE4.2, SSSE3
x86-64-v3 circa 2015 Haswell / Excavator AVX, AVX2, BMI1, BMI2, F16C, FMA, LZCNT, MOVBE, XSAVE
Out of curiosity I've tried to build #zammad #docker image for #arm64 too in a #github action. Needs 3:30h to build 😮😬🤷♂️
Time might be reduced by building assets on #amd64 and putting it in a cache, which docker build can use, but will still be a lot longer than amd64 only, so I'm asking myself if it's even worth it? 🤔
