Tiny Core Base > TCB Talk

Booting 32bit TC from 64bit efi boots to blank screen with underscore

(1/14) > >>

jimmyjohn:
I am trying to boot the standard Tiny Core 10.1 image from my mini-PC which only has 64bit UEFI available as a boot option.  I am able to get it to boot, but once booting is complete I only see a blank/black screen with an underscore in the top left corner.  From this screen I am not able to input any commands or take any actions except that by pressing Ctrl-Alt-Delete twice I am able to begin and then watch the text based shutdown process.

Is it possible to correctly boot the 32bit version from a 64bit EFI?  If so, what should I try next to get it to work correctly?

coreplayer2:

--- Quote from: jimmyjohn on July 06, 2019, 10:30:12 AM ---...
Is it possible to correctly boot the 32bit version from a 64bit EFI?  If so, what should I try next to get it to work correctly?

--- End quote ---
Hello jimmyjohn
Of course it is!!

64 bit EFI is the correct way to install EFI regardless of what OS the boot manager is booting



This screenshot shows the 64bit EFI and TC 10.1 32 bit system I’m currently booted to

You should create a new installation as in the code below, not copy a bootx64.efi bootloader from another system and expect it to work.
I never have any problems with EFI installations because I use this command to ensure a correct creation and installation of bootx64.efi bootloader

--- Code: ---sudo grub-install --target=x86_64-efi --boot-directory=/mnt/sdc2/EFI/BOOT --efi-directory=/mnt/sdc2 --removable
--- End code ---

Here's a basic grub2 config file with Home, OPT and TCE persistance

--- Code: ---insmod part_gpt
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=0
set timeout=5


menuentry "*** TC-10-Tinycore (on USB)" {
search --no-floppy --fs-uuid --set=root B854-8FE0
linux /boot/vmlinuz noswap tz=GMT 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.gz /boot/modules.gz
}

menuentry "Windows 10" --class windows --class os {
search --fs-uuid --no-floppy --set=root DE2F-EF34
chainloader (${root})/EFI/Microsoft/Boot/bootmgfw.efi
}


--- End code ---


Additionally, are you attempting to boot from an ISO or a real installation?

Sent from my iPhone using Tapatalk

jimmyjohn:
I 'burned' the ISO to a USB and am booting from that.  It works when I burn and boot CorePure64, but it does not work when I do the same with the standard TC image.  However, even with the CorePure64 image, I have been using the bootx64.efi from the most recent Ubuntu Puppy Linux (bionic) - (EDIT:  because the bootx64.efi from the CorePure64 image does not work for me on any of my machines).  I have not tried installing it manually yet, I suppose I will give it a try.

curaga:
That sounds like an incompatibility with Xvesa. When you get to that underscore, see if ctrl-alt-backspace helps. Alternatively boot with the "text" bootcode.

Corepure64 uses Xfbdev, and you can also install Xorg as the X server.

jimmyjohn:
ctrl-alt-backspace didn't work.  I am, however able to boot into the textbased terminal.

Navigation

[0] Message Index

[#] Next page