Tiny Core Linux 32-bit wifi configuring
Posted: Sun 29 Apr 2018, 01:51
For dCoreDog see: http://www.murga-linux.com/puppy/viewtopic.php?p=949292
UPDATED 28March2019:
Tiny Core Linux
Latest 32-bit tinycorelinux version 10.x (18MB download). Probably just need to change 10.x to latest XX.x when newer version comes out...
After installation, neither ethernet nor wifi found to be working on my
HP Elitebook 2530p laptop which needs wifi iwlwifi firmware (and more) for wifi to work.
Installation steps used to get working (including wifi but I didn't bother about ethernet since don't have an ethernet cable connection - if I did, would need firmware driver: not sure which but maybe firmware-intel_e100.tcz for my machine):
EDIT below: Personally I'm now using 64bit version instead since I prefer that owing to needed by some programs I use - instruction differences for 64-bits TC are included below.
Downloaded 32-bit Tiny Core (around 18MB) using my internet-connected XenialDog64 system, from:
http://tinycorelinux.net/10.x/x86/relea ... urrent.iso
1. Frugal installed it (including grub4dos menu.lst) onto my hd partition /mnt/sda5 as follows:
2. mkdir -p /mnt/sda5/tinycore32/
3. Clicked on the tinycore iso and that opened it up in filemanager in XenialDog64.
Copied the iso's /boot and /cde directories into /mnt/sda5/tinycore32/
4. Renamed cde to tce.
5. Whilst still on internet in XenialDog64, went to tinycorelinux v10.x repository page:
http://distro.ibiblio.org/tinycorelinux/10.x/x86/tcz/
or if building 64bit tinycorelinux:
http://distro.ibiblio.org/tinycorelinux ... 86_64/tcz/
From there, downloaded the following tcz extensions needed to get wifi on my system.
For each of the following, I ALSO downloaded the associated xxx.md5.txt files and,
as shown, any that also had a xxx.dep file,
and stored everything in /mnt/sda5/tinycore32/tce/optional/:
firmware-iwlwifi.tcz
libiw.tcz
libnl.tcz
ncursesw.tcz (note the w at end of ncursesw)
openssl-<version>.tcz
readline.tcz AND readline.tcz.dep
wifi.tcz AND wifi.tcz.dep
wireless-<kernel_version>-tinycore.tcz
wireless-tools.tcz AND wireless-tools.tcz.dep
wpa_supplicant.tcz AND wpa_supplicant.tcz.dep
[EDIT: for tinycorelinux 64-bit version, you need to use:
wpa_supplicant-dbus.tcz AND wpa_supplicant-dbus.tcz.deb,
which depends on,
dbus.tcz, which depends on expat2.tcz, so download all these too should you instead be installing 64-bit tiny core linux
Seems you might now (tinycore10.x) also need: elogind.tcz, acl.tcz, and attr.tcz
end:EDIT]
Note that you only need to include wifi.tcz and firmware-iwlwifi.tcz in optional/onboot.lst so they automatically get loaded at next boot. Dependencies of packages are always found and loaded automatically by the tinycore system at boot time.
6. For my grub4dos menu.lst I used:
If booting from a usb stick you'll need additional waitusb=5 at end of the menu.lst kernel line.
7. After booting, I loaded the needed wireless tcz files and, from opened terminal used
wifi.sh to connect using following commands:
followed by:
That's it.
or whatever now works from a terminal etc...
At this stage you can download/install, using tc's GUI "Apps" browser program, whatever apps tinycorelinux has in its repo.
----
If your machine doesn't use firmware iwlwifi then you need to find and substitute the firmware-<your_wifi_firmware>.tcz etc for your system.
Much the same as above is required, on my iwlwifi machine at least,
for a tinycorelinux 64-bit version install, but grub4dos menu.lst very different cos 32-bit tiny core by default uses Xvesa whereas 64-bit uses X framebuffer (though you can later install Xorg in either version); so my menu.lst for the 64-bit tinycorelinux using framebuffer is as follows:
This basic system is super small and VERY fast but even for a minimal system you'll want to use the applications manager to load up a filemanager. I recommend the very simple tinycore "fluff" filemanager. Of course, you'll want to load a browser, for general use, which will swell the size very significantly... However, I've currently just cloud-loaded fast/tiny dillo browser for typing this post.
All-in-all, tinycorelinux is a great little swiss-army-knife of a system - and nice just using ondemand loading cloud-stored apps for whatever you want to do whenever... though it's also easy enough to store the apps permanently/with-persistence and for immediate availability on boot. You'll also want to get used to using sudo for root-access permissions to directories outside of tc home (though fluff includes sudo inbuilt capability for when you need it). The default-provided FLWM desktop window manager is also super tiny and flexible (though you can change to JWM or openbox, for example, if you wish) - just right-click on its background for Application management and lots of other stuff...
EDIT: Note that, by default, tinycore can read files from ntfs filesystems too, but if you want to ability to also write to ntfs you need to download/install ntfs-3g.tcz.
EDIT2: I've also tested current slitaz-rolling release. A very easy frugal install for that one and beautiful to use and look at. Find my report/howto below link:
http://www.murga-linux.com/puppy/viewto ... 157#990157
Slitaz is best of breed for me.
wiak
EDIT_28Mar2019: Posting from latest 64bit Tiny Core Linux version 10.x right now. I used 'Apps' browser program to first search for fastest mirror, and then used Apps -> Cloud (Remote) ->Browse to fetch (OnBoot selected): firefox-Getlatest.tcz (followed by running the resultant installed shell script firefox-Getlatest.sh from terminal). So using Firefox Quantum 66.0.2. Normally, I'd actually use a separate firefox simply downloaded from Mozilla and uncompressed in its own folder for sharing between my distributions, but this was just a test install on TC. With this latest firefox installed, TC installation is taking up 144 MiB on disk. EDIT: I noticed wayland.tcz installed with firefox but that seems to just handle some 'wayland protocol' so I guess still just Xvesa framebuffer being used. Of course, default Xvesa framebuffer 64bit TC install, without firefox, is very small indeed: just 22 MiB disk space! Now installing bash, core-utils, mtpaint, geany, and mpv (since has Xorg as dependency - this will all swell the install size): Now 206 MiB, so approaching Puppy size as expected... However, best is, I feel, to use the tiny 22MB default install (albeit maybe inflated with Xorg) and load the likes of firefox ondemand only or better still as portable external apps (usable also by other distros installed).
UPDATED 28March2019:
Tiny Core Linux
Latest 32-bit tinycorelinux version 10.x (18MB download). Probably just need to change 10.x to latest XX.x when newer version comes out...
After installation, neither ethernet nor wifi found to be working on my
HP Elitebook 2530p laptop which needs wifi iwlwifi firmware (and more) for wifi to work.
Installation steps used to get working (including wifi but I didn't bother about ethernet since don't have an ethernet cable connection - if I did, would need firmware driver: not sure which but maybe firmware-intel_e100.tcz for my machine):
EDIT below: Personally I'm now using 64bit version instead since I prefer that owing to needed by some programs I use - instruction differences for 64-bits TC are included below.
Downloaded 32-bit Tiny Core (around 18MB) using my internet-connected XenialDog64 system, from:
http://tinycorelinux.net/10.x/x86/relea ... urrent.iso
1. Frugal installed it (including grub4dos menu.lst) onto my hd partition /mnt/sda5 as follows:
2. mkdir -p /mnt/sda5/tinycore32/
3. Clicked on the tinycore iso and that opened it up in filemanager in XenialDog64.
Copied the iso's /boot and /cde directories into /mnt/sda5/tinycore32/
4. Renamed cde to tce.
5. Whilst still on internet in XenialDog64, went to tinycorelinux v10.x repository page:
http://distro.ibiblio.org/tinycorelinux/10.x/x86/tcz/
or if building 64bit tinycorelinux:
http://distro.ibiblio.org/tinycorelinux ... 86_64/tcz/
From there, downloaded the following tcz extensions needed to get wifi on my system.
For each of the following, I ALSO downloaded the associated xxx.md5.txt files and,
as shown, any that also had a xxx.dep file,
and stored everything in /mnt/sda5/tinycore32/tce/optional/:
firmware-iwlwifi.tcz
libiw.tcz
libnl.tcz
ncursesw.tcz (note the w at end of ncursesw)
openssl-<version>.tcz
readline.tcz AND readline.tcz.dep
wifi.tcz AND wifi.tcz.dep
wireless-<kernel_version>-tinycore.tcz
wireless-tools.tcz AND wireless-tools.tcz.dep
wpa_supplicant.tcz AND wpa_supplicant.tcz.dep
[EDIT: for tinycorelinux 64-bit version, you need to use:
wpa_supplicant-dbus.tcz AND wpa_supplicant-dbus.tcz.deb,
which depends on,
dbus.tcz, which depends on expat2.tcz, so download all these too should you instead be installing 64-bit tiny core linux
Seems you might now (tinycore10.x) also need: elogind.tcz, acl.tcz, and attr.tcz
end:EDIT]
Note that you only need to include wifi.tcz and firmware-iwlwifi.tcz in optional/onboot.lst so they automatically get loaded at next boot. Dependencies of packages are always found and loaded automatically by the tinycore system at boot time.
6. For my grub4dos menu.lst I used:
Code: Select all
title tinycore32 sda5
root (hd0,4)
kernel /tinycore32/boot/vmlinuz showapps tce=sda5/tinycore32/tce/ desktop=flwm_topside
initrd /tinycore32/boot/core.gz
7. After booting, I loaded the needed wireless tcz files and, from opened terminal used
wifi.sh to connect using following commands:
Code: Select all
tce-load -i firmware-iwlwifi wifi
Code: Select all
sudo wifi.sh
Code: Select all
ping google.com
or whatever now works from a terminal etc...
At this stage you can download/install, using tc's GUI "Apps" browser program, whatever apps tinycorelinux has in its repo.
----
If your machine doesn't use firmware iwlwifi then you need to find and substitute the firmware-<your_wifi_firmware>.tcz etc for your system.
Much the same as above is required, on my iwlwifi machine at least,
for a tinycorelinux 64-bit version install, but grub4dos menu.lst very different cos 32-bit tiny core by default uses Xvesa whereas 64-bit uses X framebuffer (though you can later install Xorg in either version); so my menu.lst for the 64-bit tinycorelinux using framebuffer is as follows:
Code: Select all
title tinycore64 harddrive sda5
root (hd0,4)
kernel /tinycore64/boot/vmlinuz64 loglevel=3 tce=sda6/tinycore/tce/ vga=791 video=vesafb:ywrap,mtrr:3
initrd /tinycore64/boot/corepure64.gz
All-in-all, tinycorelinux is a great little swiss-army-knife of a system - and nice just using ondemand loading cloud-stored apps for whatever you want to do whenever... though it's also easy enough to store the apps permanently/with-persistence and for immediate availability on boot. You'll also want to get used to using sudo for root-access permissions to directories outside of tc home (though fluff includes sudo inbuilt capability for when you need it). The default-provided FLWM desktop window manager is also super tiny and flexible (though you can change to JWM or openbox, for example, if you wish) - just right-click on its background for Application management and lots of other stuff...
EDIT: Note that, by default, tinycore can read files from ntfs filesystems too, but if you want to ability to also write to ntfs you need to download/install ntfs-3g.tcz.
EDIT2: I've also tested current slitaz-rolling release. A very easy frugal install for that one and beautiful to use and look at. Find my report/howto below link:
http://www.murga-linux.com/puppy/viewto ... 157#990157
Slitaz is best of breed for me.
wiak
EDIT_28Mar2019: Posting from latest 64bit Tiny Core Linux version 10.x right now. I used 'Apps' browser program to first search for fastest mirror, and then used Apps -> Cloud (Remote) ->Browse to fetch (OnBoot selected): firefox-Getlatest.tcz (followed by running the resultant installed shell script firefox-Getlatest.sh from terminal). So using Firefox Quantum 66.0.2. Normally, I'd actually use a separate firefox simply downloaded from Mozilla and uncompressed in its own folder for sharing between my distributions, but this was just a test install on TC. With this latest firefox installed, TC installation is taking up 144 MiB on disk. EDIT: I noticed wayland.tcz installed with firefox but that seems to just handle some 'wayland protocol' so I guess still just Xvesa framebuffer being used. Of course, default Xvesa framebuffer 64bit TC install, without firefox, is very small indeed: just 22 MiB disk space! Now installing bash, core-utils, mtpaint, geany, and mpv (since has Xorg as dependency - this will all swell the install size): Now 206 MiB, so approaching Puppy size as expected... However, best is, I feel, to use the tiny 22MB default install (albeit maybe inflated with Xorg) and load the likes of firefox ondemand only or better still as portable external apps (usable also by other distros installed).