Wireless lost after reboot

OS is Suse 12.3, Gnome, fresh install.

In a Compaq 6715b, the script “install_bcm43xx_firmware” is used to install firmware for the wireless interface. Once installed, the wireless interface functioned very well. However, with further use (restarting the Compaq), the firmware suddenly is not recognized by SuSE 12.3. Also, access to the Network Manager (desktop:username->System Settings->Network) results in an alert “The System network services are not compatible with this version.” Apparently the latter was due to the selection to use manual network configuration (ifup), which was selected to get Samba working. Under YaST, the network configuration has been returned to Network Manager.

Access to the Network Manager using (desktop:Activities->Show Applications->System Tools->Yast) has never worked on the first attempt, the user is returned to the desktop. Repeating the access to Yast then displays the root password and allows subsequent access to Yast.

Despite numerous attempts to disable the non-functional fingerprinting password assist, the “su root” command in the Gnome Terminal results in the “Scan right finger on AuthenTec AES2501” prompt whenever a password is requested for root. The fingerprint function can be turned off for a while by inactivating the fingerprint function in the user security section, but upon reboot the fingerprint function becomes active again.

Returning to the wireless issue (the above additional issues interrupted documenting the wireless issue), reinstalling bcm43xx firmware using the above script results in corrupted text in the title section of various Gnome boxes. That problem can be corrected by a system reboot. Booting on this computer includes a number of screens with gibberish, although they are apparently benign, however now use of the wireless module is now permanently lost. The wireless lights on the keyboard are out, and the wireless options are not shown in the network screen.

This computer was obtained to replace a stable, nicely working SuSE 11.2 version, no longer supported. Binary downloads for 11.2 application software is no longer commonly offered. Suse 13.1 beta of course is still under development. Is there a way to get the wireless function working again? Is there a currently supported SuSE version that is reasonably stable that one might be able to install on this Compaq?

TIA

On 2013-10-09 00:56, hbco2 wrote:
>
> OS is Suse 12.3, Gnome, fresh install.

There is a dedicated wireless forum here. You should ask a moderator to
move your post there for getting the best support. Use the triangle
button below.


Cheers / Saludos,

Carlos E. R.
(from 11.4, with Evergreen, x86_64 “Celadon” (Minas Tirith))

On 10/08/2013 05:56 PM, hbco2 wrote:
>
> OS is Suse 12.3, Gnome, fresh install.
>
> In a Compaq 6715b, the script “install_bcm43xx_firmware” is used to
> install firmware for the wireless interface. Once installed, the
> wireless interface functioned very well. However, with further use
> (restarting the Compaq), the firmware suddenly is not recognized by SuSE
> 12.3. Also, access to the Network Manager (desktop:username->System
> Settings->Network) results in an alert “The System network services are
> not compatible with this version.” Apparently the latter was due to the
> selection to use manual network configuration (ifup), which was selected
> to get Samba working. Under YaST, the network configuration has been
> returned to Network Manager.
>
> Access to the Network Manager using (desktop:Activities->Show
> Applications->System Tools->Yast) has never worked on the first attempt,
> the user is returned to the desktop. Repeating the access to Yast then
> displays the root password and allows subsequent access to Yast.
>
> Despite numerous attempts to disable the non-functional fingerprinting
> password assist, the “su root” command in the Gnome Terminal results in
> the “Scan right finger on AuthenTec AES2501” prompt whenever a password
> is requested for root. The fingerprint function can be turned off for a
> while by inactivating the fingerprint function in the user security
> section, but upon reboot the fingerprint function becomes active again.
>
> Returning to the wireless issue (the above additional issues interrupted
> documenting the wireless issue), reinstalling bcm43xx firmware using the
> above script results in corrupted text in the title section of various
> Gnome boxes. That problem can be corrected by a system reboot. Booting
> on this computer includes a number of screens with gibberish, although
> they are apparently benign, however now use of the wireless module is
> now permanently lost. The wireless lights on the keyboard are out, and
> the wireless options are not shown in the network screen.
>
> This computer was obtained to replace a stable, nicely working SuSE
> 11.2 version, no longer supported. Binary downloads for 11.2 application
> software is no longer commonly offered. Suse 13.1 beta of course is
> still under development. Is there a way to get the wireless function
> working again? Is there a currently supported SuSE version that is
> reasonably stable that one might be able to install on this Compaq?

This effect is usually self inflicted. If you have ever messed with wl, then it
has blacklisted b43 and ssb. That prevents the driver from loading normally.

To check this, try the following things:


ls /lib/firmware/b43
lsmod | grep b43
sudo /sbin/modprobe -v b43

Are files listed for the first command? If so, the firmware is installed. Does
the second command show anything? If so, then the driver is loaded. If #2 shows
nothing, then ‘egrep “ssb|b43” /etc/modprobe.d/*’. Any line that show b43 or ssb
needs to be deleted.

(1) the driver software is loaded, and a portion of the wireless screens now appears again in the Network Manager. However, the hardware is apparently not active (no activity lights) and there is no way to configure the wireless interface in Network Manager (no selection of links, no way to set security).
(2) the driver is apparently not loaded, null response from lsmod.
(3) apparently there aren’t any entries in the modprove.d files. ‘egrep “ssb|b43” /etc/modprobe.d/*’ returned nothing, ran seperately for ssb and b43.
(4) will follow recommendation to move this topic to wireless. Thank you!

Moving to wireless. NNTP users please to not reply.

Moved from Install/Boot/Login. Open again

After following some of the recommendations in the wireless section to research the Compaq computer, the conclusion was reached that the system couldn’t find a hint of Broadcom wireless hardware. That prompted some fear the wireless module had been bricked. The computer was turned off while the attempt was made from another computer to set up a memory stick with a live version of SuSE 12.1.

In that effort, booted a live 12.1. Couldn’t use the GUI, but switched to a command line and attempted to install_bcm43xx_firmware, only to receive the notice that the firmware software for b43 was listed but a file could not be found in the repository for SuSE 12.1. After that, and after frustration with attempting to load alternative SuSE Live versions on the memory stick, the latter which was suddenly write-protected and unable to accept writes from imagewriter, the at-rest Compaq was again restarted with SuSE 12.3.

Probably due to a previous reconfiguration (Traditional use of Ifup unselected in Yast Network), the wireless lights suddenly came to life, and the wireless function returned to operation as if nothing had ever happened. Wireless is again working, but why it disappeared and couldn’t be more easily restored will remain a mystery of call backs and who knows what sort of component interface synchronization.

For the record, the device is:
Device: BCM4312 802.11a/b/g pci/ssb
Subvendor Identifier 69692
Subvendor: Hewlett-Packard Company
Vendor Identifier: 70884
Vendor: Broadcom

At any rate, thank you for your attention and response!

Not sure if you are saying that you turned ifup ON or OFF.

I tried Network Manager a few years back, Did not like it, so I always make sure that I am using ifup. Now here are work I have to uninstall it, because some computers hang on boot saying Network Manager dependency failed. Even though the network settings are configured for ifup and services has Network Manager disabled, systemd still wants Network Manager at boot.

Dave W

On 2013-10-09 13:46, dwestf wrote:

> Even though the network settings are configured for
> ifup and services has Network Manager disabled, systemd still wants
> Network Manager at boot.

That’s solvable, I think. Ask if you wish to try (another thread,
networking forum).


Cheers / Saludos,

Carlos E. R.
(from 11.4, with Evergreen, x86_64 “Celadon” (Minas Tirith))