I did hazardous changes after facing wifi problems on last debian 7.4 software update. My wifi keyboard key doesn't switch wifi on/off anymore. It keeps the off state.

Wifi key

After searching google I found that

$ sudo apt-get install rfkill
$ rfkill list
0: hp-wifi: Wireless LAN
    Soft blocked: yes
    Hard blocked: yes

states that in fact the wifi was "hard blocked" so I did

sudo rfkill unblock wifi

that gives now

$ rfkill list
0: hp-wifi: Wireless LAN
    Soft blocked: no
    Hard blocked: no

I can toggle the hard blocked state by pressing the wifi keyboard button. That solved the hardware problem.

Wifi driver

I remember having removed the previously associated lw driver with modprobe -r ... while following a post (that didn't succeed).

My previous configuration was : (I track updates)

lspci -nnk | grep -iA2 net
02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller [10ec:8136] (rev 02)
    Subsystem: Hewlett-Packard Company Device [103c:143c]
    Kernel driver in use: r8169
03:00.0 Network controller [0280]: Broadcom Corporation BCM4313 802.11b/g/n Wireless LAN Controller [14e4:4727] (rev 01)
    Subsystem: Hewlett-Packard Company Device [103c:145c]
    Kernel driver in use: wl

so a BCM4313 chipset associated with the wl kernel driver

Now I read

02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller [10ec:8136] (rev 02)
    Subsystem: Hewlett-Packard Company Device [103c:143c]
    Kernel driver in use: r8169
03:00.0 Network controller [0280]: Broadcom Corporation BCM4313 802.11b/g/n Wireless LAN Controller [14e4:4727] (rev 01)
    Subsystem: Hewlett-Packard Company Device [103c:145c]

so no driver found anymore.

my questions are :

how to setup a driver for a wifi card ? modprob ... ?
Which driver to use : lw or B43 ?

Thanks for your help

Wrong kernel module selected

Looking at a previous post where I faced a Network Unclaimed issue on my wireless card I missed to mention that the original problem was in fact this keyboard issue solved as described in this post by issuing