Author Topic: TinyCorePure64 and UEFI boot (Read 29181 times)

hamak · « **on:** January 02, 2019, 04:08:34 PM »

Hello there
I am very very new to linux and Tiny Core

I am trying to make TinyCorePure64 v9.0 boot with UEFI and I have followed this tutorial on partition the USB Drive: http://forum.tinycorelinux.net/index.php/topic,20939.msg130829.html#msg130829

I get the usb boot menu up as USB HDD: AI MASS STORAGE
I have disabled secure boot but I cannot disable UEFI or change it

I am trying to be able to boot with both legacy MBR BIOS and UEFI so I can use tinycore on allmost all computers

My laptop is Acer Aspire ES 11, ES1-132-C3TU with eMMC 32GB Drive

I have added images of folders and files on usb drive and settings from BIOS on laptop

Hope there is a way to get this to work

polikuo · « **Reply #1 on:** January 03, 2019, 03:44:43 AM »

Hi, I can see you have your F12 Boot Menu Enabled.
You should try pressing F12 right after you power up your laptop.
The USB should appear on the pop up list.
I suggest trying this method before hacking your motherboard setting.

Quote from: hamak on January 02, 2019, 04:08:34 PM

My laptop is Acer Aspire ES 11, ES1-132-C3TU with eMMC 32GB Drive

To hack your motherboard, please refer to this How to Boot from USB vedio.
Although it's a tutorial on installing M$, it tells you how to disable UEFI.
It uses another similar laptop model "ACER ASPIRE ES 15".
You could give it a shot and see if the it works on your PC.

hamak · « **Reply #2 on:** January 03, 2019, 05:40:54 AM »

Thank you for quick reply
I already use f12 to get the boot menu but when I try to boot from usb it only starts windows.
I think it is not finding tiny core.
Do I need to install tinycore after everything in the tutorial is done or is corepure64.gz the tinycore os?

Thank you

polikuo · « **Reply #3 on:** January 03, 2019, 11:11:22 AM »

Quote from: hamak on January 03, 2019, 05:40:54 AM

I already use f12 to get the boot menu but when I try to boot from usb it only starts windows.

It's good to hear that your laptop recognizes an USB bootable media
I've seen tablet PCs that just won't boot from an USB drive

Are you booting in legacy mode or UEFI mode ?
If you are running in legacy mode, please check if the partition is marked active
It's an essential step for your PC to find the system files

corepure64.gz is 64bit for TC
The minimum requirements are 2 files
vmlinuz64 is the kernel
corepure64.gz is the initial ram disk
If you set up your bootloader properly, you should be able to boot

hamak · « **Reply #4 on:** January 03, 2019, 03:08:10 PM »

I only have UEFI on this laptop and I cannot change it to legacy but I have disabled secure boot

I think the problem is the bootloader and I have followed the tutorial on this page:
http://forum.tinycorelinux.net/index.php/topic,20939.msg130829.html#msg130829

Maybe I cannot use syslinux? I know there is mentioned extlinux but here is my syslinux.cfg config:

Code: [Select]

UI vesamenu.c32
DEFAULT tc

LABEL tc
MENU LABEL Tiny Core
KERNEL /vmlinuz64
INITRD /corepure64.gz
APPEND root=UUID="1B5B-059C" rw

hamak · « **Reply #5 on:** January 03, 2019, 05:33:04 PM »

I looks like my laptop Acer Aspire ES11 ES1-132 only can boot with microsoft bootloader.
Maybe Acer only want me to use windows 10? that was installed on it?
I dont know if tinycore can boot with windows bootloader

It looks like the paths on my laptop is hardcoded as mentioned here:

Code: [Select]

Recently I installed LinuxMint in this laptop, and this is the link helped me to install...

I have found a way to boot Ubuntu on a russian linux forum, where the reason for this problem is explained. 
The reason for it is that someone naughty has hardcoded all possible paths you can use to boot your system ('thanks a lot'). The paths are:

\EFI\Linux\BOOTX64.efi (Linux)
\EFI\Microsoft\Boot\bootmgfw.efi (Windows Boot Manager)
\EFI\ubuntu\shim.efi (ubuntu SECURE)
\EFI\ubuntu\shim$cpu$.efi (ubuntu SECURE)
\EFI\ubuntu\grub.efi (ubuntu NORMAL)
\EFI\fedora\shim.efi (Fedora)
\EFI\android\bootx64.efi (Android)
\EFI\opensuse\grubx64.efi (topenSUSE)
\EFI\redhat\grub.efi (Red Hat Linux)
\EFI\SuSE\elilo.efi (SuSE Linux)
\EFI\ubuntu\grub$cpu$.efi (ubuntu NORMAL)

http://community.acer.com/t5/E-F-V-and-M-Series-Laptops/ES1-132-cannot-install-other-OS-than-Windows-10-BIOS-options/td-p/476726/page/2

I will look more into this tomorrow and see if it works

Rich · « **Reply #6 on:** January 03, 2019, 09:10:10 PM »

Hi hamak

Quote

I looks like my laptop Acer Aspire ES11 ES1-132 only can boot with microsoft bootloader.
Maybe Acer only want me to use windows 10? that was installed on it?

If I've read things correctly it sounds like Acer just restricted the boot paths it will recognize. It sounds like if you create the path:

Code: [Select]

\EFI\Linux\It should show up as another boot option. Now replace /EFI/BOOT with \EFI\Linux at this tutorial you linked to:
http://forum.tinycorelinux.net/index.php/topic,20939.0.html

polikuo · « **Reply #7 on:** January 03, 2019, 09:54:47 PM »

Quote from: hamak on January 03, 2019, 03:08:10 PM

here is my syslinux.cfg config
Code: [Select]
APPEND root=UUID="1B5B-059C" rw

Can you boot into syslinux menu ?
If you can then a quick fix should do:
TC does not use root=...
Instead, we use tce=...

BTW, I don't think "rw" is required
I would go with

Code: [Select]

APPEND quiet tce=UUID="1B5B-059C" lang="zh_TW.utf8"

hamak · « **Reply #8 on:** January 04, 2019, 06:30:44 PM »

Thank you very much for replying but it sadly does not work

Does anyone actually have an UEFI Tinycore ISO image that works by following the tutorial on the page I have posted or are people just giving up and skipping the UEFI problem?

I am talking about this version of TinyCorePure64:
https://distro.ibiblio.org/tinycorelinux/9.x/x86_64/release/TinyCorePure64-9.0.iso

I must say that I get it to work on the old computers without using UEFI but I really want to be able to use one usb drive that can handle both UEFI and Legacy BIOS. My friend was over today and he was not able to boot any of the many many ways be tried to build the UEFI. we even tried to use YUMI UEFI but had no luck there either.

I am still googling for tutorials on how to make UEFI work with syslinux or extlinux because that is what I really want to learn and use.

To go back to the basic what is the minimum of partitions. Here is what I have so far.

Gparted one partition with GPT +550M, ef00 and make it hybrid MBR and set bootflag on it and formatted with mkfs.vfat

tomorrow I will make a short screen recording of what I do if anyone wants to see if I do it right

Thank you and have a good night

coreplayer2 · « **Reply #9 on:** January 04, 2019, 10:05:34 PM »

Quote from: hamak on January 04, 2019, 06:30:44 PM

Does anyone actually have an UEFI Tinycore ISO image that works by following the tutorial on the page I have posted or are people just giving up and skipping the UEFI problem?
...
we even tried to use YUMI UEFI but had no luck there either.

what do you mean by image?

Sure, I create USB thumb drives that boot via UEFI or Legacy Bios mode. However I use Grub2-multi from the corepure64 repo, to multi boot Corepure64 and TinyCore32 in all TC versions 8.x, 9.x and now 10.x alpha from the same USB thumb drive.

For UEFI you should use x86_64 version of grub2, just follow the instructions in the grub2-multi.tcz.info file

Having said that about grub2, there’s no reason why you can’t get extlinux to boot in either mode.

I use Fat32 for the small boot partition containing grub2, linux, tinycore and module files. Then ext2 partition for Home, OPT and TC version & architecture specific tce directories.

It’s very important to get the paths right as UEFI expects to find required files at certain paths, then booting grub2 or extlinux should be straight forward. booting Tinycore is simply a matter of telling the boot loader where the files are.. use config files for that

My ASUS notebook will boot either UEFI or Legacy BIOS mode, but UEFI mode is marginally quicker otherwise you can't tell the difference.

Good luck

Sent from my iPhone using Tapatalk

hamak · « **Reply #10 on:** January 05, 2019, 10:05:56 AM »

I mean ISO image when I say image. I just want to know if I am using the correct image that supports UEFI x64 OS

Can someone give me a tree output of the file structure of a working UEFI USB Drive?

Here is my non working configuration step by step and as someone helped me figure out before is that I had to change from /EFI/BOOT to /EFI/Linux because that is only where my cheap laptop searches for.

Everything is done from Virtualbox with bootable TinyCorePure64.iso

Code: [Select]

tce-load -wil gdisk dosfstools syslinux mtools glibc_gconv tree nano

sudo gdisk /dev/sdc
x      # expert command
z      # wipe out gpt
yes
yes   # blank out MBR
sudo gdisk /dev/sdc
o      #delete all partitions and create new protective MBR
yes
n       # add a new partition
enter    # partition number 1 default
enter    # first sector 2048 default
+550M  # last sector
ef00     # efi system
x          # expert command
a          # set attribute
2          # legacy BIOS bootable
enter
enter
w          # Write new GUID partition table
yes
enter
sudo mkfs.vfat /dev/sdc/

mounted drive /dev/sdc1 to /mnt/sdc1

sudo mkdir /mnt/sdc1/EFI
sudo mkdir /mnt/sdc1/EFI/Linux

sudo extlinux -i /mnt/sdc1/EFI/Linux

sudo cp /usr/local/share/syslinux/efi64/syslinux.efi /mnt/sdc1/EFI/Linux/BOOTX64.EFI

sudo dd if=/usr/local/share/syslinux/gptmbr.bin of=/dev/sdc bs=440 count=1

sudo cp /usr/local/share/syslinux/efi64/libutil.c32 /mnt/sdc1/EFI/Linux
sudo cp /usr/local/share/syslinux/efi64/libcom32.c32 /mnt/sdc1/EFI/Linux
sudo cp /usr/local/share/syslinux/efi64/vesamenu.c32 /mnt/sdc1/EFI/Linux
sudo cp /usr/local/share/syslinux/libutil.c32 /mnt/sdc1
sudo cp /usr/local/share/syslinux/libcom32.c32 /mnt/sdc1
sudo cp /usr/local/share/syslinux/vesamenu.c32 /mnt/sdc1
sudo cp /mnt/sr0/boot/corepure64.gz /mnt/sdc1
sudo cp /mnt/sr0/boot/vmlinuz64 /mnt/sdc1

blkid -s UUID /dev/sdc1          # Gives me the UUID for the boot partition

sudo nano /mnt/sdc1/syslinux.cfg

UI vesamenu.c32
DEFAULT tc
LABEL tc
MENU LABEL Tiny Core
KERNEL /vmlinuz64
INITRD /corepure64.gz 
APPEND quiet waitusb=5:tce=UUID="58D6-C6F7"

sudo cp /mnt/sdc1/syslinux.cfg /mnt/sdc1/EFI/Linux

NOW I first UnMount /mnt/sdc1 and then run tc-install and choose
Frugal
Excisting Partition
sdc1
I DeSelect both "Mark Partition Active" and "Install boot loader"
Under Formatting Options I choose: No formatting, use existing.

When done I mount the /dev/sdc1 to /mnt/sdc1 and the tree looks like this

/mnt/sdc1
|-- EFI
|    `-- Linux
|        |-- BOOTX64.EFI
|        |-- libcom32.c32
|        |-- libutil.c32
|        |-- syslinux.cfg
|        |-- vesamenu.c32
|-- corepure64.z
|-- libcom32.c32
|-- libutil.c32
|-- syslinux.cfg
|-- tce
|    |-- boot
|    |     |-- corepure64.gz    
|    |     |-- extlinux
|    |     `-- vmlinuz64
|    |-- mydata.tgz
|    |-- onboot.lst
|    `-- optional
|          |--HERE IS ALOT OF FILES
|-- vesamenu.c32
`-- vmlinuz64

As you see I only have one partition that is 550MB with EFI so I guess this should be easy or...

not

coreplayer2 · « **Reply #11 on:** January 05, 2019, 10:06:47 PM »

Quote from: hamak on January 05, 2019, 10:05:56 AM

Can someone give me a tree output of the file structure of a working UEFI USB Drive?

Sure, but I remind you this is Grub2. Sorry this USB example which is a little complex..

"FAT32 Boot Partition" from my currently working USB thumb drive booted using UEFI via grub2

Code: [Select]

/mnt/sdb1 $ tree *  
EFI
`-- BOOT
    |-- BOOTX64.EFI
    `-- grub
        |-- fonts
        |   `-- unicode.pf2
        |-- grub.cfg
        |-- grub.cfg.bak
        |-- grubenv
        |-- locale
        `-- x86_64-efi
            `-- "Grub UEFI modules"
boot
|-- grub
|   |-- fonts
|   |   `-- unicode.pf2
|   |-- grubenv
|   |-- i386-pc
|   |   |-- "Grub Legacy modules"
|   `-- locale
|-- modules-41410.gz
|-- modules-41910.gz
|-- modules-4817.gz
|-- modules64-41410.gz
|-- modules64-41910.gz
|-- modules64-4817.gz
|-- rootfs-10.gz
|-- rootfs-10A2.gz
|-- rootfs-821.gz
|-- rootfs-90.gz
|-- rootfs64-10.gz
|-- rootfs64-10A2.gz
|-- rootfs64-821.gz
|-- rootfs64-90.gz
|-- vmlinuz-41410
|-- vmlinuz-41910
|-- vmlinuz-4817
|-- vmlinuz64-41410
|-- vmlinuz64-41910
`-- vmlinuz64-4817

Note the naming convention which is the UEFI standard (and is expected AFAIK)

Code: [Select]

EFI
`-- BOOT
    |-- BOOTX64.EFI

Current persistent storage partition (which needs to be ext2/4)

Code: [Select]

/mnt/sdb3 $ tree -L 2
.
|-- home
|   `-- tc
|-- opt
|   |-- alsa
|   |-- backgrounds
|   |-- bootlocal.sh
|   |-- bootlocal.sh.bak
|   |-- bootsync.sh
|   |-- bootsync.sh.bak
|   |-- eth0.sh
|   |-- passwd
|   |-- shadow
|   |-- shadow.bak
|   |-- shutdown.sh
|   |-- tcemirror
|   `-- wlan0.sh
|-- tc10-x86
|   |-- firstrun
|   |-- getOnboot.sh
|   |-- onboot.lst
|   |-- ondemand
|   |-- optional
|   |-- provides.db
|   `-- xwbar.lst
|-- tc10-x86_64
|   |-- OnbootPure64Def.lst
|   |-- firstrun
|   |-- onboot.lst
|   |-- ondemand
|   |-- optional
|   |-- provides.db
|   `-- xwbar.lst
|-- tc8-x86
|   |-- defonboot.lst
|   |-- defonboot.lst.bak
|   |-- firstrun
|   |-- mydata_tc7x86.Vesa.tgz
|   |-- mydata_tc7x86.Xorg.tgz
|   |-- mydata_tc8x86.Vesa.tgz
|   |-- onboot.lst
|   |-- onboot_Core64.lst
|   |-- onboot_Core64.lst.bak
|   |-- onboot_Core64.lst~
|   |-- onboot_x86_NvidiaCompile.lst
|   |-- onboot_x86_Xorg.lst
|   |-- onboot_x86_Xorg.lst.bak
|   |-- onboot_x86_Xvesa.lst
|   |-- ondemand
|   |-- optional
|   |-- provides.db
|   |-- submit
|   `-- xwbar.lst
|-- tc8-x86_64
|   |-- OnbootPure64Def.lst
|   |-- firstrun
|   |-- mydataCorePure64.tgz
|   |-- mydataCorePure64_bak.tgz
|   |-- onboot.lst
|   |-- onboot_CorePure64.lst
|   |-- onboot_CorePure64.lst.bak
|   |-- ondemand
|   |-- optional
|   |-- provides.db
|   |-- submitqc
|   |-- testOnboot64.lst
|   |-- xbase.lst
|   `-- xwbar.lst
|-- tc9-x86
|   |-- copy2fs.lst
|   |-- defonboot.lst
|   |-- defonboot.lst.bak
|   |-- firstrun
|   |-- mydata_tc7x86.Vesa.tgz
|   |-- mydata_tc7x86.Xorg.tgz
|   |-- mydata_tc8x86.Vesa.tgz
|   |-- mydata_tc9x86.Nvidia.tgz
|   |-- onboot.lst
|   |-- onboot_Core64.lst
|   |-- onboot_Core64.lst.bak
|   |-- onboot_Core64.lst~
|   |-- onboot_Core64_Xfbdev.lst
|   |-- onboot_x86_ISO_Style.lst
|   |-- onboot_x86_Nvidia.lst
|   |-- onboot_x86_Nvidia.lst.bak
|   |-- onboot_x86_NvidiaCompile.lst
|   |-- onboot_x86_NvidiaMinimal.lst
|   |-- onboot_x86_NvidiaMinimal.lst.bak
|   |-- onboot_x86_Xorg.lst
|   |-- onboot_x86_Xorg.lst.bak
|   |-- onboot_x86_Xvesa.lst
|   |-- ondemand
|   |-- optional
|   |-- provides.db
|   |-- submit
|   `-- xwbar.lst
|-- tc9-x86_64
|   |-- OnbootPure64Def.lst
|   |-- firstrun
|   |-- mydata.tgz
|   |-- mydataCorePure64
|   |-- mydataCorePure64.tgz
|   |-- mydataCorePure64_bak.tgz
|   |-- mydata_tc7x86.Xorg.tgz
|   |-- onboot.lst
|   |-- onboot_CorePure64.lst.bak
|   |-- onboot_CorePure64_Nvidia.lst
|   |-- onboot_CorePure64_Xfbdev.lst
|   |-- onboot_x86_64_NvidiaCompile.lst
|   |-- onboot_x86_64_NvidiaCompile.lst.bak
|   |-- onboot_x86_64_NvidiaLoadTest.lst
|   |-- ondemand
|   |-- optional
|   |-- optionalXfbdev.tcz
|   |-- provides.db
|   |-- submit
|   |-- submitqc
|   |-- testOnboot64.lst
|   |-- xbase.lst
|   `-- xwbar.lst

And even more sorry for this complex config file...

Code: [Select]

insmod part_msdos
insmod fat
insmod ext2
loadfont unicode
insmod efi_gop
insmod efi_uga
insmod font
insmod gfxterm
set gfxmode=auto
set gfxterm_font=unicode
set gfxpayload=keep
terminal_output gfxterm

#Timeout for menu
set default=5
set timeout=5


menuentry "*** TC-8-x86 (Xorg on USB)" {
search --no-floppy --fs-uuid --set=root B854-8FE0
linux /boot/vmlinuz-4817 vmalloc=256MB tz=GMT noswap loglevel=3 waitusb=5:UUID="b313c2c4-fedf-4c44-bf42-6a6fca54b311" tce=UUID="b313c2c4-fedf-4c44-bf42-6a6fca54b311"/tc8-x86 opt=UUID="b313c2c4-fedf-4c44-bf42-6a6fca54b311" home=UUID="b313c2c4-fedf-4c44-bf42-6a6fca54b311" lst=onboot_x86_Xorg.lst mydata=mydata_tc7x86.Xorg
initrd /boot/rootfs-821.gz /boot/modules-4817.gz
}

menuentry "*** TC-8-Core64 (on USB)" {
search --no-floppy --fs-uuid --set=root B854-8FE0
linux /boot/vmlinuz64-4817 tz=GMT loglevel=3 noswap waitusb=5:UUID="b313c2c4-fedf-4c44-bf42-6a6fca54b311" tce=UUID="b313c2c4-fedf-4c44-bf42-6a6fca54b311"/tc8-x86 opt=UUID="b313c2c4-fedf-4c44-bf42-6a6fca54b311" home=UUID="b313c2c4-fedf-4c44-bf42-6a6fca54b311" lst=onboot_Core64.lst
initrd /boot/rootfs-821.gz /boot/modules64-4817.gz
}

menuentry "*** TC-8-Corepure64 (on USB)" {
search --no-floppy --fs-uuid --set=root B854-8FE0
linux /boot/vmlinuz64-4817 noswap tz=GMT loglevel=3 waitusb=5:UUID="b313c2c4-fedf-4c44-bf42-6a6fca54b311" tce=UUID="b313c2c4-fedf-4c44-bf42-6a6fca54b311"/tc8-x86_64 opt=UUID="b313c2c4-fedf-4c44-bf42-6a6fca54b311" home=UUID="b313c2c4-fedf-4c44-bf42-6a6fca54b311" lst=onboot_CorePure64.lst mydata=mydataCorePure64
initrd /boot/rootfs64-821.gz /boot/modules64-4817.gz
}

menuentry "*** TC-8-x86 (Test on USB)" {
search --no-floppy --fs-uuid --set=root B854-8FE0
linux /boot/vmlinuz-4817 tz=GMT vmalloc=256MB noswap loglevel=3 waitusb=5:UUID="b313c2c4-fedf-4c44-bf42-6a6fca54b311" tce=UUID="b313c2c4-fedf-4c44-bf42-6a6fca54b311"/tc8-x86 home=UUID="b313c2c4-fedf-4c44-bf42-6a6fca54b311" lst=defonboot.lst norestore
initrd /boot/rootfs-821.gz /boot/modules-4817.gz
}

menuentry "*** TC-9-x86 (Xvesa on USB)" {
search --no-floppy --fs-uuid --set=root B854-8FE0
linux /boot/vmlinuz-41410 tz=GMT loglevel=3 noswap waitusb=5:UUID="b313c2c4-fedf-4c44-bf42-6a6fca54b311" tce=UUID="b313c2c4-fedf-4c44-bf42-6a6fca54b311"/tc9-x86 opt=UUID="b313c2c4-fedf-4c44-bf42-6a6fca54b311" home=UUID="b313c2c4-fedf-4c44-bf42-6a6fca54b311" lst=onboot_x86_Xvesa.lst
initrd /boot/rootfs-90.gz /boot/modules-41410.gz
}

menuentry "*** TC-9-x86 (Nvidia on USB)" {
search --no-floppy --fs-uuid --set=root B854-8FE0
linux /boot/vmlinuz-41410 vmalloc=384MB tz=GMT noswap loglevel=3 waitusb=5:UUID="b313c2c4-fedf-4c44-bf42-6a6fca54b311" tce=UUID="b313c2c4-fedf-4c44-bf42-6a6fca54b311"/tc9-x86 opt=UUID="b313c2c4-fedf-4c44-bf42-6a6fca54b311" home=UUID="b313c2c4-fedf-4c44-bf42-6a6fca54b311" lst=onboot_x86_Nvidia.lst mydata=mydata_tc9x86.Nvidia
initrd /boot/rootfs-90.gz /boot/modules-41410.gz
}

menuentry "*** TC-9-x86 (NvidiaMinimal on USB)" {
search --no-floppy --fs-uuid --set=root B854-8FE0
linux /boot/vmlinuz-41410 vmalloc=384MB tz=GMT noswap loglevel=3 syslog waitusb=5:UUID="b313c2c4-fedf-4c44-bf42-6a6fca54b311" tce=UUID="b313c2c4-fedf-4c44-bf42-6a6fca54b311"/tc9-x86 opt=UUID="b313c2c4-fedf-4c44-bf42-6a6fca54b311" home=UUID="b313c2c4-fedf-4c44-bf42-6a6fca54b311" lst=onboot_x86_NvidiaMinimal.lst mydata=mydata_tc9x86.Nvidia
initrd /boot/rootfs-90.gz /boot/modules-41410.gz
}

menuentry "*** TC-9-x86 (Xorg on USB)" {
search --no-floppy --fs-uuid --set=root B854-8FE0
linux /boot/vmlinuz-41410 vmalloc=384MB tz=GMT noswap loglevel=3 waitusb=5:UUID="b313c2c4-fedf-4c44-bf42-6a6fca54b311" tce=UUID="b313c2c4-fedf-4c44-bf42-6a6fca54b311"/tc9-x86 opt=UUID="b313c2c4-fedf-4c44-bf42-6a6fca54b311" home=UUID="b313c2c4-fedf-4c44-bf42-6a6fca54b311" lst=onboot_x86_Xorg.lst
initrd /boot/rootfs-90.gz /boot/modules-41410.gz
}

menuentry "*** TC-9-Core64 (Xfbdev on USB)" {
search --no-floppy --fs-uuid --set=root B854-8FE0
linux /boot/vmlinuz64-41410 noswap tz=GMT loglevel=3 vga=891 waitusb=5:UUID="b313c2c4-fedf-4c44-bf42-6a6fca54b311" tce=UUID="b313c2c4-fedf-4c44-bf42-6a6fca54b311"/tc9-x86 opt=UUID="b313c2c4-fedf-4c44-bf42-6a6fca54b311" home=UUID="b313c2c4-fedf-4c44-bf42-6a6fca54b311" lst=onboot_Core64_Xfbdev.lst
initrd /boot/rootfs-90.gz /boot/modules64-41410.gz
}

menuentry "*** TC-9-Corepure64 (Nvidia on USB)" {
search --no-floppy --fs-uuid --set=root B854-8FE0
linux /boot/vmlinuz64-41410 noswap tz=GMT loglevel=3 waitusb=5:UUID="b313c2c4-fedf-4c44-bf42-6a6fca54b311" tce=UUID="b313c2c4-fedf-4c44-bf42-6a6fca54b311"/tc9-x86_64 opt=UUID="b313c2c4-fedf-4c44-bf42-6a6fca54b311" home=UUID="b313c2c4-fedf-4c44-bf42-6a6fca54b311" lst=onboot_CorePure64_Nvidia.lst
initrd /boot/rootfs64-90.gz /boot/modules64-41410.gz
}

menuentry "*** TC-9-Corepure64 (Xfbdev on USB)" {
search --no-floppy --fs-uuid --set=root B854-8FE0
linux /boot/vmlinuz64-41410 noswap tz=GMT loglevel=3 vga=891 waitusb=5:UUID="b313c2c4-fedf-4c44-bf42-6a6fca54b311" tce=UUID="b313c2c4-fedf-4c44-bf42-6a6fca54b311"/tc9-x86_64 opt=UUID="b313c2c4-fedf-4c44-bf42-6a6fca54b311" home=UUID="b313c2c4-fedf-4c44-bf42-6a6fca54b311" lst=onboot_CorePure64_Xfbdev.lst
initrd /boot/rootfs64-90.gz /boot/modules64-41410.gz
}

menuentry " TC-10-x86 Alpha(on USB)" {
search --no-floppy --fs-uuid --set=root B854-8FE0
linux /boot/vmlinuz-41910 vmalloc=384MB tz=GMT noswap loglevel=3 waitusb=5:UUID="b313c2c4-fedf-4c44-bf42-6a6fca54b311" tce=UUID="b313c2c4-fedf-4c44-bf42-6a6fca54b311"/tc10-x86 opt=UUID="b313c2c4-fedf-4c44-bf42-6a6fca54b311" home=UUID="b313c2c4-fedf-4c44-bf42-6a6fca54b311" 
initrd /boot/rootfs-10A2.gz /boot/modules-41910.gz
}

menuentry " TC-10-Corepure64 Alpha(on USB)" {
search --no-floppy --fs-uuid --set=root B854-8FE0
linux /boot/vmlinuz64-41910 noswap tz=GMT loglevel=3 vga=891 waitusb=5:UUID="b313c2c4-fedf-4c44-bf42-6a6fca54b311" tce=UUID="b313c2c4-fedf-4c44-bf42-6a6fca54b311"/tc10-x86_64 opt=UUID="b313c2c4-fedf-4c44-bf42-6a6fca54b311" home=UUID="b313c2c4-fedf-4c44-bf42-6a6fca54b311" 
initrd /boot/rootfs64-10A2.gz /boot/modules64-41910.gz
}

menuentry "*** TC-9-x86 (NvidiaCompile)" {
search --no-floppy --fs-uuid --set=root B854-8FE0
linux /boot/vmlinuz-41410 vmalloc=384MB tz=GMT loglevel=3 waitusb=5:UUID="b313c2c4-fedf-4c44-bf42-6a6fca54b311" tce=UUID="b313c2c4-fedf-4c44-bf42-6a6fca54b311"/tc9-x86 opt=UUID="b313c2c4-fedf-4c44-bf42-6a6fca54b311" home=UUID="b313c2c4-fedf-4c44-bf42-6a6fca54b311" lst=onboot_x86_NvidiaCompile.lst
initrd /boot/rootfs-90.gz /boot/modules-41410.gz
}

menuentry "*** TC-9-x86_64 (NvidiaCompile)" {
search --no-floppy --fs-uuid --set=root B854-8FE0
linux /boot/vmlinuz64-41410 tz=GMT loglevel=3 waitusb=5:UUID="b313c2c4-fedf-4c44-bf42-6a6fca54b311" tce=UUID="b313c2c4-fedf-4c44-bf42-6a6fca54b311"/tc9-x86_64 opt=UUID="b313c2c4-fedf-4c44-bf42-6a6fca54b311" home=UUID="b313c2c4-fedf-4c44-bf42-6a6fca54b311" lst=onboot_x86_64_NvidiaCompile.lst
initrd /boot/corepure64-90.gz
}

menuentry "*** TC-9-x86_64 (NvidiaLoadTest)" {
search --no-floppy --fs-uuid --set=root B854-8FE0
linux /boot/vmlinuz64-41410 tz=GMT loglevel=3 base waitusb=5:UUID="b313c2c4-fedf-4c44-bf42-6a6fca54b311" tce=UUID="b313c2c4-fedf-4c44-bf42-6a6fca54b311"/tc9-x86_64 opt=UUID="b313c2c4-fedf-4c44-bf42-6a6fca54b311" home=UUID="b313c2c4-fedf-4c44-bf42-6a6fca54b311" 
initrd /boot/corepure64-90.gz
}

menuentry "System restart" {
	echo "System rebooting..."
	reboot
}

hamak · « **Reply #12 on:** January 06, 2019, 08:53:33 AM »

Thank you very much and it looks like I got something...

It booted with this text now

Code: [Select]

GNU GRUB version 2.02
Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists possibe device or filecompletions

grub>

I will try some more later and see if it will work

I think this means that is has booted from UEFI and into grub and stopped

coreplayer2 · « **Reply #13 on:** January 06, 2019, 09:17:18 AM »

Quote from: hamak on January 06, 2019, 08:53:33 AM

Thank you very much and it looks like I got something...

It booted with this text now

Code: [Select]
GNU GRUB version 2.02 Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists possibe device or filecompletions grub>
I will try some more later and see if it will work
I think this means that is has booted from UEFI and into grub and stopped

Exactly, either Grub can not find the config file or the config file provided information is not correct. When this happens grub reverts to its command line to allow manual configuration.

Sent from my iPhone using Tapatalk

hamak · « **Reply #14 on:** January 06, 2019, 01:28:42 PM »

Thank you very much coreplayer2 !!!

It now successfully booted grub and TinyCore x64 and the error was that I have repartitioned multiple times and reinstalled grub multiple times and the UUID had changed and

The tree was exacly what I needed because I got the whole picture of the file structure.

Now I must try to make this work with syslinux

Tiny Core Linux

News:

Author Topic: TinyCorePure64 and UEFI boot (Read 29181 times)

hamak

TinyCorePure64 and UEFI boot

polikuo

Re: TinyCorePure64 and UEFI boot

hamak

Re: TinyCorePure64 and UEFI boot

polikuo

Re: TinyCorePure64 and UEFI boot

hamak

Re: TinyCorePure64 and UEFI boot

hamak

Re: TinyCorePure64 and UEFI boot

Rich

Re: TinyCorePure64 and UEFI boot

polikuo

Re: TinyCorePure64 and UEFI boot

hamak

Re: TinyCorePure64 and UEFI boot

coreplayer2

Re: TinyCorePure64 and UEFI boot

hamak

Re: TinyCorePure64 and UEFI boot

coreplayer2

Re: TinyCorePure64 and UEFI boot

hamak

Re: TinyCorePure64 and UEFI boot

coreplayer2

TinyCorePure64 and UEFI boot

hamak

Re: TinyCorePure64 and UEFI boot