Tiny Core Linux
Tiny Core Base => Corepure64 => Topic started by: labeas on May 16, 2019, 01:23:56 PM
-
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.
-
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/
-
> 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.
-
Hi labeas
You might want to attach a copy of your grub.cfg file so we can see what you're doing.
-
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 ?
-
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.
-
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
-
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
-
! 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 ?
-
At first glance your grub.cfg looks OK.
Does your tinycore usb stick boot on either of the two machines?
-
! 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?
-
> 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.
-
> 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!
-
* 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?
-
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:
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
}
-
Ah - I hadn’t noticed they were on new lines..
...no that won’t work.
-
>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 ?
-
>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.
-
>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
-
Also please for the last time, learn how to use quote & code tags like everyone else. eg:
[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.
-
Hi labeas
The linux entries in your grub.cfg file should not be split into 2 lines like this:
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:
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
}
-
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.
-
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!
-
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,
-
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/
-
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
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
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
-
>>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.
-
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.
-
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.
-
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
-
Probably the easiest method to find the current SecureBoot status is to boot into Windows, then from either the "Run" command or "CMD" command enter
msinfo32
look down the list for "Secure Boot State"
Likely on your machine Secure Boot State will be listed as "Unsupported" or possibly Off. either of which is good.
If it's "On" or "Enabled" then we have a huge problem..
-
Hi coreplayer2
I suspect the combination of screen resolution and or browser led to word wrapping. ...
That may be, but if you use the copy and paste functions it would come out correctly. Word wrapping does not insert
a newline character.
-
I have one machine that appears to be a corner-case like Labeas Aptio box.
I know it sounds heretical, but from a simple diagnositic standpoint, I've had to resort to the eufi version of YUMI to get TC64 to boot properly.
There's no way to properly support a 3rd party installer like this, but perhaps a "what the heck" college try using this:
https://www.pendrivelinux.com/yumi-multiboot-usb-creator/
Specifically, the YUMI-UEFI-0.0.1.6.exe
It knows about Tinycore. It would be interesting to see if burning tcpure64 with this may provide Labeas with additional clues. Make your windows10 box do something useful. :)
I'm not advocating this as the sole solution, nor is it possible to support 3rd party installers without going totally haywire in the forums, but it might serve as a band-aid until the solution is found. That's what I'm doing with my one cranky box with TC64 until I figure out where the corner-case problem is. Otherwise, all my other TC's do just fine.
-
I'm guessing that you don't [yet] know about the EFI-shell?
I tried to let this go but failed.. Again there appears to be some confusion here about the UEFI shell, which has been around for years is merely an interface much like TC's ash shell or more closely to the Grub shell, but is only for basic command line operations and manual interaction with EFI eg: loading of specific drivers and performing firmware updates etc etc., it is of little concern for the average user who will likely never need it's features. The (optional) builtin shell is often accessed via the BIOS/Firmware Boot menu which maybe listed there as "Internal EFI Shell" which you can boot too, but is of no consequence here.
It's possible that Connex left the Shell accessible for users to perform future BIOS/Firmware updates given the Beta status of the current firmware on your 2018 L1470 notebook.
The only prerequisite for a modern UEFI supported machine to boot is an EFI bootloader installed at
x:/EFI/BOOT/BOOTX64.EFI located on a readable GPT partition (typically 200MB GPT partition formatted with Fat32) and a config file which if grub is used then a config file will need to be created and installed at
x:/EFI/BOOT/grub/grub.cfg
the boot loader (BOOTX64.EFI) is normally installed with the Grub x86_64 UEFI commands found in grub-2multi.tcz.info file
sudo grub-install --target=x86_64-efi --boot-directory=/mnt/sdx1/EFI/BOOT --efi-directory=/mnt/sdx1 --removableAs per instructed here (don't forget to change the USB paths as necessary)
tinycorelinux.net/10.x/x86_64/tcz/grub2-multi.tcz.info (http://tinycorelinux.net/10.x/x86_64/tcz/grub2-multi.tcz.info)
You can install the 64bit (or 32bit) kernel, modules and rootfs on the same Fat32 partition adjust the grub.cfg path as necessary
x:/BOOT/vmlinuz64
x:/BOOT/rootfs64.gz
x:/BOOT/modules64.gz
the remainder of TC extensions can be installed on a second Linux ext2 partition behind the boot partition particularly if you want to enjoy Home Persistence and regular Linux file permissions. Remember these need to be correctly specified in the grub config file
Not too difficult right?
-
Project status:-
Boot security blocking is no problem.
.../EFI/BOOT/grub/grub.cfg first entry:
menuentry "core" {...
runs in laptop <2015 Aptio>;
and behaves the same AFAIK in laptop <2018 Aptio>,
up to the stage of prompting for kybrdInput with:
tc@box: $ <flashing cursor prompting for input>.
With the previous line-overflow problem giving
invalid synax, now fixed, it even shows the 10 second
counting-down.
---
Obviously/simplistically the kybrd-input is disabled.
---
The other 3 grub.cfg entries are complicated in that I
don't even know how to get the vmlinuz version that
matches the modules64.gz ..etc.
Let's just first fix the simplest entry.
Or did someone write that this has problems with other
that 64bit? Or was that the secure-boot, which is no
problem?
-
Project status:-
Boot security blocking is no problem.
Great
.../EFI/BOOT/grub/grub.cfg first entry:
menuentry "core" {...
runs in laptop <2015 Aptio>;
and behaves the same AFAIK in laptop <2018 Aptio>,
up to the stage of prompting for kybrdInput with:
tc@box: $ <flashing cursor prompting for input>.
With the previous line-overflow problem giving
invalid synax, now fixed, it even shows the 10 second
counting-down.
Then all is good because the first entry has the bootcode "Text" therefore will stop at the command line prompt.
like so
tc@box $:
The other 3 grub.cfg entries are complicated in that I
don't even know how to get the vmlinuz version that
matches the modules64.gz ..etc.
You mean 4 other entries?
So you couldn't find kernel, rootfs.gz and modules.gz files either from these previously supplied links?
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/ (http://tinycorelinux.net/10.x/x86/release/distribution_files/
http://tinycorelinux.net/10.x/x86_64/release/distribution_files/)
Let's just first fix the simplest entry.
You mean the 4th entry? Ok I fixed the whole grub.cfg file (tested OK on my machine)
You may need to make adjustments for the x86 entries when those files are installed.
Meanwhile I assumed you have installed all TCZ extensions from the corepure64 ISO so I added the video bootcodes to help load Xfbdev (for corepure64 video)
You might need a different VGA Bootcode as I used the one for my screen, try vga=789 or vga=788
Or read here for more options
http://tinycorelinux.net/faq.html (http://tinycorelinux.net/faq.html)
Make a backup of existing grub cfg file and use the attached grub config file, make adjustments as necessary for your system
-
I'll try to use Win10 to make [paste in] this "reply".
----
I omitted to AGAIN write:
for 1st grub.cfg entry: "core"
laptop <Aptio 2015> completes the boot process and
starts with a PROMPT and FLASHINGcursor
WAITING for the CLI keybrd-input,
which it ECHOS one key at a time,
as is the standard behaviuor of all *nix systems.
!!!! but <Aptio 2018> does NOT react to any kybrd input
after the boot process, which ends with the count-down-trace
and the CLI:Prompt with flashing-cursor.
I.e. as if the kybrd driver was disabled.
----------------
I'll search for V10 matching kernel, initrd, etc, files
for the *64* grub.cfg entries.
Meanwhile what about the <core entry> which seems much
closer to success?!!
I.e. without multiple error messages during the failed boot process.
-
labeas
Most likely you need to start over with your tinycore installations of x86 and x86_64 modules, rootfs and kernels. I say this because of all the conflicting information provided so far.
You said previously
Meanwhile I'll start with these:
http://tinycorelinux.net/10.x/x86_64/release/distribution_files/
Then in the same post declared this:
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
Which incidentally is from a much older tinycore64 kernel
So i'm saying here that things appear mixed up, especially considering the lack of keyboard control. It's imperative you maintain some consistency here in architecture and versions.
Since I've already tried and tested the 4th menu item of the provided grub config file I sugest you start with corepure64 installation.
Please use these links for TC10 files like you said you were going to do
http://tinycorelinux.net/10.x/x86_64/release/distribution_files/vmlinuz64 (http://tinycorelinux.net/10.x/x86_64/release/distribution_files/vmlinuz64)
http://tinycorelinux.net/10.x/x86_64/release/distribution_files/modules64.gz (http://tinycorelinux.net/10.x/x86_64/release/distribution_files/modules64.gz)
http://tinycorelinux.net/10.x/x86_64/release/distribution_files/rootfs64.gz (http://tinycorelinux.net/10.x/x86_64/release/distribution_files/rootfs64.gz)
- While you're there, download the latest tinycorepure64.iso
http://tinycorelinux.net/10.x/x86_64/release/TinyCorePure64-10.1.iso (http://tinycorelinux.net/10.x/x86_64/release/TinyCorePure64-10.1.iso) - delete the current contents of x(USB):/tce64 saving any custom files you may have placed in there
- and copy all the files within x(tinycorepure64.iso):/cde/* to x(USB):/tce64
- delete x(USB):/tce64/copy2fs.lst
Next use the grub.cfg file from my last post which should boot the 4th menu item; corepure64 and take you to the tinycorepure64 desktop. If not then recheck your work and we'll have to find a way of reviewing the DMESG output
I recommend performing all the above operations from Linux (ie Not windows) particularly do not open any file (like grub.cfg) in windows.
I believe I've covered all the bases off the top of my head and I hope will assure installation consistency
-
To eliminate any doubt of the Grub UEFI install process, I grabbed an old 7GB USB thumb drive and plugged it in to a PC running TinyCorePure64 (this step is important)
Given that both your notebooks have UEFI I recommend starting over creating an EFI bootable USB
This EFI only method doesn't require CSM mode within the BIOS/Firmware.
Step 2. Open APPS utility
Install extensions
dosfstools.tcz
e2fsprogs.tcz
gparted.tcz
grub2-multi.tcz
Step 3. open gparted
sudo gparted
delete old partition structure and data on old USB thumbdrive, Apply
Go to Device > Create Partition Table > Select new partition type = GPT, Apply
Create two partitions
1. 200MB (approx) partition formatted with FAT32 & name it Boot
2. new partition of remaining empty space formatted with ext2, name it ext (name it whatever)
Apply.
Step 4. Install Grub2
sudo grub-install --target=x86_64-efi --boot-directory=/mnt/sdc1/EFI/BOOT --efi-directory=/mnt/sdc1 --removable
Step 5. get UUID's for grub config
EFI Boot partition
tc@box:~$ blkid -s UUID /dev/sdc1
/dev/sdc1: UUID="964B-11FB"TCE Partition
tc@box:~$ blkid -s UUID /dev/sdc2
/dev/sdc2: UUID="d09990c6-390b-4bcc-a494-4d7e65f6ea78"
Copy attached grub.cfg file to /mnt/sdc1/EFI/BOOT/grub/grub.cfg
Edit the UUID's as necessary for your system (I provided examples)
Step 6. Download, mount tinycorepure64.iso and copy files
http://tinycorelinux.net/10.x/x86_64/release/TinyCorePure64-10.1.iso (http://tinycorelinux.net/10.x/x86_64/release/TinyCorePure64-10.1.iso)
navigate to your downloads directory
sudo mkdir /mnt/iso
sudo mount -o loop TinyCorePure64-10.1.iso /mnt/iso
Copy TCE directory from mounted ISO
sudo cp -R /mnt/iso/cde /mnt/sdc2/tc10-x86_64
Create Linux directory
sudo mkdir -p /mnt/sdc1/Linux
Copy corepure64.gz and vmlinuz64 to /mnt/sdc1/Linux
sudo cp /mnt/iso/boot/corepure64.gz /mnt/sdc1/Linux/corepure64.gz
sudo cp /mnt/iso/boot/vmlinuz64 /mnt/sdc1/Linux/vmlinuz64
It took way longer to document that process than the 10 minutes to actually create boot and test the USB
Note: remember to adjust the (mnt/sd?1/2) path as needed in all commands
-
Sorry, I forget to add one thing
After copying CDE contents to the new USB/tc10-x86_64 location don't forget to delete copy2fs.lst file that was copied from the ISO
sudo cp -R /mnt/iso/cde /mnt/sdc2/tc10-x86_64
sudo rm /mnt/sdc2/tc10-x86_64/copy2fs.lst
-
Labeas, com’n get with the program here and give us the outcome of starting from scratch with a pure EFI bootable USB stick??
Takes 10 ok maybe 15 minutes to make..
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.
...
Problem 2 is to get this <HOWto dual boot> working.
...
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.
I’ve read this first post many time to see where the confusion is.. I suspect you’re going about this all wrong.
First, you have two machines which run EFI firmware so why attempt to make a legacy BIOS bootable USB in the first place when EFI USB would work fine on both machines?
I believe that either this new laptop manufacturer didn’t provide a Compatibility Mode option for you to boot a legacy USB stick or you didn’t enable CSM in the BIOS/Firmware
You can check for CSM and enable it but I doubt you’ll find it since it’s a beta BIIS and Connex didn’t provide SecureBoot either.
On an EFI PC
1. To boot an unsigned OS, Secure boot must be disabled. It appears that SecureBoot is disabled so that’s step 1 accomplished.
2. Also if you created a Legacy MBR USB and trying to boot it on an EFI machine then depending on the firmware implementation you may need to enable CSM (as it does on my EFI test notebook). At least that’s the only workaround I’m aware of to boot a Legacy MBR Partition Table on an EFI Machine if the firmware doesn’t specifically support that (and few pc’s do from the 2017-2018 era)
When I attempt to boot an MBR partitioned USB stick without CSM enabled, the boot process hangs somewhere between the kernel and a graphic desktop loading. does that sound familiar?
Frankly we don’t know the history or even the current Status of your installation or USB. Therefore in the event you’ve created a Legacy MBR Compatible USB and there’s no support for that scenario in your new notebook’s firmware start afresh with a pure EFI USB Stick with GPT and FAT32 (fat32 for the boot loader and kernel partition) as described in my last couple of posts..
If your old notebook’s EFI BIIS/firmware supports CSM then disable it to boot either machine with your new UEFI only USB Stick
Good luck
Sent from my iPhone using Tapatalk
-
I temporarily lost my Wifi access AFTER I got <grub2EFI> working.
What helped was trimming of the cosmetic-fluff from the grub.cfg entry,
which allowed the vital error mesg: <KERNEL TOO OLD> to be read,
instead of flashing-past. ….. I'll post details tomorrow.
-
2019-June-20 I'm writing this from Win10. Reportedly some posts are <pending>?
Compared to proper protocols eg. NNTP, this web-based forum, like gmail,
is problematic.
I still must read/follow the June 13 post; only now seen.
---
Removing the <cosmetic parameters> from grub-entries allowed me to read
<Kernel too old> and focus on MY ERROR of commenting out the <wget kernel10>
from the script which wgot the other V10-files.
Probably I wanted to avoid the additional problems of upgrading;
from the main concern of how to handle the secure-boot-lock.
---
Current status of <Aptio 2018> Laptop:
Power off / on & F7 = list of Bootable USBstiks & partitions.
Select <the one> Partn 2 = GRUB selection menu.
I don't now remember the details of my newly added grub.cfg entry.
In nonroot VT do 7 times: sudo openvt
Can do: fdisk, df, mount, …..
Locate my dir on old TC64-stik which installs my Ver7 & 8 apps.
=> mc & gpm are alive
=> startx runs except no <bottom bar App list>
=> opera-12 <better rendering than old laptop> !!
----
Can I hope to activate the 4 wifi *.tcz by following my logs,
from Ver7 & 8 days?
-
=> startx runs except no <bottom bar App list>
That probably means that you did not load the wbar extension or, if you did, then one of the deps is missing.
Can I hope to activate the 4 wifi *.tcz by following my logs, from Ver7 & 8 days?
Nothing changed with wifi since then, so it should work - you may need to update your wifi firmware extension if you use one.
-
Hi labeas
This forum is a place for communicating questions, answers, and ideas. You come here seeking assistance and proceed to
make your posts difficult to follow by cluttering them with irrelevant information, unrelated opinions, and syntax like => and <>,
which makes it difficult to follow what you are trying to say, i.e the communicating part I mentioned earlier.
2019-June-20 I'm writing this from Win10.
Irrelevant. You can post to this forum using any Operating System you wish.
Reportedly some posts are <pending>?
I have no idea what you mean by that.
Compared to proper protocols eg. NNTP, this web-based forum, like gmail, is problematic.
Unrelated opinion. To the best of my knowledge, you are the only one here who finds this "web-based" forum problematic
Nobody cares what you think of Gmail since it's unrelated to this threads topic. More clutter on your part.
I still must read/follow the June 13 post; only now seen.
You should probably read all replies in a thread prior to posting again. They might address some issue you are about to post about.
You have a 64 bit machine so I know it's up to the task of running an HTML capable browser. Install a proper browser and then:
1. Learn how to wrap terminal commands and responses in Code Tags (see below).
2. Learn the proper use of Quote Tags so others can find where the quote came from (see below).
3. When referring to another thread, provide a link to that thread (see http://forum.tinycorelinux.net/index.php/topic,22848.msg142805.html#msg142805)
4. Understand that the individuals trying to help you do not work for you. They are volunteers giving up their own time. Yet for
some reason you seem to feel this forum and its members need to learn to conform to your way of thinking and doing things.
That type of self centered behavior likely discourages some individuals from responding to your requests for help.
Please use Code Tags when posting commands and responses seen in a terminal. To use Code Tags click on the # icon
above the reply box and paste your text between the Code Tags
Code Tags serve as visual markers between what you are trying to say and the information you are posting. They also preserve
spacing so column aligned data displays properly.
-
Coreplayer 2 wrote:-
> To eliminate any doubt of the Grub UEFI install process, I grabbed
> an old 7GB USB thumb drive and plugged it in to a PC running
> TinyCorePure64 (this step is important)
> Given that both your notebooks have UEFI I recommend starting over
> creating an EFI bootable USB.
> This EFI only method doesn't require CSM mode within the BIOS/Firmware..
I'll exercise this later and report my results.
Right now I need Wifi capability for the now TC64 <Aptio 2018>.
Apparently my recent attempted post/query failed:
How to install Wifi to the <Aptio 2018> laptop,
which does run Wifi under W10, but only shows an empty Xterm,
for some seconds, when the <bar's> WifiIcon is activated.
PS. opera-12 has a nicer rendering than the <Aptio 2015> laptop.
-
Please make your wifi help request in a new post and tell us what hardware you have.
-
> Please make your wifi help request in a new post and tell us what hardware you have.
OK thanks, I'll dig-out my logs from the Vers 7 Wifi installation.
===> Previously composed:--
Do I remember correctly that TC assumes the user has a fixed-line
inet-connection?
My TC64 vers 7?8 boot straight into <Xfdev>. but this:
$ uname -r = 4.19.10-tinycore64 ; $ version = 10.0
starts in CLI mode.
Because I need mc to keep its setting from the previous session,
and TC has no way of knowing WHERE these setting are kept, I've
got my own install/setup procedure.
I've got a dir of *.tcz and a script: ./InstallThese.
Plus a script for installing my apps which are independent of TC.
Now I need to replace all Vers7?8 *.tcz with Vers10.
Amazingly, [most of] the old ones seem to run OK under Ver10.0.
So I need Wifi facilities, that match my firmware.
The <Aptio 2018> laptop which runs Wifi for Win10, gives some info for:
dmesg | grep ireless ; dmesg | grep 802
-
I've got my own install/setup procedure.
I've got a dir of *.tcz and a script: ./InstallThese.
Plus a script for installing my apps which are independent of TC.
Now I need to replace all Vers7?8 *.tcz with Vers10.
Amazingly, [most of] the old ones seem to run OK under Ver10.0.
So I need Wifi facilities, that match my firmware.
The <Aptio 2018> laptop which runs Wifi for Win10, gives some info for:
dmesg | grep ireless ; dmesg | grep 802
All the above is of no consequence.
You'll need to run tce-install -wi wifi from the command line while connected via ethernet to correctly install the kernel compatible driver and other deps for TC-10 x86_64 and your latest notebook
tce-install -wi wifiOr grab wifi.tcz and all it's many dependencies from the latest TC-10 x86_64 ISO and install them using tce-install -i wifi
tce-install -i wifi
Then run dmesg | grep wifi to determine which firmware if any you need to install
then install the required firmware
Be sure to install wifi.tcz and firmware-xxxxx.tcz to your onboot.lst
-
... Because I need mc to keep its setting from the previous session,
and TC has no way of knowing WHERE these setting are kept, I've
got my own install/setup procedure. ...
Nonsense. MC keeps its settings in ~/.config/mc/. If you have a persistent /home , settings are remembered because it is
persistent. If you have a non-persistent home , settings are remembered because it should be included in your backup.
-
Re. can TC restore </root saved setups> ?
Rich wrote:-
> Nonsense. MC keeps its settings in ~/.config/mc/.
> If you have a persistent /home , settings are remembered because it is
> persistent. If you have a non-persistent home , settings are remembered
> because it should be included in your backup.
-------
The verbatum extract from /media/sdb1/Setup4gs is:-
sleep 5
sudo rm -r /root/.config/mc
sudo cp -rf /home/tc/.config/mc/ /root/.config/mc# home was OK but not root ?
--------------------------------------------------
I'm guessing the problem is that I'm naughty:
normally run as root.
Non-root is for the office-girls/FB-twitter-kiddies,
where they have [expensive to create] cartoons of PaperFolders
to represent Directories....
PS. you can handle "2 + 3 = 5" notation ?
Standard english prose does not suffice for techno-communication.
[EDIT] Added code tags. Rich
-
Hi labeas
Re. can TC restore </root saved setups> ? ...
To the best of my knowledge, TC does not discriminate against /root or any other directory. Open your /opt/.filetool.lst file
and add a line that says:
rootThen remove this stuff:
sleep 5
sudo rm -r /root/.config/mc
sudo cp -rf /home/tc/.config/mc/ /root/.config/mcNow run a backup and you should be set.
-
I've saved and hope to execute your instruction sequence within the
context of installing TCver10 PROPERLY.
>...TC does not discriminate against /root or any other directory.
That's why I didn't use the intended/proper way to install/run V7&8.
When I want to intall/use LinuxNativeOberon etc which TC knows nothing
about: I need to create my own/new Dirs. ..
Honestly, I don't remember the details of the PROPER way to
install/restore. Eg, I don't use the <ExitPanel>.
Here's the new log for:
launch TC > comment out 3lines:setup mc > Exit:Shutdown;Backup;sdb1
> relaunch > Xterm:mc=NotFound > Run NewSetup which installs mc.tcz
> mc : nonRoot is setup; mc:Root is not!
--------------------------
My attempt to install V10 on a new USBstik, needs fetching all the
V10:*.tcz, possibly via Win10:Wifi; and exiting properly via the
<ExitPanel> appropriately set.
?!? But I can only see the <ExitPanel> because I have
INSTALLED MY OLD LIST OF *V7?8:*.tcz ?!
It's painfull to search/re-read the instructions after you're
used the thing for hundreds of hours.
-
Hi labeas
... Here's the new log for:
launch TC > comment out 3lines:setup mc > Exit:Shutdown;Backup;sdb1
> relaunch > Xterm:mc=NotFound > Run NewSetup which installs mc.tcz
> mc : nonRoot is setup; mc:Root is not! ...
You did not follow the instructions. Read my last post again. The first thing I told you to do was:
... Open your /opt/.filetool.lst file and add a line that says:
root
-
> did you <mark Dir:root as needing to be saved?>
I can't remember, but it's the PRINCIPLE that matters:
TC can't know where random apps save their setup-data.
More confusing for this thread which is about UEFI-installation - not mc:
I can't find my notes/logs of how2 extract *.tcz from *.iso
-
> did you <mark Dir:root as needing to be saved?>
I can't remember, but it's the PRINCIPLE that matters:
TC can't know where random apps save their setup-data.
More confusing for this thread which is about UEFI-installation - not mc:
I can't find my notes<<<I use OneNote<<</logs of how2 extract *.tcz from *.iso
-
Hi labeas
... TC can't know where random apps save their setup-data. ...
Nor should it. It's your responsibility to add whatever needs to be saved to your backup.
... More confusing for this thread which is about UEFI-installation - not mc: ...
Then you should have brought it up in a separate thread and not this one.
-
...
More confusing for this thread which is about UEFI-installation - not mc:
I can't find my notes/logs of how2 extract *.tcz from *.iso
Please, what is it under "Step 6" of this post you don't understand?
http://forum.tinycorelinux.net/index.php/topic,22848.msg143377.html#msg143377
-
Sorry, I've been away solving other problems.
on: June 05, 2019, Juanito wrote:-
>> * 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?
My code & files are based on the 2015 Dec. article, which
AFAIK was for TC64. But YES ! I was focussing on the M$:UEFI:lockout
problem, and ALSO wanted to install TC32, as well as the latest TC64.
Perhaps because the M$:UEFI:lockout problem applies equally to TC64
& TC32, it never occured to me that I couldn't boot both 64 & 32
from the same GRUB. Didn't more experienced TC users, see that of
the several <grub.cfg entries> the 32bit one had it's files in a
different dir ?
So TC64 boots & runs OK, but I need to install Wifi.
First trace the firmware via: dmesg | grep <keyWord>
.... and installing TC32 needs a different grub ?
Where is THAT grub ?
-
...
it never occurred to me that I couldn't boot both 64 & 32
from the same GRUB.
...
and installing TC32 needs a different grub ?
Where is THAT grub ?
OK labeas, Heads up!
Yes you can boot both TC-10-x86 and TC-10-x86_64 from Grub2 (but you must install the 64bit version of grub2)
Please don't use TC10-x86 (32bit) version of grub2, it only for old 32bit EFI firmware, specifically early and limited manufactured Apple MacBook 32bit EFI firmware. I am not aware of any other Intel based hardware that ever used a 32bit EFI. A PC which has a 32bit EFI firmware requiring a 32bit EFI grub2 is an extremely rare species and I doubt very much if you have one of these. So Please don't use the grub2 32bit version on any modern 64bit hardware.
From Grub2 "64 bit version installed from corepure64"
you may run any and all these TC versions
TC-10-x86 (tinycore 32bit)
TC-10-x86_64 (core64)
TC-10-x86_64 (corepure64)
Didn't more experienced TC users, see that of
the several <grub.cfg entries> the 32bit one had it's files in a
different dir
The only way to boot either 32bit or 64bit TC versions is for each version to have a dedicated TCE directory, I noticed but that is the correct way to accomplish multi boot scenario.
In fact I run the last three 8,9 & 10 TC versions each with "tinycore 32bit", "Core64" & "Corepure64" editions from my current USB Stick(s) using grub2 (64bit)
Each version and each architecture runs from a dedicated tce directory.
-
So TC64 boots & runs OK, but I need to install Wifi.
First trace the firmware via: dmesg | grep <keyWord>
Are you asking what word to grep for?
Please show output of this instead
dmesg | tail -10
We're looking for the name of the firmware file the wireless driver is failing to load
You may have shown this before but I couldn't find it easily so, please show output of
(you may need to load pciutils.tcz first, but then)
lspci -v | grep -A 8 'Network'
While you there, please show ouput of
showbootcodes
-
This is not a REPLY. Like all "web-based" apps this is crap!
2019 Aug 24. I'm writing this from the problematic:WinTelLockoutUEFI
laptop, which has been running for several days..
AFAIR I got core booted OK [which is 32 bit with no GUI ?] and this
is TC64, which I hacked [possibly using some of my *.tcz of Ver7.2].
It still needs to be cleaned up to proper V10.0
opera-12 is better than on Vers7.2, without the font-tearing.
BTW I didn't D/L ver10's opera-12.
# version == 10.0
# uname -a == Linux box 4.19.10-tinycore64 #1999 SMP \
Tue Dec 18 15:18:54 UTC 2018 x86_64 GNU/Linux
Until I get wifi working here, I must manually transfer <wgotS>
from the TC7.2 laptop.
A major problem is that TC's *CORE ASSUMPTION*: that we all have
ethernet, is not valid.
Juanito wrote:
> Please make your wifi help request in a new post
> and tell us what hardware you have.
OK: Wifi installation - new laptop.
-
Based on coreplayer2's post of June 12, 2019, I'll try creating a new
<set of files> to boot the Old wifi-capable Laptop using EFI & Ver10.
> Step 2. Open APPS utility
> Install extensions
> dosfstools.tcz
...
?! This all assumes a working inet-connection and a *Ver10 system*
where the APPS utility fetches Ver10 files ?! Or am I missing something?
Yes, I know about the script to fetch <other version *.tcz>.
What's it called again?
-
I'm continuing from this old thread in my attempt to
limit-the-number-of-variables: hardware, booter, TCversion,
to eventually have wifi on the laptop which needs UEFIbooting.
coreplayer2 wrote:--
>Given that both your notebooks have UEFI I recommend
> starting over creating an EFI bootable USB.
I followed your steps and expected to get at least a GUI
like I get with syslinux and TC64 Ver7.2.
Of course I couldn't test the known-good <rtl-wifi> under the
new <grub2-multi> because I didn't even get a GUI with copy-paste
facilities. If the iso doesn't give these basic apps, I'm wondering
how I installed the original Ver7.2.
What's about that script that installs ver:N apps from Ver:N-M ?
Of course I get GUI ..etc with the laptop that can't do wifi; but
that's from hacking the Ver7.2 *.tcz/s into the Ver10 base, which
may be one reason why I can't get it's wifi working.
If 26624K:
http://tinycorelinux.net/10.x/x86_64/release/TinyCorePure64-10.1.iso
hasn't got the GUI; how is the wifi installed, when the wifi needs
the GUI?
-
I just tested TinyCorePure64-10.1.iso in a qemu vm:
$ sudo modprobe kvm-intel
$ qemu-img create -f qcow2 vdisk.img 2G
Formatting 'vdisk.img', fmt=qcow2 size=2147483648 cluster_size=65536 lazy_refcounts=off refcount_bits=16
$ qemu-system-x86_64 -enable-kvm -hda vdisk.img -m 2G -cdrom /tmp/TinyCorePure64-10.1.iso -boot d..it boots directly to a gui without problems.
Since the TinyCorePure64-10.1.iso used Xfbdev, it should work well with your uefi laptops.
The wifi extension does not need a gui - the wifi.sh script will run from a console prompt.
Please post your bootloader config file.
-
Both laptops are occupied with other projects.
I vaguely remember some test reporting <can't find display mode>.
The aim is to confirm the <Ver7.2laptop's> wifi with Ver10:<dos2Booter>.
So I'll try the wifi.sh script.
-
I found the paper-written-error-log:"No suitable video mode found".
Which is probably why <GUI> was not started?
Since I don't want to be distracted away from the wifi problem,
and I need a 32bit installation for my own accumulated binaries,
if I must involve wifi.sh,
I'll try to get wifi working on the problematic Laptop via <core32>.
---
Here's the grub entry which starts core32 -I use the 2nd one to see
more error-traces. Can you see <initialisation re.video mode-error>?
----- extract of grub entries ---------
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" {
linux /boot/vmlinuz waitusb=10:UUID="bfe6116c-473a-4ee9-bbac-3638039dc9ad"
initrd /boot/rootfs.gz /boot/modules.gz
}
menuentry "core64" {
------------------- end of extract of grub entries -----------
Remind me again of the URLs to <wget the required tczTrees via the wifi-able
laptop.> to test wifi.sh : <core32>:Ver10 ?
---
"core" seems to boot ok:-
$ df =.../mnt/sda1 <- it doesn't see the Win10 nativeDisk?
$ uname -a =...4.19.10...i686...
-
The only significant difference I see with my grub.cfg us that you have "insmod efi_gop" and I have "insmod all_video", because I use the same config for uefi and legacy bios boot.
Since you get a video mode error, are you sure "800x600x32" is the native resolution of your screen?
The tree file is at: http://tinycorelinux.net/10.x/x86/tcz/wifi.tcz.tree
Wouldn't the native win10 disk be /mnt/sda3?
-
Juanito wrote:-
> Since you get a video mode error, are you sure "800x600x32"
> is the native resolution of your screen?
OK, I expect that will fix the <Ver7.2 laptop> when its free to test.
And testing with native resolution on the newer problematic laptop
gives font too small. I guess any one of several VALID resolutions
can be chosen.
---
> The tree file is at: http://tinycorelinux.net/10.x/x86/tcz/wifi.tcz.tree
With much pain I traced the trees and Win10Got the 11.tcz for mc & gpm to
make the installation usable. I use: InstallThese.sh ==
for F in `ls ./*.tcz` ; do tce-load -i $F ; done
An unpleasant task: that's why I never updated from V7.2.
Must I suffer the same punishment to install the wifi for V10:core
:no GUI ? And where the 'HOW2' and about critical installation sequence.