kernel panic on boot

Teufel · 01-11-2015, 05:40 PM

Well, I see parts of both (Grub and LILO) bootloaders installed.
Do you remember, which one do you installed and configured during installation?
what does

Code:

ls -l /media/boot/grub

shows?

And what is the output of

Code:

cat /media/etc/lilo.conf

command?

Please, wrap the outputs into tags . It helps a lot to read your posts.

xavi_slacky · 01-11-2015, 06:40 PM

Hi Teufel ,

> Well, I see parts of both (Grub and LILO) bootloaders installed.
> Do you remember, which one do you installed and configured during installation?

The last one, LILO.

> what does
> Code:
>
> ls -l /media/boot/grub
>
> shows?
>

Code:

total 32
drwxr-xr-x 2 root root  4096 Jan 10 20:19 fonts/
-rw------- 1 root root  5931 Jan 10 20:23 grub.cfg
-rw-r--r-- 1 root root  1024 Jan 10 20:19 grubenv
drwxr-xr-x 2 root root 12288 Jan 10 20:23 i386-pc/
drwxr-xr-x 2 root root  4096 Jan 10 20:19 locale/

> And what is the output of
> Code:
>
> cat /media/etc/lilo.conf
>
> command?
>

Code:

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
# Append any additional kernel parameters:
append=" vt.default_utf8=0"
boot = /dev/sda

#compact        # faster, but won't work on all systems.

# Boot BMP Image.
# Bitmap in BMP format: 640x480x8
  bitmap = /boot/slack.bmp
# Menu colors (foreground, background, shadow, highlighted
# foreground, highlighted background, highlighted shadow):
  bmp-colors = 255,0,255,0,255,0
# Location of the option table: location x, location y, number of
# columns, lines per column (max 15), "spill" (this is how many
# entries must be in the first column before the next begins to
# be used.  We don't specify it here, as there's just one column.
  bmp-table = 60,6,1,16
# Timer location x, timer location y, foreground color,
# background color, shadow color.
  bmp-timer = 65,27,0,255

# Standard menu.
# Or, you can comment out the bitmap menu above and 
# use a boot message with the standard menu:
#message = /boot/boot_message.txt

# Wait until the timeout to boot (if commented out, boot the
# first entry immediately):
prompt
# Timeout before the first entry boots.
# This is given in tenths of a second, so 600 for every minute:
timeout = 1200
# Override dangerous defaults that rewrite the partition table:
change-rules
  reset
# Normal VGA console
vga = normal
# Ask for video mode at boot (time out to normal in 30s)
#vga = ask
# VESA framebuffer console @ 1024x768x64k
#vga=791
# VESA framebuffer console @ 1024x768x32k
#vga=790
# VESA framebuffer console @ 1024x768x256
#vga=773
# VESA framebuffer console @ 800x600x64k
#vga=788
# VESA framebuffer console @ 800x600x32k
#vga=787
# VESA framebuffer console @ 800x600x256
#vga=771
# VESA framebuffer console @ 640x480x64k
#vga=785
# VESA framebuffer console @ 640x480x32k
#vga=784
# VESA framebuffer console @ 640x480x256
#vga=769
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
  root = /dev/sda2
  label = Linux
  read-only
# Linux bootable partition config ends

>
> Please, wrap the outputs into tags . It helps a lot to read your posts.

OK, now better ?

Thanks, see you.

colorpurple21859 · 01-11-2015, 08:34 PM

mount /dev/sda1 and post what is on it.

Teufel · 01-11-2015, 09:19 PM

What might be there? It's a swap. I doubt ls will show anything on swap partition:

Code:

Device Boot Start End Blocks Id System
/dev/sda1 2048 4196351 2097152 82 Linux swap

@xavi_slacky
Since you are using huge kernel it shouldn't be a kernel module issue (assuming you are using Live media with the same kernel).
And I see that you have both Grub and Lilo installed. It might cause a mess.
Your lilo.conf seems fine, and points to correct partition, so I'd suggest to chroot into your installation from live media and run "lilo" once more. Keep in mind, you have to run "lilo" command on every lilo.conf changes.
Exit chroot, shut down PC (do not forget to detach any usb sticks that attached, they might change drives enumeration order) and try to boot.

Added:
How to chroot:
Boot with your media, open terminal and run as root:

Code:

mount /dev/sda2 /mnt
mount -t proc none /mnt/proc
mount -o bind /dev /mnt/dev
mount -o bind /sys /mnt/sys
chroot /mnt /bin/bash
liloconfig
lilo
exit

When running liloconfig, at this stage:
http://i.imgur.com/paEx2nQ.jpg
select "Skip" option.
And at this stage:
http://i.imgur.com/Y6uB7fg.jpg
select "MBR".
When liloconfig exited (cursor at command line starts to blinking), continue with "lilo" and "exit"

Using this ISO I installed Slackware and booted.

colorpurple21859 · 01-11-2015, 09:23 PM

Misread the partition table was looking for the efi patition and if there is an elilo configuration file and if so what was in it.

Teufel · 01-12-2015, 12:36 AM

.deleted.

xavi_slacky · 01-12-2015, 08:40 AM

> Today, 03:34 AM #18
> colorpurple21859

Hi colorpurple21859 ,

>
> mount /dev/sda1 and post what is on it.

For me, /dev/sda1 is my Linux swap partition.

I try with /dev/sda2 which is my Linux root partition.

Code:

total 180
drwxr-xr-x  2 root root  4096 May 23  2009 bin/
drwxr-xr-x  3 root root  4096 Jan 10 20:40 boot/
drwxr-xr-x 17 root root 69632 Jan 10 06:09 dev/
drwxr-xr-x 97 root root 12288 Jan 10 20:36 etc/
-rw-r--r--  1 root root  3975 Jan 10 19:23 etc.txt
drwxr-xr-x  3 root root  4096 Sep 18  2012 home/
drwxr-xr-x  7 root root  4096 Oct 10  2013 lib/
drwxr-xr-x  2 root root  4096 Jan 10 06:31 lib64/
drwx------  2 root root 16384 Jan 10 06:06 lost+found/
drwxr-xr-x 16 root root  4096 Jan 10 06:09 media/
drwxr-xr-x 10 root root  4096 Sep 26  2006 mnt/
drwxr-xr-x  2 root root  4096 Jun 10  2007 opt/
drwxr-xr-x  2 root root  4096 Oct  6  1997 proc/
drwx--x---  2 root root  4096 Jan 10 20:36 root/
drwxr-xr-x  4 root root  4096 Jan 10 20:23 run/
drwxr-xr-x  2 root root 12288 Dec 18 19:58 sbin/
drwxr-xr-x  2 root root  4096 Jan 10 06:30 srv/
drwxr-xr-x  2 root root  4096 May 12  2004 sys/
drwxrwxrwt  4 root root  4096 Jan 10 20:34 tmp/
drwxr-xr-x 18 root root  4096 Dec 18 19:58 usr/
drwxr-xr-x 17 root root  4096 Dec 18 19:58 var/

Thanks, see you.

---------- Post added 01-12-15 at 03:40 PM ----------

> Today, 04:19 AM #19
> Teufel

Hi Teufel ,

>
> What might be there? It's a swap. I doubt ls will show anything on swap partition:
> Code:
>
> Device Boot Start End Blocks Id System
> /dev/sda1 2048 4196351 2097152 82 Linux swap
>

Yes, correct.

> @xavi_slacky
> Since you are using huge kernel it shouldn't be a kernel module issue (assuming you are using Live media with the same kernel).
> And I see that you have both Grub and Lilo installed. It might cause a mess.
> Your lilo.conf seems fine, and points to correct partition, so I'd suggest to chroot into your installation from live media and run "lilo" once more. Keep in mind, you have to run "lilo" command on every lilo.conf changes.
> Exit chroot, shut down PC (do not forget to detach any usb sticks that attached, they might change drives enumeration order) and try to boot.
>
> Added:
> How to chroot:
> Boot with your media, open terminal and run as root:
> Code:
>
> mount /dev/sda2 /mnt
> mount -t proc none /mnt/proc
> mount -o bind /dev /mnt/dev
> mount -o bind /sys /mnt/sys
> chroot /mnt /bin/bash
> liloconfig
> lilo
> exit
>
> When running liloconfig, at this stage:
> http://i.imgur.com/paEx2nQ.jpg
> select "Skip" option.
> And at this stage:
> http://i.imgur.com/Y6uB7fg.jpg
> select "MBR".
> When liloconfig exited (cursor at command line starts to blinking), continue with "lilo" and "exit"
>

I don't get LILO ncurses menu.

> Using this ISO I installed Slackware and booted.

I following yours step to step but I get same initial issue.

More ideas ?

Thanks, see you.

JackHair · 01-12-2015, 09:05 AM

You could try running pkgtool from the chroot and try to reinstall lilo.

bassmadrigal · 01-12-2015, 09:06 AM

How new is your system? Do you know if it is UEFI or is it BIOS based? If it is UEFI, we'll work on ELILO, if it is BIOS based, we'll work on regular LILO. Knowing this should help us better help you.

Also, did you do a full install of Slackware?

xavi_slacky · 01-12-2015, 10:20 AM

> Today, 04:05 PM #23
> JackHair

Hi JackHair ,

>
> You could try running pkgtool from the chroot and try to reinstall lilo.

I try running pkgtool from chroot but, I don't know install LILO from USB stick installation.
How can I install it from pkgtool on chroot ?

Thanks, see you.

---------- Post added 01-12-15 at 05:21 PM ----------

> Today, 04:06 PM #24
> bassmadrigal

Hi bassmadrigal ,

>
> How new is your system? Do you know if it is UEFI or is it BIOS based? If it is UEFI, we'll work on ELILO, if it is BIOS based, we'll work on regular LILO. Knowing this should help us better help you.
>

Is an X64 bit.

I have UEFI BIOS boot option.

How can I install ELILO ?

> Also, did you do a full install of Slackware?

Yes.

Thanks, see you.

JackHair · 01-12-2015, 10:30 AM

I try running pkgtool from chroot but, I don't know install LILO from USB stick installation.
How can I install it from pkgtool on chroot ?

Thanks, see you.

In pkgtool go to "setup" then in the list find lilo (or elilo if you have an uefi mobo).

bassmadrigal · 01-12-2015, 10:57 AM

If you aren't forcing UEFI right now and are doing a BIOS emulation, it may be easier to just stick with BIOS and using LILO. If you decide to stick with this route, what happens if you do the following (after booting off the Slackware install disc)?

Code:

mount /dev/sda2 /mnt
mount -o bind /dev /mnt/dev
mount -o bind /proc /mnt/proc
mount -o bind /sys /mnt/sys
chroot /mnt
lilo -vt        #this just does a test run of everything to show you any warnings that may crop up post the output of this

[/code]

If the lilo test seems to run fine without any errors (there might be a warning about LBA32, which you can safely ignore), then you can go ahead and run lilo without any arguments. If you're not sure if the output is an error or not, feel free to paste it here and we can let you know.

If this doesn't work, you may already be running in UEFI mode, but if you didn't partition for /boot/efi, then you're going to run into problems. See the README_UEFI.TXT on using UEFI on Slackware.

http://slackbuilds.org/mirror/slackw...EADME_UEFI.TXT

Also, this may be considered nitpicking, but it is much easier to see what you're replying to if you encase it in quote tags (square brackets [word] around the word (replace word with quote) at the start and square brackets around the word with a fordward slash in front of it at the close [/word]). To me, it is a bit jarring to see the > greater than symbol on a forum (since I hardly even see it in email anymore thanks to gmail).

Quote:

To put something in quotes, use

Code:

[quote]Quote tags to make it much easier to read[/quote]

Teufel · 01-12-2015, 11:03 AM

liloconfig doesn't show ncurses menu? Did you really run it from chroot?

You can install Grub instead of LILO, I replaced LILO with Grub using the same Slint ISO. And I created here exactly the same partitions layout: sda1 is swap and sda2 is root (/).
Try this when booted into Slint live system:

Code:

mount /dev/sda2 /mnt
mount -t proc none /mnt/proc
mount -o bind /dev /mnt/dev
mount -o bind /sys /mnt/sys
chroot /mnt /bin/bash
grub-install /dev/sda
grub-mkconfig -o /boot/grub/grub.cfg
exit

Now I have Grub bootloader instead of LILO. Grub menu looks a bit different than LILO, but it doesn't matter.
If you can't install Grub, it might be due to inconsistent Slint ISO.
Anyway, try the code above.

Didier Spaier · 01-12-2015, 11:38 AM

Well xavi_slacky, as you used a Slint installer, I assume that I ought you some support or after sales service

First, please confirm that :

you downloaded the 32-bit image
you checked the integrity of the ISO using the md5sum before writing it on a DVD or USB stick

Then please boot again the installer and once logged in provide the output of following command:

Code:

lsblk -o name,type,model,size,fstype,mountpoint,label,uuid

Then, please indicate how you intend to use each of the partitions listed. Hopefully this will help us to help you.

As others have pointed out, to make the text you copy here easier to read, please place the results of the command inside code tags. In the same vein, when you quote another post, please use the quote tags.

xavi_slacky · 01-12-2015, 02:33 PM

> Today, 05:30 PM #26
> JackHair

Hi JackHair ,

>
> In pkgtool go to "setup" then in the list find lilo (or elilo if you have an uefi mobo).

Which list ?

Thanks, see you.

---------- Post added 01-12-15 at 09:34 PM ----------

> Today, 05:57 PM #27
> bassmadrigal

Hi bassmadrigal ,

>
> If you aren't forcing UEFI right now and are doing a BIOS emulation, it may be easier to just stick with BIOS and using LILO. If you decide to stick with this route, what happens if you do the following (after booting off the Slackware install disc)?
>
> Code:
>
> mount /dev/sda2 /mnt
> mount -o bind /dev /mnt/dev
> mount -o bind /proc /mnt/proc
> mount -o bind /sys /mnt/sys
> chroot /mnt
> lilo -vt #this just does a test run of everything to show you any warnings that may crop up post the output of this
>

Code:

 / [To install, type setup] # mount /dev/sdb2 /mnt/
 / [To install, type setup] # mount -o bind /dev/ /mnt/dev/
 / [To install, type setup] # mount -o bind /proc/ /mnt/proc/
 / [To install, type setup] # mount -o bind /sys/ /mnt/sys/
 / [To install, type setup] # chroot /mnt/
 / [To install, type setup] # pwd
 /
 / [To install, type setup] # ls
   bin   dev  etc.txt  lib    lost+found  mnt  proc  run   srv  tmp  var
   boot  etc  home     lib64  media       opt  root  sbin  sys  usr
 / [To install, type setup] # lilo -vt
   Fatal: Not a number: "t"
 / [To install, type setup] #

Wrong option ?

Thanks, see you.