New kernel in core64; and compatibility with UEFI?

(17 posts) (3 voices)

Tags:

No tags yet.

Ceel

offline
Administrator

I think I've understood.

With Rolling core64, CPU 3 & 4 are updated -> it seems the 32bit kernel doesn't use CPU 3 & 4. Right?

Posted 6 years ago #
Ceel

offline
Administrator
@ Bellard,

Hi, I come back to the original subject of this topic.

What is the bootx64.efi you use to boot in EFI mode?

Understood. It's vmlinuz renamed.
Why not using rEFInd or GRUB 2 to boot in UEFI? They are much smaller than the kernel

I created 32bit ISOs with TazLiTo, replacing the kernel by rEFInd/GRUB 2:
- from Qemu, rEFInd doesn't work correctly (does not read its config file and does not scan partitions);
- with GRUB 2, from Qemu, SliTaz booted in graphic mode;
- from Virtual Box (Live session with kernel 3.2.98), rEFInd works correctly but SliTaz starts in console mode.
I don't understand these differences; please can you enlighten me?
Is Qemu entirely compatible with EFI? Maybe it needs to be updated.
And maybe Virtual Box needs to be updated too?

I noticed when I created my ISOs that TazLiTo
- limits the space for /efi (I had to suppress the not useful rEFInd's icons (otherwise -> Boot Failed. EFI); or maybe it doesn't like we do modifications in /efi?
- delete my /boot/grub repertory when it generates ISOs (-> have to launched GRUB 2 from its command line);
- doesn't extract my /boot/refind_linux.conf file from my ISOs.
Bugs or normal working?
Posted 5 years ago #

Reply

You must log in to post.