From: Ethan Blanton <eblanton@cs.ohiou.edu>
To: Derrik Pates <dpates@dsdk12.net>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Airport driver sleep problem and solution
Date: Mon, 20 Aug 2001 11:47:42 -0400 [thread overview]
Message-ID: <20010820114742.J22957@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.33.0108200926520.27201-100000@andromeda.dsdk12.net>; from dpates@dsdk12.net on Mon, Aug 20, 2001 at 09:38:15AM -0600
[-- Attachment #1: Type: text/plain, Size: 1216 bytes --]
Derrik Pates spake unto us the following wisdom:
> I recently found that, if the Airport card in an iBook I've been running
> Linux on was not brought "up" at the time the system was put to sleep (by
> putting the lid down), after bringing it back out of sleep, it would no
> longer correctly operate until the driver was removed and reloaded -
> ifconfig would receive an ENODEV error, and iwconfig would report that the
> device had no wireless extensions. I found that the problem is on line 179
> of linux/drivers/net/wireless/airport.c (v0.06f, in 2.4.9-benh0), where
> the driver only calls "netif_device_attach" if card->open is TRUE - but it
> unconditionally calls "netif_device_detach" in the PBOOK_SLEEP_NOW case.
> Line 179 should be changed from "else if (card->open)" to just "else", so
> that the network device is "reattached" to the networking subsystem.
Spectacular! I've had this trouble as well, and I solved it my just
leaving my Airport card configured all the time, regardless of whether
I was on a network or not. I'm glad to see a real fix. :-)
Ethan
--
If I've told you once, I've told you once
And once is all that you needed.
-- The Refreshments, "Carefree"
[-- Attachment #2: Type: application/pgp-signature, Size: 0 bytes --]
prev parent reply other threads:[~2001-08-20 15:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-20 15:38 Airport driver sleep problem and solution Derrik Pates
2001-08-20 15:47 ` Ethan Blanton [this message]
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=20010820114742.J22957@localhost.localdomain \
--to=eblanton@cs.ohiou.edu \
--cc=dpates@dsdk12.net \
--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).