Tiny Core Extensions > TCE Tips & Tricks
Howto make a legacy bios/uefi dual boot usb stick with grub2
labeas:
> Please post your grub.cfg so that we can try to help you.
===================
=> move stik from dud W10 Laptop to W8.1 Laptop:
=> locate, mount & list Dir/S
=> locate & list grub.cfg
==> Some extra files, Dirs are omitted from the listings.
--- Code: ----> ls -l /mnt/sde2/EFI/BOOT/ ==
-rwxrwxrwx 1 root root 121344 May 16 15:59 BOOTX64.EFI
drwxrwxrwx 6 root root 4096 May 16 16:24 grub
--- End code ---
--- Code: ----> ls -l /mnt/sde2/EFI/BOOT/grub/ ==
drwxrwxrwx 2 root root 4096 May 16 15:59 fonts
-rwxrwxrwx 1 root root 1048 May 24 16:12 grub.cfg
-rwxrwxrwx 1 root root 1288 May 16 16:26 grub.cfgBak
-rwxrwxrwx 1 root root 1024 May 16 15:59 grubenv
drwxrwxrwx 2 root root 20480 May 16 16:03 i386-pc
drwxrwxrwx 2 root root 4096 May 16 15:59 locale
drwxrwxrwx 2 root root 20480 May 16 15:59 x86_64-efi
--- End code ---
--- Code: ----> cat /mnt/sde2/EFI/BOOT/grub/grub.cfg ==
loadfont unicode
insmod efi_gop
set gfxmode=800x600x32
set gfxpayload=keep
set gfxterm_font=unicode
terminal_output gfxterm
search --no-floppy --fs-uuid --set=root 5c4d3b5d-47c9-4e67-8403-4aa4eb9fb767
menuentry "core" {
linux /boot/vmlinuz quiet text tce=UUID="5c4d3b5d-47c9-4e67-8403-4aa4eb9fb767" waitusb=10:UUID="5c4d3b5d-47c9-4e67-8403-4aa4eb9fb767"
initrd /boot/rootfs.gz /boot/modules.gz
}
menuentry "core64" {
linux /boot/vmlinuz64 quiet text tce=UUID="5c4d3b5d-47c9-4e67-8403-4aa4eb9fb767" waitusb=10:UUID="5c4d3b5d-47c9-4e67-8403-4aa4eb9fb767"
initrd /boot/rootfs.gz /boot/modules64.gz
}
menuentry "corepure64" {
linux /boot/vmlinuz64 quiet text tce=UUID="5c4d3b5d-47c9-4e67-8403-4aa4eb9fb767"/tce64 waitusb=10:UUID="5c4d3b5d-47c9-4e67-8403-4aa4eb9fb767"
initrd /boot/rootfs64.gz /boot/modules64.gz
}
menuentry "corepure64 base" {
linux /boot/vmlinuz64 quiet text tce=UUID="5c4d3b5d-47c9-4e67-8403-4aa4eb9fb767"/tce64 waitusb=10:UUID="5c4d3b5d-47c9-4e67-8403-4aa4eb9fb767" base norestore
initrd /boot/rootfs64.gz /boot/modules64.gz
}
--- End code ---
-------------------------
I don't know how this posting's line-len-overflow will work?
[EDIT]: Added code tags. Rich
PDP-8:
Hey, it works! Thanks Juanito..
I used CFDISK for the formatter and had no problem.
Tip: after formatting with mkfs, I removed the stick so the system would properly recognize the new partitions. THEN I proceeded with mounting properly for the grub install. I think everyone knows this, but this tripped me up before. :)
I actually turned this into a Tinycore / 64 setup with some tips from coreplayer2 - thanks man.
So happy I scarfed an entire pizza. :)
labeas:
=> /mnt/sda2/Tmp/Forum/CagedAces 2019 Aug 13
I'm used to acessing the whole file-tree, which includes ALL the
plugged devices in the USBhub, and the 4-partition Microsoft hardDrive
when running TC64ver7.2 from a USBstik via the <APTIO 2015> laptop.
Now I've managed to boot only the 2nd-listing-below of the 5 grub.cfg
entries. And install gpm & mc and get 1+11=12 VTs via `sudo openvt`
on the problematic <APTIO 2018> laptop.
Q: Why does `fdisk -l` & other tests NOT see the Microsoft hardDrive ?
--- Code: ---root@box:/home/tc# ls /mnt
mmcblk0p1 sda1 sda2 <-sda=USBstik;mmcblk0p1=equipped SDcard
root@box:/home/tc# dmesg | grep sd
sees sda* PLUS:...
sd 1:0:0:0: [sdb] 0 512-byte logical blocks: (0 B/0 B)
sd 1:0:0:0: [sdb] 0-byte physical blocks
sd 1:0:0:0: [sdb] Test WP failed, assume Write Enabled
sd 1:0:0:0: [sdb] Asking for cache data failed
sd 1:0:0:0: [sdb] Assuming drive cache: write through
sd 1:0:0:0: [sdb] Attached SCSI disk
--- End code ---
OK, maybe sdb is the Microsoft hardDrive. I didn't notice that previousy.
When I can afford to take the USBhub from the <APTIO 2015> laptop,
I'll test if this system CAN see other devices, than its own-booted.
We often must "put the research to WRITNG" to spot our mistakes?
Now I'll boot to Win10; to post this FAT text from partn2 of our
<how to boot UEFI via grub> USBstik. Q: does `halt -n` <autoUnmount> ?
---> listing PASTED via mc & gpm:-
--- Code: ---/mnt/sda2/EFI/BOOT/grub/grub.cfg 1154/1200 96%loadfont unicode
insmod efi_gop
set gfxmode=800x600x32
set gfxpayload=keep
set gfxterm_font=unicode
terminal_output gfxterm
search --no-floppy --fs-uuid --set=root bfe6116c-473a-4ee9-bbac-3638039dc9ad
menuentry "core" {
linux /boot/vmlinuz quiet text tce=UUID="bfe6116c-473a-4ee9-bbac-3638039dc9ad" waitusb=10:UUID="bfe6116c-473a-4ee9-bbac-3638039dc9ad"
initrd /boot/rootfs.gz /boot/modules.gz
}
menuentry "coreB" { <-- ONLY THIS entry works OK
linux /boot/vmlinuz waitusb=10:UUID="bfe6116c-473a-4ee9-bbac-3638039dc9ad"
initrd /boot/rootfs.gz /boot/modules.gz
}
menuentry "core64" {
linux /boot/vmlinuz64v10 quiet text tce=UUID="bfe6116c-473a-4ee9-bbac-3638039dc9ad" waitusb=10:UUID="bfe6116c-473a-4ee9-bbac-3638039dc9ad"
initrd /boot/rootfs.gz /boot/modules64.gz
}
--- End code ---
...
PS. I notice how the smart-arse web-based forum FALSELY wraps code-lines.
NNTP of 25 years ago is far superior. Too late to change now.
Whereas we wrote "27"; todays FB, twitter kiddie write "twenty seven".
[EDIT]: Added code tags and corrected Microsoft spelling. Rich
Rich:
Hi labeas
Please refrain from your "clever" spelling of Microsoft. If you feel a need to bash them, take it elsewhere. I'm sure there are sites
out there that specialize in that.
--- Quote from: labeas on August 13, 2019, 02:15:15 AM --- ... Q: Why does `fdisk -l` & other tests NOT see the Microsoft hardDrive ? ...
--- End quote ---
Since you didn't show the results of fdisk -l we don't know what it saw. If your disk has GPT partitions, you probably need gdisk.
--- Quote ---PS. I notice how the smart-arse web-based forum FALSELY wraps code-lines.
--- End quote ---
If your line is longer than the display area it wraps at the last whitespace that still fits on the line. It will not wrap in the middle of a
word. If it encounters this and it's too long to still fit on the current line:
--- Code: ---waitusb=10:UUID="5c4d3b5d-47c9-4e67-8403-4aa4eb9fb767"
--- End code ---
it will wrap that to the next line because it contains no whitespace. If you use code tags, it will wrap in the editing window, but
when you click the Preview button, you'll see it in a code box with a horizontal scrollbar on the bottom.
labeas:
This is the first & last time I use a FULL-BROWSER for the TCforum.
And now I see were the verbose/redundant:jsGenerated "Code: " comes from.
It seems absurd for TINYcore, which hasn't even got: awk, bash, X to want to ape
the WinTel/Bigboys? And we'd better solve this UEFI-booting, since there's a whole
flood of ChineseCheapo UEFI WinTel laptops coming.
---The following seems inconsistent with previous instructions:--
>installing manually is quite easy if you check off the following list items & notes below
>...
>* that Grub2 is installed from a 64bit operating system, with the following directory paths
>* sd(x)1/EFI/BOOT
?????????? On the USBstik which mostly works, nonTClinux sees:---
=> /mnt/sdg2/EFI/BOOT/grub/ =fonts/ grub.cfg grubenv i386-pc/ x86_64-efi/
Ie. -/EFI/BOOT is on the 2nd [FAT] partition, not the 1st [linux].
How can I continue fumbling in the dark; or has this instruction-error been corrected?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version