From: Valdis.Kletnieks@vt.edu
To: Norman Diamond <ndiamond@wta.att.ne.jp>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Tried to run 2.6.0-test1
Date: Sun, 20 Jul 2003 11:26:54 -0400 [thread overview]
Message-ID: <200307201526.h6KFQs9K003972@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Mon, 21 Jul 2003 00:03:57 +0900." <081701c34ed0$5be60070$64ee4ca5@DIAMONDLX60>
[-- Attachment #1: Type: text/plain, Size: 977 bytes --]
On Mon, 21 Jul 2003 00:03:57 +0900, Norman Diamond <ndiamond@wta.att.ne.jp> said:
> What does the thing need in order to use modules?
ftp://ftp.kernel.org/pub/linux/kernel/people/people/rusty/modules/
And read http://www.codemonkey.org.uk/post-halloween-2.5.txt for
all the OTHER stuff you might need...
> come up? By the way there are also no tones from PCMCIA during the
> boot process so I'm pretty sure it's also not recognizing my LAN card,
The 'no tones' confused me too. In 'make menuconfig', go to 'Input Device support',
select 'Misc' - this will add an entry 'PC Speaker Support'. Check that, it will add
CONFIG_INPUT_PCSPKR which should make the beeps return.
If you hit other snags, *read the post-halloween file*. Most of the gotchas are
in there already. If you do what that says, and it STILL doesn't work, feel free to
post again - the whole point of the -testX series is so we can find all the remaining
gotchas and either fix or workaround them.
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
next prev parent reply other threads:[~2003-07-20 15:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-20 15:03 Tried to run 2.6.0-test1 Norman Diamond
2003-07-20 15:26 ` Valdis.Kletnieks [this message]
2003-07-20 15:48 ` Norman Diamond
2003-07-20 16:02 ` Diego Calleja García
2003-07-20 19:20 ` Gabor MICSKO
2003-07-21 5:48 ` Norman Diamond
2003-07-21 6:23 Norman Diamond
2003-07-21 6:52 ` Brett
2003-07-21 7:06 ` Norman Diamond
2003-07-21 7:18 ` Brett
2003-07-21 10:07 ` Gene Heskett
2003-07-21 6:56 Norman Diamond
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=200307201526.h6KFQs9K003972@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=ndiamond@wta.att.ne.jp \
/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).