Boot with both legacy and UEFI

[Rabie]

hi polikuo,

Have you tried it on other machine ?

not yet

Have you locked your UEFI by accident ?

no i can boot windows with the same machine with UEFI and i checked extra.

I have no clue for now, I don't have a UEFI machine around right now for me to test.

you or someone else may have/has an Idea why it doesn't work ?
i realy need to boot with UEFI 

i am using this machine: https://www.zotac.com/at/product/mini_pcs/ci329-nano

[polikuo]

Have you locked your UEFI by accident ?

no i can boot windows with the same machine with UEFI and i checked extra.

I'm referring to the secure boot

[Rabie]

Hi polikuo,

I'm referring to the secure boot

it's disabled.
should it be enabled for UEFI?

 

[polikuo]

Hi polikuo,

I'm referring to the secure boot

it's disabled.
should it be enabled for UEFI?

No, you should keep it disabled.

[Rabie]

i am goin crazy!

i don't know why it's not working.

so i am gonna try grub with the tutorial from Juanito: http://forum.tinycorelinux.net/index.php/topic,19364.0.html

But this part i don't unterstand:

menuentry "corepure64" {
linux /boot/vmlinuz64 quiet text tce=UUID="d4432cde-d21a-4d40-b44b-f097ce72cdba"/tce64 waitusb=10:UUID="d4432cde-d21a-4d40-b44b-f097ce72cdba"
initrd /boot/rootfs64.gz /boot/modules64.gz
}

what i know that both of those files /boot/rootfs64.gz /boot/modules64.gz make the core file but i just have the Corepure64 file.

so my question is:
should i split the core into those files ? or how does it work ?

[polikuo]

what i know that both of those files /boot/rootfs64.gz /boot/modules64.gz make the core file but i just have the Corepure64 file.

so my question is:
should i split the core into those files ? or how does it work ?

Hi Rabie
If you have corepure64.gz, use that.
If you have rootfs64.gz and modules64.gz, you might wanna merge them together.

Code: [Select]

cat rootfs64.gz modules64.gz > corepure64.gz
I don't use GRUB2, but I think different bootloader use different syntax
SYSLINUX:(comma)

Code: [Select]

INITRD /boot/rootfs64.gz,/boot/modules64.gzGRUB2:(space)

Code: [Select]

initrd /boot/rootfs.gz /boot/modules.gz

[Rabie]

hi polikuo,

yes, but if i just have the core file, would the syntax be like this?

Code: [Select]

initrd /boot/corepure64.gz
or it doesn't matter and still have to be like this :

Code: [Select]

initrd /boot/rootfs64.gz /boot/modules64.gz

[polikuo]

hi polikuo,

yes, but if i just have the core file, would the syntax be like this?

Code: [Select]

initrd /boot/corepure64.gz

Hi Rabie.
Yes, that should work.

[Rabie]

hi polikuo,
yes it did work, now i can boot from UEFI with grub   

but i still wanna know why it didn't work with syslinux    

Thank you very much for teaching me so much 

[Rabie]

Hi polikuo,

like i said i did exactly the steps from Juanitos Tuturial: http://forum.tinycorelinux.net/index.php/topic,19364.0.html
and it does boot with UEFI.

The only problem now, that i am getting the following error and after that i must start x manually   

Code: [Select]

SQUASHES error: zlib decompression failed, data probably corrupt
SQUASHFS error: squashfs read data failed to read block Ox9d534
SQUASHIS error: zlib decompression failed, data probably corrupt
SQUASHES error: squashfs _read _data failed to read block Ox9dae4
SQUASHIS error: zlib decompression failed, data probably corrupt
SQUASHIS error: squashfs _read _data failed to read block Ox9e644
SQUASHES error: zlib decompression failed, data probably corrupt
SQUASHES error: squashfs read data failed to read block Ox9ebf4
.SQUASHIS error: zlib decompression failed, data probably corrupt
"SQUASHES error: squashfs_read data failed to read block Oxa3dd5
SQUASHFS error: zlib decompression failed, data probably corrupt
SQUASHFS error: squashfs _read _data failed to read block Oxa4329
SQUASHIS error: zlib decompression failed, data probably corrupt
I SQUASHES error: squashfs _read data failed to read block Oxa5569
SQUASHES error: zlib decompression failed, data probably corrupt
SQUASHIS error: squashfs _read _data failed to read block Oxa58bd
SQUASHES error: zlib decompression failed, data probably corrupt
SQUASHFS error: squashfs read_data failed to read block 0x8c970
SQUASHIS error: zlib decompression failed, data probably corrupt
SQUASHFS error: squashfs read _data failed to read block 0x8cd18
SQUASHES error: zlib decompression failed, data probably corrupt
SQUASHTS error: squashfs _read _data failed to read block OxBe15e
rc _core: IR keymap rc-cec not found

do you know what is that ?

edit:

i ran gdisk to check the USB drive and got that the partition is damaged!

Code: [Select]

#sudo gdisk /dev/sdd
GPT fdisk (gdisk) version 1.0.4

Caution: invalid main GPT header, but valid backup; regenerating main header
from backup!

Warning: Invalid CRC on main header data; loaded backup partition table.
Warning! Main and backup partition tables differ! Use the 'c' and 'e' options
on the recovery & transformation menu to examine the two tables.

Warning! Main partition table CRC mismatch! Loaded backup partition table
instead of main partition table!

Warning! One or more CRCs don't match. You should repair the disk!
Main header: ERROR
Backup header: OK
Main partition table: ERROR
Backup partition table: OK

Partition table scan:
  MBR: MBR only
  BSD: not present
  APM: not present
  GPT: damaged

Found valid MBR and corrupt GPT. Which do you want to use? (Using the
GPT MAY permit recovery of GPT data.)
 1 - MBR
 2 - GPT
 3 - Create blank GPT

why whould that happen ? i have repeated the tutorial many times and i am getting the same thing

what am i doing wrong ?

[polikuo]

Code: [Select]

data probably corruptthe partition is damaged!

I guess your hardware is failing.
You should verify your extensions (and your corepure64.gz) like this

Code: [Select]

tc@box: /tmp/md5 $ ls
kmaps.tcz          kmaps.tcz.md5.txt
tc@box: /tmp/md5 $ md5sum -c kmaps.tcz.md5.txt
kmaps.tcz: OK
tc@box: /tmp/md5 $ echo corrupt > kmaps.tcz
tc@box: /tmp/md5 $ md5sum -c kmaps.tcz.md5.txt
kmaps.tcz: FAILED
md5sum: WARNING: 1 of 1 computed checksums did NOT match


[jazzbiker]

Hi guys,

I use USB-flash installed TinyCore and regularly (not so frequent, around once per month) check it with
the help of attached script. The names of the corrupted extensions will be seen on the screen after the script exit.

Have a nice Core!

@Rabie, so Your partition has GPT table? You've mentioned that You followed the steps from Juanito's HOWTO, but he mentioned fdisk and MBR partition in his posts. I've never used gdisk, but seems that it don't want to work with MBR.

[Rabie]

hi polikuo,

I guess your hardware is failing.
You should verify your extensions (and your corepure64.gz) like this

yes you were right, there was one extainsion failing

Code: [Select]

md5sum: can't open '/mnt/sda1/tce/optional/mylocale.tcz': No such file or directory
/mnt/sda1/tce/optional/mylocale.tcz: FAILED
md5sum: WARNING: 1 of 1 computed checksums did NOT match
but i am still getting this:

Code: [Select]

rc _core: IR keymap rc-cec not found
should i mybe reinstall kemaps or is that something else ?

[Rabie]

Hi guys,

I use USB-flash installed TinyCore and regularly (not so frequent, around once per month) check it with
the help of attached script. The names of the corrupted extensions will be seen on the screen after the script exit.

Have a nice Core!

thank you i will try the script later.

@Rabie, so Your partition has GPT table? You've mentioned that You followed the steps from Juanito's HOWTO, but he mentioned fdisk and MBR partition in his posts. I've never used gdisk, but seems that it don't want to work with MBR.

yes, i think that the USB drive wasn't formatted correctly 

[jazzbiker]

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