ROCm
us.zoom.Zoom | ROCm | |
---|---|---|
31 | 198 | |
34 | 3,637 | |
- | - | |
7.1 | 0.0 | |
10 days ago | 5 months ago | |
Shell | Python | |
- | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
us.zoom.Zoom
-
Use a custom data folder on Flatpak apps
For example, let's say we want a separate instance of Zoom (Zoom on Flathub) to run along the default one.
-
btw
It seems to divert the discussion to something that doesn't make too much sense. X and Wayland are two different things by design, this probonopd sounds extraordinarily salty that moving an application under a new server breaks some things, making some applications entirely useless, but I say, that is to be expected. Saying that Wayland breaks stuff by design, as if that was their only objective is just petty, of course it's a pity that those devs have thrown in the towel, but let's not pretend like theirs were the only options, e.g. screen recording works perfectly fine with OBS, at least it has done so on my machines with AMD/Intel GPUs; Jitsi works now; Zoom screensharing being GNOME only is Zoom devs being dicks that can't be arsed to support standards, the community came in to work around it and also I don't know how they could bring up a proprietary application that has not made the Flatpak package themselves as an example, the whole thing is a community effort there apparently; etc. etc. (I'm not going to debunk all the others that are invalid, the internet is there for everyone)
-
KDE is starting to treat X11 users as second-class citizens
Can you be specific about the problems with X11? I've been using X11 for decades and it's been ROCK SOLID. And that is exactly what you want from something so essential. Wayland feels like an expensive boondogle, frankly. Wayland breaks everything and only provides 20% the functionality that X11. It also forces application and DE developers to implement special tools and solutions for wayland which have always been provided as a common interface by X11, like screenshots/ recording and screen sharing, e.g. https://github.com/flathub/us.zoom.Zoom/issues/22
-
Zoom on Ubuntu-based Linux
For college and therapy, I've had to use Zoom. I've been using the zoom flatpak, as I try and use flatpak for any proprietary software. That being said, it is not officially supported (by zoom), and also doesn't listen to Pop!_OS's tiling window manager. Certainly, I'm not the only one who has questioned which client to use, but I'm curious what y'all think. I like flatpak because I can trust that, worst case scenario, the proprietary software (read: Spyware) only has access to a limited amount of my system. But it'd also be nice to, ya know, use the tiling feature.
-
Consistent crashes joining meetings
I've gathered a coredump and a stack trace, which might be useful.
- Zoom crashes when joining a meeting
-
A Problem with Zoom and the Solution
You can get it as a flatpak too which should (presumably) take care of any dependencies automatically. :)
-
Can it run Zoom?
Here you go: https://flathub.org/apps/details/us.zoom.Zoom
-
Will this be fixed with the next linux 5.18 kernel? I'm only getting 2 hours of battery life while getting 5-6 on Windows 11...
Check this out https://github.com/flathub/us.zoom.Zoom/blob/master/zoom.sh
-
Screen sharing on Zoom (Wayland & Fedora 36)
Link to the github issue for the flatpak
ROCm
-
AMD May Get Across the CUDA Moat
Yep, did exactly that. IMO he threw a fit, even though AMD was working with him squashing bugs. https://github.com/RadeonOpenCompute/ROCm/issues/2198#issuec...
- ROCm 5.7.0 Release
-
ROCm Is AMD's #1 Priority, Executive Says
Ok, I wonder what's wrong. maybe it's this? https://stackoverflow.com/questions/4959621/error-1001-in-cl...
Nope. Anything about this on the arch wiki? Nope
This bug report[2] from 2021? Maybe I need to update my groups.
[2]: https://github.com/RadeonOpenCompute/ROCm/issues/1411
$ ls -la /dev/kfd
-
Simplifying GPU Application Development with HMM
HMM is, I believe, a Linux feature.
AMD added HMM support in ROCm 5.0 according to this: https://github.com/RadeonOpenCompute/ROCm/blob/develop/CHANG...
-
AMD Ryzen APU turned into a 16GB VRAM GPU and it can run Stable Diffusion
Woot AMD now supports APU? I sold my notebook as i hit a wall when trying rocm [1] Is there a list oft Wirkung apu's ?
[1] https://github.com/RadeonOpenCompute/ROCm/issues/1587
-
Nvidia's CUDA Monopoly
Last I heard he's abandoned working with AMD products.
https://github.com/RadeonOpenCompute/ROCm/issues/2198#issuec...
-
Nvidia H100 GPUs: Supply and Demand
They're talking about the meltdown he had on stream [1] (in front of the mentioned pirate flag), that ended with him saying he'd stop using AMD hardware [2]. He recanted this two weeks after talking with AMD [3].
Maybe he'll succeed, but this definitely doesn't scream stability to me. I'd be wary of investing money into his ventures (but then I'm not a VC, so what do I know).
[1] https://www.youtube.com/watch?v=Mr0rWJhv9jU
[2] https://github.com/RadeonOpenCompute/ROCm/issues/2198#issuec...
[3] https://twitter.com/realGeorgeHotz/status/166980346408248934...
-
Open or closed source Nvidia driver?
As for rocm support on consumer devices, AMD wont even clarify what devices are supported. https://github.com/RadeonOpenCompute/ROCm/pull/1738
-
Why Nvidia Keeps Winning: The Rise of an AI Giant
He flamed out, then is back after Lisa Su called him (lmao)
https://geohot.github.io/blog/jekyll/update/2023/05/24/the-t...
https://www.youtube.com/watch?v=Mr0rWJhv9jU
https://github.com/RadeonOpenCompute/ROCm/issues/2198#issuec...
https://geohot.github.io/blog/jekyll/update/2023/06/07/a-div...
On a personal level that youtube doesn't make him come off looking that good... like people are trying to get patches to him and generally soothe him/damage control and he's just being a bit of a manchild. And it sounds like that's the general course of events around a lot of his "efforts".
On the other hand he's not wrong either, having this private build inside AMD and not even validating official, supported configurations for the officially supported non-private builds they show to the world isn't a good look, and that's just the very start of the problems around ROCm. AMD's OpenCL runtime was never stable or good either and every experience I've heard with it was "we spent so much time fighting AMD-specific runtime bugs and specs jank that what we ended up with was essentially vendor-proprietary anyway".
On the other other hand, it sounds like AMD know this is a mess and has some big stability/maturity improvements in the pipeline. It seems clear from some of the smoke coming out of the building that they're cooking on more general ROCm support for RDNA cards, and generally working to patch the maturity and stability issues he's talking about. I hate the "wait for drivers/new software release bro it's gonna fix everything" that surrounds AMD products but in this case I'm at least hopeful they seem to understand the problem, even if it's completely absurdly late.
Some of what he was viewing as "the process happening in secret" was likely people doing rush patches on the latest build to accommodate him, and he comes off as berating them over it. Again, like, that stream just comes off as "mercurial manchild" not coding genius. And everyone knew the driver situation is bad, that's why there's notionally alpha for him to realize here in the first place. He's bumping into moneymakers, and getting mad about it.
-
Disable "SetTensor/CopyTensor" console logging.
I tried to train another model using InceptionResNetV2 and the same issues happens. Also, this happens even using the model.predict() method if using the GPU. Probably this is an issue related to the AMD Radeon RX 6700 XT or some mine misconfiguration. System Inormation: ArchLinux 6.1.32-1-lts - AMD Radeon RX 6700 XT - gfx1031 Opened issues: - https://github.com/RadeonOpenCompute/ROCm/issues/2250 - https://github.com/ROCmSoftwarePlatform/tensorflow-upstream/issues/2125
What are some alternatives?
flathub - Issue tracker and new submissions
tensorflow-directml - Fork of TensorFlow accelerated by DirectML
nix-gui - Use NixOS Without Coding
Pytorch - Tensors and Dynamic neural networks in Python with strong GPU acceleration
xdg-desktop-portal - Desktop integration portal
rocm-arch - A collection of Arch Linux PKGBUILDS for the ROCm platform
xdotool - fake keyboard/mouse input, window management, and more
oneAPI.jl - Julia support for the oneAPI programming toolkit.
flatpak-cve-checker
SHARK - SHARK - High Performance Machine Learning Distribution
xdg-desktop-portal-gtk - Gtk implementation of xdg-desktop-portal
llama.cpp - LLM inference in C/C++