@exterma287 have you tried to unpair and repair the controller?
@exterma287 have you tried to unpair and repair the controller?
EYes multiple times too 
Hdoes it affect both your switch controllers?
Hjust trying to see if we can narrow anything down at this point
EYes both controllers have the issue and on 2 different user accounts
EAlso happened on holo iso, chimeraos and now bazzite so must be something on steam causing it
ENot tried connecting to steamdeck to try on stock steamos though
ESteam on my pc is fine
ESnap same mousepad, best mouse and mouse pad I've ever had
Kprobably not 
HHas anyone managed to boot UBlue with USB Gadget support for the SteamDeck? This would allow the console to be used as a kind of virtual Keyboard, Mouse, Disk, Ethernet etc (See Linux kernel src drivers/usb/gadget).
- Some Previous Art / Proof of Concept: https://www.reddit.com/r/SteamDeck/comments/ystmyd/its_now_ez_to_use_stwamdeck_as_usb_gadget_ie_usb/
K@exterma287
KI made a custom glass pad for it
Kthe mouse is modded too
Kbird for scale
EProbably not what?
EAh I mean the system
Kah yeah I love it
Kwireless charging mice for life
ENever having to plug it in or swap batteries is so good
ECould it be the Bluetooth adapter causing the issue? Anyway to disable the built in one on my motherboard via os and would a 4.0 USB one work to try that?
ENot sure if I can disable via bios not seen an option but not home to try
EQuick Google seems can't turn it off via bios
Hi know in kde you can name the adapters and you will have to disable the adapter each time you start up bazzite
Hin gnome i know you can disable 1 adapter and it will stay off between reboots
WDo you mind at least telling me where I need to edit that stuff? In those pages it doesn't tell me where I have to
Hfor kernel arguments check
for modules just check if they are enabled with
rpm-ostree kargsfor modules just check if they are enabled with
lsmod | grep nvidia
RDRD is half broken, so no, not yet. They also reverted it back on 120
RIt's more an hassle rather than a feature right now.
R@KyleGospo
RHmm.
RThis post remember me something I had experienced recently.
Hi know for hybrid graphics bazzite comes with the required hybrid graphics tools
RPeople point to this as the fix, @KyleGospo https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/commit/?id=df24d38bc7acd546eebd5567ea2d41f8eb2d6afa
RNot sure why bluez assumes a commit not even merged in mainline as the default, but that's another issue entirely.
RGitHub
Hello, Bluez 5.71 introduced a regression where the initial auto-connect for Bluetooth devices doesn't work anymore. Indeed, at system startup, starting a Bluetooth device (headset in my case) ...
RHere is the reference.
RAnd yeah, my suspicion regarding a kernel regression seems to be correct in this case.
WOnly thing missing is fbdev=1, how do I add it?
Krpm-ostree kargs --append=fbdev=1WSince it's for the nvidia_drm module, it is --append=nvidia_drm.fbdev=1 ?
Kwhat are you trying to do exactly?
WChecking over what is missing, I already fixed the random freezes
Kwe do this for you
WThat parameter is missing, shouldnt I add it?
K/etc/modprobe.d/nvidia.confWOk, now I just need to setup PRIME for switchable graphics then
Kdone for you
WReally? Where do I find the Optimus option then?
KGitHub
Mirrored from gitlab. Contribute to Jhyub/supergfxctl-plasmoid development by creating an account on GitHub.
