Slackware - Installation This forum is for the discussion of installation issues with Slackware. |
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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
 |
|
09-27-2017, 12:10 PM
|
#1
|
LQ 5k Club
Registered: Jan 2006
Location: Oldham, Lancs, England
Distribution: Slackware64 15; SlackwareARM-current (aarch64); Debian 12
Posts: 8,311
Rep: 
|
kernel panic!
Got a refurbished Dell T3600, wiped Windows 10, bunged in my Slackware64 14.2 DVD, booted up, loading kernel...then disaster! Couldn't take a photo, camera battery flat, but the error ended with:
Code:
Kernel Panic - not syncing:Attempted to kill int!
exit code=0x00000009
Tried Slackware Live, loaded & ran OK, wouldn't install.
Tried Mint 18.2, installed and running - no problem.
Googled but with no luck.
What's the difference between the Slackware and Mint installers?
REALLY want Slack on this beast!!!
Edit: more details:
Legacy BIOS
Xeon E5-1650, 16 GB RAM
Last edited by brianL; 09-27-2017 at 12:17 PM.
|
|
|
09-27-2017, 12:31 PM
|
#2
|
LQ Veteran
Registered: Jan 2008
Location: florida panhandle
Distribution: Slackware Debian, Fedora, others
Posts: 7,780
|
Quote:
Tried Slackware Live, loaded & ran OK, wouldn't install.
|
Which slackware live did you try? The Xfce live doesn't have option to install to hard drive, all others do.
|
|
|
09-27-2017, 12:34 PM
|
#3
|
LQ 5k Club
Registered: Jan 2006
Location: Oldham, Lancs, England
Distribution: Slackware64 15; SlackwareARM-current (aarch64); Debian 12
Posts: 8,311
Original Poster
Rep: 
|
The full version, which is more or less a duplicate of the install DVD (slackware-live-current.iso).
Another edit:
It got to the same stage of booting as the install DVD, loading kernel, then froze with the same error message.
Last edited by brianL; 09-27-2017 at 12:40 PM.
|
|
|
09-27-2017, 12:54 PM
|
#4
|
Member
Registered: Jan 2017
Location: Fremont, CA, USA
Distribution: Trying any&ALL on old/minimal
Posts: 997
|
Can you see 1st fcn name after " Call Trace:"? Or EIP: somefcn+...
Might there be a msg like can't mount root just before?
(PM'ed you about sundialsvcs " sticky" fyi in case you hadn't seen it)
VeryWildGuess: GPU model? Try kernel boot parms like noapic nomodeset ...
Not totally the distro, just their chosen kernel&driver config. Try ?other.s?
I think the 00009 (vs 00b etc) is tellng us something, but Idk....
Last edited by !!!; 09-27-2017 at 01:57 PM.
|
|
|
09-27-2017, 01:08 PM
|
#5
|
LQ 5k Club
Registered: Jan 2006
Location: Oldham, Lancs, England
Distribution: Slackware64 15; SlackwareARM-current (aarch64); Debian 12
Posts: 8,311
Original Poster
Rep: 
|
Quote:
Originally Posted by !!!
Can you see 1st fcn name after " Call Trace:"?
Might there be a msg like can't mount root just before?
(PM'ed you about sundialsvcs " sticky" fyi in case you hadn't seen it)
|
Have to get my camera battery charged, then take a photo. There were some details after Call trace, but can't remember what they all said.
Yeah, I read sundialsvc's thread. Helpful, but not in this case.
|
|
|
09-27-2017, 01:23 PM
|
#6
|
Member
Registered: Jan 2017
Location: Fremont, CA, USA
Distribution: Trying any&ALL on old/minimal
Posts: 997
|
Just need a couple words (maybe not whole pic),
like: fooLPfcn after sysD_not_found msg 
And the 'good stuff' may have scrolled off
(anyone know how to catch it???
Not relevant cuz cpu halted, but is this 2.0kernel tldp the latest??)
(I edited in a bit more junk into my post, while you were replying, sorry)
Last edited by !!!; 09-27-2017 at 07:39 PM.
|
|
|
09-27-2017, 02:28 PM
|
#7
|
LQ 5k Club
Registered: Jan 2006
Location: Oldham, Lancs, England
Distribution: Slackware64 15; SlackwareARM-current (aarch64); Debian 12
Posts: 8,311
Original Poster
Rep: 
|
Here's a photo:
|
|
|
09-27-2017, 02:37 PM
|
#8
|
LQ 5k Club
Registered: Jan 2006
Location: Oldham, Lancs, England
Distribution: Slackware64 15; SlackwareARM-current (aarch64); Debian 12
Posts: 8,311
Original Poster
Rep: 
|
What puzzles me is why would Mint install and run perfectly, but not Slackware? I looked through all the options in the BIOS setup menus, to see if anything was interfering. Not used to having problems with Slackware. 
|
|
|
09-27-2017, 07:35 PM
|
#9
|
Member
Registered: Jan 2017
Location: Fremont, CA, USA
Distribution: Trying any&ALL on old/minimal
Posts: 997
|
Try retain_initrd
|
|
|
09-28-2017, 05:40 AM
|
#10
|
LQ 5k Club
Registered: Jan 2006
Location: Oldham, Lancs, England
Distribution: Slackware64 15; SlackwareARM-current (aarch64); Debian 12
Posts: 8,311
Original Poster
Rep: 
|
Quote:
Originally Posted by !!!
Try retain_initrd
|
Would that be at the boot options prompt?
Actually made a bit of progress. Did another websearch on "exit code=0x00000009", found a Ubuntu user who'd solved it by reverting to an older kernel. So I tried Slackware64 14.0, and it installed OK, lilo in the root partition (/dev/sda3). Websearched for chainloading lilo from grub2, found something that didn't work, so just ran update-grub. Slack was added to the menu. Rebooted into Slackware. Things seemed OK, then it froze when it reached this:
|
|
|
09-28-2017, 09:33 AM
|
#11
|
LQ Guru
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 8,792
|
It might just be an issue with the kernel in 14.2. Have you tried the -current ISO to see if that boots fine? If so, you should be able to boot off that ISO and then point the installer to 14.2 packages. You could either try the patched kernel for 14.2 or just install the kernel from -current (or an even newer one from 55020's dusk project... he has 4.12 available).
|
|
|
09-28-2017, 10:49 AM
|
#12
|
LQ 5k Club
Registered: Jan 2006
Location: Oldham, Lancs, England
Distribution: Slackware64 15; SlackwareARM-current (aarch64); Debian 12
Posts: 8,311
Original Poster
Rep: 
|
Yeah, I've tried -current, same results as 14.2. And it can't be just a matter of older vs newer kernels, because Mint is OK using:
Code:
brian@mintdesk ~ $ uname -r
4.10.0-35-generic
|
|
|
09-28-2017, 12:36 PM
|
#13
|
LQ Guru
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 8,792
|
Quote:
Originally Posted by brianL
Yeah, I've tried -current, same results as 14.2. And it can't be just a matter of older vs newer kernels, because Mint is OK using:
Code:
brian@mintdesk ~ $ uname -r
4.10.0-35-generic
|
It could still be kernel related. Mint is using 4.10, which neither 14.2 (4.4) or -current (4.9) are using. Plus, as far as I know, they are not vanilla kernels, and they've patched them beyond what you can download at kernel.org. It could also be something with how Pat compiled the Slackware kernel, maybe some option or module is causing the problem.
Can you try with the 14.1 kernel? That is 3.10 based and if you can boot off that for the installer, you should be able to install 14.2 using a local copy (or from another USB drive or CD/DVD disk). Then you could either install the 14.1 kernel, replacing 14.2's or try 55020's 4.12 kernel. It might even work with 14.0's kernel, but I don't know if any of these programs will break with such an old kernel.
|
|
|
09-28-2017, 12:40 PM
|
#14
|
LQ 5k Club
Registered: Jan 2006
Location: Oldham, Lancs, England
Distribution: Slackware64 15; SlackwareARM-current (aarch64); Debian 12
Posts: 8,311
Original Poster
Rep: 
|
I tried with 14.0, with the results mentioned in post #10. It installed OK, then froze part way through first boot.
|
|
|
09-28-2017, 01:30 PM
|
#15
|
LQ Sage
Registered: Nov 2004
Location: Saint Amant, Acadiana
Distribution: Gentoo ~amd64
Posts: 7,675
Rep: 
|
Time for custom kernel, methinks.
|
|
|
All times are GMT -5. The time now is 02:02 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|