Re: airport stops working on debian side of computer
You mght try blacklisting bcm43xx. Do a google for Linksys WMP54GS running on Debian. Ben On Sat, Sep 20, 2008 at 12:22 AM, Cheryl Homiak [EMAIL PROTECTED] wrote: Unfortunately, blaclisting those drivers had no effect. How did you know which ones to blacklist/ Perhaps I have a similar problem but with different drivers.
Re: airport stops working on debian side of computer
Also it appears that you must have ndiswrapper installed along with wireless-tools . On Sat, Sep 20, 2008 at 2:45 AM, Benjamin Hoffman [EMAIL PROTECTED]wrote: You mght try blacklisting bcm43xx. Do a google for Linksys WMP54GS running on Debian. Ben On Sat, Sep 20, 2008 at 12:22 AM, Cheryl Homiak [EMAIL PROTECTED]wrote: Unfortunately, blaclisting those drivers had no effect. How did you know which ones to blacklist/ Perhaps I have a similar problem but with different drivers.
Re: airport stops working on debian side of computer
On Fri, Sep 19, 2008 at 08:06:01PM -0500, Cheryl Homiak wrote: I am running a ppc mac mini with the broadcom chip (bcm4306); am running debian unstable with kernel 2.6.26-1; have just updated with apt-get hoping this would ix the problem but it didn't. My wireless suddenly stopped working--using airport extreme--but still works fine on the mac side of the computer. /var/log/messages shows all the broadcom components being loaded but shows link not ready when brought up. cat /proc/net/dev shows wlan0_rename (also a eth1) but all zeros. The relevant part of lspci -knn shows: 0001:10:12.0 Network controller [0280]: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller [14e4:4320] (rev 03) Kernel driver in use: b43-pci-bridge Kernel modules: ssb I did make the firmware changes as instructed with the 2.6.25 kernel and this problem didn't occur when I changed to 2.6.26. Has anybody had this happen and are there other tests I should run or other logs in which I need to look to find out wt is wrong? Could you please include the output of dmesg (only relevant parts), ifconfig -a and iwconfig. The wlan0_rename above you mention could indicate that something with persistent device name rules of udev could be wrong. You could try to delete /etc/udev/rules.d/70-persistent-net.rules and reboot. After that all your network devices will have new persistent names assigned by udev. What mechanism do you use to configure your wlan (/etc/network/interfaces, network-manager, ...)? Are you using any kind of encription on the wireless link? In general your card should be well supported by the b43 kernel module. So I suspect you have an error in your configuration. Gaudenz -- Ever tried. Ever failed. No matter. Try again. Fail again. Fail better. ~ Samuel Beckett ~ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
