From: M Sweger <mikesw@ns1.whiterose.net>
To: linux-kernel@vger.kernel.org
Subject: linux 2.2.19pre14 is marked as pre13, plus some config/other problems. (fwd)
Date: Mon, 26 Feb 2001 17:05:19 -0500 (EST) [thread overview]
Message-ID: <Pine.BSF.4.21.0102261704570.37304-100000@ns1.whiterose.net> (raw)
Alan,
See below for a list of problems with the linux
2.2.19pre14 patch. The errors should be apparent.
I have a Dell optiplex 333mhz Intel with a 9gig SCSI
card.
A). The version of the linux 2.2.19pre14 on 2.2.18
is compiling and saying it is pre13. Thus the
make file has the wrong version.
B). After doing "make menuconfig". The textboxes
displayed for the menu options "Processor family"
and "Maximum Physical memory" are displayed
incorrectly (half missing).
If I move the keyboard cursor arrow up and down
for each of the above menus, then the display is
redrawn with all of the missing menu options, color
and graphics. Note: I have libcurses v5.0beta1 which
didn't have problems in linux 2.2.19pre5 or earlier.
C). Errors during "make dep".
note: I have md5sum from textutils v1.22.
If my config file will help here, I can send it.
md5sum: MD5 check failed for 'isac.c'
md5sum: MD5 check failed for 'isdnl1.c'
md5sum: MD5 check failed for 'isdnl2.c'
md5sum: MD5 check failed for 'isdnl3.c'
md5sum: MD5 check failed for 'tei.c'
md5sum: MD5 check failed for 'callc.c'
md5sum: MD5 check failed for 'l3dss1.c'
md5sum: MD5 check failed for 'l3_1tr6.c'
md5sum: MD5 check failed for 'elsa.c'
md5sum: MD5 check failed for 'diva.c'
md5sum: MD5 check failed for 'sedlbauer.c'
next reply other threads:[~2001-02-26 22:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-26 22:05 M Sweger [this message]
2001-02-27 11:56 linux 2.2.19pre14 is marked as pre13, plus some config/other problems. (fwd) M Sweger
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=Pine.BSF.4.21.0102261704570.37304-100000@ns1.whiterose.net \
--to=mikesw@ns1.whiterose.net \
--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;
as well as URLs for NNTP newsgroup(s).