public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "David Cooper" <david@forcedpotato.com>
To: "Ilguiz Latypov" <ilatypov@superbt.com>
Cc: "Linux MTD" <linux-mtd@lists.infradead.org>
Subject: RE: X Windows Performance with DOC 2000
Date: Thu, 20 Jun 2002 15:41:06 -0400	[thread overview]
Message-ID: <AIEOIMKIOAAJKHJOGAEFMEEOCEAA.david@forcedpotato.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0206181008320.3554-100000@server.superbt.com>

Hello,

I have tried more and found out more.

(1) M-Systems Firmware

Strange, but true. If I use M-System's DOS-based dformat utility to load
firware version 4.2 into the DOC 2000 this prevents X from runnning from the
IDE drive.  This is true even if I boot with a kernel that has no support
for the DOC 2000.  As long as the DOC is sitting in my system (with Rev 4.2
firmware) X will not run.  I should point out that X does not cause the
system to hang in this case.

(2) nftl_format

So I bit the bullet and tried to remove all firmware (M-Systems dformat
/empty) and then do a complete low-level format with the MTD nftl_format
utility.  Then I put on top of that a ext2 root filesystem (not self
bootable of course).  This provided no improvement.  X still falls over at
the same spot.

(3) X Modules

I then was able to look at the X log file (/var/log/XFree86.0.log) and it
seemed that the point at which X fell over was when it was trying to load
the ddc module (libddc.a).  So I then mounted the entire
/usr/X11R6/lib/modules directory from the IDE drive and ran the rest from
the root filesystem on the DOC.  This allows X to get a little further
(seems to try to load a screen from the VESA BIOS).  But it still hangs,
this time after putting rubbish graphics on the screen (as in a normal
initialisation).

Question:  Why does X have trouble loading the libddc.a module from the DOC?

Thanks for you advice and suggestions thus far.

Cheers,

David Cooper


-----Original Message-----
From: linux-mtd-admin@lists.infradead.org
[mailto:linux-mtd-admin@lists.infradead.org]On Behalf Of Ilguiz Latypov
Sent: Tuesday, June 18, 2002 10:12 AM
To: David Cooper
Cc: Linux MTD
Subject: RE: X Windows Performance with DOC 2000



David,

Perhaps, running xinit command under gdb can help.  To go step-by-step
through the lines of code, a debug version of xinit would be more helpful.
I believe the gcc -g option will provide necessary debug information in
the produced executable binary.

Ilguiz

On Mon, 17 Jun 2002, David Cooper wrote:

> I tried this but, of course, the screen goes blank, system hangs and I
> can never look at the xinit.log file.


______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

  reply	other threads:[~2002-06-20 19:32 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-14  3:09 X Windows Performance with DOC 2000 David Cooper
2002-06-15 22:32 ` Charles Manning
2002-06-17 22:30   ` David Cooper
2002-06-17 22:32     ` Ilguiz Latypov
2002-06-18  0:22       ` David Cooper
2002-06-18  0:40         ` Brendan J Simon
2002-06-21 23:33           ` Christopher Fowler
2002-06-18 14:11         ` Ilguiz Latypov
2002-06-20 19:41           ` David Cooper [this message]
2002-06-20 21:59             ` David Woodhouse
2002-06-21  0:33               ` David Cooper
2002-06-21  0:39                 ` David Woodhouse
2002-06-21  5:46                   ` David Cooper
2002-06-21  7:04                     ` David Woodhouse
2002-06-26 18:30                       ` David Cooper
2002-06-26 21:28                         ` David Woodhouse
2002-06-21 13:56                     ` Ilguiz Latypov
2002-06-21 14:09                       ` cfowler
2002-06-21 14:12                         ` David Woodhouse
2002-06-21 14:28                           ` cfowler
2002-06-22  0:01                             ` Ilguiz Latypov
2002-06-22  0:15                               ` Christopher Fowler
2002-06-22  1:14                                 ` David Cooper
2002-06-22  1:11                                   ` Gonzalo Servat
2002-06-22  9:18                                 ` David Woodhouse

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=AIEOIMKIOAAJKHJOGAEFMEEOCEAA.david@forcedpotato.com \
    --to=david@forcedpotato.com \
    --cc=ilatypov@superbt.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox