wheeldawg

So first off, what I'm TRYING to accomplish here is to have 3 drives show in Dolphin with their correct names. They are 3 physical drives (no crazy partition shenigans), but I'm having several issues trying to get them to be usable. All 3 are nvme drives connected directly to the board. (I'm new to Linux, not building machines.) The main drive is encrypted and is showing as type LVM2, the others are just ext4.

I am still fairly new with this, and didn't mess with this much when I used Windows, but when I did everything worked fine the first time. I'm pretty competent at following directions, and willing to learn vocab and lingo.

So the 3 drives are:

-main system drive

-drive to store photos (labelled 'Archive')

-Had a 3rd drive sitting around when I put this system together. No real intended use for it yet, but I'll think of something later.

So I'd like to have them listed as Main, Archive, and Drive3 for now. For a while I just had Main and Archive working. I just tried to add some photos to the Archive drive a couple minutes ago, but it's not longer showing in the Devices section in the sidebar. There is still a "Main" listed, but it says "An error occurred while accessing 'Home', the system responded: An unspecified error has occurred: No such interface “org.freedesktop.UDisks2.Filesystem” on object at path /org/freedesktop/UDisks2/block_devices/dm_2d0" whenever I click on it.

Seeing as I know my computer is currently working, that doesn't make any sense to me. There is another drive simply listed as "1.8 TiB Internal Drive dm-1" which is actually the correct drive for my system install. So the listing it was under now doesn't work, but it's still easily accessible with this default name.

There is now a recovery device listed, but I haven't created a recovery partition, and I certainly don't want to see it listed in the devices, as if I need it I will just use it as intended, I don't ever need to browse it easily.

The Archive drive is not listed at all anymore. I can still see it in GParted, and it shows up just fine, but says it isn't mounted. At the moment I still have the original copies of everything I've put on it, so worst case scenario I can reformat it and start over, but I'm just trying to understand what happened here so it isn't a recurring problem. It wasn't mounted according to GParted and the Disks utility, so I just tried mounting it and it worked, but none of the files that were on it are still there. But they're still on the Main drive, so I can just drag them back.

After mounting the drive just now, the Devices section has disappeared in Dolphin. I'm getting more and more confused the more I try to figure it out and fix it.

I'm assuming if it's showing blank (other than an empty 'lost+found' directory that means the data is gone. I'm almost afraid to reboot now and feel like it's about to implode on me. I can get screenshots of whatever might need to be seen, but honestly now with the Devices section just entirely missing, the idea of this being convenient is becoming hopeless. I just want the drives to always show up with the correct names, and not give errors trying to navigate them. This shouldn't be this complicated. At least the system itself is functioning, but this is killing me. I've never had drives just stop showing up before.

Oh so the 3rd drive I did just add recently, so it really hasn't had time to have an error with it, as I haven't touched it yet. Nothing is on it, it was just recently added

So in short, any ideas why the "Main" listing stopped working and why it showed up as a default named partition? The Archive part actually may not have been copied over yet (I can't remember stuff to save my life sometimes) but I know the drive itself was at least accessible before. Which it seems to be now, but was unmounted by default, which is kinda odd. Also when I mounted it, it showed up as a folder with a long name of random numbers and letters, but it still shows the correct partition name in GParted. The 3rd drive shows correctly as "Drive3" which is its volume/partition name, but the partition on this drive is named/labelled "Archive" but shows as a long string of numbers, letters, and dashes.

And now I'm unsure which drives are still working at any given moment since the Devices part isn't even there and I have to keep manually digging into them from the media mount point "folder". I can make a version of it by manually adding a "Place" to the Dolphin sidebar, but it's not in its own category anymore, and is much more annoying to me this way. I could use it like that if I have to, but I'd rather go back to each one showing on its own.

Any ideas or help?

edit- Using Pop with KDE

So I'm getting the famous gray screen crash on trying to start the game.

I have finally moved to Linux for my main machine and almost everything is running smoothly except this game in particular.

I using Lutris to get to BattleNet. Overwatch 2 works great. But Diablo 4 just shows a gray screen for 2 or 3 seconds and then the window closes bringing me back to whatever was on the screen when it tried launching.

I've seen a bunch of mentions of this issue, most are for the Steam Deck or are Windows-related, and I've seen a lot of posts about switching Proton versions and VKD3D versions, but I cannot seem to get a working combination to just get into the game.

I don't have a clue what is wrong or how to even diagnose what else to do here. All of the links I can find that mention anything.

I had to stop after launch because my last machine only had 4GB of RAM and would choke after a few minutes, but this machine should not be having problems.

Edit- Game is still having problems even when launched from Steam.

I cannot get Battle.net to launch with any regular Proton version or Experimental. I also can only get it running with GE after version 8-26. (only 3 versions, 8-26, 9-1, and 9-5)

But every version up to 9-5 has the gray screen for a couple seconds, then the game closes with no error message.

First of all, big surprise, right? Stuck with it for now, though. Not sure if AMD is actually any better at this point, but that's a problem for a different time.

So I've tried fedora now, (can list hardware later in post)and got it to install fine, did the system update, 4gb or so later, that's good to go, so now I figure it's time to get the GPU drivers working so I can make progress on making a daily driver out of this machine.

There's a lot of conflicting information and alternate routes to go with the drivers as I've gone to see, so that's confusing enough already.

So I'm on the KDE version of F38, since I would like to use Plasma.

I found and installed the "latest" dkms driver via cuda.

Haven't made other changes at all yet.

But at this point, it black screens after the grub menu. If I use nomodeset I can access the system, but I'm stuck in 1024x768. This is obviously terrible, I have a GPU for a reason and I would like it to work. Before installing these drivers I could at least use native resolution and native refresh rate.

It's defaulted to Wayland of course, which I hear can be another issue by itself, but I don't know the pros and cons of it vs using X (or X11 it whatever is actually called). I also know the open drivers can have issues, but am not sure if they would be useful for me.

Relevant hardware: MSI MAG Z790 i7 13700K RTX 3070 Ti

So obviously these drivers don't work for me, but I'm not sure what I need to do from here. Google got me this far, but there's not a lot of mentioned of being forced to use nomodeset, and nothing relevant at all if how to get proper drivers installed properly.

I did add the RPM Fusion repo, but haven't used it yet. Or at least the free one, can't remember if I added the non free one yet.

Happy to find outputs of whatever you need, but I'm still very new to using a terminal, so I don't know much about what I can do with it in general, much less what to do with it or try to look at in this specific case. I've picked up bits and pieces, but until I can get a working environment, learning is difficult.

Hello,

Finally built a new rig, and wanted to ditch Windows.

Got KDE neon up and running, booted into it, got my browser mostly back to how I like it, ran an update for my video card. I didn't notice the screen blackout and come back like it normally would for a video update, but I don't think that has anything to do with my current issue. I tried to restart to make sure it was running, and the update part of discover showed up and said I had a couple hundred updates to get, no big surprise there, since it is a fresh install.

Then it hung on fetching updates, and while I could browse my list of programs, I couldn't do anything else. So I did a hard shut down and powered back up.

It sticks on some kennel warnings and won't go any further.

Obviously I can't really do anything from there that I know of.

I also can't even get it to boot with the install media. That just sticks on a black screen. I can tell the monitor is actually showing black, as it doesn't give the "NO SIGNAL" warning. I have no idea what to do from here since I can't get it to react to anything, much less know how to fix anything if I could get in.

As for what the warnings say, there are 6 or so lines saying the same thing: problem blacklisting hash (-13), and one more that says nvme2: failed to set APST feature (2)

I haven't put anything on nvme2 yet, I haven't even formatted it yet, just the primary drive (nvme0). So I'm not sure what could possibly be wrong with it yet.