grub settings

[coreplayer2]

http://forum.tinycorelinux.net/index.php/topic,19364.msg119228.html#msg119228

I was looking for that link, probably should be in wiki??

@ punkgeek
If you follow juanito's guide found at that link you'll be set. 
But most likely the missing command (among other things) was

Code: [Select]

search --no-floppy --fs-uuid --set=root 196fcfb2-bd37-495d-b855-41f08201be7d
Obviously replacing the uuid for your install device uuid

[Iko113]

Same subject, similar (same?) problem: installation of grub2-multi according to instructions of Juanito in this thread (23/12/2015) fails with error:
"/usr/lib/grub/x86_64-efi/modinfo.sh doesn't exist. Please specify --target or --directory":   see attachment!
(see also citation "bugzilla.redhat.com/show_bug.cgi?id=1101352" "Chris Murphy 2014-06-30 16:47:43": "Looks like this is intentional...")
Any solution?

[Iko113]

installation of grub2-multi according to instructions of Juanito in this thread

Correction: in deviation of the instructions I made the USB stick with PartedMagic as GPT with partitions 1)ext4 and 2)DOS/UEFI since I need this to boot a Acer Aspire 7 with UEFI only.

[Juanito]

"/usr/lib/grub/x86_64-efi/modinfo.sh doesn't exist.

The file is at /usr/local/lib/grub/x86_64-efi/modinfo.sh - perhaps a script is calling it at the wrong location?

[Iko113]

"/usr/lib/grub/x86_64-efi/modinfo.sh doesn't exist.

The file is at /usr/local/lib/grub/x86_64-efi/modinfo.sh - perhaps a script is calling it at the wrong location?

The script I used is "sudo grub-install --target=x86_64-efi --boot-directory=/mnt/sdc2/EFI/BOOT --efi-directory=/mnt/SDC2 --removable". But the file in my case is at  /usr/local/lib/grub/i386-efi/modinfo.sh (created by grub2-multi?) (see attachment previous post). Can I change this location?

[Juanito]

If you use "--target=x86_64-efi", I presume /usr/local/lib/grub/x86_64-efi/modinfo.sh will be used.

In any case, both:

/usr/local/lib/grub/x86_64-efi/modinfo.sh
/usr/local/lib/grub/i386-pc/modinfo.sh

..are present in the grub2-multi extension.

[Iko113]

If you use "--target=x86_64-efi", I presume /usr/local/lib/grub/x86_64-efi/modinfo.sh will be used.

In any case, both:

/usr/local/lib/grub/x86_64-efi/modinfo.sh
/usr/local/lib/grub/i386-pc/modinfo.sh

..are present in the grub2-multi extension.

Thank you very much for your help. On my PC I have modinfo.sh both in i386-efi and in i386-pc, but not in x86_64-efi (this folder doesn't exist): see attachment. Can I use "--target=i386-efi" (or i386-pc) for grub-install?

[Juanito]

Ah - you're using the grub2-multi extension from the x86 repo - this thread is about the extension from the x86_64 repo.

I believe (I might be wrong) that i386-efi is only useful for old macs, which use 32-bit efi. For new macs and pcs, which use 64-bit (u)efi, you will need x86_64-efi supplied by the extension in the CorePure64 repo.

[Iko113]

For new macs and pcs, which use 64-bit (u)efi, you will need x86_64-efi supplied by the extension in the CorePure64 repo.

Is x86_64-efi also present in TinyCorePure64? Otherwise I'll have to start all over...

[curaga]

TinyCore is just Core with some extensions included, the repo is the same. Also note that you don't have to install the same system you installed grub with, you can create your usb stick with a live corepure64 edition and have it boot 32-bit core.

Some history with this, grub 0.97 could not be compiled 64-bit, so if your system was pure 64-bit, you needed to use a 32-bit system to install grub.

[Iko113]

For new macs and pcs, which use 64-bit (u)efi, you will need x86_64-efi supplied by the extension in the CorePure64 repo.

Sorry for all my questions and thank you for your patience. But my stick, made with TinycorePure64-9.0.iso, has i386-pc/modinfo.sh and not x86_64-efi: see attachment. My history: Stick (sdc) made with [GPT, sdc1 (ext4) and sdc2 (DOS/UEFI)]. Copy TinycorePure64-9.0.iso to sdc1 with dd. Copy Bootx64.EFI from sdc1 (efiboot.img) to sdc2/EFI/BOOT. Grub.cfg made at  mnt/sdc2/EFI/BOOT/grub (and also copied to.../grub/grub)(see same attachment). But when I try to boot from this stick, I boot into the grub screen, not into TC?? Problem with grub.cfg? Maybe I should go the ubuntu-way like suggested in "Tiny Core Linux » Tiny Core Base » TCB Talk » Frugal install on new laptop (UEFI-BIOS trouble)?

[Rich]

Hi Iko113
Not related to your grub problem, but why are you including the  cde  boot code?

[Iko113]

Hi Iko113
Not related to your grub problem, but why are you including the  cde  boot code?

I cannot reconstruct exactly what i did, but I copied the whole bootcode from a original grub.cfg that was present on sdc2/EFI/BOOT/grub after dd of TinycorePure64-9.0.iso to sdc (my usb-stick) or after a (failed)  "grub-install --target=x86_64-efi --boot-directory=/mnt/sdc2/EFI/BOOT --efi-directory=/mnt/sdc2 --removable".

[Iko113]

Hi Iko113
Not related to your grub problem, but why are you including the  cde  boot code?

More info: see attachment for the origin of cde. I suppose it is necessary to load the extensions in cde?

[Iko113]

For new macs and pcs, which use 64-bit (u)efi, you will need x86_64-efi supplied by the extension in the CorePure64 repo.

... My history: Stick (sdc) made with [GPT, sdc1 (ext4) and sdc2 (DOS/UEFI)]. Copy TinycorePure64-9.0.iso to sdc1 with dd. Copy Bootx64.EFI from sdc1 (efiboot.img) to sdc2/EFI/BOOT. Grub.cfg made at  mnt/sdc2/EFI/BOOT/grub...
But when I try to boot from this stick, I boot into the grub screen, not into TC??

Listing of the partitions in the grub prompt says "unknown filesystem". GParted error: e2fsprogs required (see annex 1 for another trial with ext2), although this was installed. Debian manpages says "some older kernels and older versions of e2fsprogs will not support file systems with this ext4 feature (64bit) enabled." (see annex 2). What now??