Sorry, I am new to Linux and not quite sure what I am doing. I ran the install command as you recommended and got the message that “b43 firmware successfully installed.” However, my prompt didn’t come back as expected. Is this a Linux feature? Also, the KDE Network Manager still doesn’t show anything and the wireless is grayed out. The YaST Network Settings shows only the wired enp0s25 port. What else is missing? Thanks!
> Sorry, I am new to Linux and not quite sure what I am doing. I ran the
> install command as you recommended and got the message that “b43
> firmware successfully installed.” However, my prompt didn’t come back as
> expected. Is this a Linux feature? Also, the KDE Network Manager still
> doesn’t show anything and the wireless is grayed out. The YaST Network
> Settings shows only the wired enp0s25 port. What else is missing?
No, that is not a Linux feature. There is a bug in the b43 driver that affects
installation of the firmware. We can work around it with the following steps:
su -c "echo \"blacklist b43\" > /etc/modprobe.d/50-b43.conf"
That statement is a little tricky and it is best you copy and paste it. At this
point, reboot. Then
That last command should have shown your AP. If it says “Interface doesn’t
support scanning : Network is down” or some such statement, make certain that
your wireless switch is on. At this point, you should see a wireless device. If
not, then post the output of
Make sure that “User Controlled with NetworkManager” is enabled in the “Global Options” tab in YaST Network Settings. This is needed for the KDE Network Manager to work obviously.
Apparently you have set that to “Traditional Method with ifup”, otherwise YaST would give you a warning that NetworkManager is enabled.
Sorry, but now it seems to be really screwed up: The first blacklisting command was successful. However, rebooting no longer worked, as the hard drive was still running after stopping openSUSE, so I had to turn off and restart the computer. Then the new install did exactly the same by printing “b43 firmware successfully installed.” without returning the prompt. As for the rest, this is what I got:
Unfortunately, no change. The scan still provides the same:
linux-t741:/home/misi # sudo /usr/sbin/iwlist scan
enp0s25 Interface doesn’t support scanning.
On 01/04/2014 10:16 AM, mgl wrote:
>
>
> I am embarrassed, as I obviously did something stupid, but no idea what.
> Should I re-install the entire system and start from scratch?
Reinstallation will geet you back to exactly the same place as you are now.
I think the forced power off lost the blacklist file. That will sometimes happen
with new files and a crash.
As root, create a file named /etc/modprobe.d/50-b43.conf that contains the
following:
blacklist b43
blacklist ssb
Then issue the following:
sudo sync
sudo /sbin/reboot
After the system comes back up, run the command ‘lsmod | grep b43’. That should
produce no output. If it lists b43, then your blacklist file is not there, or
not correct.
Once you have verified that b43 is not loaded, then run the firmware
installation step again.
On 01/04/2014 12:16 PM, mgl wrote:
>
> wolfi323;2613633 Wrote:
>> Then it didn’t work again, so no wonder that your wireless is still not
>> working.
>>
>> Hm, maybe installing th firmware RPMs from Packman would work?
>> ‘PackMan :: Informationen zum Paket b43-firmware’
>> (http://packman.links2linux.de/package/b43-firmware)
>>
>> Your wired connection is working, right?
>> Then just type this to install that package:
>>>
> Code:
> --------------------
> > > sudo rpm -i http://packman.links2linux.de/download/b43-firmware/1567608/b43-firmware-4.174.64.19-3.1.noarch.rpm
> --------------------
>>>
>
> Unfortunately, no change. The scan still provides the same:
> linux-t741:/home/misi # sudo /usr/sbin/iwlist scan
> enp0s25 Interface doesn’t support scanning.
Until he gets the firmware installed, any mention of ifup, NetworkManager, or
anything else is just likely to confuse him.
I think you quoted the wrong post here. This one is just about installing the firmware…
But I just wanted to mention that thing because he might think his wireless is not working when in fact it is (and only NetworkManager not).
Now that would likely confuse him as well I think.
On 01/04/2014 04:16 PM, wolfi323 wrote:
> I think you quoted the wrong post here. This one is just about
> installing the firmware…
Yes, I did.
> But I just wanted to mention that thing because he might think his
> wireless is not working when in fact it is (and only NetworkManager
> not).
> Now that would likely confuse him as well I think.
He still does not have a wlan device, and that is the main symptom when the
firmware is not available.
b43 firmware successfully installed.
WARNING: All config files need .conf: /etc/modprobe.d/50-b43, it will be ignored in a future release.
WARNING: All config files need .conf: /etc/modprobe.d/50-b43, it will be ignored in a future release.
However, again without returning the prompt. The rest is the same as before:
linux-t741:/ # sudo rm /etc/modprobe.d/50-b43.conf
rm: cannot remove ‘/etc/modprobe.d/50-b43.conf’: No such file or directory
linux-t741:/ # sudo /usr/sbin/iwlist scan
enp0s25 Interface doesn’t support scanning.
lo Interface doesn’t support scanning.
So I am back to square one. Thanks again and sorry …
On 01/04/2014 08:16 PM, mgl wrote:
>
> lwfinger;2613672 Wrote:
>> On 01/04/2014 10:16 AM, mgl wrote:
>>>
>>>
>>> I am embarrassed, as I obviously did something stupid, but no idea
>> what.
>>> Should I re-install the entire system and start from scratch?
>>
>> Reinstallation will geet you back to exactly the same place as you are
>> now.
>>
>> I think the forced power off lost the blacklist file. That will
>> sometimes happen
>> with new files and a crash.
>>
>> As root, create a file named /etc/modprobe.d/50-b43.conf that contains
>> the
>> following:
>>
>>>
> Code:
> --------------------
> > >
> > blacklist b43
> > blacklist ssb
> >
> --------------------
>>>
>>
>> Then issue the following:
>>
>>>
> Code:
> --------------------
> > >
> > sudo sync
> > sudo /sbin/reboot
> >
> --------------------
>>>
>>
>> After the system comes back up, run the command ‘lsmod | grep b43’.
>> That should
>> produce no output. If it lists b43, then your blacklist file is not
>> there, or
>> not correct.
>>
>> Once you have verified that b43 is not loaded, then run the firmware
>> installation step again.
>
> I crated the file:
>
> linux-t741:/etc/modprobe.d # ls
> 00-system.conf 50-blacklist.conf 50-cdc_ncm.conf
> 50-iwlagn.conf 50-sound.conf.YaST2save
> 50-alsa.conf 50-bluetooth.conf 50-ipw2200.conf
> 50-prism54.conf 99-local.conf
> 50-b43 50-broadcom-wl-blacklist.conf 50-iwl3945.conf
> 50-sound.conf
>
> Then synced and rebooted. However, I had to force reboot again, as the
> system didn’t come back.
>
> linux-t741:/ # lsmod | grep b43
> linux-t741:/ # sudo /usr/sbin/install_bcm43xx_firmware
>
> returned:
>
> b43 firmware successfully installed.
> WARNING: All config files need .conf: /etc/modprobe.d/50-b43, it will be
> ignored in a future release.
> WARNING: All config files need .conf: /etc/modprobe.d/50-b43, it will be
> ignored in a future release.
>
> However, again without returning the prompt. The rest is the same as
> before:
>
> linux-t741:/ # sudo rm /etc/modprobe.d/50-b43.conf
> rm: cannot remove ‘/etc/modprobe.d/50-b43.conf’: No such file or
> directory
> linux-t741:/ # sudo /usr/sbin/iwlist scan
> enp0s25 Interface doesn’t support scanning.
>
>
> lo Interface doesn’t support scanning.
>
> So I am back to square one. Thanks again and sorry …
Apparently you named the file 50-b43 rather than 50-b43.conf. That doesn’t
matter as the system still recognizes them.
When the system failed to come back after a reboot, what happened?
Because b43 was not loaded, the problem I was trying to fix cannot have caused
the problem. I have no idea what is happening; however, you are having a number
of strange problems. Perhaps you should reinstall.
Again, I am a novice, so I would appreciate if you could describe step-by-step how to set up the wireless after I run the installation the 3rd time. Is there anything I need to be careful while installing? Partitions, other installed OS, etc. Thanks!
Yes, I know.
But his question (to which I replied) was:
This would suggest that NetworkManager is not running IMHO, so KDE’s networkmanagement applet won’t ever show any wireless.
Well, do you still have that b43-firmware package from Packman installed, or did you do a fresh install since then?
If it’s still there, try to remove the file /etc/modprobe.d/50-b43:
sudo rm /etc/modprobe.d/50-b43
And apparently you also tried to install the broadcom-wl packages because you have a file 50-broadcom-wl-blacklist.conf as well.
This of course blocks the b43 driver, so uninstall those by running YaST->Software Management, type broadcom-wl into the search field and mark all found packages for removal.
Maybe it is working then after a reboot?
(try the iwlist and rfkill commands then to check)
This has not only failed to fix the problem, but I created a much bigger one: The reboot required again forced booting and I lost other drivers as well (mouse, keybord, …) after that. I tried to reinstall open SUSE, but the installation broke down and now the system wouldn’t boot at all. I got the “grub rescue>” prompt. “ls” provides (hd0) (hd0,msdos1, 2, 3 and 5) (hd1) (hd1,msdos1, 2, and 3), but insmod with anything provides only “unknown filesystem”. It is a disaster …
By just doing what I wrote? You either removed some other stuff as well, or you have a hardware problem…
Or maybe you accidentally installed some other kernel (a *-base variant maybe?) which you booted afterwards.
You should have been able to boot the working kernel by choosing “Advanced Options” in the boot menu in that case.
I tried to reinstall open SUSE, but the installation broke down and now the system wouldn’t boot at all. I got the “grub rescue>” prompt. “ls” provides (hd0) (hd0,msdos1, 2, 3 and 5) (hd1) (hd1,msdos1, 2, and 3), but insmod with anything provides only “unknown filesystem”. It is a disaster …
So the boot loader is not installed correctly. Not very surprising if the installation did not work.
Could you explain more how “the installation broke down” please?
Maybe try to install again.
And I would say you should open a new thread for that, this has nothing to do with the wireless anymore.
Maybe the reason is my first attempt switching to Linux, as I installed first Ubuntu that had the same problem with rebooting. I tried then openSUSE that installed normally leaving Ubuntu installed. I also liked the interface better. However, after a while the rebooting issue surfaced with openSUSE as well. I cannot recall the exact installation problem, but after checking the system there was a warning that a file with a long cryptic name is corrupted. Skipping it wouldn’t continue with the installation and accepting it lead to a loop. After turning off the computer, I got grub prompt.
