I’ve got myself into a bit of a pickle!
I use Leap 15.1
I bought a WiFi dongle which needed drivers compiling from source. The instructions and experiences I found on the net were all for Ubuntu based OSs. But I noticed that they had been compiled on this page… http://download.opensuse.org/tumbleweed/repo/oss/noarch/
So I took the plunge and ‘upgraded’ to Tumbleweed.
The drivers didn’t work, or at least I couldn’t get them to work, so I used Filesystem Snapshots in Yast to go back to my Leap install.
There was another recent thread that described a relatively recent change upstream in systemd to disable retaining old kernels…
I strongly believe that is a mistake and hope that openSUSE maintainers will modify that setting and push to all openSUSE Users ASAP.
And unfortunately I believe that is why old snapshots may not work across the board, not just in your situation.
In your case,
I’d expect (and hope) that a 15.1 DVD image will do what your NET install is not.
If you’re having wireless driver issues, I’m also hoping that you are connecting to the Internet with a wired connection.
Worse case is if your fs is truly so munged that it can’t be recognized, you might have to install new and try to recover your data forensically.
Something else to try is a kernel fallback mechanism that many distros do not offer - symlinks to current kernel and initrd. At the Grub menu strike the E key. Then on the linux and initrd lines, remove all the versioning characters from the kernel and initrd lines, so all that remains of them is /boot/vmlinuz resume=blaa… and /boot/initrd. Also it may be worth removing the entire resume= string, and possibly the root= string, then proceed to boot with F10 or Ctrl-X. You might get lucky enough to apply a real fix.
After spending some time searching and not finding the thread,
I can only say to the best of my recollection,
It was very recent, likely within the past 2 weeks.
I’m pretty sure it had to do with loading a previous kernel using the grub menu, but it failed because only the current kernel is installed.
I remember clearly the problem wasn’t too many kernels, the problem was missing kernels when multiple kernels were expected. Enabling multi-kernel was the solution going forward although didn’t help the @OP of that thread.
I don’t remember the particulars, but I remember feeling uncomfortable about saying the disabled multi-kernel problem applies to every system.
Whatever the details were, it should be easy to verify if a problem exists… Do a “zypper up” to be sure you have the latest updates on your system. Then reboot and select an older kernel (not latest and current). Can you boot? If you can fine… But if you unexpectedly can’t, then it’s good you caught the problem now instead of a real problem. That’s assuming the problem still exists of course… I haven’t looked at this again in the past couple weeks.
Thank you for your replies. I’m sorry for the slow response back… I haven’t been home since I posted my message a couple of days ago.
I somehow managed to get the bootable USB start to ‘upgrade’ but when it got to the screen when you select your root partition it didn’t recognise any of my partitions as my root. I clicked on ‘show all partitions’, chose my root but it the installer wouldn’t accept it.
I ended up formatting and doing a fresh install. I keep all my files on removable storage and only have a few programs installed so it was no big deal.
I’ve got 32bit Tumbleweed on my laptop so I’ll install the driver and see if I can get it working on that before I attempt the desktop again when I get home.