Slax author's Blog (RSS)
10
October2023
Slax's Recent Release: A Tale of Challenges
Last week marked a significant milestone for me as I released the latest version of Slax. Slax, for those unfamiliar, is a modern, portable, small and fast Linux operating system with modular approach and outstanding design. However, like any software release, it wasn't without its challenges.
The Slackware Hiccup
In my enthusiasm to refine and optimize, I made a last-minute decision to remove the devel-tools module, which I use during preparations of Slax based on Slackware. Little did I realize that this module housed crucial libraries for the X panel (xfce4-panel). As a result, the Slackware version of Slax faced issues. It's an unfortunate example of the unforeseen consequences that can arise from even well-intentioned changes.
The Debian Dilemma
While the Slackware version had its problems, the Debian version wasn't without its own set of challenges as well. A leftover whiteout file (.wh.*) in the chromium module led to an unexpected behavior. It gave the appearance as if the entire /root/.fluxbox folder had vanished into thin air. Consequently, the default fluxbox configuration was initiated, which was not the intended outcome. For users familiar with Slax, this was a noticeable and unintended shift :)
Rising from the Challenges
Acknowledging these issues, I immediately set to work. It's essential to understand that in the world of software development, challenges are not setbacks but opportunities to refine, learn, and grow, right? :) I'm pleased to announce that both the issues have been addressed and rectified. Updated ISO files have been released to ensure users get the best experience possible.
Moreover, the Debian version of Slax has been updated to version 12.2. and the Slackware version has been updated to align with Slackware current.
In Conclusion
Releasing software is a journey filled with excitement, anticipation, challenges, and learning. The recent release of Slax was no different. I'm grateful for your feedback and patience!
As usual, enjoy the new release, which you can download from www.slax.org
User comments
Hello Tomas!
I sent a picture of the driver /usr/lib/x86_64-linux-gnu/dri/i965_dri.so , i saw it in as linux-mint
happy birthday, Mr. Matejicek !!
Thank you for all the good work !!
mfg ,keinz
Thanks for both new releases.
Two quick notes: i couldn't load them (both) and after many retries i found out that only on CSM and not
on UEFI i was able to load both new releases. Also (someone had mentioned it before), on Slack there is sound
but not on the Debian distro.
Hello,
I don't know where to ask si i'm posting hère.
I can't boot recent slax versions, be it 32, 64, debian or Slackware variants.
The kernel allways hangs
I am not sure how to describe but I took a screenshot.
Here it IS
pasteboard.co/gMV1BInGeOaw.jpg
I Hope somebody can forward it to thomas.
Or knows a boot parameter to fix this problem.
Thank you.
@GeMo,
How long did you wait? Above 11.4, it hangs for about 5 minutes on bootup on my system. I didn't think anything was going on, then it finally completed booting and was normal speed after that. Some kind of timeout I am hitting I believe. You might try the boot parameter acpi=off, but you might then have other problems like fans not working.
Pat
@parrothead
thank you very much for the quick and useful reply.
acpi=off worked.. kind off. Only console was available .
But waiting surprisingly was better.
Is there a way to reduce the loading time?
As you might guessed it's an old 64bit acpi laptop.
@GeMo
Glad it is working now! I have not found a way to reduce the startup time. Mine is also an old laptop, Toshiba. I don't think it is the slowness of the machine because 11.4 boots normally, and 12.x runs at a normal speed once it is booted. I think the kernel is waiting for something at bootup, then finally gives up after 5 minutes but I don't know what. I leave my system up for long periods so bootup time isn't critical for me. I would guess that after these new kernels get more widespread use, that either the kernel developers will fix what is causing the hang, or owners of these old laptops will figure out a boot parameter to work around it.
Pat
@parrothead
Braking news ;)
After watching the moment it's hangs, and trying to follow the same in dmesg output,
pasteboard.co/PGzy6ZwcB2h1.jpg
The solution was in the dmesg log, the kernel parameter to be added is
tsc=unstable
Works like a charm ????
Hope it will help someone else.
Cheers
@GeMo
Great news - I'll have to try that the next time I need to reboot!
Pat
My curiosity got the best of me so I decided to reboot and try tsc=unstable. It worked for me too - eliminated the long bootup I'd had with recent kernels. I've only been running for a couple of hours so far but I have not seen any other problems from using this boot code.
Pat
Highly energetic article, I liked that bit. Will there be a part 2?
Hi. Thank you Tomas for this OS. My only problem is that I cannot connect to my wifi network. Any ideas for how I can fix this?
Windows defender Detected:
Trojan:Script/Wactac.H!ml
Status: Active
File:
slack-64bit-Debian-12.2.0.iso->slax\boot\initrfs.img->(xz)->bin/@mount.httpfs2
I am going to assume it is a false positive. People on Reddit have reported similar things with programs they and their friends created.
The checksum is right as well.
I don't think popular Linux developers are making viruses.
Slax wento from 292mb (slax-64bit-11.6.0) to 416mb (slax-64bit-debian-12.2.0), why?!?
Thanks for excellent information. What trips can you recommend in 2024? Astro tourism, eco diving, home swapping, train stations are the new food destinations,sports tourism, coolcationing, gig tripping, private group travel?
I wrote the 6th comment and i found the solution (that works for me) to boot the latest builds on UEFI.
On the EFI folder that's created on the root of the drive i have to copy the "full" syslinux.cfg file (from slax\boot) and remove the path from the first line for UI vesamenu.c32
Hello Tomas,
I've been waiting for a fix for my problem but thus far the newest debian download as of yesterday still has not worked for me. I cannot get Slax debian to load the gui. The OS boots to the root login. I have tried startx but it fails. I noticed one other person was having the same problem (at the beginning of the comments section), where you requested the Xorg log files. I for the life of me cannot figure out how to get this to you. I saved logs to the documents folder but once the OS is exited, I cannot gain access to the file on the USB drive.
Thanks for any suggestions ( I was able to get slackware to run but my preference is debian).
venejo is correct - I had to follow his solution to get it working:
- replace syslinux.cfg file in \EFI\boot\ with syslinux.cfg file from \slax\boot\
- edit first line in syslinux.cfg (\EFI\boot\) to "UI vesamenu.c32"
I wonder if vesamenu.c32 in \slax\boot\ is corrupt? It's a different size...
I am so glad that I got to know linux, I am so happy that I found out SLAX.
I tried the latest 32 bit version and it was so REFRESHING.
Want to thank TOMAS and the entire team that goes into making, maintaining, debugging etc of Slax.
Pure Juy (that is what FREEdom in Linux means I hope!)
Hats of to people who make this world a better place to live in by living themselves selflessly.
Hello,
Please add SLAX ISO netboot to netboot.x.y.z. project, so it can be easily netbooted via PXE.
Sign in with Facebook
Sign in with Google
Sign in with Email
Hello again,
i tried the new slax (deb64, 12,2,0) and got the same errors as before. "No Display. Xinit: Server error. Couldnt connect to XServer - Connection refused". Nothing changed!
But the Slackware 64bit version 15.0.4 runs ok!!! Display, Server - all.
That is strange for me. Whats wrong with the deb-version?