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

I copied vmlinuz vmlinuz64 from /mnt/sdb1/boot/; but where are:
rootfs.gz, rootfs64.gz, modules.gz, modules64.gz ?
-> find / -name "rootfs*" =nX

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 ?

[labeas]

Complex problems like this need to be trimmed. Reduce points-of-concern.
So, let's concentrate only on the <core entry> of the 4 entries.
I made a bad omission by not testing the created USBstik *ALSO* on the
older Laptop. Which DOES in fact load/run core! Since I lack experience
with core, I don't know if the installation is expected to have no
<Fbdev>. All the elementary test are OK.

  Noticeable is that the older/no-problem laptop doesn't show the
<flashy TC startup logo> like the new laptop, which hangs with
cursor blinking but accepting no kybrd-input. Does that possibly
suggest different treatment of the video parameters?

What's the syntax to <live editing in> a <wait parameter> before:
  linux /boot/vmlinuz ?

AFAIK the problematic UEFI is firmware, independent of Win8.1 or Win10.
It's just that the new (2018) "Aptio Setup Utility" has less google
documentation available than older versions.

And it's got a built-in "UEFI Built-in EFI Shell" which can list
dirs/files ...etc. But I can't think of any tests I could use it to do.

[coreplayer2]

We need to see your grub.cfg file contents exactly as written.  Unfortunately, it’s important info is obliterated with comments and is unreadable as presented.

Kindly show the untouched contents in code tags, or attach as original file.





Sent from my iPhone using Tapatalk

[coreplayer2]

AFAIK, you can't just edit grub.cfg. It must be <installed> ??

That assumption is not correct, it’s something commonly suggested to keep newbies out of trouble.
All the many grub config file I ever had have been manually created from scratch and edited as needed.

If you create a config file and place it where’s grub expects to find it then all will be well

But locations where grub expects to find it’s files is exactly your problem.  Because the flashing cursor is almost always a result of grub being unable to find it’s files.  What I’m saying here is the installation is messed up and the best solution is to wipe the installation and start over.

One quick question though, did you remember to disable “secure boot” in the bios?



Sent from my iPhone using Tapatalk

[labeas]

! OMG: I've never seen/posted-via Win10 before.

coreplayer2 wrote:
We need to see your grub.cfg file contents exactly as written. 
Unfortunately, it’s important info is obliterated with comments and is unreadable as presented.
Kindly show the untouched contents in code tags, or attach as original file.
---------- I'll try to attach. 

I've made a basic error with this project:
 I wrongly assumed that IntelAtom [dating from the old days] was 32bit.
The W10-info indicates b64.
I wanted to combine this project with installing 32bit-TC, since I have problems
running some valuable old 32b apps.
 Getting back to TC64: 
  <bios/uefi> shows [for 60 secs]:--------------------------
   the TC <logo with the static-flash>
   Text info: <efi: requested map not found; ESRT is not in the memory map;
    Can't read CTR while initialising i8042; kernel too old <-- ?!
    not syncing; Attempting to kill init! exitcode=0x00007f00
----------------
How much of the above trace-info originated from EFI or TinyCore ?

> did you remember to disable “secure boot” in the bios?

In my older Laptop I was not able to run other than <windows>
without disabling <secure boot> in the Aptio Setup Utiity
 This 2018 <Aptio> is very different. I've become confident using it:-
 Power off/on F7 Shows 4 sensible entries:
UEFI : Built-in EFI Shell
Windows Boot Manager
UEFI: Sandisk, Partition 2
Enter Setup
======== Above info for future TC victims of WinTel-monopolosts.
Sandisk is crap: plastic-sides wear away. Same price Toshiba less compact, has metal plug.
NB. Entry-3 identifies device AND PARTITION !  Also for other boot-stiks.
---------- Let's plug further [proven on older laptop] bootStik ??
== Very confusing ! Now try attach file ?

[Juanito]

At first glance your grub.cfg looks OK.

Does your tinycore usb stick boot on either of the two machines?

[coreplayer2]

! OMG: I've never seen/posted-via Win10 before.

coreplayer2 wrote:
We need to see your grub.cfg file contents exactly as written. 
Unfortunately, it’s important info is obliterated with comments and is unreadable as presented.
Kindly show the untouched contents in code tags, or attach as original file.
---------- I'll try to attach.

Thank you, I also agree doesn't appear to be anything wrong with it

> did you remember to disable “secure boot” in the bios?

In my older Laptop I was not able to run other than <windows>
without disabling <secure boot> in the Aptio Setup Utiity
 This 2018 <Aptio> is very different. I've become confident using it:-
 Power off/on F7 Shows 4 sensible entries:
UEFI : Built-in EFI Shell
Windows Boot Manager
UEFI: Sandisk, Partition 2
Enter Setup

Maybe I wasn't specific enough;  on the PC you can't boot properly from did you remember to disable “secure boot” in the bios? 

[labeas]

> Does your tinycore usb stick boot on either of the two machines?

Let's be a bit more scientific/professional in handling the 4 cases:-

 Aptio Setup Utility 2015 = Tab: Boot <-must be toggled to "Disabled"
*  TinyCore etc. Proven USBstiks = Regularly boots TC64, Ver8,9...and other linux.
*  New/Experimental BIOS/UEFI dual bootStik = "..grub/i386-pc*efi*gop.mod not found
     no suitable video mode found"
   Opens GRUB V 2.02~ menu with 4 entries per grub.cfg
   Selecting 1st-entry: "core" == "no relocation needed done..."
   `fdisk -l` =shows only 4 partition /dev/sda ;
    nor does `dmesg | grep sd` show detected extra-USBs plugged;
 I thought the <2015 laptop> had handled OK: the BIOS/UEFI dual bootStik;
 otherwise there's no reason to focus the error-diagnosis on the <2018 laptop> ?
 It CAN eg. mount /dev/sda2 /mnt/sda2 ; less /mnt/sda2/<file>
   
 Aptio Setup Utility 2018 = No <disable security> like <2015>
   Power On/Off + F7 =menu with plugged USBdevices..etc.
*  TinyCore etc. Proven USBstiks = Only goes to boot Win10
*  New/Experimental BIOS/UEFI dual bootStik = EFI-menu shows each USBstik;
   EVEN that BIOS/UEFIstik <boots from partn 2>
   Reaction for 4 grub entries as previosly described;
   Error mesgs similar to <Aptio Setup Utility 2015>;
   Action by "core"/1st entry suggests that <waiting for> kybrd is disabled.
---------------------
> did you remember to disable “secure boot” in the bios?
It's UEFI: not BIOS. <2015> simply needed disable “secure boot”.
<2018 Aptio> has a completely different format [including a complete EFI-shell !]
I didn't find reference to secure boot.
But it *DOES* try to boot from the USBstik.
Ie. does not just go to Win10, if NOT secure boot disabled, like the <2015 Aptio>.

== crg.

[coreplayer2]

> Does your tinycore usb stick boot on either of the two machines?

Let's be a bit more scientific/professional in handling the 4 cases:-

How about we make our inquiries more legible,  please?

> did you remember to disable “secure boot” in the bios?
It's UEFI: not BIOS. <2015> simply needed disable “secure boot”.
<2018 Aptio> has a completely different format [including a complete EFI-shell !]
I didn't find reference to secure boot.
But it *DOES* try to boot from the USBstik.
Ie. does not just go to Win10, if NOT secure boot disabled, like the <2015 Aptio>.

We are only interested in the 2018 notebook.

You can google "2018 Aptio bios, disable secure boot" and you'll find 3 or 4 methods to disable secure boot.   Which method is the correct one for your notebook will depend on the notebook model and/or version

Or,  please provide the the make and model # of the relevant notebook  and I'll attempt to provide the correct link with procedure to disable secure boot on your machine.   

IMO.   Microsoft developed a plan, under the disguise of providing extra security for IT departments,  which would prevent all new notebooks from booting other Operating Systems.   
While "Secure Boot" is enabled, you will never boot any other operating system (unless the kernel is signed) on this notebook, period! 

[Juanito]

*  New/Experimental BIOS/UEFI dual bootStik = "..grub/i386-pc*efi*gop.mod not found
     no suitable video mode found"

It looks like you installed 32-bit grub (i386-pc) rather than 64-bit (x86_64-efi) uefi?

[Rich]

Hi Juanito

At first glance your grub.cfg looks OK. ...

Is it OK for the  linux  line to span multiple lines? The  waitusb  parameters are on a separate line from the  tce  parameters.

labeas grub.cfg:

Code: [Select]

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 "T4Slak13Noinitrd" {
linux /boot/vmlinuz quiet text tce=UUID="edf38d93-6e84-4cf1-80c7-50131fa6ba27"
}

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
}