Is anybody else having this problem with the Slackware installer?
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.
Is anybody else having this problem with the Slackware installer?
I just installed Slackware 12.2 today. During the installation of all the packages, the installer would hang every few minutes. I was able to get it to start working again by pressing any key on my keyboard, so it's not that big a deal. Just wondering if anyone else was having this problem
Yeah...I saw that too for a bit. I didn't do anything about it, I went to the fridge for another beer. The 12.2 install continued and finished up successfully.
I've noticed one oddity. Not a big deal really. I have a HP Laserjet P2015 printer. When I was setting up the printer in KDE 3.5.10 I received an error message when I selected my printer. I clicked through the dialogue boxes and the printer works just fine.
However, when I print a document the green printer "ready" light flashes continually after the print job is finished. This did not happen in 12.1. I noticed during the install process that in 12.2 the printer drivers have changed somewhat.
When I did the upgrade to current I noticed that one or two of the packages took a very long time to install. Gutenprint was one of them. I fired up a 'top' and found it was running some command which looked like it was compiling printer definition files. My box is only a p3-800 so any places were it gets 'busy' are emphasised.
It's possible that the pause you saw was just something like this and that pressing enter didn't actually do anything to help. Alternatively, you may have found some other sort of bug. I just raise this as a possibility.
I installed two systems from a late -current custom DVD, and I experienced these pauses on my HP notebook but not on my desktop. It seemed to 'go to sleep' after installing very small packages and had to be woken up by hitting a key. It was the first time I'd installed Slack on this notebook so I chalked it up to a notebook quirk.
When I did the upgrade to current I noticed that one or two of the packages took a very long time to install. Gutenprint was one of them. I fired up a 'top' and found it was running some command which looked like it was compiling printer definition files.
I confirm that upgrading gutenprint took a long time, about 10 minutes on my 500MHz desktop. The long running command was "cups-genppd".
Another weird thing that happened was the installer hung for a while at the part where it runs "fc-update." I saw a bunch of text fly by the screen, but it went away too fast for me to read it. I reran fc-update again after installation just to make sure nothing was wrong.
I just got my system configured the way I want it, even built a custom kernel. Everything seems to be working fine.
I had the gutenprint "hang" but that was about it. What was annoying was that it seemed to be inside the package installation itself (unlike similar tasks like fc-cache etc.) and on a Dual-Core machine it sat there spinning on one CPU... I'm sure things like this must be able to be forked out to a seperate process.
Surely in the well-checked confines of the official install process, we can spawn two or three threads each installing a package - order is catered for already in the process because I can just slap any random collection of packages onto a CD to make it fit and the installer sorts it out and things don't stomp over each others files anyway. On a lot of machines, I/O isn't the bottleneck during install, it's the un-gzipping of things like the kernel source.
I noticed a few delays during the install too.
When I hit alt-F4 I saw some error messages pertaining to hdc and hdd
(which are not present on my system).
Don't remember the exact message though,
and don't know if this has anything to do with the pauses during installation.
The install eventually finished and all seems fine now.
i did the installation from hdd, and in the part of the fc-update, take a lot of time, for a moment i think that maybe was because i did the install from hdd and with the 3 iso's, (the iso's of disk one, two and three), but well don't was just for me, to other people is happening the same with the fc-update.
And i don't know but with this install is taking me a lot config a good font, for instance gmail looks horrible. Well i will trying to find a good config for my fonts.
I've noticed one oddity. Not a big deal really. I have a HP Laserjet P2015 printer. When I was setting up the printer in KDE 3.5.10 I received an error message when I selected my printer. I clicked through the dialogue boxes and the printer works just fine.
However, when I print a document the green printer "ready" light flashes continually after the print job is finished. This did not happen in 12.1. I noticed during the install process that in 12.2 the printer drivers have changed somewhat.
Please disregard this post of mine. I fixed my printer issue. I selected a different driver for my HP Laserjet P2015 printer. Error messages and all issues are gone. Heh-heh, PEBKAC:-)
Many thanks to PV and the Slackware developers for delivering a first-rate version of Slackware. 12.2 rocks:-)
Many thanks to PV and the Slackware developers for delivering a first-rate version of Slackware. 12.2 rocks:-)
Slackware 12.2 Rocks?
Is Pat following Canonical's lead with release names now?
Can't wait for Slackware 13.0 Bouncy Boulders.
But, seriously, I think the lack of issues with this release is a real testament to Pat and the guys. Ubuntu would have had to replace a good 20-30 packages by this stage after a release day!
Is Pat following Canonical's lead with release names now?
Can't wait for Slackware 13.0 Bouncy Boulders.
But, seriously, I think the lack of issues with this release is a real testament to Pat and the guys. Ubuntu would have had to replace a good 20-30 packages by this stage after a release day!
LMAO.......Bouncy Boulders:-)
Agreed. I'm very impressed with the fact that 12.2 runs smooth as silk.
Well-done, gentlemen!!
But, seriously, I think the lack of issues with this release is a real testament to Pat and the guys. Ubuntu would have had to replace a good 20-30 packages by this stage after a release day!
Not to mention a few Kernel patches as well.........
Is Pat following Canonical's lead with release names now?
Can't wait for Slackware 13.0 Bouncy Boulders.
But, seriously, I think the lack of issues with this release is a real testament to Pat and the guys. Ubuntu would have had to replace a good 20-30 packages by this stage after a release day!
There were no real big changes here either - relatively speaking. The last .2 release was 10.2 and we waited a year (for a variety reasons) before 11.0 came out. Hard work of the team still acknowledged and appreciated though.
While this is probably the most "optional" upgrade I've seen in awhile, I agree with the choice to release now and save the next round of major changes for 13.0.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.