linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Norman Diamond" <ndiamond@wta.att.ne.jp>
To: "Russell King" <rmk@arm.linux.org.uk>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: Trying to run 2.6.0-test3
Date: Fri, 15 Aug 2003 21:39:07 +0900	[thread overview]
Message-ID: <0d7c01c3632a$668da140$1aee4ca5@DIAMONDLX60> (raw)
In-Reply-To: 20030815111442.A12422@flint.arm.linux.org.uk

"Russell King" <rmk@arm.linux.org.uk> replied to me:

> > 1.  Although both yenta and i82365 are compiled in, my 16-bit NE2000 clone
> > isn't recognized.  If I boot kernel 2.4.19 I can use the network, if I
> > boot kernel 2.6.0 I can't find any way to use the network.  Partial output
> > of various commands and files are shown below.
>
> As a general rule, you should be using yenta not i82365.  There have
> been some historical problems when you build both into the kernel,
> so you might like to try disabling i82365.

I will do that in my next build.  For some reason I wasn't sure if yenta
would handle 16-bit cards.  But this turns out not to be necessary.  Also
the PCMCIA suggestions which Felipe Alfaro Solana suggested (the suggestions
which I intended to try) turned out not to be necessary.  The winner is the
next one:

> I don't see any sign of cardmgr starting up in your message logs,

You're right.  I started it from the command line.  It didn't recognize the
existing card, but "cardctl eject 0" followed by "cardctl insert 0" taught it.

Now the question is why cardmgr doesn't start automatically in 2.6.0-test3.
In 2.4.19, PCMCIA support was a module, for which I guess I never bothered
to change SuSE's default.  In 2.6.0-test1 since had to set all options
myself, I compiled in PCMCIA support, and it's still that way in test3.
I'll try to see if I can find the reason, though of course you might be able
to guess it instantaneously.

Thank you.

  reply	other threads:[~2003-08-15 12:42 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-15  8:11 Trying to run 2.6.0-test3 Norman Diamond
2003-08-15  8:53 ` Felipe Alfaro Solana
2003-08-15 10:00   ` Norman Diamond
2003-08-15 11:53     ` Felipe Alfaro Solana
2003-08-15 13:20       ` Norman Diamond
2003-08-15 15:02         ` Felipe Alfaro Solana
2003-08-16 13:21           ` Norman Diamond
2003-08-15 10:14 ` Russell King
2003-08-15 12:39   ` Norman Diamond [this message]
2003-08-15 13:04     ` Mikael Pettersson
2003-08-17  1:51       ` Norman Diamond
2003-08-15 16:43     ` Joshua Kwan
2003-08-15 17:06       ` Randy.Dunlap
2003-08-15 17:15         ` Russell King
2003-08-15 17:16 ` Greg KH
2003-08-16 13:20   ` Norman Diamond
2003-08-17  7:59 Norman Diamond
2003-08-17 13:33 ` Russell King
2003-08-18 10:41   ` Norman Diamond
2003-08-18 11:21     ` Russell King
2003-08-17  9:57 Norman Diamond
2003-08-17 17:25 ` Alan Cox
2003-08-18 10:35   ` Norman Diamond
2003-08-18 11:00     ` Vojtech Pavlik
2003-08-23 12:29       ` Norman Diamond
2003-08-25 14:24         ` Vojtech Pavlik
2003-08-18 11:37 John Bradford

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='0d7c01c3632a$668da140$1aee4ca5@DIAMONDLX60' \
    --to=ndiamond@wta.att.ne.jp \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk@arm.linux.org.uk \
    /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).