Have you enabled Southern Islands support as a kernel parameter? Your generation of GPU was originally supported on radeon
, so you need to explicitly enable SI (Southern Islands) support to use amdgpu
.
See ArchWiki for more information
Have you enabled Southern Islands support as a kernel parameter? Your generation of GPU was originally supported on radeon
, so you need to explicitly enable SI (Southern Islands) support to use amdgpu
.
See ArchWiki for more information
Maybe the LLMs they prompted didn't know about the built-in SSH support, hence still recommends PuTTY? 🤔
Yes, so R&D and finalizing the model weight is done on NVIDIA GPUs (I guess you need an excessive amount of VRAM).
Inference is probably gonna be offloaded to consumers in the end where the NPU is taking care of the inference cost (See Apple, Qualcomm etc)
Not the best on AI/LLM terms, but I assume that training the models was done on Nvidia, while inference (using the model/getting the data from the model) is done on Huawei chips
To add: Training the model is a huge single-cost expense, while inference is a continuous expense.
The whole downside is that not everyone is a data horder with space for videos
Some media players allows for streaming directly using yt-dlp, e.g.;
mpv <youtube url>
Will use yt-dlp if installed
Sounds like you might just be max'ing out the capacity of the coax cable as well (depending on length/signal integrity). E.g. ITGoat (not sure how trustworthy this webpage is, just an example) lists 1 Gbps as the maximum for coax while you would typically expecting less than that, again depending on your situation (cable length, material, etc)
What's your situation into the wall? Depending on country/ISP/regulations they might give you up to 1000 Mbps under the assumption that it's a single line going to a single user, however quite often that line is shared with potentially a lot of different customers.
Some countries allows you to buy packages where you have a standalone line going to your wall, however at an additional cost
If all nodes are connected through ethernet to each other (or at least one common node) you could go for OpenWRT's 'Dumb AP' setup as well
Edit: Already mentioned here; https://feditown.com/comment/1980836
Maintainer has been absent for some time so kernel v6.11 and v6.12 isn't supported OOTB, to get it to work with kernel v6.11 you need to pull the fix from: !48
People usually use/recommend LACT for undervolting/overlocking on Linux