I cannot establish anything solid about that. The behavior is extremely
unpredictable.
It could work sometimes right away, sometimes I have to try to reconnect
several times, sometimes I unload/reload the driver. At sometimes I tried the
command
'sudo iwconfig eth0 ap any' which seemed to help,
Well, maybe not related to the original problem, but so far what I found out is
when I come back from sleep I eventually find (after trying to connect for a
few minutes) the following in dmesg:
[81518.921534] bcm43xx: IRQ_READY timeout
So I unloaded and reloaded the module which then worked.
Als
Something made it work somehow now. It's not the instructions from that
page coz I haven't done any changes to /etc/network/interfaces -
NetworkManager just succeeded in connecting this time. I will have to
try some more to see what exactly is going on. I'll report back...
--
bcm43xx in edgy does
@fuoco:
can you try these steps to install the firmware (or did you do it already?):
sudo apt-get install bcm43xx-fwcutter
sudo /usr/share/bcm43xx-fwcutter/install_bcm43xx_firmware.sh
Took this from the forum:
https://help.ubuntu.com/community/WifiDocs/Driver/bcm43xx/Dapper
Please read the chapt
Indeed the module is correctly autoloaded. There is no problem of
scanning for me. I do get results with 'iwlist scan' and also
NetworkManager shows some APs. When I choose mine, however, it tries to
connect but doesn't succeed.
--
bcm43xx in edgy doesn't connect to AP anymore
https://launchpad.n
The module loads automatically:
$ lsmod | grep bcm
bcm43xx 124436 0
ieee80211softmac 30720 1 bcm43xx
ieee80211 33608 2 bcm43xx,ieee80211softmac
>From dmesg:
[17179589.724000] ieee80211_crypt: registered algorithm 'NULL'
[17179589.756000] ieee80211: 802.11 data
The module loads automatically:
$ lsmod | grep bcm
bcm43xx 124436 0
ieee80211softmac 30720 1 bcm43xx
ieee80211 33608 2 bcm43xx,ieee80211softmac
>From dmesg:
[17179589.724000] ieee80211_crypt: registered algorithm 'NULL'
[17179589.756000] ieee80211: 802.11 data
Hello again, lets try next step:
is the module properly loaded? You can check this with the command:
sudo lsmod | grep bcm
Please post the output.
If not, you could add the module to /etc/modules - which could solve the
problem temporarily.
--
bcm43xx in edgy doesn't connect to AP anymore
htt
I have the same behaviour on a fresh Edgy installation on an Dell
Inspiron 6400 (sometimes I get a lockup) but mostly I can only view the
accesspoints, but not assosiate with them.
The firmware has been installed using "bcm43xx-fwcutter" and the script
coming in that package.
--
bcm43xx in edgy
I tried that command but nothing happens. It doesn't fail or something, but
pinging the router or any other address fails:
$ ping 192.168.1.1
connect: Network is unreachable
$ ping yahoo.com
ping: unknown host yahoo.com
--
bcm43xx in edgy doesn't connect to AP anymore
https://launchpad.net/bugs/
Please try this:
sudo ifconfig wlan0 up
where wlan0 is your wireless card.
Xou can display your wireless settings, if already configured with
sudo iwconfig
--
bcm43xx in edgy doesn't connect to AP anymore
https://launchpad.net/bugs/68704
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.
I have these packages installed:
linux-restricted-modules-2.6.17-10-powerpc
linux-restricted-modules-common
linux-restricted-modules-powerpc
I have not tried to connect the network via console, I don't really know how
to. If you can point me to instructions I will try that.
Also I suspected bcm4
Thank you for your bug report.
Could you please check if the package linux-restricted-modules is
installed?
Did you try to connect the network via console? If so, please attatch
the console output.
Thanks Peter
--
bcm43xx in edgy doesn't connect to AP anymore
https://launchpad.net/bugs/68704
** Changed in: Ubuntu
Sourcepackagename: None => linux-source-2.6.17
--
bcm43xx in edgy doesn't connect to AP anymore
https://launchpad.net/bugs/68704
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
14 matches
Mail list logo
