public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Andrey Vul" <andrey.vul@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Howto erase the "Insert root floppy and press enter" item before the kernel panic?
Date: Fri, 10 Oct 2008 23:06:09 -0400	[thread overview]
Message-ID: <e38d12ff0810102006g6d72b2c0sb0bd5181ab9535b8@mail.gmail.com> (raw)
In-Reply-To: <20081011113336.e42519a1.davidwei@newbread.tj.cn>

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?



  reply	other threads:[~2008-10-11  3:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-10  8:34 [gentoo-user] Howto erase the "Insert root floppy and press enter" item before the kernel panic? David Wei
2008-10-10 14:05 ` Andrey Vul
2008-10-11  2:33   ` David Wei
2008-10-11  3:06     ` Andrey Vul [this message]
2008-10-11  4:00       ` David Wei
2008-10-11  6:08         ` Andrey Vul
2008-10-11  6:30           ` David Wei
2008-10-11 12:01       ` David Relson
2008-10-11 17:23         ` Andrey Vul
2008-10-12  0:21           ` David Relson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e38d12ff0810102006g6d72b2c0sb0bd5181ab9535b8@mail.gmail.com \
    --to=andrey.vul@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox