You're missing any AMD stuff, I can run a quantized deepseek r1 671B on 4 framework desktops, yet it's "insufficient" for 10 Nvidia gpus.
Readit Newsamstan commented on A GPU Calculator That Helps Calculate What GPU to Use calculator.inference.ai/... · Posted by u/chlobunnee
Deleted Comment
amstan commented on Show HN: I made a 3D printed VTOL drone tsungxu.com/p/i-made-a-3d... · Posted by u/tsungxu
It's an impressive achievement for an amateur.
He has separate motors for vertical and horizontal flights, which simplifies the design, but creates a rather bad inefficiency, the vertical motors create lots of drag during the horizontal flight.
Maybe it's not a big deal, I'm not sure. Making motors rotate would add weight for sure, thus reducing the range.
Shameless plug: https://aliptera.com/
Tilt-rotor on all 4 motors with an extra twist: the wing shape adds to the lift in vertical mode, so you can use smaller motors, so they're more efficient even in horizontal mode.
amstan commented on Why Archers Didn't Volley Fire acoup.blog/2025/05/02/col... · Posted by u/StefanBatory
YouTube suggested an old NileRed video to me today. He bought 100 lbs of titanium shot for a project. It came in a bag in a metal can.
The first two times he lifted the bag he said this isn’t that heavy, maybe he got defrauded, so he got a scale and checked. But by the time he tried to lift it off the scale he was struggling, and getting it back into the metal can was serious work.
Stamina separates the pro from the amateur, but fatigue comes for all of us.
> Traditionally, programs will place their code into non-writeable memory, and store variable data in memory that is writeable but not executable. And that's definitely the safer way to do things, but we can't be bothered with all that.
Woah, I have a feeling this does something even more. If the program modifies its own instructions, the kernel will probably save those modifications in the file too.
amstan commented on The chroot Technique – a Swiss army multitool for Linux systems livesys.se/posts/the-chro... · Posted by u/mariuz
> sudo mkdir /rescue/boot
> sudo mount /dev/nvme0n1p3 /rescue/boot
This is a little extra. What you can generally do is immediatelly after chroot just run 'mount -a' to mount everything from the chroot's fstab. The empty `/boot` probably already exists.
amstan commented on The chroot Technique – a Swiss army multitool for Linux systems livesys.se/posts/the-chro... · Posted by u/mariuz
Is there already a wrapper utility to automate all of this process laid out in the article?
There is!
arch-chroot [1], despite its name pretty much does all the `mount -t proc` stuff the post says. It's also available on other distros like debian [2]. I have used it in the past to chroot into fedora as well.
[1] https://man.archlinux.org/man/arch-chroot.8 [2] https://packages.debian.org/arch-install-scripts
On linux, the gpu can go up to 110 GB.
It can go higher actually, just that when I setup my test devices I had a "ought to be enough for everyone" moment when typing `options amdgpu gttsize=110000`. I guess this number spread too far, heh.
See also:
[1] https://en.wikipedia.org/wiki/Graphics_address_remapping_tab...
[2] https://www.kernel.org/doc/html/v4.19/gpu/amdgpu.html#:~:tex...
Deleted Comment
The BIOS allows pre-allocating 96 GB max, and I'm not sure if that's the maximum for Windows, but under Linux, you can use `amdttm.pages_limit` and `amdttm.page_pool_size` [1]
[1] https://www.jeffgeerling.com/blog/2025/increasing-vram-alloc...