From: Hugh Dickins <hugh.dickins@tiscali.co.uk>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "John W. Linville" <linville@tuxdriver.com>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
linux-wireless@vger.kernel.org
Subject: Re: 2.6.31-git wireless broken
Date: Sat, 26 Sep 2009 16:33:14 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0909261631110.4336@sister.anvils> (raw)
In-Reply-To: <1253973831.5122.33.camel@johannes.local>
On Sat, 26 Sep 2009, Johannes Berg wrote:
> On Sat, 2009-09-26 at 15:00 +0200, Johannes Berg wrote:
> >
> > I'm downloading a livecd to figure out what might be going wrong.
>
> It appears that just uses
> test -d /sys/class/net/wlan0/wireless
>
> but that should be ok, unless that's actually a link now for some reason
> -- can you verify what happens there? And double-check you have
> CONFIG_WIRELESS_EXT_SYSFS please, the config you sent me did have it
> tho.
I do have CONFIG_WIRELESS_EXT_SYSFS=y,
and I do have /sys/class/net/wlan0/ containing various things,
but I don't have any /sys/class/net/wlan0/wireless with recent kernels.
Hugh
next prev parent reply other threads:[~2009-09-26 15:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-24 17:18 2.6.31-git wireless broken Hugh Dickins
2009-09-24 17:35 ` Johannes Berg
2009-09-24 18:14 ` Hugh Dickins
2009-09-24 18:23 ` Johannes Berg
2009-09-24 19:45 ` Hugh Dickins
2009-09-25 5:20 ` Johannes Berg
2009-09-25 8:06 ` Hugh Dickins
2009-09-25 8:43 ` Johannes Berg
2009-09-25 14:15 ` Hugh Dickins
2009-09-26 13:00 ` Johannes Berg
2009-09-26 14:03 ` Johannes Berg
2009-09-26 15:06 ` Sven-Haegar Koch
2009-09-26 15:33 ` Hugh Dickins [this message]
2009-09-27 11:08 ` Johannes Berg
2009-09-27 11:15 ` Johannes Berg
2009-09-26 15:31 ` Hugh Dickins
2009-09-26 15:58 ` Larry Finger
2009-09-25 8:45 ` Holger Schurig
2009-09-25 14:56 ` Christian Lamparter
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.LNX.4.64.0909261631110.4336@sister.anvils \
--to=hugh.dickins@tiscali.co.uk \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=rjw@sisk.pl \
/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