Re:[Qemu-devel] Kernel panic - not syncing: No init found. Trypassing init= option to kernel.

Re:[Qemu-devel] Kernel panic - not syncing: No init found. Trypassing init= option to kernel.

[Clemens Kolbitsch]

On Friday 19 October 2007 09:13:40 qemu-devel-request@nongnu.org wrote:
> Then I try this command:
> qemu -m 32 hda rootfs.img kernel linux-2.6.18.1/arch/i386/boot/bzImage
> -append “root=/dev/hda \clock=pit”
>
> and I get the error...
>
> I tried to pass init=/sbin/init or init=/bin/init but it doesn't help...

Hi!
Although allmost every documentation tells you to use exactly what you did, I 
always use

qemu [....] -append "root=/dev/hda1"

(note HDA1 instead HDA)

and direct booting works fine for me :-)

Clemens

RE: [Qemu-devel] Kernel panic - not syncing: No init found. Trypassing init= option to kernel.

[Kjel Delaey]

[-- Attachment #1: Type: text/plain, Size: 1239 bytes --]

If I do this I got a VFS problem

Not syncing: VFS: Unable to mount root fs on unknown-block(3,1.)

I also tried to enable reiserfs support. I read on a forum that this may be a solution to the init problem. In my case it wasn't a working solution.

> From: clemens.kol@gmx.at
> To: qemu-devel@nongnu.org; kjel_delaey@hotmail.com
> Subject: Re:[Qemu-devel] Kernel panic - not syncing: No init found. Trypassing	init= option to kernel.
> Date: Fri, 19 Oct 2007 09:19:59 +0200
> CC: 
> 
> On Friday 19 October 2007 09:13:40 qemu-devel-request@nongnu.org wrote:
> > Then I try this command:
> > qemu -m 32 hda rootfs.img kernel linux-2.6.18.1/arch/i386/boot/bzImage
> > -append “root=/dev/hda \clock=pit”
> >
> > and I get the error...
> >
> > I tried to pass init=/sbin/init or init=/bin/init but it doesn't help...
> 
> Hi!
> Although allmost every documentation tells you to use exactly what you did, I 
> always use
> 
> qemu [....] -append "root=/dev/hda1"
> 
> (note HDA1 instead HDA)
> 
> and direct booting works fine for me :-)
> 
> Clemens
> 
> 

_________________________________________________________________
Neem je vrienden overal mee dankzij Messenger op je gsm.
http://messenger.live.com

[-- Attachment #2: Type: text/html, Size: 1670 bytes --]

Re: [Qemu-devel] Kernel panic - not syncing: No init found. Trypassing init= option to kernel.

[Christian MICHON]

On 10/19/07, Kjel Delaey <kjel_delaey@hotmail.com> wrote:
>
> If I do this I got a VFS problem
>
> Not syncing: VFS: Unable to mount root fs on unknown-block(3,1.)

then maybe it's a kernel config issue. it may not be only fs dependent.

do you have the .config file ?

>
> I also tried to enable reiserfs support. I read on a forum that this may be
> a solution to the init problem. In my case it wasn't a working solution.
>
> ________________________________
> > From: clemens.kol@gmx.at
> > To: qemu-devel@nongnu.org; kjel_delaey@hotmail.com
> > Subject: Re:[Qemu-devel] Kernel panic - not syncing: No init found.
> Trypassing init= option to kernel.
> > Date: Fri, 19 Oct 2007 09:19:59 +0200
> > CC:
>
> >
> > On Friday 19 October 2007 09:13:40 qemu-devel-request@nongnu.org wrote:
> > > Then I try this command:
> > > qemu -m 32 hda rootfs.img kernel linux-2.6.18.1/arch/i386/boot/bzImage
> > > -append "root=/dev/hda \clock=pit"
> > >
> > > and I get the error...
> > >
> > > I tried to pass init=/sbin/init or init=/bin/init but it doesn't help...
> >
> > Hi!
> > Although allmost every documentation tells you to use exactly what you
> did, I
> > always use
> >
> > qemu [....] -append "root=/dev/hda1"
> >
> > (note HDA1 instead HDA)
> >
> > and direct booting works fine for me :-)
> >
> > Clemens
> >
> >
>
> ________________________________
> Start vandaag nog je eigen Windows Live Space en deel je leven met je
> vrienden Windows Live Spaces


-- 
Christian
--
http://detaolb.sourceforge.net/, a linux distribution for Qemu with Git inside !

RE: [Qemu-devel] Kernel panic - not syncing: No init found. Trypassing init= option to kernel.

[Kjel Delaey]

#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.18.1
# Fri Oct 19 09:40:25 2007
#
CONFIG_X86_32=y
CONFIG_GENERIC_TIME=y
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_SEMAPHORE_SLEEPERS=y
CONFIG_X86=y
CONFIG_MMU=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y
CONFIG_GENERIC_HWEIGHT=y
CONFIG_ARCH_MAY_HAVE_PC_FDC=y
CONFIG_DMI=y
CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"

#
# Code maturity level options
#
# CONFIG_EXPERIMENTAL is not set
CONFIG_BROKEN_ON_SMP=y
CONFIG_INIT_ENV_ARG_LIMIT=32

#
# General setup
#
CONFIG_LOCALVERSION=""
# CONFIG_LOCALVERSION_AUTO is not set
# CONFIG_SWAP is not set
# CONFIG_SYSVIPC is not set
# CONFIG_BSD_PROCESS_ACCT is not set
# CONFIG_IKCONFIG is not set
# CONFIG_RELAY is not set
CONFIG_INITRAMFS_SOURCE=""
# CONFIG_EMBEDDED is not set
CONFIG_UID16=y
CONFIG_SYSCTL=y
CONFIG_KALLSYMS=y
# CONFIG_KALLSYMS_EXTRA_PASS is not set
CONFIG_HOTPLUG=y
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_SHMEM=y
CONFIG_SLAB=y
CONFIG_VM_EVENT_COUNTERS=y
CONFIG_RT_MUTEXES=y
# CONFIG_TINY_SHMEM is not set
CONFIG_BASE_SMALL=0
# CONFIG_SLOB is not set

#
# Loadable module support
#
# CONFIG_MODULES is not set

#
# Block layer
#
# CONFIG_LBD is not set
# CONFIG_BLK_DEV_IO_TRACE is not set
# CONFIG_LSF is not set

#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
# CONFIG_IOSCHED_AS is not set
# CONFIG_IOSCHED_DEADLINE is not set
# CONFIG_IOSCHED_CFQ is not set
# CONFIG_DEFAULT_AS is not set
# CONFIG_DEFAULT_DEADLINE is not set
# CONFIG_DEFAULT_CFQ is not set
CONFIG_DEFAULT_NOOP=y
CONFIG_DEFAULT_IOSCHED="noop"

#
# Processor type and features
#
# CONFIG_SMP is not set
CONFIG_X86_PC=y
# CONFIG_X86_ELAN is not set
# CONFIG_X86_VOYAGER is not set
# CONFIG_X86_NUMAQ is not set
# CONFIG_X86_SUMMIT is not set
# CONFIG_X86_BIGSMP is not set
# CONFIG_X86_VISWS is not set
# CONFIG_X86_GENERICARCH is not set
# CONFIG_X86_ES7000 is not set
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
CONFIG_M686=y
# CONFIG_MPENTIUMII is not set
# CONFIG_MPENTIUMIII is not set
# CONFIG_MPENTIUMM is not set
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
# CONFIG_MK8 is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MEFFICEON is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MGEODEGX1 is not set
# CONFIG_MGEODE_LX is not set
# CONFIG_MCYRIXIII is not set
# CONFIG_MVIAC3_2 is not set
CONFIG_X86_GENERIC=y
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_L1_CACHE_SHIFT=7
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_X86_PPRO_FENCE=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_CMPXCHG64=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_INTEL_USERCOPY=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_X86_TSC=y
# CONFIG_HPET_TIMER is not set
CONFIG_PREEMPT_NONE=y
# CONFIG_PREEMPT_VOLUNTARY is not set
# CONFIG_PREEMPT is not set
# CONFIG_X86_UP_APIC is not set
# CONFIG_X86_MCE is not set
CONFIG_VM86=y
# CONFIG_TOSHIBA is not set
# CONFIG_I8K is not set
# CONFIG_X86_REBOOTFIXUPS is not set
# CONFIG_MICROCODE is not set
# CONFIG_X86_MSR is not set
# CONFIG_X86_CPUID is not set

#
# Firmware Drivers
#
# CONFIG_EDD is not set
# CONFIG_DELL_RBU is not set
# CONFIG_DCDBAS is not set
CONFIG_NOHIGHMEM=y
# CONFIG_HIGHMEM4G is not set
# CONFIG_HIGHMEM64G is not set
CONFIG_PAGE_OFFSET=0xC0000000
CONFIG_FLATMEM=y
CONFIG_FLAT_NODE_MEM_MAP=y
# CONFIG_SPARSEMEM_STATIC is not set
CONFIG_SPLIT_PTLOCK_CPUS=4
# CONFIG_RESOURCES_64BIT is not set
# CONFIG_MATH_EMULATION is not set
# CONFIG_MTRR is not set
# CONFIG_REGPARM is not set
# CONFIG_SECCOMP is not set
# CONFIG_HZ_100 is not set
CONFIG_HZ_250=y
# CONFIG_HZ_1000 is not set
CONFIG_HZ=250
CONFIG_PHYSICAL_START=0x100000
# CONFIG_COMPAT_VDSO is not set

#
# Power management options (ACPI, APM)
#
# CONFIG_PM is not set

#
# ACPI (Advanced Configuration and Power Interface) Support
#

#
# CPU Frequency scaling
#
# CONFIG_CPU_FREQ is not set

#
# Bus options (PCI, PCMCIA, EISA, MCA, ISA)
#
# CONFIG_PCI is not set
CONFIG_ISA_DMA_API=y
# CONFIG_ISA is not set
# CONFIG_MCA is not set
# CONFIG_SCx200 is not set

#
# PCCARD (PCMCIA/CardBus) support
#
# CONFIG_PCCARD is not set

#
# PCI Hotplug Support
#

#
# Executable file formats
#
CONFIG_BINFMT_ELF=y
# CONFIG_BINFMT_AOUT is not set
# CONFIG_BINFMT_MISC is not set

#
# Networking
#
# CONFIG_NET is not set

#
# Device Drivers
#

#
# Generic Driver Options
#
CONFIG_STANDALONE=y
# CONFIG_PREVENT_FIRMWARE_BUILD is not set
# CONFIG_FW_LOADER is not set
# CONFIG_SYS_HYPERVISOR is not set

#
# Connector - unified userspace <-> kernelspace linker
#

#
# Memory Technology Devices (MTD)
#
# CONFIG_MTD is not set

#
# Parallel port support
#
# CONFIG_PARPORT is not set

#
# Plug and Play support
#

#
# Block devices
#
# CONFIG_BLK_DEV_FD is not set
# CONFIG_BLK_DEV_COW_COMMON is not set
# CONFIG_BLK_DEV_LOOP is not set
# CONFIG_BLK_DEV_RAM is not set
# CONFIG_BLK_DEV_INITRD is not set
# CONFIG_CDROM_PKTCDVD is not set

#
# ATA/ATAPI/MFM/RLL support
#
CONFIG_IDE=y
CONFIG_BLK_DEV_IDE=y

#
# Please see Documentation/ide.txt for help/info on IDE drives
#
# CONFIG_BLK_DEV_IDE_SATA is not set
# CONFIG_BLK_DEV_HD_IDE is not set
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_IDEDISK_MULTI_MODE=y
# CONFIG_BLK_DEV_IDECD is not set
# CONFIG_BLK_DEV_IDEFLOPPY is not set
# CONFIG_IDE_TASK_IOCTL is not set

#
# IDE chipset support/bugfixes
#
CONFIG_IDE_GENERIC=y
# CONFIG_BLK_DEV_CMD640 is not set
# CONFIG_IDE_ARM is not set
# CONFIG_BLK_DEV_IDEDMA is not set
# CONFIG_IDEDMA_AUTO is not set
# CONFIG_BLK_DEV_HD is not set

#
# SCSI device support
#
# CONFIG_RAID_ATTRS is not set
# CONFIG_SCSI is not set

#
# Multi-device support (RAID and LVM)
#
# CONFIG_MD is not set

#
# Fusion MPT device support
#
# CONFIG_FUSION is not set

#
# IEEE 1394 (FireWire) support
#

#
# I2O device support
#

#
# ISDN subsystem
#

#
# Telephony Support
#
# CONFIG_PHONE is not set

#
# Input device support
#
CONFIG_INPUT=y

#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
# CONFIG_INPUT_MOUSEDEV_PSAUX is not set
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
# CONFIG_INPUT_JOYDEV is not set
# CONFIG_INPUT_TSDEV is not set
# CONFIG_INPUT_EVDEV is not set
# CONFIG_INPUT_EVBUG is not set

#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_LKKBD is not set
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_KEYBOARD_NEWTON is not set
# CONFIG_INPUT_MOUSE is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
# CONFIG_INPUT_MISC is not set

#
# Hardware I/O ports
#
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
# CONFIG_SERIO_SERPORT is not set
# CONFIG_SERIO_CT82C710 is not set
CONFIG_SERIO_LIBPS2=y
# CONFIG_SERIO_RAW is not set
# CONFIG_GAMEPORT is not set

#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
# CONFIG_VT_HW_CONSOLE_BINDING is not set
# CONFIG_SERIAL_NONSTANDARD is not set

#
# Serial drivers
#
# CONFIG_SERIAL_8250 is not set

#
# Non-8250 serial port support
#
CONFIG_UNIX98_PTYS=y
# CONFIG_LEGACY_PTYS is not set

#
# IPMI
#
# CONFIG_IPMI_HANDLER is not set

#
# Watchdog Cards
#
# CONFIG_WATCHDOG is not set
# CONFIG_HW_RANDOM is not set
# CONFIG_NVRAM is not set
# CONFIG_RTC is not set
# CONFIG_GEN_RTC is not set
# CONFIG_DTLK is not set
# CONFIG_R3964 is not set

#
# Ftape, the floppy tape device driver
#
# CONFIG_FTAPE is not set
# CONFIG_MWAVE is not set
# CONFIG_PC8736x_GPIO is not set
# CONFIG_NSC_GPIO is not set
# CONFIG_CS5535_GPIO is not set
# CONFIG_RAW_DRIVER is not set
# CONFIG_HANGCHECK_TIMER is not set

#
# TPM devices
#

#
# I2C support
#
# CONFIG_I2C is not set

#
# SPI support
#
# CONFIG_SPI is not set
# CONFIG_SPI_MASTER is not set

#
# Dallas's 1-wire bus
#

#
# Hardware Monitoring support
#
# CONFIG_HWMON is not set
# CONFIG_HWMON_VID is not set

#
# Misc devices
#

#
# Multimedia devices
#
# CONFIG_VIDEO_DEV is not set
CONFIG_VIDEO_V4L2=y

#
# Digital Video Broadcasting Devices
#

#
# Graphics support
#
# CONFIG_FIRMWARE_EDID is not set
# CONFIG_FB is not set

#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
# CONFIG_VGACON_SOFT_SCROLLBACK is not set
# CONFIG_VIDEO_SELECT is not set
CONFIG_DUMMY_CONSOLE=y
# CONFIG_BACKLIGHT_LCD_SUPPORT is not set

#
# Sound
#
# CONFIG_SOUND is not set

#
# USB support
#
# CONFIG_USB_ARCH_HAS_HCD is not set
# CONFIG_USB_ARCH_HAS_OHCI is not set
# CONFIG_USB_ARCH_HAS_EHCI is not set

#
# NOTE: USB_STORAGE enables SCSI, and 'SCSI disk support'
#

#
# USB Gadget Support
#
# CONFIG_USB_GADGET is not set

#
# MMC/SD Card support
#
# CONFIG_MMC is not set

#
# LED devices
#
# CONFIG_NEW_LEDS is not set

#
# LED drivers
#

#
# LED Triggers
#

#
# InfiniBand support
#

#
# EDAC - error detection and reporting (RAS) (EXPERIMENTAL)
#

#
# Real Time Clock
#

#
# DMA Engine support
#
# CONFIG_DMA_ENGINE is not set

#
# DMA Clients
#

#
# DMA Devices
#

#
# File systems
#
CONFIG_EXT2_FS=y
CONFIG_EXT2_FS_XATTR=y
# CONFIG_EXT2_FS_POSIX_ACL is not set
CONFIG_EXT2_FS_SECURITY=y
# CONFIG_EXT2_FS_XIP is not set
# CONFIG_EXT3_FS is not set
CONFIG_FS_MBCACHE=y
# CONFIG_REISERFS_FS is not set
# CONFIG_JFS_FS is not set
# CONFIG_FS_POSIX_ACL is not set
# CONFIG_XFS_FS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_ROMFS_FS is not set
# CONFIG_INOTIFY is not set
# CONFIG_QUOTA is not set
CONFIG_DNOTIFY=y
# CONFIG_AUTOFS_FS is not set
# CONFIG_AUTOFS4_FS is not set
# CONFIG_FUSE_FS is not set

#
# CD-ROM/DVD Filesystems
#
# CONFIG_ISO9660_FS is not set
# CONFIG_UDF_FS is not set

#
# DOS/FAT/NT Filesystems
#
# CONFIG_MSDOS_FS is not set
# CONFIG_VFAT_FS is not set
# CONFIG_NTFS_FS is not set

#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
# CONFIG_PROC_KCORE is not set
CONFIG_SYSFS=y
# CONFIG_TMPFS is not set
# CONFIG_HUGETLBFS is not set
# CONFIG_HUGETLB_PAGE is not set
CONFIG_RAMFS=y

#
# Miscellaneous filesystems
#
# CONFIG_HFSPLUS_FS is not set
# CONFIG_CRAMFS is not set
# CONFIG_VXFS_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set

#
# Partition Types
#
# CONFIG_PARTITION_ADVANCED is not set
CONFIG_MSDOS_PARTITION=y

#
# Native Language Support
#
# CONFIG_NLS is not set

#
# Kernel hacking
#
CONFIG_TRACE_IRQFLAGS_SUPPORT=y
# CONFIG_PRINTK_TIME is not set
# CONFIG_MAGIC_SYSRQ is not set
# CONFIG_UNUSED_SYMBOLS is not set
# CONFIG_DEBUG_KERNEL is not set
CONFIG_LOG_BUF_SHIFT=14
CONFIG_DEBUG_BUGVERBOSE=y
# CONFIG_DEBUG_FS is not set
# CONFIG_UNWIND_INFO is not set
CONFIG_EARLY_PRINTK=y
CONFIG_DOUBLEFAULT=y

#
# Security options
#
# CONFIG_KEYS is not set
# CONFIG_SECURITY is not set

#
# Cryptographic options
#
# CONFIG_CRYPTO is not set

#
# Hardware crypto devices
#

#
# Library routines
#
# CONFIG_CRC_CCITT is not set
# CONFIG_CRC16 is not set
# CONFIG_CRC32 is not set
# CONFIG_LIBCRC32C is not set
CONFIG_PLIST=y
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_X86_BIOS_REBOOT=y
CONFIG_KTIME_SCALAR=y

----------------------------------------> Date: Fri, 19 Oct 2007 10:12:51 +0200> From: christian.michon@gmail.com> To: qemu-devel@nongnu.org> Subject: Re: [Qemu-devel] Kernel panic - not syncing: No init found. Trypassing init= option to kernel.>> On 10/19/07, Kjel Delaey  wrote:>>>> If I do this I got a VFS problem>>>> Not syncing: VFS: Unable to mount root fs on unknown-block(3,1.)>> then maybe it's a kernel config issue. it may not be only fs dependent.>> do you have the .config file ?>>>>> I also tried to enable reiserfs support. I read on a forum that this may be>> a solution to the init problem. In my case it wasn't a working solution.>>>> ________________________________>>> From: clemens.kol@gmx.at>>> To: qemu-devel@nongnu.org; kjel_delaey@hotmail.com>>> Subject: Re:[Qemu-devel] Kernel panic - not syncing: No init found.>> Trypassing init= option to kernel.>>> Date: Fri, 19 Oct 2007 09:19:59 +0200>>> CC:>>>>>>>> On Friday 19 October 2007 09:13:40 qemu-devel-request@nongnu.org wrote:>>>> Then I try this command:>>>> qemu -m 32 hda rootfs.img kernel linux-2.6.18.1/arch/i386/boot/bzImage>>>> -append "root=/dev/hda \clock=pit">>>>>>>> and I get the error...>>>>>>>> I tried to pass init=/sbin/init or init=/bin/init but it doesn't help...>>>>>> Hi!>>> Although allmost every documentation tells you to use exactly what you>> did, I>>> always use>>>>>> qemu [....] -append "root=/dev/hda1">>>>>> (note HDA1 instead HDA)>>>>>> and direct booting works fine for me :-)>>>>>> Clemens>>>>>>>>>> ________________________________>> Start vandaag nog je eigen Windows Live Space en deel je leven met je>> vrienden Windows Live Spaces>>> --> Christian> --> http://detaolb.sourceforge.net/, a linux distribution for Qemu with Git inside !>>

_________________________________________________________________
Deel al je foto's met je vrienden! Maak je eigen online plek!
http://spaces.live.com

Re: [Qemu-devel] Kernel panic - not syncing: No init found. Trypassing init= option to kernel.

[Christian MICHON]

try to turn on these:

CONFIG_BLK_DEV_INITRD=y
CONFIG_BLOCK=y
CONFIG_PROC_SYSCTL=y (this one may not be valid for 2.6.18*)

-- 
Christian
--
http://detaolb.sourceforge.net/, a linux distribution for Qemu with Git inside !

Re: [Qemu-devel] Kernel panic - not syncing: No init found. Trypassing init= option to kernel.

[Christian MICHON]

Kjel,

I managed to compile the kernel with your config file and the vanilla
linux 2.6.18.1.
With the "debug" initramfs from DetaolB, I get similar error messages.

I enabled only CONFIG_BLK_DEV_INITRD=y and the problem was gone.

Could you please try this ? I can send you separately (off list) the
"debug" file.

-- 
Christian
--
http://detaolb.sourceforge.net/, a linux distribution for Qemu with Git inside !

RE: [Qemu-devel] Kernel panic - not syncing: No init found. Trypassing init= option to kernel.

[Kjel Delaey]

[-- Attachment #1: Type: text/plain, Size: 2460 bytes --]

I came home and I tried the stuff at my desktop (I was in school in the morning).
 
I followed your steps Christian and I have also downloaded the detaolb_v06.iso file. I have also changed the line in .config.I have extracted "debug" in my working directory.
If I use "debug" I have the following message:
/bin/sh: can't access tty: job control turned off.
 
By the way, thank you all for helping me out :)
I'm trying since 8.30 am. It must work ;)
(init problem/solved!)qemu -m 32 -hda rootfs.img -kernel linux-2.6.18.1/arch/i386/boot/bzImage -append "root=/dev/hda \clock=pit"
(tty problem)qemu -m 32 -hda rootfs.img -kernel linux-2.6.18.1/arch/i386/boot/bzImage -initrd debug -append "root=/dev/hda \clock=pit"
 
Turning off tty in busybox isn't a working solution.
I couldn't send an email earlier because I had problems with Hotmail.//*************************************************Why do I keep getting "sh: can't access tty; job control turned off" errors? Why doesn't Control-C work within my shell?
Job control will be turned off since your shell can not obtain a controlling terminal. This typically happens when you run your shell on /dev/console. The kernel will not provide a controlling terminal on the /dev/console device. Your should run your shell on a normal tty such as tty1 or ttyS0 and everything will work perfectly. If you REALLY want your shell to run on /dev/console, then you can hack your kernel (if you are into that sortof thing) by changing drivers/char/tty_io.c to change the lines where it sets "noctty = 1;" to instead set it to "0". I recommend you instead run your shell on a real console... 



> Date: Fri, 19 Oct 2007 14:19:55 +0200> From: christian.michon@gmail.com> To: qemu-devel@nongnu.org> Subject: Re: [Qemu-devel] Kernel panic - not syncing: No init found. Trypassing init= option to kernel.> > Kjel,> > I managed to compile the kernel with your config file and the vanilla> linux 2.6.18.1.> With the "debug" initramfs from DetaolB, I get similar error messages.> > I enabled only CONFIG_BLK_DEV_INITRD=y and the problem was gone.> > Could you please try this ? I can send you separately (off list) the> "debug" file.> > -- > Christian> --> http://detaolb.sourceforge.net/, a linux distribution for Qemu with Git inside !> > 
_________________________________________________________________
Start vandaag nog je eigen Windows Live Space en deel je leven met je vrienden
http://spaces.live.com

[-- Attachment #2: Type: text/html, Size: 2955 bytes --]

RE: [Qemu-devel] Kernel panic - not syncing: No init found. Trypassing init= option to kernel.

[Kjel Delaey]

[-- Attachment #1.1: Type: text/plain, Size: 2714 bytes --]

qemu screens


From: kjel_delaey@hotmail.comTo: qemu-devel@nongnu.orgSubject: RE: [Qemu-devel] Kernel panic - not syncing: No init found. Trypassing init= option to kernel.Date: Fri, 19 Oct 2007 19:04:54 +0200


I came home and I tried the stuff at my desktop (I was in school in the morning). I followed your steps Christian and I have also downloaded the detaolb_v06.iso file. I have also changed the line in .config.I have extracted "debug" in my working directory.If I use "debug" I have the following message:/bin/sh: can't access tty: job control turned off. By the way, thank you all for helping me out :)I'm trying since 8.30 am. It must work ;)(init problem/solved!)qemu -m 32 -hda rootfs.img -kernel linux-2.6.18.1/arch/i386/boot/bzImage -append "root=/dev/hda \clock=pit"(tty problem)qemu -m 32 -hda rootfs.img -kernel linux-2.6.18.1/arch/i386/boot/bzImage -initrd debug -append "root=/dev/hda \clock=pit" Turning off tty in busybox isn't a working solution.I couldn't send an email earlier because I had problems with Hotmail.//*************************************************Why do I keep getting "sh: can't access tty; job control turned off" errors? Why doesn't Control-C work within my shell?Job control will be turned off since your shell can not obtain a controlling terminal. This typically happens when you run your shell on /dev/console. The kernel will not provide a controlling terminal on the /dev/console device. Your should run your shell on a normal tty such as tty1 or ttyS0 and everything will work perfectly. If you REALLY want your shell to run on /dev/console, then you can hack your kernel (if you are into that sortof thing) by changing drivers/char/tty_io.c to change the lines where it sets "noctty = 1;" to instead set it to "0". I recommend you instead run your shell on a real console... 

> Date: Fri, 19 Oct 2007 14:19:55 +0200> From: christian.michon@gmail.com> To: qemu-devel@nongnu.org> Subject: Re: [Qemu-devel] Kernel panic - not syncing: No init found. Trypassing init= option to kernel.> > Kjel,> > I managed to compile the kernel with your config file and the vanilla> linux 2.6.18.1.> With the "debug" initramfs from DetaolB, I get similar error messages.> > I enabled only CONFIG_BLK_DEV_INITRD=y and the problem was gone.> > Could you please try this ? I can send you separately (off list) the> "debug" file.> > -- > Christian> --> http://detaolb.sourceforge.net/, a linux distribution for Qemu with Git inside !> > 

Neem je vrienden overal mee dankzij Messenger op je gsm. Messenger voor Mobile 
_________________________________________________________________
Deel al je foto's met je vrienden! Maak je eigen online plek!
http://spaces.live.com

[-- Attachment #1.2: Type: text/html, Size: 3547 bytes --]

[-- Attachment #2: Init.png --]
[-- Type: image/png, Size: 209554 bytes --]

[-- Attachment #3: tty.png --]
[-- Type: image/png, Size: 206183 bytes --]

Re: [Qemu-devel] Kernel panic - not syncing: No init found. Trypassing init= option to kernel.

[Christian MICHON]

On 10/19/07, Kjel Delaey <kjel_delaey@hotmail.com> wrote:
>
> I came home and I tried the stuff at my desktop (I was in school in the
> morning).
>
>  I followed your steps Christian and I have also downloaded the
> detaolb_v06.iso file. I have also changed the line in .config.
> I have extracted "debug" in my working directory.
>  If I use "debug" I have the following message:
>  /bin/sh: can't access tty: job control turned off.
>
>  By the way, thank you all for helping me out :)
>
> I'm trying since 8.30 am. It must work ;)
>  (init problem/solved!)
> qemu -m 32 -hda rootfs.img -kernel linux-2.6.18.1/arch/i386/boot/bzImage
> -append "root=/dev/hda \clock=pit"
>  (tty problem)
> qemu -m 32 -hda rootfs.img -kernel linux-2.6.18.1/arch/i386/boot/bzImage
> -initrd debug -append "root=/dev/hda \clock=pit"
>
>  Turning off tty in busybox isn't a working solution.
>
> I couldn't send an email earlier because I had problems with Hotmail.
>

it's normal. "debug" is where the first process is actually a shell.
you need to boot on an initramfs that contains proper runlevel 3 and
login utils.

Please download detaolb_v01.iso and extract "initrmfs.v01".
This should do!

-- 
Christian
--
http://detaolb.sourceforge.net/, a linux distribution for Qemu with Git inside !

RE: [Qemu-devel] Kernel panic - not syncing: No init found. Trypassing init= option to kernel.

[Kjel Delaey]

[-- Attachment #1: Type: text/plain, Size: 3021 bytes --]

Problem solved!Thanks for helping me out!
 
Kjel D.


From: kjel_delaey@hotmail.comTo: qemu-devel@nongnu.orgSubject: RE: [Qemu-devel] Kernel panic - not syncing: No init found. Trypassing init= option to kernel.Date: Fri, 19 Oct 2007 19:05:55 +0200


qemu screens


From: kjel_delaey@hotmail.comTo: qemu-devel@nongnu.orgSubject: RE: [Qemu-devel] Kernel panic - not syncing: No init found. Trypassing init= option to kernel.Date: Fri, 19 Oct 2007 19:04:54 +0200

I came home and I tried the stuff at my desktop (I was in school in the morning). I followed your steps Christian and I have also downloaded the detaolb_v06.iso file. I have also changed the line in .config.I have extracted "debug" in my working directory.If I use "debug" I have the following message:/bin/sh: can't access tty: job control turned off. By the way, thank you all for helping me out :)I'm trying since 8.30 am. It must work ;)(init problem/solved!)qemu -m 32 -hda rootfs.img -kernel linux-2.6.18.1/arch/i386/boot/bzImage -append "root=/dev/hda \clock=pit"(tty problem)qemu -m 32 -hda rootfs.img -kernel linux-2.6.18.1/arch/i386/boot/bzImage -initrd debug -append "root=/dev/hda \clock=pit" Turning off tty in busybox isn't a working solution.I couldn't send an email earlier because I had problems with Hotmail.//*************************************************Why do I keep getting "sh: can't access tty; job control turned off" errors? Why doesn't Control-C work within my shell?Job control will be turned off since your shell can not obtain a controlling terminal. This typically happens when you run your shell on /dev/console. The kernel will not provide a controlling terminal on the /dev/console device. Your should run your shell on a normal tty such as tty1 or ttyS0 and everything will work perfectly. If you REALLY want your shell to run on /dev/console, then you can hack your kernel (if you are into that sortof thing) by changing drivers/char/tty_io.c to change the lines where it sets "noctty = 1;" to instead set it to "0". I recommend you instead run your shell on a real console... 

> Date: Fri, 19 Oct 2007 14:19:55 +0200> From: christian.michon@gmail.com> To: qemu-devel@nongnu.org> Subject: Re: [Qemu-devel] Kernel panic - not syncing: No init found. Trypassing init= option to kernel.> > Kjel,> > I managed to compile the kernel with your config file and the vanilla> linux 2.6.18.1.> With the "debug" initramfs from DetaolB, I get similar error messages.> > I enabled only CONFIG_BLK_DEV_INITRD=y and the problem was gone.> > Could you please try this ? I can send you separately (off list) the> "debug" file.> > -- > Christian> --> http://detaolb.sourceforge.net/, a linux distribution for Qemu with Git inside !> > 

Neem je vrienden overal mee dankzij Messenger op je gsm. Messenger voor Mobile 

Deel je gedachten direct met je vrienden Windows Live Messenger 
_________________________________________________________________
Deel je gedachten direct met je vrienden
http://messenger.live.com

[-- Attachment #2: Type: text/html, Size: 4194 bytes --]