Something like for-jay-yo.
From https://forgejo.org/faq/ :
Forgejo (pronounced /forˈd͡ʒe.jo/) is inspired by forĝejo, the Esperanto word for forge.
Something like for-jay-yo.
From https://forgejo.org/faq/ :
Forgejo (pronounced /forˈd͡ʒe.jo/) is inspired by forĝejo, the Esperanto word for forge.
I recently upgraded to a 7900 XTX on Debian stable, as well. I’m running the newest kernel from Debian’s backports repo (6.6, I think), and I didn’t have that same problem.
I did have other problems with OpenCL, though. I made a thread about this and solved it with some trouble. Check my post history if you’re interested. I hope it helps. I can take a closer look at my now-working system for comparison if you have further issues.
IT WORKS NOW! I will need time to run additional tests, but the gist of my solution was:
Backport llvm-18 from sid following the guide you linked at https://wiki.debian.org/SimpleBackportCreation
After compiling and installing all those deb files, I then installed the “jammy” version of amdgpu-install_6.0.60002-1.deb from https://www.amd.com/en/support/linux-drivers
Downloaded the latest kernel sources from https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git, and simply copied all the files from its lib/firmware/amdgpu folder into my system’s /lib/firmware/amdgpu. Got that idea from https://discussion.fedoraproject.org/t/amdgpu-doesnt-seem-to-function-with-navi-31-rx-7900-xtx/72647
sudo update-initramfs -u && sudo reboot
I’m not totally sure it step 3 was sane or necessary. Perhaps the missing piece before that was that I needed to manually update my initramfs? I’ve tried like a million things at this point and my system is dirty, so I will probably roll back to my snapshot from before all of this and attempt to re-do it with the minimal steps, when I have time.
Anyway, I was able to run a real-world OpenCL benchmark, and it’s crazy-fast compared to my old GTX 1080. Actually a bigger difference than I expected. Like 6x.
THANKS FOR THE HELP!
Thanks for the links! I’ve never attempted making my own backport before. I’ll give it a shot. I might also try re-upgrading to sid to see if I can wrangle it a little differently. Maybe I don’t actually need mesa-opencl-ics if I’m installing AMD’s installer afterwards anyway. At least, I found something to that effect in a different but similar discussion.
Update: I upgraded to Sid. Unfortunately, mesa-opencl-icd depends on libclc-17, which uninstalls -18. So I can’t get OpenCL working while the correct libclc is installed.
No idea where to go from here. I’ll probably restore my Bookworm snapshot, since I don’t want to be on Sid if it doesn’t solve this problem.
Update: Running amdgpu-install did not provide those files. There were a few errors regarding vulkan packages when I attempted, I guess because it’s assuming Ubuntu repos. Trying with just opencl and not vulkan succeded, but still clinfo
reported the missing files.
I don’t think I can get this working without a whole newer llvm.
Ah, somehow I didn’t see 18 there and only looked at 17. Thanks!
I tried pulling just the one package from the sid repo, but that created a cascade of dependencies, including all of llvm. I was able to get those files installed but not able to get clinfo to succeed. I also tried installing llvm-19 from the repo at https://apt.llvm.org/, with similar results. clinfo didn’t throw the fatal errors anymore, but it didn’t work, either. It still reported Number of devices 0
and OpenCL-based tools crashed anyway. Not with the same error, but with something generic about not finding a device or possibly having corrupt drivers.
Should I bite the bullet and do a full ugprade to sid, or is there some way to this more precisely that won’t muck up Bookworm?
Can you explain more about your workflow? Do the Nix packages have their own isolated dependency resolution? How does it work when Debian packages depend on a library you get from Nix, or vice-versa?
Thanks, that’s good advice. There are lower-numbered gfx* files in there. 900, 902, 904, 906. No 1030 or 1100. Same after reinstalling.
Looks like these files are actually provided by the libclc-15
package. libclc-16 has the same set of files. Even libclc-17 from sid has the same files. So I guess upgrading to testing/unstable wouldn’t help.
apt-file search gfx1100-amdgcn-mesa-mesa3d.bc
yields no results, so I guess I need to go outside of the Debian repos. I’ll try the AMD package tonight.
Not sure if you’re referring to the graphics or to the shitty bench design. If the latter…it’s a real thing. :(
They’re called “leaning benches” or “lean bars”. This bench design is sort of “futuristic” in the sense that adoption has only recently started taking off around the world. They are a user-hostile design made specifically to prevent people (specifically homeless people) from lying down, sleeping, or otherwise, y’know, using it as a goddamn bench. Because removing the ability for anyone to sit down is apparently, in the eyes of authorities, a small price to pay to make homeless people’s lives that much harder.
The Wikipedia article for “Leaning bench” redirects to hostile architecture, where you can read more about this and similar efforts, if you are in the mood to be enraged at the sheer malice of bureaucrats.
I’ve seen them in several cities across America. NYC starting rolling them out within the past decade and you’ll see them in any recently renovated station. See https://www.nydailynews.com/2017/09/11/subway-riders-slam-brooklyn-stations-new-leaning-bars-as-incredibly-unwelcoming/ (scroll through the image slideshow to see the new).
Not sure if the image embed will work here but I’ll try:
This is correct, albeit not universal.
KDE has a predefined schedule for “release candidates”, which includes RC2 later this month. So “RC1” is clearly not going to be the final version. See: https://community.kde.org/Schedules/February_2024_MegaRelease
This is at least somewhat common. In fact, it’s the same way the Linux kernel development cycle works. They have 7 release candidates, released on a weekly basis between the beta period and final release. See: https://www.kernel.org/category/releases.html
In the world of proprietary corporate software, I more often see release candidates presented as potentially final; i.e. literal candidates for release. The idea of scheduling multiple RCs in advance doesn’t make sense in that context, since each one is intended to be the last (with fingers crossed).
It’s kind of splitting hairs, honestly, and I suspect this distinction has more to do with the transparency of open-source projects than anything else. Apple, for example, may indeed have a schedule for multiple macOS RCs right from the start and simply choose not to share that information. They present every “release candidate” as being potentially the final version (and indeed, the final version will be the same build as the final RC), but in practice there’s always more than one. Also, Apple is hardly an ideal example to follow, since they’ve apparently never even heard of semantic version numbering. Major compatibility-breaking changes are often introduced in minor point releases. It’s infuriating. But I digress.
All the time. Not always by choice!
A lot of my work involves writing scripts for systems I do not control, using as light a touch as is realistically possible. I know for a fact Python is NOT installed on many of my targets, and it doesn’t make sense to push out a whole Python environment of my own for something as trivial as string manipulation.
awk is super powerful, but IMHO not powerful enough to justify its complexity, relative to other languages. If you have the freedom to use Python, then I suggest using that for anything advanced. Python skills will serve you better in a wider variety of use cases.
Thank you for saving me the trouble of investigating this as an option.
No reason to tolerate proprietary licenses when there are so many viable FLOSS solutions out there.
I doubt any billionaires have that much money “sitting in a bank”.
Most wealth is non-liquid. For example, if you found a company that becomes massive, and you maintain a controlling share, then you could be a billionaire on paper while having no real money to spend – the only way to turn that into “real” money would be to sell shares in the company, and thus lose control of it. If the company is doing good work, it could be better to retain control and act through the company, by ensuring that it pays employees good wages to do good work for the benefit of society. This is not completely incompatible with profit in theory, though in practice…yeah. I’m not sure if there are any such billionaires in the world today.
The real problem is more fundamental to the economy, in that it fairly consistently rewards bad behavior.
Larry Page basically became a billionaire overnight when Google went public. I don’t recall Page or Google doing anything especially evil or exploitative before that, though their success was certainly built in an unsustainable economic bubble.
If Amazon didn’t treat its employees like shit and poison the entire economy, then Bezos could probably still be a billionaire and I wouldn’t necessarily hold that against him.
Steve Wozniak, co-founder of Apple.
I don’t think he was ever a billionaire, though he’s certainly done quite well for himself. Since leaving Apple, he has founded several new companies and projects, focusing a lot on education and philanthropy. He was also involved in founding the EFF.
He’s an engineer first and foremost, and several of his projects never achieved mainstream success, partly for being, IMHO, ahead of their time – for example, a programmable universal remote in the 80s, and a GPS-based item tracker in the early 2000s.
As far as I know, he has never been involved in any notable scandals.
Can’t be arsed.
It means you don’t care to put in the effort required.
I used to run Tumbleweed with KDE on my Nvidia system. I found the rolling release structure of Tumbleweed to cause extra work for me, because kernel updates came frequently and occasionally broke the Nvidia drivers. As a workaround, I ended up pinning my kernel to an old version.
Nvidia drivers have been at least a little troublesome on every distro I’ve used, particularly with the additional CUDA libraries.
One nice thing about Suse is that it uses BTRFS by default, and you can use snapper to revert your whole system if something goes wrong. So if Nvidia shits the the bed after an update, it’s easy to roll back. Most distros default to ext4 and do not have snapshot support by default, which feels like living in the stone age to me after using Suse and BTRFS.
Of course you CAN set up BTRFS and snapshots in any distro, but that’s a lot to ask for a beginner with Linux. I strongly recommend choosing a distro that does that for you, like Suse.
Carbon wasn’t that prevalent 10 years ago. 15, maybe. 20, definitely.
10 years ago, Carbon was already officially deprecated, and it had clearly been a second-class citizen for years before that. Most apps were already using Cocoa at that point.
Debian Stable is an excellent replacement for Ubuntu LTS.
Mint is an excellent replacement for mainline Ubuntu.
btrfs’s RAID features are not production-ready, and at this point I doubt they ever will be. See:
https://en.wikipedia.org/wiki/Btrfs#Implemented_but_not_recommended_for_production_use
https://wiki.archlinux.org/title/Btrfs
https://www.phoronix.com/news/Btrfs-Warning-RAID5-RAID6
ZFS is definitely more robust.