Kernel Panic After Fresh Install

Kk2 · 12-19-2018, 05:53 PM

Hi guys, i have tried everything you could imagine, tried to boot the huge, the generic to add rootdelay, changed elilo to lilo, from lilo to grub

but its seems like slackware doesnt like me at all, every other distro i tried works just the one i want most doenst haha..

here is a screenshot of the kernel panic screen:

https://i.imgur.com/nHI4hfR.jpg

btw, i tried with slackware64 14.2 and current

and also i had problems with not UEFI boot during install that slack iso doens't recorgnize my keyboard (CORSAIR STRAGE RGB) i know there is a module for this in kernel corsair specific but in generic should be enable by default right?

Thanks anyway, and if i dont find any solution goodbye slack

Setup:

Quote:

Intel Core I5-6600 Skylake
MSI GeForce GTX970
ASUS mATX H110M-CS/BR
8GB DDR4
SSD 128GB
HD 1TB

Partition Table

Quote:

/dev/sda1 / ext4 noatime 0 1
/dev/sdb1 none swap sw 0 0
/dev/sdb2 /home/kk2/Work xfs defaults 0 2

BW-userx · 12-19-2018, 06:17 PM

what is your set up, IE, Partiton Table, BIOS setup to match it, ie uefi va MBR, if it is a GPT Partition Table cannot boot MBR install because the install will see it as a UEFI and should (try) to install as such, but if you do not have your HDD setup with that boot partition and marked for UEFI and BIOS is not set up properly either, then anyone will have issues, and visa versa.

Everything has to match up between the partition table being used with the BIOS set up to boot same type of set up.

I have my UEFI turned off in BIOS and an MBR partition table on my HDD, and have no issues with slack install along with 3 to 4 other distros, plus windows in a grub boot setup.

Kk2 · 12-19-2018, 07:30 PM

my Setup is a
<- Intel i5 6660k ->
<- 8gb ddr4 ->
<- GPU: nvidia Geforce gtx970 ->
<- Asus Motherboard ->
<- SSD 120gb ->
<- HD 1TB ->

Quote:

/dev/sda1 / ext4 noatime 0 1
/dev/sdb1 none swap sw 0 0
/dev/sdb2 /home/kk2/Work xfs defaults 0 2

I have deactivated UEFI from my BIOS so its pretty much a BIOS setup only now

bassmadrigal · 12-20-2018, 05:12 PM

Please don't open up multiple threads on a topic. I've requested the moderators to close your other thread.

As to your issue, with your screenshot, it shows it craps out at the 66 second mark. Does the system freeze at the beginning and then it finally panics and dumps that info or does the boot process move along initially and eventually panics?

And is the error the same regardless of whether you use huge or generic? And how are you making that change? Are you familiar enough with lilo to make the proper edits and write the changes to the bootloader? (I don't mean this to be condescending... just trying to cover all bases.)

Have you tried Alien Bob's Slackware Live?

https://docs.slackware.com/slackware:liveslak

Right now, we just don't have a whole lot to go on to try and solve this. (Or maybe I just don't have enough to go on since I don't see any helpful hints with your screenshot.)

Kk2 · 12-20-2018, 05:33 PM

so, yes i have tried the liveslack and i was able to boot there,

im getting the kernel panic in huge and generic i mostly edited on grub the configs on boot time like to add the rootdelay on fly and everything

how shall i proceed? anyway to improve the initial screen size of the terminal so i can fetch the hole kernel error? not just that final part?

BW-userx · 12-20-2018, 06:03 PM

if you are playing around with your grub conf then you have to had already had a fully operational Install of Slackware, because it installs lilo by default, and grub has to be installed manually after one has booted into it after installing it.

mount it get your grub.conf and post it, so everyone can see what you're doing to it to cause you to crash and burn.

Kk2 · 12-20-2018, 06:12 PM

i installed grub after install without exiting, just went terminal and did it,

grub-install /dev/sda
grub-mkconfig -o /boot/grub/grub.cfg

BW-userx · 12-20-2018, 06:18 PM

exacly ,, meaning it was working, until you started playing around with your conf .. so logic states, the problem is operator error. So please mount your system, get your grub.conf and whatever else you might have been modifiying and post it. So someone can help you with getting it right.

or
did you install that from a live USB boot install? can you even do that?

Kk2 · 12-20-2018, 06:23 PM

sure bro, calm down :'(

Quote:

menuentry 'Slackware 14.2 x86_64 (post 14.2 -current) (em /dev/sdc1)' --class slackware --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-simple-2d804e78-d734-43fb-8e58-666ab7a7e06f' {
insmod part_msdos
insmod ext2
set root='hd2,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd2,msdos1 --hint-efi=hd2,msdos1 --hint-baremetal=ahci2,msdos1 2d804e78-d734-43fb-8e58-666ab7a7e06f
else
search --no-floppy --fs-uuid --set=root 2d804e78-d734-43fb-8e58-666ab7a7e06f
fi
linux /boot/vmlinuz-generic-4.19.11 root=/dev/sdc1
}
submenu 'Opções avançadas para Slackware 14.2 x86_64 (post 14.2 -current) (em /dev/sdc1)' $menuentry_id_option 'osprober-gnulinux-advanced-2d804e78-d734-43fb-8e58-666ab7a7e06f' {
menuentry 'Slackware 14.2 x86_64 (post 14.2 -current) (em /dev/sdc1)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-generic-4.19.11--2d804e78-d734-43fb-8e58-666ab7a7e06f' {
insmod part_msdos
insmod ext2
set root='hd2,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd2,msdos1 --hint-efi=hd2,msdos1 --hint-baremetal=ahci2,msdos1 2d804e78-d734-43fb-8e58-666ab7a7e06f
else
search --no-floppy --fs-uuid --set=root 2d804e78-d734-43fb-8e58-666ab7a7e06f
fi
linux /boot/vmlinuz-generic-4.19.11 root=/dev/sdc1
}
menuentry 'Slackware 14.2 x86_64 (post 14.2 -current) (em /dev/sdc1)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-huge-4.19.11--2d804e78-d734-43fb-8e58-666ab7a7e06f' {
insmod part_msdos
insmod ext2
set root='hd2,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd2,msdos1 --hint-efi=hd2,msdos1 --hint-baremetal=ahci2,msdos1 2d804e78-d734-43fb-8e58-666ab7a7e06f
else
search --no-floppy --fs-uuid --set=root 2d804e78-d734-43fb-8e58-666ab7a7e06f
fi
linux /boot/vmlinuz-huge-4.19.11 root=/dev/sdc1
}
}

BLKID

Quote:

/dev/sda1: UUID="deca6a96-8dd5-40a2-ae51-8be821cc0370" TYPE="ext4" PARTUUID="f87cf6a3-01"
/dev/sdb1: UUID="2c1ba65a-4c2f-45f3-a95a-4b5a7ab234d7" TYPE="swap" PARTUUID="0fda0503-01"
/dev/sdb2: LABEL="home" UUID="8f12bd80-3014-4caf-8b24-1bac1f79cc47" TYPE="xfs" PARTUUID="0fda0503-02"
/dev/sdc1: UUID="2d804e78-d734-43fb-8e58-666ab7a7e06f" TYPE="ext4" PARTUUID="3f39b179-01"
/dev/sdc2: UUID="910aa582-ea8f-4757-bac9-b6e9af5ddba5" TYPE="swap" PARTUUID="3f39b179-02"
/dev/sdd1: UUID="2018-12-20-06-13-20-00" LABEL="Slackware-current DVD" TYPE="iso9660" PTUUID="317e3617" PTTYPE="dos" PARTUUID="317e3617-01"
/dev/sdd2: SEC_TYPE="msdos" UUID="FF13-78CF" TYPE="vfat" PARTUUID="317e3617-02"

BW-userx · 12-20-2018, 06:43 PM

I'm not upset, I am just pointing out that logic states it is the operator and not Slackware fault it crashed.

I was actully refereing to your default grub config. as that one looks ok ,and should be

Code:


#
# Configuration file for GRUB.
#
GRUB_DEFAULT=0
#GRUB_HIDDEN_TIMEOUT=0
#GRUB_HIDDEN_TIMEOUT_QUIET=false
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR="Void"
GRUB_CMDLINE_LINUX_DEFAULT="loglevel=4 slub_debug=P page_poison=1"
# Uncomment to use basic console
#GRUB_TERMINAL_INPUT="console"
# Uncomment to disable graphical terminal
#GRUB_TERMINAL_OUTPUT=console
#GRUB_BACKGROUND=/usr/share/void-artwork/splash.png
#GRUB_GFXMODE=1920x1080x32
#GRUB_DISABLE_LINUX_UUID=true
#GRUB_DISABLE_RECOVERY=true
# Uncomment and set to the desired menu colors.  Used by normal and wallpaper
# modes only.  Entries specified as foreground/background.
#GRUB_COLOR_NORMAL="light-blue/black"
#GRUB_COLOR_HIGHLIGHT="light-cyan/blue"

that is not slacks grub config but it is simular this is where you want to put your customizations for your grub display, time outs, and images up on the screen etc.. it is in

Code:

/etc/default
grub is the file name

did you mess with that one?

Kk2 · 12-20-2018, 07:18 PM

Here is it my /etc/default/grub

Quote:

# Copyright 1999-2015 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
#
# To populate all changes in this file you need to regenerate your
# grub configuration file afterwards:
# 'grub2-mkconfig -o /boot/grub/grub.cfg'
#
# See the grub info page for documentation on possible variables and
# their associated values.

GRUB_DISTRIBUTOR="Gentoo"

# Default menu entry
#GRUB_DEFAULT=0

# Boot the default entry this many seconds after the menu is displayed
#GRUB_TIMEOUT=5
#GRUB_TIMEOUT_STYLE=menu

# Append parameters to the linux kernel command line
#GRUB_CMDLINE_LINUX=""
#
# Examples:
#
# Boot with network interface renaming disabled
# GRUB_CMDLINE_LINUX="net.ifnames=0"
#
# Boot with systemd instead of sysvinit (openrc)
# GRUB_CMDLINE_LINUX="init=/usr/lib/systemd/systemd"

# Append parameters to the linux kernel command line for non-recovery entries
#GRUB_CMDLINE_LINUX_DEFAULT=""

# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL=console

# The resolution used on graphical terminal.
# Note that you can use only modes which your graphic card supports via VBE.
# You can see them in real GRUB with the command `vbeinfo'.
#GRUB_GFXMODE=640x480

# Set to 'text' to force the Linux kernel to boot in normal text
# mode, 'keep' to preserve the graphics mode set using
# 'GRUB_GFXMODE', 'WIDTHxHEIGHT'['xDEPTH'] to set a particular
# graphics mode, or a sequence of these separated by commas or
# semicolons to try several modes in sequence.
#GRUB_GFXPAYLOAD_LINUX=

# Path to theme spec txt file.
# The starfield is by default provided with use truetype.
# NOTE: when enabling custom theme, ensure you have required font/etc.
#GRUB_THEME="/boot/grub/themes/starfield/theme.txt"

# Background image used on graphical terminal.
# Can be in various bitmap formats.
#GRUB_BACKGROUND="/boot/grub/mybackground.png"

# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to kernel
#GRUB_DISABLE_LINUX_UUID=true

# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY=true

# Uncomment to disable generation of the submenu and put all choices on
# the top-level menu.
# Besides the visual affect of no sub menu, this makes navigation of the
# menu easier for a user who can't see the screen.
#GRUB_DISABLE_SUBMENU=y

# Uncomment to play a tone when the main menu is displayed.
# This is useful, for example, to allow users who can't see the screen
# to know when they can make a choice on the menu.
#GRUB_INIT_TUNE="60 800 1"

bassmadrigal · 12-20-2018, 07:52 PM

Quote:

Originally Posted by BW-userx

I'm not upset, I am just pointing out that logic states it is the operator and not Slackware fault it crashed.

He said that he installed grub before he rebooted out of the installer. He didn't have a successful boot after installation.

@OP, unfortunately, I'm not familiar grub. So, I'm not sure if that's where your issue lies.

Another option could be to try installing Slackware Live using setup2hd script included on the live media to see if this is an issue with the Slackware installer or something else.

BW-userx · 12-20-2018, 08:03 PM

Quote:

Originally Posted by bassmadrigal

He said that he installed grub before he rebooted out of the installer. He didn't have a successful boot after installation.

@OP, unfortunately, I'm not familiar grub. So, I'm not sure if that's where your issue lies.

Another option could be to try installing Slackware Live using setup2hd script included on the live media to see if this is an issue with the Slackware installer or something else.

that's why I modded, and asked if he installed with live, nor do I think one can even install slack using live, but I'm not sure about that one, and I've never thought of such a thing using the dvd burn to USB stick, to ? switch ttys and run install grub, then reboot.

I play it safe, install, if he has a different linux boot loader, then do not install lilo,

skip it, boot using that grubs main Linux that controls grub, then update it and let it pick up slack, or if not then install lilo, boot into slack do post install, install grub, update it, then I've never had an issue.

I haven't been able to post until now, I am just back in a fresh install of a system, and doing post setting up.

and I am not an experiet either, but the files looked ok to me. makes me wonder exactly how he installed grub.

he might OP might want to reinstall, and just install lilo and let it boot slack, then in slack install grub, and do what else you need to do.

save yourelf some time, instead of bouncing back in here and keep looking for an answer to how to fix it like it is. It has been how many days now? something to think about.

bassmadrigal · 12-20-2018, 08:07 PM

Quote:

Originally Posted by BW-userx

that's why I modded, and asked if he installed with live, nor do I think one can even install slack using live, but I'm not sure about that one, and I've never thought of such a thing using the dvd burn to USB stick, to ? switch ttys and run install grub, then reboot.

I play it safe, install, if he has a different linux boot loader, then do not install lilo, skip it, if not then install lilo, boot into slack do post install, install grub, update it, then I've never had an issue.

You stated it was an operator error, when he never had a successful boot. You don't have enough information to know if it was something he's done or some incompatibility with his hardware and Slackware. Once you finish the install, you can either type reboot, or you can start doing some basic tweaking of things within the system mounted to /mnt/ by running chroot. I will change my lilo.conf, add a user, and a few other minor things before I ever do my first boot up of Slackware.

And yes, you can install using Slackware Live, but only once you're fully booted into the distro and you then run setup2hd through a command prompt as root.

colorpurple21859 · 12-20-2018, 08:16 PM

Quote:

im getting the kernel panic in huge and generic

the generic kernel won't work unless you have created an initrd.gz with the mkinitrd command, see the mkinitd.README in /boot. Running /usr/share/mkinitrd/mkinitrd_command_generator show what modules are needed for your system .Sometimes booting the huge kernel and loading the initrd.gz at boot will also cause kernel panics.