this post was submitted on 05 Sep 2023
19 points (88.0% liked)

linux4noobs

1421 readers
2 users here now

linux4noobs


Noob Friendly, Expert Enabling

Whether you're a seasoned pro or the noobiest of noobs, you've found the right place for Linux support and information. With a dedication to supporting free and open source software, this community aims to ensure Linux fits your needs and works for you. From troubleshooting to tutorials, practical tips, news and more, all aspects of Linux are warmly welcomed. Join a community of like-minded enthusiasts and professionals driving Linux's ongoing evolution.


Seeking Support?

Community Rules

founded 1 year ago
MODERATORS
19
submitted 1 year ago* (last edited 1 year ago) by wheeldawg to c/[email protected]
 

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.

you are viewing a single comment's thread
view the rest of the comments
[–] wheeldawg 1 points 1 year ago (1 children)

This is annoying, but better now than after I get settled in.

Do you know anything I might've done to cause this? I don't wanna do whatever it was again.

[–] [email protected] 1 points 1 year ago (1 children)

when you reinstall, try to use btrfs (idk if kde neon support it in the installer)

then use timeshift to do a snapshot every day and a snapshot before upgrade. but set it up so that there are not more than ~10 snapshots.

next time something goes wrong you can restore the last snapshot.

Some distros also set it so you have previous snapshots as boot entries in grub.

[–] wheeldawg 1 points 1 year ago* (last edited 1 year ago)

It was an option, but I was planning on trying a couple different distros, and I know ext4 has better compatibility, and didn't want to format the whole drive back and forth, or have multiple systems at once time on different partitions. Once I settle permanently if it is an option I've heard some say it's better, but haven't looked into it yet.

Edit: just realized this sounds a little consider to the other comment.

What I mean to say is at least it was before I installed any programs and got to try it out. Based on another comment, I now know this is a rolling release which is not something I'm interested in anyway.