This bug report is being closed because we received no response to the
previous inquiry for information. Please reopen if this is still an
issue in the current Ubuntu release, Jaunty Jackalope 9.04 -
http://www.ubuntu.com/getubuntu/download. To reopen the bug, click on
the current status under the
The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the
upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would
appreciate it if you could please test this newer 2.6.27 Ubuntu kernel.
There are one of two ways you should be able to test:
1) If you are comfortable
Apologies typo - to confirm,
> iwlist scanning
retrieved no networks,
> sudo iwlist scanning
found two networks (under an older kernel or windows I can usually find
a couple more - not an issue though as I don't need to use the other
two).
--
Feisty wireless broken after update
https://bugs.l
dsiv I'm exactly the same as you (yellow light blinking) . Although I
can't see any sign of wireless in KNetworkManager (under Kubuntu that
is). It was there initially (not working connecting to any network
however) but since initial upgrade to Feisty I think I've had at least
two further upgrades
Just wondering if anyone has found any sort of solution to this?
I simply see my Netgear WG511 (v1) scanning (yellow light blinking
somewhat) with available network names displayed, but never able to
connect.
--
Feisty wireless broken after update
https://bugs.launchpad.net/bugs/105357
You recei
I can confirm that too - same behaviour as that of Jan Schmidt (I did not try
the new kernel). My card is a Netgear WG511v1 and does work without any problem
with ubuntu 6.06.1.
With feisty the card does find some open networks but is not able to connect
to any of them.
--
Feisty wireless br
I can confirm the same behavior as reported by Jan Schmidt: no firmware loading
problem and two different devices wmaster0 and wlan0.
No one is working. The latest kernel upgrade 2.6.20-16-generic didn't change
anything.
My card is ISL3890 PCMCIA that works well on the same notebook and Edgy
in
Another thing to note about this bug is that I can't see mentioned is that my
card is appearing as 2 distinct devices in the ifconfig list:
> ifconfig -a
wmaster0 IEEE 802.11g Frequency:2.412 GHz
RTS thr:off Fragment thr=2346 B
wlan0 IEEE 802.11g ESSID:""
dmidecode
** Attachment added: "dmidecode.txt"
http://librarian.launchpad.net/7563349/dmidecode.txt
--
Feisty wireless broken after update
https://bugs.launchpad.net/bugs/105357
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
-
lsusb
** Attachment added: "lsusb.txt"
http://librarian.launchpad.net/7563345/lsusb.txt
--
Feisty wireless broken after update
https://bugs.launchpad.net/bugs/105357
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bu
lspci -vv output
** Attachment added: "lspci-vv.txt"
http://librarian.launchpad.net/7563341/lspci-vv.txt
--
Feisty wireless broken after update
https://bugs.launchpad.net/bugs/105357
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubunt
iwlist scan output
** Attachment added: "iwlist.txt"
http://librarian.launchpad.net/7563340/iwlist.txt
--
Feisty wireless broken after update
https://bugs.launchpad.net/bugs/105357
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
I am having the same problem, on a Dell Latitude CPxJ. It has a PCMCIA
Prism54 card (Gigafast WF728-AEX) worked fine on Edgy.
Upon upgrading to Feisty, the card is recognized, and can scan for APs,
but does not associate.
dmesg shows:
[ 42.764000] p54: LM86 firmware
[ 43.80] wmaster0: Se
** Changed in: linux-source-2.6.20 (Ubuntu)
Sourcepackagename: network-manager => linux-source-2.6.20
--
Feisty wireless broken after update
https://bugs.launchpad.net/bugs/105357
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
I am having the same problem: Netgear WG511v1, so the prism54 chipset,
and it detects networks, but can't associate.
--
Feisty wireless broken after update
https://bugs.launchpad.net/bugs/105357
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact f
I should add that this card worked with no problems on Edgy, but has
been unable to associate since doing a clean install of Feisty.
--
Feisty wireless broken after update
https://bugs.launchpad.net/bugs/105357
You received this bug notification because you are a member of Ubuntu
Bugs, which is t
ok, my fault. De-duplicate and confirm it
Thank you for your work Peter
** This bug is no longer a duplicate of bug 90902
prism54: eeprom failed
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) => Ubuntu Kernel Team
Status: Unconfirmed => Confirmed
--
Feisty wirele
I agreed with Peter... I also believe that the issues described here are
different from Bug # 90902.
I was able to get my WG511v1 to finally connect wirelessly with WPA
using the guidance found in the following Bug Report:
https://bugs.launchpad.net/bugs/105858
although it's only a temporary sol
*** This bug is a duplicate of bug 90902 ***
https://bugs.launchpad.net/bugs/90902
I checked the firmware at http://prism54.org/fullmac.html and it is the
same as /lib/firmware/2.6.20-15-generic/isl3890 so this is definitely a
different issue.
--
Feisty wireless broken after update
https://b
*** This bug is a duplicate of bug 90902 ***
https://bugs.launchpad.net/bugs/90902
I don't believe this is a duplicate for two reasons.
I don't get an eeprom load failure:
[88098.194770] p54: LM86 firmware
I have the same loss of function for a marvell chipset using
ndiswrapper.
--
Feisty
*** This bug is a duplicate of bug 90902 ***
https://bugs.launchpad.net/bugs/90902
Thanks for the bug report. This particular bug has already been reported
into our bug tracking system, but please feel free to report any further
bugs you find.
** This bug has been marked a duplicate of bug 90
I just upgrade a laptop to feisty and am having trouble with a PCMCI
prism54 based card as well - it appears to associate with the router OK,
but no traffic gets through for DHCP negotiation (this is on an open
network - no WEP/WPA).
Setting an ESSID and IP address manually also doesn't work - iwc
I also have wireless connection problem with my WG511v1 after upgrading
from Edgy to Fiesty. In Edgy, I was able use Ndiswrapper with the
netwg511.inf driver for wireless connection with my 802.11g network
using WPA. In Fiesty, I'd to blacklist not just prism54 but also
prism54pci to just connect
I believe I am having the same problem. I also have a netgear router and
am unable to connect wirelessly. I tried removing my WEP password but
that did not help. I am new to ubuntu tho so maybe I am just doing
something wrong, but I was under the impression that the wireless
connectivity would just
I'm gonna file another bug in case my problem is a separate issue. I
will post the bug# here after I have done that.
--
Feisty wireless broken after update
https://bugs.launchpad.net/bugs/105357
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact f
Interestingly on yet another laptop (IBM T40) running Feisty which has
builtin wireless using the airo driver, I've had no issues at all.
Even more interestingly, when I plug my WG511v1 card into this working
laptop I am unable to connect which suggests either a device recognition
issue or somethi
I was prompted for for my keyring password and I don't get the firmware
load issue so your problem appears to be slightly different.
--
Feisty wireless broken after update
https://bugs.launchpad.net/bugs/105357
You received this bug notification because you are a member of Ubuntu
Bugs, which is t
Hi Peter,
I have a Netgear WG511v1 with the isl3880 chipset that uses the prism54
driver natively. I too had no problem with this card until upgrading to
Feisty on 2007-04-05. I clicked around with network-manager for a bit
and got to the System | Administration |Network dialog. This showed two
wi
WG511v1 uname -a
Linux wlittle 2.6.20-14-generic #2 SMP Mon Apr 2 20:37:49 UTC 2007 i686
GNU/Linux
--
Feisty wireless broken after update
https://bugs.launchpad.net/bugs/105357
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
u
My network is WEP 128bit.
The machine with the WG511v1 was recently built and has worked with Edgy
and Feisty until early April.
The machine with the WG511v2 was built in 2006 has worked correctly
using Etch, Edgy and Feisty until early April.
This bug suggests some udev funkiness may be involve
WG511v1
** Attachment added: "iwconfig"
http://librarian.launchpad.net/7259745/iwconfig
--
Feisty wireless broken after update
https://bugs.launchpad.net/bugs/105357
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bu
/etc/network/interfaces contains:
auto lo
iface lo inet loopback
--
Feisty wireless broken after update
https://bugs.launchpad.net/bugs/105357
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bug
WG511v1
** Attachment added: "lspci -vv"
http://librarian.launchpad.net/7259744/lspcivv
--
Feisty wireless broken after update
https://bugs.launchpad.net/bugs/105357
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bu
** Attachment added: "dmesg"
http://librarian.launchpad.net/7259743/dmesg
--
Feisty wireless broken after update
https://bugs.launchpad.net/bugs/105357
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing lis
WG511v1 - Attached daemon.log showing negotiation by network manager.
** Attachment added: "daemon.log"
http://librarian.launchpad.net/7259742/daemon.log
--
Feisty wireless broken after update
https://bugs.launchpad.net/bugs/105357
You received this bug notification because you are a member o
35 matches
Mail list logo
