Tiny Core Extensions > TCE Tips & Tricks

Howto make a legacy bios/uefi dual boot usb stick with grub2

<< < (2/11) > >>

Arii:
Hi, not sure what the necro-posting policy is here but given the relevance I decided to forgo it.

Upon loading "grub2-multi", the directories for x86 aren't actually there, only the i386 ones... I'm assuming they're not in a separate package because it probably would've been mentioned by now. Is something wrong with how I've gone about this or do I need to acquire it from somewhere else?

Juanito:
the i386 files are the equivalent of x86 ones, no?

Misalf:
Hi Arii,
I believe  i386-pc  is pretty much what you're looking for. As in i286, i386, i486, i586 ... = x86.
While this version of grub2 will boot on CPUs compatible with i386 and above, it won't on i286 and below, thus the strict naming.

labeas:
I didn't realise that this thread which was started in 2015, could be continued
in 2019!
My [possibly wrong] understanding of the STRUCTURE of this project is:
* Works only once the <UEFI security-lock> is overcome.
*  grub2-multi.tcz is installed.
    Does `man grub2-multi` exist; or is it internal to TC only ?
* The 2015 example/documented <grub2-multi HOW2> lists 4 entries.
   To reduce the confusion I want to analyse only the 1st: "core".
* The various versions of the <grub family>, list <global-vars / parameters>
  at the listing-start: which apply to all of the following entries.
   The grub2-multi that I'm trying to use: fails to responde to kybrd;
   showing: <the good 3-line-logo> plus:
     tc@box:~$
     with an appropriately FLASHING CURSOR;
     which to me, suggests that grub2-multi's kybrd-driver is bad.
------------
THIS laptop which runs TC64ver8, overcomes the UEFI/restiction problem by:
 navigation to the "Aptio Setup Utility/boot"
 and <disabling the UEFI-restriction>.
The Intel-Atom-based W10 which I'm trying to USBstik-boot TC from, has
 a differnt/newer (2018) "Aptio Setup Utility/boot".
 Examining the W10's settings NOW: I'll reorder:
  "Boot Option Priorities" to
  "Boot Option #1     [UEFI: SanDisk, Part...]"
!! Interestingly: it knows/shows that the USBstik has partn2 for booting;
and AFAIR it showed that my 32bitDebian7-stik used Partn-3.
  So a lot of the system seems to be working ?

What test can I do to help find out why <tc@box:~$ & Flashing cursor>
 doesn't respond to kybrd ?

Juanito:
The extension is called grub2-multi because it contains both i386-pc and x86_64-efi files.

Please post your grub.cfg so that we can try to help you.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version