* UnitSizeFactor != 1 ?
@ 2001-08-23 21:14 pla
0 siblings, 0 replies; only message in thread
From: pla @ 2001-08-23 21:14 UTC (permalink / raw)
To: linux-mtd
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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2001-08-23 21:08 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2001-08-23 21:14 UnitSizeFactor != 1 ? pla
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox