UEFI Boot Issue with KDE MX AHS Live USB on 2015 Acer Laptop

[Danathar]

I think this might be UEFI related, but I'm not sure what to check.

I have two Live USB sticks, both created with the MX Live USB Maker and set to full-featured mode with persistence. One was created from KDE MX AHS and the other from MX XFCE. The KDE stick is not recognized on a 2015 Acer laptop I tried it on, while the XFCE version is recognized. I've used the MX KDE stick on another UEFI system (an HP Elitebook 1040 G6) without issues, so I know the stick isn't broken.

The system is in UEFI mode. Is there something specific about the KDE MX AHS stick that would prevent it from appearing in the BIOS boot menu?

Apologies for not adding the system info to the post, I'm not near the system at the moment. I can add it later if need be. Any insight GREATLY appreciated!
thanks!

[CharlesV]

Yes Please post your QSI. ( MX Menu, Quick System Info, Copy for Forum, Paste here )

And both your live USB's are mx23 ?

I have seen a couple of updates to mx-live usbmaker over the past couple of months, possibly verify that you have the latest, and also when did you make that live usb? (ie how old is it?)

Also... not all USB sticks are created equal. I have seen where a machine will to boot on a particular USB stick, (perfectly fine usb and live load), but another computer will boot from it. If you have a third USB stick, I would try that.

[Danathar]

Yes Please post your QSI. ( MX Menu, Quick System Info, Copy for Forum, Paste here )

And both your live USB's are mx23 ?

I have seen a couple of updates to mx-live usbmaker over the past couple of months, possibly verify that you have the latest, and also when did you make that live usb? (ie how old is it?)

Also... not all USB sticks are created equal. I have seen where a machine will to boot on a particular USB stick, (perfectly fine usb and live load), but another computer will boot from it. If you have a third USB stick, I would try that.

Yes, both were MX 23. What's strange is that the bios didn't even recognize it. I would of thought at least it would give show me the entry and just not boot from it.

The laptop was over at my relatives house, so it may be this week sometime before I can get back to it and get the QSI, but I will get that. I made the USB stick probably about 2 months ago? The newest one was on Saturday (that worked).

[CharlesV]

This is sounding like a USB vs BIOS issue. You may have a usb-3 in an older USB 1 which is not happy with it?

[Danathar]

This is sounding like a USB vs BIOS issue. You may have a usb-3 in an older USB 1 which is not happy with it?

I'll need to check, but I don't think that would be the problem. The device that worked was a Sandisk Ultra Flair, which is a USB 3.0 device. The one that isn't working is a Samsung USB 3.1 Fit Plus, which is advertised as being fully backwards compatible with USB 1.0, 2.0, and 3.0.

Of course, one definitive way to check would be to reformat the Samsung device and set it up in the same way as the Ultra Flair. I could live with that, but it would be preferable if I could fix the one I have without having to completely wipe it and reinstall everything.

[CharlesV]

Ya, the bios not seeing the USB is a really interesting thing... and it may just be THAT usb stick. ( Sizes maybe ? or else maybe just 'a thing' ... I have seen this. )

[Danathar]

Ya, the bios not seeing the USB is a really interesting thing... and it may just be THAT usb stick. ( Sizes maybe ? or else maybe just 'a thing' ... I have seen this. )

Hmm...size is an interesting theory. Its a 2015 laptop, and the Samsung USB drive is a 256GB thumb stick. I wonder if it can't see a usb storage device that big. Did they have usb storage that big in 2015? I can't remember.

[j2mcgreg]

This is sounding like a USB vs BIOS issue. You may have a usb-3 in an older USB 1 which is not happy with it?

Or a USB 3.0 port which cannot be used to boot either.

[j2mcgreg]

In the interim can you give us the complete model name of this ACER?

[Danathar]

This is sounding like a USB vs BIOS issue. You may have a usb-3 in an older USB 1 which is not happy with it?

Or a USB 3.0 port which cannot be used to boot either.

I used the same port for both sticks.