Boot with both legacy and UEFI

[jazzbiker]

I think polikuo is right, Your system exhibits unstable behaviour, some hardware problems are probably present, bad power, unstable contacts somewhere... Beware of possible storage damage. Try to power-off the system and check the cables.

[Rabie]

Why You say MBR is incorrect? I think it's all right. I use MBR.

i think you were right, that gdisk don't want to work with MBR.

[Rabie]

is there a way to remove the message "Welcome to GRUB!" ?

[jazzbiker]

Load grub2 sources, remove this message, compile and pack Your own extension
By the way Arch includes grub-silent package.

[jazzbiker]

Edit: This was the bad message, please forget if You've seen the previous content.

[Rabie]

Hi jazzbiker,

Load grub2 sources, remove this message, compile and pack Your own extension
By the way Arch includes grub-silent package.

thank you

[Rabie]

does anyone know what this Error mean?

Code: [Select]

rc _core: IR keymap rc-cec not found

[curaga]

It concerns remote controls (like your TV's), you can ignore it if you're not using any.

[Rabie]

Hi curaga,

It concerns remote controls (like your TV's), you can ignore it if you're not using any.

i see, thnx 

[polikuo]

Hi

I've found something.

I think the dosfstools.tcz on x86_64 needs to be recompiled.

This is what happens on CorePure64 13.0

Code: [Select]

tc@box:~$ mkfs.vfat /dev/sdc1
mkfs.fat 4.2 (2021-01-31)
Cannot initialize conversion from codepage 850 to UTF-8: Invalid argument
Cannot initialize conversion from UTF-8 to codepage 850: Invalid argument
Using internal CP850 conversion table
On PiCore-aarch64 13.1

Code: [Select]

tc@pi3:~$ mkfs.vfat /dev/sda1
mkfs.fat 4.2 (2021-01-31)
I can load into UEFI GUI vesamenu with the re-formatted partition.
However, something went wrong when I try to boot.
I guess it'll take a while for me to find out why.

[polikuo]

Hi again.

It appears the cause is the kernel.

TC 12 boots without any problem.

TC 13 refuses to boot.

I guess this might be related:
https://wiki.syslinux.org/wiki/index.php?title=Common_Problems#Linux_EFI_kernels

Due to a bug in the configuration system, some EFI kernels are not safely relocatable. CONFIG_EFI now requires CONFIG_RELOCATABLE. Syslinux will (safely) attempt to load such a kernel at its preferred address and bail if the memory is not available. This will likely exhibit itself as working on some platforms while bailing on others (with different memory maps).

Wonderful, we'll need to recompile the kernel 

[polikuo]

CONFIG_EFI now requires CONFIG_RELOCATABLE

Hi yet again

http://tinycorelinux.net/13.x/x86_64/release/src/kernel/config-5.15.10-tinycore64

Code: [Select]

CONFIG_RELOCATABLE=y
CONFIG_EFI=y

We do have those options enabled.
This is getting nowhere 

[curaga]

Those conversion errors may mean it requires glibc-gconv.

[polikuo]

Those conversion errors may mean it requires glibc-gconv.

Hi curaga
Both machine have mylocale.tcz onboot (depends on glibc_gconv.tcz)
They have the same version, too.

CorePure64

Code: [Select]

tc@box:~$ mkdosfs --help 2> /dev/null
mkfs.fat 4.2 (2021-01-31)PiCore-aarch64

Code: [Select]

tc@pi3:~$ mkdosfs --help 2> /dev/null
mkfs.fat 4.2 (2021-01-31)
Anyway, there are 2 problems.
First, dosfstools.tcz is messing around.
(a corrupted partition can't get Syslinux running at all, returns to "BIOS menu")
Second, the kernel 13 simply can not boot with Syslinux UEFI, but kernel 12 can.

[jazzbiker]

Hi polikuo,
Sorry for the noobish 2 cents, but syslinux.tcz seems to be unchanged since TC7. Is it possible that rebuilding the extension will help?