• 0 Posts
  • 13 Comments
Joined 7 months ago
cake
Cake day: August 30th, 2024

help-circle
  • statler_waldorf@sopuli.xyztoLinux@lemmy.ml"SO proof" distro
    link
    fedilink
    English
    arrow-up
    5
    ·
    26 days ago

    I should probably clarify that I think my wife did something wrong and not Pop. I ran it smoothly for months before moving to Bazzite on my item machine. She knows enough to be dangerous and may have changed something without knowing what it did.

    An atomic system would be more SO proof for me.


  • statler_waldorf@sopuli.xyztoLinux@lemmy.ml"SO proof" distro
    link
    fedilink
    English
    arrow-up
    5
    ·
    26 days ago

    I’ve had my wife on Pop for 3-4 months now but she performed some update in the Pop Shop this week that totally borked the bootloader. I was not able to repair or even get it to see her hard drive.

    I was able to mount the drive using the Pop live USB and backup her data. I moved her over to Bazzite, which is what I use.


  • It just works for me. I tried it about a year ago when I still had an Nvidia card and Wayland wasn’t playing nice. I’ve since upgraded to an AMD and most things just work out of the box.

    Indiana Jones and the Great Circle gave me some trouble, but that’s just typical for MachineGames’s engine on Linux.

    The most difficult thing about Bazzite is figuring out rpm-ostree and package layering. Luckily there isn’t much I need that’s not in the package library.


  • Everyone else seems to have addressed the cloud part, which I was a little skeptical about too. I understood it is a development aspect, not an end user aspect, so I decided to use it. I’ve been using it as my daily driver for about 6 months and have had no problems.

    The atomic part was the biggest hurdle for me, since I wasn’t familiar with rpm-ostree, but I’m getting the hang of it. It’s had the added benefit of keeping me from breaking things through stupid mistakes since I can just roll back my changes.



  • Bluefin/Bazzite/Aurora are immutable, atomic versions of Fedora. I’ll probably explain it wrong but they’re more secured than normal Linux flavors and you get several copies of your core system files, so when you inevitably fuck something up, you roll back to the previous version and undo your mistake.

    I’ve only just moved over to Bazzite in the last 6 months or so, so I’m no expert, but it’s been a cinch to get most games running.



  • I don’t recall the names of them all. There were a couple I bounced off of like the House Party one and the platformer with insane controls.

    There were a couple that stuck with me like the Bubble Bobble soccer one, the paint racer, Bushido Ball, and the one where you make a chain reaction to blow up demons and save pilgrims.

    Camouflage/Chameleon got its hooks in me though and I cherried it in just a few sessions.





  • It did work before on Pop, and I should have been clearer. When I put the Switch Pro Controller into pair mode and use the KDE Bluetooth module to connect a new Bluetooth device, it doesn’t even see the device. I am able to see and pair other Bluetooth devices without trouble.

    I was going to familiarize myself with some terminal Bluetooth commands tomorrow and maybe dig up an old Bluetooth controller to see if it’s specific to controllers.

    I have an 8bitdo controller attached and working fine, but it’s got a wired base station that uses 2.4ghz to communicate with. I’d just use the 8bitdo controller, but it doesn’t have a gyro that I need for certain games.

    Edit I was able to solve this by using ‘bluetoothctl scan on’. It made the device appear in the KDE Bluetooth settings panel and it paired like normal.


  • I recently switched to Bazzite from Pop! and cannot get my Bluetooth to see my Switch Pro controller. It works fine wired, I can connect other devices via Bluetooth, the controller will connect other computers fine.

    I’ve tried two different USB Bluetooth adapters on USB 2.0 and 3.0 ports on the front, back and on the extra USB port on my keyboard. I’ve rebooted, restarted the Bluetooth service, and googled the hell out of it, but most problems I’ve seen are from years ago before Linux officially included the Pro controller driver in the kernel.