Still having no luck with any of the derivatives of 18.04 that I've tried (Black Lab, LXLE, Ultimate, Voyager); either there's no sound on playback or they won't boot at all on my machine. I've gone back and installed an old version of Bodhi (4.2), which works fine, as does the latest version of Sabayon XFce (18.05)._________________Packard Bell iMedia 6020 (AMD Athlon 3800+, 4 GB of RAM, 250 GB hard drive) running Slackel Openbox 7.1, AntiX 19a1, Bunsen Helium 4, VLocity 7.2, Debian stable 9.6,, Puppy Xenial 7.5 CE and Pardus 17.5.

Bunsen Labs have just released Helium RC1, the latest iteration of their fork of the well regarded CrunchBang distro.

I haven't installed it but it's working well as a live disk; the theme colours though, which range from grey through to blue and slate blue on to inky black, may be a bit too sombre and dramatic for some people's taste.

Here's a short video, provided by someone called Distro Tester on Youtube;

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:

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.

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:

Code:

tce-load -i firmware-iwlwifi wifi

followed by:

Code:

sudo wifi.sh

That's it.

Code:

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:

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:

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

screenshot_tinycorelinux32.png

Description

tinycorelinux 32-bit screenshot

Filesize

124.51 KB

Viewed

1458 Time(s)

Last edited by wiak on Sun 31 Mar 2019, 06:46; edited 18 times in total

A bit tricky to set this one up for me (to get wireless working) and persistence/remastering, but I thoroughly recommend you put in the effort and give it a try. It's a nice wee system to actually use once you have all that set up and working (then it is a lovely fast breeze to use).

Downloaded iso from XenialDog64, clicked on it to open it up and copied its /boot folder to my hard drive /mnt/sda5/slitaz_rolling/

Then in terminal at that directory concatenated all the four separate rootfsX.gz into one rootfs.gz using command:

Wow... I'm always impressed by this beautiful tiny distribution (less than 50MB download); comes with openbox wm, pcmanfm filemanager, mtpaint, epdfview, and very nicely put together midori browser (which is also configured to act as a video player...).

For me, it is easily the nicest looking small distribution around, and the most efficient and full-featured for its size. Great piece of work.

To finish wifi config, I need to add the appropriate iwlwifi driver to /lib/firmware and then wifibox will find it (wifi now working on my HP Elitebook 2530p after taking iwlwifi-5000-5.ucode from my 32-bit xenialdog system and putting copy into slitaz /lib/firmware). Same procedure applied if you want to use slitaz-cooking version instead.

EDIT re 'persistence': tricky thing is getting 'persistence' of changes with Slitaz - that is where it is clumsy unfortunately. You can get persistent /home using grub4dos kernel line extra: home=sda5 (or whatever partition you want as /home or home=usb if using usb stick). But... for major filesystem change, like new apps you have to re-write rootfs.gz; there is a utility in Slitaz for that called via command "tazusb writefs gzip" (really, this part of things is remastering rather than usual persistence - you need to arrange for the new rootfs.gz to over-write the old one). I have since studied tazusb, which is just a shell script. Turns out you can give full path to the rootfs.gz you are wishing to remaster, so I actually used command:

I'd like to modify this operation somewhat to be more like tinycorelinux, which saves only what changes you want rather than remastering the whole rootfs.gz - then could arrange proper automatic persistence. I'll report back if I manage to make that addition sometime, which is what slitaz lacks IMO.

Following the above, I now have wireless connection and sending this post from my Slitaz frugal install at this moment (via Midori). Note that I am using home=sda5 on my menu.lst kernel line AND copied iwlwifi-5000-5.ucode from my XenialDog32 to /lib/firmware/ on Slitaz AND then remastered Slitaz rootfs.gz using the above tazusb command. Note that you need to use the appropriate wifi driver for your system. That particlar iwlwifi firmware happened to be the correct one for my system.

NOTE that you CAN login to Desktop of root user (default password root) or as user tux (default no password), so use sudo if tux, but don't need sudo if, unwisely many would say, you logged in as user root.

NOTE: The memory used value in Slitaz 'free' utility (see screenshot) may look a lot, but actually it is fantastic cos that is with absolutely everything loaded to RAM (including midori) - hence the incredible speed. Also CPU utilisation in top is close to zero most of the time (i.e. 100% idle).

The folder contents size of my current tinycorelinux32 is 80Mb with hardly any actual applications in it. After extraction of slitaz /boot from the 50MB iso, my slitaz folder is only 99.8 MB with all sorts of apps including:

Couple of problems:
- Touchpad "tap-to-click" is on (which i loathe). Can't get into /root/.flsynclient because I don't have root permissions (thank god for BK and puppy)
- Can't find a way to get wifi working (posting from eth0)

Other than these minor issues it is very impressive! (No hangs from Midori yet...)

Please see my Slitaz post again greengeek - I basically explain how to add a firmware driver for wifi and how to then remaster the rootfs.gz - it isn't as difficult to do as it sounds.

As for root user - I also mention that you CAN in fact login to the desktop as user root (with root password also root). Then you don't need sudo and you can use pcmanfm filemanager to move anything about just as easily as in Puppy.

I was very surprised that that particular Midori is working with:

bbc news
gmail.com

and even...

facebook...

youtube video playing worked for me too, though it couldn't do fullscreen (but did do theatre-mode).

With facebook, you do need to click ok on some box that pops up about Javascript (I think it is) and to see the chat messages you need to click on the Messenger link - it all seems ot work though (despite Facebook suggesting you upgrade the browser). That's a huge plus if this Midori proves reliable since it is very lightweight - let's hope it doesn't crash (Facebook seemed to freeze and I did killall Midori, but it hadn't actually crashed at all, I just didn't notice the popup about Jave-something that I had to click ok on...).

All in all, Slitaz is amazing low resource using - must be a great contender for old laptop that can't really handle firefox and so on. But if this Midori doesn't crash then I like it even on this machine that normally does run Firefox or Chrome - should be able to open far more tabs before RAM runs out...

Basically for wireless you just need to get the 32bit driver firmware you are using elsewhere and copy it into your Slitaz /lib/firmware/ directory and then remaster... which is a simple one line command:

Code:

tazusb writefs gzip <path_to_where_existing_rootfsgz_is>

but see my above Slitaz post for more details since you need home=... persistence set up in your grub4dos menu.lst first.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum