i’m halfway capable with this kind of thing, but not an expert. not really sure why it would be having this issue. thanks in advance for anyone that can give me some help <3

  • aanes_appreciator [he/him, comrade/them]@hexbear.netEnglish
    8·
    1 month ago

    Okay annoying IT guy moment but are you SURE 144hz is selected in your monitor settings? Sometimes I’ve found a new OS (both windows and linux) can default to 60hz.

    Secondly, this will depend on your Distro, but you will want to make sure youre using the official Nvidia drivers, rather than open source drivers (called “Nouveau” usually) that some may default to. The open source drivers are OK but for newer cards are inferior and prone to weird bugs (such as stuttering, potentially!).

    I can’t really help you figure out what drivers you’re using or how to switch them as I have an all-AMD system and dont know your Distro. However, this is a very common task when setting up a Linux system so you can literally search “official nvidia drivers <distro> install” and you’ll be able to find relevant (and developer-recommended) info.

    Of course, the usual warnings of don’t copy paste random commands you don’t understand apple, because thats how you end up breaking things and reinstalling everything. I have enjoyed this many times, lol.

    Finally, this is a tangent since you mentioned dual booting: be careful!

    Bonus unsolicited advice

    Dualbooting setups are usually fickle thanks to Windows and Linux using two different programs (called bootloaders) to start themselves. If one updates and becomes incompatible the other, you may not be able to (easily) boot into one of your operating systems. IF this happens, you don’t need to panic: your data is safe. It’s usually easier to just backup sensitive data to the working OS and reinstall the other (or just delete it for good).

    If you had Windows and Linux on different physical drives (ie. one SSD with Linux, one with Windows) then this is usually not an issue, and your BIOS can find both systems independently without risks of cross-contamination.

    I won’t guarantee you’ll have issues, some people go years fine! I won’t guarantee it’s risk free either, but there’s mitigations and ways to prepare yourself if it goes wrong.

    • cinnaa42 [none/use name]@hexbear.netOPEnglish
      3·
      1 month ago

      thanks - I’ll triple-check all the settings. The weird thing is that it’s definitely doing 144hz at the desktop but when I’m using applications it’s clearly slower. I’ll have a look at drivers too - I went for the ones that it prompted me to install, but maybe those aren’t the best!

      Re: dualboot (thanks again for all the advice) - I had a moment of worry when I tried to boot into Windows after installing Linux and it bluescreened immediately, but after rebooting a couple of times and letting it fix itself, both seem to be working fine. I’m intending to eventually get rid of Windows altogether though, as I don’t want to have my 1tb NVME split between two different OSes. I may get a cheap second-hand SSD and stick it in my PC to use as a Windows backup drive just in case I ever need to use it.

    • PorkrollPosadist [he/him, they/them]@hexbear.netEnglish
      2·
      1 month ago

      Dualbooting setups are usually fickle thanks to Windows and Linux using two different programs (called bootloaders) to start themselves. If one updates and becomes incompatible the other, you may not be able to (easily) boot into one of your operating systems.

      This has gotten much better since the large-scale introduction of UEFI (required by Microsoft for device certification since Windows 8). With UEFI, the boot loaders are installed in parallel, and generally don’t mess with each other except for possibly changing which one is the default (and when this happens, the vast majority of UEFI firmwares allow you to choose from any of the installed bootloaders by holding a key at startup). It is a great improvement over the BIOS days, when you got one 512 byte master boot record per drive, and OSes would just clobber it.

      On UEFI systems, you typically want to have only one EFI System Partition (where all the bootloaders live), even if the operating systems themselves live on separate disks.

      Now, if only Windows would stop setting the hardware clock to local time…