My system could not rotate wtmpdb was one error message that showed up after boot was stuck after 15 minutes or so. I tried to boot the current kernel in recovery mode, no effect, tried to boot the previous kernel, no effect. I tried to boot an openSUSE gnome live dvd, use gparted to scan and fix my system, error message, didn’t work. So what’s the point of having btrfs? What’s the point of those seemingly useless boot options if you’re not choosing a snapshot that works. Right now, my system won’t boot. I’m not even sure what I could do to rectify it unless I just download the lastest openSUSE tumbleweed, and upgrade my system using the latest .iso written to memory stick and booted off that. Plus, side note, I’m bothered that openSUSE doesn’t show the boot options on both the external monitor and the computer monitor by default (I’m talking about the openSUSE Gnome tumbleweed live dvd, and my current system).
Should I post a bug in bugzilla?
Idk if this is related bcuz I do not remember my error or recognize yours, but I too had my system remain blank at startup for far longer than it should have. I Still had tumbleweed on an USB ISO so I launched the installer and got frustrated. long story short, its still not fixed as far as I am concerned.
I did find that the kernel update 6.16.8 to 6.16.9 started it all. my ISO was 6.16.7 and I did start with a upgrade install because 6.17 just released. I was up and running doing an upgrade. This might be worth checking out.
I downloaded the openSUSE tumbleweed snapshot 20251007, wrote to USB using Rufus, booted the USB, but it just sat there when I selected “upgrade”, blank screen with the cursor blinking. So I’ll download a later version, and see if I can run the install from there. But still, you’d think there’d be a failsafe mode for booting. I choose the other kernel option, doesn’t boot. I’m not sure if I chose “recovery mode” and what happened there. But still, at least Windows has the option to boot into “safe mode”, or “safe mode with networking”, or “safe mode command prompt”. I thought that I would be able to choose a working image to boot off of. I know I can’t be the only one having such problems. I suppose others would just give up on openSUSE, and not even both to register in order to complain or file a bug.
Sigh… Don;t use rufus it must be a clean modified binary copy to the USB device not a partition/
yeah mine did the same thing, when it updated to 6.16.9. Sucks you werent able to upgrade. if you have your home folder on another drive you can always do fresh install.
seems kind of popular to not be reliable. should we go back to Daemon tools to mount ISO’s to usb drives?
I simply use cp others use dd all good if the install helper has a dd mode or simply does a non-changing copy then that should work too. Point is that programs that alter the iso will break openSUSE . The ISO is boot ready and does not require alteration
Well, if you figure that it could be Rufus that’s the problem, then I could try using ventoy, and then select the iso file I want to boot. I use openSUSE-Tumbleweed-DVD-x86_64-Snapshot20251014-Media and it boots, but when I choose “Upgrade”, I get the blank screen with the mouse cursor in the top left not blinking. I just figured it was a problem with the .iso. I found that I could boot into a previous image (supposedly read only), but I’m not sure if I can do an update using that. Choosing other kernels didn’t do anything to help me get back into my system.
ANY install helper can cause problems. only a simple binary copy to the device works every time.
Programs like ventoy and rufus may be needed by other distro’s but on opensuse only a clean non modified coy is needed
Ok so I have to write it to a DVD and then boot off that? Rufus write to usb using DD mode, so it should be okay…
No…LOL just copy to the USB. dd mode probably will work but any other mode will not…
I use cp (ie command line copy) if on Windows use a forensic copying program like
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.