• 0 Posts
  • 155 Comments
Joined 9 months ago
cake
Cake day: February 10th, 2025

help-circle


  • e: just saw your edits, you don’t need to do any of this, you can just look at your journal with ‘sudo journalctl’ from a terminal (or whatever GUI app Mint ships with)

    Did the install complete and then you rebooted and it failed?

    This is progress! Presumably, when your system tried to boot it would be writing information to a log that we can read. With your fancy new sysrescuecd, you can boot into a live environment and read that log.

    We’ll need to use the sysrescuecd live environment to mount your hard drive and read the log.

    Start sysrescuecd, startx, and open a terminal.

    Make a directory

    mkdir mint-root
    

    Find the device for your system’s root partition. Run

    lsblk
    

    You’ll see a list of things like sda, sdb, nvme0n1. If you’re using a M.2 drive it’ll probably be nvme0n1. Under that it will list the partitions (ex. nvme0n1p1). Your system partition should be the largest one but I don’t know Mint’s default partition layout. If there are multiple we can check them all, so just choose the most likely one.

    Once you’ve found the right device you can mount it to the folder you created (you’re already root, you don’t need sudo):

    mount /dev/nvme0n1p2 mint-root
    

    Now if you look in that directory (ls mint-root), you should see a bunch of directories like /bin, /dev, /sys, /usr, /var. If so, this is your system drive. If not and you see a directory named after the user your created when you installed mint, go back and choose the other partition, this is just a home partition.

    Assuming you have your system partition, now you can look at the logs:

    journalctl --directory=mint-root/var/log/journal
    

    This viewer uses vim-like controls, so j to go down and k to go up. Page Up and Page Down should also work (probably mouse scrolling too if you’re in a GUI terminal).

    The thing that caused the problem should be in the last few lines.


  • Ventoy rocks, everyone should use it.

    That is the expected behavior for sysrescuecd, it dumps you into a terminal because that’s enough for most tasks but if you run startx you get a de (xfce, I think).

    Ok, so that means this is something specific to how Mint is doing things.

    How far in the boot process do you get? Ideally, you don’t need to use compatibility mode because your laptop supports UEFI. Just stick to that option. As long as you don’t have

    Does GRUB load? This screen:

    It sounds like you do, since you’re able to try nomodeset. If you have an NVIDIA gpu, you can also try nouveau.noaccel=1 in the boot options.

    Going through their Installation Guide, the last thing Mint recommends is to try to install an older version, and then upgrade via the package manager. You can pick the iso with the DE you want here: https://www.linuxmint.com/download_all.php I’d try installing 21



  • Sorry you’re having such annoying problems so early in the process, I know it’s frustrating… Most people at least get to their DE before having problems at least!

    Try https://www.system-rescue.org/

    It’s not a distro that you’ll use day-to-day, but it’s a great live environment to keep on a USB. It boots on basically everything, has a lightweight DE and a ton of applications to diagnose and fix most systems.

    Importantly for us is that it’ll let us see if maybe Mint is doing something funky with their bootloader options. If you can’t boot into sysrescue it’s likely something we can fix in the UEFI.

    e: oh, already recommended Ventoy, oops. I promise I’m not an ad bot

    Keep at it, it’s frustrating at first, but it’s worth it.


  • Could you try a different live environment to see if it specific to that distro?

    It’s annoying to keep flashing a usb, if you haven’t already you can use ventoy. It’ll give you a partition to put all of your iso files and you can pick the one you want to boot to.

    And, as a Hail Mary, could you try connecting to a different hdmi or display port. I’ve had systems fail to boot because it was trying to use the incorrect display port and it dumps you right into efi errors.







  • You wouldn’t need to track them all, any distro’s installed package distribution (statistical, not Linux distro) should be strongly correlated with all of the others.

    Just like how you can poll a large crowd based on the opinions of a few thousand people. Arch is a good place to look since all packages are explicitly chosen by the user while in other distros the default software packages ensure that their repo stats will be skewed.

    When I’m looking into alternatives, I usually just search social media and note the things people recommend. The software ecosystem is small enough that this method isn’t (yet) polluted by bots promoting software.



  • That’s certainly a way of looking at it.

    The talent was upset at a conflict between kernel maintainers and posted a personal attack on Mastodon. The comment is now deleted ( https://web.archive.org/web/20250204004048/https://social.treehouse.systems/@marcan/113941358237899362 ).

    The Code of Conduct explicitly lists public harassment as an example of unacceptable behavior.

    Examples of unacceptable behavior by participants include:

    -The use of sexualized language or imagery and unwelcome sexual attention or advances

    -Trolling, insulting/derogatory comments, and personal or political attacks

    -Public or private harassment

    -Publishing others’ private information, such as a physical or electronic address, without explicit permission.

    -Other conduct which could reasonably be considered inappropriate in a professional setting

    Even if he is correct about about it being a code of conduct violation (it wasn’t), there is way to take action and it isn’t posting an attack on social media.

    Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the Code of Conduct Committee at conduct@kernel.org. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The Code of Conduct Committee is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.

    There has certainly been drama around Rust, but as was said in the thread: “Being toxic on the right side of an argument is still toxic, […]”



  • There isn’t a global 30% performance loss. There are specific games/configurations that have performance issues and bugs, but it isn’t all games.

    For example, there is a current bug, if you’re using some features in VKD3D(like ray tracing) which NVIDIA has identified and is creating a fix. The problem isn’t Linux specific, if you use VKD3D on Windows it also has this problem.

    The second Reddit link is a user confusing a Baldur’s Gate 3 bug, where vulkan was implemented in a buggy way, with a performance problem.

    There are always bugs and performance issues that appear and get fixed, that’s the nature of Linux. The social media meme “NVIDIA sucks on Linux” is based on old issues when NVIDIA cards had bugs that broadly affected games and other software to the point where it required a lot of effort (like patching your own software using git).

    This is not the case now, NVIDIA works without major issues. The strongest reason to use NVIDIA over AMD would be if you used CUDA to run local AI. AMD doesn’t work with CUDA and the projects that fix this are in the alpha stages.

    Gaming-wise, unless you play video games by staring at MangoHUD and comparing your historical frame-time graphs across multiple OSs, it works just fine.




  • You’re misinformed, mostly.

    NVIDIA had driver issues, incompatibility with gamescope (which was required for HDR) and a few instances of bugs, in WINE/proton, that caused performance problems in specific games/configurations.

    Now, the driver issues for the mainline cards (the most common ones on Steam’s hardware survey) are about the same frequency as AMD hardware and we use Wayland’s native HDR, so gamescope isn’t a concern.

    I’ve been using NVIDIA on Linux for 2 years now and I have never seen anything like a 30% performance reduction on any game, and I can also run local AI with acceleration.

    As long as you’re using current hardware then you’re fine. If your graphics card was released 2 days ago, or is from the ‘00s then you may experience issues but otherwise NVIDIA cards work just fine.