Main menu:

Sponsoring

Please consider a small donation:

 

 

Or you can donate bitcoin:

 

Thanks to TekLinks in Birmingham, AL, for providing colocation and bandwidth.

Page Rank

Fame

FOSS Force Best Blog--2013 Award

Recent posts

Recent comments

About this blog

I am Eric Hameleers, and this is where I think out loud.
More about me.

Search

Subscribe to Blog via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 345 other subscribers

My Favourites

Slackware

Calendar

December 2017
M T W T F S S
« Nov    
 123
45678910
11121314151617
18192021222324
25262728293031

RSS Alien's Slackware packages

RSS Alien's unofficial KDE Slackware packages

RSS Alien's multilib packages

RSS Slackware64-current

Meta

Refreshed ISO’s for Slackware Live Edition, and more

blueSW-64pxWhen I released new Live ISO images almost two weeks ago, a bug in the init script which became apparent with the latest Slackware initrd broke the encrypted /home feature. Therefore I am releasing an updated set of ‘liveslak‘ scripts with version 1.1.9.1 .

The latest set of Slackware Live Edition ISOs are based on liveslak 1.1.9.1 and Slackware-current dated “Fri Sep 29 22:58:54 UTC 2017“). That means, the new Live ISOs contain the updates to TexLive and Python3 (well, no texlive in the XFCE image due to its size limit of course).

If you already use a Slackware Live USB stick that you do not want to re-format, you should use the “-r” parameter to the “iso2usb.sh” script. The “-r” or refresh parameter allows you to refresh the liveslak files on your USB stick without touching your custom content. If you want to modify other parameters of your USB stick, use the script “upslak.sh“. It’s main feature is that it can update the kernel on the USB stick, but it also can replace the Live init script. As with most (if not all) of my scripts, use the “-h” parameter to get help on its functionality.

And more:

I built new versions for the palemoon packages for Slackware 14.2 and -current to the latest 27.5.0 version. Someone stated he had issues compiling on slackware-current so I made sure the palemoon.SlackBuild works. The new palemoon package is included in the refreshed PLASMA5 Live ISO image. Note that to compile this on slackware-current you will need my gcc5 package; this software cannot be built with gcc6. Before starting the compile, source the gcc5 profile script:
“. /etc/profile.d/gcc5.sh” – note the dot.

I updated the Chromium package as well.
Chromium had a recent bugfix upgrade to 61.0.3163.100 which I missed initially.

 

And even more:

The recent flurry of activity in the Slackware-current development tree (boost, poppler, python3), caused repeated broken-ness of my own packages. The collection of multilibcompat32” packages was renewed several times. I recompiled LibreOffice 5.4.1 for slackware-current and in my ‘ktown‘ repository for Plasma5 there were multiple updates. I did manage to ‘sneak in’ new versions for Krita and KDEConnect at the same time. This too is all part of the refreshed PLASMA5 Live ISO image.

Comments

Comment from DKK
Posted: October 1, 2017 at 23:43

iso2usb.sh didnt work. so I change 2 lines, first:
if ! tune2fs -O ‘^64bit’ ${TARGET}3 1>/dev/null 2>/dev/null ; then
to
if ! tune2fs -O ^64bit ${TARGET}3 1>/dev/null 2>/dev/null ; then
and:
FEAT_64BIT=”-O ‘^64bit'”
to
FEAT_64BIT=-O “^64bit”
and script start to work…

Comment from DKK
Posted: October 1, 2017 at 23:45

correction swcond line to:
FEAT_64BIT=”-O ^64bit”

Pingback from Links 2/10/2017: Linux 4.14 RC3, Claims of GNU/Linux Market Share of 6.91% in September | Techrights
Posted: October 2, 2017 at 14:33

[…] Refreshed ISO’s for Slackware Live Edition, and more […]

Comment from alienbob
Posted: October 2, 2017 at 14:53

Hi DDK…. that’s what happens when someone on 32bit Ubuntu complains to me about that “-O ^64bit” parameter. I forgot to actually check the code I modified to help him out.
Thanks for reporting the fix here!

Comment from joji
Posted: October 3, 2017 at 16:23

Just to say : Dank!

Downloading the slackware64-live-plasma5-current iso.

Comment from Nate Bargmann
Posted: November 3, 2017 at 18:38

Hi!

I am trying to get an HP Probook 6465B working with Liveslak 1.1.9.1 and whenever the startup sequence enables the frame buffer, the screen blanks and then the backlight shuts off. I see nothing after that and it doesn’t matter if I edit inittab to start run level 3 instead of 4. Where can I disable the frame buffer so that the console remains in 80×25 so I can log in and troubleshoot further?

I will be traveling for work next week and only want to deal with carrying one laptop. I have not tried any other live distribution yet.

TIA

– Nate

Comment from alienbob
Posted: November 3, 2017 at 19:48

Nate, first try disabling kermel mode setting (KMS). Your laptop should have an AMD Radeon HD 6520G inside and the linux “radeon” driver supports that one.
On the (syslinux or grub) boot commandline try adding either “radeon.modeset=0” or just “nomodeset”. If neither of those fix the issue I would suggest opening a support thread on the Slackware forum of linuxquestions.org as this is a generic Linux issue and has nothing to do with liveslak.
My knowledge of this old laptop is zero, perhaps people on LQ can add their voice.

Comment from Nate Bargmann
Posted: November 4, 2017 at 01:11

Thanks, Eric.

Using “nomodeset” worked to get to a console prompt. In the scrollby I saw something to the effect of ‘radeon module: no UMS support’. Then ‘startx’ brought up a scrambled screen that cleared and KDE started, which is seriously over taxing this poor old machine (supposed to get a new one sometime in the future).

Thanks for the tip.

– Nate

Comment from Nate Bargmann
Posted: November 4, 2017 at 03:53

On a final note, the issue is not present with the Slackware64 Liveslak. Also, the computer is actually running at its full potential now and KDE is flowing right along. With the 32 bit version only one CPU core was enabled (per htop) and only about half the memory was visible with a load average of around 2.00! Now it has a load average of 0.00 and all four cores visible along with the full amount of RAM.

Thanks again!

– Nate

Write a comment