Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)DA
Posts
1
Comments
271
Joined
2 yr. ago

  • You shouldn't need to download any graphics drivers, Ubuntu (and pretty much every other distribution) ships with the open-source AMD driver stack by default, which are significantly better than and less hassle than the proprietary drivers for pretty much all purposes. If you're getting video out it's almost certainly already using the internal GPU, but if you're unsure you can open a terminal and run sudo apt install mesa-utils and then glxinfo -B to double-check what is being used for rendering.

  • Thinking of a modern GPU as a "graphics processor" is a bit misleading. GPUs haven't been purely graphics processors for 15 years or so, they've morphed into general-purpose parallel compute processors with a few graphics-specific things implemented in hardware as separate components (e.g. rasterization, fragment blending).

    Those hardware stages generally take so little time compared to the rest of the graphics pipeline that it normally makes the most sense to have far more silicon dedicated to general-purpose shader cores than the fixed-function graphics hardware. A single rasterizer unit might be able to produce up to 16 shader threads worth of fragments per cycle, so even if your fragment shader is very simple and only takes 8 cycles per pixel, you can keep 8x16 cores busy with only one rasterizer in this example.

    The result is that GPUs are basically just a chip packed full of a staggering number of fully programmable floating-point and integer ALUs, with only a little bit of fixed hardware dedicated to graphics squeezed in between. Any application which doesn't need the graphics stuff and just wants to run a program on thousands of threads in parallel can simply ignore the graphics hardware and stick to the programmable shader cores, and still be able to leverage nearly all of the chip's computational power. Heck, a growing number of games are bypassing the fixed-function hardware for some parts of rendering (e.g. compositing with compute shaders instead of drawing screen-sized rectangles, etc.) because it's faster to simply start a bunch of threads and read+write a bunch of pixels in software.

  • I follow a huge number of artists on Bandcamp which I mostly discovered through Chiptunes=WIN (which unfortunately seems to have erased itself from the internet), and the occasional collab album is enough to keep gradually discovering new artists.

  • KDE user here, I still use X11 to play old Minecraft versions. LWJGL2 uses xrandr to read (and sometimes modify? wtf) display configurations on Linux, and the last few times I've tried it on Wayland it kept screwing the whole desktop up.

  • It takes like half a second on my Fairphone 3, and the CPU in this thing is absolute dogshit. I also doubt that the power consumption is particularly significant compared to the overhead of parsing, executing and JIT-compiling the 14MiB of JavaScript frameworks on the actual website.

  • True, but there are also some legitimate applications for 100s of gigabytes of RAM. I've been working on a thing for processing historical OpenStreetMap data and it is quite a few orders of magnitude faster to fill the database by loading the 300GiB or so of point data into memory, sorting it in memory, and then partitioning and compressing it into pre-sorted table files which RocksDB can ingest directly without additional processing. I had to get 24x16GiB of RAM in order to do that, though.

  • In my experience, nouveau is painfully slow and crashes constantly to the point of being virtually unusable for anything. The developers agree, as in the last couple months nouveau has been phased out of Mesa entirely. More recent Mesa versions now implement OpenGL on Nvidia using Zink on NVK, and the result is quite a bit faster and FAR more stable.

    If your distribution currently still ships a Mesa version which uses nouveau, I would personally recommend you just stick with the Intel graphics for now.

  • Based on that plus the various other mistakes, my guess is that OP's native language isn't English, but probably one of the many languages which uses masculine pronouns as gender-neutral, and they're just doing a literal translation from their native language.

  • Aside from checking the kernel log (sudo dmesg) and system log (sudo journalctl -xe) for any interesting messages, I might suggest simply watching for any processes which are abnormally high while the system is running slow. My initial approach would be to use htop (disable "Hide Kernel Threads" and enable "Detailed CPU Time"), and seeing which processes, if any, are eating up your CPU time. The colored core utilization bars at the top show how much CPU time is being spent on what: gray for disk wait, red for kernel, green for regular user process, etc. That information will be a good starting point.

  • I mean, there are plenty of wealthy immigrants here, but I would say there are probably more immigrant families from regular or (relatively) poor families around. Like, people with a regular income who are working a regular job, not your average finance expat from an English-speaking country on an all-expenses-paid expat package plus a neat half million bucks per year salary on top.

    That said, the non-expat immigrants I know are overwhelmingly from eastern European countries, so I wouldn't be surprised if the acceptance policy is biased against non-Europeans. You don't see many average working-class Americans around here unless they married a Swiss person.

  • Linux @lemmy.ml

    bcachefs is now in linux-next!