WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: How to transfer proven TC64Ver7 to EFI:grub Laptop?  (Read 1493 times)

Offline labeas

  • Sr. Member
  • ****
  • Posts: 266
How to transfer proven TC64Ver7 to EFI:grub Laptop?
« on: October 20, 2020, 09:55:34 AM »
Trying to get TC64wifi working on a problematic <EFI>laptop has failed,
so I'll try SIMPLIFYING: by <transfering> the wifi-working TC64Ver7
from the other laptop.

  The working/proven isolinux.cfg entry:---
LABEL tcPersistent
MENU LABEL Boot TinyCorePure64PersistentB
TEXT HELP
Boot TinyCorePure64 with Embedded X/GUI extensions.
Boot media is removable. Use TAB to edit options for specific needs.
ENDTEXT
KERNEL /boot/vmlinuz64 waitusb=15 tce=sdb1
INITRD /boot/corepure64.gz
APPEND loglevel=3 cde vga=788
       must be translated to a grub.cfg similar entry:---
menuentry "SDTC64 UUID=6264-3564" {
linux /boot64/vmlinuz64 waitusb=10:UUID="6264-3564"
initrd /boot64/rootfs64.gz /boot64/modules64.gz
}
-----------
AFAIK normal linux systems boot via: kernel followed by initrd?
Does the syslinuxVer7's corepure64.gz correspond to grub's rootfs64.gz?
The sizes are similar: 6M8 & 8M6.
Is modules64.gz just for grub's modules ?
Version7's <cde Dir> will just be copied to the new <UUID>/cde.
Are there any obvious errors or suggestions here?
---
PS. the other complication is that: the problematic laptop has SDcard,
but is not seen by <EFIbootMenu>. So must boot from USBstik, which
occupies NEEDED socket.
Since grub is more-powerfull than EFI: will it find the UUiD/SDcard ?
  Must now boot to M$pook to post this tedious.....

--TIA.

Offline polikuo

  • Hero Member
  • *****
  • Posts: 710
Re: How to transfer proven TC64Ver7 to EFI:grub Laptop?
« Reply #1 on: October 20, 2020, 09:22:29 PM »
AFAIK normal linux systems boot via: kernel followed by initrd?
Does the syslinuxVer7's corepure64.gz correspond to grub's rootfs64.gz?
The sizes are similar: 6M8 & 8M6.
Is modules64.gz just for grub's modules ?
core.gz = modules.gz + rootfs.gz
corepure64.gz = modules64.gz + rootfs64.gz
It doesn't matter which bootloader you're using.

SYSLINUX:
KERNEL /boot/vmlinuz64
INITRD /boot/corepure64.gz
or
INITRD /boot/modules64.gz,/boot/rootfs64.gz
concatenate with a comma

GRUB2:
linux /boot64/vmlinuz64
initrd /boot/corepure64.gz
or
initrd /boot64/rootfs64.gz /boot64/modules64.gz
space is fine

PS. the other complication is that: the problematic laptop has SDcard,
but is not seen by <EFIbootMenu>. So must boot from USBstik, which
occupies NEEDED socket.
Since grub is more-powerfull than EFI: will it find the UUiD/SDcard ?
Most likely not.
I've seen stubborn laptops refuse to boot from SD cards, sometimes from USBs.
Here's an abbreviate version of how a PC usually boot:
power up -> hardware check -> UEFI / LegacyMBR (<EFIbootMenu> here) -> find a storage media (HDD,USB) -> look for boot manager -> syslinux/grub -> search for files (anywhere should be fine) -> kernel booting...
Since your <EFIbootMenu> can't see your SD card, it doesn't matter which boot manager you're using. (syslinux / grub)
It's a Mother Board problem.