public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andries.Brouwer@cwi.nl
To: hpa@zytor.com, linux-kernel@vger.kernel.org
Subject: Re: zImage not supported for 2.2.20?
Date: Fri, 28 Dec 2001 21:06:25 GMT	[thread overview]
Message-ID: <UTC200112282106.VAA133464.aeb@cwi.nl> (raw)

    From: "H. Peter Anvin" <hpa@zytor.com>

    > Unfortunately, I need to use zImage on my Tecra.  I know that zImage is
    > old, and I've heard that support for it will eventually be withdrawn,
    > but I don't really have much alternative right now unless there is
    > a patch which works around the Tecra's buggy A20 handling.

    Oh, by the way, the "I need to use zImage on my Tecra" thing is making
    it work by the use of voodoo.  It's rather unfortunate it worked on
    some systems -- it's going to fail randomly on you anyway; it's just a
    matter of which way the timings and cache items get jerked around.

    I have asked Alan for more details on the workaround, but perhaps the
    thing to do is to backport the latest 2.4 A20 code back to 2.2 and see
    if that solves the *real* problem, so bzImage works.

    I don't think there is any reason to believe zImage doesn't work
    unless bzImage works on your system.

I my A20 writeup (http://www.win.tue.nl/~aeb/linux/kbd/A20.html) I wrote:

------------------------------------------------------------------------
Jens Maurer reported in 1996 on boot problems with a bzImage kernel: 

    On the Toshiba laptop, the first two bytes at 0x100000 are incorrect
    and identical to those from address 0x000000 (which was an alias for
    0x100000 before the A20 gate enable). At a second read from 0x100000
    immediately afterwards, the correct memory content is returned.
    Asus P55TP5XE boards (Triton I chipset) show quite the same problem,
    but there, only the first byte is incorrect and booting bzImage kernels
    works fine. To me, this looks like some buffer or cache coherency
    problem although I think that caches are organized in at least 16
    byte cache lines. ... This exact same problem reportedly also exists
    on Fujitsu 555T (report from Andrea Caltroni) laptop and Compudyne
    Pentium 60 (report from David Kerr) desktop computers. 

He gives a patch, and adds "Unfortunately, Philip Hands reports that
the above patch makes some people with other non-laptop computers unable
to boot." 

Using zImage instead of bzImage avoids the problem (since zImage is not
loaded high). Debian has distributed special Tecra boot floppies for a while.
Later it was found out that these laptops just have an incredibly slow
keyboard controller and that all is fine with a larger timeout. 
------------------------------------------------------------------------

Is this inaccurate?

Andries

             reply	other threads:[~2001-12-28 21:06 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-28 21:06 Andries.Brouwer [this message]
2001-12-28 21:55 ` zImage not supported for 2.2.20? H. Peter Anvin
2001-12-28 23:57 ` Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2001-12-29  0:01 Andries.Brouwer
2001-12-29  0:17 ` H. Peter Anvin
2001-12-29  0:20 ` H. Peter Anvin
2001-12-28 10:18 Roy Hills
2001-12-28 12:12 ` Matthias Andree
2001-12-28 13:11 ` Roy Hills
2001-12-28 13:35   ` Matthias Andree
2001-12-28 14:32   ` Petri Kaukasoina
2001-12-28 20:13     ` Wolfgang Erig
2001-12-29  2:23       ` H. Peter Anvin
2002-01-01 15:16         ` Wolfgang Erig
2001-12-28 17:44   ` Roy Hills
2001-12-28 18:19     ` Alan Cox
2001-12-28 20:36       ` Petri Kaukasoina
2001-12-29  2:25         ` H. Peter Anvin
2001-12-29  2:58           ` Alan Cox
2001-12-29 11:01           ` Petri Kaukasoina
2001-12-28 18:36     ` H. Peter Anvin
2001-12-28 19:04       ` Alan Cox
2001-12-28 18:42     ` H. Peter Anvin
2001-12-31  9:12     ` Roy Hills
2002-01-02  0:54       ` H. Peter Anvin
2001-12-31 12:16     ` Roy Hills
2001-12-31 13:06       ` Petri Kaukasoina

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=UTC200112282106.VAA133464.aeb@cwi.nl \
    --to=andries.brouwer@cwi.nl \
    --cc=hpa@zytor.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox