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.
I have been using Slackware 14.1 updated to current without any problems until I updated to current 11 August. That's when I thought I had screwed up lilo. After backing up my disk, I attempted to install current Slackware 14.2 using Alien's mirror script. That is when I discovered that 14.2 will not install on my system (Asus M4A88TD-V EVO/USB with AMD Phenom CPU). This is what occurs during a new installation:
The recent Slackware insistence to go 64bit wide from bottoms up.
That comment does not make any sense at all. The 64bit Slackware release is 7 years old, and 32bit Slackware is just as much supported as the 64bit variant. I guess you are confused and are thinking about Ubuntu?
After many trials of installing and booting, I have definitely identified the latest 14.2 -64 current kernel as the culprit.
I was finally able to get a good system with a 14.2 64 bit patches only updates to work.
The latest 14.2 -64 current kernel (4.4.17) on August 11 will cause my AMD Phenom II 64 bit 6 core cpu to act like it is running at one hertz (joking). After 10 minutes, it actually will boot up normally. A reboot will again take another 10 minutes to start.
My primary problem is solved, and I hope the next current kernel will work for me.
The 64bit Slackware release is already 7 years old, and 32bit Slackware is just as much ignored/sabotaged, as we can, in favor the 64bit variant.
I corrected for you, my dear Eric...
Give me the favor to believe that is also the result of developing everything on 64bit, even that MATE shit, which, after all, is a fair runner for... XFCE position?
That call to Dark Side would be find disturbing even by Darth Vader!
Last edited by Darth Vader; 08-14-2016 at 07:03 AM.
Give me the favor to believe that is also the result of developing everything on 64bit, even that MATE shit, which, after all, is a fair runner for... XFCE position?
That call to Dark Side would be find disturbing even by Darth Vader!
You are so full of bullshit that I can't begin to find the words to describe it for fear of getting painted brown.
If you think the 32bit variant is not getting enough attention why don't you contribute by writing actually useful contributions that are free of ALLCAPS and free of insulting and contemptuous remarks? And do that during the development cycle, not afterwards?
Unlike a Monty Python script, I didn't come here for an argument. I want to fix the problem with the 4.4.17 kernel. I compared the kernel config files for 4.4.17 against 4.4.14, and they are identical. 4.4.14 works OK, 4.4.17 doesn't, at least not normally.
Unlike a Monty Python script, I didn't come here for an argument. I want to fix the problem with the 4.4.17 kernel. I compared the kernel config files for 4.4.17 against 4.4.14, and they are identical. 4.4.14 works OK, 4.4.17 doesn't, at least not normally.
Pat himself noticed this behaviour with some of the 32bit 4.4.x kernels: http://www.linuxquestions.org/questi...1/#post5559180 ... apparently it's only in 4.4.13 and 4.4.14 where the early boot works at normal speed.
I've got a similar problem with -current on an Intel i7. I added verbose=5 to elilo.conf and it prints out the following
Code:
read_config=Success
trying chooser simple
selected chooser simple
kernel is 'vmlinuz'
arguments are 'root=/dev/sda2 vga=normal ro ro'
ELILO v3.16 for EFI/x86_64
.
Probing loader: gzip_x86_64
Probing loader: plain_elf64
plain_probe: kname=vmlinuz
Probing loader: bzImage_loader
kernel header (2.13) suggests kernel start at address 0x100000 (relocatable!)
kernel_start: 0x100000 kernel_size: 8388608
Loading kernel vmlinuz... done
Using bzImage_loader loader
kernel loaded in [0x100000-0x900000] entry=0x100000
final cmdline(0): BOOT_IMAGE=dev000:\EFI\Slackware\vmlinuz root=/dev/sda2 vga=normal ro ro
...............
_
Each of those 15 dots takes a second to print and then it sits at the static prompt for a further 54 seconds before the kernel messages start. Only started doing it when I upgraded to 4.4.17 a couple of days ago.
The latest kernel update to 4.4.19 fixed the problem of the ultra slow boot up.
Maybe the kernel modules contributed to the problem. Life is good again.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.