I am using Opensuse 13.2 to test a number of systems, ATOM E3800 Series. I have 1 USB device that I boot each System from during test.
I am having a problem getting the “Minimal X Windows” build to boot on any of the Systems except the System I built the USB device on.
“KDE Desktop” and “Minimal Server” (Text Mode) work on all Systems (The one USB device boots all systems).
Is the “X Windows” build tied to the MACID of the original system in “Minimal X Windows”?
Or is there some other key being used?
I have the TPM disabled in the BIOS setup.
On the working System the USB shows up in the Boot Order as: opensuse (Sandisk Cruzer Glide 1.26).
On the failing Systems the USB shows up in the Boot Order as: UEFI: Sandisk Cruzer Glide 1.26.
I have the BIOS configured for UEFI boot and built the USB device with the following:
SDA1: FAT, /boot/efi
SDA2: Linux Swap
SDA3: Linux EXT4
The problem is your failing systems use UEFI to boot (If you don’t know what it is, here’s a nice simple explanation; https://en.opensuse.org/openSUSE:UEFI ) whilst the system you installed it on uses legacy BIOS. The UEFI systems expect to have a FAT partition where the files required for booting are. As you installed it on a system that uses a legacy BIOS, this was never created.
You have two choices;
Either you create a USB stick with the UEFI layout (instructions in the link above) or change the systems that fail to use legacy boot, different vendors have different ways to achieve this; https://neosmart.net/wiki/enable-legacy-boot-mode/
Are you sure the system that it works on isn’t using Legacy (CSM) boot?
The USB stick is in no way ‘tied’ to the system it was installed on apart from possibly having some configuration files that include the network adapters configuration information.
If you INSTALLED to a USb stick initrd is set to that machine so until you rum mkinitrd most any other machine is going to not run right. It should boot to recovery mode (in advanced boot menu) But when an install is made a basic picture of the hardware configuration is made in intird and is used for normal booting to speed it up because it does not have to discover new hardware. If you use a live DVD it is made to query the hardware on each boot so is more likely to boot correctly on arbitrary hardware.
I don’t fully understand the reason you are doing the exercise but without more input I say use a live DVD
I was able to figure out that the issue is somehow tied to “Secure Boot”.
I had been disabling that in the Installation step.
Today I built the USB device with “Secure Boot” enabled and now I am able to use
1 USB boot device on multiple systems (Each system is identical to the others, hardware)