SlackwareThis Forum is for the discussion of Slackware Linux.
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.
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.
I installed Slackware 9.1 from scratch. Everything was fine without any error during the installation
process.
Each time the PC starts, lilo boots, it seems ok.
But it will stop half way and prompted Kernel panic. No init found.
Below was the error message from the screen:
Freeing unused kernel memory, 116k freed.
Warning:unable to open an console.
Kernel panic. No init found. Try passing init=option to kernel.
Can any Slack guru please help me. urgent!
Thank you.
I make 3 partition ie, / (hda4), /boot(hda3), /swap(hda6)
My fdisk -l showed this:
Disk /dev/hda: 30.7 GB, 30750031872 bytes
255 heads, 63 sectors/track, 3738 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hda1 1 1305 10482381 7 HPFS/NTFS
/dev/hda2 1306 2626 10610932+ f W95 Ext'd (LBA)
/dev/hda3 * 2627 2657 249007+ 83 Linux
/dev/hda4 2658 3738 8683132+ 83 Linux
/dev/hda5 1306 2610 10482381 b W95 FAT32
/dev/hda6 2611 2626 128488+ 82 Linux swap
I installed lilo to the superbloack.
The content of my lilo.conf is :
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/hda
#compact # faster, but won't work on all systems.
prompt
timeout = 300
# Normal VGA console
vga = normal
# 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
# ramdisk = 0 # paranoia setting
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/hda3
label = Slack
read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Linux bootable partition config ends
# DOS bootable partition config begins
other = /dev/hda1
label = Windows2000
table = /dev/hda
# DOS bootable partition config ends
You have over 40 posts and should know our rules by now. Please do not post the same thread in more than one forum. Picking the most relevant forum and posting it once there makes it easier for other members to help you and keeps the discussion all in one place.
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/hda3 <----- should be root=/dev/hda4
label = Slack
read-only # Non-UMSDOS filesystems should be mounted read-only for checking
root = /dev/hda3 <----- should be root=/dev/hda4 in lilo.conf
I've always thought that you wanted / /boot and /bin on the same partition to prevent problems. Or is this no longer the case since Slack 9 puts vmlinux in /noot instead of / ?
Please do not post replies to threads in which we have warned users that they have double posted. Its already been reported to be closed 100% of the time once a moderator of that forum gets to it.
Thanks.
He posted this also in the Slackware Installation forum.
As tricky has mentioned this thread is going to be closed as it's a double post. Any/all discussion should be continued on the 'other' thread on this subject.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.