Tiny Core Base > Corepure64
legacy bios/uefi dual boot usb stick ?
labeas:
From: December 23, 2015; relating to the Topic:
> Howto make a legacy bios/uefi dual boot usb stick with grub2
> In case you need to boot tinycore from a usb stick on
> legacy bios and uefi machines.
I don't understand. This laptop needs to be stepped from Win8.1, to the
"UEFI Firmware Settings window" / "Aptio Setup Utility" to disable <I think
its the post-BIOS security which prevents BIOS insecurity>.
That's worked OK for 2 years, and is writing/posting this from TC64 - now.
But now I've also got a Win10 laptop, which has a different
"Aptio Setup Utility" window, which I can't get to boot my TC64 USBstiks.
Problem 2 is to get this <HOWto dual boot> working.
Following the instructoins seems OK until:-
> Copy the distribution files rootfs.gz, rootfs64.gz, modules.gz,
> modules64.gz, vmlinuz and vmlinuz64 to /mnt/sdc1/boot
I copied vmlinuz vmlinuz64 from /mnt/sdb1/boot/; but where are:
rootfs.gz, rootfs64.gz, modules.gz, modules64.gz ?
-> find / -name "rootfs*" =nX
Please help me to:
1. setup Win10 to boot my existing TC64 USBstiks.
2. make a legacy bios/uefi dual boot usb stick per December 23, 2015 article.
==crg
PS. powering up the new bios/uefi dual bootStik, looks good.
It reports the rootfs64 missing.
I've just scan-read the January thread re. UEFI booting laptop.
Rich:
Hi labeas
Next time post the link you are quoting:
http://forum.tinycorelinux.net/index.php/topic,19364.msg119228.html#msg119228
--- Quote ---I copied vmlinuz vmlinuz64 from /mnt/sdb1/boot/; but where are:
rootfs.gz, rootfs64.gz, modules.gz, modules64.gz ?
-> find / -name "rootfs*" =nX
--- End quote ---
You don't mention which version so here are links for TC10:
http://tinycorelinux.net/10.x/x86/release/distribution_files/
http://tinycorelinux.net/10.x/x86_64/release/distribution_files/
labeas:
> You don't mention which version so here are links for TC10:
Thanks rich. I'm sweating-blood to get this Intel-Atom W10 laptop to
run linux from a USBstik. It doesn't follow my older laptop's setup
to use UEFI, so I though the words:-
> ..then create a grub.cfg in /mnt/sdc2/EFI/BOOT/grub that will be shared
> by legacy bios and uefi boot
sugested a solution for the UEFI problem.
Now I'm guessing that Intel-Atom doesn't handle 64-bit. Google will tell?
So I'm focusing on the non-64 entry in GRUB.
Following your pointer, I fetched rootfs.gz, and the 1-of-4/non-64
GRUB entries flashes through the boot <trace> in half a second and
hangs, with no kybrd reaction; showing the TC header/logo &
tc@box:$
My old TC64 is versn8 and uses syslinux.
Perhaps I can add an entry to that USBstik - since I seem to have
discovered how to navigate from W10:Setting to HOW2 handle the
UEFI booting?
Oh, the 3: *64* [of 4] GRUB entries also show the TC logo with
error messages, so apparently Intel-Atom does handle 64-bit ?
Still I want a 32bit version, to access some old apps.
Rich:
Hi labeas
You might want to attach a copy of your grub.cfg file so we can see what you're doing.
labeas:
Rich suggessted that I <paste for evaluation> the grub.cfg
Assume it's created by auto/[no typos] copying from the
<2015 Dec 23 Article that you traced> and the <UUID is similarly
auto-updated>.
But Yes: lets analyse the ACTUAL text that grub gets to run;
since this is available [even for editing] before grub executes it.
The 2015 article has 3 *64* entries and 1 core.
The *64* entries give strange error-lists, like <kernel too old>.
Let's restrict our attention to the <core entry> which importantly is
the only one which halts with the CURSOR flashing - instead of frozen.
And I like the way it scrolls through the familiar TC <start INFO: in
colors against black background> in half a second.
--- I'll now [error prone] copy some of the <displayed by grub for
possible editing> from the W10 screen to the working W8.1 machine:
setparams 'core'
<blank line>
linux /boot/vlinuz quiet text tce==UUID="5c4...767"
waitusb=10:UUID="5c4...767"
initrd /boot/rootfs.gz /boot/modules.gz
---------------
The above is a waste of time, since the text is per the 2015-article.
More relevant is the <global variables to the 4 entries:
eg: "set gfxmode=1366x768x32" seems not valid, since AFAIK the
W10 device is 800X600.
I suspect these <initial global entries> may be why there's no
kybrd responce>? But they aren't editable IN GRUB.
!!!!!!!!!! OK, I've just read this now:
"Substitute your machine's native resolution for 1366x768x32
if required."
AFAIK, you can't just edit grub.cfg. It must be <installed> ??
But I'll try just editing. ---------------
OK! Editing to "800X600x32" gives a bigger font.
I suspect the <global Variable/s>: applicable to all 4 entries
cause the lack of kybrd-action ?
Navigation
[0] Message Index
[#] Next page
Go to full version