So after faffing about forever I got ubuntu installed, can’t use it because it lacks drivers probably.
How do you guys deal with it? I understand why Wendell is so into motherboards now. From what I’ve gathered you need to thread the needle perfectly to even install Linux, then there is the fact that it won’t boot GUI without drivers so that explains why there is such happynoises about IPMI since it’s probably really useful to get a linux machine up and running.
I thought Linux was ahead of windows with pnp, I don’t know what I don’t know, but I don’t know how linux got users in the first place. Non-masochists need not apply?
1 Like
do a bare minimum initial install, then just install drivers after installing the main OS. not a big deal.
for what hardware are you having difficulty finding drivers?
3 Likes
Try different linux distributions by running them on a USB first, test that it has all the drivers you need before installing it.
My personal preference is ZorinOS, it is based on Ubuntu LTS release actually but is much more polished
What drivers are you lacking?
3 Likes
I’m using an Asus Pro Art x870e, 9950x3D and a 5090. Since I’m gonna be off working for a while I wanted to try this vast ai thing and it requires ubuntu so that’s what I’m trying to get running on it.
I’m assuming GPU drivers since I just get black screen and nomode doesn’t seem to nomode.
“install drivers after installing the main OS” is kind of a no deal since I can’t get an image on my screen when booting
1 Like
what kernel parameters are you booting with? i suspect your problem lies somewhere in there.
specifically things like “quiet” and “splash” tend to cause issues with Nvidia hardware.
ive also heard that the Ubuntu server installer is more stable than Ubuntu Desktop. iirc, they are the same OS, just different default packages and configs.
2 Likes
I have no idea, as I said never tried as a Linux desktop OS before. Is there no such thing as default install and it just boots? I’ve tried so many different bios settings, rebar on/off. Just plugged in a random WTG with a super old w10 on it. boots right up, works no problem.
It’s got no system specific drivers naturally, but it does just fine. Why is Linux like this?
1 Like
you’ll definitely want the proprietary Nvidia drivers, not the open source ones. But even those might be behind and not support the RTX 5000 series yet. Generally you dont want to jump in with the absolute latest hardware
4 Likes
a certain old quote from Mr. Torvalds regarding Nvidia cooperation with Linux comes to mind.
5 Likes
lol yep, I remember that video 
4 Likes
A windows install from when the 2000 series was new still outputs fine so that’s another thing that doesn’t make sense to me.
actually now that I’m in windows none of the volumes are mapped and showing up. Shouldn’t they be or is this a linux thing to not map them?
I’m more clueless than you might think so there is probably an easy fix (for not me) to apply somewhere but I’m basically just flipping switches until the light comes on
1 Like
can you install the base linux system without any desktop environment or gui software initially? i think the Ubuntu server installer gives you the option to forgo a GUI.
1 Like
The volumes from your linux install wont show up when you boot into windows and look for them? Those are probably using a file system Windows doesn’t know how to read so they don’t show up anywhere. Windows knows FAT32, ExFAT, NTFS, and ReFS. Linux often uses EXT3/4 or BTRFS, etc as they are much more advanced.
2 Likes
do not recommend BTRFS to newbies. idk why its the default on SteamOS.
2 Likes
They show in disk management, but they don’t have drive letters and I cannot apply any to them either.
I’ve been following the guide here Vast.ai | Console
But there is this section
Ubuntu 22.04 is recommended for all GPUs, but w/ Nvidia GPUs it has a nvidia-container issue that must be mitigated. The simple workaround that seems to work is option 2: Explicitly disabling systemd cgroup management in Docker.
Add the parameter "exec-opts": ["native.cgroupdriver=cgroupfs"] to the /etc/docker/daemon.json file and restart docker.
Then check the output of "docker info", and look for the Cgroup driver part, should look like this:
Logging Driver: json-file
Cgroup Driver: cgroupfs
Cgroup Version: 1
The intall script tests for this nvml bug.
I assumed this was related to running the service later on.
Then there is the sentence
Now wait for ubuntu to finish installing, and proceed once it has successfully booted. The rest of the installation will be automated by our installer script.
This is also something I assumed would come later since the install of their software is listed as a much later step.
Is installing ubuntu just “building a skeleton” then I have to build the rest of the OS up my self? (if so I think I give up)
1 Like
ah yes, they are ext file systems
Thats how all Linux systems are.
1 Like
Oh god. I think I prefer fighting windows than my self
1 Like
So are you installing Ubuntu 22.04 LTS in a docker container or VM then? Not just on a normal hard drive as the base OS?
Typically you really shouldn’t have to fight with things or jump through hoops when installing Linux anymore. This isnt always the case such as when using the latest hardware or installing it in virtualized environments or when using other special distributions
1 Like
Straight on the drive from a USB
Then you shouldnt need to follow anything in that guide you posted. That sounds to me like it is listing some specific peculiarities for installing Ubuntu within a docker container.
Edit: You will have to use the Nvidia 570.86.16 linux driver or newer to have RTX 5090 support. This will likely mean manually installing the drivers, though it is possible something like Arch Linux may have them included by default by now. Im not sure I havent really looked.
https://www.phoronix.com/news/NVIDIA-570.86.16-Linux-Driver
1 Like
