From: Ollie Lho <ollie@sis.com.tw>
To: Jason Walker <jasonw@uswo.net>
Cc: MTD Mailing List <linux-mtd@lists.infradead.org>
Subject: Re: Oddities with MTD/DOC
Date: Wed, 09 May 2001 17:15:08 +0800 [thread overview]
Message-ID: <3AF90A9C.E0FE06F2@sis.com.tw> (raw)
In-Reply-To: NEBBIDMHCLDPHDHEGDMLEEHACBAA.jasonw@uswo.net
Jason Walker wrote:
>
> Just a question for you all: Have you ever had a DOC just *not* work
> anymore? After formatting/installing my software on one for about 10-20
> times, the device refuses to be recognized by the kernel. I have a stack of
> boxes that are in this state now. Do I have to do some kind of low level
> format to them? I can't even fdisk them. I would have a hard time believing
> these are all just faulty. Any insight on this?
>
It happens a lot. You got two options: 1. replace it with another,
2. wait a few days, sometimes it just come back "magically".
Ollie
next prev parent reply other threads:[~2001-05-09 9:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-08 23:38 Oddities with MTD/DOC Jason Walker
2001-05-09 9:15 ` Ollie Lho [this message]
2001-05-09 9:57 ` David Woodhouse
2001-05-09 14:14 ` Shuh C Chang
-- strict thread matches above, loose matches on Subject: below --
2001-05-09 15:16 Vadim Khamlinsky
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=3AF90A9C.E0FE06F2@sis.com.tw \
--to=ollie@sis.com.tw \
--cc=jasonw@uswo.net \
--cc=linux-mtd@lists.infradead.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