LMDE and Broadcom driver

[Monsta]

My next step will be to study the repositories management system in Debian and LMDE

For a start, I recommend reading LMDE FAQ. It's a bit outdated, but it still has a lot of valuable information.

[hbco2]

This is the second attempt at a reply, the first dematerialized.
monsta wrote: "Were there any error messages?

.. Is this significant?
MODPOST 1 modules
WARNING: modpost: Found 1 section mismatch(es).
To see full details build your kernel with:
'make CONFIG_DEBUG_SECTION_MISMATCH=y'
.. I am not sure what to run make against (or in which directory).

There are two concerns. One is the wireless function on the Compaq 6715b, which works under Windows7, is not working at all with the present MintDE. The broadcom wireless card does work under MintDE just after initial install but ceases to operate after MintDE is updated. I think that has been covered by the bug report described above.

Following the installation of the Debian upgrade as described, another, more obscure issue has presented itself. The Compaq 6715b has a curious hardware switch/blue light on the keyboard surface. The blue light is lit when the wireless card is active. The blue indicator can be pushed on and off to enable wireless, though if it is pushed off and the computer is powered down, the wireless function will not be recognized by either MintDE or WIndows7. The only reliable way to ensure the wireless function is enabled is to reset the computer bios to system defaults before bringing up an operating system.

The concern is that the current MintDE may be disabling the wireless hardware. If MintDE is ever run, it is necessary to reset the bios in order for the wireless to work in Windows7. If this is the case, it might explain why wireless is not working at present with MintDE, at least on this computer.

Do you think Debian unstable might have better broadcom software?

Any suggestions welcome!
BIll

[Monsta]

MODPOST 1 modules
WARNING: modpost: Found 1 section mismatch(es).
To see full details build your kernel with:
'make CONFIG_DEBUG_SECTION_MISMATCH=y'

That's not an error message, that's a piece of log with some warnings that seem to be unimportant.

.. I am not sure what to run make against (or in which directory).

There's no need to run make manually.

[hbco2]

monsta wrote: "Were there any error messages?
I don't think you were referring to error messages during IPL, but LinuxMint reports the following twice during bootup. Once before the user login screen, and again after:
modprobe: can't load module microcode (kernel/arch/.x86/kernel/microcode.ko) no such device.
Bill

[hbco2]

Sorry for the long post...
in http://forums.linuxmint.com/viewtopic.p ... 7&start=20 a series of probes were suggested to identify the state of the broadcom driver. The results on this system are repeated below. Is this any help?
Bill

~ $ uname -a
Linux hbnb 3.10-2-amd64 #1 SMP Debian 3.10.5-1 (2013-08-07) x86_64 GNU/Linux

~ $ modprobe -r b43 ssb

~ $ modprobe b43

~ $ lsmod
Module Size Used by
b43 331214 0
bcma 33472 1 b43
mac80211 358182 1 b43
ssb 49429 1 b43
mmc_core 77762 2 b43,ssb
rng_core 12761 1 b43
pcmcia 32813 2 b43,ssb
ppdev 12763 0
lp 13025 0
bnep 17535 2
rfcomm 33471 0
bluetooth 170002 10 bnep,rfcomm
cpufreq_userspace 12576 0
cpufreq_conservative 14159 0
cpufreq_stats 12866 0
cpufreq_powersave 12454 0
binfmt_misc 12925 1
ext2 59601 1
loop 22869 0
fuse 67503 1
dm_crypt 18457 0
dm_mod 64008 1 dm_crypt
lib80211_crypt_tkip 13283 0
snd_hda_codec_analog 78587 1
wl 4128894 0
snd_hda_intel 35718 2
hp_wmi 13287 0
snd_hda_codec 122850 2 snd_hda_intel,snd_hda_codec_analog
sparse_keymap 12760 1 hp_wmi
sp5100_tco 12864 0
edac_mce_amd 17070 0
powernow_k8 17425 1
edac_core 43448 0
processor 28526 1 powernow_k8
yenta_socket 22908 0
hp_accel 25200 0
snd_hwdep 13189 1 snd_hda_codec
ac 12668 0
pcmcia_rsrc 17533 1 yenta_socket
shpchp 31346 0
pcmcia_core 18471 3 pcmcia,pcmcia_rsrc,yenta_socket
snd_pcm_oss 41175 0
snd_mixer_oss 18034 1 snd_pcm_oss
snd_pcm 68525 3 snd_pcm_oss,snd_hda_codec,snd_hda_intel
parport_pc 22409 1
parport 31901 3 lp,ppdev,parport_pc
k8temp 12711 0
tpm_infineon 12985 0
i2c_piix4 12704 0
snd_page_alloc 13018 2 snd_pcm,snd_hda_intel
snd_seq_midi 12848 0
snd_seq_midi_event 13316 1 snd_seq_midi
lis3lv02d 17926 1 hp_accel
joydev 17278 0
input_polldev 12906 1 lis3lv02d
snd_rawmidi 23040 1 snd_seq_midi
snd_seq 45186 2 snd_seq_midi_event,snd_seq_midi
battery 13101 0
snd_seq_device 13176 3 snd_seq,snd_rawmidi,snd_seq_midi
snd_timer 22773 2 snd_pcm,snd_seq
snd 53068 15 snd_pcm_oss,snd_hwdep,snd_timer,snd_pcm,snd_seq,snd_rawmidi,snd_hda_codec,snd_hda_intel,snd_seq_device,snd_mixer_oss,snd_hda_codec_analog
kvm_amd 47719 0
tpm_tis 17320 0
tpm 18071 2 tpm_tis,tpm_infineon
tpm_bios 17540 1 tpm
lib80211 12941 2 wl,lib80211_crypt_tkip
soundcore 13026 1 snd
kvm 301458 1 kvm_amd
cfg80211 319971 3 wl,b43,mac80211
rfkill 19242 5 cfg80211,hp_wmi,bluetooth
psmouse 74832 0
serio_raw 12940 0
pcspkr 12632 0
evdev 17611 13
ext4 381419 2
crc16 12343 2 ext4,bluetooth
jbd2 76205 1 ext4
mbcache 13082 2 ext2,ext4
btrfs 641507 0
xor 16985 1 btrfs
zlib_deflate 25638 1 btrfs
raid6_pq 95431 1 btrfs
crc32c 12656 1
libcrc32c 12426 1 btrfs
vga16fb 17347 0
vgastate 12617 1 vga16fb
uvesafb 26184 0
sg 26095 0
sr_mod 21988 0
cdrom 35212 1 sr_mod
sd_mod 40541 5
crc_t10dif 12348 1 sd_mod
ata_generic 12490 0
video 17792 0
radeon 689925 3
i2c_algo_bit 12841 1 radeon
ttm 54470 1 radeon
drm_kms_helper 31837 1 radeon
firewire_ohci 31931 0
drm 211856 5 ttm,drm_kms_helper,radeon
thermal 17468 0
firewire_core 49211 1 firewire_ohci
crc_itu_t 12347 1 firewire_core
i2c_core 24353 5 drm,i2c_piix4,drm_kms_helper,i2c_algo_bit,radeon
fan 12681 0
thermal_sys 23137 4 fan,video,thermal,processor
pata_atiixp 12838 0
ahci 25148 4
libahci 23136 1 ahci
wmi 13243 1 hp_wmi
ohci_hcd 26678 0
ehci_pci 12472 0
ehci_hcd 40590 1 ehci_pci
tg3 133391 0
ptp 13364 1 tg3
pps_core 13232 1 ptp
libata 141969 4 ahci,libahci,ata_generic,pata_atiixp
libphy 23785 1 tg3
button 12944 0
scsi_mod 158249 4 sg,libata,sd_mod,sr_mod
usbcore 134993 3 ohci_hcd,ehci_hcd,ehci_pci
usb_common 12440 1 usbcore
total 32

~ $ ls-l /etc/modprobe.d
-rw-r--r-- 1 root root 229 May 3 2011 alsa-base-blacklist.conf
-rw-r--r-- 1 root root 1186 Aug 26 2012 alsa-base.conf
-rw-r--r-- 1 root root 180 Jan 30 2013 broadcom-sta-dkms.conf
-rw-r--r-- 1 root root 127 Dec 7 2011 dkms.conf
-rw-r--r-- 1 root root 456 Apr 28 2013 fbdev-blacklist.conf
-rw-r--r-- 1 root root 23 Nov 7 2010 i915-kms.conf
-rw-r--r-- 1 root root 356 Mar 24 2012 oss-compat.conf
-rw-r--r-- 1 root root 26 Nov 7 2010 radeon-kms.conf

~ $ cat: /etc/modprobe.d/broadcom-sta-common.conf: No such file or directory

cat: /etc/modprobe.d/broadcom-sta-dkms.conf
# wl module from Broadcom conflicts with the following modules:
blacklist b43
blacklist b43legacy
blacklist b44
blacklist bcma
blacklist brcm80211
blacklist brcmsmac
blacklist ssb

[kurotsugi]

if you're sure that the driver is b43 you can delete it from the blacklist list. however, the common used broadcomm driver is 'wl'. activate b43 in most cases will cause some problem

[Monsta]

Yes, I gave the instructions for setting up the proprietary driver, "wl", from broadcom-sta-dkms package. One user already reported everything's working, the other one seems to have difficulties describing what the problem is.

[ptyxs]

@hbcc2 :

I executed your instructions, everything worked well, without any error message, and after reboot I finally got a wifi connexion.

Did you try these instructions, step by step ? if so did you notice any error message during their execution ? then what did you do exactly after that and what failed ? I think as long as you won't explain all of that precisely Monsta won't be able to help you.

[hbco2]

@hbcc2 :

I executed your instructions, everything worked well, without any error message, and after reboot I finally got a wifi connexion.

Did you try these instructions, step by step ? if so did you notice any error message during their execution ? then what did you do exactly after that and what failed ? I think as long as you won't explain all of that precisely Monsta won't be able to help you.

If you are referring to (hbco2), absolutely yes. The Debian site discussing the bug was reviewed and your instructions were followed very carefully with results quoted in a previous post. In summary, nothing changed, the wireless hardware remained unrecognized and during boot received the modprobe error message as previously quoted:
"modprobe: can't load module microcode (kernel/arch/x86/kernel/microcode.ko) no such device."

After my previous post, and upon reboot, the system became completely unstable with pages of error messages during normal boot and also during boot-recovery concluding in a completely locked system. LinuxMintDE was again installed without updating and is in use with an active wireless link to compose this message. wl is the driver.
Linux hbnb 3.2.0-4-amd64 #1 SMP Debian 3.2.32-1 x86_64 GNU/Linux

It would be useful to be able to update and upgrade this software.
Bill

[ptyxs]

i was referring indeed to hbco2, sorry for the typo.

[hbco2]

Well, I misspoke, after installation the system was updated and the module "firmware-b43-installer" was installed to activate the wireless hardware. In this latest incarnation, the LinuxMint software has not been upgraded to the current release.

The upgrade was attempted several times in previous installation attempts but never went smoothly, the old Linux kernel was not removed and was visible in grub. Also, multiple font statements were left in scripts.

The major consequence of an upgrade is the modprobe firmware error, which appears on the screen twice briefly during cold boot, and subsequent loss of wireless. The error also appears after the upgrade in a boot of the original kernel.
Bill

[Monsta]

"modprobe: can't load module microcode (kernel/arch/x86/kernel/microcode.ko) no such device."

This looks unrelated to wireless stuff.

After my previous post, and upon reboot, the system became completely unstable with pages of error messages during normal boot and also during boot-recovery concluding in a completely locked system.

Well, I'm pretty sure nothing in the instructions should cause this... unless you additionally did something with modprobe and blacklist. Next I was going to ask to post the exact error messages, since descriptions like "pages of error messages" cannot be used to help anyone. But since you've already reinstalled the system, I think the subject can be considered closed at this.

It would be useful to be able to update and upgrade this software.

You can upgrade the system and still use your old kernel. It won't be deleted automatically on upgrade.

[hbco2]

"modprobe: can't load module microcode (kernel/arch/x86/kernel/microcode.ko) no such device."

This looks unrelated to wireless stuff.

I'll have to investigate further (will have to recreate the procedure used), but in previous digging, was able to manually step though some of the installation, and reproduce this message in an attempt to load the wireless driver.

After my previous post, and upon reboot, the system became completely unstable with pages of error messages during normal boot and also during boot-recovery concluding in a completely locked system.

Well, I'm pretty sure nothing in the instructions should cause this... unless you additionally did something with modprobe and blacklist. Next I was going to ask to post the exact error messages, since descriptions like "pages of error messages" cannot be used to help anyone. But since you've already reinstalled the system, I think the subject can be considered closed at this.

Would agree. I don't know the cause of the failure, but it was massive. Nothing was deliberately changed. I suppose the error printout could have been interrupted before the system crashed, but the error strings were so extensive it didn't seem worth exploring. It just occurred to me that I am living under high-tension power lines and have recently seen a number of unusual glitches in the several systems running here. I wouldn't normally make that association, but... At any rate, this part can be closed, but don't wish to dismiss the inability to run wireless under the current version of LinuxMintDE.

To address your request to list error messages, other than the modprobe printout, there have been none. The wireless function simply disappears. The only history is in the network-connections application that maintains the wireless attachment information, and of course the installed driver software. The Network application variously has no indication of wireless at all, or would show the wireless option with the message "firmware missing." Results of various reporting utilities have been listed in posts in this thread. Again, troubleshooting attempts will need to be retraced in order to recreate the modprobe 'missing firmware' message. And the message may turn out to be unrelated to wireless!

It would be useful to be able to update and upgrade this software.

You can upgrade the system and still use your old kernel. It won't be deleted automatically..[snips]

I'd like to upgrade the system and use wireless
Thanks for your help.
Bill

[hbco2]

Solved! I don't have details, and didn't have to do anything special other than run 'sudo apt-get install firmware-b43-installer' before upgrading, then took the plunge and upgraded the system. It took a back and forth combination of running the Update Manager and apt-get upgrade to complete the system upgrade from the installation .iso, but am now running MintDE SMP Debian 3.10.5-1, and wireless is happily active. 'lsmod |grep b43' shows the b43 driver installed, a change from the wl driver previously shown. With kurosgi's admonitions, remain cautiously optimistic, but for the present all seems well! Yes, the modprobe firmware missing statement must be unrelated, as it has reappeared during boot with the upgrade but without apparent impact.
Thank you all for all the great support. Obviously a lot of time and effort has gone into looking at this issue.
Bill

[hbco2]

Alas, the delight was only temporary. After working without apparent incident for a couple of days, the wireless function lost connection, then proceeded to shut down, taking the wireless configuration with it. An extract of daemon.log showing the gory details is available if anyone is interested. Still think that some part of the broadcom driver is not being used to initialize or reset some component of the hardware. At any rate, the wireless hardware is now unrecognized (iwconfig shows 'no wireless connections' for eth1 and lo, and wlan0 is not listed) and there doesn't seem to be any way to enable wireless. UP7 installed; debian verson of broadcom-sta-dkms was installed, but no change.