I updated my computer recently; something was wrong with Discover and it was no longer notifying me of new updates, so there were a lot to go through. One of those was a Tumbleweed update (from the 4th, I assume). I had to run both ‘sudo zypper update’ and ‘sudo zypper dup’ to download them all. I then reset my computer, and now I get stuck on the screen in the image below every time. I can still access the Bios Menu, thankfully, but I have no idea what I may be able to do within it to fix this problem.
Any help is appreciated.
Not sure how useful it may be to know, but it’s an Intel system using UEFI with no legacy boot support.
Only Intel and UEFI give us virtually nothing to go on. 
Are the graphics Intel too, or AMD or NVidia (and if so which?)? Do you Get a boot menu before that screen goes blank? After that blank screen has been there long enough to be sure the PC finished booting if it could have, are you able to Ctrl-Alt-F4 (or 3, 5, 6) to reach a login prompt? If yes, logs and other information for troubleshooting can be collected. Also, if you do get a boot menu, in the Advanced options there are other boot options to try. Do any work, such as recovery, rescue or failsafe?
Press ESC to see more.
NVIDIA dedicated, Intel integrated.
If I pull up the boot menu while the computer is turning on, the menu operates as normal. It will not appear on its own, though.
Once the boot process starts, it does not register any inputs whatsoever.
I don’t see an Advanced option, but System Recovery does the same thing as booting normally.
The only alternatives in the boot menu I see are Ubuntu (which puts me in a very basic terminal not connected to any file system) and Windows, which just boots up Tumbleweed (???) maybe a holdover from an incorrectly deleted partition, idk.
I left my computer on that screen all night hoping it might have just been an incredibly slow process, but it’s still frozen.
The ‘Ubtuntu’ terminal is grub, if that matters at all.
Furthermore, it does have access to a filesystem, I was mistaken on that. However, the only folder in / is efi/, which has ubuntu/, boot/, and opensuse/ folders within it.
Ok, I’m learning a lot I wish I didn’t need to learn today. I have access to every partition on my device from this menu, but it keeps telling me I need to “load the kernel first.” Most questions I’m finding online have answers referencing files I can’t find the equivalent of. Within the main partition, /@/boot has grub2 in it, which - from what I’ve seen - means secure boot and is not compatible with most solutions out there.
Which answers? All you describe should not be necessary. “load the kernel first” means that you are trying to boot directly from the / partition.
What Ubuntu does doesn’t matter. They do their own stuff.
@FrasherGray likely need to add no modeset to grub/systemd-boot(?)
Probably kernel updates and the nvidia driver, all hard to say…
I have no idea. I’m just trying to provide as much information as possible because I have no clue what is going wrong or why.
I didn’t read it mentioned yet, but:
- For TW, we shouldn’t rely on Discover to perform “dup” functionality. Yea, you might have Flatpak apps installed, so that makes sense. Discover can also update the BIOS.
- What was the reasoning to run an “up”??
- The “dup” is what should ONLY be used to TW. And it appears it was your last update functionality attempt to execute to “fix things”??
“zypper dup” should only be used when updating TW. Then, run Discover to check for Flatpak updates … but reboot first if the “dup” required it.
I didn’t know about the TW update until after I ran ‘sudo zypper up’.
.
… then we read:
There’s a distinct possibility that there’s some issue(s) with the system because of all the mixed up update processes.
Plus the confusing information provided. For example, #1 suggests a Linux command line terminal, then #3 clarifies it’s a GRUB command line (?).
And still confused about #2, “Windows that boots TW”, There’s a Windows boot menu to boot TW (?).
Questions:
- Is Ubuntu bootable?
- Is Windows bootable?
- When did you install TW, and what method do you use to boot it?
The obvious challenge for new Linux users is understanding it’s core components, how they work, and the terminology used. (personally, TW should be for Linux knowledgeable).
Personally, based on explanations provided, I think the system is unusable at this point. A fresh install is probably best at this point.
Sorry. To clarify, in the Boot Menu, there’s three options, and one of them is labeled “Windows Boot Manager” but it doesn’t actually boot Windows. Idk why.
As for Ubuntu, it doesn’t boot up a kernel, it just gives me access to a grub terminal.
I’m going to try and download a different OS on a USB stick using a family member’s computer tonight and see if I can’t roll back the update or at least salvage my data…
I chose Tumbleweed because it was supposedly good for gaming and NVIDIA drivers, but the former is not the case in my experience. I think I switched back in March of this year. Despite the wide variety of linux distros available, it’s a lot more difficult to pin down which actually suit your needs (and capability) than I thought it would be.
1 Like
This may no longer be the appropriate place to continue this dialog, but I’m having a very frustrating issue where I can see my user home (/home/frasher) directory when in the grub terminal, but when I boot from USB and view the local harddrive, it’s just gone. The /home dir is empty. I can’t find anything about it online; if I could just transfer the files to a USB I’d be home free but I can’t even see them. I tried unmounting the harddrive partition but it immediately remounted and nothing changed.
Lots to learn first off you need to have fast boot turned off in Windows. With it on windows partitions are invisible to Linux.
Next default portioning is BTRFS with /home as a sub partition mounted in /root partition. Again invisible unless the root partition is mounted as BTRFS .
You should be able to start Windows from the BIOS and turn off fast boot.
Then tackle the rest. Do you have a NVIDIA card/chip?
That’s the thing; I don’t have any Windows partitions.
I have a dedicated NVIDIA GPU, yes.
Do you have a working boot menu that allows to choose various selections? If yes, does anything work, such as booting a prior kernel, or safe or recovery mode?
Are you able to do as @malcolmlewis suggested in post #9?
Screwed up reply feature again, sorry.
I have no options to boot in a prior kernel or safe mode, and the System Recovery option does not do anything.
I have no idea what malcomlewis was talking about or how I would accomplish it, sorry. From what I can tell, I can’t edit files except maybe with echo? I haven’t tried.