Very Computer

I have a slackware 8.1 machine that works fine with 2.4.18/19 kernels,
but,when I reboot with the 2.5.31/32 kernels, the system have a "kernel
panic: no init found. try passing init= option to kernel" The fs is a
reisersfs v.3.6 on Intel PIIX4 chipset with udma33 disk.
The disk is not corrupted because if I back to 2.4.X the machine boot
fine.

what's wrong?

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

What are you passing as the init= arg? What is your boot manager? (Grub?
Lilo? 3rd Party?)

no init means that when the kernel boot sequence tries to spawn off
/sbin/init, it cannot find the file.The fault could be any one of multiple.
It would help in the future if for problems like this you pasted your boot
loader config file.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

the boot manager is Lilo 22.2

my lilo.conf is:
-----------------
boot= /dev/hda
image = /boot/vmlinuz
  root = /dev/hda2
  label = Linux
  read-only
-----------------

Quote:> no init means that when the kernel boot sequence tries to spawn off
> /sbin/init, it cannot find the file.The fault could be any one of multiple.

I don't know why with 2.4.xx works fine and with 2.5.xx make a kernel
panic...

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

The driver for /dev/hda2 (IDE driver) may not have been compiled in
or not otherwise installed. This would make the root file-system
inaccessible so /sbin/init can't be found.

Check for other boot messages to verify this.

Cheers,
* Johnson
Penguin : Linux version 2.4.18 on an i686 machine (797.90 BogoMips).
The US military has given us many words, FUBAR, SNAFU, now ENRON.
Yes, top management were graduates of West Point and Annapolis.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://www.veryComputer.com/
Please read the FAQ at  http://www.veryComputer.com/

The driver is compiled in :-) and the kernel detect the disk.
The disk appear to being correctly mounted ro, but the system hang...

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

I've tried to compile with a minimal 2.5.32 kernel:

CONFIG_X86=y
CONFIG_ISA=y
CONFIG_UID16=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_NET=y
CONFIG_SYSVIPC=y
CONFIG_SYSCTL=y
CONFIG_M686=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_X86_L1_CACHE_SHIFT=5
CONFIG_X86_TSC=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_X86_PPRO_FENCE=y
CONFIG_NOHIGHMEM=y
CONFIG_PCI=y
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_NAMES=y
CONFIG_KCORE_ELF=y
CONFIG_BINFMT_AOUT=y
CONFIG_IDE=y
CONFIG_BLK_DEV_IDE=y
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_IDEDISK_MULTI_MODE=y
CONFIG_BLK_DEV_IDECD=y
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
CONFIG_BLK_DEV_IDEDMA_PCI=y
CONFIG_IDEDMA_PCI_AUTO=y
CONFIG_BLK_DEV_IDEDMA=y
CONFIG_BLK_DEV_PIIX=y
CONFIG_PIIX_TUNING=y
CONFIG_IDEDMA_AUTO=y
CONFIG_BLK_DEV_IDE_MODES=y
CONFIG_INPUT=y
CONFIG_SOUND_GAMEPORT=y
CONFIG_INPUT_KEYBOARD=y
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
CONFIG_UNIX98_PTYS=y
CONFIG_UNIX98_PTY_COUNT=256
CONFIG_REISERFS_FS=y
CONFIG_RAMFS=y
CONFIG_PROC_FS=y
CONFIG_DEVPTS_FS=y
CONFIG_MSDOS_PARTITION=y
CONFIG_VGA_CONSOLE=y
CONFIG_VIDEO_SELECT=y
CONFIG_SECURITY_CAPABILITIES=y
CONFIG_ZLIB_INFLATE=y
CONFIG_ZLIB_DEFLATE=y

This is my last row on the screen before the kernel panic:

ide: Assuming 33MHz system bus speed for PIO modes; override with
idebus=xx
PIIX4: IDE controller on PCI bus 00 dev 11
PIIX4: chipset revision 1
PIIX4: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0x10c0-0x10x7, BIOS settings: hda:pio, hdb:pio
    ide1: BM-DMA at 0x10c8-0x10cf, BIOS settings: hdc:pio, hdd:pio
hda: HITACHI_DK239A-65, ATA DISK drive
hdc: SANYO CRD-S372BVA, ATAPI CD/RVR-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
blk: queue c020544, I/O limit 4095Mb (mask 0xffffffff)
hda: host protected area => 1
hda: 12685680 sectors (6495 MB) w/512KiB Cache, CHS=789/255/63, UDMA(33)
hdc: ATAPI 24X CD-ROM drive, 256kB Cache, DMA
Uniform CD-ROM driver Revision: 3.12
 hda: hda1 hda2
found reiserfs format "3.6" with standard journal
Reiserfs hournal params: device ide0(3,2), size 8192, journal first
block 18, max trans len 1024, max batch 900, max commit age 30, max
trans age 30
reiserfs: checking transaction log (ide0(3,2)) for (ide0(3,2))
Using r5 hash to sort names
VFS: Mounted root (reiserfs filesystem) readonly.
Freeing unused kernel memory: 208K freed
Kernel panic: No init found.  Try passing init= option to kernel.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/