I downloaded both the Tumbleweed DVD iso and the Live Tumbleweed KDE iso and wrote them to usb drives with dd so they would be bootable. When I go into the BIOS and select to boot from either of these drives, I’m taken to a grub screen with bash-like capabilities.
Why isn’t the Live-KDE or the DVD installer showing up?
Are you using your BBS menu instead of going into the BIOS to make a selection? Are there not at least 2 BBS menu choices (UEFI vs. MBR/Legacy) for either media that you want to boot from? Does this happen regardless which USB port you use?
My BIOS gives a choice between the drive or a UEFI partition. I’ve tried both. If I select the drive, it boots from my Nvme drive instead. Which takes me to emergency mode. If I select the UEFI partition it takes me to the grub screen.
USB port doesn’t matter.
I don’t know if this matters, but I was able to boot from a Bitdefender usb drive but I wasn’t able to do anything with that.
I can’t tell you with specificity because you haven’t bothered to tell us anything about the computer you’re trying to put TW on in either of your threads. A search engine should be able to tell you generally. Here is a link that hopefully will tell you how to activate yours, and lead you to whatever your actual BIOS calls it. More info here.
Well first, I’m trying to either reinstall Tumbleweed on a computer that’s been running it for the about the last six years, or fix whatever the problem is that’s causing it boot into emergency mode when I boot normally. I’ve never had a problem before booting from a usb drive by going into the BIOS and selecting that drive.
And why am I given a grub screen when I boot from either usb drive?
I don’t know. If what you really care about is reinstalling TW, download loader and linux from here, save them where Grub can find them, load them with Grub, and perform the NET installation that results. This is my normal installation method for all distros, which originated with SUSE 8.0. Here’s a Grub stanza I use for the purpose with UEFI:
Don’t be put off by all those linu line options, about half of which setup static IP in the installation and installed systems. Several I delete at runtime rather than having to remember what to type or look them up if I need them (most that follow the graphics options). They’re all options found here. You don’t need any of them for the YaST NET installer to function.
Well, you did not answer the question how you created this USB stick. Assuming that hd0 is your stick, grub sees one partition on it, while openSUSE installation image should have two partitions. Also, the whole disk should be accessible as ISO9660 filesystem, so error “unknown filesystem” here is unexpected. I certainly can access $cmdpath here after going into grub command line in UEFI. This error also explains why grub stops in CLI.
What is output of “fdisk -l” and “blkid” after you connect USB stick in booted Linux?
That’s wrong. It puts installation image on the first partition instead of the whole disk. You need to dd to output device /dev/rdisk4 (or whatever disk name for your USB stick is).
This has worked before.
For booting openSUSE installation image? I have my doubts, but of course different firmware may behave differently. Assuming that it can detect nested image inside partition … may be. But that is apparently not what grub expects.
Create installation device using the correct procedure.