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.
I had similar issues recently on my ideapad while slapping KUbuntu onto it. I doubt these are all specifically related to your issue, but some heads-ups won’t hurt.
Totally ignore anything on
snap, it can break your entire system like it did mine. I had an issue with my package manager afterward that prevented me from updating dirty codes. Just use a flatpak or appimage, or install from a repo, and it will save you a world of hurt. (If Neon doesn’t supportsnap, then good on them. Never again.)If you have trouble with the “open” Nvidia driver, it’s worth considering the proprietary right now; my desktop machine on Mint had a very similar issue to yours after an update, which I had to fix with Timeshift. Apparently that driver is sketchy as hell anyway, but I haven’t been following that drama very closely.
It’s good to hear that you’ve got it booting from USB again; I would strongly suggest installing all updates before anything else, other than graphics drivers. While you don’t usually need to reboot after an update on Linux, this is technically not true for kernel updates or modules; and by experience, it’s also not something you want to wait around on with graphics card updates, even if the system doesn’t say it explicitly.
So it should isolate your issue if you install the OS, install all updates other than graphics, reboot, install graphics card drivers, reboot, and then worry about software-- if there’s an issue, you’ll have it isolated.
I would check on that RAM, and your Mobo, though. It sounds like you might be the lucky winner of a bathtub fault on it, which any reasonable vendor should be able to refund or replace.
I actually haven’t gotten it to reboot into USB yet, am working on getting back to the machine here in a few minutes.
I saw an article where the open driver for version 530 was marked as “recommended”, but borked systems. On 535 the closed one was recommended, so I went with that.
Hadn’t gotten around to any software yet.
I’m not familiar with the phrase bathtub fault. What’s that slang about? I’m really hoping I don’t have to RMA the board, taking it apart again would be a huge pain in the ass.
New hardware failures tend to follow what’s known as a “bathtub curve” for failures over time-- in one hand, you have a steady climb on the far end because of wear and tear with age; but due to undetectable manufacture faults, there’s another steep rise at the beginning, too. There may be internal issues that simply no one has seen yet.
So getting a piece of hardware with an early defect is what’s casually called a “bathtub fault”. I know it’s irritating, but let’s not jump to conclusions yet. It might still be fine.
In the worst case scenario, you might also consider reseting the CMOS if you really can’t get it to boot-- could be a wonky BIOS setting and that would remove that.
Each mobo has its own thing for that, but you can also pop the battery, flip off the PSU switch, and hold power for thirty seconds to drain the caps, and that will force it back to its defaults. I mean you got it to run once, so it’s probably something stupid.
Good luck!