** Changed in: wpasupplicant (Ubuntu Dapper)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/47144
Title:
wpasupplicant in dapper doesn't work with madwif
I guess this bug can be closed because its hopelessly outdated?
--
wpasupplicant in dapper doesn't work with madwifi-ng
https://bugs.launchpad.net/bugs/47144
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubu
[Expired for Dapper Backports because there has been no activity for 60
days.]
--
wpasupplicant in dapper doesn't work with madwifi-ng
https://bugs.launchpad.net/bugs/47144
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs m
well, it is not possible to have a wpa_supplicant which works with both
madwifi-old and madwifi-ng. So simply backporting the version from edgy
will certainly break all installations with the version of the madwifi
driver which is shipped with dapper.
--
wpasupplicant in dapper doesn't work with
Sorry, by 'confirm' I mean 'set to "in progress"' when it works.
--
wpasupplicant in dapper doesn't work with madwifi-ng
https://launchpad.net/bugs/47144
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
backporters team, please confirm that the current feisty package will
work for dapper and either confirm or reject this bug. Thank you!
** Changed in: dapper-backports (upstream)
Status: In Progress => Needs Info
--
wpasupplicant in dapper doesn't work with madwifi-ng
https://launchpad.ne
On Fri, Jul 28, 2006 at 08:23:32AM -, Bart Verwilst wrote:
> i'm using kernel 2.6.15-25-686.
>
> [17179587.708000] new_ath_hal: module license 'Proprietary' taints kernel.
> [17179587.708000] new_ath_hal: 0.9.16.16 (AR5210, AR5211, AR5212, RF5111,
> RF5112, RF2413, RF5413)
> [17179587.86]
i'm using kernel 2.6.15-25-686.
[17179587.708000] new_ath_hal: module license 'Proprietary' taints kernel.
[17179587.708000] new_ath_hal: 0.9.16.16 (AR5210, AR5211, AR5212, RF5111,
RF5112, RF2413, RF5413)
[17179587.86] new_ath_rate_sample: 1.2 (svn 2006-06-15)
[17179587.868000] ath_pci: 0.9.4
On Thu, Jul 27, 2006 at 08:03:46PM -, Peter Frühberger wrote:
> I tried your test packages and with them WEP (yes not wpa) networking
> ist working for my Cisco Aironet Card - did not work with the default
> dapper wpasupplicant. I just came to this report because of searching
> solution.
>
>
-just a side note:
I tried your test packages and with them WEP (yes not wpa) networking
ist working for my Cisco Aironet Card - did not work with the default
dapper wpasupplicant. I just came to this report because of searching
solution.
could this version get to the current dapper updates, plea
On Fri, Jul 14, 2006 at 07:08:55AM -, John Dong wrote:
> Reinhard, were there any source changes you were meaning to make to the
> backport package?
No, there shouldn't be any patches necessary.
--
wpasupplicant in dapper doesn't work with madwifi-ng
https://launchpad.net/bugs/47144
--
ubun
On Thu, Jul 27, 2006 at 02:22:53PM -, Bart Verwilst wrote:
> I just installed the testing debs, rebooted, but still i'm not able to
> connect to WPA-secured networks. knetworkmanager stops for a while at
> 28%, and then switches back to wired connection after a minute or so.
are you sure you a
I just installed the testing debs, rebooted, but still i'm not able to connect
to WPA-secured networks. knetworkmanager stops for a while at 28%, and then
switches back to wired connection after a minute or so.
I'm having an atheros card in a macbook.
If you need any more info, please let me kno
On Thu, Jul 13, 2006 at 01:07:27PM -, John Dong wrote:
> So this should be ready to evaluate backporting, correct?
Yes, the wpasupplicant package should now be in shape for packporting to
dapper. Note that is compiled agains madiwifi-ng in dapper, but is
trivial to change to madwifi-old (just
Attached is a testing backport of wpasupplicant, compiled from Edgy with
no source changes. Please report back.
Reinhard, were there any source changes you were meaning to make to the
backport package?
** Changed in: dapper-backports (upstream)
Importance: Untriaged => Low
Status: Confi
for what it is worth, I rebuild edgy wpasupplicant on dapper and it
works.
thanks for the hints.
--
wpasupplicant in dapper doesn't work with madwifi-ng
https://launchpad.net/bugs/47144
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bug
So this should be ready to evaluate backporting, correct?
** Changed in: dapper-backports (upstream)
Status: Needs Info => Confirmed
--
wpasupplicant in dapper doesn't work with madwifi-ng
https://launchpad.net/bugs/47144
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://l
wpasupplicant in edgy has been compiled with -Dmadwifi driver backend
compiled against madwifi-ng headers. To compile against madwifi-old, you
need to adapt debian/patches/00list
** Changed in: wpasupplicant (Ubuntu)
Assignee: (unassigned) => Reinhard Tartler
Status: Needs Info => Fix
I'd like to have #51351 fixed before backporting
** Changed in: wpasupplicant (Ubuntu Dapper)
Importance: Untriaged => Medium
Status: Unconfirmed => Confirmed
--
wpasupplicant in dapper doesn't work with madwifi-ng
https://launchpad.net/bugs/47144
--
ubuntu-bugs mailing list
ubuntu-bu
Awaiting new wpasupplicant -- marking "Needs Info" in the meantime.
** Changed in: dapper-backports (upstream)
Status: Unconfirmed => Needs Info
--
wpasupplicant in dapper doesn't work with madwifi-ng
https://launchpad.net/bugs/47144
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.c
The new madwifi-ng seems to work with -Dwext, but I'm not sure if this
works with the standard ubuntu wpa_supplicant.
--
wpasupplicant in dapper doesn't work with madwifi-ng
https://launchpad.net/bugs/47144
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman
** Also affects: dapper-backports (upstream)
Importance: Untriaged
Status: Unconfirmed
--
wpasupplicant in dapper doesn't work with madwifi-ng
https://launchpad.net/bugs/47144
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
It is correct that the wpasupplicant package in dapper does not work
with madwifi-ng, mainly because the decision to include madwifi-ng is
only for some few newer cards, and because it was made very very late.
Debian has an updated wpasupplicant package prepared, which we will have
in edgy soon. w
23 matches
Mail list logo
