this bug is old and alsmost certainly was fixed in the meantime. Please
open individual new bug reports for your wifi chipset/driver if you
still see something like this.
** Changed in: network-manager (Ubuntu)
Status: Confirmed = Invalid
--
Unable to connect to an open network,
I have the same problem.
Writing this comment connected to an open network, so it obviously
USUALLY works fine.
Earlier today tried connecting to two different open networks and both
generated the
same problems. /var/log/syslog visually looked like the first report on the
problem here.
I'm
** Changed in: network-manager (Ubuntu)
Status: Incomplete = Confirmed
--
Unable to connect to an open network, wlassistant can connect
https://bugs.launchpad.net/bugs/89092
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
Everything just works with the current released versions of 7.10 for
Ubuntu and Kubuntu.
On Nov 28, 2007 3:42 PM, Brian Murray [EMAIL PROTECTED] wrote:
al_erola - Could you please post your '/var/log/syslog' files from both
Kubuntu and Ubuntu? Thanks in advance.
--
Unable to connect to an
I am not sure that it just works for me. It is not 100% easy to roproduce
this bug, but I will try and repost.
- Mitch Golden
On Tue, 4 Dec 2007, al_erola wrote:
Everything just works with the current released versions of 7.10 for
Ubuntu and Kubuntu.
On Nov 28, 2007 3:42 PM, Brian
al_erola - Could you please post your '/var/log/syslog' files from both
Kubuntu and Ubuntu? Thanks in advance.
--
Unable to connect to an open network, wlassistant can connect
https://bugs.launchpad.net/bugs/89092
You received this bug notification because you are a member of Ubuntu
Bugs, which
The latest Gutsy networkmanager does not recognize a Broadcom wifi with
ndiswrapper and the bcmwl5.inf driver.
Dmesg shows that the driver and device are working as eth1.
I can almost work around knetworkmanager with kwlan or configuring
wpa_supplicant directly.
This driver and chipset have
On Gutsy using Ubuntu's nm-applet works perfectly well. Knetworkmanager
does not work.
Dell e1505 Broadcom wifi 1390. Ndiswrapper with bcmwl5.inf.
--
Unable to connect to an open network, wlassistant can connect
https://bugs.launchpad.net/bugs/89092
You received this bug notification because
On Sun, Sep 23, 2007 at 02:37:33PM -, Mitch Golden wrote:
As I said in the original post, it is a Broadcom 1390. I am running
the latest version of the driver, from the Dell website.
Could you please test with latest gutsy network-manager: =
0.6.5-0ubuntu15 ?
Thanks,
- Alexander
--
As I said in the original post, it is a Broadcom 1390. I am running
the latest version of the driver, from the Dell website.
dell:~ lspci -v
00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS/940GML and 945GT
Express Memory Controller Hub (rev 03)
Subsystem: Dell Unknown device
On Sun, Sep 16, 2007 at 02:18:04PM -, Mitch Golden wrote:
I just tried testing with a Live CD. (I can't install Gutsy since I use
by Dell Inspiron 6400 for production work - it has Feisty on it).
Here's the problem: when I install ndiswrapper on the machine, it
generally requires a
I just tried testing with a Live CD. (I can't install Gutsy since I use
by Dell Inspiron 6400 for production work - it has Feisty on it).
Here's the problem: when I install ndiswrapper on the machine, it
generally requires a power-cycle reboot to get the card to work. Or at
least, that's how I
Hi Mitch, do you still have this problem in Gutsy? (could you test with
a live CD perhaps?)
** Changed in: network-manager (Ubuntu)
Importance: Undecided = Low
Status: New = Incomplete
--
Unable to connect to an open network, wlassistant can connect
I still have this problem in Feisty.
--
Unable to connect to an open network, wlassistant can connect
https://bugs.launchpad.net/bugs/89092
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Hey Mitch, can you connect to any *open* access points (i.e., access
points that do not use any encryption)? I have had a problem with
network-manager since Dapper, I believe, which prevents me from
connecting to open networks. network-manager *will* connect properly to
WEP-encrypted networks; I
That is what is sort of strange about it. This is not a problem in
general with networkmanager and open networks. Usually networkmanager
works. But there was something about that particular network that it
wouldn't connect to. I have a vague sense it had something to do with the
network
16 matches
Mail list logo
