[gentoo-user] Howto erase the "Insert root floppy and press enter" item before the kernel panic?

[gentoo-user] Howto erase the "Insert root floppy and press enter" item before the kernel panic?

[David Wei]

Hi,
I am trying kexec with "kernel panic reboot" cause i have to manage my server remotely.
the "kernel panic reboot" (http://gentoo-wiki.com/TIP_Kernel_Panic_Reboot) has beening working so good so far for the regular kernel panic.However,sometimes when i were missed some file system items,the booking process would ask me:
"VFS: Unable to mount root fs via NFS,trying floppy
Insert root floppy and Press Enter."
And the system hungup there waiting for my Enter.
How can I remove this item from the booting process and panic directly so that it can reboot? Besides,I want to keep the NFS service.
Thank you in advance.

-------------------------------
魏亮 David Wei

您可以通过下面的方式和我联系：
MSN: inadavid@hotmail.com
Gtalk: inadavid@gmail.com
Email: davidwei@newbread.tj.cn

Re: [gentoo-user] Howto erase the "Insert root floppy and press enter" item before the kernel panic?

[Andrey Vul]

2008/10/10 David Wei <davidwei@newbread.tj.cn>:
> Hi,
> I am trying kexec with "kernel panic reboot" cause i have to manage my server remotely.
> the "kernel panic reboot" (http://gentoo-wiki.com/TIP_Kernel_Panic_Reboot) has beening working so good so far for the regular kernel panic.However,sometimes when i were missed some file system items,the booking process would ask me:
> "VFS: Unable to mount root fs via NFS,trying floppy
> Insert root floppy and Press Enter."
> And the system hungup there waiting for my Enter.
> How can I remove this item from the booting process and panic directly so that it can reboot? Besides,I want to keep the NFS service.
> Thank you in advance.
I'm guessing that this is due to the floppy being compiled into the
emergency kernel.
In any case, can you post your .config for the emergency kernel?

--
Andrey Vul

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

Re: [gentoo-user] Howto erase the "Insert root floppy and press enter" item before the kernel panic?

[David Wei]

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

Sorry, I forgot that file .
the .config is in the attachment this time.
Thank you .

On Fri, 10 Oct 2008 10:05:36 -0400
"Andrey Vul" <andrey.vul@gmail.com> wrote:

> 2008/10/10 David Wei <davidwei@newbread.tj.cn>:
> > Hi,
> > I am trying kexec with "kernel panic reboot" cause i have to manage my server remotely.
> > the "kernel panic reboot" (http://gentoo-wiki.com/TIP_Kernel_Panic_Reboot) has beening working so good so far for the regular kernel panic.However,sometimes when i were missed some file system items,the booking process would ask me:
> > "VFS: Unable to mount root fs via NFS,trying floppy
> > Insert root floppy and Press Enter."
> > And the system hungup there waiting for my Enter.
> > How can I remove this item from the booting process and panic directly so that it can reboot? Besides,I want to keep the NFS service.
> > Thank you in advance.
> I'm guessing that this is due to the floppy being compiled into the
> emergency kernel.
> In any case, can you post your .config for the emergency kernel?
> 
> --
> Andrey Vul
> 
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
> A: Top-posting.
> Q: What is the most annoying thing in e-mail?
> 


-------------------------------
魏亮 David Wei

您可以通过下面的方式和我联系：
MSN: inadavid@hotmail.com
Gtalk: inadavid@gmail.com
Email: davidwei@newbread.tj.cn

[-- Attachment #2: .config --]
[-- Type: application/octet-stream, Size: 22578 bytes --]

#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.25-gentoo-r8
# Fri Oct 10 12:08:11 2008
#
# CONFIG_64BIT is not set
CONFIG_X86_32=y
# CONFIG_X86_64 is not set
CONFIG_X86=y
CONFIG_ARCH_DEFCONFIG="arch/x86/configs/i386_defconfig"
# CONFIG_GENERIC_LOCKBREAK is not set
CONFIG_GENERIC_TIME=y
CONFIG_GENERIC_CMOS_UPDATE=y
CONFIG_CLOCKSOURCE_WATCHDOG=y
CONFIG_GENERIC_CLOCKEVENTS=y
CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_HAVE_LATENCYTOP_SUPPORT=y
CONFIG_SEMAPHORE_SLEEPERS=y
CONFIG_FAST_CMPXCHG_LOCAL=y
CONFIG_MMU=y
CONFIG_ZONE_DMA=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y
CONFIG_GENERIC_BUG=y
CONFIG_GENERIC_HWEIGHT=y
# CONFIG_GENERIC_GPIO is not set
CONFIG_ARCH_MAY_HAVE_PC_FDC=y
CONFIG_DMI=y
# CONFIG_RWSEM_GENERIC_SPINLOCK is not set
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
# CONFIG_ARCH_HAS_ILOG2_U32 is not set
# CONFIG_ARCH_HAS_ILOG2_U64 is not set
CONFIG_ARCH_HAS_CPU_IDLE_WAIT=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
# CONFIG_GENERIC_TIME_VSYSCALL is not set
CONFIG_ARCH_HAS_CPU_RELAX=y
# CONFIG_HAVE_SETUP_PER_CPU_AREA is not set
CONFIG_ARCH_HIBERNATION_POSSIBLE=y
CONFIG_ARCH_SUSPEND_POSSIBLE=y
# CONFIG_ZONE_DMA32 is not set
CONFIG_ARCH_POPULATES_NODE_MAP=y
# CONFIG_AUDIT_ARCH is not set
CONFIG_ARCH_SUPPORTS_AOUT=y
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_X86_BIOS_REBOOT=y
CONFIG_KTIME_SCALAR=y
CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"

#
# General setup
#
CONFIG_EXPERIMENTAL=y
CONFIG_BROKEN_ON_SMP=y
CONFIG_INIT_ENV_ARG_LIMIT=32
CONFIG_LOCALVERSION=""
# CONFIG_LOCALVERSION_AUTO is not set
# CONFIG_SWAP is not set
# CONFIG_SYSVIPC is not set
# CONFIG_POSIX_MQUEUE is not set
# CONFIG_BSD_PROCESS_ACCT is not set
# CONFIG_TASKSTATS is not set
# CONFIG_AUDIT is not set
# CONFIG_IKCONFIG is not set
CONFIG_LOG_BUF_SHIFT=18
# CONFIG_CGROUPS is not set
# CONFIG_GROUP_SCHED is not set
# CONFIG_SYSFS_DEPRECATED_V2 is not set
# CONFIG_RELAY is not set
CONFIG_NAMESPACES=y
# CONFIG_UTS_NS is not set
# CONFIG_USER_NS is not set
# CONFIG_PID_NS is not set
CONFIG_BLK_DEV_INITRD=y
CONFIG_INITRAMFS_SOURCE=""
CONFIG_CC_OPTIMIZE_FOR_SIZE=y
CONFIG_SYSCTL=y
# CONFIG_EMBEDDED is not set
CONFIG_UID16=y
CONFIG_SYSCTL_SYSCALL=y
CONFIG_KALLSYMS=y
CONFIG_KALLSYMS_ALL=y
# CONFIG_KALLSYMS_EXTRA_PASS is not set
CONFIG_HOTPLUG=y
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
CONFIG_COMPAT_BRK=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_ANON_INODES=y
CONFIG_EPOLL=y
CONFIG_SIGNALFD=y
CONFIG_TIMERFD=y
CONFIG_EVENTFD=y
CONFIG_SHMEM=y
CONFIG_VM_EVENT_COUNTERS=y
CONFIG_SLUB_DEBUG=y
# CONFIG_SLAB is not set
CONFIG_SLUB=y
# CONFIG_SLOB is not set
CONFIG_PROFILING=y
# CONFIG_MARKERS is not set
CONFIG_OPROFILE=y
CONFIG_HAVE_OPROFILE=y
CONFIG_HAVE_KPROBES=y
CONFIG_HAVE_KRETPROBES=y
CONFIG_PROC_PAGE_MONITOR=y
CONFIG_SLABINFO=y
CONFIG_RT_MUTEXES=y
# CONFIG_TINY_SHMEM is not set
CONFIG_BASE_SMALL=0
# CONFIG_MODULES is not set
CONFIG_BLOCK=y
CONFIG_LBD=y
# CONFIG_BLK_DEV_IO_TRACE is not set
# CONFIG_LSF is not set
# CONFIG_BLK_DEV_BSG is not set

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

#
# Processor type and features
#
# CONFIG_TICK_ONESHOT is not set
# CONFIG_NO_HZ is not set
# CONFIG_HIGH_RES_TIMERS is not set
CONFIG_GENERIC_CLOCKEVENTS_BUILD=y
# CONFIG_SMP is not set
# CONFIG_X86_PC is not set
# 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=y
# CONFIG_X86_ES7000 is not set
# CONFIG_X86_RDC321X is not set
# CONFIG_X86_VSMP is not set
# CONFIG_SCHED_NO_NO_OMIT_FRAME_POINTER is not set
# CONFIG_PARAVIRT_GUEST is not set
CONFIG_X86_CYCLONE_TIMER=y
# 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 is not set
# CONFIG_MPENTIUMII is not set
CONFIG_MPENTIUMIII=y
# 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_MVIAC7 is not set
# CONFIG_MPSC is not set
# CONFIG_MCORE2 is not set
# CONFIG_GENERIC_CPU is not set
# CONFIG_X86_GENERIC is not set
CONFIG_X86_CMPXCHG=y
CONFIG_X86_L1_CACHE_SHIFT=5
CONFIG_X86_XADD=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_INTEL_USERCOPY=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_X86_P6_NOP=y
CONFIG_X86_TSC=y
CONFIG_X86_CMOV=y
CONFIG_X86_MINIMUM_CPU_FAMILY=6
CONFIG_X86_DEBUGCTLMSR=y
# CONFIG_HPET_TIMER is not set
# CONFIG_IOMMU_HELPER is not set
# CONFIG_PREEMPT_NONE is not set
CONFIG_PREEMPT_VOLUNTARY=y
# CONFIG_PREEMPT is not set
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
# 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=y
CONFIG_MICROCODE_OLD_INTERFACE=y
CONFIG_X86_MSR=y
CONFIG_X86_CPUID=y
# CONFIG_NOHIGHMEM is not set
CONFIG_HIGHMEM4G=y
# CONFIG_HIGHMEM64G is not set
CONFIG_PAGE_OFFSET=0xC0000000
CONFIG_HIGHMEM=y
CONFIG_SELECT_MEMORY_MODEL=y
CONFIG_FLATMEM_MANUAL=y
# CONFIG_DISCONTIGMEM_MANUAL is not set
# CONFIG_SPARSEMEM_MANUAL is not set
CONFIG_FLATMEM=y
CONFIG_FLAT_NODE_MEM_MAP=y
# CONFIG_SPARSEMEM_STATIC is not set
# CONFIG_SPARSEMEM_VMEMMAP_ENABLE is not set
CONFIG_SPLIT_PTLOCK_CPUS=4
CONFIG_RESOURCES_64BIT=y
CONFIG_ZONE_DMA_FLAG=1
CONFIG_BOUNCE=y
CONFIG_VIRT_TO_BUS=y
# CONFIG_HIGHPTE is not set
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y
CONFIG_SECCOMP=y
# CONFIG_HZ_100 is not set
CONFIG_HZ_250=y
# CONFIG_HZ_300 is not set
# CONFIG_HZ_1000 is not set
CONFIG_HZ=250
# CONFIG_SCHED_HRTICK is not set
# CONFIG_KEXEC is not set
# CONFIG_CRASH_DUMP is not set
CONFIG_PHYSICAL_START=0x100000
# CONFIG_RELOCATABLE is not set
CONFIG_PHYSICAL_ALIGN=0x100000
CONFIG_COMPAT_VDSO=y
CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y

#
# Power management options
#
# CONFIG_PM is not set

#
# CPU Frequency scaling
#
# CONFIG_CPU_FREQ is not set
# CONFIG_CPU_IDLE is not set

#
# Bus options (PCI etc.)
#
# CONFIG_PCI is not set
# CONFIG_ARCH_SUPPORTS_MSI is not set
CONFIG_ISA_DMA_API=y
# CONFIG_ISA is not set
# CONFIG_MCA is not set
# CONFIG_SCx200 is not set
# CONFIG_PCCARD is not set

#
# Executable file formats / Emulations
#
# CONFIG_BINFMT_ELF is not set
# CONFIG_BINFMT_AOUT is not set
# CONFIG_BINFMT_MISC is not set

#
# Networking
#
CONFIG_NET=y

#
# Networking options
#
CONFIG_PACKET=y
# CONFIG_PACKET_MMAP is not set
CONFIG_UNIX=y
CONFIG_XFRM=y
# CONFIG_XFRM_USER is not set
# CONFIG_XFRM_SUB_POLICY is not set
# CONFIG_XFRM_MIGRATE is not set
# CONFIG_XFRM_STATISTICS is not set
# CONFIG_NET_KEY is not set
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
# CONFIG_IP_ADVANCED_ROUTER is not set
CONFIG_IP_FIB_HASH=y
CONFIG_IP_PNP=y
CONFIG_IP_PNP_DHCP=y
# CONFIG_IP_PNP_BOOTP is not set
# CONFIG_IP_PNP_RARP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_IP_MROUTE is not set
# CONFIG_ARPD is not set
# CONFIG_SYN_COOKIES is not set
# CONFIG_INET_AH is not set
# CONFIG_INET_ESP is not set
# CONFIG_INET_IPCOMP is not set
# CONFIG_INET_XFRM_TUNNEL is not set
CONFIG_INET_TUNNEL=y
CONFIG_INET_XFRM_MODE_TRANSPORT=y
CONFIG_INET_XFRM_MODE_TUNNEL=y
# CONFIG_INET_XFRM_MODE_BEET is not set
# CONFIG_INET_LRO is not set
CONFIG_INET_DIAG=y
CONFIG_INET_TCP_DIAG=y
# CONFIG_TCP_CONG_ADVANCED is not set
CONFIG_TCP_CONG_CUBIC=y
CONFIG_DEFAULT_TCP_CONG="cubic"
# CONFIG_TCP_MD5SIG is not set
CONFIG_IPV6=y
# CONFIG_IPV6_PRIVACY is not set
# CONFIG_IPV6_ROUTER_PREF is not set
# CONFIG_IPV6_OPTIMISTIC_DAD is not set
# CONFIG_INET6_AH is not set
# CONFIG_INET6_ESP is not set
# CONFIG_INET6_IPCOMP is not set
# CONFIG_IPV6_MIP6 is not set
# CONFIG_INET6_XFRM_TUNNEL is not set
# CONFIG_INET6_TUNNEL is not set
CONFIG_INET6_XFRM_MODE_TRANSPORT=y
CONFIG_INET6_XFRM_MODE_TUNNEL=y
# CONFIG_INET6_XFRM_MODE_BEET is not set
# CONFIG_INET6_XFRM_MODE_ROUTEOPTIMIZATION is not set
CONFIG_IPV6_SIT=y
# CONFIG_IPV6_TUNNEL is not set
# CONFIG_IPV6_MULTIPLE_TABLES is not set
# CONFIG_NETWORK_SECMARK is not set
# CONFIG_NETFILTER is not set
# CONFIG_IP_DCCP is not set
# CONFIG_IP_SCTP is not set
# CONFIG_TIPC is not set
# CONFIG_ATM is not set
# CONFIG_BRIDGE is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_DECNET is not set
# CONFIG_LLC2 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set
# CONFIG_NET_SCHED is not set

#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
# CONFIG_HAMRADIO is not set
# CONFIG_CAN is not set
# CONFIG_IRDA is not set
# CONFIG_BT is not set
# CONFIG_AF_RXRPC is not set

#
# Wireless
#
# CONFIG_CFG80211 is not set
# CONFIG_WIRELESS_EXT is not set
# CONFIG_MAC80211 is not set
# CONFIG_IEEE80211 is not set
# CONFIG_RFKILL is not set
# CONFIG_NET_9P is not set

#
# Device Drivers
#

#
# Generic Driver Options
#
CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug"
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y
CONFIG_FW_LOADER=y
# CONFIG_DEBUG_DRIVER is not set
# CONFIG_DEBUG_DEVRES is not set
# CONFIG_SYS_HYPERVISOR is not set
# CONFIG_CONNECTOR is not set
# CONFIG_MTD is not set
# CONFIG_PARPORT is not set
CONFIG_BLK_DEV=y
CONFIG_BLK_DEV_FD=y
# CONFIG_BLK_DEV_COW_COMMON is not set
CONFIG_BLK_DEV_LOOP=y
# CONFIG_BLK_DEV_CRYPTOLOOP is not set
# CONFIG_BLK_DEV_NBD is not set
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_COUNT=16
CONFIG_BLK_DEV_RAM_SIZE=4096
# CONFIG_BLK_DEV_XIP is not set
# CONFIG_CDROM_PKTCDVD is not set
# CONFIG_ATA_OVER_ETH is not set
CONFIG_MISC_DEVICES=y
# CONFIG_EEPROM_93CX6 is not set
# CONFIG_ENCLOSURE_SERVICES is not set
CONFIG_HAVE_IDE=y
# CONFIG_IDE is not set

#
# SCSI device support
#
# CONFIG_RAID_ATTRS is not set
CONFIG_SCSI=y
CONFIG_SCSI_DMA=y
# CONFIG_SCSI_TGT is not set
CONFIG_SCSI_NETLINK=y
# CONFIG_SCSI_PROC_FS is not set

#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=y
# CONFIG_CHR_DEV_ST is not set
# CONFIG_CHR_DEV_OSST is not set
CONFIG_BLK_DEV_SR=y
# CONFIG_BLK_DEV_SR_VENDOR is not set
CONFIG_CHR_DEV_SG=y
# CONFIG_CHR_DEV_SCH is not set

#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
# CONFIG_SCSI_MULTI_LUN is not set
# CONFIG_SCSI_CONSTANTS is not set
# CONFIG_SCSI_LOGGING is not set
# CONFIG_SCSI_SCAN_ASYNC is not set

#
# SCSI Transports
#
CONFIG_SCSI_SPI_ATTRS=y
CONFIG_SCSI_FC_ATTRS=y
# CONFIG_SCSI_ISCSI_ATTRS is not set
# CONFIG_SCSI_SAS_LIBSAS is not set
# CONFIG_SCSI_SRP_ATTRS is not set
CONFIG_SCSI_LOWLEVEL=y
# CONFIG_ISCSI_TCP is not set
# CONFIG_SCSI_DEBUG is not set
# CONFIG_ATA is not set
# CONFIG_MD is not set
# CONFIG_MACINTOSH_DRIVERS is not set
# CONFIG_NETDEVICES is not set
# CONFIG_ISDN is not set
# CONFIG_PHONE is not set

#
# Input device support
#
CONFIG_INPUT=y
# CONFIG_INPUT_FF_MEMLESS is not set
# CONFIG_INPUT_POLLDEV is not set

#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
# CONFIG_INPUT_JOYDEV is not set
CONFIG_INPUT_EVDEV=y
# 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_KEYBOARD_STOWAWAY is not set
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
CONFIG_MOUSE_PS2_ALPS=y
CONFIG_MOUSE_PS2_LOGIPS2PP=y
CONFIG_MOUSE_PS2_SYNAPTICS=y
CONFIG_MOUSE_PS2_LIFEBOOK=y
CONFIG_MOUSE_PS2_TRACKPOINT=y
# CONFIG_MOUSE_PS2_TOUCHKIT is not set
# CONFIG_MOUSE_SERIAL is not set
# CONFIG_MOUSE_VSXXXAA is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TABLET 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=y
CONFIG_SERIAL_8250_CONSOLE=y
CONFIG_FIX_EARLYCON_MEM=y
CONFIG_SERIAL_8250_NR_UARTS=4
CONFIG_SERIAL_8250_RUNTIME_UARTS=4
# CONFIG_SERIAL_8250_EXTENDED is not set

#
# Non-8250 serial port support
#
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
CONFIG_UNIX98_PTYS=y
CONFIG_LEGACY_PTYS=y
CONFIG_LEGACY_PTY_COUNT=256
# CONFIG_IPMI_HANDLER is not set
CONFIG_HW_RANDOM=y
CONFIG_HW_RANDOM_VIA=y
# CONFIG_NVRAM is not set
CONFIG_RTC=y
# CONFIG_R3964 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=y
CONFIG_MAX_RAW_DEVS=256
# CONFIG_HANGCHECK_TIMER is not set
# CONFIG_TCG_TPM is not set
# CONFIG_TELCLOCK is not set
# CONFIG_I2C is not set

#
# SPI support
#
# CONFIG_SPI is not set
# CONFIG_SPI_MASTER is not set
# CONFIG_W1 is not set
# CONFIG_POWER_SUPPLY is not set
# CONFIG_HWMON is not set
# CONFIG_THERMAL is not set
# CONFIG_WATCHDOG is not set

#
# Sonics Silicon Backplane
#
CONFIG_SSB_POSSIBLE=y
# CONFIG_SSB is not set

#
# Multifunction device drivers
#
# CONFIG_MFD_SM501 is not set

#
# Multimedia devices
#
# CONFIG_VIDEO_DEV is not set
# CONFIG_DVB_CORE is not set
CONFIG_DAB=y

#
# Graphics support
#
# CONFIG_VGASTATE is not set
# CONFIG_VIDEO_OUTPUT_CONTROL is not set
# CONFIG_FB is not set
# CONFIG_BACKLIGHT_LCD_SUPPORT is not set

#
# Display device support
#
# CONFIG_DISPLAY_SUPPORT is not set

#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
CONFIG_VGACON_SOFT_SCROLLBACK=y
CONFIG_VGACON_SOFT_SCROLLBACK_SIZE=128
CONFIG_VIDEO_SELECT=y
CONFIG_DUMMY_CONSOLE=y

#
# Sound
#
CONFIG_SOUND=y

#
# Advanced Linux Sound Architecture
#
# CONFIG_SND is not set

#
# Open Sound System
#
CONFIG_SOUND_PRIME=y
# CONFIG_SOUND_OSS is not set
CONFIG_HID_SUPPORT=y
CONFIG_HID=y
# CONFIG_HID_DEBUG is not set
# CONFIG_HIDRAW is not set
CONFIG_USB_SUPPORT=y
# 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'
#
# CONFIG_USB_GADGET is not set
# CONFIG_MMC is not set
# CONFIG_MEMSTICK is not set
# CONFIG_NEW_LEDS is not set
# CONFIG_EDAC is not set
# CONFIG_RTC_CLASS is not set

#
# Userspace I/O
#
# CONFIG_UIO is not set

#
# Firmware Drivers
#
# CONFIG_EDD is not set
# CONFIG_DELL_RBU is not set
# CONFIG_DCDBAS is not set
# CONFIG_DMIID is not set

#
# File systems
#
# CONFIG_EXT2_FS is not set
# CONFIG_EXT3_FS is not set
# CONFIG_EXT4DEV_FS is not set
# CONFIG_REISERFS_FS is not set
# CONFIG_JFS_FS is not set
CONFIG_FS_POSIX_ACL=y
# CONFIG_XFS_FS is not set
# CONFIG_GFS2_FS is not set
# CONFIG_OCFS2_FS is not set
# CONFIG_DNOTIFY is not set
# CONFIG_INOTIFY is not set
# CONFIG_QUOTA is not set
# CONFIG_AUTOFS_FS is not set
# CONFIG_AUTOFS4_FS is not set
# CONFIG_FUSE_FS is not set
CONFIG_GENERIC_ACL=y

#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=y
# CONFIG_JOLIET is not set
# CONFIG_ZISOFS is not set
# CONFIG_UDF_FS is not set

#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=y
CONFIG_MSDOS_FS=y
CONFIG_VFAT_FS=y
CONFIG_FAT_DEFAULT_CODEPAGE=437
CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1"
# CONFIG_NTFS_FS is not set

#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_PROC_SYSCTL=y
CONFIG_SYSFS=y
CONFIG_TMPFS=y
CONFIG_TMPFS_POSIX_ACL=y
CONFIG_HUGETLBFS=y
CONFIG_HUGETLB_PAGE=y
# CONFIG_CONFIGFS_FS is not set

#
# Miscellaneous filesystems
#
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_HFSPLUS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EFS_FS is not set
# CONFIG_CRAMFS is not set
# CONFIG_SQUASHFS is not set
# CONFIG_VXFS_FS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_ROMFS_FS is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set
CONFIG_NETWORK_FILESYSTEMS=y
CONFIG_NFS_FS=y
CONFIG_NFS_V3=y
# CONFIG_NFS_V3_ACL is not set
# CONFIG_NFS_V4 is not set
# CONFIG_NFS_DIRECTIO is not set
CONFIG_NFSD=y
CONFIG_NFSD_V3=y
# CONFIG_NFSD_V3_ACL is not set
# CONFIG_NFSD_V4 is not set
CONFIG_NFSD_TCP=y
CONFIG_ROOT_NFS=y
CONFIG_LOCKD=y
CONFIG_LOCKD_V4=y
CONFIG_EXPORTFS=y
CONFIG_NFS_COMMON=y
CONFIG_SUNRPC=y
# CONFIG_SUNRPC_BIND34 is not set
# CONFIG_RPCSEC_GSS_KRB5 is not set
# CONFIG_RPCSEC_GSS_SPKM3 is not set
# CONFIG_SMB_FS is not set
# CONFIG_CIFS is not set
# CONFIG_NCP_FS is not set
# CONFIG_CODA_FS is not set
# CONFIG_AFS_FS is not set

#
# Partition Types
#
# CONFIG_PARTITION_ADVANCED is not set
CONFIG_MSDOS_PARTITION=y
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="iso8859-1"
CONFIG_NLS_CODEPAGE_437=y
# 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_ASCII=y
CONFIG_NLS_ISO8859_1=y
# 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=y
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
CONFIG_NLS_UTF8=y
# CONFIG_DLM is not set

#
# Kernel hacking
#
CONFIG_TRACE_IRQFLAGS_SUPPORT=y
# CONFIG_PRINTK_TIME is not set
CONFIG_ENABLE_WARN_DEPRECATED=y
# CONFIG_ENABLE_MUST_CHECK is not set
CONFIG_MAGIC_SYSRQ=y
CONFIG_UNUSED_SYMBOLS=y
# CONFIG_DEBUG_FS is not set
# CONFIG_HEADERS_CHECK is not set
CONFIG_DEBUG_KERNEL=y
# CONFIG_DEBUG_SHIRQ is not set
CONFIG_DETECT_SOFTLOCKUP=y
# CONFIG_SCHED_DEBUG is not set
# CONFIG_SCHEDSTATS is not set
CONFIG_TIMER_STATS=y
# CONFIG_SLUB_DEBUG_ON is not set
# CONFIG_SLUB_STATS is not set
# CONFIG_DEBUG_RT_MUTEXES is not set
# CONFIG_RT_MUTEX_TESTER is not set
# CONFIG_DEBUG_SPINLOCK is not set
# CONFIG_DEBUG_MUTEXES is not set
# CONFIG_DEBUG_LOCK_ALLOC is not set
# CONFIG_PROVE_LOCKING is not set
# CONFIG_LOCK_STAT is not set
# CONFIG_DEBUG_SPINLOCK_SLEEP is not set
# CONFIG_DEBUG_LOCKING_API_SELFTESTS is not set
# CONFIG_DEBUG_KOBJECT is not set
# CONFIG_DEBUG_HIGHMEM is not set
CONFIG_DEBUG_BUGVERBOSE=y
# CONFIG_DEBUG_INFO is not set
# CONFIG_DEBUG_VM is not set
# CONFIG_DEBUG_LIST is not set
# CONFIG_DEBUG_SG is not set
# CONFIG_FRAME_POINTER is not set
# CONFIG_BOOT_PRINTK_DELAY is not set
# CONFIG_BACKTRACE_SELF_TEST is not set
# CONFIG_FAULT_INJECTION is not set
# CONFIG_LATENCYTOP is not set
# CONFIG_SAMPLES is not set
CONFIG_EARLY_PRINTK=y
CONFIG_DEBUG_STACKOVERFLOW=y
# CONFIG_DEBUG_STACK_USAGE is not set
# CONFIG_DEBUG_PAGEALLOC is not set
# CONFIG_DEBUG_RODATA is not set
# CONFIG_4KSTACKS is not set
CONFIG_X86_FIND_SMP_CONFIG=y
CONFIG_X86_MPPARSE=y
CONFIG_DOUBLEFAULT=y
CONFIG_IO_DELAY_TYPE_0X80=0
CONFIG_IO_DELAY_TYPE_0XED=1
CONFIG_IO_DELAY_TYPE_UDELAY=2
CONFIG_IO_DELAY_TYPE_NONE=3
CONFIG_IO_DELAY_0X80=y
# CONFIG_IO_DELAY_0XED is not set
# CONFIG_IO_DELAY_UDELAY is not set
# CONFIG_IO_DELAY_NONE is not set
CONFIG_DEFAULT_IO_DELAY_TYPE=0
# CONFIG_CPA_DEBUG is not set

#
# Security options
#
# CONFIG_KEYS is not set
# CONFIG_SECURITY is not set
# CONFIG_SECURITY_FILE_CAPABILITIES is not set
CONFIG_CRYPTO=y
# CONFIG_CRYPTO_SEQIV is not set
# CONFIG_CRYPTO_MANAGER is not set
# CONFIG_CRYPTO_HMAC is not set
# CONFIG_CRYPTO_XCBC is not set
# CONFIG_CRYPTO_NULL is not set
# CONFIG_CRYPTO_MD4 is not set
# CONFIG_CRYPTO_MD5 is not set
# CONFIG_CRYPTO_SHA1 is not set
# CONFIG_CRYPTO_SHA256 is not set
# CONFIG_CRYPTO_SHA512 is not set
# CONFIG_CRYPTO_WP512 is not set
# CONFIG_CRYPTO_TGR192 is not set
# CONFIG_CRYPTO_GF128MUL is not set
# CONFIG_CRYPTO_ECB is not set
# CONFIG_CRYPTO_CBC is not set
# CONFIG_CRYPTO_PCBC is not set
# CONFIG_CRYPTO_LRW is not set
# CONFIG_CRYPTO_XTS is not set
# CONFIG_CRYPTO_CTR is not set
# CONFIG_CRYPTO_GCM is not set
# CONFIG_CRYPTO_CCM is not set
# CONFIG_CRYPTO_CRYPTD is not set
# CONFIG_CRYPTO_DES is not set
# CONFIG_CRYPTO_FCRYPT is not set
# CONFIG_CRYPTO_BLOWFISH is not set
# CONFIG_CRYPTO_TWOFISH is not set
# CONFIG_CRYPTO_TWOFISH_586 is not set
# CONFIG_CRYPTO_SERPENT is not set
# CONFIG_CRYPTO_AES is not set
# CONFIG_CRYPTO_AES_586 is not set
# CONFIG_CRYPTO_CAST5 is not set
# CONFIG_CRYPTO_CAST6 is not set
# CONFIG_CRYPTO_TEA is not set
# CONFIG_CRYPTO_ARC4 is not set
# CONFIG_CRYPTO_KHAZAD is not set
# CONFIG_CRYPTO_ANUBIS is not set
# CONFIG_CRYPTO_SEED is not set
# CONFIG_CRYPTO_SALSA20 is not set
# CONFIG_CRYPTO_SALSA20_586 is not set
# CONFIG_CRYPTO_DEFLATE is not set
# CONFIG_CRYPTO_MICHAEL_MIC is not set
# CONFIG_CRYPTO_CRC32C is not set
# CONFIG_CRYPTO_CAMELLIA is not set
# CONFIG_CRYPTO_AUTHENC is not set
# CONFIG_CRYPTO_LZO is not set
CONFIG_CRYPTO_HW=y
# CONFIG_CRYPTO_DEV_PADLOCK is not set
CONFIG_HAVE_KVM=y
CONFIG_VIRTUALIZATION=y
# CONFIG_KVM is not set
# CONFIG_LGUEST is not set
# CONFIG_VIRTIO_BALLOON is not set

#
# Library routines
#
CONFIG_BITREVERSE=y
# CONFIG_CRC_CCITT is not set
# CONFIG_CRC16 is not set
# CONFIG_CRC_ITU_T is not set
CONFIG_CRC32=y
# CONFIG_CRC7 is not set
# CONFIG_LIBCRC32C is not set
CONFIG_PLIST=y
CONFIG_HAS_IOMEM=y
CONFIG_HAS_IOPORT=y
CONFIG_HAS_DMA=y

Re: [gentoo-user] Howto erase the "Insert root floppy and press enter" item before the kernel panic?

[Andrey Vul]

On Fri, Oct 10, 2008 at 10:33 PM, David Wei <davidwei@newbread.tj.cn> wrote:
> Sorry, I forgot that file .
> the .config is in the attachment this time.
> Thank you .
>
> On Fri, 10 Oct 2008 10:05:36 -0400
> "Andrey Vul" <andrey.vul@gmail.com> wrote:
>
>> 2008/10/10 David Wei <davidwei@newbread.tj.cn>:
>> > Hi,
>> > I am trying kexec with "kernel panic reboot" cause i have to manage my server remotely.
>> > the "kernel panic reboot" (http://gentoo-wiki.com/TIP_Kernel_Panic_Reboot) has beening working so good so far for the regular kernel panic.However,sometimes when i were missed some file system items,the booking process would ask me:
>> > "VFS: Unable to mount root fs via NFS,trying floppy
>> > Insert root floppy and Press Enter."
>> > And the system hungup there waiting for my Enter.
>> > How can I remove this item from the booting process and panic directly so that it can reboot? Besides,I want to keep the NFS service.
>> > Thank you in advance.
>> I'm guessing that this is due to the floppy being compiled into the
>> emergency kernel.
>> In any case, can you post your .config for the emergency kernel?
>>

Nothing in the .config looks suspicious.
It looks like it's inevitable that kernel patching will be needed, at
least, using the preprocessor to "hide" the floppy code.
Try this (it comments out floppy support which happens after NFS support):
comment_floppy.patch
--- init/do_mounts.c    2008-04-16 22:49:44.000000000 -0400
+++ init/do_mounts2.c   2008-10-10 23:03:06.867876561 -0400
@@ -308,7 +308,8 @@
                ROOT_DEV = Root_FD0;
        }
 #endif
-#ifdef CONFIG_BLK_DEV_FD
+/* #ifdef CONFIG_BLK_DEV_FD */
+#if 0
        if (MAJOR(ROOT_DEV) == FLOPPY_MAJOR) {
                /* rd_doload is 2 for a dual initrd/ramload setup */
                if (rd_doload==2) {

cd to your /usr/src/linux-... and run patch -p0 < comment_floppy.patch
It should fix the _specific_ issue. It might not fix the root cause, however.

-- 
Andrey Vul

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

Re: [gentoo-user] Howto erase the "Insert root floppy and press enter" item before the kernel panic?

[David Wei]

Thanks Andrey, that patch works , my test kernel dose not ask for the floppy before the panic. Just by the way,dose that mean I cannot use floppy drive on this box?

Thanks again!!

On Fri, 10 Oct 2008 23:06:09 -0400
"Andrey Vul" <andrey.vul@gmail.com> wrote:

> On Fri, Oct 10, 2008 at 10:33 PM, David Wei <davidwei@newbread.tj.cn> wrote:
> > Sorry, I forgot that file .
> > the .config is in the attachment this time.
> > Thank you .
> >
> > On Fri, 10 Oct 2008 10:05:36 -0400
> > "Andrey Vul" <andrey.vul@gmail.com> wrote:
> >
> >> 2008/10/10 David Wei <davidwei@newbread.tj.cn>:
> >> > Hi,
> >> > I am trying kexec with "kernel panic reboot" cause i have to manage my server remotely.
> >> > the "kernel panic reboot" (http://gentoo-wiki.com/TIP_Kernel_Panic_Reboot) has beening working so good so far for the regular kernel panic.However,sometimes when i were missed some file system items,the booking process would ask me:
> >> > "VFS: Unable to mount root fs via NFS,trying floppy
> >> > Insert root floppy and Press Enter."
> >> > And the system hungup there waiting for my Enter.
> >> > How can I remove this item from the booting process and panic directly so that it can reboot? Besides,I want to keep the NFS service.
> >> > Thank you in advance.
> >> I'm guessing that this is due to the floppy being compiled into the
> >> emergency kernel.
> >> In any case, can you post your .config for the emergency kernel?
> >>
> 
> Nothing in the .config looks suspicious.
> It looks like it's inevitable that kernel patching will be needed, at
> least, using the preprocessor to "hide" the floppy code.
> Try this (it comments out floppy support which happens after NFS support):
> comment_floppy.patch
> --- init/do_mounts.c    2008-04-16 22:49:44.000000000 -0400
> +++ init/do_mounts2.c   2008-10-10 23:03:06.867876561 -0400
> @@ -308,7 +308,8 @@
>                 ROOT_DEV = Root_FD0;
>         }
>  #endif
> -#ifdef CONFIG_BLK_DEV_FD
> +/* #ifdef CONFIG_BLK_DEV_FD */
> +#if 0
>         if (MAJOR(ROOT_DEV) == FLOPPY_MAJOR) {
>                 /* rd_doload is 2 for a dual initrd/ramload setup */
>                 if (rd_doload==2) {
> 
> cd to your /usr/src/linux-... and run patch -p0 < comment_floppy.patch
> It should fix the _specific_ issue. It might not fix the root cause, however.
> 
> -- 
> Andrey Vul
> 
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
> A: Top-posting.
> Q: What is the most annoying thing in e-mail?
> 


-------------------------------
魏亮 David Wei

您可以通过下面的方式和我联系：
MSN: inadavid@hotmail.com
Gtalk: inadavid@gmail.com
Email: davidwei@newbread.tj.cn

Re: [gentoo-user] Howto erase the "Insert root floppy and press enter" item before the kernel panic?

[Andrey Vul]

On Sat, Oct 11, 2008 at 12:00 AM, David Wei <davidwei@newbread.tj.cn> wrote:
> Thanks Andrey, that patch works , my test kernel dose not ask for the floppy before the panic. Just by the way,dose that mean I cannot use floppy drive on this box?
>
You can use the floppy drive, but the kernel cannot run init / use
initrd from a floppy (i.e. you are not allowed to use root=/dev/fd0 or
initrd=/dev/fd0). This is because the floppy is fallback code if the
NFS mount of / fails.

But this is Gentoo, you make your own kernel (hopefully), and never
have to worry about initrd.

/ and /dev/root are used interchangeably, for readabilty, similar to /
and /dev/hdaX.

All I did was comment out the floppy fallback code.

This is how mount_root was originally written:
If CONFIG_ROOT_NFS is defined
    If root device is NFS
        If the NFS root mounted
            Return
        Print message "VFS: Unable to mount root fs via NFS, trying floppy.\n"
        Set root device as floppy disk 0
If CONFIG_BLK_DEV_FD (floppy disk) is defined
    If the root device is a floppy
        If dual initrd/ramload is enabled
            If the first partition of the ramdisk image could be
loaded into memory
                Set the root device as a ramdisk
                Set the root device name as null
            Else
                Prompt for root floppy
If CONFIG_BLOCK is defined
    Create a device named "/dev/root" with the major & minor modes
equal to the root device
    Mount "/dev/root" with root device mountflags

If you want more detail, you should post to lkml.

All I have done was replace the following line:
If CONFIG_BLK_DEV_FD (floppy disk) is defined
with
If false

}
> Thanks again!!
No problem.
In reality, the fix was simple.
All I did was grep the source tree for the exact string (grep -R "VFS:
Unable to mount root fs via NFS, trying floppy" .
)
Then open up vim (or emacs or nano), find the line, and add an #if 0
... #endif block where needed.
>
> On Fri, 10 Oct 2008 23:06:09 -0400
> "Andrey Vul" <andrey.vul@gmail.com> wrote:
>
>> On Fri, Oct 10, 2008 at 10:33 PM, David Wei <davidwei@newbread.tj.cn> wrote:
>> > Sorry, I forgot that file .
>> > the .config is in the attachment this time.
>> > Thank you .
>> >
>> > On Fri, 10 Oct 2008 10:05:36 -0400
>> > "Andrey Vul" <andrey.vul@gmail.com> wrote:
>> >
>> >> 2008/10/10 David Wei <davidwei@newbread.tj.cn>:
>> >> > Hi,
>> >> > I am trying kexec with "kernel panic reboot" cause i have to manage my server remotely.
>> >> > the "kernel panic reboot" (http://gentoo-wiki.com/TIP_Kernel_Panic_Reboot) has beening working so good so far for the regular kernel panic.However,sometimes when i were missed some file system items,the booking process would ask me:
>> >> > "VFS: Unable to mount root fs via NFS,trying floppy
>> >> > Insert root floppy and Press Enter."
>> >> > And the system hungup there waiting for my Enter.
>> >> > How can I remove this item from the booting process and panic directly so that it can reboot? Besides,I want to keep the NFS service.
>> >> > Thank you in advance.
>> >> I'm guessing that this is due to the floppy being compiled into the
>> >> emergency kernel.
>> >> In any case, can you post your .config for the emergency kernel?
>> >>
>>
>> Nothing in the .config looks suspicious.
>> It looks like it's inevitable that kernel patching will be needed, at
>> least, using the preprocessor to "hide" the floppy code.
>> Try this (it comments out floppy support which happens after NFS support):
>> comment_floppy.patch
>> --- init/do_mounts.c    2008-04-16 22:49:44.000000000 -0400
>> +++ init/do_mounts2.c   2008-10-10 23:03:06.867876561 -0400
>> @@ -308,7 +308,8 @@
>>                 ROOT_DEV = Root_FD0;
>>         }
>>  #endif
>> -#ifdef CONFIG_BLK_DEV_FD
>> +/* #ifdef CONFIG_BLK_DEV_FD */
>> +#if 0
>>         if (MAJOR(ROOT_DEV) == FLOPPY_MAJOR) {
>>                 /* rd_doload is 2 for a dual initrd/ramload setup */
>>                 if (rd_doload==2) {
>>
>> cd to your /usr/src/linux-... and run patch -p0 < comment_floppy.patch
>> It should fix the _specific_ issue. It might not fix the root cause, however.
>>
>> --
>> Andrey Vul
>>
>> A: Because it messes up the order in which people normally read text.
>> Q: Why is top-posting such a bad thing?
>> A: Top-posting.
>> Q: What is the most annoying thing in e-mail?
>>
>
>
> -------------------------------
> 魏亮 David Wei
>
> 您可以通过下面的方式和我联系：
> MSN: inadavid@hotmail.com
> Gtalk: inadavid@gmail.com
> Email: davidwei@newbread.tj.cn
>
>



-- 
Andrey Vul

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

Re: [gentoo-user] Howto erase the "Insert root floppy and press enter" item before the kernel panic?

[David Wei]

I'm gonna do that next time before I post here.
thanks Andrey.

On Sat, 11 Oct 2008 02:08:56 -0400
"Andrey Vul" <andrey.vul@gmail.com> wrote:

> On Sat, Oct 11, 2008 at 12:00 AM, David Wei <davidwei@newbread.tj.cn> wrote:
> > Thanks Andrey, that patch works , my test kernel dose not ask for the floppy before the panic. Just by the way,dose that mean I cannot use floppy drive on this box?
> >
> You can use the floppy drive, but the kernel cannot run init / use
> initrd from a floppy (i.e. you are not allowed to use root=/dev/fd0 or
> initrd=/dev/fd0). This is because the floppy is fallback code if the
> NFS mount of / fails.
> 
> But this is Gentoo, you make your own kernel (hopefully), and never
> have to worry about initrd.
> 
> / and /dev/root are used interchangeably, for readabilty, similar to /
> and /dev/hdaX.
> 
> All I did was comment out the floppy fallback code.
> 
> This is how mount_root was originally written:
> If CONFIG_ROOT_NFS is defined
>     If root device is NFS
>         If the NFS root mounted
>             Return
>         Print message "VFS: Unable to mount root fs via NFS, trying floppy.\n"
>         Set root device as floppy disk 0
> If CONFIG_BLK_DEV_FD (floppy disk) is defined
>     If the root device is a floppy
>         If dual initrd/ramload is enabled
>             If the first partition of the ramdisk image could be
> loaded into memory
>                 Set the root device as a ramdisk
>                 Set the root device name as null
>             Else
>                 Prompt for root floppy
> If CONFIG_BLOCK is defined
>     Create a device named "/dev/root" with the major & minor modes
> equal to the root device
>     Mount "/dev/root" with root device mountflags
> 
> If you want more detail, you should post to lkml.
> 
> All I have done was replace the following line:
> If CONFIG_BLK_DEV_FD (floppy disk) is defined
> with
> If false
> 
> }
> > Thanks again!!
> No problem.
> In reality, the fix was simple.
> All I did was grep the source tree for the exact string (grep -R "VFS:
> Unable to mount root fs via NFS, trying floppy" .
> )
> Then open up vim (or emacs or nano), find the line, and add an #if 0
> ... #endif block where needed.
> >
> > On Fri, 10 Oct 2008 23:06:09 -0400
> > "Andrey Vul" <andrey.vul@gmail.com> wrote:
> >
> >> On Fri, Oct 10, 2008 at 10:33 PM, David Wei <davidwei@newbread.tj.cn> wrote:
> >> > Sorry, I forgot that file .
> >> > the .config is in the attachment this time.
> >> > Thank you .
> >> >
> >> > On Fri, 10 Oct 2008 10:05:36 -0400
> >> > "Andrey Vul" <andrey.vul@gmail.com> wrote:
> >> >
> >> >> 2008/10/10 David Wei <davidwei@newbread.tj.cn>:
> >> >> > Hi,
> >> >> > I am trying kexec with "kernel panic reboot" cause i have to manage my server remotely.
> >> >> > the "kernel panic reboot" (http://gentoo-wiki.com/TIP_Kernel_Panic_Reboot) has beening working so good so far for the regular kernel panic.However,sometimes when i were missed some file system items,the booking process would ask me:
> >> >> > "VFS: Unable to mount root fs via NFS,trying floppy
> >> >> > Insert root floppy and Press Enter."
> >> >> > And the system hungup there waiting for my Enter.
> >> >> > How can I remove this item from the booting process and panic directly so that it can reboot? Besides,I want to keep the NFS service.
> >> >> > Thank you in advance.
> >> >> I'm guessing that this is due to the floppy being compiled into the
> >> >> emergency kernel.
> >> >> In any case, can you post your .config for the emergency kernel?
> >> >>
> >>
> >> Nothing in the .config looks suspicious.
> >> It looks like it's inevitable that kernel patching will be needed, at
> >> least, using the preprocessor to "hide" the floppy code.
> >> Try this (it comments out floppy support which happens after NFS support):
> >> comment_floppy.patch
> >> --- init/do_mounts.c    2008-04-16 22:49:44.000000000 -0400
> >> +++ init/do_mounts2.c   2008-10-10 23:03:06.867876561 -0400
> >> @@ -308,7 +308,8 @@
> >>                 ROOT_DEV = Root_FD0;
> >>         }
> >>  #endif
> >> -#ifdef CONFIG_BLK_DEV_FD
> >> +/* #ifdef CONFIG_BLK_DEV_FD */
> >> +#if 0
> >>         if (MAJOR(ROOT_DEV) == FLOPPY_MAJOR) {
> >>                 /* rd_doload is 2 for a dual initrd/ramload setup */
> >>                 if (rd_doload==2) {
> >>
> >> cd to your /usr/src/linux-... and run patch -p0 < comment_floppy.patch
> >> It should fix the _specific_ issue. It might not fix the root cause, however.
> >>
> >> --
> >> Andrey Vul
> >>
> >> A: Because it messes up the order in which people normally read text.
> >> Q: Why is top-posting such a bad thing?
> >> A: Top-posting.
> >> Q: What is the most annoying thing in e-mail?
> >>
> >
> >
> > -------------------------------
> > 魏亮 David Wei
> >
> > 您可以通过下面的方式和我联系：
> > MSN: inadavid@hotmail.com
> > Gtalk: inadavid@gmail.com
> > Email: davidwei@newbread.tj.cn
> >
> >
> 
> 
> 
> -- 
> Andrey Vul
> 
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
> A: Top-posting.
> Q: What is the most annoying thing in e-mail?


-------------------------------
魏亮 David Wei

您可以通过下面的方式和我联系：
MSN: inadavid@hotmail.com
Gtalk: inadavid@gmail.com
Email: davidwei@newbread.tj.cn

Re: [gentoo-user] Howto erase the "Insert root floppy and press enter" item before the kernel panic?

[David Relson]

On Fri, 10 Oct 2008 23:06:09 -0400
Andrey Vul wrote:

> On Fri, Oct 10, 2008 at 10:33 PM, David Wei <davidwei@newbread.tj.cn>
> wrote:
> > Sorry, I forgot that file .
> > the .config is in the attachment this time.
> > Thank you .
> >
> > On Fri, 10 Oct 2008 10:05:36 -0400
> > "Andrey Vul" <andrey.vul@gmail.com> wrote:
> >
> >> 2008/10/10 David Wei <davidwei@newbread.tj.cn>:
> >> > Hi,
> >> > I am trying kexec with "kernel panic reboot" cause i have to
> >> > manage my server remotely. the "kernel panic
> >> > reboot" (http://gentoo-wiki.com/TIP_Kernel_Panic_Reboot) has
> >> > beening working so good so far for the regular kernel
> >> > panic.However,sometimes when i were missed some file system
> >> > items,the booking process would ask me: "VFS: Unable to mount
> >> > root fs via NFS,trying floppy Insert root floppy and Press
> >> > Enter." And the system hungup there waiting for my Enter. How
> >> > can I remove this item from the booting process and panic
> >> > directly so that it can reboot? Besides,I want to keep the NFS
> >> > service. Thank you in advance.
> >> I'm guessing that this is due to the floppy being compiled into the
> >> emergency kernel.
> >> In any case, can you post your .config for the emergency kernel?
> >>
> 
> Nothing in the .config looks suspicious.
> It looks like it's inevitable that kernel patching will be needed, at
> least, using the preprocessor to "hide" the floppy code.
> Try this (it comments out floppy support which happens after NFS
> support): comment_floppy.patch
> --- init/do_mounts.c    2008-04-16 22:49:44.000000000 -0400
> +++ init/do_mounts2.c   2008-10-10 23:03:06.867876561 -0400
> @@ -308,7 +308,8 @@
>                 ROOT_DEV = Root_FD0;
>         }
>  #endif
> -#ifdef CONFIG_BLK_DEV_FD
> +/* #ifdef CONFIG_BLK_DEV_FD */
> +#if 0
>         if (MAJOR(ROOT_DEV) == FLOPPY_MAJOR) {
>                 /* rd_doload is 2 for a dual initrd/ramload setup */
>                 if (rd_doload==2) {
> 
> cd to your /usr/src/linux-... and run patch -p0 < comment_floppy.patch
> It should fix the _specific_ issue. It might not fix the root cause,
> however.
> 
> -- 
> Andrey Vul

Looking in do_mounts.c, the code that generates the message is:

  #ifdef CONFIG_ROOT_NFS
    if (MAJOR(ROOT_DEV) == UNNAMED_MAJOR) {
      if (mount_nfs_root())
        return;

      printk(KERN_ERR "VFS: Unable to mount root fs via NFS, trying floppy.\n"); 
      ROOT_DEV = Root_FD0;
    }
  #endif

Looking at the .config file, I see "CONFIG_ROOT_NFS=y".  Since the
message is being printed, we know that 

  if (MAJOR(ROOT_DEV) == UNNAMED_MAJOR)

is true which wmeans that the

  if (MAJOR(ROOT_DEV) == FLOPPY_MAJOR)

is false, i.e. the change to "#if 0" looks to be incorrect.

Perhaps "CONFIG_ROOT_NFS=y" in .config is the root cause.  I'd suggest
changing the .config.

HTH,

David

Re: [gentoo-user] Howto erase the "Insert root floppy and press enter" item before the kernel panic?

[Andrey Vul]

On Sat, Oct 11, 2008 at 8:01 AM, David Relson <relson@osagesoftware.com> wrote:
> On Fri, 10 Oct 2008 23:06:09 -0400
> Andrey Vul wrote:
>
>> On Fri, Oct 10, 2008 at 10:33 PM, David Wei <davidwei@newbread.tj.cn>
>> wrote:
>> > Sorry, I forgot that file .
>> > the .config is in the attachment this time.
>> > Thank you .
>> >
>> > On Fri, 10 Oct 2008 10:05:36 -0400
>> > "Andrey Vul" <andrey.vul@gmail.com> wrote:
>> >
>> >> 2008/10/10 David Wei <davidwei@newbread.tj.cn>:
>> >> > Hi,
>> >> > I am trying kexec with "kernel panic reboot" cause i have to
>> >> > manage my server remotely. the "kernel panic
>> >> > reboot" (http://gentoo-wiki.com/TIP_Kernel_Panic_Reboot) has
>> >> > beening working so good so far for the regular kernel
>> >> > panic.However,sometimes when i were missed some file system
>> >> > items,the booking process would ask me: "VFS: Unable to mount
>> >> > root fs via NFS,trying floppy Insert root floppy and Press
>> >> > Enter." And the system hungup there waiting for my Enter. How
>> >> > can I remove this item from the booting process and panic
>> >> > directly so that it can reboot? Besides,I want to keep the NFS
>> >> > service. Thank you in advance.
>> >> I'm guessing that this is due to the floppy being compiled into the
>> >> emergency kernel.
>> >> In any case, can you post your .config for the emergency kernel?
>> >>
>>
>> Nothing in the .config looks suspicious.
>> It looks like it's inevitable that kernel patching will be needed, at
>> least, using the preprocessor to "hide" the floppy code.
>> Try this (it comments out floppy support which happens after NFS
>> support): comment_floppy.patch
>> --- init/do_mounts.c    2008-04-16 22:49:44.000000000 -0400
>> +++ init/do_mounts2.c   2008-10-10 23:03:06.867876561 -0400
>> @@ -308,7 +308,8 @@
>>                 ROOT_DEV = Root_FD0;
>>         }
>>  #endif
>> -#ifdef CONFIG_BLK_DEV_FD
>> +/* #ifdef CONFIG_BLK_DEV_FD */
>> +#if 0
>>         if (MAJOR(ROOT_DEV) == FLOPPY_MAJOR) {
>>                 /* rd_doload is 2 for a dual initrd/ramload setup */
>>                 if (rd_doload==2) {
>>
>> cd to your /usr/src/linux-... and run patch -p0 < comment_floppy.patch
>> It should fix the _specific_ issue. It might not fix the root cause,
>> however.
>>
>> --
>> Andrey Vul
>
> Looking in do_mounts.c, the code that generates the message is:
>
>  #ifdef CONFIG_ROOT_NFS
>    if (MAJOR(ROOT_DEV) == UNNAMED_MAJOR) {
>      if (mount_nfs_root())
>        return;
>
>      printk(KERN_ERR "VFS: Unable to mount root fs via NFS, trying floppy.\n");
>      ROOT_DEV = Root_FD0;
>    }
>  #endif
>
> Looking at the .config file, I see "CONFIG_ROOT_NFS=y".  Since the
> message is being printed, we know that
>
>  if (MAJOR(ROOT_DEV) == UNNAMED_MAJOR)
>
> is true which wmeans that the
>
>  if (MAJOR(ROOT_DEV) == FLOPPY_MAJOR)
>
> is false, i.e. the change to "#if 0" looks to be incorrect.
>
> Perhaps "CONFIG_ROOT_NFS=y" in .config is the root cause.  I'd suggest
> changing the .config.
He has explicity mentioned that his root device is NFS. You have
misinterpreted the code. The floppy event only occurs *if*
mount_nfs_root() failed.
It's false from the start, but becomes true when NFS mount-root failed.



-- 
Andrey Vul

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

Re: [gentoo-user] Howto erase the "Insert root floppy and press enter" item before the kernel panic?

[David Relson]

On Sat, 11 Oct 2008 13:23:10 -0400
Andrey Vul wrote:

> On Sat, Oct 11, 2008 at 8:01 AM, David Relson
> <relson@osagesoftware.com> wrote:
> > On Fri, 10 Oct 2008 23:06:09 -0400
> > Andrey Vul wrote:
> >
> >> On Fri, Oct 10, 2008 at 10:33 PM, David Wei
> >> <davidwei@newbread.tj.cn> wrote:
> >> > Sorry, I forgot that file .
> >> > the .config is in the attachment this time.
> >> > Thank you .
> >> >
> >> > On Fri, 10 Oct 2008 10:05:36 -0400
> >> > "Andrey Vul" <andrey.vul@gmail.com> wrote:
> >> >
> >> >> 2008/10/10 David Wei <davidwei@newbread.tj.cn>:
> >> >> > Hi,
> >> >> > I am trying kexec with "kernel panic reboot" cause i have to
> >> >> > manage my server remotely. the "kernel panic
> >> >> > reboot" (http://gentoo-wiki.com/TIP_Kernel_Panic_Reboot) has
> >> >> > beening working so good so far for the regular kernel
> >> >> > panic.However,sometimes when i were missed some file system
> >> >> > items,the booking process would ask me: "VFS: Unable to mount
> >> >> > root fs via NFS,trying floppy Insert root floppy and Press
> >> >> > Enter." And the system hungup there waiting for my Enter. How
> >> >> > can I remove this item from the booting process and panic
> >> >> > directly so that it can reboot? Besides,I want to keep the NFS
> >> >> > service. Thank you in advance.
> >> >> I'm guessing that this is due to the floppy being compiled into
> >> >> the emergency kernel.
> >> >> In any case, can you post your .config for the emergency kernel?
> >> >>
> >>
> >> Nothing in the .config looks suspicious.
> >> It looks like it's inevitable that kernel patching will be needed,
> >> at least, using the preprocessor to "hide" the floppy code.
> >> Try this (it comments out floppy support which happens after NFS
> >> support): comment_floppy.patch
> >> --- init/do_mounts.c    2008-04-16 22:49:44.000000000 -0400
> >> +++ init/do_mounts2.c   2008-10-10 23:03:06.867876561 -0400
> >> @@ -308,7 +308,8 @@
> >>                 ROOT_DEV = Root_FD0;
> >>         }
> >>  #endif
> >> -#ifdef CONFIG_BLK_DEV_FD
> >> +/* #ifdef CONFIG_BLK_DEV_FD */
> >> +#if 0
> >>         if (MAJOR(ROOT_DEV) == FLOPPY_MAJOR) {
> >>                 /* rd_doload is 2 for a dual initrd/ramload setup
> >> */ if (rd_doload==2) {
> >>
> >> cd to your /usr/src/linux-... and run patch -p0 <
> >> comment_floppy.patch It should fix the _specific_ issue. It might
> >> not fix the root cause, however.
> >>
> >> --
> >> Andrey Vul
> >
> > Looking in do_mounts.c, the code that generates the message is:
> >
> >  #ifdef CONFIG_ROOT_NFS
> >    if (MAJOR(ROOT_DEV) == UNNAMED_MAJOR) {
> >      if (mount_nfs_root())
> >        return;
> >
> >      printk(KERN_ERR "VFS: Unable to mount root fs via NFS, trying
> > floppy.\n"); ROOT_DEV = Root_FD0;
> >    }
> >  #endif
> >
> > Looking at the .config file, I see "CONFIG_ROOT_NFS=y".  Since the
> > message is being printed, we know that
> >
> >  if (MAJOR(ROOT_DEV) == UNNAMED_MAJOR)
> >
> > is true which wmeans that the
> >
> >  if (MAJOR(ROOT_DEV) == FLOPPY_MAJOR)
> >
> > is false, i.e. the change to "#if 0" looks to be incorrect.
> >
> > Perhaps "CONFIG_ROOT_NFS=y" in .config is the root cause.  I'd
> > suggest changing the .config.
> He has explicity mentioned that his root device is NFS. You have
> misinterpreted the code. The floppy event only occurs *if*
> mount_nfs_root() failed.
> It's false from the start, but becomes true when NFS mount-root
> failed.

You are correct.  I hadn't re-read the orginal post and didn't know the
use of NFS and I didn't look deeply enough into the code to learn that
Root_FD0 relates to FLOPPY_MAJOR.