Have you searched the community for related issues?
[ x] No similar issues found.
Please describe the problem you’ve encountered in detail:
I created an install USB which successfully worked on an old system76 laptop. Brilliant. Using the same device on a newish Asus S13, I get a blank screen for a few seconds and then the boot process restarts (from the beginning).
I have installed on that machine currently PopOS and it runs like a champ. Secure boot is turned off. I tried with a second USB, same thing. (Note that the first one was a USB-C fairly large USB. The second one was an old USB-A that comes in at 7.8 G.).
I tried hacking this by creating a bootable USB and copying the bin directly, then trying to mount it and boot into it. Unfortunately the kernel for FydeOS doesn’t seem to have EFI stubs and it didn’t work. So that was probably a dead-end.
Any ideas?
System & Device Information
ASUS Zenbook UX305CA
Hardware & System Configuration:
Processor: Intel Core m3-6Y30
Graphics Card(Please specify if there’s a discrete graphics card):
I misquoted the processor. The original S13 came out with the one originally mentioned. This is a quite new machine. My bad for trusting a google search and not verifying. Using lscpu it’s actually an Intel Core Ultra 7 155U.
The machine meets the boot requirements as documented. The Ultra processor line is specifically called out as being supported in the documentation for choosing the right variant. Notice that it has Meteor Lake which is the 155H processor as being supported by the Modern variant. The 155U is not called out explicitly (which I believe is Arrow Lake) but it is extremely close to the 155H. It’s hard to imagine that that minuscule difference in the number of cores and frequencies would cause the machine not to boot.
When you say “Ultra is not supported” what specifically do you mean and what about it is not supported?
Ok, thanks for the tip. They are officially supported it looks like, but there seems to be some bugginess in that support. Seems like the Meteor Lake processors (and therefore Arrow Lake as well) all have the same issues.
I might have a shot at trying to build the kernel and replacing it in the image with one that has EFI handover enabled. I suspect if I can get past the initial boot process I might be able to get it to work. I’ll post back if I am able to make some progress.
Question Description
System & Device Information