All of lore.kernel.org
 help / color / mirror / Atom feed
From: Riffer <riffer@penny.prima.de>
To: linux-wireless@vger.kernel.org
Subject: Bleeding Edge b43 dated since 30 of september no longer working & today does not even compile.
Date: Tue, 06 Oct 2009 20:52:23 +0200	[thread overview]
Message-ID: <4ACB91E7.5010405@penny.prima.de> (raw)

Hello!

The problem is described in the topic.

Symptons:

The driver gets loaded and all depending drivers too but the wireless
device does not come up (iwconfig shows nothing, "ADDRCONF(NETDEV_UP):"
does not follow in /var/log/messages after modprobing).

Any hints for me? Maybe a new functionality that has to be triggered?

I am using the bleeding drivers on a Compaq 615 Notebook having PCI ID
14e4:4315 (Broadcom) under Ubuntu 9.04 with kernel
2.6.30-02063006-generic AMD64.

Currently I am testing the bleeding edge driver nearly every day because
I am a very curious man :-) and my hope is to one day find the best
(fast and stable) wireless driver I can get for my notebook ;-)

The most stable driver at the moment (for me) is the archive from the
16th of september and as you can read here
http://forums.opensuse.org/2045067-post38.html bleeding edge had already
a failure that stopped working from 17th to 26th of september (for me)
where Larry pointed to a problem with cfg80211 (I am using WPA2).

Another problem is that the archive from today can not be compiled:

/home/riffer/bleeding/compat-wireless-2009-10-06/drivers/net/wireless/ath/main.o
In file included from
/home/riffer/bleeding/compat-wireless-2009-10-06/include/net/mac80211.h:22,
                 from
/home/riffer/bleeding/compat-wireless-2009-10-06/drivers/net/wireless/ath/ath.h:22,
                 from
/home/riffer/bleeding/compat-wireless-2009-10-06/drivers/net/wireless/ath/main.c:20:
/home/riffer/bleeding/compat-wireless-2009-10-06/include/net/cfg80211.h:1146:
Fehler: »ETHTOOL_BUSINFO_LEN« ist hier nicht deklariert (nicht in einer
Funktion)
(translation:
Error »ETHTOOL_BUSINFO_LEN« is not declared here (not in a function))

best regards

p.s.:
I am only a user and not a developer. If my posting to this mailing-list
is a mistake please tell me!!!
-- 
Riffer

             reply	other threads:[~2009-10-06 19:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-06 18:52 Riffer [this message]
2009-10-06 19:30 ` Bleeding Edge b43 dated since 30 of september no longer working & today does not even compile Gábor Stefanik
2009-10-06 21:11 ` John W. Linville
2009-10-07 18:34   ` Bleeding Edge does not compile (was Re: Bleeding Edge b43 dated since 30 of september no longer working & today does not even compile.) Riffer
2009-10-12 11:09     ` Florian Fainelli
2009-10-12 18:03       ` Riffer

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=4ACB91E7.5010405@penny.prima.de \
    --to=riffer@penny.prima.de \
    --cc=linux-wireless@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.