Howto make a legacy bios/uefi dual boot usb stick with grub2

[Juanito]

There are two parts to (u)efi boot:

1 - Choose the correct bootloader - 32-bit for old apple machines and 64-bit for almost everything else

2 - Create an appropriate grub.cfg or equivalent.

It is still unclear from your posts where the problem lies with your atom machine.

[Rich]

Hi labeas

This is the first & last time I use a FULL-BROWSER for the TCforum. ...

Then use a lightweight browser like  dillo  which is capable of properly displaying this forums content.

... And now I see were the verbose/redundant:jsGenerated "Code: [Select]" comes from. ...

The purpose of the  [Select]  link is to highlight all the text in the code box so you can copy it (Ctrl-C) into the paste buffer and
then paste it (Ctrl-V) elsewhere. Good news, if you use  dillo  you'll need to highlight text in the code box with your mouse since
dillo  does not support Javascript.

... It seems absurd for TINYcore, which hasn't even got: awk, bash, X to want to ape ...

What are you talking about? awk and ash are supplied by busybox (first line after Currently defined functions:):

Code: [Select]

tc@E310:~$ busybox
BusyBox v1.29.3 (2018-12-19 15:29:37 UTC) multi-call binary.
BusyBox is copyrighted by many authors between 1998-2015.
Licensed under GPLv2. See source distribution for detailed
copyright notices.

Usage: busybox [function [arguments]...]
   or: busybox --list[-full]
   or: busybox --install [-s] [DIR]
   or: function [arguments]...

        BusyBox is a multi-call binary that combines many common Unix
        utilities into a single executable.  Most people will create a
        link to busybox for each function they wish to use and BusyBox
        will act like whatever it was invoked as.

Currently defined functions:
        [, [[, addgroup, adduser, adjtimex, ar, arp, arping, ash, awk, basename, bunzip2, bzcat, bzip2, cal, cat, chgrp, chmod,
        chown, chpasswd, chroot, chrt, chvt, cksum, clear, cmp, comm, cp, cpio, crond, cut, date, dc, dd, deallocvt, delgroup,
        deluser, depmod, df, diff, dirname, dmesg, dnsdomainname, dos2unix, du, dumpkmap, dumpleases, echo, egrep, eject, env,
        ether-wake, expr, false, fbset, fdflush, fdformat, fdisk, fgconsole, fgrep, find, flock, fold, free, freeramdisk, fsck,
        ftpget, ftpput, fuser, getopt, getty, grep, gunzip, gzip, halt, hdparm, head, hexdump, hostid, hostname, hwclock, id,
        ifconfig, inetd, init, insmod, install, ipcalc, ipcrm, ipcs, kill, killall, killall5, klogd, last, less, linux32, linux64,
        ln, loadfont, loadkmap, logger, logname, logread, losetup, ls, lsmod, lsof, lzcat, lzma, md5sum, mesg, microcom, mkdir,
        mkfifo, mknod, mkswap, mktemp, modinfo, modprobe, more, mv, nameif, nbd-client, nc, netstat, nice, nohup, nslookup, ntpd,
        od, openvt, patch, pgrep, pidof, pivot_root, pkill, poweroff, printenv, printf, ps, pstree, pwd, rdate, readlink, realpath,
        reboot, renice, reset, resize, rev, rm, rmdir, rmmod, route, rpm, rpm2cpio, script, sed, seq, setarch, setconsole,
        setkeycodes, setsid, sh, sha1sum, sleep, sort, split, start-stop-daemon, strings, stty, sulogin, sum, swapoff, swapon,
        switch_root, sync, sysctl, syslogd, tail, tar, taskset, tee, telnet, test, tftp, tftpd, time, timeout, top, touch, tr,
        true, tty, udhcpc, udhcpd, udpsvd, uname, uncompress, uniq, unix2dos, unlink, unlzma, unxz, unzip, uptime, usleep, vconfig,
        vi, watch, wc, wget, which, who, whoami, xargs, xz, xzcat, yes, zcat
tc@E310:~$
If you want GNU awk, install  gawk.tcz.  If you want bash, install  bash.tcz. If you want X, there's Xvesa (X86 only), Xorg, or Xfbdev.

[labeas]

Re: Howto make a legacy bios/uefi dual boot usb stick with grub2
« Reply #15 on: November 28, 2019, 01:55:30 AM »

Quote
There are two parts to (u)efi boot:

1 - Choose the correct bootloader - 32-bit for old apple machines and 64-bit for almost everything else

2 - Create an appropriate grub.cfg or equivalent.

It is still unclear from your posts where the problem lies with your atom machine.
-------------------------------------end of pasted quote.
As an experiment I'm using W10 to read/write this.
What a DISASTER !!
My previous post [inteded to] told that <from possibly faulty human memory rather than
copy-pasted> the Wifi-firmware needed is RTL8723BS. <--- !!!

[PDP-8]

Labeas - I can confirm these instructions work on cheapo uefi-only hardware.  I currently run on devices that are uefi-only that are made that way, OR when I have disabled all legacy stuff myself just to prove a point.

1) Wintel W8 Pro hockey puck.  UEFI only with American Megtrends bios / Aptio .  All you have to do is change your boot drive and leave the rest alone.  No legacy at all.

2) Vnopn fanless mini-pc.  Same deal, although it tries to be all things.  I turned OFF any legacy options, and run uefi-only.

3) Intel NUC.  Even turned off the old-school hybrid-iso booting hack.  UEFI only.

4) Acer laptop emulating a cheap Chromebook.  No legacy stuff there - running uefi only and just changed my boot order to boot from usb stick.

Kind of hard to keep track of all that you have done, although I'm wondering if maybe you aren't able to scroll the code Juanito supplies and might be missing the end of some lines?

I even went so far as to not even make the stick dual-boot, just basically corepure64 distribution files only.  Works great every time, on every machine.

Maybe your build environment is so twisted that something is wrong?  Have you tried using these instructions on a full-featured distribution like a live Debian Buster or equivalent which has all these tools?

Or maybe as a worst-case, resetting anything you've done to your Bios back to "default", and trying again?

Anyway, just wanted to give you hope that although for UEFI, *core isn't click-n-play, it is pretty easy and fast to create your own.  Is it time to go clean-slate and try again?

[labeas]

PDP-8 wrote:-   
> Anyway, just wanted to give you hope that although for UEFI, *core isn't
> click-n-play, it is pretty easy and fast to create your own.  Is it
> time to go clean-slate and try again?
--
My only experience with TC has been 64PureVer7.2.
I put about 8 entries in the <grub2-UEFI> QuadAtom.
TC64 & core both boot; others fail.
Core which is running now on the QuadAtom:-
$ uname -a = ...4.19.10...i686
 That's 32bit isn't it? The remaining problem is RTL8723BS driver.
$ sudo openvt (times 8: gives me 8 root Terminals).
# df | grep loop = Nul; shows that it's bare/no *.tcz installed yet.
An inconvenient quirk is that the native/Win10 disk is not seen,
so the TC-effort/bootStik is seen as /dev/sda.
It sees the sdCard, which has LinuxNativeOberon. Astounding!
Especially for anybody with PASCAL experience.
Full GUI with color...Multiple Frames per Screen, to be able to
see multiple aspects of complex problems, and even wipe/dab
texts to different colors/fonts to represent a further layer
of association. Eg. 6 Frames, showing 6 files, and RED, BLUE, GREEN,
YELLOW. marking of textS to Highlight the Price, Weight, Age,
Language aspects of the problem under consideration.
And it's running in TC:core with no X/GUI - via framebuffer.
This dating from the 90's compared to the lame-shit Win10 of today!
Yes LNO running under TCcore, now: a full GUI/OS.
nuf-sed....

[Juanito]

The remaining problem is RTL8723BS driver

rtl8723bs-4.19.10-tinycore extension posted to the tc-10.x x86 repo.

You need to download the following:

http://tinycorelinux.net/10.x/x86/tcz/rtl8723bs-4.19.10-tinycore.tcz
http://tinycorelinux.net/10.x/x86/tcz/rtl8723bs-4.19.10-tinycore.tcz.dep
http://tinycorelinux.net/10.x/x86/tcz/rtl8723bs-4.19.10-tinycore.tcz.md5.txt

You also need to download the *tcz, *tcz.dep and *tcz.md5.txt files for each extension listed in the following url:

http://tinycorelinux.net/10.x/x86/tcz/rtl8723bs-4.19.10-tinycore.tcz.tree

..and repeat recursively for each of the extension tree files.

[Rich]

Hi Juanito

... http://tinycorelinux.net/10.x/x86/tcz/rtl8723bs-4.19.10-tinycore.tcz.tree

..and repeat recursively for each of the extension tree files.

Huh? Maybe I'm misunderstanding your wording, but the  rtl8723bs-4.19.10-tinycore.tcz.tree  file already lists all of the dependencies.

[Juanito]

Ah - you’re correct - well spotted 

[labeas]

Got: http://tinycorelinux.net/10.x/x86/tcz/rtl8723bs-4.19.10-tinycore.tcz
wget http://tinycorelinux.net/10.x/x86/tcz/rtl8723bs-4.19.10-tinycore.tcz.dep
= 61bytes : rtl8723bs-4.19.10-tinycore.tcz.dep ==
wireless-KERNEL.tcz
firmware-rtlwifi.tcz
firmware-rtl_bt.tcz
wget http://tinycorelinux.net/10.x/x86/tcz/wireless-KERNEL.tcz =wget: bad address...
wget http://tinycorelinux.net/10.x/x86/tcz/firmware-rtlwifi.tcz =750240 : firmware-rtlwifi.tcz
wget http://tinycorelinux.net/10.x/x86/tcz/firmware-rtl_bt.tcz =wget: bad address 'tinycorelinux.net'
wget http://tinycorelinux.net/10.x/x86/rtl8723bs-4.19.10-tinycore.tcz.tree
 == wget: bad address 'tinycorelinux.net'
---- BTW I found the GOOD <TC wiki for wifi>.html
and would like to test/confirm the precedures,
on the minimalist: TC:core [uname -a =...686i...]
which seems to UEFI:boot without problems.
Various wiki-listed tests/confirms fail for the
TC64: rtl8723bs-4.19.10 install attempt.
Isn't there a script to fetch/install the dependencies
which haven't aleady been installed?

[Rich]

Hi labeas

... wget http://tinycorelinux.net/10.x/x86/tcz/wireless-KERNEL.tcz =wget: bad address... ...

You're supposed to replace  KERNEL  with your kernel version:
http://tinycorelinux.net/10.x/x86/tcz/wireless-4.19.10-tinycore.tcz

wget http://tinycorelinux.net/10.x/x86/tcz/firmware-rtl_bt.tcz =wget: bad address 'tinycorelinux.net'

That one's fine. I don't know why you have a problem with it.

wget http://tinycorelinux.net/10.x/x86/rtl8723bs-4.19.10-tinycore.tcz.tree
 == wget: bad address 'tinycorelinux.net'

Of course it won't work if you mangle the address:
http://tinycorelinux.net/10.x/x86/tcz/rtl8723bs-4.19.10-tinycore.tcz.tree

[labeas]

Your superior visio-cognitive skills, compensates for using inferior tools.
-rw-r--r-- 1 root root     112 Dec 10 07:45 rtl8723bs-4.19.10-tinycore.tcz.tree
-rw-r--r-- 1 root root 3284992 Dec 18  2018 wireless-4.19.10-tinycore.tcz

Further possible errorS:
wireless-4.19.10-tinycore.tcz =3284992 <- for 32bit system?.
wireless-4.19.10-tinycore64.tcz =3481600

Recent advances in USBstik technology will boost the use of tinycore.
Assuming the USA also is still dominated by <SanDisk> ?
These plasticPlugged things *WEAR* each time they're moved.
For me, Toshiba metalPlugged stiks prevent disasterous loss due
to SanDisk becoming unuseable.

[Rich]

Hi labeas

... Further possible errorS:
wireless-4.19.10-tinycore.tcz =3284992 <- for 32bit system?.
wireless-4.19.10-tinycore64.tcz =3481600 ...

Yes, the first one is for 32 bit systems and the second one is for 64 bit systems.
No, they don't have to be the same size.
If you still feel there is a "possible error" you will have to be more specific.

[labeas]

Huh? Maybe I'm misunderstanding your wording, but the
  rtl8723bs-4.19.10-tinycore.tcz.tree
  file already lists all of the dependencies.
------------------------
Writing now from lame-Win10, would the following work from *nix:-
cat <wifi.tcz> <-lists wifi.tcz & all dependencies- possibly repeated.
cat <wifi.tcz> | uniq <- removes possible repeats.
wget `cat <wifi.tcz> | uniq`
Or: <functional notation> algorithms to install wifi.sh:-
 cat wifi.tcz | uniq | <wget> | tce-load -i
That's probably what the App-GUI does?
Apparently it's difficult for full-facility-TCusers to realise
 the difficulty of installing *.tcz using Win10 ?

[labeas]

The defective:web-based:Microsoft-inspired <search> seems to indicate that I had
 not already posted the following: my actual latest <install script> which gave
the results/tests of the post-before-this-one:--

Install.sh ==
echo "the extensions need to be loaded in the following order:
1. firmware-rtl_bt"
cd /mnt/sda2/Core32/Wifi/tczS/FIRMWARE
tce-load -i firmware-rtl_bt.tcz

echo "2. firmware-rtlwifi"
tce-load -i firmware-rtlwifi.tcz

echo "3. wireless-4.19.10-tinycore
is seen to be a <LEAF> of 2 binaries;
 so will show ALREADY INSTALLED for load-wifi"
cd /mnt/sda2/Core32/Wifi/tczS
tce-load -i wireless-4.19.10-tinycore

echo "4. rtl8723bs-4.19.10-tinycore
Apparently these above 4 have no deps ?"
cd /mnt/sda2/Core32/Wifi
tce-load -i rtl8723bs-4.19.10-tinycore.tcz

echo "After loading these extensions,
 you can then load the wifi extension
 and all of its deps.
 Which number 9"
cd /mnt/sda2/Core32/Wifi/tczS
./InstallThese

echo  "and run sudo wifi.sh"
sudo wifi.sh

    [EDIT]: Removed MS slur.  Rich

[Rich]

Hi labeas
Please refrain from your  "clever"  spelling of Microsoft. If you feel a need to bash them, take it elsewhere. I'm sure there are sites
out there that specialize in that. Politics have no place here.