Vous n'êtes pas connecté.
Pages: 1
I've been trying to revive an old laptop of using SliTaz; the laptop is quite limited as it only has ~700MB of RAM but I need it to run 64bit executables, which does not seem possible with SliTaz 5.0 even when using base64 (I presume this is caused by the userspace still being 32bit).
After some research, I found the fully 64bit development build of SliTaz 6.0(?) (https://people.slitaz.org/~shann/slitaz-current64-stuff/slitaz-current64-core64-grub2.iso) and so I decided to try that instead...only to discover that it panics rather quickly on boot supposedly due to the low RAM. I tried emulating the laptop using a VM and it also would panic *unless* the VM was given more than 700MB of RAM.
(A screenshot of the panic from the VM is included in this post.)
Is this a bug or just inevitable for a fully 64bit build? If it's a bug, is there anything I can do to get it to boot or should I wait for the proper stable release?
[attachment=54003,3852]
Hors ligne
Hi Rosy,
Sad to read this, which iso did you use ?
https://people.slitaz.org/~shann/slitaz-current64-stuff/isos/slitaz-current64-base64-grub2.iso
https://people.slitaz.org/~shann/slitaz-current64-stuff/isos/slitaz-6.0-base64-grub2.iso
For both i successfully boot with 512M (see qemu below)
Infact for core64 need at least 768Mo to boot correctly (need to improve this point, sorry).
base64 (console only)
core64 (full desktop)
Sorry for confusion (core should be rename desktop to avoid this)
[attachment=54005,3854]
Hors ligne
I tried all of the core64 iso I could find in there, but I didn't try the base64 ones as the executables I need to run are all graphical... (I did try base64 now and it *does* boot)
it seems my laptop is just barely below the RAM requirement...what are the chances that the requirement is lowered?
thank you for the quick response!
Hors ligne
I just noticed that in my first post I accidentally wrote "base64" instead of "core64", whoops.
The two are easily confused...core should 100% be renamed as you said lol
Hors ligne
Hello Rosy.iso,
You can boot base64 and install it, then install Xorg, Openbox (the only WM available in the current64 repo I believe) and SLiM.
Or if you prefer a "ready to use image", I could send a link to you to download some rootfs: one with the WM e16 (< 30M), another one with an old release of xfwm4 in stanalone mode (< 70M). I’ll just need to clean them a few before.
Hors ligne
I'd probably mess up the manual installation somehow so, if it's not a bother, I'd prefer the ready to use .iso file, thank you for your time!
Hors ligne

OK, just let me a few time to cleann the rootfs from all the specific things. I think the e16 rootfs can be ready today or tomorow. I've so things to do (bake a rhubarb pie for five o'clock, and one with onion for tonight
)
For xfwm4, will need a little more time, but with this stormy week that should do it.
the executables I need to run are all graphical
Just curious, what apps? Hope they will be compatible.
Hors ligne
AppImages beta builds of my games! I'm a gamedev and I believe that culture should be accessible to everyone, so I want to make sure my games work on low end specs too.
AppImages usually work on every Linux distro, so I hope they won't have too many issues running on SliTaz.
Hors ligne
Hi Rosy, i renaming iso to avoid confusion.
base64 => console
desktop64 => full desktop
For desktop iso, let's check to rebuild iso lighter to be use with 512M.
Hors ligne
I need to improve but desktop64 iso can boot with 700M of memory now, for 512M kernel panic due of rootfs size can't ship.
Think need to create alternative iso don't embedded firmware-amdgpu (~70Mo uncompressed) it's necessary only with laptop/desktop have amd ryzen with integrated gpu.
Hors ligne
That was already quick work, nice! SliTaz has a wonderful dev team 
Hors ligne
I put iso here, it's ok with 700Mo (with 600Mo it's ok but for 512Mo kernel panic due of rootfs size ~265Mo)
https://people.slitaz.org/~shann/slitaz-current64-stuff/isos/slitaz-current64-desktop64-noamdgpu.iso
compare to classic desktop64-grub2.iso :
web-applications, webgames, firmware-amdgpu has been removed.
Hors ligne
Thank you! I'll try it out and see what happens...
Hors ligne
Tried it on the VM and it did manage to boot just fine! The AppImage also...starts but immediatly crashes due to some missing libraries...though this probably is most likely fixable somehow.
I haven't tested the actual laptop since it's...worringly struggling to turn on at all right now, I'll let it charge for a while and then try again later.
(Included screenshot of the AppImage error)
Hors ligne
ok found issue line 4 your app said explicitly required glibc 2.35 minimum version but not found, infact my version "current" provide only glibc 2.34.
Hors ligne
will 2.35 be added eventually?
Hors ligne
Hello there,
Seems I arrive after the battle 
Not sure you still need a rootfs for your tests but here it is: https://share.mailo.com/?key=KpfLElel70t014MynYzvAxOSMFM7zCuW1oI%2BXy%2BVIpzFMlMRWh12pVtUQTNBg4ZQtWZ3VuFs2zo%3D
(clean= all stuffs specific for my computer and utilisation suppressed; hope it'll be really clean
)
Keep in mind this rootfs is built from Current64 so glibc= 2.34...; it will run with the same kernel that the one that is in the slitaz-current64-desktop64-noamdgpu.iso ISO.
Passwords are the usual passwords used in SliTaz: tux (no password), root:root
Only a few apps: dvtm, nnn, lynx and of course xterm (the xfwm4 rootfs will be more friendly with some graphical apps: Thunar, Mousepad, Palemoon)
Right click on the desktop opens the settings menu, left click the user menu.
Hors ligne
Thank you regardless, I appreciate the effort!
I guess now I gotta either wait for the updated dependencies or see if there's a way to manually install/compile the newer versions...
Hors ligne
Pages: 1
[ Généré en 0.017 secondes, 7 requêtes exécutées - Utilisation de la mémoire: 1.57 MiO (Pic : 1.77 MiO) ]