LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 04-20-2004, 01:11 PM   #1
mus335
LQ Newbie
 
Registered: Apr 2004
Distribution: Slackware, Debian Sid/Sarge
Posts: 7

Rep: Reputation: 0
Question 2.6.* kernel not booting slack VFS: and INIT: fails


I am having a problem getting my newly compiled 2.6.* series kernels
to boot in slackware 9.1.

slack is working well with default kernel 2.4.20, so i know the filesystem, etc.
is fine, i can always select default (2.4.20) at lilo prompt and boot ok.

I have compiled 2.6.5 - several times, with same result. ( I thought it may be
something i left out, .. i no longer feel this way, otherwise i wouldn't be
posting .
(I have sucessfully compiled quite a few kernels before, this is not first time)
I have compiled 2.4.* series kernel on slack.
but have not sucessfully compiled 2.6.* on slackware 9.1 yet.

general steps for review.
-----------------------------------------------
get source from kernel.org
wget kernel.org/pub/linux/kernel/v2.6/linux-2.6.5.tar.bz2
tar xjvf kernel-2.6.5.tar.bz2
ls -s linux-2.6.5 linux
cd linux
apply specific patches.
make mrproper
make clean
make menuconfig
make && make modules && make modules_install
cp arch/i386/boot/bzImage /boot/kernel-2.6.5
mv /boot/System.map /boot/System.map-old
cp System.map /boot/System.map
ln -s /boot/kernel-2.6.5 /Linux-2.6.5
ln -s /boot/System.map /System.map

vi /etc/lilo.conf - add new kernel
boot=/dev/hda
root=/dev/hda2
message=/boot/bootmess.txt
prompt
timeout=150
delay=10
map=/System.map
vga=771
default=Linux-2.4.20

image=/vmlinuz-2.4.20
label=Linux-2.4.20
read-only

image=/Linux-2.6.5
label=Linux-2.6.5
read-only

/sbin/lilo
added
Linux-2.4.20*
Linux-2.6.5

cat /etc/fstab
####
# I am including this so you know, but this is not in fstab,
# does not get mounted, I thought this was part of the problem,
# like if i add a new kernel, i'm putting in on '/boot' which is actually
# on dev/hda2 because the real '/boot' is not mounted, however
# the system seems to know where real boot is, if i do a make install
# with the kernel the image get's moved to /dev/hda1 '/boot' properly.
###/dev/hda1 /boot ext2 defaults 0 0

/dev/hda2 / reiserfs defaults 1 1
/dev/hda5 /usr reiserfs defaults 1 2
/dev/hda6 /var reiserfs defaults 1 2
/dev/hda7 /home reiserfs defaults 1 2
/dev/hda8 /tmp reiserfs defaults 1 2
/dev/cdrom /mnt/cdrom iso9660 noauto,user,ro 0 0
/dev/fd0 /mnt/floppy auto noauto,owner 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
proc /proc proc defaults 0 0

all standard.

yes, kernel compiled with ext2 ext3 reiserfs ide, support (not as modules) etc.

problem occurs with booting new kernel.
dies with INIT: kernel panic no init found (try passing init= to kernel)

(I have tried passing init=/sbin/init, init=/bin/bash, root=/dev/hda2,
( even, root=/dev/hda1, for 'kicks')
to no-avail, I think the real problem lies in the fact that the kernel
sees root as ext2,... why(?!)

a few lines before that the informative line is:
VFS: mounting root ( ext2 filesystem ) ro

this is wrong, root is a reiserfs filesystem '/boot' is ext2.
( the default kernel sees this correctly ( VFS: mounting root (resierfs filesystem) ro )

I have been to google and back, I suppose i am missing something but i can't
seem to figure out what.

slackware has no mkinitrd, to create a initrd.img,

I have made sure my core tools are up to date for 2.6.*, i believe
i got them all. gcc, make, binutils, etc.
gcc version 3.2.2
GNU Make 3.80
GNU ld version 2.13.90.0.18 20030121
etc,...

thank you for all you help.
also is there a decent slackware post group somewhere, i haven't
fond one.

-cmus
 
Old 04-20-2004, 01:21 PM   #2
Duffy
Member
 
Registered: Aug 2003
Posts: 54

Rep: Reputation: 15
This guide works for me

Quote:
2. Go into the directory you downloaded it to and type the following:

mv linux-2.6.0.tar.gz /usr/src
cd /usr/src
tar -zxvf linux-2.6.0.tar.gz
ln -s /usr/src/linux-2.6.0 /usr/src/linux

This moves the downloaded kernel source file into /usr/src, extracts it and updates the 'linux' link to point to the newly created folder.

If you do would prefer to store the kernel sources in another directory (e.g. your home directory) then you may ignore the first two commands and change the last one to link to another directory:

su -c "ln -s /home/username/linux-2.6.0 /usr/src/linux"

This has a number of advantages and is especially useful for normal users to be able to execute the various make commands without the need of being root.

Note, I do not worry about moving it home

3. Next move into the 'linux' directory and configure the options you wish to compile into the kernel:

cd linux
make menuconfig

If you are running X-Windows you may want to run xconfig (or gconfig in gnome) for the nice graphical interface instead of menuconfig.
When finished exit and save the new configuration.

4. Now its time to compile everything:

make bzImage
make modules
make modules_install

This compiles the kernel and the various modules needed by it.

5. Next configure your system so it can boot the new kernel:

cp arch/i386/boot/bzImage /boot/vmlinuz-2.6
cp System.map /boot/System.map-2.6
rm /boot/System.map
ln -s /boot/System.map-2.6 /boot/System.map
pico -w /etc/lilo.conf

The last command will open the lilo configuration file in the pico text editor.
From here make a copy of the entry for the previous kernel making the following changes:

# Linux bootable partition config begins
image = /boot/vmlinuz-2.6
root = /dev/hda1
label = Linux-2.6
read-only

Where /dev/hda1 is the location of your boot partition.
Exit pico using cmd-x, selecting yes (y) when asked to save changes.

6. Commit the changes to the boot loader:

/sbin/lilo

If no errors occur then you should be ready to reboot and start using your new kernel!

N.B. If the new kernel boots OK but you find that various part of the system fail to initialise (the network being the obvious one) then it may be worth deleting the config link file in the /boot folder:

rm /boot/config

Last edited by Duffy; 04-20-2004 at 01:24 PM.
 
Old 04-21-2004, 11:41 AM   #3
mus335
LQ Newbie
 
Registered: Apr 2004
Distribution: Slackware, Debian Sid/Sarge
Posts: 7

Original Poster
Rep: Reputation: 0
new kernel. dies with INIT: kernel panic no init found (try passing init= to kernel)

Ok, thanks for the response.
I think you may have missed what i was asking, possibly from poor wording on my part
I am very familiar with compiling the kernel.
I am not familiar with the occurance of VFS not correctly identifying the correct root '/' partition type.
I would like some insight into this.

booting new kernel. dies with INIT:
VFS: mounting root ( ext2 filesystem ) ro

this is wrong, root is a reiserfs filesystem '/boot' is ext2.
( the default kernel sees this correctly ( VFS: mounting root (resierfs filesystem) ro )
 
Old 04-21-2004, 01:54 PM   #4
Stuartb21
Member
 
Registered: Jun 2003
Location: U.K
Distribution: Slack - Current
Posts: 55

Rep: Reputation: 15
As far as i can tell 2.6.5 has some MAJOR bugs in it, like not being able to read reiserfs.

Im sticking with 2.4.26 for now
 
Old 04-21-2004, 02:03 PM   #5
neondonkey
LQ Newbie
 
Registered: Apr 2004
Location: illinois
Distribution: home: slackware 11 and work: SLES 9 on zseries
Posts: 13

Rep: Reputation: 0
try installing the newest module-init-tools. i have heard of other people not being able to boot their 2.6* kernels because of not having this installed, or not having the newest version.
 
Old 04-21-2004, 02:38 PM   #6
mus335
LQ Newbie
 
Registered: Apr 2004
Distribution: Slackware, Debian Sid/Sarge
Posts: 7

Original Poster
Rep: Reputation: 0
Quote:
"As far as i can tell 2.6.5 has some MAJOR bugs in it, like not being able to read reiserfs."
-really, are you sure about this (?!)
This is the newest STABLE kernel,... where did you hear this,...

I don't think that is accurate,...

On another box (debian) i run 2.6.5 fine, with reiserfs. (I always make sure that /boot is ext2 though,...)

Linux 2.6.5 #3 Wed Apr 7 13:49:10 EDT 2004 i686 GNU/Linux
/dev/hda1 /boot ext2 defaults 0 2
/dev/hda2 none swap sw 0 0
/dev/hda3 / reiserfs defaults 0 0
proc /proc proc defaults 0 0
/dev/hda5 /root reiserfs defaults 0 0
/dev/hda6 /home reiserfs defaults 0 0
/dev/hda7 /var reiserfs defaults 0 0
/dev/hda8 /tmp reiserfs defaults 0 0
/dev/hda9 /usr reiserfs defaults 0 0

It did take 3 re-compiles to get this working but it's but stable so far.
I think the kernel is fine i think my .config is fine, (in fact i took the same one from the working box)
I think this is something slackware specific i am missing,.... like that slack doesn't use mkinitrd, I think I have a knowledge gap somewhere booting kernel, slackwise.

Quote:
"try installing the newest module-init-tools"
I believe i did, when i made sure i had newest, gcc, make, biinutils, etc. but i will check tonight when i get home, thanks.
 
Old 04-21-2004, 03:16 PM   #7
Stuartb21
Member
 
Registered: Jun 2003
Location: U.K
Distribution: Slack - Current
Posts: 55

Rep: Reputation: 15
What i said is just my opinion, im gonna wait till theres a few more releases, and besides if it aint broke, dont fix it!
 
Old 04-21-2004, 03:58 PM   #8
trey85stang
Senior Member
 
Registered: Sep 2003
Posts: 1,090

Rep: Reputation: 41
Thumbs up

I have had 0 problems with 2.6.* I dont run a linux machine without it

I have had similar boot problems due to newbie type errors on my part.. but I have worked them all out.

something to look at is to make sure you have support for your chipset and IDE. I will make the assumption that your .config is fine everywhere else.

You might want to post up your config file others might be able to glance at it and find a problem with it.
 
Old 04-21-2004, 06:10 PM   #9
sbharvey_linux
LQ Newbie
 
Registered: Apr 2004
Distribution: RH 8.2 and SuSE 9.0
Posts: 4

Rep: Reputation: 0
As you already know there were quit a few changes with from
kernel version 2.4.x to 2.6.*. I am also having problems.
My situation is a little worse, I am trying to get my AMD64 system going with a true 64 bit kernel. I have to patch the kernel then "peel" the oninon on all of the other issues. I have read that this is possible, and it looks
like my system wants to work, except I am having the same problem
it sounds like you are having. VFS boot failures.


I have found out that you need to have the latest mkinitrd, I believe
this binary is part of the modutils. Also I have read google etc posting..
that you must make the ext3 file system module as part of your kernel,
i.e not a loadable module. This is done in the .config file that drives the
build of the kernel.

Hope this helps
 
Old 04-22-2004, 01:52 PM   #10
mus335
LQ Newbie
 
Registered: Apr 2004
Distribution: Slackware, Debian Sid/Sarge
Posts: 7

Original Poster
Rep: Reputation: 0
here is lspci and .config:

toshiba satellite 335cds laptop
266mhz mmx
96MB RAM


(Important note to add to this post. Last night, I swapped in an old hard
drvie with debian 2.4 kernel on it updated all necessary tools for 2.6 kernel, compiled with this exact .config, it worked and booted fine. The only
difference between the two system other than distro is that the debian disk is alll ext2)


00:00.0 Host bridge: Toshiba America Info Systems 601 (rev a0)
Subsystem: Toshiba America Info Systems: Unknown device 0001
Flags: bus master, medium devsel, latency 0

00:04.0 VGA compatible controller: Chips and Technologies F65555 HiQVPro (rev c6) (prog-if 00 [VGA])
Subsystem: Toshiba America Info Systems: Unknown device 0001
Flags: stepping, medium devsel
Memory at fd000000 (32-bit, non-prefetchable) [size=16M]
Expansion ROM at <unassigned> [disabled] [size=256K]

00:0b.0 USB Controller: NEC Corporation USB (rev 02) (prog-if 10 [OHCI])
Subsystem: Toshiba America Info Systems USB
Flags: bus master, medium devsel, latency 64, IRQ 11
Memory at fcfff000 (32-bit, non-prefetchable) [size=4K]

00:11.0 Communication controller: Toshiba America Info Systems FIR Port (rev 21)
Subsystem: Toshiba America Info Systems: Unknown device 0001
Flags: bus master, slow devsel, latency 64, IRQ 11
I/O ports at ffe0 [size=32]

00:13.0 CardBus bridge: Toshiba America Info Systems ToPIC95 (rev 07)
Subsystem: Toshiba America Info Systems: Unknown device 0001
Flags: bus master, slow devsel, latency 0, IRQ 11
Memory at 10000000 (32-bit, non-prefetchable) [size=4K]
Bus: primary=00, secondary=14, subordinate=14, sec-latency=0
Memory window 0: 10400000-107ff000 (prefetchable)
Memory window 1: 10800000-10bff000
I/O window 0: 00004000-000040ff
I/O window 1: 00004400-000044ff
16-bit legacy interface ports at 0001

00:13.1 CardBus bridge: Toshiba America Info Systems ToPIC95 (rev 07)
Subsystem: Toshiba America Info Systems: Unknown device 0001
Flags: bus master, slow devsel, latency 0, IRQ 11
Memory at 10001000 (32-bit, non-prefetchable) [size=4K]
Bus: primary=00, secondary=15, subordinate=15, sec-latency=0
Memory window 0: 10c00000-10fff000 (prefetchable)
Memory window 1: 11000000-113ff000
I/O window 0: 00004800-000048ff
I/O window 1: 00004c00-00004cff
16-bit legacy interface ports at 0001

15:00.0 Ethernet controller: Abocom Systems Inc RTL8139 [FE2000VX] CardBus Fast Ethernet Attached Port Adapter (rev 10)
Subsystem: Abocom Systems Inc RTL8139 [FE2000VX] CardBus Fast Ethernet Attached Port Adapter
Flags: bus master, medium devsel, latency 64, IRQ 11
I/O ports at 4800 [size=256]
Memory at 11000000 (32-bit, non-prefetchable) [size=512]
Capabilities: [50] Power Management version 2


# only selected options included
CONFIG_X86=y
CONFIG_MMU=y
CONFIG_UID16=y
CONFIG_GENERIC_ISA_DMA=y
# Code maturity level options
CONFIG_EXPERIMENTAL=y
CONFIG_CLEAN_COMPILE=y
CONFIG_STANDALONE=y
CONFIG_BROKEN_ON_SMP=y
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_BSD_PROCESS_ACCT=y
CONFIG_SYSCTL=y
CONFIG_HOTPLUG=y
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
CONFIG_KALLSYMS=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
CONFIG_MODULE_FORCE_UNLOAD=y
CONFIG_OBSOLETE_MODPARM=y
CONFIG_MODVERSIONS=y
CONFIG_KMOD=y
# Processor type and features
CONFIG_X86_PC=y
CONFIG_M586MMX=y
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_X86_PPRO_FENCE=y
CONFIG_X86_F00F_BUG=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_ALIGNMENT_16=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_INTEL_USERCOPY=y
CONFIG_HPET_TIMER=y
CONFIG_PREEMPT=y
CONFIG_X86_UP_APIC=y
CONFIG_X86_UP_IOAPIC=y
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
CONFIG_X86_TSC=y
CONFIG_X86_MCE=y
CONFIG_NOHIGHMEM=y
CONFIG_MTRR=y
CONFIG_HAVE_DEC_LOCK=y
CONFIG_PM=y
CONFIG_ACPI=y
CONFIG_ACPI_BOOT=y
CONFIG_ACPI_INTERPRETER=y
CONFIG_ACPI_BATTERY=m
CONFIG_ACPI_BUS=y
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_PCI=y
CONFIG_ACPI_SYSTEM=y
# CPU Frequency scaling
CONFIG_PCI=y
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_MMCONFIG=y
# CONFIG_PCI_LEGACY_PROC is not set
CONFIG_PCI_NAMES=y
CONFIG_PCMCIA=y
CONFIG_PCMCIA_DEBUG=y
CONFIG_YENTA=m
CONFIG_CARDBUS=y
CONFIG_BINFMT_ELF=y
# Memory Technology Devices (MTD)
CONFIG_PARPORT_1284=y
# Plug and Play support
CONFIG_BLK_DEV_FD=y
CONFIG_BLK_DEV_LOOP=y
# CONFIG_BLK_DEV_CRYPTOLOOP is not set
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_INITRD=y
CONFIG_LBD=y
CONFIG_IDE=y # IDE compiled in
CONFIG_BLK_DEV_IDE=y
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_BLK_DEV_IDECD=y
CONFIG_BLK_DEV_IDESCSI=y
CONFIG_IDE_TASKFILE_IO=y
CONFIG_IDE_GENERIC=y
CONFIG_BLK_DEV_CMD640=y
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_BLK_DEV_GENERIC=y
CONFIG_BLK_DEV_IDEDMA_PCI=y
CONFIG_BLK_DEV_ADMA=y
CONFIG_BLK_DEV_IDEDMA=y
CONFIG_SCSI=y
CONFIG_SCSI_PROC_FS=y
# SCSI support type (disk, tape, CD-ROM)
CONFIG_BLK_DEV_SD=y
CONFIG_CHR_DEV_SG=y
CONFIG_SCSI_MULTI_LUN=y
CONFIG_SCSI_REPORT_LUNS=y
CONFIG_SCSI_QLA2XXX=y
CONFIG_NET=y
CONFIG_PACKET=y
CONFIG_NETLINK_DEV=y
CONFIG_UNIX=y
CONFIG_NET_KEY=y
CONFIG_INET=y
CONFIG_INET_AH=y
CONFIG_INET_ESP=y
CONFIG_INET_IPCOMP=y
CONFIG_XFRM=y
CONFIG_XFRM_USER=y
CONFIG_NETDEVICES=y
CONFIG_DUMMY=m
CONFIG_NET_ETHERNET=y
CONFIG_MII=y
# Tulip family network device support
CONFIG_NET_PCI=y
CONFIG_EEPRO100=y
CONFIG_E100=y
CONFIG_NET_RADIO=y
# Wireless 802.11 Frequency Hopping cards support
CONFIG_NET_WIRELESS=y
CONFIG_NET_PCMCIA=y
# ISDN subsystem
# Telephony Support
CONFIG_INPUT=y
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
CONFIG_INPUT_JOYDEV=m
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
CONFIG_INPUT_MISC=y
CONFIG_INPUT_PCSPKR=y
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
CONFIG_SERIAL_8250=y
CONFIG_SERIAL_8250_CS=y
CONFIG_SERIAL_CORE=y
CONFIG_UNIX98_PTYS=y
# Ftape, the floppy tape device driver
CONFIG_AGP=y
CONFIG_DRM=y
CONFIG_DRM_R128=y
CONFIG_SYNCLINK_CS=m
CONFIG_FB=y
# CONFIG_FB_CYBER2000 is not set
CONFIG_FB_VGA16=y
CONFIG_FB_VESA=y
CONFIG_VIDEO_SELECT=y
# Console display driver support
CONFIG_VGA_CONSOLE=y
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_PCI_CONSOLE=y
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
CONFIG_LOGO=y
CONFIG_LOGO_LINUX_VGA16=y
CONFIG_LOGO_LINUX_CLUT224=y
CONFIG_SOUND=y
CONFIG_SND=y
CONFIG_SND_OSSEMUL=y
CONFIG_SND_DUMMY=m
CONFIG_SND_YMFPCI=m
# Open Sound System
CONFIG_SOUND_TRACEINIT=y
CONFIG_SOUND_YM3812=m
CONFIG_SOUND_YMFPCI=m
CONFIG_SOUND_YMFPCI_LEGACY=y
CONFIG_USB=y
CONFIG_USB_DEBUG=y
CONFIG_USB_DEVICEFS=y
CONFIG_USB_BANDWIDTH=y
CONFIG_USB_DYNAMIC_MINORS=y
CONFIG_USB_EHCI_HCD=y
CONFIG_USB_EHCI_SPLIT_ISO=y
CONFIG_USB_OHCI_HCD=y
CONFIG_USB_UHCI_HCD=y
CONFIG_USB_STORAGE=y
CONFIG_USB_STORAGE_DEBUG=y
CONFIG_USB_STORAGE_DATAFAB=y
CONFIG_USB_STORAGE_FREECOM=y
CONFIG_USB_STORAGE_ISD200=y
CONFIG_USB_STORAGE_DPCM=y
CONFIG_USB_STORAGE_SDDR09=y
CONFIG_USB_STORAGE_SDDR55=y
CONFIG_USB_HIDINPUT=y
CONFIG_USB_HIDDEV=y
# File systems SEE all compiled in
CONFIG_EXT2_FS=y
CONFIG_EXT3_FS=y
CONFIG_JBD=y
CONFIG_REISERFS_FS=y # <- HERE it is
CONFIG_XFS_FS=y
CONFIG_MINIX_FS=y
CONFIG_ROMFS_FS=y
CONFIG_AUTOFS_FS=y
CONFIG_ISO9660_FS=y
CONFIG_JOLIET=y
CONFIG_ZISOFS=y
CONFIG_ZISOFS_FS=y
# DOS/FAT/NT Filesystems
CONFIG_FAT_FS=y
CONFIG_MSDOS_FS=y
CONFIG_VFAT_FS=y
CONFIG_NTFS_FS=y
CONFIG_NTFS_DEBUG=y
CONFIG_NTFS_RW=y
# Pseudo filesystems
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_RAMFS=y
# Network File Systems
CONFIG_NFS_FS=y
CONFIG_LOCKD=y
CONFIG_SUNRPC=y
CONFIG_SMB_FS=y
# Partition Types
CONFIG_MSDOS_PARTITION=y
CONFIG_NLS=y
CONFIG_NLS_CODEPAGE_437=y
CONFIG_NLS_ISO8859_1=y
CONFIG_NLS_UTF8=y
CONFIG_EARLY_PRINTK=y
CONFIG_X86_FIND_SMP_CONFIG=y
CONFIG_X86_MPPARSE=y
# Security options
# Cryptographic options
CONFIG_CRYPTO=y
CONFIG_CRYPTO_HMAC=y
CONFIG_CRYPTO_MD5=y
CONFIG_CRYPTO_SHA1=y
CONFIG_CRYPTO_SHA256=m
CONFIG_CRYPTO_SHA512=m
CONFIG_CRYPTO_DES=y
CONFIG_CRYPTO_BLOWFISH=m
CONFIG_CRYPTO_TWOFISH=m
CONFIG_CRYPTO_SERPENT=m
CONFIG_CRYPTO_AES=m
CONFIG_CRYPTO_CAST5=m
CONFIG_CRYPTO_CAST6=m
CONFIG_CRYPTO_DEFLATE=y
CONFIG_CRYPTO_TEST=m
# Library routines
CONFIG_ZLIB_INFLATE=y
CONFIG_ZLIB_DEFLATE=y
CONFIG_X86_BIOS_REBOOT=y
CONFIG_PC=y
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
kernel panic: not syncing: VFS on Slack 10.2 Twister512 Slackware 8 12-06-2005 10:06 AM
Not booting: Kernel panic: VFS: unable to mount root fs hamish Linux - Hardware 8 02-16-2005 03:13 AM
kernel upgrade fails, VFS error (me too, have read other posts) abs Slackware 7 08-23-2004 01:20 PM
kernel upgrade fails, VFS error cragwolf Slackware 6 08-19-2004 01:17 AM
booting new kernel. Booting new kernel dies with INIT: VFS issue, really mus335 Linux - General 0 04-21-2004 11:52 AM


All times are GMT -5. The time now is 06:07 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration