legacy bios/uefi dual boot usb stick ?

[Juanito]

Ah - I hadn’t noticed they were on new lines..

...no that won’t work.

[labeas]

>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.   
  == connex L1470 14 inch Laptop; & pss-on info re.<missing  audio driver/s>
>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.   
That was my opinion.I'm guessingthat you don't [yet] know about the EFI-shell?
-------
>It looks like you installed 32-bit grub (i386-pc) rather than 64-bit (x86_64-efi) uefi?
 That's quiet likely: trying to be too cleva; solving the need for a 32TC at the same
time. But the complexity with the strange machine overwhelmned me.
Was the 1st entry of grub.cfg: "core" my own addition?
Can you know from the file-sizes listed below?
-------
> Is it OK for the  linux  line to span multiple lines? The  waitusb  parameters
> are on a separate line from the  tce  parameters. 
  I also suspect so. I'll test it.
----------------
The laptop with <Aptio 2015> boots linux via USBstik, after disabling secure boot,
 and has no need for this troublesome project. It only might help debugging
 how to run any linux on the new: <Aptio 2018> laptop.
---
Consider some of the possible 8 cases: 2 x Aptio; 4 x <grub.cfg entries>.

Aptio2015: select core == Runs; but no value/improvement over existing TC !
Aptio2018: select core == seems to run, same as 2015; except at halt for keybrd
  input, with cursor-flashing: no echo/response to kybrd. As if no good kybrdDriver.
Aptio2015: select *64* ==
   BEFORE the 4 grub.cfg menu: </EFI/BOOT/grub/i386-pc/efi_gop.mod not found
   No suitable video mode found.>
   ?! INDEED: efi_gop.mod is CORRECTLY in the *64* directory; not i386* ?!
   AFTER "corepure64 base" selected == <Fatal kernel too old ;
   Kernel panic; not syncing ;attempted to kill init;
   Kernel offset: disabled; Rebooting in 60 seconds.>
===============================
Does this not simply look as if: *.mod/<grub drivers>, kernel & initrd are
not located per gub.cfg ?
----------------------------------------------
Compare FileTree with grup.cfg entries:--
menuentry "core64" {
linux /boot/vmlinuz64 quiet text tce=UUID="5c4d3b5d-47c9-4e67-8403-4aa4eb9f
b767"
waitusb=10:UUID="5c4d3b5d-47c9-4e67-8403-4aa4eb9fb767"
initrd /boot/rootfs.gz /boot/modules64.gz
}
-> blkid ==/dev/sdc1: UUID="5c4d3b5d-47c9-4e67-8403-4aa4eb9fb767"
-> ls /media/sdc1/boot/vmlinuz64 == OK  : 3807184
-> ls /media/sdc1/boot/rootfs.gz == OK  : 2803638
?? What about <nonMatchingVersions> = See listed FileSizes.

 WDYS ?

[Juanito]

>It looks like you installed 32-bit grub (i386-pc) rather than 64-bit (x86_64-efi) uefi?
 That's quiet likely: trying to be too cleva; solving the need for a 32TC at the same
time.

You’re mixing two different things here.

Almost all uefi machines require a 64 bit boot loader.

Once the 64 bit boot loader is installed you can boot both 32 and 64 bit software.

[coreplayer2]

>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.   
  == connex L1470 14 inch Laptop

I’ll research PC specific solutions to disable Secure Boot. Meanwhile you’d best read this document. 

https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/disabling-secure-boot

Because of their alliance with MS. each year the UEFI consortium of PC manufactures make it more difficult to disable secure boot   Recently they’ve hidden secure boot options behind the supervisors password.   Remaining hidden in its respective menu until a password is set.  An older solution in some cases required enabling CSM,  etc. etc..
but trust this “secure boot can always be disabled” and will always be required to boot a Linux kernel which doesn’t have a digital signature.

>It looks like you installed 32-bit grub (i386-pc) rather than 64-bit (x86_64-efi) uefi?
...
   ?! INDEED: efi_gop.mod is CORRECTLY in the *64* directory; not i386* ?!

This is a secondary issue which additionally needs to be fixed, installing from the x86_64 version is mandatory for all modern PC’s.




Sent from my iPhone using Tapatalk

[coreplayer2]

Also please for the last time, learn how to use quote & code tags like everyone else.   eg:

Code: [Select]

[quote] copied text here [/quote] 

using <> == and any other symbols is not recommended in most forums including this one, additionally makes it extremely hard to read messages and for you to get the assistance you're looking for.

[Rich]

Hi labeas
The  linux  entries in your  grub.cfg  file should not be split into 2 lines like this:

Code: [Select]

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
}
They should occupy a single line like this:

Code: [Select]

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
}

[coreplayer2]

Labeas,

In case there's some model specific procedure to resolve this issue, I send the Connex manufacturer in ZA a quick email regarding how to unveil the hidden Secure Boot feature within Aptio setup utility used on this model, as I didn't find model or BIOS version (Firmware, machine code, BIOS, setup utility, call it what ever you like) specific solution yet.

The latest Aptio Manual from American Megatrends Inc I could find is from 2012, which is not much help, other than confirm name changes of certain features.
However I came across a simple method to disable secure boot in the latest 2018 Aptio setup utility which is supposed to address yet another bios issue.

From ASUS

To allow your computer to detect foreign HDDs and SSD and recognize them as such, you need to:

    Boot your computer up and wait for it to boot into the Aptio Setup Utility.
    Once in the Aptio Setup Utility, navigate to the Security
    Expand the Secure Boot menu section and disable Secure Boot.
    Navigate to the Save & Exit tab, save your changes, exit the Aptio Setup Utility, restart your computer and wait for it to boot into the utility once again.
    Navigate to the Boot
    Disable Secure Boot and Fast Boot
    Enable CSM (Compatibility Support Module).
    Navigate to the Save & Exit tab, save your changes, exit the Aptio Setup Utility and restart your computer.

The BIOS setup utility is very often specific to each manufacturer who can configure any option as they desire.

Items to note,

• SecureBoot used to be located in Boot option menus, now it's found in "Security"
• Sometimes An admin password is required to be set and used before "SecureBoot option is visible
• SecureBoot's disable option is also available with Windows10
• This maybe outdated but in the Aptio "Save & Exit" menu there may be a "Boot Overide" option to boot directly from a legacy USB, an EFI configured USB or go directly to the UEFI shell.   Booting to either USB option may automatically disable secure boot, but the jury is still out on that... 

[/list]

When the manufacturer replies I'll post the outcome   The most sensible option is for automated disabling of secure Boot  when both an Admin password and Boot Override is used to select a USB boot device, but manufactures don't always see the logic in that.

In general, all PC's should have the ability to disable Secure Boot.   There are few exceptions like ATM's and other Kiosk style computers in which Secure Boot is of high security interest.

[coreplayer2]

One quick correction;

SecureBoot's disable option is also available with Windows10

I meant to say the UEFI options are available, but was thinking secure boot so that's what I wrote...   DOH!

[coreplayer2]

Additionally,  if these options are available in your setup

This tip may not be required or valid on the Connex notebook, however to unveil many AMI hidden bios/UEFI options during initial bootup on some PC's you can try

"Alt" and "F1" keys, or
"Shift" and "F1" keys, or
"Ctrl" and "F1" keys,

[labeas]

Project status:
 The original instructions/code dates from 2015.
 Who has got a CURRENTLY working version?
 What version/S of TC does it boot?
 What version/date of firmware/<Aptio> was confirmed?

I made a mistake in trying to combine
  "legacy bios/uefi dual boot" with installing TC32bit.
I've read that <this new stuff>/EFI is not for 32bit ?
---
It has been suggested that:
>  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/

Although I've not yet used TC64 ver10, I should try
bios/uefi-dual-boot with the files that other colaborators
have confirmed.
How do I quickly see which TC64 version I'm currently running?
-> uname -a == Linux box 4.2.9-tinycore64 #1999 SMP
           Mon Jan 18 19:59:34 UTC 2016 x86_64 GNU/Linux
---
I believe that my tests show that I can handle the <EFI/secure boot>
with my <Aptio 2018> laptop; so if I can see the URL-fetch, and
 location w.r.t. the grub.cfg [and sizes for confirmation] of files
 which are cormfirmed by other user/s, then I too could succeed.
---
We all made a booboo in not realising that the grub.cfg
SYNTAX is:
   menuentry "<title>" { <kernel Line> <initrd Line> }
---
After editing/fixing the entry: the "waitusb=10" parameter is
indeed seen to be running by <displaying the count down>.
---
I'm optimistic that my <Aptio 2018> system. will boot the 3-line-entry:
   menuentry "corepure64" {
   linux /boot/vmlinuz64 quiet text tce=<UUIDarg>/tce64 waitusb=10:<UUIDarg>
   initrd /boot/rootfs64.gz /boot/modules64.gz
   }
if I can get the same files as confirmed by other TC-user/S.
---
Meanwhile I'll start with these:
http://tinycorelinux.net/10.x/x86_64/release/distribution_files/

[coreplayer2]

Project status:
The original instructions/code dates from 2015.

Of what exactly?  Grub2? UEFI? Machine firmware/Bios? what?

Who has got a CURRENTLY working version?

Again, of what exactly?  Grub2? or grub2 in UEFI mode?

What version/S of TC does it boot?

Again, why make it so hard to assist you; what are you talking about?  Grub2?

What version/date of firmware/<Aptio> was confirmed?

Is this a clue?  are you talking about firmware/bios version in all the above?

I made a mistake in trying to combine
  "legacy bios/uefi dual boot" with installing TC32bit.
I've read that <this new stuff>/EFI is not for 32bit ?

To install Grub2 with UEFI support then you must boot tc-x x86_64 version, then install and load a "grub2-multi.tcz", then install to your device using the commands provided in the "grub2-multi.tcz" info file

Although I've not yet used TC64 ver10, I should try
bios/uefi-dual-boot with the files that other colaborators
have confirmed.

Know that there's no support for older versions after a new stable version is posted

How do I quickly see which TC64 version I'm currently running?
-> uname -a == Linux box 4.2.9-tinycore64 #1999 SMP
           Mon Jan 18 19:59:34 UTC 2016 x86_64 GNU/Linux

Code: [Select]

tc@box:~$ version
10.0
tc@box:~$ uname -r
4.19.10-tinycore64


I believe that my tests show that I can handle the <EFI/secure boot>
with my <Aptio 2018> laptop; so if I can see the URL-fetch, and
 location w.r.t. the grub.cfg [and sizes for confirmation] of files
 which are confirmed by other user/s, then I too could succeed.

That's great, but we still don't know why secure boot is disabled though I have my suspicion on that

We all made a booboo in not realising that the grub.cfg
SYNTAX is:
   menuentry "<title>" { <kernel Line> <initrd Line> }
---
After editing/fixing the entry: the "waitusb=10" parameter is
indeed seen to be running by <displaying the count down>.
---

sorry I have no idea what this means

I'm optimistic that my <Aptio 2018> system. will boot the 3-line-entry:
   menuentry "corepure64" {
   linux /boot/vmlinuz64 quiet text tce=<UUIDarg>/tce64 waitusb=10:<UUIDarg>
   initrd /boot/rootfs64.gz /boot/modules64.gz
   }

American Megatrends Bios/UEFI has nothing to do with how Grub2 parses it's own config file.
However, if the grub config - kernel command line has a carriage return anywhere in it, all info thereafter is discarded (eg: not processed)
therefore any info you want grub2 to pass to the kernel MUST be on the single kernel command line

if I can get the same files as confirmed by other TC-user/S.

I don't have a clue what files you're talking about here...

TC-10x files?  you have http://tinycorelinux.net/downloads.html  then browes the x86_64 distribution files?
maybe you're looking for the grub2 config file?   which is not provided, you have to make your own

GRUB2 config file?  This is an extract from my UEFI installed grub2 config file (/mnt/sdb1/EFI/BOOT/grub/grub.cfg) which boots TC-10 x86_64 or Windows 10  from grub2's menu

Code: [Select]

insmod part_gpt
insmod part_msdos
insmod fat
insmod ext2
loadfont unicode
insmod efi_gop
insmod efi_uga
insmod font
insmod gfxterm
set gfxmode=auto
set gfxterm_font=unicode
set gfxpayload=keep
terminal_output gfxterm

#Timeout for menu
set default=0
set timeout=5


menuentry "*** TC-10-Corepure64 (on USB)" {
search --no-floppy --fs-uuid --set=root B854-8FE0
linux /boot/vmlinuz64-41910 noswap tz=GMT loglevel=3 vga=891 waitusb=5:UUID="b313c2c4-fedf-4c44-bf42-6a6fca54b311" tce=UUID="b313c2c4-fedf-4c44-bf42-6a6fca54b311"/tc10-x86_64 opt=UUID="b313c2c4-fedf-4c44-bf42-6a6fca54b311" home=UUID="b313c2c4-fedf-4c44-bf42-6a6fca54b311"
initrd /boot/rootfs64-100.gz /boot/modules64-41910.gz
}

menuentry "Windows 10" --class windows --class os {
search --fs-uuid --no-floppy --set=root DE2F-EF34
chainloader (${root})/EFI/Microsoft/Boot/bootmgfw.efi
}
Note: there is no carriage return on the kernel command line

Also note that because of multiple tc versions I boot using this config file I have to rename kernel and support files
vmlinuz64-41910
rootfs64-100.gz
modules64-41910.gz

This should not be require if you have only one system installed

[labeas]

>>Project status:
>>The original instructions/code dates from 2015.

>>Of what exactly?  Grub2? UEFI? Machine firmware/Bios? what?

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
<HOWto make a legacy bios/uefi …..by Juanito Dec 23 2015>
Is he still alive ! His original post <wrongly> formats grub.cfg
to show the <kernel line's> arguments overflowing to a new line.

[Rich]

Hi labeas

<HOWto make a legacy bios/uefi …..by Juanito Dec 23 2015>
Is he still alive ! His original post <wrongly> formats grub.cfg
to show the <kernel line's> arguments overflowing to a new line.

Juanitos post is correct. You somehow copied it incorrectly.

[coreplayer2]

I suspect the combination of screen resolution and or browser led to word wrapping.   


In my last post there's a grub.cfg example which is taken from a working  bootable USB in either UEFI or legacy BIOS  which loads TC-10 x86_64.    The original grub.cfg I created boots many TC systems including TC9 and TC-10 x86 and x86_64 versions.  However the TC-10 x86_64 example below is tested and works on my UEFI notebook with an 2018 American Megatrends BIOS and UEFI, it's not a aptio variant though.

[coreplayer2]

Answer from Connex tech support regarding
L1470 notebook and SecureBoot

A. You cannot set the secure boot on that device

Q. are you saying that on this device “SecureBoot” is shipped “Disabled” by default?
A. Yes, It is the evaluation copy of BIOS and we are currently working on updating BIOS for this device.


So I assume from their replies that Secure boot is not an option and should not be a factor on this L1470 notebook at least until they update the BIOS



Sent from my iPhone using Tapatalk