From: Zou M. <zo...@co...> - 2002-04-18 15:51:30
|
Hi, I compiled my own uml kernel using uml-patch-2.4.18-16, and then I tried to boot it as: $ ./linux-2.4.18/linux mem=256M ubd0=root_fs Then I got the following message: [...SNIP] INIT: version 2.84 booting Activating swap. Checking root file system... fsck 1.27 (8-Mar-2002) fsck.ext2: No such file or directory while trying to open /dev/ubd0 /dev/ubd0: The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> fsck failed. Please repair manually and reboot. Please note that the root file system is currently mounted read-only. To remount it read-write: # mount -n -o remount,rw / CONTROL-D will exit from this shell and REBOOT the system. (none):~# [...SNIP] However, if I use original debian linux-2.4.18.13um-1 to boot the root_fs, it runs well. What's the problem with my home-compiled um-linux? If changing "/etc/fstab" on my root_fs from "/dev/ubd0 / ext2 defaults 0 1" to "/dev/ubd/0 / ext2 defaults 0 1" it hangs after the following message: (the login virtual terminal is not popped out) [...SNIP] Starting kernel log daemon: klogd. Starting internet superserver: inetd. Starting deferred execution scheduler: atd. Starting periodic command scheduler: cron. INIT: Id "1" respawning too fast: disabled for 5 minutes INIT: Id "2" respawning too fast: disabled for 5 minutes INIT: no more processes left in this runlevel [...SNIP] Anyway, what is the difference between "/dev/ubd0" and "/dev/ubd/0"? how to let my home-compiled uml kernel recognize one of them? TIA! -------------------------------------------------------------------------- below is the config file for my home-compiled uml: # # Automatically generated make config: don't edit # CONFIG_USERMODE=y # CONFIG_ISA is not set # CONFIG_SBUS is not set # CONFIG_PCI is not set CONFIG_UID16=y CONFIG_RWSEM_XCHGADD_ALGORITHM=y # # Code maturity level options # CONFIG_EXPERIMENTAL=y # # General Setup # CONFIG_STDIO_CONSOLE=y # CONFIG_NET is not set CONFIG_SYSVIPC=y CONFIG_BSD_PROCESS_ACCT=y CONFIG_SYSCTL=y CONFIG_BINFMT_AOUT=y CONFIG_BINFMT_ELF=y CONFIG_BINFMT_MISC=y CONFIG_UNIX98_PTYS=y CONFIG_UNIX98_PTY_COUNT=256 CONFIG_SSL=y CONFIG_HOSTFS=m CONFIG_MCONSOLE=y CONFIG_MAGIC_SYSRQ=y # CONFIG_HOST_2G_2G is not set # CONFIG_UML_SMP is not set # CONFIG_SMP is not set CONFIG_CON_ZERO_CHAN="fd:0,fd:1" CONFIG_CON_CHAN="xterm" CONFIG_SSL_CHAN="pty" # # Loadable module support # CONFIG_MODULES=y # CONFIG_KMOD is not set # # Devices # CONFIG_BLK_DEV_UBD=y # CONFIG_BLK_DEV_UBD_SYNC is not set CONFIG_BLK_DEV_LOOP=y CONFIG_BLK_DEV_RAM=y CONFIG_BLK_DEV_RAM_SIZE=4096 CONFIG_BLK_DEV_INITRD=y # CONFIG_MMAPPER is not set # CONFIG_UML_SOUND is not set # CONFIG_SOUND is not set # CONFIG_HOSTAUDIO is not set CONFIG_FD_CHAN=y CONFIG_NULL_CHAN=y CONFIG_PORT_CHAN=y CONFIG_PTY_CHAN=y CONFIG_TTY_CHAN=y CONFIG_XTERM_CHAN=y # # File systems # CONFIG_QUOTA=y CONFIG_AUTOFS_FS=m CONFIG_AUTOFS4_FS=m CONFIG_REISERFS_FS=m # CONFIG_REISERFS_CHECK is not set # CONFIG_REISERFS_PROC_INFO is not set # CONFIG_ADFS_FS is not set # CONFIG_AFFS_FS is not set # CONFIG_HFS_FS is not set # CONFIG_BFS_FS is not set # CONFIG_EXT3_FS is not set # CONFIG_JBD is not set CONFIG_FAT_FS=m CONFIG_MSDOS_FS=m CONFIG_UMSDOS_FS=m CONFIG_VFAT_FS=m # CONFIG_EFS_FS is not set CONFIG_JFFS_FS_VERBOSE=0 CONFIG_JFFS_PROC_FS=y CONFIG_JFFS2_FS_DEBUG=0 # CONFIG_CRAMFS is not set # CONFIG_TMPFS is not set # CONFIG_RAMFS is not set CONFIG_ISO9660_FS=m # CONFIG_JOLIET is not set # CONFIG_ZISOFS is not set CONFIG_MINIX_FS=m # CONFIG_VXFS_FS is not set # CONFIG_NTFS_FS is not set # CONFIG_HPFS_FS is not set CONFIG_PROC_FS=y CONFIG_DEVFS_FS=y CONFIG_DEVFS_MOUNT=y # CONFIG_DEVFS_DEBUG is not set CONFIG_DEVPTS_FS=y # CONFIG_QNX4FS_FS is not set # CONFIG_ROMFS_FS is not set CONFIG_EXT2_FS=y # CONFIG_SYSV_FS is not set # CONFIG_UDF_FS is not set # CONFIG_UFS_FS is not set # CONFIG_NCPFS_NLS is not set # CONFIG_SMB_FS is not set # CONFIG_ZISOFS_FS is not set # CONFIG_ZLIB_FS_INFLATE is not set # # Partition Types # # CONFIG_PARTITION_ADVANCED is not set CONFIG_MSDOS_PARTITION=y # CONFIG_SMB_NLS is not set CONFIG_NLS=y # # Native Language Support # CONFIG_NLS_DEFAULT="iso8859-1" # CONFIG_NLS_CODEPAGE_437 is not set # CONFIG_NLS_CODEPAGE_737 is not set # CONFIG_NLS_CODEPAGE_775 is not set # CONFIG_NLS_CODEPAGE_850 is not set # CONFIG_NLS_CODEPAGE_852 is not set # CONFIG_NLS_CODEPAGE_855 is not set # CONFIG_NLS_CODEPAGE_857 is not set # CONFIG_NLS_CODEPAGE_860 is not set # CONFIG_NLS_CODEPAGE_861 is not set # CONFIG_NLS_CODEPAGE_862 is not set # CONFIG_NLS_CODEPAGE_863 is not set # CONFIG_NLS_CODEPAGE_864 is not set # CONFIG_NLS_CODEPAGE_865 is not set # CONFIG_NLS_CODEPAGE_866 is not set # CONFIG_NLS_CODEPAGE_869 is not set # CONFIG_NLS_CODEPAGE_936 is not set # CONFIG_NLS_CODEPAGE_950 is not set # CONFIG_NLS_CODEPAGE_932 is not set # CONFIG_NLS_CODEPAGE_949 is not set # CONFIG_NLS_CODEPAGE_874 is not set # CONFIG_NLS_ISO8859_8 is not set # CONFIG_NLS_CODEPAGE_1250 is not set # CONFIG_NLS_CODEPAGE_1251 is not set # CONFIG_NLS_ISO8859_1 is not set # CONFIG_NLS_ISO8859_2 is not set # CONFIG_NLS_ISO8859_3 is not set # CONFIG_NLS_ISO8859_4 is not set # CONFIG_NLS_ISO8859_5 is not set # CONFIG_NLS_ISO8859_6 is not set # CONFIG_NLS_ISO8859_7 is not set # CONFIG_NLS_ISO8859_9 is not set # CONFIG_NLS_ISO8859_13 is not set # CONFIG_NLS_ISO8859_14 is not set # CONFIG_NLS_ISO8859_15 is not set # CONFIG_NLS_KOI8_R is not set # CONFIG_NLS_KOI8_U is not set # CONFIG_NLS_UTF8 is not set # # Multi-device support (RAID and LVM) # # CONFIG_MD is not set # # Memory Technology Devices (MTD) # # CONFIG_MTD is not set # # Kernel hacking # # CONFIG_DEBUG_SLAB is not set CONFIG_DEBUGSYM=y CONFIG_PT_PROXY=y # CONFIG_GPROF is not set # CONFIG_GCOV is not set # # Statistics Gathering # CONFIG_MEMORY_STATS=y |
From: David C. <da...@da...> - 2002-04-18 16:39:38
|
Zou Min wrote: > Anyway, what is the difference between "/dev/ubd0" and "/dev/ubd/0"? how > to let my home-compiled uml kernel recognize one of them? /dev/ubd0 is a regular /dev entry, and /dev/ubd/0 is from devfs. To get rid of the initial error, pass 'devfs=nomount' to your kernel at boot time. Note that you've configured your kernel to have Devfs mount at boot time, rather than having it mount when devfsd is started - Generally, this is a bad thing. As for the terminals respawning, it could be that UML is trying to run xterm, but can't - By the look of it, for all consoles (other than 0), it's going to try to run xterm, so you'll want to see if it can. Usually, that error is caused by getty not being able to open the appropriate /dev entry, so getty just bails out, but without more info, it's rather difficult to figure it out clearly. David. -- David Coulson http://davidcoulson.net/ d...@vi... http://journal.davidcoulson.net/ |