All of lore.kernel.org
 help / color / mirror / Atom feed
From: pla <pla@tmok.com>
To: linux-mtd@lists.infradead.org
Subject: UnitSizeFactor != 1 ?
Date: Thu, 23 Aug 2001 17:14:48 -0400 (EDT)	[thread overview]
Message-ID: <200108232114.RAA35279@stone.tmok.com> (raw)

Okay, new odd question.  Still using a 32mb DOC2000.  Everything
works well, until...
 
I try running XFree86 4.1.0, tried the C&T driver (I have a ct65555),
the FB driver, and the VESA driver.  All produce the same results,
namely, inconsistant "really odd" errors (such as various modules
looking like invalid modules, random sig-11's, etc).  By loading
all the X-stuff into a ramdisk, I can at least get the server to
start, but it locks up within a few seconds.  If I kill the server
before the lockup, I get back to a prompt and the system still
locks up within a few seconds (sometimes so badly that magic SysRq
functions don't respond, and even when they do, it won't finish
a sync or unmount).
 
This occurs with 2.4.8, MTD snapshot 20010812, and DOC stock firmware 4.2.
 
Now, about the subject line...
 
I tried upgrading the DOC to the newer 5.0 firmware, and I get the
error "Sorry, we don't support UnitSizeFactor of != 1 yet" at boot.
 
Both of these seem like at least somewhat serious problems, but the
latter ends up leaving me without a /dev/nftl/ entry, so I consider
it the more serious of the two, thus my subject line.
 
Thank you for any advice you might offer.
 
 
 
              - Ben Despres

                 reply	other threads:[~2001-08-23 21:08 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200108232114.RAA35279@stone.tmok.com \
    --to=pla@tmok.com \
    --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 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.