Re: BCM4312/b43 acts weird with NetworkManager and F13
ke, 2010-08-11 kello 18:36 -0500, Dan Williams kirjoitti: > Yes, against the acer-wmi kernel module. It's clear that something is > going on; either the module is misdetecting the presence of a > killswitch on your device, or the state of that killswitch, or it > doesn't properly support your model yet. Here's the bug report: https://bugzilla.kernel.org/show_bug.cgi?id=16570 -- Ville-Pekka Vainio ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: BCM4312/b43 acts weird with NetworkManager and F13
On Wed, 2010-08-11 at 23:38 +0300, Ville-Pekka Vainio wrote: > I tried blacklisting the acer-wmi module and it seems NetworkManager now > works as expected: when I log in to GNOME, it has connected to my wifi > network. Should I report this as a kernel bug? Yes, against the acer-wmi kernel module. It's clear that something is going on; either the module is misdetecting the presence of a killswitch on your device, or the state of that killswitch, or it doesn't properly support your model yet. Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: BCM4312/b43 acts weird with NetworkManager and F13
I tried blacklisting the acer-wmi module and it seems NetworkManager now works as expected: when I log in to GNOME, it has connected to my wifi network. Should I report this as a kernel bug? -- Ville-Pekka Vainio ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: BCM4312/b43 acts weird with NetworkManager and F13
la, 2010-08-07 kello 21:54 -0500, Dan Williams kirjoitti: > Before you check "enable wireless", what is the contents of: > > /var/lib/NetworkManager/NetworkManager.state [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true > and what is the output of: > > rfkill list 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: acer-wireless: Wireless LAN Soft blocked: yes Hard blocked: no 2: phy0: Wireless LAN Soft blocked: no Hard blocked: no > cat /sys/class/rfkill/*/state 1 0 1 > cat /sys/class/rfkill/*/type bluetooth wlan wlan > Lets see what those have in them and then we can debug further. ALso, > what are the top lines of /var/log/daemon.log when NetworkManager starts > up? I don't have such a file in the system, but here's some stuff I grepped from /var/log/messages: Aug 11 22:50:53 lenovo-s12 NetworkManager[963]: NetworkManager (version 0.8.1-1.fc13) is starting... Aug 11 22:50:53 lenovo-s12 NetworkManager[963]: Read config file /etc/NetworkManager/NetworkManager.conf Aug 11 22:50:53 lenovo-s12 NetworkManager[963]: trying to start the modem manager... Aug 11 22:50:53 lenovo-s12 NetworkManager[963]:ifcfg-rh: Acquired D-Bus service com.redhat.ifcfgrh1 Aug 11 22:50:53 lenovo-s12 NetworkManager[963]: Loaded plugin ifcfg-rh: (c) 2007 - 2008 Red Hat, Inc. To report bugs please use the NetworkManager mailing list. Aug 11 22:50:53 lenovo-s12 NetworkManager[963]: found WiFi radio killswitch rfkill2 (at /sys/devices/pci:00/:00:1c.1/:03:00.0/ssb0:0/ieee80211/phy0/rfkill2) (driver ) Aug 11 22:50:53 lenovo-s12 NetworkManager[963]: found WiFi radio killswitch rfkill1 (at /sys/devices/platform/acer-wmi/rfkill/rfkill1) (driver acer-wmi) Aug 11 22:50:53 lenovo-s12 NetworkManager[963]: WiFi disabled by radio killswitch; enabled by state file Aug 11 22:50:54 lenovo-s12 NetworkManager[963]: WWAN enabled by radio killswitch; enabled by state file Aug 11 22:50:54 lenovo-s12 NetworkManager[963]: WiMAX enabled by radio killswitch; enabled by state file Aug 11 22:50:54 lenovo-s12 NetworkManager[963]: Networking is enabled by state file Aug 11 22:50:54 lenovo-s12 NetworkManager[963]: (eth0): carrier is OFF Aug 11 22:50:54 lenovo-s12 NetworkManager[963]: (eth0): new Ethernet device (driver: 'tg3' ifindex: 2) Aug 11 22:50:54 lenovo-s12 NetworkManager[963]: (eth0): exported as /org/freedesktop/NetworkManager/Devices/0 Aug 11 22:50:54 lenovo-s12 NetworkManager[963]: (eth0): now managed Aug 11 22:50:54 lenovo-s12 NetworkManager[963]: (eth0): device state change: 1 -> 2 (reason 2) Aug 11 22:50:54 lenovo-s12 NetworkManager[963]: (eth0): bringing up device. Aug 11 22:50:54 lenovo-s12 NetworkManager[963]: (eth0): preparing device. Aug 11 22:50:54 lenovo-s12 NetworkManager[963]: (eth0): deactivating device (reason: 2). Aug 11 22:50:54 lenovo-s12 NetworkManager[963]: (wlan0): driver supports SSID scans (scan_capa 0x01). Aug 11 22:50:54 lenovo-s12 NetworkManager[963]: (wlan0): new 802.11 WiFi device (driver: 'b43' ifindex: 3) Aug 11 22:50:54 lenovo-s12 NetworkManager[963]: (wlan0): exported as /org/freedesktop/NetworkManager/Devices/1 Aug 11 22:50:54 lenovo-s12 NetworkManager[963]: (wlan0): now managed Aug 11 22:50:54 lenovo-s12 NetworkManager[963]: (wlan0): device state change: 1 -> 2 (reason 2) Aug 11 22:50:54 lenovo-s12 NetworkManager[963]: (wlan0): bringing up device. Aug 11 22:50:54 lenovo-s12 NetworkManager[963]: (wlan0): deactivating device (reason: 2). Aug 11 22:50:54 lenovo-s12 NetworkManager[963]: modem-manager is now available Aug 11 22:50:54 lenovo-s12 NetworkManager[963]: bluez error getting default adapter: The name org.bluez was not provided by any .service files Aug 11 22:50:54 lenovo-s12 NetworkManager[963]: Trying to start the supplicant... Aug 11 22:50:54 lenovo-s12 NetworkManager[963]: (wlan0): supplicant manager state: down -> idle Aug 11 22:50:57 lenovo-s12 NetworkManager[963]: /sys/devices/virtual/net/pan0: couldn't determine device driver; ignoring... One thing which puzzles me here is the acer-wmi driver. As you might guess from the host name, the laptop is a Lenovo Ideapad S12 with Intel and Broadcom hardware. Often driver names are different from hardware brand names, but still "acer" doesn't really seem to fit the picture here. -- Ville-Pekka Vainio ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: BCM4312/b43 acts weird with NetworkManager and F13
On Sat, 2010-08-07 at 16:32 +0300, Ville-Pekka Vainio wrote: > I decided to test the Broadcom proprietary driver and it has the same > problem as b43, I still need to click "Enable Wireless" before NM shows > any wifi networks. I think that's unnecessary, the wireless could just > be enabled by default. Before you check "enable wireless", what is the contents of: /var/lib/NetworkManager/NetworkManager.state and what is the output of: rfkill list cat /sys/class/rfkill/*/state cat /sys/class/rfkill/*/type Lets see what those have in them and then we can debug further. ALso, what are the top lines of /var/log/daemon.log when NetworkManager starts up? It'll be something like this: Aug 2 21:34:54 dcbw NetworkManager[1271]: WiFi enabled by radio killswitch; enabled by state file Aug 2 21:34:54 dcbw NetworkManager[1271]: WWAN disabled by radio killswitch; disabled by state file Aug 2 21:34:54 dcbw NetworkManager[1271]: WiMAX enabled by radio killswitch; enabled by state file Aug 2 21:34:54 dcbw NetworkManager[1271]: Networking is enabled by state file Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: BCM4312/b43 acts weird with NetworkManager and F13
On 08/07/2010 08:32 AM, Ville-Pekka Vainio wrote: > I decided to test the Broadcom proprietary driver and it has the same > problem as b43, I still need to click "Enable Wireless" before NM shows > any wifi networks. I think that's unnecessary, the wireless could just > be enabled by default. As I suspected, it is not a b43 problem. ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: BCM4312/b43 acts weird with NetworkManager and F13
I decided to test the Broadcom proprietary driver and it has the same problem as b43, I still need to click "Enable Wireless" before NM shows any wifi networks. I think that's unnecessary, the wireless could just be enabled by default. -- Ville-Pekka Vainio ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: BCM4312/b43 acts weird with NetworkManager and F13
Em 6 de agosto de 2010 15:43, Ville-Pekka Vainio escreveu: > On Fri, 6 Aug 2010 15:32:27 -0300, "José Queiroz" wrote: > > In Ubuntu, the native b43 module is broken, as the device is always > > disabled. > > > > We have to block it and use the bcmwl-kernel-source, which installs a > "wl" > > driver > > that works. > > > > Maybe this works for you, too? > > > Thanks for the suggestion, but I'd rather not use closed source drivers as > long > as the open source ones work, at least to some degree. > > -- > Ville-Pekka Vainio > Won't you even give it a try? ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: BCM4312/b43 acts weird with NetworkManager and F13
2010/8/6 Ville-Pekka Vainio > Hi, > > I'm running Fedora 13 with NetworkManager-0.8.1-1 and a 2.6.34 kernel from > koji. My system has a BCM4312 wifi chip which I'm using with the b43 module > and the proprietary firmware from Broadcom. > > In Ubuntu, the native b43 module is broken, as the device is always disabled. We have to block it and use the bcmwl-kernel-source, which installs a "wl" driver that works. Maybe this works for you, too? NetworkManager is acting a bit weird with wifi. Every time I reboot the > laptop, the wireless connection is disabled, meaning I have to right click > on the nm-applet icon and choose "Enable wireless". Based on > /var/log/messages the firmware is loaded to the device at this point like > this: > > NetworkManager[968]: (wlan0): bringing up device. > kernel: b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23) > kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready > dbus-daemon: [system] Rejected send message, 1 matched rules; > type="method_return", sender=":1.1" (uid=0 pid=968 comm="NetworkManager) > interface="(unset)" member="(unset)" error name="(unset)" requested_reply=0 > destination=":1.56" (uid=500 pid=1563 comm="nm-applet)) > NetworkManager[968]: (wlan0): supplicant interface state: starting > -> ready > NetworkManager[968]: (wlan0): device state change: 2 -> 3 (reason > 42) > NetworkManager[968]: Activation (wlan0) starting connection 'Auto > ' > > etc. etc. > > With my previous laptop, which had an Intel wifi chip, the wireless network > was always automatically enabled when I booted up the computer. I know the > b43 drivers are still under development, but does anyone have an idea what > could be going wrong? The dbus error does look a bit scary to me. > > -- > Ville-Pekka Vainio > ___ > networkmanager-list mailing list > networkmanager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list > ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
