Slackware-14 32-bit installed successfully. Kernel panic upon booting :(
1 Attachment(s)
Hi,
Wanting to try Slackware for a loong time now. Cut my teeth with a Slackware derivative (Salix OS 14 KDE and XFCE) over the weekend. The install (exactly the same Slackware CUI installer) was a breeze. I use GRUB and a debian sid as my bootloader/bootload maintainer. Both distros played extremely well with my hardware specs. So, I got bold, and created a live USB out of my DVD ISO and installed Slackware 14.0 32 bit. The ISO itself was downloaded sometime in April 2013 from LQ itself. I used Rufus 1.3.4 (comes with Portable Apps platform) in Windows 7 for creating the Live USB. The install went okay, and GRUB update recognised Slackware 14 on my partition. I boot into it, and I get a "Kernel Panic" message. I am attaching the screenshot here, as well as a separate attachment with this post (see below). I am not new to Linux itself (use Debian distros before) but absolutely new to Slackware and the Slackware way of doing things, and so, I might be needing hand-holding in terms of debugging. Many thanks in advance for your help and comments. Best, Surio. |
Just wanted to add, I used Rufus 1.3.4 (comes with Portable Apps platform) in Windows 7 for creating the Live USB.
|
"No filesystem could mount root" usually indicates that there is either a problem with your /etc/fstab or no support for the filesystem used for / (root). The latter can happen if this file system (ext4 is the default in Slackware) is neither built in the kernel, nor provided in the initrd.
Assuming you didn't change the default filesystem and installed the "huge" kernel, which have ext4 built-in (could you confirm both assumptions?), it could be a problem with grub. Unfortunately I can't help you much there as I use lilo (the default in Slackware). Anyhow please provide a little more information, as your hard disk layout (which partitions are used for what, with which file systems and which is bootable if any) and your /etc/fstab, and last but not least your grub config file. Also, do you intend to install only Slackware or is it a multi-boot? In the latter case please indicate which system is expected to use each partition. |
I typed a huge reply, and my browser crashed, and now it is all gone. Frustrating!
Hi Didier, Thank you for replying. The system is a "family owned/family operated" laptop. It has Windows 7 home premium 64 bits installed. As of now, I have around 25 EXT4 partitions of approximately 10 GB for installing different distros and playing with it. I have roughly 10 or so distros on the HDD as of now. For sure, I intend for it to remain multi-boot. Here is my fdisk -l output: Code:
Code:
/dev/sda5 swap swap defaults 0 0 GRUB is the last of my worries. I am typing this from a MATE Salix 13.37 session, which I am upgrading based on the Salix wiki as we speak. The kernel is 2.6.xx and doesn't support my broadcom wifi hardware. OTOH, the Salix 14 KDE/XFCE worked "out of the box" and detected all my hardware. Anyway, here is my generate grub.cfg for you or the others to look into. |
Quote:
Quote:
Code:
mkdir /myslack |
Quote:
/etc/fstab is as I shared above. Here it is Code:
/dev/sda5 swap swap defaults 0 0 Code:
bash-4.2# ls -l /boot Code:
Linux surio-pc 3.2.29-smp #2 SMP Mon Sep 17 13:16:43 CDT 2012 i686 A few bizarre things that I noticed...
Bye for now. Thanks, Surio. |
Quote:
|
Didier,
Thank you, all of this worked, and I can log into both XFCE and KDE sessions. I had omitted ":" from the ending of "id:4:initdefault" initially and got prompted at boot for run level. I realised it with "aha!" later on, and edited the inittab file by accessing slackware partition from debian (as I was on that session at that time). Soon afterwards, when I tried logging into slackware some time later, I had another bout of "kernel panic"(!) but I recreated the GRUB menu and that fixed this problem once again. Small addendum: Is there a GUI based package manager for selecting from software repos? Right now I installed and use the slackpkg CLI tool. |
Quote:
|
Didier,
Thanks again for helping me solve this problem. I hope I have seen the last of the "kernel panic" error, which somehow miraculously disappeared on its own, as quickly as it appeared. :D |
All times are GMT -5. The time now is 11:09 AM. |