This appears similar to some issues I’ve seen when searching, but those appear to have been fixed from Fedora 40 onwards and I’m using 41.
If I boot from the USB installer a GRUB menu appears and allows me to choose to boot, verify the media etc. etc. Whatever I option I choose I get a single underscore-like cursor on the screen and nothing else happens.
I’ve tried a couple of different USB sticks and the problem persists. Debian doesn’t appear to be affected, but I’d rather not install that…
Just now I found a thread which appears to be the same issue. It mentions that the Intel Ultra 7 isn’t affected but the Ultra 5 is. My laptop should have the Ultra 7:
I can’t find any legacy mode settings (this BIOS is unfamiliar), as far as I am aware this system is using UEFI.
I’ve tried looking for BIOS info. but haven’t found anything, so I don’t think I’ll be able to flash a different version. Apparently, Clevo don’t make anything available for Linux users: LVFS: Search Results
This model is used by some of the Linux Laptop vendors but this example has an i7 and coreboot instead:
…so presumably it’s the different processor/motherboard/BIOS etc. which are causing problems for me.
So far I’m wondering if I can return it and get something else.
Coreboot eh? While ‘open source BIOS’ sounds utopian, I will say that with absolutely no evidence whatsoever, it may not be more secure. It is possible to update though, Flashing firmware tutorial — coreboot 24.08-1260-g2f808d0ab6 documentation but will that get you anywhere I do not know.
On the page you provided for your model Clevo do say it is Fedora compatible, and the little icon jumps, it is so cute. I would approach Clevo and complain!
I suspect the issue is Coreboot BIOS related. I do not see why it would be processor, and I highly doubt the motherboard is at issue.
It sees that I was unclear - sorry about that.
This laptop doesn’t have coreboot installed, it’s running whatever firmware Clevo has installed. There appear to be a few threads here with people reporting the same symptoms who also have Intel Ultra 7 processors (though on different hardware), with the BIOS implicated in the failure.
What I linked to was another vendor’s Linux version of this Clevo model, which I presume is working more reliably due to the different firmware.
I was able to get Ubuntu 24.04.1 LTS to install, but that has an older kernel (6.8?). Ubuntu 24.10 will boot but then runs very slowly and the installer crashes. The latest Gentoo liveUSB will not boot, showing the same symptoms as Fedora.
I’ve been looking myself and Clevo’s information is well hidden. This is one reason why I’m tempted to see if I can replace this with a system which is easier to work with, e.g. Dell or Lenovo - they do at least have an easy way to get firmware.
This laptop claims to be a V560TU with a V54x_6x_TU motherboard and “ME FW Version 18.0.10.2341”.
I was surprised at the lack of info. on Clevo’s site.
Certainly, I would prefer something else but I may be thwarted by bureaucracy.
I’ve tried Lenovo and Dell machines and the Fedora experience has been pretty good, though the Lenovo device was plagued by overheating (Thinkpad Z16).
Two is to enable ‘legacy’ mode in the BIOS or possibly pressing F12 (or other key??) on startup
Three is renaming the .efi file on the USB. Rename \EFI\BOOT\grubx64.efi to \EFI\BOOT\mmx64.efi . This is speculative, I found it in a linux mint forum but it won’t break your computer! You are being redirected...
Probably all I can suggest today it is now 1am, good luck and I’ll check back tomorrow.
This laptop does have a proprietary BIOS, not coreboot.
I mentioned earlier in the thread that some vendors sell this laptop with coreboot and a different processor, but I’m purchasing via a bureaucracy and can’t get those.
I looked for Clevo systems in the LHDB and didn’t find any recent instances (but lots of Clevo Core 2 Duo systems), which is a strong hint that nobody has linux running on your model.
At my former work, IT provides Dell systems with a Windows. Users who needed linux had 2 options: WSL at no cost or access to RHEL in a data center with “cost recovery” from the user’s budget.
One of my systems (Dell SFF) failed to boot Fedora for the 3rd month after the monthly Windows 11 update. I tried Fedora 41, 40, and 39 Workstation installers but they fail to boot. The Fedora installer that worked was the network installer, which I like as it gets you current packages.