edinbruh

joined 2 years ago
[–] edinbruh@feddit.it 1 points 2 hours ago* (last edited 2 hours ago)

If you read the documentation you would know that:

  • Drivers have a part in the kernel and some others outside the kernel
  • The part inside the kernel is called amdgpu most likely already installed and you don't need to do anything
  • For the parts outside you can use either amd's (the ones you tried to install) or the community made ones (mesa)
  • Amd's own stuff is better only in raytracing and worse in everything else, so unless you are doing raytracing you should avoid it and use mesa
  • Mesa is likely already installed and you could have just done nothing, if not look up how to install that
  • If you still want amd's own stuff, or if you want rocm, you should look that up on mint documentation and forum

Footnote: it is possible to install both mesa and amd's software, and set up some games to use one and some and everything else to use the other, this allows you to always use mesa, except for those games with raytracing, but seeing that you are already overwhelmed I would avoid that for now, and maybe try if when you are more experienced.

[–] edinbruh@feddit.it 1 points 2 hours ago (1 children)

You should not ask chatgpt for these things, you should look for documentation and forums. A good place to understand how things work is the arch wiki, even if you don't use arch, most of the stuff is valid for other distros... except instructions on installing packages, that you should look in your distro's specific documentation and forums.

[–] edinbruh@feddit.it 6 points 2 weeks ago (1 children)

What is non-plain-tezxt code?

[–] edinbruh@feddit.it 5 points 2 weeks ago

For esolang nerds. They enjoy the existence of the language, not its usage

[–] edinbruh@feddit.it 5 points 2 weeks ago

I think Hellwig understands everything very well, he just wants things done his way, for whatever (possibly valid) reason he might have.

Literaly from your quotation: "I assume that we’re good with maintaining the DMA Rust abstractions separately [...] No, I'm not" He understands the abstractions would not be in his domain and maintained by someone else, he does not want abstraction at all.

Maybe you are not familiar with the proposal but these "separate rust abstractions" would be a separate module that depends on DMA mapping as a client and deals with cross-language issues, rust drivers would then be clients of this module, it would not be part of the DMA mapping module, it would not be mixed with the DMA code. But Hellwig doesn't want an abstraction module at all, Instead he want's you to "do that [the abstraction] in your driver so that you have to do it [maintain a cross-language codebase]".

Please notice that the abstraction module would not add any more burden on him than the drivers themselves would, because as of now C code is allowed to break Rust code. It would only remove burden from maintainers of Rust drivers, and even if it weren't it would be easier to fix just the abstraction instead of every driver.

He also refuses to have other people maintain the abstraction, this too for whatever reason, which accredits his request to not add abstraction he would have to maintain. If the abstraction were part of the core dma mapping code, I think it would be a reasonable request, but it wouldn't be.

Now, we do not know the reason why he opposes it so much. From his words it looks like he doesn't want Linux to be a cross-language codebase, which would be a valid reason in itself, but dealing with abstractions in drivers instead of a module doesn't make it any less cross-language, unless the drivers are out of tree, which they wouldn't be. Some people (e.g. Hector Martin) think that he's hoping the Rust for Linux project to fail altogether, and fore rust code to be removed from the kernel, and this obstruction would partake in that. I do not think it is that drastic, I think he just fears that those abstraction would eventually become part of what he has to maintain, and no amount of reassurance or new maintainers would change his mind.

I also don't think Martin's brigading is anything productive, and I hope that doesn't become the reason that rust code gets obstructed from being merged into the kernel, but it sure does focus the attention on these matters.

[–] edinbruh@feddit.it 21 points 2 weeks ago* (last edited 2 weeks ago) (4 children)

What they are asking is not to change the c code to suit rust, but to leave the C code as is, and have a single Rust-written wrapper that links into the C DMA code so that other Rust drivers can link into the wrapper. Additionally, said wrapper is not to be maintained by Hellwig, but by the maintainers of the drivers that will use the wrapper, so without overhead for Hellwig.

He is not asking to not make his work harder, he's explicitly asking to make it harder to write rust drivers that use DMA.

[–] edinbruh@feddit.it 6 points 2 weeks ago (1 children)

Ham is made from the thighs of the pig

[–] edinbruh@feddit.it 4 points 2 weeks ago* (last edited 2 weeks ago)

I think it's origin is actually the same as Shrek and Fiona. In the book "Shrek!" there is a donkey that accompanies Shrek to a castle where he meets a princess uglier than him.

Source: Wikipedia

[–] edinbruh@feddit.it 9 points 4 weeks ago

This meme is so old it uses jQuery

[–] edinbruh@feddit.it 2 points 1 month ago

What is this referring to?

[–] edinbruh@feddit.it 7 points 1 month ago* (last edited 1 month ago) (2 children)

The Nazis got it from the fascists who got it from a screenplay from D'Annunzio that Mussolini liked. D'Annunzio pulled it out of his ass, Romans didn't salute like that.

 
 

I'm using sunshine for remote gaming on my Linux PC. Because I use Wayland and don't have an Nvidia I use kmsgrab for capture (under the hood sunshine uses ffmpeg).

I have noticed that I can enter tty and kmsgrab will capture it as well. If it just captured after logging in my user I wouldn't be surprised, but it also captures the login screen.

I autostart it at login using my systemd user configuration (not systemwide) so it should just have my user's permission level. I get the same results if I put it in KDE's autostart section, so it's not a systemd thing.

Why does that work? Shouldn't you need special privileges to capture everything?

The installation instructions tells you to do sudo setcap -r $(readlink -f $(which sunshine)) is this the reason why it works? What does the command do exactly?

 

SOTTR can now run in proton-experimental (it used to crash due to a missing vulkan feature), but how does it compare to the native version?

Normally I would just use the native version, but got the game from epic, which doesn't provide the native build. So if I wanted to run native I would have to acquire the game from other sources (keep in mind that I own the game on epic), which is less than ideal. But I wouldn't do it if there's no advantage.

 

SOTTR can now run in proton-experimental (it used to crash due to a missing vulkan feature), but how does it compare to the native version?

Normally I would just use the native version, but got the game from epic, which doesn't provide the native build. So if I wanted to run native I would have to acquire the game from other sources (keep in mind that I own the game on epic), which is less than ideal. But I wouldn't do it if there's no advantage.

 

Do you have an AMD aura GPU? Do you also use Linux? There's this this driver that needs to be tested.

It allows you to control the lighting of the GPU using programs like openRGB.

I wrote that PR that should make it work for more GPUs, but I only have an RX 480 so I can only test that one. It would be useful to try it on a Vega gpu.

If you have an rDNA 1/2/3 GPU, it most likely won't work, but without the card there's nothing I can do.

On a side note, if you are interested in maintaining the driver it would be great.

 

Detailed issue

Basically Kwin and other programs (simple xdg-desktop-portal or even gimp) crash and they bork the entire screen with no recovery other than rebooting. When the program that crash is Kwin it's particularly bad because it happens at login.

 

This is a short appreciation/user experience story. Tl;Dr I'm enjoying my time on linux

I have been using Linux for a while (gnome for a year with an Intel UHD gpu, and KDE for a couple of months on a recent AMD gpu), and till now there was no brightness slider. Moreover, I have used the same display with windows for several years and there was no slider as well.

As far as I know (I looked up online some years ago, but this info is sometimes hard to find) my display supports DDC/CI but doesn't expose brightness (haven't actually tried).

For some reason, about a week ago a brightness slider appeared on KDE but it didn't do anything. Yesterday while updating some unrelated stuff I noticed the slider again and moved it for shit and giggles, and the brightness actually changed...

I have several questions... and I don't even know which piece of software is responsible for this... but thanks

I have been using Linux on and off for several years, often alongside windows, but I have entirely switched to it (almost, I still have a windows PC that I use once in a while) about 16 months ago. I have to say that Linux does take a lot more effort in getting some things to work, but when everything goes smoothly it's sooo good, and improves every month.

In the span of a year my desktop experience has only got better. But the shock was when I booted up an Ubuntu 16.04 cd I had lying around to fix grub on a dual boot machine and it was barely usable. Now instead it's almost "plug and play". Plus Nvidia cards are getting more and more usable with every update, explicit sync is almost merged, and prime works fine already.

There won't be a year of the Linux desktop anytime soon (there's still too much that needs improvement), but the next years will definitely be exciting.

P.s.: does any of you know why display brightness works now?

 

I have a Nvidia gpu with the latest proprietary drivers, and I'm trying to play BAA from egs (using heroic) but physX doesn't work.

I have run the automatic winetricks (I don't know which ones because heroic doesn't tell) and I have tryed this also the environment variable PROTON_ENABLE_NVAPI=1, but it still doesn't run on the gpu, even if the message "no hardware physx detected" stopped showing.

And if hardware acceleration doesn't work, I get the same behaviour on arkham city, but the game runs at double the framerate, even if using the cpu. Would it be possible to get asylum to run like city? I have tried swapping some dlls but nothing.

 

I have a Nvidia gpu with the latest proprietary drivers, and I'm trying to play BAA from egs (using heroic) but physX doesn't work.

I have run the automatic winetricks (I don't know which ones because heroic doesn't tell) and I have tryed this also the environment variable PROTON_ENABLE_NVAPI=1, but it still doesn't run on the gpu, even if the message "no hardware physx detected" stopped showing.

And if hardware acceleration doesn't work, I get the same behaviour on arkham city, but the game runs at double the framerate, even if using the cpu. Would it be possible to get asylum to run like city? I have tried swapping some dlls but nothing.

 

Can I get a better Nvidia+Wayland experience by using prime and connecting the display to an AMD iGPU? I saw that in the last year Nvidia Prime had some improvements, do they make it feasible?

I can't just try it because I have yet to buy said AMD iGPU. And I'd like to know it before buying

 

I don't like my ssh keys being stored in plain sight, I also don't like having to type a passphrase to use them.

On windows, once you run ssh-add, the key is stored in a secure way and managed by some kind of session manager (source), at that point you can delete the key file and go about your life knowing that the key is safe and you won't need to type a password again.

I would like something similar on linux, like storing the key via libsecret as you do with git, so that you can access your servers without having a key in plain text.

I think it's possible to generate a key with a passphrase and have gnome-keyring or kwallet remember the passphrase, but it would be nicer to just securely store the key itself.

Can that be done?

 

I have a projector that needs limited rgb range, but for some reason (maybe a faulty hdmi-vga dongle) the intel driver selects full range. I want to force the limited rgb range when I plug the projector, but I need it set to auto normally, because my usual monitor needs full range.

I read this guide that explains how to use proptest to switch mode when in wayland. The problem is that running the command when the gnome session is open doesn't work and returns an error 243 (I can't find it in errno.h, but google says its EACCESS). The guide deals with this by launching the command with systemd before gdm starts, but as I said, I only want to force the limited range when using the projector.

I noticed that I can switch to a tty, set the range, and switch back to gnome while everything is still running and it works, which is my current "workaround", and I'd like to automate it. So I thought that there's a moment when gnome "takes control" of a screen where this can be set. I tried to use a udev rule to switch as soon as a monitor is plugged, but it exits with 243 as usual. I suspect gdm has a way to automate such things that might possibly work, but I can't find it, I only read about some xorg scripts.

Also, there's this issue that's being worked on. One of the commenters uses an udev rule as a work arount but it doesn't work for me.

view more: next ›