Tiny Core Linux
Tiny Core Base => Corepure64 => Topic started by: labeas on August 24, 2019, 10:03:46 AM
-
This topic is NOT specific to this Group, but the web-based forum-app
"doesn't help"!
Juanito wrote:
> Please make your wifi help request in a new post
> and tell us what hardware you have.
HOW would I get to know that? -------------
For installation of TC64 V7.2, coreplayer2 wrote:
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
No! I haven't got ethernet. We installed wifi to Ver7.2, starting
from detecting the existing hardware. After that was reported, a
whole set of <RTL firmware> was added to the ver7.2 repository.
For this newer/UEFIproblematic laptop:-
# dmesg | grep 802 == MACsec IEEE 802.1AE
# dmesg | grep ifi == nil
Please advise on steps to proceed, without ethernet.
================
I wrote the above in Ver10.0: hacked GUI & wily.
Now I'm in V7.2 which has working wifi.
BTW I seem to have succeeded in installing "core" [which is 32b
and has no GUI?] to the UEFI-problematic laptop.
So it seems a bad idea that wifi on this V7.2 needs GUI?
Also BTW, I tested the <grub2UEFIbootStik> on the older (V7.2)
laptop for TC64 booting. It starts with "<no suitable video>".
And I wasn't able to hack it to `startx`.
As expected: it is just by chance that the newer laptop gets to
startx, with Ver7.2 files. ------------------
I've noted, and will try to do:--
> 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
> Code: [Select]
> 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
------
But I need V10.0 NOT the LATEST? Moving target problem !
What's the URL of that Ver 10,0 x86_64 ISO?
-
Hi labeas
... But I need V10.0 NOT the LATEST? Moving target problem !
What's the URL of that Ver 10,0 x86_64 ISO?
http://tinycorelinux.net/10.x/x86_64/archive/10.0/
-
I've noted, and will try to do:--
> grab wifi.tcz and all it's many dependencies from the latest TC-10
perhaps "Script to download extensions+dependencies on other Linux distros" - http://forum.tinycorelinux.net/index.php/topic,23034.0.html
can be used to get 10.x wifi.tcz and dependencies from the 7.x wireless connection !?!!
-
HOW would I get to know that?
Use the "lspci" command available via the pciutils extension.
-
One should not be subject to such torture !
I couldn't remember nor find my log of how I installed my Ver7.2;
but it seems absurd to need to get the kernel & initrd off an ISO.
So I had to study <The Book ver 4> chapter 10, 11.
The problematic laptop doesn't show the Win10 disk [as sda], so.
USBstik is sda1, sda2 and I just tested it with my old Ver7.2 apps:-
cd /mnt/sda1/tczList
sudo openvt
sudo openvt
sudo openvt
sudo openvt
sudo openvt
sudo openvt
sudo openvt
sudo openvt
./InstallThese # FOR loop
sudo gpm -m /dev/psaux -t ps2
sudo ln -s /mnt/sda1/tczList/dvtm /usr/local/sbin/dvtm
echo "TEST: gpm, mc, dvtm, opera-12, wily : "
which gpm
which mc
which dvtm
which opera-12
which wily
------------ Everything looks good, especially
opera-12 has no font tearing like in Ver7.2 ------------
Then I tested the GrubUEFIstik on *THIS* laptop which has got wifi.
At boot == "no suitable video mode found".
I can't remember if the problematic latop needed `startx`, or like
this Ver7.2 it auto-startsX.
`startx` on the <V7.2 laptop> with the GrubUEFI bootStik
== "No hup: failed for waitX."
The idea was to use the wifi capable laptop to get proper V10.0 *tczS.
HOW2 test/use wifi without GUI ?
--------------
Juanito wrote:
> Please make your wifi help request in a new post
> and tell us what hardware you have.
OK: Wifi installation - new laptop.
=====.
This topic is NOT specific to this Group, but the web-based forum-app
"doesn't help"! ========
For installation of TC64 V7.2, coreplayer2 wrote:.
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
No! I haven't got ethernet. We installed wifi to Ver7.2, starting
from detecting the existing hardware. After that was reported, a
whole set of <RTL firmware> was added to the ver7.2 repository.
For this newer/UEFIproblematic laptop:-
# dmesg | grep 802 == MACsec IEEE 802.1AE
# dmesg | grep ifi == nil
Please advise on steps to proceed, without ethernet.
I know the <win10WifiDriver>.zip from google.
-
Hi labeas
One should not be subject to such torture !
I couldn't remember nor find my log of how I installed my Ver7.2;
but it seems absurd to need to get the kernel & initrd off an ISO. ...
Yes, it would be absurd if that were true, but you ask for the ISO. Here's your request and my response:
Hi labeas
... But I need V10.0 NOT the LATEST? Moving target problem !
What's the URL of that Ver 10,0 x86_64 ISO?
http://tinycorelinux.net/10.x/x86_64/archive/10.0/
If you take a look in the distribution_files directory of the above link:
http://tinycorelinux.net/10.x/x86_64/archive/10.0/distribution_files/
you will find the following:
../
corepure64.gz 09-Jun-2019 12:39 10397440
corepure64.gz.md5.txt 09-Jun-2019 12:39 48
modules64.gz 09-Jun-2019 12:37 6826959
modules64.gz.md5.txt 09-Jun-2019 12:37 47
rootfs64.gz 09-Jun-2019 12:39 3595754
rootfs64.gz.md5.txt 09-Jun-2019 12:39 46
vmlinuz64 09-Jun-2019 12:37 4721024
vmlinuz64.md5.txt 09-Jun-2019 12:37 44
Not only are the kernel and initrd there, so are the 2 files that make up the initrd.
-
OK, I see Rich's URL to v10Distribution files. But I'll post this already composed.
Offline Juanito
? How to know what wifi hardware is equiped ?
HOW would I get to know that?
Use the "lspci" command available via the pciutils extension.
-------------------
Plan: move UEFIstik to 7.2 laptop > Test: lspci
ELSE fetch/save/install lspi > Test: lspci
GetScript to fetch Ver10.0:*.tcz > fetch/save *lspi*
move UEFIstik to 10.0 laptop > Test: lspci > post results.
# lspci == lspci: not found
> AppTool > no lspci [between] lsof lsscsi.
> wget -O getOtherVer.html http://forum.tinycorelinux.net/index.php/topic,23034.0.html
> edit to extract script > Setscript for ver 10.0
# ./getOtherVer lspci ==
./getOtherVer: line 61: check: not found
http://repo.tinycorelinux.net/10.0/x86/tcz/lspci.tcz.tree not found.
> edit for correct architecture: <x86-64>
# ./getOtherVer lspci ==
http://repo.tinycorelinux.net/10.0/x86_64/tcz/lspci.tcz.tree not found.
# wget -O x86_64Tcz.html http://repo.tinycorelinux.net/10.0/x86_64/tcz/ ==
wget: server returned error: HTTP/1.1 404 Not Found
# links http://repo.tinycorelinux.net/ == ... > ...
Archive of past base releases: 1.x 2.x 3.x 4.x 5.x 6.x 7.x 8.x 9.x 10.x
... o Other Ports (x86-64, dCore, & Raspberry Pi)
# links http://repo.tinycorelinux.net/ports.html
... o Browse Pure 64 TCZs ==...lsof.tcz lsscsi.tcz ... BAD luck !!
< Core Pure 64 Latest Build == http://repo.tinycorelinux.net/10.x/x86_64/release
== Index of /10.x/x86_64/release/
------------------------------
../
distribution_files/ 20-Jan-2019 11:37 -
src/ 19-Dec-2018 12:17 -
CorePure64-10.1.iso 11-Jun-2019 09:47 15548416
CorePure64-10.1.iso.md5.txt 11-Jun-2019 09:47 54
CorePure64-10.1.iso.zsync 11-Jun-2019 09:47 53353
CorePure64-current.iso 11-Jun-2019 09:47 15548416
TinyCorePure64-10.1.iso 11-Jun-2019 09:47 27262976
TinyCorePure64-10.1.iso.md5.txt 11-Jun-2019 09:47 58
TinyCorePure64-10.1.iso.zsync 11-Jun-2019 09:47 93401
TinyCorePure64-current.iso 11-Jun-2019 09:47 27262976
-----------------
I'm guessing that lspci is a cmnd in another-named.tcz ?
# links http://tinycorelinux.net/10.x/x86_64/archive/10.0/
== looks better; will try after posting this.
-
As said:
Use the "lspci" command available via the pciutils extension
-
Hi labeas
I'm guessing that lspci is a cmnd in another-named.tcz ?
It's in pci-utlis.
> wget -O getOtherVer.html http://forum.tinycorelinux.net/index.php/topic,23034.0.html
> edit to extract script > Setscript for ver 10.0
If that means you changed the TC variable in my script to 10.0, that's wrong. There is only one extension repository for each
version of Tinycore. In your case it should be left as:
# Tinycore version
TC="10.x"
The only variable you need to change is ARCH to 64 bit like this:
# Processor architecture, current options are x86 x86_64 armv6 armv7
ARCH="x86_64"
Then run:
FetchExt.sh pci-utils
You'll find the tcz, tcz.dep, and tcz.md5.txt files for pci-utils and its dependencies in the same directory you issued the
FetchExt.sh pci-utils command.
-
I didn't manage to get V10.0 <parent of lspci> altho' the script did fetch other *.tcz
# lspci ==
00:00.0 Host bridge: Intel Corporation Device 2280 (rev 36)
00:02.0 VGA compatible controller: Intel Corporation Device 22b0 (rev 36)
00:03.0 Multimedia controller: Intel Corporation Device 22b8 (rev 36)
00:0b.0 Signal processing controller: Intel Corporation Device 22dc (rev 36)
00:14.0 USB controller: Intel Corporation Device 22b5 (rev 36)
00:1a.0 Encryption controller: Intel Corporation Device 2298 (rev 36)
00:1f.0 ISA bridge: Intel Corporation Device 229c (rev 36)
! No apparent wifi. Ver 10.0 would NOT show more ?
-
Hi labeas
I didn't manage to get V10.0 <parent of lspci> altho' the script did fetch other *.tcz ...
Are you referring to pci-utils for version 10.0? There are no .tcz files for 10.0 or 10.1, only 10.x.
-
I'm in Win10 now. And I saved this thread to C:<file>.
But as previously discussed, when I go to TC64ver10.0, I wont be able to access C:.
=======Let me paste this absurd TCforum post==========
Posts: 6730
Re: Wifi installation - new laptop.
« Reply #10 on: Today at 10:14:42 AM »
Quote
Hi labeas
Quote from: labeas on Today at 09:48:07 AM
I didn't manage to get V10.0 <parent of lspci> altho' the script did fetch other *.tcz ...
Are you referring to pci-utils for version 10.0? There are no .tcz files for 10.0 or 10.1, only 10.x.
===== end of absurd TCforum post=====
Compare this format to NNTP format.
Consider 2 opposing armies, where yours writes "twenty seven" and mine writes "27".
And BTW is it pci-utils or <pci-utils>; ie. not assured to be verbatim/pasteable correct,
but a mere concept. Both valuable but not to be UNdiscriminated.
This abused TC-betaTester is exhausted !!
Ver 7.2 lspci-binaries are unlikely to show show less than the latest version.
And the quirk may be related to the fact that the laptop lacked wifi & audio drivers,
as ADVERTISED/MARKED when I bought it.
-
=======Let me paste this absurd TCforum post==========
Posts: 6730
Re: Wifi installation - new laptop.
« Reply #10 on: Today at 10:14:42 AM »
Quote
Hi labeas
Quote from: labeas on Today at 09:48:07 AM
I didn't manage to get V10.0 <parent of lspci> altho' the script did fetch other *.tcz ...
Are you referring to pci-utils for version 10.0? There are no .tcz files for 10.0 or 10.1, only 10.x.
===== end of absurd TCforum
At this point in the game you’re expected to know the basics of a URL
You’ve been previously provided with the correct repo url so it should be obvious to any linux user how to navigate the directory hierarchy to find whatever you’re looking for without folks having to spell it out
http://repo.tinycorelinux.net/10.x/x86_64/
Is the current url for all Ver10.x corepure64 files. Note: the current collection of files are listed under 10.x there are no 10.0 or 10.1 directories at this url (except those archived)
http://repo.tinycorelinux.net/10.x/x86_64/tcz/
Adding tcz/ to the path will result in a printout of the current list of extensions
(https://uploads.tapatalk-cdn.com/20190826/97600e494dcd06eec352581a8b64b07d.jpg)
You’ll find that extension names occasionally change so it’s wise to verify yourself.
http://repo.tinycorelinux.net/10.x/x86_64/tcz/pciutils.tcz.info
Adding pciutils.tcz.info to the path will print out pciutils info file
Or
http://repo.tinycorelinux.net/10.x/x86_64/tcz/pciutils.tcz.dep
Adding pciutils.tcz.dep will list any required dependencies
How easy is that?
Sent from my iPhone using Tapatalk
-
Sorry, i've been away for a while. This project is dragging on;
altho' I've been using my ver. 7.2 *tcz/S with the ver10 <base>;
which all seem to work except for Wifi.
coreplayer2's last post is an example of what I try to encourage:
giving info whch is GENERAL/UNIVERSAL, which allows the reader to
build/expand on. Ie. give the algorithm of multiplying integers,
rather than the answer of 17x483, as if the reader was a dumb CPU.
wily which allows LITERATE programming does:-
-> wget http://repo.tinycorelinux.net/10.x/x86_64/tcz/
-> wget http://repo.tinycorelinux.net/10.x/x86_64/tcz/pciutils.tcz.info
-> wget http://repo.tinycorelinux.net/10.x/x86_64/tcz/pciutils.tcz.dep
-> Lz
-> mv index.html 10.x64tczList
-> wget http://repo.tinycorelinux.net/10.x/x86_64/tcz/pciutils.tcz
-> wget http://repo.tinycorelinux.net/10.x/x86_64/tcz/libpci.tcz
=> $ cd /tmp <install 2*.tcz> == tce-load -i pciutils.tcz & libpci.tcz
For transfering to USBstik of <APTIO 18> laptop:-
-> cp pciutils.tcz /mnt/sdd1/pciutilsInstl/
-> cp libpci.tcz /mnt/sdd1/pciutilsInstl/
-> lspci == for W8.1/<APTIO 15> == ...skip several ...
02:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8723BE PCIe Wireless Network Adapter
OMG another umount, unplug, plug, mount to show how the <APTIO 18> laptop shows no Wifi.....
-> dmesg | tail > mount /mnt/sdd1 > Lz /mnt/sdd1 == 4096 : pciutilsInstl
> ls /mnt/sdd1/pciutilsInstl == ...lspciAptio18
> cat /mnt/sdd1/pciutilsInstl/lspciAptio18 ==
00:00.0 Host bridge: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series SoC Transaction Register (rev 36)
00:02.0 VGA compatible controller: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers (rev 36)
00:03.0 Multimedia controller: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Imaging Unit (rev 36)
00:0b.0 Signal processing controller: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Power Management Controller (rev 36)
00:14.0 USB controller: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series USB xHCI Controller (rev 36)
00:1a.0 Encryption controller: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Trusted Execution Engine (rev 36)
00:1f.0 ISA bridge: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCU (rev 36)
... to be continued...
-
Goal Summary: Install wifi to newProblematicLaptop
using OldLaptop's TC64ver7.2 wilfi to fetch needed files.
# wget -/10.x/x86_64/tcz/pciutils.tcz*
fetched by LaptopTC64ver7.2 was tested on LaptopTC64ver7.2
[most packages only have minor changes between versions].
This confirmed lspci: which gave several entries, including:
"02:00.0 Network controller: Realtek Semiconductor
Co., Ltd. RTL8723BE PCIe Wireless Network Adapter".
But copying the Ver10 lspci files to <APTIO18> and testing
gave the fewer results, all listed in the previous post,
and seems to have no wifi entry.
-----------
Since the IRREGULAR running of Ver7.2 *.tczS on Ver10<core>
is expected to give unreliable results, I'll copy my well-tested
V7.2 to the <APTIO18>Problematic Laptop to REtest lspci for wifi.
---
I thought of doing a `grep <keyWord>` on the few files of the
<APTIO18>Win10 [whose Wifi works]; but TC doesn't see the Win10
partitions. TC installs to sda; so perhaps Win10 installs to RAM ?
-
This confirmed lspci: which gave several entries, including:
"02:00.0 Network controller: Realtek Semiconductor
Co., Ltd. RTL8723BE PCIe Wireless Network Adapter".
rtl8723befw.bin and rtl8723befw_36.bin are provided by the firmware-rtlwifi extension in tc-10.x
Maybe you could load this extension before the wifi extension and then check the last 10-20 lines of dmesg for useful information?
-
> Maybe you could load this extension
> before the wifi extension and then
> check the last 10-20 lines of dmesg for useful information?
----
Surprisingly 10.x:firmware-rtlwifi.tcz was 819200
whereas 7.2:* was only 360448.
I <grub2dos>booted <APTIO18> and:
$ cd *
$ tce-load -i ./firmware-rtlwifi.tcz
== ACPI: AC: found native INT33F4 PMIC, not loading <-repeat mesg
As was: `dmesg | tail -22`
NB. NO other *.tcz were loaded, as confirmed by `df` listing:
rootfs, tmpfs, /dev/sda1<-also a quirk,
/dev/loop0 ... /tmp/tcloop/firmware-rtlwifi
ALSO <nonRootPrompt> didn't return until extra Kybrd:<Enter>.
Has anyone BlueToothed from a MobilePhone to TC:laptop ?
Perhaps the <UEFI Shell> gives info re. Interrupt 33F4 ?
Who knows about installing an audio driver for TC ?
-
You have to load the firmware-rtlwifi extension and then load the wifi extension to get the required dmesg output.
Yes, you can connect a mobile phone to a tinycore machine via bluetooth - if you search these forums there are several threads on the subject.
There are many threads on the subject of setting up audio on tinycore, please search the forum.