linux4noobs

1340 readers

1 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?

Mention your Linux distro and relevant system details.
Describe what you've tried so far.
Share your solution even if you found it yourself.
Do not delete your post. This allows other people to see possible solutions if they have a similar problem.
Properly format any scripts, code, logs, or error messages.
Be mindful to omit any sensitive information such as usernames, passwords, IP addresses, etc.

Community Rules

Keep discussions respectful and amiable. This community is a space where individuals may freely inquire, exchange thoughts, express viewpoints, and extend help without encountering belittlement. We were all a noob at one point. Differing opinions and ideas is a normal part of discourse, but it must remain civil. Offenders will be warned and/or removed.
Posts must be Linux oriented
Spam or affiliate links will not be tolerated.

founded 1 year ago

MODERATORS

PlutoParty@programming.dev

Fresh newbie with a boot problem (sh.itjust.works)

submitted 1 year ago* (last edited 1 year ago) by wheeldawg@sh.itjust.works to c/linux4noobs@programming.dev

29 comments fedilink hide all child comments

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

[–] taco_ballerina@lemmy.world 3 points 1 year ago (1 children)

If your memory is not stable you're always going to have weird problems. I would get to the bottom of that first before anything else.

[–] wheeldawg@sh.itjust.works 2 points 1 year ago (1 children)

Well I have no idea what to check or how in that regard.

New build, new hardware, and got me, totally new OS.

[–] taco_ballerina@lemmy.world 2 points 1 year ago (1 children)

Not too different than on Windows. Stress tests, MemTest86, disable/enable XMP, double check voltage, update your BIOS. Check that your RAM is on the motherboard's qualified vendor list. It might be worth making a separate post about it.

[–] wheeldawg@sh.itjust.works 1 points 1 year ago (1 children)

I meant I don't know how to do that given that it won't boot with both sticks in. Another weird thing is the shot the motherboard says to use first is not working, but the door it says to use 2nd is.

QVL lists this exact memory, but only the smaller version (2x16 instead of 2x32). Not sure if that would cause an issue, especially since one stick works at a time. So clearly the sticks themselves aren't bad, they both work one at a time. Max compatible capacity is 192, so I would think you'd be able to get there somehow. I can double check voltage, but I haven't touched it, and I would assume the default is safe. But maybe that's on me for assuming.

I can try toggling xmp, but that doesn't seem likely. I'll give it a shot in a couple hours.

As for bios update, I haven't checked into it yet, but they gave a usb with some updater that's meant to be run under Windows, I don't know how I would use that or what I would do instead. I figured I could get it running before I got that done but maybe it needs to be done sooner than I thought.

Either way I'll try to figure out both of those ideas before making another thread for that.

[–] taco_ballerina@lemmy.world 1 points 1 year ago

I think it's worth looking into before pointing a finger at any particular OS. If your troubleshooting requires you to install Windows, go for it. My gut feeling is that the memory requires more voltage but that's not based on anything but my own experience. Go through all the troubleshooting steps.