linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Ethan Blanton <eblanton@cs.ohiou.edu>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Internal airport card not working? (2.4.6-benh)
Date: Sun, 15 Jul 2001 17:04:46 -0400	[thread overview]
Message-ID: <20010715170446.A20595@localhost.localdomain> (raw)
In-Reply-To: <20010715201118.9038@smtp.wanadoo.fr>; from benh@kernel.crashing.org on Sun, Jul 15, 2001 at 10:11:18PM +0200


Benjamin Herrenschmidt spake unto us the following wisdom:
> >Removing the driver stack (airport, orinoco, hermes) and reinserting
> >the modules fixes the problem for me...  Until I suspend and resume a
> >few times, at which point I'll have to remove/reinsert again.
> >
> >I know that's not a *fix*, but it should get you working again in the
> >meantime.  :-)
> >Ethan
>
> Interesting. Do you see any error message in the dmesh log ?

Not that I see...  I see nothing in my log until the removal and
reinsertion of the drivers, at which point I just see a 'su' and then
the driver banner messages.

Everything *acts* like it's working, it just doesn't.  If that makes
sense.  :-)
Ethan

--
If I've told you once, I've told you once
And once is all that you needed.
		-- The Refreshments, "Carefree"

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2001-07-15 21:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-14 17:02 Internal airport card not working? (2.4.6-benh) Jeremy Radlow
2001-07-14 17:12 ` Ethan Blanton
2001-07-15 20:11   ` Benjamin Herrenschmidt
2001-07-15 21:04     ` Ethan Blanton [this message]
2001-07-15 21:08       ` Benjamin Herrenschmidt
2001-07-15 21:15         ` Ethan Blanton
2001-08-19  0:46 ` Internal airport card works (was Re: Internal airport card not working? (2.4.6-benh)) Jeremy Radlow

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=20010715170446.A20595@localhost.localdomain \
    --to=eblanton@cs.ohiou.edu \
    --cc=benh@kernel.crashing.org \
    --cc=linuxppc-dev@lists.linuxppc.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).