LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 08-13-2016, 03:32 AM   #1
staus
Member
 
Registered: Apr 2004
Posts: 155

Rep: Reputation: 10
Slackware 14.2 Release will not install - help...


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:

boot:
Loading /kernels/huge.s/bzimage.......
Loading initrd.img .................ready

Then the screen goes blank and after about three minutes I see very very slowly this:

early console in decompress_kernel
input_data: 0x00000000024ea3b4
input_len: 0x00000000007382ca
output: 0x0000000001000000
output_len: 0x0000000001c0f748
run_size: 0x0000000001bdb000

I stopped after that.
I figured that I might have a corrupted iso, so I downloaded the official 14.2 release from a mirror. MD5 sum checked OK.

Booting from a genuine release iso gave me the same output as above.

So right now I'm Slack-less. What could possibly have changed?
 
Old 08-13-2016, 03:57 AM   #2
malekmustaq
Senior Member
 
Registered: Dec 2008
Location: root
Distribution: Slackware & BSD
Posts: 1,669

Rep: Reputation: 498Reputation: 498Reputation: 498Reputation: 498Reputation: 498
Quote:
What could possibly have changed?
The recent Slackware insistence to go 64bit wide from bottoms up.
 
Old 08-13-2016, 05:44 AM   #3
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 8,559

Rep: Reputation: 8105Reputation: 8105Reputation: 8105Reputation: 8105Reputation: 8105Reputation: 8105Reputation: 8105Reputation: 8105Reputation: 8105Reputation: 8105Reputation: 8105
Quote:
Originally Posted by malekmustaq View Post
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?
 
Old 08-13-2016, 03:08 PM   #4
STDOUBT
Member
 
Registered: May 2010
Location: Stumptown
Distribution: Slackware64
Posts: 583

Rep: Reputation: 242Reputation: 242Reputation: 242
Quote:
Booting from a genuine release iso gave me the same output as above.
Just to be clear, you're trying to install from a mounted .iso file?
 
Old 08-13-2016, 11:40 PM   #5
staus
Member
 
Registered: Apr 2004
Posts: 155

Original Poster
Rep: Reputation: 10
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.
 
Old 08-14-2016, 05:32 AM   #6
Darth Vader
Senior Member
 
Registered: May 2008
Location: Romania
Distribution: DARKSTAR Linux 2008.1
Posts: 2,727

Rep: Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247
Quote:
Originally Posted by Alien Bob View Post
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.
 
Old 08-14-2016, 08:44 AM   #7
allend
LQ 5k Club
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware64-15.0
Posts: 6,357

Rep: Reputation: 2739Reputation: 2739Reputation: 2739Reputation: 2739Reputation: 2739Reputation: 2739Reputation: 2739Reputation: 2739Reputation: 2739Reputation: 2739Reputation: 2739
The problem with a tin foil hat is that, although little gets in, garbled transmissions still get out.
 
2 members found this post helpful.
Old 08-14-2016, 10:26 AM   #8
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 8,559

Rep: Reputation: 8105Reputation: 8105Reputation: 8105Reputation: 8105Reputation: 8105Reputation: 8105Reputation: 8105Reputation: 8105Reputation: 8105Reputation: 8105Reputation: 8105
Quote:
Originally Posted by Darth Vader View Post
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!
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?
 
1 members found this post helpful.
Old 08-14-2016, 10:36 AM   #9
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: McKinney, Texas
Distribution: Slackware64 15.0
Posts: 3,858

Rep: Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225
In the US, we'd say something like "You are so full of bullshit that your eyes must be brown."
 
1 members found this post helpful.
Old 08-15-2016, 06:51 AM   #10
staus
Member
 
Registered: Apr 2004
Posts: 155

Original Poster
Rep: Reputation: 10
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.
 
Old 08-15-2016, 07:14 AM   #11
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 8,559

Rep: Reputation: 8105Reputation: 8105Reputation: 8105Reputation: 8105Reputation: 8105Reputation: 8105Reputation: 8105Reputation: 8105Reputation: 8105Reputation: 8105Reputation: 8105
Quote:
Originally Posted by staus View Post
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.
 
Old 08-15-2016, 09:14 AM   #12
Bertical
Member
 
Registered: Oct 2008
Location: Kingdom of Mercia
Distribution: Slackware
Posts: 83

Rep: Reputation: 14
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.
 
Old 08-24-2016, 05:18 AM   #13
staus
Member
 
Registered: Apr 2004
Posts: 155

Original Poster
Rep: Reputation: 10
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.
 
1 members found this post helpful.
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Unofficial Slackware 14 release (and install) party... tallship Slackware 6 09-29-2012 08:41 AM
install opensuse release candidate upgrade path to final release newbuyer17 Linux - General 2 06-05-2008 08:23 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 09:27 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration