From: Matthew Dharm <mdharm-kernel@one-eyed-alien.net>
To: Chris Hanson <cph@zurich.ai.mit.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Booting from USB floppy?
Date: Sat, 11 Aug 2001 22:29:36 -0700 [thread overview]
Message-ID: <20010811222936.A13150@one-eyed-alien.net> (raw)
In-Reply-To: <E15VlgK-0005GO-00@trixia.ai.mit.edu>
In-Reply-To: <E15VlgK-0005GO-00@trixia.ai.mit.edu>; from cph@zurich.ai.mit.edu on Sat, Aug 11, 2001 at 11:12:52PM -0400
[-- Attachment #1: Type: text/plain, Size: 2576 bytes --]
Some people have reported limited success by placing a multi-second delay
just before the root fs is mounted, to give the USB system time to identify
and properly attach the scsi devices.
Matt
On Sat, Aug 11, 2001 at 11:12:52PM -0400, Chris Hanson wrote:
> I have been trying to build Debian 2.2 boot/root floppies for the HP
> OmniBook 500 laptop, which (in some configurations) has only a USB
> floppy drive. I've been unable to get the kernel to load the root
> floppy. These tests were done using Linux 2.4.6.
>
> At this point, I think this isn't possible without some real work in
> the kernel. I'd like to get some feedback about whether this is a
> correct deduction. To that end, here is my analysis.
>
> 1. The function mount_root() in "fs/super.c" specially detects floppy
> devices and handles them differently than other devices that might
> be specified by the "root=" parameter, such as "root=/dev/sda" in
> this case. So handling a floppy drive that appears to be a SCSI
> floppy looks like it can't be done without patching that code.
>
> 2. If that is worked around, there is a further problem: the USB
> storage driver sets up the SCSI translator asynchronously. Prior
> to this, the device "/dev/sda" doesn't exist, which means there's a
> race condition between the USB-SCSI initialization and the boot
> process accessing the root device. I discovered this by specifying
> "root=/dev/sda", and seeing that the kernel didn't initialize the
> USB floppy device before it tried to open "/dev/sda", and failed
> with a "no such device" error. So fixing this would also requiring
> synchronizing the race -- but it's not clear how you'd figure out
> that synchronization would even be needed here.
>
> Does this seem like a reasonably correct analysis of the situation?
> Is it easier than I think? Is anyone else working on booting from USB
> floppies?
>
> Please CC me to any replies, since I don't read this list.
>
> TIA,
> Chris
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Matthew Dharm Home: mdharm-usb@one-eyed-alien.net
Maintainer, Linux USB Mass Storage Driver
It's not that hard. No matter what the problem is, tell the customer
to reinstall Windows.
-- Nurse
User Friendly, 3/22/1998
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2001-08-12 5:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-12 3:12 Booting from USB floppy? Chris Hanson
2001-08-12 5:19 ` H. Peter Anvin
2001-08-12 5:29 ` Matthew Dharm [this message]
2001-08-17 3:30 ` Chris Hanson
-- strict thread matches above, loose matches on Subject: below --
2001-08-15 2:50 John Sheahan
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=20010811222936.A13150@one-eyed-alien.net \
--to=mdharm-kernel@one-eyed-alien.net \
--cc=cph@zurich.ai.mit.edu \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.