Fedora Linux

I was trying to get my Sony DualSense controller to work ingame and managed to google my way to a solution (I think).

The controller works fine in Steam fullscreen mode, but refuses to pass the signals on to the game?

I found this, and started following the instructions and everything went well until I came to point 5.

What does it mean to "put 'X' into 'Y' file"? How do I do this? Which commands do I need to input in my console? is 'uinput' a separate file that I missed to download or do I just need to append the text "uinput" to the file somehow?

I just ran into problems while installing Fedora KDE and fixed them. I thought this might help some people.

1. No problem: installing Live .iso on USB-Stick: Had fedora on another PC installed already, while struggling to open balenaEtcher I learned fedora media writer does the same but more simple. Easy install.

2. Running the Live Version Installer: Freezes - fixed. Now the problem was starting. When I opened the installer two windows opened and closed really fast - then nothing. When I used it one more time after a few mins it just froze. -> Restart into Troubleshooting on USB -> Install worked perfectly.

Now I have my Computers on Fedora - one on KDE one on Gnome.

So I have a bequiet keyboard with lights. When I open up the web-based settings it says following:

It seems that you are using our device on a Linux system. To ensure full functionality, root user permission is required, while you follow these additional steps

And then goes on how I must install a *.rules file in the "/etc/udev/rules.d/" folder and then run:

sudo udevadm control --reload-rules
sudo udevadm trigger

Back when I bought the keyboard I had Mint installed on my computer.

I went through the same procedure as below on my Mint installation, and it worked. But now when I do the same on my Fedora, it does not work.

So I created a file (/etc/udev/rules.d/10-bequiet.rules). The rule file contains the following:

SUBSYSTEM=="usb", ATTR{bInterfaceNumber}=="02", ATTRS{idVendor}=="373f", ATTRS{idProduct}=="0001", TAG+="bequiet"
SUBSYSTEM=="usb", ATTR{bInterfaceNumber}=="02", ATTRS{idVendor}=="373f", ATTRS{idProduct}=="0002", TAG+="bequiet"
SUBSYSTEM=="usb", ATTR{bInterfaceNumber}=="02", ATTRS{idVendor}=="373f", ATTRS{idProduct}=="0003", TAG+="bequiet"
SUBSYSTEM=="usb", ATTR{bInterfaceNumber}=="02", ATTRS{idVendor}=="373f", ATTRS{idProduct}=="0005", TAG+="bequiet"
SUBSYSTEM=="usb", ATTR{bInterfaceNumber}=="02", ATTRS{idVendor}=="373f", ATTRS{idProduct}=="0007", TAG+="bequiet"
SUBSYSTEM=="usb", ATTRS{idVendor}=="373f", ATTRS{idProduct}=="0009", TAG+="bequiet"
SUBSYSTEM=="usb", ATTRS{idVendor}=="373f", ATTRS{idProduct}=="000a", TAG+="bequiet"
SUBSYSTEM=="usb", ATTRS{idVendor}=="373f", ATTRS{idProduct}=="0010", TAG+="bequiet"
SUBSYSTEM=="usb", ATTRS{idVendor}=="373f", ATTRS{idProduct}=="0011", TAG+="bequiet"
SUBSYSTEM=="usb", ATTRS{idVendor}=="373f", ATTRS{idProduct}=="0016", TAG+="bequiet"
SUBSYSTEM=="usb", ATTRS{idVendor}=="373f", ATTRS{idProduct}=="0017", TAG+="bequiet"
SUBSYSTEM=="usb", ATTRS{idVendor}=="373f", ATTRS{idProduct}=="0023", TAG+="bequiet"
SUBSYSTEM=="usb", ATTRS{idVendor}=="373f", ATTRS{idProduct}=="0024", TAG+="bequiet"
SUBSYSTEM=="usb", ATTRS{idVendor}=="373f", ATTRS{idProduct}=="0025", TAG+="bequiet"
SUBSYSTEM=="usb", ATTRS{idVendor}=="373f", ATTRS{idProduct}=="0026", TAG+="bequiet"
KERNEL=="hidraw*", SUBSYSTEM=="hidraw", TAGS=="bequiet", MODE="0660", GROUP="plugdev", TAG+="uaccess"

After creating the file and running the udevadm methods in the terminal, I still get the same error.

So I looked around and found another suggestion, which was to add an additional file:

# create rule
sudo nano /etc/udev/rules.d/99-bequiet-lightmount.rules

# add this into the rule file
SUBSYSTEM=="hidraw", ATTRS{idVendor}=="373f", ATTRS{idProduct}=="0002", MODE:="000"

# reload
sudo udevadm control --reload-rules
sudo udevadm trigger

So I added this file and ran the udevadm methods again, this also didn't make any difference (Although after this step it did work on Mint).

Is there any difference between these two that different on how I should create and "apply" rules? It did work on one system but not on the second. The Hardware is the same nothing has changed in that regards.

Does this rule stuff work differently on Fedora? Am I missing a step that I should do on Fedora that I didn't have to do on Mint?

Does "root user permission" mean that I might need to add something more, or do something different, rather than just the rule files?

What was different in Mint, was that I didn't have to add the files in "admin mode", if that makes sense. Do I perhaps need to start the browser in "admin mode" for it to work on Fedora?

Do anyone know what the issue could be here?

Thanks!

Hey everyone, I'm running into a weird problem with Fedora Workstation. Basically whenever my computer starts up, GRUB freezes (sometimes with the menu displaying, sometimes without it). It works fine when, while starting up, I go into the select bootloader menu (for me by pressing F9), select Fedora, and then GRUB works great. I don't have another OS installed, but I think the windows bootloader is still on the device, though Fedora and GRUB are the default bootloader. I do have secure boot on if that changes anything. Any advice on how to fix?

Intense discussion approves AI – but subject to full responsibility and disclosure

Helping with some @fedora@fosstodon.org @fedora@lemmy.ml @linux@lemmy.ml @Linux@linuxrocks.online #kernel617 #kernel 6.17 testing to go up from bed and do something

On the face of it, my old work laptop should be perfect for Linux. It's Intel based, drivers are very mature, it has a hefty CPU, 16 GB RAM and a zippy SSD. It was a beast in its day, and it should be able to re-live its glory days as a Fedora box.

My problem is Fedora has moved away from x11 and gone all-in on wayland. But the GeForce 650M GPU this thing shiped with is no longer supported by Nvidia drivers. I need to use the 470 version, which doesn't seem to work with wayland.

Has anyone gotten akmod-nvidia-470xx/xorg-x11-drv-nvidia-470xx working on Fedora 42? Would I have better luck trying a XFCE spin and installing KDE onto that?

UPDATE 24 Hours Later:
I had mostly answered my question with the idea of changing to the XFCE spin. I wiped it and reinstalled that spin which loads LightDM and an x11 environment. I got it working with that starting point. The irony is: I think I may have actually got there on the old spin also - for some reason the 6.16.9-200.fc42.x86_64 kernel won't display the LUKS prompt with those 470 drivers loaded. I thought it just wasn't booting. I'll never know now.

It's still a bit glitchy, but I think I'll sort the remaining issues out. Sometimes when something calls OpenGL, the display goes glitchy, but loading nvidia-settings restores things.

so I have this Rapoo BLE/BT3.0 mouse for years and it worked without issues up until Fedora 42. initially it worked there as well but after a bluez update it started with this shit.

everytime it goes to sleep due to inacitivity and then tries to reconnect on movememt or button press, it prompts me to authorize it. I've of course clicked trust and authorize with another mouse but it won't get remembered.

I've tried using bluetoothctl to manually pair, authorize, and connect and it don't make no difference. it behaves thusly on every BT controller I've tried, intel, broadcom, USB and onboard.

the mouse has two modes, BLE and BT3.0 and this behaviour is only with BLE, which is far superior - way faster tracking, reaction, reconnect, etc. - and I really don't wanna use the BT3.0 option.

on F42 there was a solution - downgrade bluez to the stack shipped with the initial install and exclude it from dnf upgrades. it starts working immediately after downgrade with zero issues. on F43 there is no such option.

tried searching but apart from some poor soul with the same mouse, no sensible clues.

any ideas on what to look up as I know dick about the whole bluetooth stack. please no chantgpt suggestions, thanks.

I have installed CUDA Toolkit, which comes with its own Nvidia drivers etc. However, since the Nvidia drivers and tools from rpmfusion-nonfree-updates are slightly newer, Fedora tries to install those instead, which fails due to conflicts.

How can I prevent Fedora from trying to overwrite packages from the cuda-fedora42 repo with similar packages from rpmfusion-nonfree-updates? I would prefer not having to lock the package version, as I want updates when available in the cuda repo. I would also prefer to not remove rpmfusion-nonfree-updates entirely, since I get Discord and some other packages from there too.

How does hardware video acceleration work on ARM? I would like to install Fedora on a Raspberry Pi, but first I would like to make sure I can take advantage of hardware video acceleration. Most likely ARM GPUs don't support VAAPI and I don't think there are tools equivalent to vainfo and intel_gpu_top. I'm looking for someone who can provide me with information on this topic 🙂 Thanks

So keyboard works fine and all at first. When i flip the laptop to draw fedora shows the keyboard disabled icon. But when i flip the keyboard back it fedora doesnt turn on the keyboard. Only when i suspend/close lid, does the keyboard start working again..

Ive tested on fedora workspace and now im on silverblue. Im not sure what the issue is, everything was working just fine.

Is anyones 2 in 1 laptop having the same issues on linux?

EDIT: I'm rephrasing some sentences Edit2: I gave up.

I just installed Fedora and to my surprise I can't use my NAS.

Through a SMB share I can see everything easily enough through GUI but I can't open any file, then I tried NFS.

With NFS I followed many tutorials to mount the shared folders, each one slightly different than the previous one, some told me to mount at /var/folder some told me to mount at /mnt/folder. I don't understand the difference. Anyway, now I know how to mount and how to put it in fstab so everything gets mounted on boot, not ideal but I can live with that.

What every single tutorial fails to say is that I can only access those shares as administrator and every time I want to open any file I have to type my password.

What I am missing here?

This tutorial is the one I finally followed

Here I noticed the the commenter added some options