** Description changed:

  In 32-bit Lucid Lynx I was able to get the broadcom BCM4212 wireless
  working with the proprietary driver that I installed. There is however a
  very annoying bug related to the wireless switch on this Dell Vostro
  1320 and I am not sure if it is related to the switch itself, with the
  wireless driver or with network-manager. What happens is the following:
  
  Whenever the computer is turned on (or returning from suspend/hibernate)
  the current position of the wireless switch is recognized by network-
- manager (or kernel, don´t know where this is detected) as being in
- disabled mode. This is fine if that's in fact the position of the switch
- is actually disabled as enabling it will turn on the hardware (blue
- wireless light comes on) and network-manager will identify it as active
- automatically enabling wireless (unless I deactivate it there of course)
- allowing we to connect. If the switch is actually in the "on" position
- when the computer is turned on (which it will be most of the time) the
- blue wireless light is on and seemingly working while network-manager
+ manager (actually likely by rfkill) as being in disabled mode. This is
+ fine if that's in fact the position of the switch is actually disabled
+ as enabling it will turn on the hardware (blue wireless light comes on)
+ and network-manager will identify it as active automatically enabling
+ wireless (unless I deactivate it there of course) allowing we to
+ connect. If the switch is actually in the "on" position when the
+ computer is turned on (which it will be most of the time) the blue
+ wireless light is on and seemingly working while network-manager
  recognizes it as being off and grays out the option of activating
  wireless. Flipping the switch now will cause network-manager to think it
  is on (and so it "activates" wireless) but at the same time the hardware
  is actually turned off (blue light goes off as well) so no networks are
  ever found.
  
  This is really annoying since I always have to reboot/suspend all the
  time to be able to use wireless. It is even more frustrating because the
  computer is not mine (I am just configuring it for a complete
  linux/ubuntu newbie) and my friend is waiting for a fully functional
  ubuntu.
  
  I should also mention that the the switch works as it should in Windows
  Vista (it's a dual-boot configuration).
  
  Trying the behavior from a live-usb (lucid) gives the same results even
  before activating the proprietary driver (which leads me to believe the
  problem is not with the driver itself).
  
- I checked /var/log/messages and /var/log/kernel and didn´t see any
- entries when flipping the switch so I do not know if the problem is with
- network-manager or with the kernel and I also don´t know which log
- files/command outputs I should include/look into to further troubleshoot
- but let me know which ones are valid and I´ll include them right away.
- 
  Short of a solution, any workaround would be very welcome. Such as
  fooling kernel/network-manager that wireless switch is always on etc.
  
  Kristofer
+ 
+ Here is the output of some commands that might be useful:
+ 
+ rfkill - seemingly the culprit, here showing hardware as off even though
+ it was on as happens when turning computer on with switch on:
+ 
+ rfkill list
+ 0: dell-wifi: Wireless LAN
+       Soft blocked: no
+       Hard blocked: yes
+ 
+ Turning the killswitch off at this point "wrongly" toggles the
+ killswitch to the "Hard blocked: no" state.
+ 
+ $lspci | grep Broadcom
+ 0e:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g (rev 01)
+ 
+ 
+ $ lsmod
+ Module                  Size  Used by
+ binfmt_misc             6587  1 
+ ppdev                   5259  0 
+ vboxnetadp              6326  0 
+ vboxnetflt             15162  0 
+ vboxdrv               190409  2 vboxnetadp,vboxnetflt
+ snd_hda_codec_idt      51914  1 
+ fbcon                  35102  71 
+ tileblit                2031  1 fbcon
+ font                    7557  1 fbcon
+ bitblit                 4707  1 fbcon
+ softcursor              1189  1 bitblit
+ vga16fb                11385  0 
+ vgastate                8961  1 vga16fb
+ joydev                  8708  0 
+ snd_hda_intel          21877  2 
+ snd_hda_codec          74201  2 snd_hda_codec_idt,snd_hda_intel
+ snd_hwdep               5412  1 snd_hda_codec
+ snd_pcm_oss            35308  0 
+ snd_mixer_oss          13746  1 snd_pcm_oss
+ snd_pcm                70662  3 snd_hda_intel,snd_hda_codec,snd_pcm_oss
+ snd_seq_dummy           1338  0 
+ snd_seq_oss            26726  0 
+ snd_seq_midi            4557  0 
+ snd_rawmidi            19056  1 snd_seq_midi
+ snd_seq_midi_event      6003  2 snd_seq_oss,snd_seq_midi
+ snd_seq                47263  6 
snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event
+ snd_timer              19098  2 snd_pcm,snd_seq
+ snd_seq_device          5700  5 
snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq
+ i915                  282354  3 
+ drm_kms_helper         29297  1 i915
+ uvcvideo               56990  0 
+ dell_wmi                1793  0 
+ snd                    54148  16 
snd_hda_codec_idt,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
+ lib80211_crypt_tkip     7596  0 
+ drm                   162471  4 i915,drm_kms_helper
+ psmouse                63245  0 
+ videodev               34361  1 uvcvideo
+ dell_laptop             6856  0 
+ dcdbas                  5422  1 dell_laptop
+ soundcore               6620  1 snd
+ snd_page_alloc          7076  2 snd_hda_intel,snd_pcm
+ sdhci_pci               5470  0 
+ sdhci                  15462  1 sdhci_pci
+ led_class               2864  1 sdhci
+ intel_agp              24177  2 i915
+ serio_raw               3978  0 
+ agpgart                31724  2 drm,intel_agp
+ v4l1_compat            13251  2 uvcvideo,videodev
+ i2c_algo_bit            5028  1 i915
+ wl                   1959598  0 
+ lib80211                5046  2 lib80211_crypt_tkip,wl
+ video                  17375  1 i915
+ output                  1871  1 video
+ lp                      7028  0 
+ parport                32635  2 ppdev,lp
+ r8169                  33884  0 
+ ohci1394               26950  0 
+ mii                     4381  1 r8169
+ ahci                   32008  4 
+ ieee1394               81181  1 ohci1394
+ 
+ $ nm-tool 
+ ...
+ - Device: eth2 
-----------------------------------------------------------------
+   Type:              802.11 WiFi
+   Driver:            wl
+   State:             unavailable
+   Default:           no
+   HW Address:        00:26:5E:82:30:5B
+ 
+   Capabilities:
+ 
+   Wireless Properties
+     WEP Encryption:  yes
+     WPA Encryption:  yes
+     WPA2 Encryption: yes
+ 
+   Wireless Access Points

** Branch linked: lp:ubuntu/lucid/rfkill

** Branch unlinked: lp:ubuntu/lucid/rfkill

-- 
Wireless switch position not properly detected
https://bugs.launchpad.net/bugs/588366
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to