My time with Linux has been equal parts amazing and absolutely infuriating. Linux Mint is NOT usable out of the box. Here have been my issues:

Nvidia GPU - Trying to figure out how to get the drivers working was a nightmare with ten million different people giving different advice on how to get it to work. Eventually I was able to get them signed and it seems to work

Bluetooth - Another nightmare. Bluetooth is terrible on Linux. It took hours to get it even remotely working ok, but I still don’t think it’s perfect.

Compatibility - Some things just straight up don’t work for seemingly no reason. None of my controllers work with Steam, no matter how many countless hours I’ve spent troubleshooting.

And that is where I am disappointed. Troubleshooting Linux issues sucks. There are so many people giving their opinions and all of them are different and most don’t work.

When Linux is working right it is amazing, and I love it. But right now, it just isn’t as good as Windows and extremely infuriating more often than not. Guess I am going to switch back and give Bill Gates all of my info again. Really fucking disappointing

Update: Controllers seem to work after forcing compatibility mode in Steam. No idea why that was off or why Steam was essentially hijacking my controller, but it seems to work now. For everyone that helped thank you.

  • Xanza@lemm.ee
    link
    fedilink
    English
    arrow-up
    0
    ·
    2 years ago

    Linux Mint is NOT usable out of the box.

    I set Mint up for my 65 year old mother about 4 years ago, and she hasn’t had a single issue since. I think it’s less about Mint being usable out of the box and more about Mint not doing what you want out of the box…

    • IHave69XiBucks@lemmygrad.mldeleted by creator
      link
      fedilink
      arrow-up
      0
      ·
      2 years ago

      My 73 year old grandmother also uses it and says its “minty fast” lol not sure what that means. She latched onto the name when she heard it.

  • ikidd@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    2 years ago

    Mint isn’t the platform for gaming on Linux. It’s way behind on a lot of things like display drivers. Try something like Bazzite or Nobara that have a ton of tweaks for both Nvidia and steam. Honestly, I’m really shying away from recommending Mint to new users, it’s getting really stale.

    • AlligatorBlizzard@sh.itjust.works
      link
      fedilink
      arrow-up
      0
      ·
      2 years ago

      Bazzite has been great for me. Bluetooth, Nvidia GPU, controllers, Bluetooth controllers all worked out of the box, and it’s based on Fedora so you get all of those perks, and the rollback feature, which comes by default, works (to an end user) rather like timeshift (I think - it lets you return to the previous working configuration if an update has a problem, which admittedly did happen to me recently, I just rolled back and waited for the devs to fix the problem the next day, lol).

      It doesn’t have a live boot option so it just has to be installed to try it, which is disappointing.

      But I totally get if OP wants to take a break and maybe come back to Linux in a few years, because Linux will keep getting better and Windows will keep getting worse.

    • ikidd@lemmy.world
      link
      fedilink
      English
      arrow-up
      0
      ·
      2 years ago

      Ventoy with all the distro LiveUSB images you want to try on it. You should be able to configure them as if they’re installed, unless you have to reboot. If your issues are hardware based, you’ll have a tough time doing anything useful on VMs. If you find you have to reboot to do anything, you’re probably going to want to actually install it. But you should get an idea of how things will go with a distro by doing this.

  • bluelander@lemmy.ml
    link
    fedilink
    arrow-up
    0
    ·
    2 years ago

    I’ve been on and off with Linux for about 15 years and just want to counter some of the people trying to troubleshoot or criticize to say: it can be really tough.

    We need our computers to work and we expect things to function correctly.

    I’ve used dozens of distros over the years. I was a super early Arch adopter, mained Gentoo for about three years, ran my own BSD server for programming projects, and still maintain several small home Linux servers. And even I sometimes want to pull my hair out trying to get semi-new hardware working right in my distro of choice. I spent three hours today fighting Nvidia and sound drivers and eventually just had to give up on that machine after being told that what I want just flat out isn’t supported in Linux on the hardware I have.

    Take a breath, set it aside until you’re ready to take another crack at it, and know that it’s a journey. You’ll get there or the software will catch up and meet you halfway. No shame in being frustrated :)

  • r.EndTimes@lemm.ee
    link
    fedilink
    English
    arrow-up
    0
    ·
    2 years ago

    Use cachy or bazzite, both are supposed to work well with ndvida theres also nodora

  • IsoSpandy@lemm.ee
    link
    fedilink
    arrow-up
    0
    ·
    2 years ago

    I can see everyone down voting you to oblivion… And that’s sort of fair. But that’s beside the point.

    I was having trouble with NVIDIA while using mint early on and decided to switch to Fedora. Maybe try that once. Fedora has better defaults for nvidia.

    Use the KDE Plasma spin btw. See if it works.

    • kusivittula@sopuli.xyzdeleted by creator
      link
      fedilink
      arrow-up
      0
      ·
      2 years ago

      I guess there’s difference with the gpu model too, because for me it has been the opposite: mint works without issues and fedora has been a nightmare, especially the kde spin one. last time it killed itself afrer the first updates. nobara was almost perfect but I could never figure out why it can’t turn the monitor back on after it has turned off.

      • IsoSpandy@lemm.ee
        link
        fedilink
        arrow-up
        0
        ·
        2 years ago

        I know. That’s why the live usbs are a life saver. I really just use the live usb to test everything out.

  • Shimitar@downonthestreet.eu
    link
    fedilink
    English
    arrow-up
    0
    ·
    2 years ago

    I think you are addressing the issues wrong.

    Unsupported hardware is a reality in Linux, even if I didn’t find any in the last 10+ years, my needs are much more limited.

    Controllers do work just fine, as well as Bluetooth, in my experience. Maybe share some issues and let’s see why.

    Troubleshooting in Linux means understand why stuff don’t work as you expect, not copypasta 50 different solutions. There are 50 solutions because there are 100 ways to do stuff and different distros and versions out there. The “unified” experience is from the windows world, not the Linux world.

    Nvidia is a known issue on Linux, prrprietary drivers kind of sucks and there are no good open ones, at least for newish nvidia cards. But again, my experience with nvidia has always been very good, with proprietary drivers.

    Steam, I used it trough wine to run windows games on Linux, with good success (1 game, so YMMV), and I found it amazing that it was even possible to do. But never used controllers

      • Shimitar@downonthestreet.eu
        link
        fedilink
        English
        arrow-up
        0
        ·
        2 years ago

        Keep on your “windows mindset”, won’t be very good on Linux i guess.

        Maybe a fresh install could help if you made too much of a mess, who knows.

        Still won’t fix your problems unless you find a way to address the issues. Maybe post them here so that we could help.

  • Naich@lemmings.world
    link
    fedilink
    arrow-up
    0
    ·
    2 years ago

    Maybe Linux isn’t the solution you are looking for in this case? I use Linux whenever I can, especially at home because I have far fewer problems than with windows. But it’s not a panacea, and if it’s easier to use windows then use windows.

    • Cold_Brew_Enema@lemmy.worldOP
      link
      fedilink
      arrow-up
      0
      ·
      2 years ago

      That’s the thing, I’ve loved Linux when it’s worked right. I want to use it full time. My first install, after fixing everything, was going great. I had to reinstall because I messed something up, and now I can’t fix any of this.

  • just_another_person@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    2 years ago

    Bruh. You been on here for two days complaining about something where you’ve been told exactly what the issue is, and it’s not your Mint install, Linux, or anything else about the same system or with the community you’re asking for help in.

    You’re not doing the work to find the issue, or help the people trying to debug with you. You’re actually seemingly going out of your way to not be helpful and just complain, and that’s a YOU problem. Have fun on Windows 👋

    • Cold_Brew_Enema@lemmy.worldOP
      link
      fedilink
      arrow-up
      0
      ·
      2 years ago

      Are you fucking serious? I’ve followed all the god damn advice I was given and have spent over 10 hours troubleshooting this ONE issue and nothing has worked.

      • GravitySpoiled@lemmy.mldeleted by creator
        link
        fedilink
        English
        arrow-up
        0
        ·
        2 years ago

        That’s what atomic distros are for. Detecting problems at the development level, not the user level. Might give one of them a try. And get rid of the dual boot, that’s just pain in the ass

      • just_another_person@lemmy.world
        link
        fedilink
        arrow-up
        0
        ·
        2 years ago

        Yes, and then you come back here raging that “Mint is not ready out of the box”, which isn’t true. The problem is with Steam and steam-input. You’ve been told this half a dozen times now. It has nothing to do with Linux (where you’re posting in), or Mint specifically. It’s your setup with Steam.

        • Cold_Brew_Enema@lemmy.worldOP
          link
          fedilink
          arrow-up
          0
          ·
          2 years ago

          I don’t see how. I have done everything you suggested with steam. I’ve tried every possible configuration, and nothing works.

            • Cold_Brew_Enema@lemmy.worldOP
              link
              fedilink
              arrow-up
              0
              ·
              2 years ago

              Dude, I have the exact same steam configuration in Windows, and my controller works. Tell me that’s not a Linux issue

              • Xanza@lemm.ee
                link
                fedilink
                English
                arrow-up
                0
                ·
                2 years ago

                Again, it’s a driver issue. Has nothing to do with *nix. The manufacturer of the controller doesn’t ensure that *nix distros have access to the driver. So how can it work?

                Specifically which controller is it? Have you looked for *nix drivers specifically for that device? From the manufacturer?

                • Cold_Brew_Enema@lemmy.worldOP
                  link
                  fedilink
                  arrow-up
                  0
                  ·
                  2 years ago

                  Thats the thing. I’ve tried both xbox and ps5 controllers, and none are working. I test with jstest-gtk and whats weird is the right joystick shows it only moves up and down. Not sure if that’s related, but it’s weird

              • just_another_person@lemmy.world
                link
                fedilink
                arrow-up
                0
                ·
                2 years ago

                Kid, if you want proof, DM me an invite to a call somewhere you can screencast and I’ll show you exactly what the issue is and fix it quickly. I’m that positive.

      • Xanza@lemm.ee
        link
        fedilink
        English
        arrow-up
        0
        ·
        2 years ago

        You can absolutely dual boot PopOS! and Windows. The only real issue you’ll run into is Windows update is destructive–so you’ll have to manually keep fixing systemd boot to ensure your PopOS! instance can continue to boot after Windows update.

      • catloaf@lemm.ee
        link
        fedilink
        English
        arrow-up
        0
        ·
        2 years ago

        Why does secure boot need to stay on?

        Even so, you should be able to sign the drivers and use the boot shim if you really want to go through that process.

        • Cold_Brew_Enema@lemmy.worldOP
          link
          fedilink
          arrow-up
          0
          ·
          2 years ago

          I would have no idea how to set that up. I already tried creating a VM within linux for windows, and it went very poorly

          • huskypenguin@sh.itjust.works
            link
            fedilink
            arrow-up
            0
            ·
            2 years ago

            Bro. You need to grab for sanity right now. Switch back to windows until you’re ready to take another dive. It’s worth it imo, but a lot of these comments are just plane unhelpful. Linux is great, if it’s not working for your hardware try a different tact.

            Nvidia support just turned a corner at the end of last year. It’s getting much much better.

              • huskypenguin@sh.itjust.works
                link
                fedilink
                arrow-up
                0
                ·
                2 years ago

                Yea and the purists are getting heated back. You’re obviously at a learning gap, and that’s the firmware gap. It’s annoying. But with older hardware it “just works”.

                I’m guessing since mint is Debian based it’s not getting the latest and greatest firmware blobs, or it’s on an older kernel.

                What’s your hardware? What version of Linux mint?

                You might want to try some gaming specific distros as they are a little more cutting edge. I’d suggest giving Bazzite or Nobara a try. Bazzite is immutable, so if it’s not working on first boot just give up and switch. But it is my personals favorite.

                Both are based on Fedora which is a little more cutting edge.

                You also might want to try Manjaro which is like Arch Linux with training wheels. It may just work on boot.

                Edit: Bazzite and Nobara will have Nvidia specific ISOs, so getting drivers working is no big deal. The core and legacy systems (Ubuntu, mint, Fedora, opensuse) all take a little more effort to get Nvidia working. Their spinoffs often times include the driver for you.

      • GravitySpoiled@lemmy.mldeleted by creator
        link
        fedilink
        English
        arrow-up
        0
        ·
        2 years ago

        Properly dual booting is much more difficult than starting a vm. Starting a vm is as simple as installing boxes and choosing the iso.

    • Cold_Brew_Enema@lemmy.worldOP
      link
      fedilink
      arrow-up
      0
      ·
      2 years ago

      System: Kernel: 6.8.0-53-generic arch: x86_64 bits: 64 compiler: gcc v: 13.3.0 Desktop: Cinnamon v: 6.4.6 tk: GTK v: 3.24.41 wm: Muffin dm: LightDM Distro: Linux Mint 22.1 Xia base: Ubuntu 24.04 noble Machine: Type: Desktop Mobo: ASUSTeK model: ROG STRIX X570-F GAMING v: Rev X.0x serial: <superuser required> part-nu: SKU UEFI: American Megatrends v: 5013 date: 03/18/2024 CPU: Info: 12-core model: AMD Ryzen 9 3900X bits: 64 type: MT MCP arch: Zen 2 rev: 0 cache: L1: 768 KiB L2: 6 MiB L3: 64 MiB Speed (MHz): avg: 2321 high: 3800 min/max: 2200/4672 boost: enabled cores: 1: 2200 2: 2200 3: 2200 4: 2051 5: 2200 6: 2200 7: 2200 8: 2200 9: 2200 10: 2200 11: 2200 12: 2200 13: 2200 14: 2200 15: 2200 16: 2200 17: 3800 18: 2200 19: 2200 20: 2200 21: 2200 22: 2200 23: 2057 24: 3800 bogomips: 182408 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm Graphics: Device-1: NVIDIA GA104 [GeForce RTX 3060 Ti Lite Hash Rate] vendor: Micro-Star MSI driver: nvidia v: 550.120 arch: Ampere pcie: speed: 5 GT/s lanes: 16 ports: active: none off: DP-1,DP-2 empty: DP-3,HDMI-A-1 bus-ID: 08:00.0 chip-ID: 10de:2489 Display: x11 server: X.Org v: 21.1.11 with: Xwayland v: 23.2.6 driver: X: loaded: nouveau unloaded: fbdev,modesetting,vesa failed: nvidia gpu: nvidia,nvidia-nvswitch display-ID: :0 screens: 1 Screen-1: 0 s-res: 2560x1440 s-dpi: 96 Monitor-1: DP-0 size-res: N/A Monitor-2: DP-2 pos: primary res: 2560x1440 dpi: 108 diag: 690mm (27.15") API: EGL v: 1.5 platforms: device: 0 drv: nvidia device: 2 drv: swrast surfaceless: drv: nvidia x11: drv: nvidia inactive: gbm,wayland,device-1 API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 550.120 glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2 Audio: Device-1: NVIDIA GA104 High Definition Audio vendor: Micro-Star MSI driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s lanes: 16 bus-ID: 08:00.1 chip-ID: 10de:228b Device-2: AMD Starship/Matisse HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s lanes: 16 bus-ID: 0a:00.4 chip-ID: 1022:1487 Device-3: Focusrite-Novation Scarlett 2i2 4th Gen driver: snd-usb-audio type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 1-3:2 chip-ID: 1235:8219 Device-4: PreSonus Audio ATOM driver: snd-usb-audio type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 bus-ID: 5-1:2 chip-ID: 194f:0206 Device-5: Blue Microphones Yeti Stereo Microphone driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 1.1 speed: 12 Mb/s lanes: 1 bus-ID: 5-2:3 chip-ID: b58e:9e84 API: ALSA v: k6.8.0-53-generic status: kernel-api Server-1: PipeWire v: 1.0.5 status: active with: 1: pipewire-pulse status: active 2: wireplumber status: active Server-2: PulseAudio v: 16.1 status: off (using pipewire-pulse) Network: Device-1: Intel I211 Gigabit Network vendor: ASUSTeK driver: igb v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: f000 bus-ID: 04:00.0 chip-ID: 8086:1539 IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: <filter> Bluetooth: Device-1: ASUSTek Broadcom BCM20702A0 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 bus-ID: 3-1:2 chip-ID: 0b05:17cb Report: hciconfig ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 4.0 lmp-v: 6 sub-v: 220e Drives: Local Storage: total: 2.27 TiB used: 165.04 GiB (7.1%) ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO 500GB size: 465.76 GiB speed: 31.6 Gb/s lanes: 4 serial: <filter> temp: 42.9 C ID-2: /dev/sda vendor: Samsung model: SSD 860 QVO 2TB size: 1.82 TiB speed: 6.0 Gb/s serial: <filter> Partition: ID-1: / size: 921.69 GiB used: 165.01 GiB (17.9%) fs: ext4 dev: /dev/sda4 ID-2: /boot/efi size: 95 MiB used: 32.7 MiB (34.4%) fs: vfat dev: /dev/nvme0n1p2 Swap: ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2 file: /swapfile Sensors: System Temperatures: cpu: 35.0 C mobo: 38.0 C gpu: nvidia temp: 48 C Fan Speeds (rpm): N/A gpu: nvidia fan: 0% Repos: Packages: 2166 pm: dpkg pkgs: 2160 pm: flatpak pkgs: 6 No active apt repos in: /etc/apt/sources.list Active apt repos in: /etc/apt/sources.list.d/1password.list 1: deb [arch=amd64 signed-by=/usr/share/keyrings/1password-archive-keyring.gpg] https://downloads.1password.com/linux/debian/amd64 stable main Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list 1: deb http://packages.linuxmint.com/ xia main upstream import backport 2: deb http://archive.ubuntu.com/ubuntu noble main restricted universe multiverse 3: deb http://archive.ubuntu.com/ubuntu noble-updates main restricted universe multiverse 4: deb http://archive.ubuntu.com/ubuntu noble-backports main restricted universe multiverse 5: deb http://security.ubuntu.com/ubuntu/ noble-security main restricted universe multiverse Info: Memory: total: 64 GiB note: est. available: 62.7 GiB used: 4.1 GiB (6.5%) Processes: 470 Power: uptime: 15m wakeups: 0 Init: systemd v: 255 target: graphical (5) default: graphical Compilers: gcc: 13.3.0 Shell: Bash v: 5.2.21 running-in: gnome-terminal inxi: 3.3.34

      • Nabuu@lemmings.world
        link
        fedilink
        arrow-up
        0
        ·
        2 years ago

        I have pretty similar hardware, but I do not have an NVIDIA card. Can confirm that Bluetooth is pretty dog shit most of the time, but I generally use wired accessories (preference). I did have some pretty good luck with an ASUS bluetooth adapter which worked better than the onboard one. Controllers work great with steam both wireless (save BT issues) and wired. I also run Fedora on all my machines so I couldn’t speak to anything Mint specific but I have been running Linux for a very long time and have found that some distros have better support for newer hardware than others.

        Mint is fantastic and that community does great work, all systems I manage that I do not own (family) run Mint. It is what i would recommend for any new linux user. However, for your use-case it might not be a terrible idea to give something else a try (if you haven’t already).

        There will always be troubleshooting that needs to be done regardless of the OS, as others have said, hardware manufacturers do not take (desktop) Linux seriously unfortunately.

        • Cold_Brew_Enema@lemmy.worldOP
          link
          fedilink
          arrow-up
          0
          ·
          2 years ago

          Thanks for the response. If I can figure this controller thing out I think I am good. But yeah I may try another distro if needed

          • Nabuu@lemmings.world
            link
            fedilink
            arrow-up
            0
            ·
            2 years ago

            Can I ask how you have steam installed? IIRC Mint does not use snapd so is it via flatlak or apt? If it’s Flatpak it could be that the flatpak doesn’t have the appropriate access to dbus which can be changed with something like Warehouse or Flatseal.

            I typically perfer a native .deb (or .rpm in my case) for something like steam.

              • Nabuu@lemmings.world
                link
                fedilink
                arrow-up
                0
                ·
                2 years ago

                If you have issues with your controllers with the flatpak I would try switching to the native package. There should be a .deb package for steam. If it doesn’t change the behavior, then I would assume something else is causing a problem.

                You can also install flatseal and try messing with the dbus setting, should be like half way down the menu for the steam flatpak. Since flatpaks are usually not given access to the entire system I could see it not having the correct permissions.

                • Cold_Brew_Enema@lemmy.worldOP
                  link
                  fedilink
                  arrow-up
                  0
                  ·
                  2 years ago

                  Thanks! I tried switching to the deb package and it was all the same issues. I think I got it working though. Just forced compatibility in Steam and it eventually worked. Still don’t fully understand why.

      • enkers@sh.itjust.works
        link
        fedilink
        arrow-up
        0
        ·
        2 years ago

        Just a heads up, if you want that to be more readable, put it in between two sets of 3 backticks (```):

        System:
          Kernel: 6.8.0-53-generic arch: x86_64 bits: 64 compiler: gcc v: 13.3.0
          Desktop: Cinnamon v: 6.4.6 tk: GTK v: 3.24.41 wm: Muffin dm: LightDM
            Distro: Linux Mint 22.1 Xia base: Ubuntu 24.04 noble 
        
  • ShortN0te@lemmy.ml
    link
    fedilink
    arrow-up
    0
    ·
    2 years ago

    Looks like you used hardware that was designed for windows and are blaming it now on Linux.

    I am not understanding the issue you have that requires signing of drivers.

    Yes some Bluetooth devices lack the support from the manufacturer’s for Linux, the Controllers i have used work great, at least for my needs.

    Controllers have better support Linux for ages. Not understanding the issue here either.

    Troubleshooting on Windows sucks at least to the same degree. The same non specific error message gets you 50 possible solutions.

    No need to announce your departure.

    • KSP Atlas@sopuli.xyz
      link
      fedilink
      arrow-up
      0
      ·
      2 years ago

      The reality is, people will be using Linux on Windows hardware, people won’t build special computers just for Linux or buy a premade Linux computer, they’ll flash Linux on their Windows computer expecting it to work and get annoyed if it doesn’t, the person in the post is making very valid points and those issues should be worked on

      • ShortN0te@lemmy.ml
        link
        fedilink
        arrow-up
        0
        ·
        2 years ago

        I absolutely disagree with you. If a manufacturer does not care about Linux support, it’s on the manufacturer. Do not blame the thousands of unpaid volunteers and a few paid ppl for not supporting a specific BT chip or controller or whatever.

        The signing issue is so on OP cause disabling secure boot or using a supported distro like ubuntu could have fixed that, and yes you can run Windows 11 with Linux dual boot without secure boot.

        • Stowaway@midwest.social
          link
          fedilink
          arrow-up
          0
          ·
          2 years ago

          I don’t think anyone is blaming volunteers. More so stating the obvious. If you’re new to Linux, you cant be expected to know everything about it. You may not know that some hardware may not work well with Linux. You may not know secure boot sux with linux. You may not know arch is not the best intro to Linux but because arch based distros are recommended frequently for gaming you may try it first. Linux can have a steep learning curve, expecting everyone to RTFM and all the forum posts is unreasonable. Sometimes people just need to try and experience pain and frustration.

    • Cold_Brew_Enema@lemmy.worldOP
      link
      fedilink
      arrow-up
      0
      ·
      2 years ago

      I’m venting because I don’t understand how the experience is so vastly different for people. And what do you mean hardware designed for windows? Literally the only thing is the NVIDIA gpu

          • Hellmo_luciferrari@lemm.ee
            link
            fedilink
            English
            arrow-up
            0
            ·
            2 years ago

            Nvidia isn’t responsible for the other issues you have… Did you do any research about your hardware and Linux compatibility?

            Bluetooth will be whatever wireless chipset you’re using likely.

            • Cold_Brew_Enema@lemmy.worldOP
              link
              fedilink
              arrow-up
              0
              ·
              2 years ago

              No I didn’t. When I installed Linux mint the first time I was able to fix everything. I needed to reinstall it and that is where this controller issue started

              • 0x0@programming.dev
                link
                fedilink
                arrow-up
                0
                ·
                2 years ago

                You might be better off with bare-metal linux and shoving windows inside a VM where it belongs.

                • Cold_Brew_Enema@lemmy.worldOP
                  link
                  fedilink
                  arrow-up
                  0
                  ·
                  2 years ago

                  I tried installing a VM but man it was really laggy. I used the open source one on linix, not virtualbox. I probably fucked something up, though.

              • stuner@lemmy.world
                link
                fedilink
                arrow-up
                0
                ·
                2 years ago

                Sorry to hear that Linux Mint is not working well for you. Unfortunately, things can sometimes still be rough when it comes to hardware support. I have personally also had issues with Nvidia GPUs and Bluetooth. Often this is because the manufacturers only provide drivers for Windows and Linux drivers need to be created by the community.

                Regarding Nvidia and secure boot. I’ve had the same issue (on both Mint and other distros). After some frustrations (including a BIOS update) I finally gave up and disabled secure boot. Since then, I haven’t had any issues with my dual boot with Win 10 (but I probably won’t buy another Nvidia GPU). What makes you say that Windows requires Secure Boot?

                No I didn’t. When I installed Linux mint the first time I was able to fix everything. I needed to reinstall it and that is where this controller issue started

                This seems quite weird. Are you perhaps missing a package (e.g. steam-devices)?

      • ShortN0te@lemmy.ml
        link
        fedilink
        arrow-up
        0
        ·
        2 years ago

        Basically everything you stated, Bluetooth, Controller and GPU is hardware.

        Your experience is probably different since you still think and act like you use windows. This is normal. When you are used to something and then switch to something that works differently you will run into problems.

      • LordPassionFruit@lemm.ee
        link
        fedilink
        arrow-up
        0
        ·
        2 years ago

        Not the guy your responding to and I 100% get your frustration, but I want to provide a little anecdote.

        Back in November, I built a new desktop to replace my 7 year old one and put OpenSUSE on it. No matter what I tried, I could not get either Bluetooth or WiFi working. I tried updating drivers, restarting controllers, reinstalling the OS, replacing the OS with Mint. Nothing worked.

        I did a lot of searching over the next few days, and it turned out that my motherboard was so new that it’s built in WiFi chip did not have Linux drivers yet. Like at all.

        Most products aren’t created with Linux in mind, so compatibility isn’t a concern. It’s up to the community to create patches & drivers to make things work, and it can take a bit to get things working.

        I’m genuinely sorry you had the experience you did, but I hope that if you do return to Windows that you’ll give Linux another try in the future. Search your products to see if others have had issues, along with potential solutions, before you dive in.

        • Cold_Brew_Enema@lemmy.worldOP
          link
          fedilink
          arrow-up
          0
          ·
          2 years ago

          Thanks for the thoughtful response, and not chastising me like half the other people in this thread. Yes it’s been very frustrating because I want to switch full time. I don’t understand how I am having these issues on a reinstall of Linux, when my first install had none of these issues.

          • IHave69XiBucks@lemmygrad.mldeleted by creator
            link
            fedilink
            arrow-up
            0
            ·
            2 years ago

            If you have newer hardware mint isnt what you wanna use. It is more stability focused. There are other distros that arr more geared towards faster updates and supporting new stuff faster.

      • Xanza@lemm.ee
        link
        fedilink
        English
        arrow-up
        0
        ·
        2 years ago

        I’m venting because I don’t understand how the experience is so vastly different for people.

        It’s always going to be a driver issue. It takes time and money to develop drivers for *nix, so most manufacturers don’t bother. It’s the most significant issue *nix has to deal with and if it wasn’t an issue, no one would deal with Windows.

  • Kongar@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    0
    ·
    2 years ago

    Those are not normal problems. Linux generally does work out of the box unless you’ve got weird or new hardware.

    Mint usually does the trick ez peasy and that’s why it’s recommended so much. BUT, sometimes it craps on your hardware. I’d actually suggest trying a different distro before you make up your mind. Some are newer than mint and might work where mint doesn’t.

    Might I suggest fedora workstation or popos? Fedora and the rpm fusion team make installing nvidia a breeze and it’s running pretty recent kernels and code. I’ve never run popos but it seems to be gaming focused and people generally like it.

    If your having the same issues, then you probably do have some hardware incompatibilities. And if that’s the case, you have my condolences-you’d be better off just sticking with something that works - aka windows.

    But please do believe me/us when I say you shouldn’t have to work that hard - mint is either too old, or you’ve got wonky hardware that is going to be a pain no matter what.

    • Cold_Brew_Enema@lemmy.worldOP
      link
      fedilink
      arrow-up
      0
      ·
      2 years ago

      I appreciate the response. I fixed my current issue, but honestly I’m thinking off messing with other distros. We’ll see.

  • Jumuta@sh.itjust.works
    link
    fedilink
    arrow-up
    0
    ·
    2 years ago

    fucking hate bluetooth ngl, it’s a horrendous standard that doesn’t do what I want it to do and even when it can it fails horribly and is unbearably unreliable

    how did you install the nvidia drivers btw? I thought in mint there was a “driver manager” thingy that installed it for you with one click

    • Ferk@lemmy.ml
      link
      fedilink
      arrow-up
      0
      ·
      edit-2
      2 years ago

      Bluetooth works great in Android for me though… once the devices have been paired, they connect the moment they are available and it just works.

      However, for some reason on PC it’s often quirky (Windows or Linux). My PC bluetooth works through a dongle so I wonder if an integrated card would do better.

      Also, most devices will not keep more than 1 pairing, so it will be annoying if you plan to be jumping around between computers. But that’s not the fault of the protocol, in theory remembering multiple pairings can be supported if the devices wanted to implement that.

      • Domi@lemmy.secnd.me
        link
        fedilink
        arrow-up
        0
        ·
        2 years ago

        However, for some reason on PC it’s often quirky (Windows or Linux). My PC bluetooth works through a dongle so I wonder if an integrated card would do better.

        Is it an USB dongle?

        If so, make sure to add a short USB-A to USB-A cable between your PC and the dongle. Interference is a serious issue on USB 2.4 GHz wireless dongles when directly connected to a mainboard.

    • Cold_Brew_Enema@lemmy.worldOP
      link
      fedilink
      arrow-up
      0
      ·
      2 years ago

      It was that easy this time around, because I’m dumb. The last time I never said I needed to sign them in the installer so I had to do it manually