SlackwareThis Forum is for the discussion of Slackware Linux.
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.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Yesterday I went and updated my 2.6.7 kernel to 2.6.10 (using pkgs from 10.1). I started my system with 10.0 and updated occasionally using swaret, but I haven't been able to run swaret since about xmas. I've done probably 15 recompiles by now, but what I still get is approximately:
Kernel Panic - Not Syncing : VFS : Cannot mount root on unknown-device(3,2)
The partition is /dev/hda2, I've tried booting using root=/dev/hda2, I enabled VFS (despite the config's warning that it's obsolete), I have reiserfs, ext3, and ext2 all built into the kernel, and I've completely reconfigured the kernel, and it still gives me the error. lilo.conf is fine, fstab is fine, and other kernels (two backup 6.7s and an old 4.26, minus the mouse for the 6.7s) boot just fine.
I've also done some searching on the forum, and I found one similar problem, but no answer to it.
I'm having this exact same issue. I was succesfully running 2.6.7 in 10.0 then upgraded my system to 10.1 and it booted up fine using 2.4.29. Then I did the upgrade procedure for 2.6.10 as I need udev, and I get the kernel panic when booting with it. I'm using all tgz files from the CDs. I have no idea what to do now. Any suggestions?
OK, luv2hike, are you using udev? Because if you are, then you'll need to setup coldplug for bootup.
I use a Gentoo system, which has all the packages that I need and step-by-step howto for configuring udev (see this guide for details on how I did it with Gentoo). Udev depends on hotplug, which is the software that gets alerted when there is a harware change. Hotplug calls udev, which then performs it's thing (usually making a device in /dev). However, coldplug is kind of the same as hotplug, only it's for system startup. It could be that you need to investigate further into how to get coldplug working on your system.
Again, I'd be more specific on what to do, but I only know the Gentoo way, which is to read the howto. I hope this points you in the right direction.
I did use my 6.7 config first, and when that didn't work I made a new config as well. The generic kernel didn't work either. I was suggested by a friend to try hda=remap in the boot options, but that didn't work either.
I had also noticed at the end of "make" that it says "root device : (3,2)" or so.
I had the same problem. When I first installed Slackware 10.1 I formated my root partition with reiserFS than I upgraded my kernel from 2.4.29 to 2.6.10 and had that same problem you have. I then had to reinstall the slackware 10.1 and I chose to format my root partition using the ext2 than I upgraded my kernel to the 2.6.10 and I had no problem. And I even downloaded and installed the kernel-2.6.11-rc4 from kernel.org and got it running fine. I just cant get the Nvidia driver to install yet on the 2.6.11-rc4 kernel. The kernel 2.6.10 and kernel 2.6.11-rc4 dont work if you formated your root partition using reiserFS when you install slackware 10.1.
Thanks for the tip on coldplug and the info on reiserfs. I'm not doing a clean install of 10.1 but am upgrading a 10.0 system and the root is already formatted to reiserfs. I don't want to change this as I like the journaling feature and I have too many apps installed and configured to blow it all away. I find it odd that the "recommended" file system would not be supported by the latest kernel for the root partition. It worked with the 2.6.7 kernel in 10.0. I'll see if I can find info on the coldboot idea.
I got past the issue and successfully booted to runlevel 3's login prompt with 2.6.10. I deduced it was that reiserfs was built as a module and it needed it as the / partition was reiser. I did the mkinitrd but that did not help as it has in the past. So I rebuilt the kernel from source, compiling ext2, ext3, and reiserfs directly into the kernel, so no initrd needed now in lilo.conf. It booted up fine after doing this. Maybe prebuilt binaries should have these 3 "main" filesystems compiled in by default as it doesn't hurt anything and these are the recommened Slack partition types?