May be the last post as a Slacker (warning: long post)
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Perhaps because they value this community: it used to be more friendly and helpful most of the time. Less of this "don't let the door hit you on the way out" attitude.
I came over to the Slackware community only a few years ago and I've never found them to be anything other than helpful. It's the Archers who are intellectual snobs.
Grub looks like too much work. I just need to run elilo once to register it to nvram then I can copy the new vmlinuz and intitrd.gz to the Slackware folder on the efi partition after each update.
Grub could actually mean less work. When it's configured to use versioned kernel names, there is the need for a new grub.cfg after kernel upgrade. It would be the same with lilo.conf or elilo.conf with 'image' lines referring to versioned kernels. But grub can also be configured to look for '/boot/vmlinuz' instead of versioned kernel names. Then grub will find the new kernel on the root filesystem behind the /boot/vmlinuz link: no need to run 'lilo' or copy the kernel to the efi partition for elilo.
Grub could actually mean less work. When it's configured to use versioned kernel names, there is the need for a new grub.cfg after kernel upgrade. It would be the same with lilo.conf or elilo.conf with 'image' lines referring to versioned kernels. But grub can also be configured to look for '/boot/vmlinuz' instead of versioned kernel names. Then grub will find the new kernel on the root filesystem behind the /boot/vmlinuz link: no need to run 'lilo' or copy the kernel to the efi partition for elilo.
Good point. I used lilo for almost 20 years and I switched to grub recently. I was a bit worried about how much I will need to learn and what will be necessary to do after kernel upgrades, especially since I'm running the current line. Finally, I found out that all I need to do after an upgrade is:
Code:
cp /boot/vmlinuz-huge-x.x.x /boot/efi/EFI/Slackware/vmlinuz
and
grub-mkconfig -o /boot/grub/grub.cfg
Btw, as @Petri Kaukasoina pointed out, I probably didn't need to rerun that second one at all.
cp /boot/vmlinuz-huge-x.x.x /boot/efi/EFI/Slackware/vmlinuz
and
grub-mkconfig -o /boot/grub/grub.cfg
Btw, as @Petri Kaukasoina pointed out, I probably didn't need to rerun that second one at all.
I think the first one is not needed. Try this:
Code:
grep [[:space:]]linux /boot/grub/grub.cfg
It shows the 'linux' lines which load the kernel. If there is a line which starts 'linux /boot/vmlinuz-huge-6.9.1' then it will load the kernel from /boot (in the root filesystem, not in the EFI filesystem). The copy in /boot/efi/EFI/Slackware is not used.
But your second line is also unnecessary if you do a little change. Edit file /etc/grub.d/10_linux. Search for the first line with word 'vmlinuz'. It's this:
Code:
for i in /boot/vmlinuz-* /vmlinuz-* /boot/kernel-* ; do
Change it to:
Code:
for i in /boot/vmlinuz ; do
Then make sure that 10_linux is executable but the editor backup copy is not. Then
Code:
# grub-mkconfig > /boot/grub/grub.cfg
Now /boot/grub/grub.cfg will load the kernel using a line starting 'linux /boot/vmlinuz' and there is no need to rerun grub-mkconfig after kernel upgrade.
Last edited by Petri Kaukasoina; 05-24-2024 at 06:36 AM.
A SINGLE pkg manager, a SINGLE distribution, a SINGLE web browser, a SINGLE DE, a SINGLE graphic card, etc ...
Ok, but who decides?
Does everybody like RPM, RedHat, Chrome, Gnome, Nvidia ...?
I think I stumbled on the perfect example to use as a response:
since I have been involved with graphic, posters/marketing, etc. in the last year or so, one of the first cpl of packages that i always install when running a clean slackware are 'scribus' and 'inkscape'.
let's use the former: scribus
First SBOPKG
Code:
bash-5.2# sbopkg -i scribus
###########################################
New queue process started on:
Fri May 24 13:31:18 -01 2024
###########################################
+++++++++++++++++++++++++++++++++++++++++++
PRE-CHECK LOG
Using the UNSUPPORTED SBo git repository for -current
Queue Process: Download, build, and install
scribus:
GPG checks not supported for the SBo-git repository.
Processing scribus 1.6.1-1
Using original .info file
Using original SlackBuild file
No build options selected.
+++++++++++++++++++++++++++++++++++++++++++
Pre-check complete.
Do you wish to proceed based on the search results above? Packages not
found will be skipped during the process.
(P)roceed or (Q)uit?: p
..........
..........
[ 68%] Building CXX object scribus/plugins/import/pdf/CMakeFiles/importpdf.dir/importpdf_autogen/mocs_compilation.cpp.o
[ 68%] Building CXX object scribus/plugins/import/pdf/CMakeFiles/importpdf.dir/importpdf.cpp.o
In file included from /usr/include/poppler/Error.h:35,
from /usr/include/poppler/GlobalParams.h:47,
from /tmp/SBo/scribus-1.6.1/scribus/plugins/import/pdf/importpdf.cpp:23:
/usr/include/poppler/goo/GooString.h:241:24: error: ‘starts_with’ has not been declared in ‘std::string’
241 | using std::string::starts_with;
| ^~~~~~~~~~~
/usr/include/poppler/goo/GooString.h:244:24: error: ‘ends_with’ has not been declared in ‘std::string’
244 | using std::string::ends_with;
| ^~~~~~~~~
make[2]: *** [scribus/plugins/import/pdf/CMakeFiles/importpdf.dir/build.make:95: scribus/plugins/import/pdf/CMakeFiles/importpdf.dir/importpdf.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:5311: scribus/plugins/import/pdf/CMakeFiles/importpdf.dir/all] Error 2
make: *** [Makefile:156: all] Error 2
scribus:
Would you like to continue processing the rest of the
queue or would you like to abort? If this failed
package is a dependency of another package in the queue
then it may not make sense to continue.
(Y)es to continue, (N)o to abort, (R)etry the build?: y
+++++++++++++++++++++++++++++++++++++++++++
SUMMARY LOG
Using the UNSUPPORTED SBo git repository for -current
Queue Process: Download, build, and install
scribus:
MD5SUM check for scribus-1.6.1.tar.xz ... OK
Error occurred with build. Please check the log.
+++++++++++++++++++++++++++++++++++++++++++
###########################################
Queue process complete!
###########################################
bash-5.2#
SLPKG
Code:
bash-5.2# slpkg -b scribus
Database loading... ✔
Resolving dependencies... ✔
┌──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┐
│ Slpkg Build Packages │
├──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┤
│ The following packages will be build: │
├──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┤
│ Package: Version: Size: Repo: │
│ scribus1.5.7 sbo │
└──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┘
Total 1 packages will be build in /tmp folder.
Do you want to continue? [y/N] y
.....................
-- Autogen Include Path: /tmp/SBo/scribus-1.5.7/scribus/scribus_autogen/include
RPATH: lib64/scribus/plugins/;
-- Qt5::CoreQt5::WidgetsQt5::GuiQt5::XmlQt5::NetworkQt5::OpenGL/usr/lib64/libxml2.so/usr/lib64/libz.so
-- Qt based Markdown plugin: Qt version >= 5.14.0 Ok, Installed Qt version: 5.15.13
-- Found PkgConfig: /usr/bin/pkg-config (found version "0.29.2")
-- Checking for module 'libcdr-0.1>=0.1'
-- Found libcdr-0.1, version 0.1.6
Building Corel Draw Importer with librevenge
-- Checking for module 'libfreehand-0.1'
-- Found libfreehand-0.1, version 0.1.2
Building Freehand Importer with librevenge
-- Checking for module 'libpagemaker-0.0'
-- Found libpagemaker-0.0, version 0.0.4
Building Pagemaker Importer with librevenge
-- Checking for module 'libmspub-0.1>=0.1'
-- Found libmspub-0.1, version 0.1.4
Building MS Publisher Importer with librevenge
-- Checking for module 'libqxp-0.0'
-- Found libqxp-0.0, version 0.0.2
Building QuarkXPress Importer
-- Checking for module 'libvisio-0.1>=0.1'
-- Found libvisio-0.1, version 0.1.7
Building MS-Visio Importer with librevenge
-- Checking for module 'libzmf-0.0'
-- Found libzmf-0.0, version 0.0.2
Building Zoner Draw Importer
-- Building with Scripter 1
-- No source header files will be installed
-- /tmp/SBo/scribus-1.5.7/resources/translations
-- The following GUI languages will be installed:
-- Configuring incomplete, errors occurred!
=======================================================
Error occurred with process. Please check the log file.
=======================================================
bash-5.2#
PKGS.ORG
Code:
Slackware Current
Slackel x86_64 Third-Party
scribus-1.4.7-x86_64-1dj.txz open-source professional page layout program
Slackers x86_64 Third-Party
scribus-1.6.1-x86_64-4cf.txz open-source professional page layout program
it's worth mentioning that pkgs.org lists scribus with seven dependencies, which only 3 are already present in slackware (i know, bcos i went through the process of checking them one-by-one and then installing the mising deps)
Code:
Scribus is an open-source program that brings award-winning
professional page layout to Linux/Unix, MacOS X and Windows
desktops with a combination of "press-ready" output and new
approaches to page layout.
Alternatives 1
Package Version Arch Repository
scribus-1.4.7-x86_64-1dj.txz 1.4.7 x86_64 Slackel Third-Party
scribus All All All
Requires 7
Name Value
libcdr -
libfreehand -
libmspub -
libpagemaker -
libqxp -
libzmf -
podofo
Two package management systems for the same distro have two different versions of the same package and a 'try-to-unite-them-all' website has one more and, guess what: none of them works.
Scribus installed perfectly 3days ago (as i said, it's always one of the first installs, when I had the system seemingly working and then found out in the morning that everything was broken again).
Similar thing with inkscape (can't build it and the binary i find on pkgs.org won't launch).
I am not sure I am entitled to comment on this matter, or perhaps 20yrs of using the OS give me a little reason to say something, but if I were Patrick I would definitely say: what the heck is happening to my distro? how is this possible? 1 package, 3 sources, none of them is working!!
My computer again? maybe? hardware-software-hardware-soft....! I just have a CLEAN slackware. How can hardware issues cause this?
we all love you too...
since we all are in love (its no ironic) and since after 15 years of slacking you cant realize the wrong output
Quote:
bash-5.2# sudo inxi -r
Repos:
Active sbopkg repo: /etc/sbopkg/sbopkg.conf
1: SBo-git ~ current
slackpkg mirror in: /etc/slackpkg/mirrors
1: https://mirrors.slackware.com/slackw...are64-current/
slackpkg+ repos in: /etc/slackpkg/slackpkgplus.conf
1: slackpkgplus ~ https://slakfinder.org/slackpkg+15/
No active slpkg repos in: /etc/slpkg/repositories.toml
bash-5.2#
PLEASE day a day off... get out drink a beer , a coffee , wine... what ever you like and clean your mind from Slackware, Linux, PC and all these stuffs...
Next day you will fix everything alone... trust me.
I did it when friends suggested and it works 100%
we all love you too...
since we all are in love (its no ironic) and since after 15 years of slacking you cant realize the wrong output
PLEASE day a day off... get out drink a beer , a coffee , wine... what ever you like and clean your mind from Slackware, Linux, PC and all these stuffs...
Next day you will fix everything alone... trust me.
I did it when friends suggested and it works 100%
ahahah you are right! My last brain-cell left is over-spinning like a crazy mouse-wheel.
I noticed the wrong output once i run the line you suggested; i just didn't know about that command.
Two package management systems for the same distro have two different versions of the same package and a 'try-to-unite-them-all' website has one more and, guess what: none of them works.
Scribus installed perfectly 3days ago (as i said, it's always one of the first installs, when I had the system seemingly working and then found out in the morning that everything was broken again).
Your error message was about poppler. It was upgraded in -current a day or two ago. "l/poppler-24.05.0-x86_64-1.txz: Upgraded. This seems to require C++20 now...". In ponce git there seems to be scribus-1.6.1-poppler-24.03.patch from last week. I guess there is a need for a new patch. -current is a moving target. It can take more than a day or two to get slackbuilds upgraded. The ready-made binaries you found are even much older. Maybe you could try the stable 15.0?
You have an either or choice. It's either the the distro or the hardware.
What made you decide to replace the video card?
How old is the motherboard?
well, for a while the pc wouldn't even boot with the video card and, according to the technician, at service centre, who tried to diagnose the problem it was a faulty video card. So, i bought another one (which i am still waiting for from China). However, about a month after that expert 'diagnosis' I tried the card for curiosity and it was working flawlessly. I am still on it actually and typing this post from it. In reality though, the computer acts strange at random times i.e. it doesn't start or, all the fans go at top-speed as if it was melting or, LILO/GRUB detect non-existent partitions.... really strange things!
Quote:
Originally Posted by quickbreakfast
By the way do you have the same problem(s) running say Alienbob's live version?
I didnt try Alienbob's live CD yet; however, a few days ago, in a desperate attempt to rule out distro issues, I installed the latest Debian-12.5 and it was like 'healing-of-the-dead'. One single attempt at installing a distro that i have never used resolved all the issues. No lines on screen, no partitions confusion, etc...
Oh yes, I forgot to mention the lines on screen which, for some reason, I cannot show here because I cannot attach any files regardless of file-size; https://file.io/IO3vdi1ESxjl. These lines started about 5-6 system updates ago, during one of those kernel/MESA dance.
However, about a month after that expert 'diagnosis' I tried the card for curiosity and it was working flawlessly. I am still on it actually and typing this post from it. In reality though, the computer acts strange at random times i.e. it doesn't start or, all the fans go at top-speed as if it was melting or, LILO/GRUB detect non-existent partitions.... really strange things!
Definitely hardware and not just the video either. It's actually quite common for hardware problems to come and go in the way you describe for your video card. But the wider problems suggest a screwed-up motherboard to me.
Quote:
a few days ago, in a desperate attempt to rule out distro issues, I installed the latest Debian-12.5 and it was like 'healing-of-the-dead'. One single attempt at installing a distro that i have never used resolved all the issues. No lines on screen, no partitions confusion, etc...
So use Debian for the time being. As long as it goes on working, you're OK. If it starts playing up in the same way, get a new machine.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
