legacy bios/uefi dual boot usb stick ?

[coreplayer2]

  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

Code: [Select]

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)

Code: [Select]

lspci -v | grep -A 8 'Network'

While you there, please show ouput of

Code: [Select]

showbootcodes

[labeas]

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.

[labeas]

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?

[labeas]

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?

[Juanito]

I just tested TinyCorePure64-10.1.iso in a qemu vm:

Code: [Select]

$ 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.

[labeas]

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.

[labeas]

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...

[Juanito]

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?

[labeas]

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.