B43 phy0 error found unsupported phy analog 10 type 8 lcn revision 1 - Исправление ошибок и поиск оптимальных решений проблем

For me, it was because my computer’s Broadcom wi-fi chip was not supported by the included open-source bcma kernel module driver. No wireless connection appeared when I ran ip link, so this definitely wasn’t a transient error message. I identified the wi-fi chip by running the lspci -k command (note: might have to use lsusb if the chip is connected via USB instead of PCI), then finding the line (usually the last) saying:

03:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4352 802.11ac Wireless Network Adapter (rev 03)
    Subsystem: ASUSTeK Computer Inc. Device 855c
    Kernel driver in use: bcma
    Kernel modules: bcma

The wi-fi chip is a BCM4352, and we’re trying to use the bcma kernel module to interface with it. According to this page on kernel.org, the BCM4352 chip is not supported by the default bcma kernel module; you have to use the restrictively-licensed broadcom-wl kernel module instead. The installation process for this driver varies depending on your distro; here were the directions I used for Arch Linux.

Once you install broadcom-wl you’ll have two kernel modules competing to service your wi-fi chip — wl and bcma. You can see this by running lspci -k and seeing:

03:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4352 802.11ac Wireless Network Adapter (rev 03)
    Subsystem: ASUSTeK Computer Inc. Device 855c
    Kernel driver in use: wl
    Kernel modules: bcma, wl

To prevent conflicts you’ll want to blacklist the bcma kernel module. I did this by following the directions on the Arch Linux wiki here, creating a file at /etc/modprobe.d/nobcma.conf containing:

# Do not load the 'bcma' module on boot.
blacklist bcma

After rebooting you can run dmesg | grep bcma to check that it isn’t loaded, and dmesg | grep wl to ensure wl is loaded (along with some messages about the kernel being tainted by the proprietary code!)

I can now run ip link and see the wireless link exists:

...
3: wlp3s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/ether 54:27:1e:30:26:61 brd ff:ff:ff:ff:ff:ff

Источник

Печать

Страницы: [1] Вниз

Тема: b43-phy0 ERROR (Прочитано 2418 раз)

0 Пользователей и 1 Гость просматривают эту тему.

nullNull

Нет Wi-Fi, при аппаратном включении модуля в терминале показывается сообщение

b43-phy0 ERROR: Firmware file "b43/ucode5.fw" not found b43-phy0 ERROR: Firmware file "b43-open/ucode.fw" not found b43-phy0 ERROR: You must go to http://wireless.kernel.org/en/users/Drivers/b43#devicefirmware and download the correct firmware for this driver version. Please carefully read all instructions on this website.Пошёл на указанный сайт, нашёл, что нужно установить firmware-b43-installer:

sudo apt-get install firmware-b43-installerОднако Интернета нет, поэтому скачать на болеющий компьютер возможности нет. Есть какая-нибудь возможность скачать нужный пакет с другого компа и перенести на свой?

Спасибо за помощь , полный нуб, поймите
Ubuntu 12.4.1, ноут Lenovo B550

vasyl

Есть какая-нибудь возможность скачать нужный пакет с другого компа и перенести на свой?

Не уверен, но может b43/ucode5.fw и b43-open/ucode.fw закинуть в папку /lib/firmware ?
А, нет:

export FIRMWARE_INSTALL_DIR=»/lib/firmware»
wget http://www.lwfinger.com/b43-firmware/broadcom-wl-5.100.138.tar.bz2
tar xjf broadcom-wl-5.100.138.tar.bz2
sudo b43-fwcutter -w «$FIRMWARE_INSTALL_DIR» broadcom-wl-5.100.138/linux/wl_apsta.o

http://wireless.kernel.org/en/users/Drivers/b43
На компе с инетом :

wget http://www.lwfinger.com/b43-firmware/broadcom-wl-5.100.138.tar.bz2На компе без :

export FIRMWARE_INSTALL_DIR="/lib/firmware" tar xjf broadcom-wl-5.100.138.tar.bz2 sudo b43-fwcutter -w "$FIRMWARE_INSTALL_DIR" broadcom-wl-5.100.138/linux/wl_apsta.o

« Последнее редактирование: 26 Марта 2014, 21:07:58 от vasyl »

Ubuntu Mate 16.04 + Windows 10

nullNull

Есть какая-нибудь возможность скачать нужный пакет с другого компа и перенести на свой?

Не уверен, но может b43/ucode5.fw и b43-open/ucode.fw закинуть в папку /lib/firmware ?

а где я их возьиму я это спрашиваю

vasyl

« Последнее редактирование: 26 Марта 2014, 22:46:15 от vasyl »

Ubuntu Mate 16.04 + Windows 10

nullNull

Добавил пост выше.

гуд. Завтро попробую

Пользователь решил продолжить мысль 27 Марта 2014, 14:21:34:

…
На компе без :
export FIRMWARE_INSTALL_DIR="/lib/firmware" tar xjf broadcom-wl-5.100.138.tar.bz2 sudo b43-fwcutter -w "$FIRMWARE_INSTALL_DIR" broadcom-wl-5.100.138/linux/wl_apsta.o

В последнем ошибка при выполнении: не установлен b43-fwcutter причём при поиске в репозитории не нашёл ссылку для скачивания http://packages.ubuntu.com/search?keywords=b43-fwcutter&searchon=names&section=all

« Последнее редактирование: 27 Марта 2014, 14:21:34 от Dimon4ezzz »

Печать

Страницы: [1] Вверх

Источник

View previous topic :: View next topic

Author

Message

alpage2
n00b
n00b

Joined: 25 Apr 2004
Posts: 31
Location: UK

Posted: Mon Jun 07, 2021 7:38 pm Post subject: [SOLVED] Broadcom BCM4313 not working

I have recently installed gentoo on an old 32-bit netbook: Aspire One D-260A.

I seem to have succeeded — it is error free when I do deep world updates, and I have xorg and an xfce interface working, using the ‘desktop’ profile.

The sole exception is the broadcom wifi adapter — I just don’t seem to have the kernel configured right, despite following the details in the gentoo wifi and kernel wikis. I couldn’t find anything to help further on the gentoo forum.

The broadcom wifi adapter works fine when the system is booted with the minimum install disk, so I know it is working. As will be obvious from the outputs below, after booting, the wifi adapter is not detected.

I am not using an initramfs file — could that be the problem?

Can someone more experienced guide me to a working system? I expect it is something obvious, but I just can’t see it.

Some hardware details:

Code:

# lspci

00:00.0 Host bridge: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx DMI Bridge

00:02.0 VGA compatible controller: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller

00:02.1 Display controller: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller

00:1b.0 Audio device: Intel Corporation NM10/ICH7 Family High Definition Audio Controller (rev 02)

00:1c.0 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 1 (rev 02)

00:1c.1 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 2 (rev 02)

00:1d.0 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #1 (rev 02)

00:1d.1 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #2 (rev 02)

00:1d.2 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #3 (rev 02)

00:1d.3 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #4 (rev 02)

00:1d.7 USB controller: Intel Corporation NM10/ICH7 Family USB2 EHCI Controller (rev 02)

00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)

00:1f.0 ISA bridge: Intel Corporation NM10 Family LPC Controller (rev 02)

00:1f.2 SATA controller: Intel Corporation NM10/ICH7 Family SATA Controller [AHCI mode] (rev 02)

00:1f.3 SMBus: Intel Corporation NM10/ICH7 Family SMBus Controller (rev 02)

01:00.0 Ethernet controller: Qualcomm Atheros AR8132 Fast Ethernet (rev c0)

02:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4313 802.11bgn Wireless Network Adapter (rev 01)

The tail end of dmesg was the first sign of the problem:

Code:

[ 11.924744] ACPI: Video Device [OVGA] (multi-head: yes rom: no post: no)

[ 12.022130] cfg80211: Loading compiled-in X.509 certificates for regulatory database

[ 12.031615] cfg80211: Loaded X.509 cert ‘sforshee: 00b28ddf47aef9cea7’

[ 12.130459] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2

[ 12.130468] cfg80211: failed to load regulatory.db

[ 12.239211] acpi device:24: registered as cooling_device3

[ 12.239479] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input12

[ 12.266504] fbcon: i915drmfb (fb0) is primary device

[ 12.300712] Console: switching to colour frame buffer device 128×37

[ 12.324416] i915 0000:00:02.0: [drm] fb0: i915drmfb frame buffer device

[ 12.466534] b43-phy0: Broadcom 4313 WLAN found (core revision 24)

[ 12.467431] b43-phy0 ERROR: FOUND UNSUPPORTED PHY (Analog 10, Type 8 (LCN), Revision 1)

[ 12.467471] b43: probe of bcma0:1 failed with error -95

[ 12.467611] Broadcom 43xx driver loaded [ Features: PNL ]

[ 13.972180] EXT4-fs (sda4): re-mounted. Opts: (null)

[ 14.379025] Adding 1048572k swap on /dev/sda3. Priority:-2 extents:1 across:1048572k

[ 14.507604] EXT4-fs (sda2): mounting ext2 file system using the ext4 subsystem

[ 14.526840] EXT4-fs (sda2): mounted filesystem without journal. Opts: (null)

[ 14.526864] ext2 filesystem being mounted at /boot supports timestamps until 2038 (0x7fffffff)

[ 18.499748] udevd (565) used greatest stack depth: 5288 bytes left

So it seems the firmware for regulatory.db failed. I had followed the advice to make the b43xx driver a module to avoid this problem — so I am uncertain where this went wrong.

I see the Broadcom 43xx driver loaded, after various errors associated with 43 were reported — but the significance of that is lost on me.

I did try to emerge the broadcom-sta package, for good measure, but emerge reported that it was masked by the ~x86 keyword, I presume for good reason.

My list of modules is pretty small — I was trying to compile everything but the wifi modules into the kernel.

The ralink drivers are included because I was trying to get a ralink usb wifi adapter working as an alternative — again without success.

Code:

# lsmod

/lib/modules/5.10.27-gentoo/modules.builtin.modinfo

/lib/modules/5.10.27-gentoo/kernel/fs/ntfs/ntfs.ko

/lib/modules/5.10.27-gentoo/kernel/crypto/aes_ti.ko

/lib/modules/5.10.27-gentoo/kernel/net/wireless/cfg80211.ko

/lib/modules/5.10.27-gentoo/kernel/net/mac80211/mac80211.ko

/lib/modules/5.10.27-gentoo/kernel/lib/crypto/libarc4.ko

/lib/modules/5.10.27-gentoo/kernel/drivers/thermal/intel/x86_pkg_temp_thermal.ko

/lib/modules/5.10.27-gentoo/kernel/drivers/gpu/drm/gma500/gma500_gfx.ko

/lib/modules/5.10.27-gentoo/kernel/drivers/gpu/drm/ttm/ttm.ko

/lib/modules/5.10.27-gentoo/kernel/drivers/gpu/drm/i915/i915.ko

/lib/modules/5.10.27-gentoo/kernel/drivers/net/wireless/ralink/rt2x00/rt2x00usb.ko

/lib/modules/5.10.27-gentoo/kernel/drivers/net/wireless/ralink/rt2x00/rt2800usb.ko

/lib/modules/5.10.27-gentoo/kernel/drivers/net/wireless/ralink/rt2x00/rt2x00lib.ko

/lib/modules/5.10.27-gentoo/kernel/drivers/net/wireless/ralink/rt2x00/rt2800lib.ko

/lib/modules/5.10.27-gentoo/kernel/drivers/net/wireless/broadcom/b43/b43.ko

I also included the following in /etc/modules-load.d/network.conf

Code:

mac80211.ko

cfg80211.ko

b43.ko

but not necessarily in that order — does order make any difference? (grasping at straws here)

For comparison, the following is the matching outputs after booting the system with the minimum install disk:

Tail of dmesg from minimum install disk:

Code:

[ 74.182830] brcmsmac bcma0:1: brcms_ops_bss_info_changed: qos enabled: false (implement)

[ 74.182844] brcmsmac bcma0:1: brcms_ops_config: change power-save mode: false (implement)

[ 74.594846] NET: Registered protocol family 10

[ 74.597656] Segment Routing with IPv6

[ 133.666505] wlp2s0b1: authenticate with a0:bd:cd:4a:12:f2

[ 133.668350] wlp2s0b1: send auth to a0:bd:cd:4a:12:f2 (try 1/3)

[ 133.669909] wlp2s0b1: authenticated

[ 133.673191] wlp2s0b1: associate with a0:bd:cd:4a:12:f2 (try 1/3)

[ 133.677221] wlp2s0b1: RX AssocResp from a0:bd:cd:4a:12:f2 (capab=0x1411 status=0 aid=1)

[ 133.678468] brcmsmac bcma0:1: brcmsmac: brcms_ops_bss_info_changed: associated

[ 133.678474] brcmsmac bcma0:1: brcms_ops_bss_info_changed: qos enabled: true (implement)

[ 133.678492] wlp2s0b1: associated

[ 133.684410] brcmsmac bcma0:1: wl0: brcms_c_d11hdrs_mac80211: txop exceeded phylen 159/256 dur 1778/1504

[ 133.689981] brcmsmac bcma0:1: wl0: brcms_c_d11hdrs_mac80211: txop exceeded phylen 137/256 dur 1602/1504

[ 133.884696] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0b1: link becomes ready

[ 139.753704] brcmsmac bcma0:1: brcms_ops_bss_info_changed: arp filtering: 1 addresses (implement)

[ 173.551177] EXT4-fs (sda4): mounted filesystem with ordered data mode. Opts: (null)

[ 207.282715] EXT4-fs (sda2): mounting ext2 file system using the ext4 subsystem

[ 207.298830] EXT4-fs (sda2): mounted filesystem without journal. Opts: (null)

[ 207.298853] ext2 filesystem being mounted at /mnt/gentoo/boot supports timestamps until 2038 (0x7fffffff)

[ 239.724802] Adding 1048572k swap on /dev/sda3. Priority:-2 extents:1 across:1048572k

[ 2128.217287] brcmsmac bcma0:1: wl0: brcms_c_d11hdrs_mac80211: txop exceeded phylen 153/256 dur 1730/1504

[ 5727.669668] brcmsmac bcma0:1: wl0: brcms_c_d11hdrs_mac80211: txop exceeded phylen 153/256 dur 1730/1504

[ 9331.495216] brcmsmac bcma0:1: wl0: brcms_c_d11hdrs_mac80211: txop exceeded phylen 153/256 dur 1730/1504

[ 9331.890063] brcmsmac bcma0:1: wl0: brcms_c_d11hdrs_mac80211: txop exceeded phylen 153/256 dur 1730/1504

[ 9331.890450] brcmsmac bcma0:1: wl0: brcms_c_d11hdrs_mac80211: txop exceeded phylen 153/256 dur 1730/1504

[12927.806089] brcmsmac bcma0:1: wl0: brcms_c_d11hdrs_mac80211: txop exceeded phylen 153/256 dur 1730/1504

[16528.523952] brcmsmac bcma0:1: wl0: brcms_c_d11hdrs_mac80211: txop exceeded phylen 153/256 dur 1730/1504

[20127.963376] brcmsmac bcma0:1: wl0: brcms_c_d11hdrs_mac80211: txop exceeded phylen 153/256 dur 1730/1504

[23728.653276] brcmsmac bcma0:1: wl0: brcms_c_d11hdrs_mac80211: txop exceeded phylen 153/256 dur 1730/1504

And the list of modules after booting with the minimum install disk:

Code:

# lsmod

Module Size Used by

ctr 16384 3

ccm 20480 9

ipv6 270336 18

8021q 24576 0

brcmsmac 421888 0

brcmutil 16384 1 brcmsmac

b43 339968 0

cordic 16384 2 brcmsmac,b43

mac80211 417792 2 brcmsmac,b43

sha256_generic 16384 0

libsha256 24576 1 sha256_generic

cfg80211 393216 3 brcmsmac,b43,mac80211

snd_hda_codec_realtek 77824 1

snd_hda_codec_generic 45056 1 snd_hda_codec_realtek

ledtrig_audio 16384 2 snd_hda_codec_generic,snd_hda_codec_realtek

snd_hda_intel 24576 0

ssb 45056 1 b43

snd_intel_nhlt 16384 1 snd_hda_intel

snd_hda_codec 65536 3 snd_hda_intel,snd_hda_codec_generic,snd_hda_codec_realtek

acer_wmi 16384 0

mmc_core 90112 2 b43,ssb

snd_hda_core 45056 4 snd_hda_intel,snd_hda_codec,snd_hda_codec_generic,snd_hda_codec_realtek

sparse_keymap 16384 1 acer_wmi

pcmcia 32768 1 ssb

pcmcia_core 20480 1 pcmcia

snd_pcm 61440 3 snd_hda_intel,snd_hda_codec,snd_hda_core

rfkill 20480 3 acer_wmi,cfg80211

libarc4 16384 1 mac80211

snd_timer 24576 1 snd_pcm

i2c_i801 20480 0

wmi_bmof 16384 0

i2c_core 45056 1 i2c_i801

lpc_ich 24576 0

snd 45056 5 snd_hda_intel,snd_hda_codec,snd_timer,snd_hda_codec_generic,snd_pcm

mfd_core 16384 1 lpc_ich

bcma 36864 2 brcmsmac,b43

soundcore 16384 1 snd

wmi 20480 2 wmi_bmof,acer_wmi

ac 16384 0

video 36864 1 acer_wmi

backlight 16384 2 video,acer_wmi

button 16384 0

battery 20480 0

thermal 16384 0

fan 16384 0

acpi_cpufreq 16384 1

usb_storage 40960 1

ahci 32768 3

libahci 24576 1 ahci

libata 155648 2 ahci,libahci

uhci_hcd 24576 0

atl1c 32768 0

ehci_pci 16384 0

ehci_hcd 40960 1 ehci_pci

Is there an other output or information that would be helpful?

Many thanks in anticipation.

Alan

Last edited by alpage2 on Fri Jun 25, 2021 4:45 pm; edited 1 time in total

fedeliallalinea
Administrator

Joined: 08 Mar 2003
Posts: 29426
Location: here

Posted: Mon Jun 07, 2021 7:53 pm Post subject:

I think that for BCM4313 you need to install net-wireless/broadcom-sta _________________ Questions are guaranteed in life; Answers aren’t.

alamahant
Advocate

Joined: 23 Mar 2019
Posts: 3304

Posted: Mon Jun 07, 2021 8:05 pm Post subject:

You need firmware also.

Maybe.

Code:

emerge -av linux-firmware

Do you have these in your .config

Code:

CONFIG_NET_VENDOR_BROADCOM=y

CONFIG_BROADCOM_PHY=m

CONFIG_WLAN_VENDOR_BROADCOM=y

CONFIG_B43=m

CONFIG_B43_BCMA=y

CONFIG_B43_SSB=y

CONFIG_B43_BUSES_BCMA_AND_SSB=y

# CONFIG_B43_BUSES_BCMA is not set

# CONFIG_B43_BUSES_SSB is not set

CONFIG_B43_PCI_AUTOSELECT=y

CONFIG_B43_PCICORE_AUTOSELECT=y

CONFIG_B43_SDIO=y

CONFIG_B43_BCMA_PIO=y

CONFIG_B43_PIO=y

CONFIG_B43_PHY_G=y

CONFIG_B43_PHY_N=y

CONFIG_B43_PHY_LP=y

CONFIG_B43_PHY_HT=y

CONFIG_B43_LEDS=y

CONFIG_B43_HWRNG=y

# CONFIG_B43_DEBUG is not set

CONFIG_B43LEGACY=m

CONFIG_B43LEGACY_PCI_AUTOSELECT=y

CONFIG_B43LEGACY_PCICORE_AUTOSELECT=y

CONFIG_B43LEGACY_LEDS=y

CONFIG_B43LEGACY_HWRNG=y

CONFIG_B43LEGACY_DEBUG=y

CONFIG_B43LEGACY_DMA=y

CONFIG_B43LEGACY_PIO=y

CONFIG_B43LEGACY_DMA_AND_PIO_MODE=y

# CONFIG_B43LEGACY_DMA_MODE is not set

# CONFIG_B43LEGACY_PIO_MODE is not set

CONFIG_SSB_B43_PCI_BRIDGE=y

_________________

mustafasalih1993
n00b
n00b

Joined: 09 Feb 2021
Posts: 38

Posted: Mon Jun 07, 2021 8:15 pm Post subject:

some useful tips for you:

— enable «Broadcom 43xx wireless support» as a module in your kernel

— install net-wireless/broadcom-sta

— blacklist b43/bcma, add the following in your /etc/modprobe.d/blacklist.conf

Code:

blacklist b43

blacklist bcma

Ralphred
Guru
Guru

Joined: 31 Dec 2013
Posts: 409

Posted: Mon Jun 07, 2021 11:51 pm Post subject:

Quote:

Direct firmware load for regulatory.db failed with error -2

From memory -2 is ENOENT or «no such directory entry»; do you have net-wireless/wireless-regdb installed, it should be pulled in by wpa-supplicant, that’s what supplies the two /lib/firmware/regulatory.db* files?

You’ll need sys-firmware/b43-firmware installed (along with sys-kernel/linux-firmware for brcm/bcm43xx*.fw I think). The list of firmware referenced in /usr/src/linux-5.10.27-gentoo/drivers/net/wireless/broadcom/b43/main.c is massive, so it’s not as easy to dissect as graphics drivers to give you a list of needed fw from a device ID.

Seeing as it works on the livecd you can check what is blacklisted, though I suspect nothing. Searching through the livecd’s dmesg should let you see a full list of firmware files loaded too.

Once you know what firmware files are needed, you can add them as

Code:

CONFIG_EXTRA_FIRMWARE=»regulatory.db regulatory.db.p7s some/broadcom/ucode-1.fw … some/broadcom/ucode-n.fw»

in your .config and set your modules back to yes if you like.

I always struggle to remember where the «extra_firmware» in menuconfig is, so it’s here

Code:

Prompt: Build named firmware blobs into the kernel binary │

│ Location: │

│ -> Device Drivers │

│ -> Generic Driver Options │

│ -> Firmware loader │

│ (1) -> Firmware loading facility

alpage2
n00b
n00b

Joined: 25 Apr 2004
Posts: 31
Location: UK

Posted: Tue Jun 08, 2021 6:45 pm Post subject:

Many thanks to everyone for the detailed feedback. Due to limited access to this machine, and limited time, it may take some time to work through all the checks and changes, but I will post back here on progress, as time goes by. So far, net-wireless/broadcom-sta has been unmasked and emerged, and b43 and bcma drivers blacklisted. I’ll amend my .config file next, and recompile the kernel. Thanks again.

alpage2
n00b
n00b

Joined: 25 Apr 2004
Posts: 31
Location: UK

Posted: Fri Jun 25, 2021 4:55 pm Post subject:

Making use of all the hints above, I modified the kernel configuration and recompiled the kernel, and the broadcom adapter is now working fine. In the end I did not need to do any blacklisting, or the listing of individual firmware files. With the right kernel modules, and the simplest example of handling WPA-PSK in wpa_supplicant.conf from the Gentoo Handbook, I was online by the end of booting up. Thanks again for all the help.

Display posts from previous:

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum

Источник

Dan158: Posts: 56; Joined: 2011-03-20 02:34

Wireless Killed; update to blame. [ RESOLVED ]

Post

by Dan158 » 2014-11-05 08:46

SEE BOTOM POST FOR RESOLUTION

After my last update (this morning) my laptop refuses to start the same wlan0 wireless connection I updated it over.
I am at my wits end … yeah, it may have been a short trip , but still.

This is on an HP pavilion dv6 intel i5 laptop
uname -a;

Code: Select all

Linux xxxxx 3.17-2.dmz.1-liquorix-686-pae #1 ZEN SMP PREEMPT Debian 3.17-2 (2014-10-31) i686 GNU/Linux

note; wireless worked on kernel 3.17-1.dmz.1-liquorix-686-pae as well and now it doesn’t.
2nd note; this update reset 2 of my desktops LXDE and Xfce to defaults across the board, erased Openbox-Xfce, and made Openbox loose some of its settings like bkground etc but not the menu settings I had created.
3rd note; my NetworkManager app that I had set up to handle my wireless connection to my router is still set up … ssid, pword, and all.

I have a strange message on boot now too. It is in this block of ~/$ dmesg | less;

Code: Select all

[   12.900576] Adding 3905532k swap on /dev/sda3.  Priority:-1 extents:1 across:3905532k FS
[   13.026523] cfg80211: Calling CRDA to update world regulatory domain
[   13.684702] b43-phy0: Broadcom 4313 WLAN found (core revision 24)

[   13.685569] b43-phy0 ERROR: FOUND UNSUPPORTED PHY (Analog 10, Type 8 (LCN), Revision 1)
[   13.685621] b43: probe of bcma0:0 failed with error -95

[   13.685645] Broadcom 43xx driver loaded [ Features: PMNLS ]
[   13.997609] brcmsmac bcma0:0: mfg 4bf core 812 rev 24 class 0 irq 16
[   14.054484] ieee80211 phy1: Selected rate control algorithm 'minstrel_ht'
[   14.054845] ieee80211 phy1: registered radio enabled led device: brcmsmac-phy1:radio gpio: 243

I’ve searched for some kind of answer and found something here that might have something to do with it;

however they’re discusing eth not wlan so I figured I’d throw that in here on the off chance it had something to do with my situation.

here is my ifconfig, both before and after a ‘sudo ifconfig wlan0 up’ command;

Code: Select all

:~/Desktop$ sudo ifconfig
eth0      Link encap:Ethernet  HWaddr xx:xx:xx:xx:xx:xx 
          inet addr:192.168.1.2  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: xxx::XXX:XXXxx:xx:xxx/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:7 errors:0 dropped:0 overruns:0 frame:0
          TX packets:59 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:50 
          RX bytes:1421 (1.3 KiB)  TX bytes:8826 (8.6 KiB)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:41 errors:0 dropped:0 overruns:0 frame:0
          TX packets:41 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:3984 (3.8 KiB)  TX bytes:3984 (3.8 KiB)

wlan0     Link encap:Ethernet  HWaddr xx:xx:xx:xx:xx:xx 
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:50 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

xxxx@xxxx:~/Desktop$ man ifconfig
xxxx@xxxx:~/Desktop$ sudo ifconfig wlan0 up
xxxx@xxxx:~/Desktop$ sudo ifconfig
eth0      Link encap:Ethernet  HWaddr xx:xx:xx:xx:xx:xx 
          inet addr:192.168.1.2  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: xxx::XXX:XXXxx:xx:xxx/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:7 errors:0 dropped:0 overruns:0 frame:0
          TX packets:61 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:50 
          RX bytes:1421 (1.3 KiB)  TX bytes:9020 (8.8 KiB)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:41 errors:0 dropped:0 overruns:0 frame:0
          TX packets:41 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:3984 (3.8 KiB)  TX bytes:3984 (3.8 KiB)

wlan0     Link encap:Ethernet  HWaddr xx:xx:xx:xx:xx:xx 
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:50 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

and to add insult to injury on the wireless front I also can’t get my Raspberry Pi’s to connect on Their wireless UNLESS The Ethernet cable is plugged into them. That is probably unrelated to my laptop …. although, they are running the Debian OS ‘Raspbian’.

Thanks for any helpful hints or thoughts you can send my way. A laptop without wireless is kind of sad.

Last edited by Dan158 on 2014-12-16 09:26, edited 5 times in total.

‘Help-Fascists’;
Slanderers of the poor, frustrated & comp ignorant as «help-vampires»
who seek to ostracize the victim. As IRL; ‘Vamps’ Are increadibly rare.
Fascists though … well, They’re a dime a dozen.

stevepusser: Posts: 12651; Joined: 2009-10-06 05:53; Has thanked: 21 times; Been thanked: 33 times

Re: Wireless Killed; update to blame.

Post

by stevepusser » 2014-11-05 17:12

Do you still have the standard Jessie kernel installed, so that you can boot to it as a test to see if the wireless works?

If it really is a kernel issue, it maybe should be brought up in the Liquorix forums, not here,,,maybe Steve just misconfigured something.

MX Linux packager and developer

Dan158: Posts: 56; Joined: 2011-03-20 02:34

Re: Wireless Killed; update to blame.

Post

by Dan158 » 2014-11-06 00:07

@ wizard10000; here is the output of 1wlist wlan0 scan;

Code: Select all

:~/$ sudo iwlist wlan0 scan ### neighbors personal info removed.

wlan0     Scan completed :
          Cell 01 - Address: xx:xx:xx:xx:xx:xx
                    Channel:1
  ### the majority of this is erased, (and was never posted), it is no longer needed. 
  ### This part posted to show that the scan did list the WiFi connections available              

          Cell 06 - Address: xx:xx:xx:xx:xx:xx
                    Channel:11
                    Frequency:2.462 GHz (Channel 11)
    ### also removed .......

@ stevepusser; I installed, and tested, the latest standard jessie kernel available in my synaptic (after refreshing the pacages). The problem is the same. I still cannot get the wireless to come back up, with my router ‘open’ or hidden.

@ all; As I I DL’ed the stock kernel to test it I got to thinking that maybe the Broadcom module had changed so I did a Synaptic search for «Broadcom Wireless» and found some new firmware listed that has the «b43» signature included in the boot-up warnings I had noticed.

Before the original posts mentioned update my wireless worked well with only the installed;

I’ve just installed;

Code: Select all

 b43-fwcutter
broadcom-sta-dkms
firmware-b43-installer

and now I can start my wireless with

The boot up warnings about ‘PHY’ have disapeared (leaving only an inscrutible; «BIOS is not set for KVM» ), so I’m going to list this as solved
it won’t connect on its own at boot yet but that is a minor problem that a little search-exorcise will readily shed some light on.

Thank you both for your input and questions, it helped me stumble onto the solution.

Dan158: Posts: 56; Joined: 2011-03-20 02:34

Re: Wireless Killed; update to blame. [NOT solved!!! damnit!

Post

by Dan158 » 2014-11-08 07:21

My WiFi worked with «:~/$ sudo ifconfig wlan0 up» that day, I even shut down my comp and started it up again … That day …. and WiFi still worked (with the «:~/$ sudo ifconfig wlan0 up»). I started my laptop today and …. it refuses to connect to my WiFi router! It doesn’t even recognise its existance. Yet I have a computer and Raspberry Pi connected via ssh over the routers WiFi!

What on earth Broke the working WiFi on my Laptop with the updates that came in the past week or two?!!???
It was working fine and I updated (kind of let the updates lag for a couple of weeks so it was a big one) and then This Crap started!
I seemed to fix it (see posts above) and now it wont work!! It is not magic, Something is doing this. Can you help me figure it out please?

here is iwconfig and ifconfig info;
sudo iwlist wlan0 scan;

Code: Select all

:~/Desktop$ sudo iwlist wlan0 scan
[sudo] password for XXX: 
wlan0     Scan completed :
          Cell 01 - Address: xx:xx:xx:xx:xx:xx
                    Channel:9
                    Frequency:2.452 GHz (Channel 9)
                    Quality=39/70  Signal level=-71 dBm  
                    Encryption key:on
                    ESSID:"xxxx"
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 9 Mb/s
                              18 Mb/s; 36 Mb/s; 54 Mb/s
                    Bit Rates:6 Mb/s; 12 Mb/s; 24 Mb/s; 48 Mb/s
                    Mode:Master
                    Extra:tsf=0000000000000000
                    Extra: Last beacon: 65ms ago
                    IE: Unknown: 0004486F6D65
                    IE: Unknown: 010882848B961224486C
                    IE: Unknown: 030109
                    IE: Unknown: 2A0104
                    IE: Unknown: 32040C183060
                    IE: Unknown: 2D1AEE1117FFFF000001000000000000000000000000000000000000
                    IE: Unknown: 3D1609070600000000000000000000000000000000000000
                    IE: Unknown: 3E0100
                    IE: WPA Version 1
                        Group Cipher : TKIP
                        Pairwise Ciphers (2) : TKIP CCMP
                        Authentication Suites (1) : PSK
                    IE: IEEE 802.11i/WPA2 Version 1
                        Group Cipher : TKIP
                        Pairwise Ciphers (2) : TKIP CCMP
                        Authentication Suites (1) : PSK
                    IE: Unknown: DD180050F2020101000003A4000027A4000042435E0062322F00
                    IE: Unknown: 0B05030015127A
                    IE: Unknown: 4A0E14000A002C01C800140005001900
                    IE: Unknown: 7F0101
                    IE: Unknown: DD07000C4300000000
                    IE: Unknown: 0706555320010B10
                    IE: Unknown: DDA50050F204104A0001101044000102103B00010310470010BC329E001DD811B286012A285D326EBC102100175A7958454C20546563686E6F6C6F67792C20436F72702E1023001B5A7958454C20576972656C6573732041636365737320506F696E74102400065254323836301042000831323334353637381054000800060050F2040001101100095A7958454C2041505310080002210C103C0001011049000600372A000120
          Cell 02 - Address: xx:xx:xx:xx:xx:xx
                    Channel:6
                    Frequency:2.437 GHz (Channel 6)
                    Quality=22/70  Signal level=-88 dBm  
                    Encryption key:on
                    ESSID:"xxxx"
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 9 Mb/s
                              18 Mb/s; 36 Mb/s; 54 Mb/s
                    Bit Rates:6 Mb/s; 12 Mb/s; 24 Mb/s; 48 Mb/s
                    Mode:Master
                    Extra:tsf=0000000000000000
                    Extra: Last beacon: 65ms ago
                    IE: Unknown: 000A41525249532D30374532
                    IE: Unknown: 010882848B961224486C
                    IE: Unknown: 030106
                    IE: Unknown: 32040C183060
                    IE: Unknown: 070C5553200101110209140B0111
                    IE: Unknown: 33082001020304050607
                    IE: Unknown: 33082105060708090A0B
                    IE: Unknown: 050400010010
                    IE: Unknown: 2A0104
                    IE: WPA Version 1
                        Group Cipher : TKIP
                        Pairwise Ciphers (1) : TKIP
                        Authentication Suites (1) : PSK
                    IE: Unknown: DD180050F2020101800003A4000027A4000042435E0062322F00
                    IE: Unknown: 0B05020013127A
                    IE: Unknown: DD07000C4307000000
          Cell 03 - Address: xx:xx:xx:xx:xx:xx
                    Channel:7
                    Frequency:2.442 GHz (Channel 7)
                    Quality=18/70  Signal level=-92 dBm  
                    Encryption key:on
                    ESSID:"xxxx"
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 9 Mb/s
                              18 Mb/s; 36 Mb/s; 54 Mb/s
                    Bit Rates:6 Mb/s; 12 Mb/s; 24 Mb/s; 48 Mb/s
                    Mode:Master
                    Extra:tsf=0000000000000000
                    Extra: Last beacon: 65ms ago
                    IE: Unknown: 000F43656E747572794C696E6B36323832
                    IE: Unknown: 010882848B961224486C
                    IE: Unknown: 030107
                    IE: Unknown: 32040C183060
                    IE: Unknown: 0706555320010B14
                    IE: Unknown: 33082001020304050607
                    IE: Unknown: 33082105060708090A0B
                    IE: Unknown: DD310050F204104A000110104400010110470010BC329E001DD811B28601FEF528297720103C0001011049000600372A000120
                    IE: Unknown: 050400010000
                    IE: Unknown: DD310050F204104A000110104400010110470010BC329E001DD811B28601FEF528297720103C0001011049000600372A000120
                    IE: Unknown: 2A0104
                    IE: Unknown: 2D1AEE1117FFFF000001000000000000000000000000000000000000
                    IE: Unknown: 3D1607070600000000000000000000000000000000000000
                    IE: Unknown: 4A0E14000A002C01C800140005001900
                    IE: Unknown: 7F0101
                    IE: WPA Version 1
                        Group Cipher : TKIP
                        Pairwise Ciphers (2) : TKIP CCMP
                        Authentication Suites (1) : PSK
                    IE: IEEE 802.11i/WPA2 Version 1
                        Group Cipher : TKIP
                        Pairwise Ciphers (2) : TKIP CCMP
                        Authentication Suites (1) : PSK
                    IE: Unknown: DD180050F2020101000003A4000027A4000042435E0062322F00
                    IE: Unknown: 0B05050017127A
                    IE: Unknown: DD07000C4300000000

xx@xxxx:~/Desktop$

My router is not even there, Niether of the routers frequencies 5GHz or 2.4GHz is recognised.

sudo ifconfig, then; sudo ifconfig wlan0 up, Then another sudo ifconfig;

Code: Select all

xxxx@xxx:~/Desktop$ sudo ifconfig
eth0      Link encap:Ethernet  HWaddr 78:ac:c0:54:f8:3e  
          inet addr:192.168.1.3  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::7aac:c0ff:fe54:f83e/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2531 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1803 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:50 
          RX bytes:2160973 (2.0 MiB)  TX bytes:240887 (235.2 KiB)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:45 errors:0 dropped:0 overruns:0 frame:0
          TX packets:45 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:4184 (4.0 KiB)  TX bytes:4184 (4.0 KiB)

wlan0     Link encap:Ethernet  HWaddr ac:81:12:2d:97:fc  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:78
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:50 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:16 

xxxx@xxx:~/Desktop$ sudo ifconfig wlan0 up
xxxx@xxx:~/Desktop$ 
xxxx@xxx:~/Desktop$ 
xxxx@xxx:~/Desktop$ sudo ifconfig
eth0      Link encap:Ethernet  HWaddr 78:ac:c0:54:f8:3e  
          inet addr:192.168.1.3  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::7aac:c0ff:fe54:f83e/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2531 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1803 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:50 
          RX bytes:2160973 (2.0 MiB)  TX bytes:240887 (235.2 KiB)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:45 errors:0 dropped:0 overruns:0 frame:0
          TX packets:45 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:4184 (4.0 KiB)  TX bytes:4184 (4.0 KiB)

wlan0     Link encap:Ethernet  HWaddr ac:81:12:2d:97:fc  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:78
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:50 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:16 

xxxx@xxx:~/Desktop$

sudo iwconfig;

Code: Select all

:~/Desktop$ sudo iwconfig
wlan0     IEEE 802.11abg  ESSID:off/any  
          Mode:Managed  Access Point: Not-Associated   Tx-Power=200 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          
lo        no wireless extensions.

eth0      no wireless extensions.

before I could go to a coffee shop and connect to their WiFi (didn’t, but I could) Now I dont have that laptop function. That is Not an «upgrade», that is bad.
If you can help with this; I appreaciate your time and effort.

I can’t be the only person this has effected either.

deltaflyer: Posts: 358; Joined: 2007-10-02 18:03; Location: EastAnglia,U.K.

Dan158: Posts: 56; Joined: 2011-03-20 02:34

Re: Wireless Killed; update to blame. [NOT solved!!! damnit!

Post

by Dan158 » 2014-11-08 08:52

right on Deltaflyer, here is the output of that (Highly usfull, thank you!);

Code: Select all

collectNWData.sh V0.7.4

--- Which type of your network connection should be tested?
--- (1) Wireless connection (WLAN)

--- What's the type of networktopology?
--- (2) WLAN HW router <---> LinuxClient

--- On which host is the script executed?
--- (1) LinuxClient
--- WLAN SSID to connect to: §§§§§§§§1

--- NWCollect is collecting networkconfiguration information into file ...

--- NWEliza is analyzing the system for common network configuration errors ...
!!! CND0120E: Network card wlan0 has no IP address
!!! CND0490E: No access point with your SSID detected on interface wlan0
!!! CND0450W: WLAN key masquerading is not fully tested on this distribution. Please check output file collectNWData.txt for visible WLAN keys and masquerade them manually

--- Go to http://www.linux-tips-and-tricks.de/CND#English to get more detailed instructions 
--- about the error/warning messages and how to fix the problems on your own.

--- If you are unsuccessful then place the contents of file collectNWData.txt in the net
--- (see http://www.linux-tips-and-tricks.de/CND_UPL#English for links) 
--- and then paste the nopaste link on your favorite Linux forum.

==================================================================================================================
===== cat /etc/*[-_]release || cat /etc/*[-_]version =============================================================
/etc/os-release
PRETTY_NAME="Debian GNU/Linux jessie/sid"
NAME="Debian GNU/Linux"
ID=debian
HOME_URL="http://www.debian.org/"
SUPPORT_URL="http://www.debian.org/support/"
BUG_REPORT_URL="https://bugs.debian.org/"
===== uname -a ===================================================================================================
Linux lptp 3.17-2.dmz.1-liquorix-686-pae #1 ZEN SMP PREEMPT Debian 3.17-2 (2014-10-31) i686 GNU/Linux
===== cat /etc/network/interfaces | grep -v "^#|^$" | grep -v "=''" ==============================================
--- /etc/network/interfaces
auto lo
iface lo inet loopback
===== ping tests =================================================================================================
Ping of 173.194.35.180 failed
Ping of www.google.com OK
===== cat /etc/resolv | grep -i "nameserver" =====================================================================
nameserver %%%.%%%.8.8
nameserver %%%.%%%.4.4
nameserver 192.168.1.1
===== cat /etc/hosts =============================================================================================
127.0.0.1	localhost
127.0.1.1	xxxx.xxxxx	xxxxx
===== (route -n && route -A inet6 -n) | egrep "(en|wl|eth|ath|ra|wlan|dsl|ppp)" ==================================
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         192.168.1.1     0.0.0.0         UG    0      0        0 eth0
0.0.0.0         192.168.1.1     0.0.0.0         UG    1024   0        0 eth0
169.254.0.0     0.0.0.0         255.255.0.0     U     1000   0        0 eth0
192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0
fe80::/64                      ::                         U    256 0     0 eth0
ff00::/8                       ::                         U    256 0     0 eth0
===== ifconfig (filtered for en|wl|eth|wlan|ra|ath|dsl|ppp) ======================================================
eth0      Link encap:Ethernet  HWaddr ##:##:##:##:##:#1  
          inet addr:192.168.1.3  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::7aac:c0ff:fe54:f83e/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:8531 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4799 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:50 
          RX bytes:9165670 (8.7 MiB)  TX bytes:494451 (482.8 KiB)
wlan0     Link encap:Ethernet  HWaddr ##:##:##:##:##:#2  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:78
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:50 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:16 
===== lspci ======================================================================================================
02:00.0 Network controller [0280]: Broadcom Corporation BCM4313 802.11bgn Wireless Network Adapter [14e4:4727] (rev 01)
	Subsystem: Hewlett-Packard Company Device [103c:145c]
	Kernel driver in use: wl
03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 03)
	Subsystem: Hewlett-Packard Company Device [103c:144c]
	Kernel driver in use: r8169
===== lsusb | grep -v "root hub" =================================================================================
Bus 002 Device 005: ID 0bda:5801 Realtek Semiconductor Corp. 
Bus 002 Device 004: ID 138a:0005 Validity Sensors, Inc. VFS301 Fingerprint Reader
Bus 002 Device 003: ID 14cd:8168 Super Top 
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 003: ID 1bcf:053e Sunplus Innovation Technology Inc. 
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
===== lsmod (filtered) ===========================================================================================
| ac              | af_packet       | ahci            | binfmt_misc     | cfg80211         |
| coretemp        | drm             | drm_kms_helper  | ehci_hcd        | ehci_pci         |
| evdev           | fscache         | hid_generic     | hp_accel        | hp_wmi           |
| i2c_algo_bit    | i2c_core        | i2c_i801        | i915            | input_polldev    |
| intel_gtt       | intel_ips       | intel_powerclamp| ipv6            | jbd2             |
| kvm             | libahci         | libata          | lis3lv02d       | lp               |
| lpc_ich         | mbcache         | media           | mii             | oid_registry     |
| ppdev           | r8169           | rfkill          | scsi_mod        | sd_mod           |
| serio_raw       | sg              | shpchp          | sparse_keymap   | sr_mod           |
| uas             | usb_storage     | v4l2_common     | wl              | wmi              |
===== iwconfig ===================================================================================================
eth0      no wireless extensions.
wlan0     IEEE 802.11abg  ESSID:off/any  
          Mode:Managed  Access Point: Not-Associated   Tx-Power=200 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
===== ls /lib/firmware/*.{fw,ucode,bin} ==========================================================================
| carl9170-1.fw           | usbdux_firmware.bin     | usbduxfast_firmware.bin | usbduxsigma_firmware.bin |
===== iwlist scanning (filtered) =================================================================================
                    Channel:9
                    Frequency:2.452 GHz (Channel 9)
                    Quality=41/70  Signal level=-69 dBm  
                    ESSID:"§§§§§§§§2"
                    Channel:6
                    Frequency:2.437 GHz (Channel 6)
                    Quality=22/70  Signal level=-88 dBm  
                    ESSID:"§§§§§§§§3"
===== ndiswrapper -l =============================================================================================
No ndiswrapper module loaded
===== Active processes ===========================================================================================
wpa_supplicant:YES networkmanager:YES nm-applet:NO
===== rfkill list wifi ===========================================================================================
0: hp-wifi: Wireless LAN
	Soft blocked: no
	Hard blocked: no
1: phy0: Wireless LAN
	Soft blocked: no
	Hard blocked: no
===== Actual date for bias of following greps ====================================================================
01:05:34 2014-11-08
===== grep -i radio /var/log/messages | tail -n 5 ================================================================
Nov  5 01:28:25 lptp kernel: ieee80211 phy1: registered radio enabled led device: brcmsmac-phy1:radio gpio: 243
Nov  5 01:34:26 lptp kernel: ieee80211 phy1: registered radio enabled led device: brcmsmac-phy1:radio gpio: 243
Nov  5 15:16:47 lptp kernel: ieee80211 phy1: registered radio enabled led device: brcmsmac-phy1:radio gpio: 243
Nov  5 15:19:07 lptp kernel: ieee80211 phy1: registered radio enabled led device: brcmsmac-phy1:radio gpio: 243
Nov  5 15:54:19 lptp kernel: ieee80211 phy1: registered radio enabled led device: brcmsmac-phy1:radio gpio: 243
===== dmesg | grep -i radio | tail -n 5 ==========================================================================
===== tail -n 300 /var/log/messages | /bin/grep -i firmware | tail -n 10 =========================================
Nov  7 22:45:06 lptp kernel: [Firmware Bug]: Invalid critical threshold (0)
===== egrep 'en|wl|eth|ath|wlan|ra|ppp' /etc/udev/rules.d/*net_persistent* /etc/udev/rules.d/*persistent-net* ====
/etc/udev/rules.d/70-persistent-net.rules:SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="##:##:##:##:##:#1", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
/etc/udev/rules.d/70-persistent-net.rules:SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="##:##:##:##:##:#2", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="wlan*", NAME="wlan0"
===== egrep -r '(en.*|wl.*|eth|ath|wlan|ra)[0-9]+' /etc/modprobe.*|egrep -v -i '#|blacklist' =====================
==================================================================================================================
*** NWElizaStates V0.7.4
PNIN:1 CFR:1 IF:eth0 IM:2 IF:wlan0 IM:1 DI:2 AP:1 FALON:1 NIC:1 cNiC:2:1 NI:2 cNI:2 NIW:wlan0-0 IP6:0 WLW:0 RTDT:debian GUI:0 UID:0

I see wpa_suplicant was added along the line somewhere, people have had trouble getting that to work at all on Raspberry Pi’s Debian OS ‘Raspbian’. I wonder, (in my amature lvl of knowlage), if that is part of the problem here.

Dan158: Posts: 56; Joined: 2011-03-20 02:34

Re: Wireless Killed; update to blame. [NOT solved!!! damnit!

Post

by Dan158 » 2014-11-08 20:12

I may have found the solution;

My /etc/network/interfaces file had only;

My searches led me to this page and the link in the ‘Answer’ section

Code: Select all

http://raspberrypi.stackexchange.com/questions/9257/whats-the-difference-between-wpa-roam-and-wpa-conf-in-the-etc-network-inte

'answer link';  http://manual.aptosid.com/en/inet-setup-en.htm

I read that page and followed some of its links BEFORE Trying anything (novel concept for me).
Ultimatly I folowed the instructions on the following pages, in order;

Code: Select all

http://manual.aptosid.com/en/nf-firm-en.htm#non-free-firmware
 ... apt-get update
 ... apt-get install firmware-linux firmware-linux-free firmware-linux-nonfree
 --- "$ fw-detect" did nothing; I read the rest of the page
 --- -- then went on to the next web-page in this list.
http://manual.aptosid.com/en/inet-ifplug-en.htm
http://manual.aptosid.com/en/inet-setup-en.htm
 ... part "To enable switching between wired and wireless networks" first
 ... then from the top to the "Bring up the wirless connection [ifup wlan0]"

the «Bring up the wirless connection [sudo ifup wlan0]» Failed but ‘sudo shutdown -r now’ brought my wireless up on reboot.

The question now remains; ‘Will it Work Tomorrow?’
I haven’t tested to see if it switches from eth0 to wlan0 and back on plug/unpluging the cable. I’m reveling in this small victory for a while first … then I’ll court further possible frustration.

Dan158: Posts: 56; Joined: 2011-03-20 02:34

Re: Wireless Killed; update to blame. [ ]

Post

by Dan158 » 2014-11-08 21:54

nope, didn’t work.

when I shutdown and restarted Again … it didn’t work.
I change my settings following somebodies instructions > shutdown > restart and my WiFi works That ONE Time.
If I shutdown > restart again WiFi refuses to start from then on.

strangely I actualy want to spend all this time Using my computer … not fighting to just get my WiFi back! (so much for all the linux recomendations I’ve given to people)

dilberts_left_nut: Administrator; Posts: 5402; Joined: 2009-10-05 07:54; Location: enzed; Has thanked: 6 times; Been thanked: 49 times

Re: Wireless Killed; update to blame. [ ]

Post

by dilberts_left_nut » 2014-11-08 23:26

Dan158 wrote:The question now remains; ‘Will it Work Tomorrow?’

Dan158 wrote:strangely I actualy want to spend all this time Using my computer … not fighting to just get my WiFi back!

Maybe running stable would be a better choice then, rather than testing (with a third-party kernel)?

AdrianTM wrote:There’s no hacker in my grandma…

Dan158: Posts: 56; Joined: 2011-03-20 02:34

Re: Wireless Killed; update to blame. [ ]

#10

Post

by Dan158 » 2014-11-09 03:46

dilberts_left_nut wrote:
Maybe running stable would be a better choice then, rather than testing (with a third-party kernel)?

Ahh, … yes. That would seem to be the lesson here.
I apologize; I did not mean to sound needy, greedy, or demanding.
I am frustrated that this once fine, and once working, Linux OS has beaten me, has tethered me to my router via Ethernet cables.
I am puzzled tha …. not your problem.
You are right in your suggestion Dilbers_genitalia; I should have attempted a downgrade to stable straight away.

I must have come across as whinny and demanding,
if so; I apologize.
You folks now know that at least one person has had unresolvable problems with the changes, in the past moth or less, to the wireless systems that the Debian OS’s are using. That is all the real use I can be apparently. I leave that info and the rest of the particulars people asked for (in posts above) on your desks and scuttle off.

As for my personal problem with wireless; I’ll try stable, if that wont work … well, … I’ll lurk around until I overhear something that gives me a clue as to how to fix it, or just wait it out till some update resolves it. Maybe KDE does things a bit different and it still works, or another Distro … my musings have no place here, sorry.

Thank you for the time you took to make a few requests for added info, wizard10000, stevepusser, and deltaflyer. And Thank You dilberts_left_nut for your gentle suggestion that it’s probably time for me to go. I’m not being passive-aggressive here, though it does sound it, just saying «thanks» as I close the door on my way out.
*(hinge creeeecks, gentle click door latching …. crickets)*

dilberts_left_nut: Administrator; Posts: 5402; Joined: 2009-10-05 07:54; Location: enzed; Has thanked: 6 times; Been thanked: 49 times

Re: Wireless Killed; update to blame. [ ]

#11

Post

by dilberts_left_nut » 2014-11-09 04:24

(laughing with you, not at you …)

To be fair, this is why many here discourage the use of testing for people who just want a working PC.
Most of the time it is fine but then something will happen that causes you downtime and frustration and work to get it going again.
This necessarily means developing an understanding of how the system works, where to find relevant info,
how to troubleshoot various subsystems, and having the time to do all this whenever necessary
(not really frequent, but freeze time is prime time).

If you want to fix it people will help, but bemoaning the fact that such things happen to a testing system is just silly.

AdrianTM wrote:There’s no hacker in my grandma…

Dan158: Posts: 56; Joined: 2011-03-20 02:34

Re: Wireless Killed; update to blame. [ ]

#12

Post

by Dan158 » 2014-11-09 05:15

dilberts_left_nut wrote: (laughing with you, not at you …)
…..
If you want to fix it people will help, but bemoaning the fact that such things happen to a testing system is just silly.

Clearly.
‘ To be fair’ I should have known that portion of the comment I made while tearing my hair out (figuratively);

Dan158 wrote:strangely I actually want to spend all this time Using my computer … not fighting to just get my WiFi back! (so much for all the Linux recommendations I’ve given to people)

would instantly colour me as a ‘Linux commoner far overreaching their station’ and relegate my entire thread to the /ignore bin, other than somebody or another taking the time to kindly school me as to why I shouldn’t reach beyond my obvious level.
Its OK, I get that.
I’ve been with Linux a lot of years, I’ve actually made the case for countries to use Linux and Debian as their main systems in various dept’s, (I probably owe them an apology right about now, but I’m sure their techs have worked around things like this easy enough, … if they are still even bothering with Linux).
I’ll solve it on my own, or I wont.
(I do miss the «study group» mentality of the old Linux communities. oh well, signs of the times and all that.)

I’m marking this thread [UnResolved] and won’t comment further, this conversational path is anti-productive and off track and people searching need to know that there are no answers here.
Thank you all.

dilberts_left_nut: Administrator; Posts: 5402; Joined: 2009-10-05 07:54; Location: enzed; Has thanked: 6 times; Been thanked: 49 times

Re: Wireless Killed; update to blame. [ Unresolved ]

#13

Post

by dilberts_left_nut » 2014-11-09 07:16

Well, if that’s the way you want to read my comments, fine, but that’s not at all what I said.

FWIW, given your description in the OP, I’m not convinced it is purely a wireless problem,
and you should further investigate what *actually* happened with your upgrade
before going off on tangents trying to fix symptoms.

AdrianTM wrote:There’s no hacker in my grandma…

Dan158: Posts: 56; Joined: 2011-03-20 02:34

Re: Wireless Killed; update to blame. [ RESOLVED ]

#14

Post

by Dan158 » 2014-12-16 09:53

I’ve spent a good month and a half trying to figure this out, so here is (as near as I can figure) how it pans out;

1 — an update of something made my wireless stop — Just — Simply — Working — as it had for quite a while. The last time this happened it was Network Manager going to systemD … they reversed it at that time after finding it broke to many wifi connections. Turns out they went back to SystemD once again
—- But That was not the main prob this time, or at least it may have Sparked the prob and exacerbated it, but it is not the path to the solution.

2 — I spent a ton of time checking out various linux distros and they all produced the same prob that started a month and a half ago. Of course they all seem to use SystemD and netmanager now …. so Part of the side-problem is the death of diversity in linux distros now … read on.

3 — I turned my attention to my CISCO Linksys Router, (also has a Broadcom chip) … There is The Problem! the latest firmware from Linksys (or cisco) for this router is crap.

Solution: (mostly, netmanager is still not really ‘good’, but it’ll do and hopefully get better): http://www.dd-wrt.com/wiki/index.php/Main_Page
Flashing my routers firmware with dd-wrt firmware for its model has returned my laptops ability to connect to my wifi. My Raspberry Pi’s connect to wifi now as well.

One Solution, it turns out, for WIFI troubles is To check your router and see if maybe it is making your equipment seem problematic.

Thanks for all your help, I hope my bumbling will help somebody in the future

Источник

niculinux: White ninja; Posts: 18; Joined: 19 Feb 2012, 14:43; Location: italy

[SOLVED] Wireless problems with Broadcom wi fi card

Hello

I’m a new and very very very newbie linux user

I just discovered portues and have have to say it’s great!

Howevere, in the live session I was not able to connect to the internet with my laptop, equipped with a broadcom wi fi card

I tried the 1.1 vers 64 bit either with kde and lxde

here’s some output from my dmesg:

Code: Select all

[   38.541732] ieee80211 phy0: brcmsmac: fail to load firmware brcm/bcm43xx-0.fw
[   38.541736] ieee80211 phy0: brcmsmac: Failed to find firmware usually in /lib/firmware/brcm

Code: Select all

[   39.651698] b43-phy1: Broadcom 4313 WLAN found (core revision 24)
[   39.652547] b43-phy1 ERROR: FOUND UNSUPPORTED PHY (Analog 10, Type 8, Revision 1)
[   39.652555] b43: probe of bcma0:0 failed with error -95
[   39.652579] Broadcom 43xx driver loaded [ Features: PMNLS, Firmware-ID: FW13 ]

so it is recognized by poteus, but the firmware semms missing and the drive fails to load…it is so or I am completely wrong?

Wicd does not display any connection at all

and alittel sidenote, even with a Wicd blank window connection ne I press the button «Disconnect» Porteus hangs at once

only throuh some forced ctrl+alt+canc I am able to reboot.

Care to give an answer?

A blizzard of thanks

Last edited by niculinux on 22 Feb 2012, 20:19, edited 1 time in total.

fanthom: Moderator Team; Posts: 5542; Joined: 28 Dec 2010, 02:42; Distribution: Porteus Kiosk; Location: Poland; Contact:

Re: Wireless problems with Broadcom wi fi card (Porteus 1.1)

Post#2

by fanthom » 19 Feb 2012, 15:27

Welcome on board niculinux,

broadcom chipsets are kinda problematic. please give a shot to precompiled driver first:

http://ponce.cc/porteus/x86_64/modules/ … -2_SBo.xzm

(broadcom-sta driver worked great with previous kernel versions but i have got few reports that suddenly stopped for 3.x series)

if that wont work then please remove broadcom-sta-5.100.82.112_3.1.8_porteus-x86_64-1_SBo.xzm from /porteus/modules and download kernel firmware:

http://ponce.cc/porteus/x86_64/modules/ … arch-1.xzm

let’s hope that standard drivers provided with the kernel are good enough to support your chipset.

let us know which solution worked (if any).

Please add [Solved] to your thread title if the solution was found.

niculinux: White ninja; Posts: 18; Joined: 19 Feb 2012, 14:43; Location: italy

Re: Wireless problems with Broadcom wi fi card (Porteus 1.1)

Post#3

by niculinux » 19 Feb 2012, 15:34

ok, thank, but it will be very hard for me because I’m a very very very very linux newbie

Please in the meantime would you try those 2 solutions? I beg for mercy, but I have no enough knowledge to face then

edit: I never heard of xzm divers and therefore I do not know how to manage them

as for the broadcom cards:

according to

http://linuxwireless.org/

«b43 and b43legacy are drivers for the 802.11 B/G/N family of wireless chips that Broadcom produces. The choice of which driver your card uses depends on the revision level of the 802.11 core. If your card is a BCM4306 Rev 2 or only has 802.11b capability, it uses b43legacy. All other models use b43. This number is read by the driver ssb, and the correct choice for your device is made at that point. The drivers are called bcm43xx in mainline kernels, and b43 and b43legacy in wireless-2.6 and 2.6.24 and later. «

«The Broadcom wireless chip needs proprietary software (called «firmware») that runs on the wireless chip itself to work properly. This firmware is copyrighted by Broadcom and must be extracted from Broadcom’s proprietary drivers. To get such firmware on your system, you must download the driver from a legal distribution point, extract it, and install it. This is accomplished different ways by different Linux distributions, so please read the section for yours for the best results. You will need an alternate working internet connection (by Ethernet cable, for example) since the firmware cannot be included with the distro itself»

the core of the problem:

«Both the b43 and b43legacy drivers conflict with the broadcom-wl driver, otherwise known as Broadcom’s 802.11 Linux STA driver or simply broadcom-sta. If you want to use the b43 driver in favor of broadcom-wl, make sure that your Broadcom wireless chipset is supported on the supported device list first. You will need to either remove or unload the broadcom-wl driver prior to using b43 by following[…]:»

in the end broadcom suggest to buil and use an hybrid driver, here:

http://www.broadcom.com/support/802.11/linux_sta.php

any chances that you will use that ybrid module in the next porteus relase?

thanks again

fanthom: Moderator Team; Posts: 5542; Joined: 28 Dec 2010, 02:42; Distribution: Porteus Kiosk; Location: Poland; Contact:

Re: Wireless problems with Broadcom wi fi card (Porteus 1.1)

Post#4

by fanthom » 19 Feb 2012, 19:14

in the end broadcom suggest to buil and use an hybrid driver, here:

this is exactly the driver which i posted above.
all what you need to do it to download xzm module (this is archive — same as rar — containing broadcom kernel driver), put to /porteus/modules folder on your usb stick and reboot. if your wifi start working then all is ok if not then pls upload /var/log/messages to pastebin.com and link it in this thread so i’ll be able to have a look on it.
after that please delete broadcom-sta xzm module from /porteus/modules and download kernel firmware to the same place. do a reboot and check wifi again.

good luck!

Please add [Solved] to your thread title if the solution was found.

niculinux: White ninja; Posts: 18; Joined: 19 Feb 2012, 14:43; Location: italy

Re: Wireless problems with Broadcom wi fi card (Porteus 1.1)

Post#5

by niculinux » 20 Feb 2012, 12:28

fanthom wrote:

in the end broadcom suggest to buil and use an hybrid driver, here:

this is exactly the driver which i posted above.
all what you need to do it to download xzm module (this is archive — same as rar — containing broadcom kernel driver), put to /porteus/modules folder on your usb stick and reboot. if your wifi start working then all is ok if not then pls upload /var/log/messages to pastebin.com and link it in this thread so i’ll be able to have a look on it.
after that please delete broadcom-sta xzm module from /porteus/modules and download kernel firmware to the same place. do a reboot and check wifi again.

good luck!

ok, thanks but as os this:

there are the «raw» data files (both for 32 and 64 bit) that need to be build following the instructions reported at the same link (see readme.txt) so I gues I have to build it an do as you told, I’m a very newbie user, but that should not be hard to do, thouugh.

The juicy of my question was: will you make that hybrid driver (following the procedure above) and preload it in the next porteus relase? (for the sake of the newbie user… )

and I booted porteus live but not by an usb stick, I burned it to a cd…

thanks again, maybe I’ll give a try…

fanthom: Moderator Team; Posts: 5542; Joined: 28 Dec 2010, 02:42; Distribution: Porteus Kiosk; Location: Poland; Contact:

Re: Wireless problems with Broadcom wi fi card (Porteus 1.1)

Post#6

by fanthom » 20 Feb 2012, 13:32

will you make that hybrid driver (following the procedure above) and preload it in the next porteus relase?

i will do that when someone confirm this driver working with 3.x.x kernel. you are selected for this task as you have the hardware.

I gues I have to build it an do as you told

no — you dont have to build anything. i have compiled this driver for all porteus-1.1 64bit users and it’s ready to use. all what you need to do is to download the driver and make it activated during boot.

I booted porteus live but not by an usb stick, I burned it to a cd…

this is not a problem. porteus is very flexible in that matter: you can load modules placed in some folder on your hard-drive while booting from CD.
you can prepare the folder while being on Windows or Mac or whatever.
please create folder named «porteus-modules» on any of your partitions in top directory (example d:/porteus-modules). download broadcom module from

here

and place in that directory.
start 64bit edition (this driver wont work for 32bits) and press «TAB» key on first booting option (KDE). now add this cheatcode to the existing ones:

hit enter to start booting.
if you still wont be able to connect to your wifi then please save /var/log/porteus-livedbg and /var/log/messages on your hard-drive, go back to Windows (or whatever) and upload these 2 files to pastebin.com

let me know if you stuck somewhere.

Please add [Solved] to your thread title if the solution was found.

niculinux: White ninja; Posts: 18; Joined: 19 Feb 2012, 14:43; Location: italy

Re: Wireless problems with Broadcom wi fi card (Porteus 1.1)

Post#7

by niculinux » 20 Feb 2012, 14:25

fanthom wrote:

I booted porteus live but not by an usb stick, I burned it to a cd…

this is not a problem. porteus is very flexible in that matter: you can load modules placed in some folder on your hard-drive while booting from CD.
you can prepare the folder while being on Windows or Mac or whatever.
please create folder named «porteus-modules» on any of your partitions in top directory (example d:/porteus-modules). download broadcom module from

here

and place in that directory.
start 64bit edition (this driver wont work for 32bits) and press «TAB» key on first booting option (KDE). now add this cheatcode to the existing ones:

hit enter to start booting.
if you still wont be able to connect to your wifi then please save /var/log/porteus-livedbg and /var/log/messages on your hard-drive, go back to Windows (or whatever) and upload these 2 files to pastebin.com

let me know if you stuck somewhere.

ok, laslty:

currently I’m using another linux distro (PCLInuxOS) so it’s right tu put the above module in the current / of my laptop?

If not, where?

I’don’t have/don’t want to create a pasebin account at the moment. I’ll keep in touch for sending the log in another way.

thanks again

brokenman: Site Admin; Posts: 6104; Joined: 27 Dec 2010, 03:50; Distribution: Porteus v4 all desktops; Location: Brazil; Contact:

Re: Wireless problems with Broadcom wi fi card (Porteus 1.1)

Post#8

by brokenman » 20 Feb 2012, 14:32

Yes you can create a folder anywhere on your computer to use the extramod cheatcode.

Please create the folder in any place you like, and be sure to point directly to the new folder with the module inside: extramod=/mnt/sdb1/path/to/newfolder

You don’t need to make an account for

pastebin.com

. Just click the link here, paste your stuff in the space and hit submit, then copy the link it gives you back into the forum here.

How do i become super user?
Wear your underpants on the outside and put on a cape.

brokenman: Site Admin; Posts: 6104; Joined: 27 Dec 2010, 03:50; Distribution: Porteus v4 all desktops; Location: Brazil; Contact:

Re: [SOLVED] Wireless problems with Broadcom wi fi card

Post#10

by brokenman » 22 Feb 2012, 23:30

Correct. These drivers were removed from the v1.1 of porteus because it as reported that the kernel should now contain all necessary drivers for the broadcom family. As seen this is not always the case, and for this reason Fanthom decided to reinclude the broadcom drivers for the latest Porteus-v1.2rc1 release. Glad you got it all working. Enjoy.

How do i become super user?
Wear your underpants on the outside and put on a cape.

niculinux: White ninja; Posts: 18; Joined: 19 Feb 2012, 14:43; Location: italy

Re: [SOLVED] Wireless problems with Broadcom wi fi card

Post#11

by niculinux » 23 Feb 2012, 09:42

brokenman wrote:Correct. These drivers were removed from the v1.1 of porteus because it as reported that the kernel should now contain all necessary drivers for the broadcom family. As seen this is not always the case, and for this reason Fanthom decided to reinclude the broadcom drivers for the latest Porteus-v1.2rc1 release. Glad you got it all working. Enjoy.

great!

in the end, don’t know wheter you may find this useful, but here’s my laptop (brand and model)

click me

for some «hardware support knowlege»

over and out

angus777: Ronin; Posts: 2; Joined: 25 Feb 2012, 11:21; Location: taiwan

Re: Wireless problems with Broadcom wi fi card (Porteus 1.1)

Post#12

by angus777 » 25 Feb 2012, 12:59

fanthom wrote:

will you make that hybrid driver (following the procedure above) and preload it in the next porteus relase?

i will do that when someone confirm this driver working with 3.x.x kernel. you are selected for this task as you have the hardware.

I gues I have to build it an do as you told

no — you dont have to build anything. i have compiled this driver for all porteus-1.1 64bit users and it’s ready to use. all what you need to do is to download the driver and make it activated during boot.

I booted porteus live but not by an usb stick, I burned it to a cd…

this is not a problem. porteus is very flexible in that matter: you can load modules placed in some folder on your hard-drive while booting from CD.
you can prepare the folder while being on Windows or Mac or whatever.
please create folder named «porteus-modules» on any of your partitions in top directory (example d:/porteus-modules). download broadcom module from

here

and place in that directory.
start 64bit edition (this driver wont work for 32bits) and press «TAB» key on first booting option (KDE). now add this cheatcode to the existing ones:

hit enter to start booting.
if you still wont be able to connect to your wifi then please save /var/log/porteus-livedbg and /var/log/messages on your hard-drive, go back to Windows (or whatever) and upload these 2 files to pastebin.com

let me know if you stuck somewhere.

The driver is good for 64bits (My computer use Broadcom BCM43225)!
Do you have the driver for 32bits?

amshyd: White ninja; Posts: 10; Joined: 01 Apr 2012, 08:17; Location: Hyderabad, India

Re: Wireless problems with Broadcom wi fi card (Porteus 1.1)

Post#14

by amshyd » 01 Apr 2012, 08:33

fanthom wrote:Welcome on board niculinux,

broadcom chipsets are kinda problematic. please give a shot to precompiled driver first:

http://ponce.cc/porteus/x86_64/modules/ … -2_SBo.xzm

(broadcom-sta driver worked great with previous kernel versions but i have got few reports that suddenly stopped for 3.x series)

if that wont work then please remove broadcom-sta-5.100.82.112_3.1.8_porteus-x86_64-1_SBo.xzm from /porteus/modules and download kernel firmware:

http://ponce.cc/porteus/x86_64/modules/ … arch-1.xzm

let’s hope that standard drivers provided with the kernel are good enough to support your chipset.

let us know which solution worked (if any).

—
Hi,
I use the 32 bit version of Porteus installed on a USB stick; after using the firmware module (broadcom-sta-5.100.82.112_3.1.8_porteus-x86_64-1_SBo.xzm) suggested by fanthom above ‘iwconfig’ shows me the wireless interface as ‘wlan0’. But neither ‘wicd’ nor the ‘porteus network setup tool’ could help me to connect to my wireless network. It talks about creating a log file on the desktop but never really creates anything there.

My hardware: Dell latitude E6410 laptop
My wireless network: Hidden, WPA/WPA2 Personal

I really like porteus for its swift boot and modular approach and want to use it. What do you suggest I should do to resolve the wlan issue? Do you need any additional details from me to identify the issue?

Thank You!

Edit: Oops, I pasted the wrong module name above, actually I used the firmware module ‘kernel-firmware-20120202git-noarch-1.xzm’ with my 32bit installation after which iwconfig detected wlan0.

Last edited by amshyd on 02 Apr 2012, 13:30, edited 1 time in total.

fanthom: Moderator Team; Posts: 5542; Joined: 28 Dec 2010, 02:42; Distribution: Porteus Kiosk; Location: Poland; Contact:

Re: [SOLVED] Wireless problems with Broadcom wi fi card

Post#15

by fanthom » 02 Apr 2012, 05:59

Welcome on board amshyd,

I use the 32 bit version of Porteus installed on a USB stick; after using the firmware module (broadcom-sta-5.100.82.112_3.1.8_porteus-x86_64-1_SBo.xzm) suggested by fanthom above ‘iwconfig’ shows me the wireless interface as ‘wlan0’. But neither ‘wicd’ nor the ‘porteus network setup tool’ could help me to connect to my wireless network.

that’s because you have used 64bit driver in 32bit edition.
please build broadcom-sta driver for your platform as instructed in this post:
link

Please add [Solved] to your thread title if the solution was found.

Источник

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/topic/normal_post_locked.png" alt /> Тема: b43-phy0 ERROR (Прочитано 2418 раз)

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> nullNull

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> vasyl

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> nullNull

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> vasyl

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> nullNull

Wireless Killed; update to blame. [ RESOLVED ]

Re: Wireless Killed; update to blame.

Re: Wireless Killed; update to blame.

Re: Wireless Killed; update to blame. [NOT solved!!! damnit!

Re: Wireless Killed; update to blame. [NOT solved!!! damnit!

Re: Wireless Killed; update to blame. [NOT solved!!! damnit!

Re: Wireless Killed; update to blame. [ ]

Re: Wireless Killed; update to blame. [ ]

Re: Wireless Killed; update to blame. [ ]

Re: Wireless Killed; update to blame. [ ]

Re: Wireless Killed; update to blame. [ ]

Re: Wireless Killed; update to blame. [ Unresolved ]

Re: Wireless Killed; update to blame. [ RESOLVED ]

[SOLVED] Wireless problems with Broadcom wi fi card

Re: Wireless problems with Broadcom wi fi card (Porteus 1.1)

Re: Wireless problems with Broadcom wi fi card (Porteus 1.1)

Re: Wireless problems with Broadcom wi fi card (Porteus 1.1)

Re: Wireless problems with Broadcom wi fi card (Porteus 1.1)

Re: Wireless problems with Broadcom wi fi card (Porteus 1.1)

Re: Wireless problems with Broadcom wi fi card (Porteus 1.1)

Re: Wireless problems with Broadcom wi fi card (Porteus 1.1)

Re: [SOLVED] Wireless problems with Broadcom wi fi card

Re: [SOLVED] Wireless problems with Broadcom wi fi card

Re: Wireless problems with Broadcom wi fi card (Porteus 1.1)

Re: Wireless problems with Broadcom wi fi card (Porteus 1.1)

Re: [SOLVED] Wireless problems with Broadcom wi fi card

Тема: b43-phy0 ERROR (Прочитано 2418 раз)

nullNull

vasyl

nullNull

vasyl

nullNull