Re: Please help configure to activate Bluetooth networking for "Network controller: Broadcom Inc. and subsidiaries BCM43142 802.11b/g/n (rev 01)" card
The instructions on the webpage: https://github.com/winterheart/broadcom-bt-firmware/blob/master/README.md, the portion of the note: https://github.com/winterheart/broadcom-bt-firmware/blob/master/README.md#notes-about-combined-wifibluetooth-devices may please be perused The firmware was already in the directory: /lib/firmware/brcm, but still error messages were read on the terminal. Solved the issue. There was a simple trick involved: I had to make the file read-only for all. Then restart the computer. Now: # dmesg | grep -i bluetooth # Shows all Bluetooth driver info Output: [ 29.102165] Bluetooth: Core ver 2.22 [ 29.102210] Bluetooth: HCI device and connection manager initialized [ 29.102219] Bluetooth: HCI socket layer initialized [ 29.102224] Bluetooth: L2CAP socket layer initialized [ 29.102230] Bluetooth: SCO socket layer initialized [ 105.688413] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 105.688419] Bluetooth: BNEP filters: protocol multicast [ 105.688426] Bluetooth: BNEP socket layer initialized # dmesg | grep -i bluetooth | grep -i firmware # Shows Bluetooth firmware issues Output: None However, I am still receiving the same error messages for the other commands as listed on the post: https://lists.debian.org/debian-user/2023/10/msg00871.html I now would need your support to install specific packages and reconfigure the settings so that I no longer receive the error messages. Best wishes
Re: Please help configure to activate Bluetooth networking for "Network controller: Broadcom Inc. and subsidiaries BCM43142 802.11b/g/n (rev 01)" card
Again, I post the following output for the command:
# sudo pkexec dmesg | grep -i "BCM"
Output:
[3.731659] usb 1-4: Product: BCM43142A0
[ 17.507884] wlan0: Broadcom BCM4365 802.11 Hybrid Wireless
Controller 6.30.223.271 (r587334)
[ 18.939316] Bluetooth: hci0: BCM: chip id 70
[ 18.940314] Bluetooth: hci0: BCM: features 0x06
[ 18.956242] Bluetooth: hci0: BCM43142A
[ 18.956249] Bluetooth: hci0: BCM43142A0 (001.001.011) build
[ 19.175963] bluetooth hci0: firmware: direct-loading firmware
brcm/BCM43142A0-0a5c-216d.hcd
[ 19.175977] Bluetooth: hci0: BCM43142A0 'brcm/BCM43142A0-0a5c-216d.hcd' Patch
[ 29.429513] Bluetooth: hci0: BCM: Patch command 227b failed (-110)
[ 29.431433] Bluetooth: hci0: BCM: Patch failed (-110)
[ 39.669304] Bluetooth: hci0: BCM: Reset failed (-110)
On the webpage:
https://github.com/winterheart/broadcom-bt-firmware/blob/master/README.md,
the portion of the note:
https://github.com/winterheart/broadcom-bt-firmware/blob/master/README.md#notes-about-combined-wifibluetooth-devices
may please be perused:
Some Bluetooth controller (for example, BCM4354 and BCM4356) are
integrated to WiFi chipset (this can be BCM43XX 802.11ac Wireless
Network Adapter or just simple generic Broadcom PCIE Wireless). These
devices requires two kinds of firmware - first for WiFi, and second
for Bluetooth. Without WiFi firmware Bluetooth will not initialize and
will not work properly. Firmware for WiFi already included to kernel,
but you may need to do additional work to place correct NVRAM.
Resolution needed for the above note.
I used the instructions on the Debian page to install the packages:
https://wiki.debian.org/BluetoothUser
I have installed the packages bluetooth, blueman and the rest.
Have the following installed:
blueman
bluetooth
bluez
bluez-obexd
libbluetooth3
connman
I typed on the terminal:
# blue
then used tab. The following applications are installed.
blueman-adapters blueman-assistant blueman-report
blueman-services bluemoon
blueman-applet blueman-managerblueman-sendto blueman-tray
bluetoothctl
>From the Start Menu/Preferences/Bluetooth Manager, but the tray icon
isn't visible.
Used:
# sudo blueman-services
blueman-services version 2.1.4 starting
root@debianHPRajib:/home/rajib# sudo service bluetooth status
● bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled;
vendor preset: enabled)
Active: active (running) since Sun 2023-10-29 06:41:39 IST; 9h ago
Docs: man:bluetoothd(8)
Main PID: 815 (bluetoothd)
Status: "Running"
Tasks: 1 (limit: 4566)
Memory: 1.4M
CPU: 49ms
CGroup: /system.slice/bluetooth.service
└─815 /usr/libexec/bluetooth/bluetoothd
Oct 29 06:41:34 debianHPRajib systemd[1]: Starting Bluetooth service...
Oct 29 06:41:35 debianHPRajib bluetoothd[815]: Bluetooth daemon 5.55
Oct 29 06:41:39 debianHPRajib systemd[1]: Started Bluetooth service.
Oct 29 06:41:39 debianHPRajib bluetoothd[815]: Starting SDP server
Oct 29 06:41:40 debianHPRajib bluetoothd[815]: Bluetooth management
interface 1.18 initialized
This is consistently reported as Running.
Then tried: # sudo blueman-assistant
A pop-up says no assistant found
Then:
# sudo blueman-manager
blueman-manager version 2.1.4 starting
blueman-manager 16.17.02 ERRORManager:118 on_dbus_name_appeared:
Default adapter not found, trying first available.
blueman-manager 16.17.02 ERRORManager:122 on_dbus_name_appeared:
No adapter(s) found, exiting
Then tried:
# sudo blueman-adapters
blueman-adapters version 2.1.4 starting
blueman-adapters 16.18.13 ERRORAdapter:53 __init__ : No adapter(s) found
Then tried:
# sudo blueman-applet
blueman-applet version 2.1.4 starting
There is an instance already running
Then tried:
# sudo blueman-tray
blueman-tray version 2.1.4 starting
There is an instance already running
Then tried:
# sudo blueman-services
blueman-services version 2.1.4 starting
A window opens with title: local services and presents options.
Then tried:
# sudo blueman-report
Terminating blueman-applet
Describe your next action (keep empty if done):
Traceback (most recent call last):
File "/usr/bin/blueman-report", line 57, in
response = urllib2.urlopen('https://api.github.com/gists',
data.encode('UTF-8')).read()
File "/usr/lib/python3.9/urllib/request.py", line 214, in urlopen
return opener.open(url, data, timeout)
File "/usr/lib/python3.9/urllib/request.py", line 523, in open
response = meth(req, response)
File "/usr/lib/python3.9/urllib/request.py", line 632, in http_response
response = self.parent.error(
File "/usr/lib/python3.9/urllib/request.py", line 561, in error
return self._call_chain(*args)
File "/usr/lib/python3.9/urllib/request.py", line 494, in _call_chain
result = func(*args)
File "/
Broadcom WiFi/Bluetooth BCM43142 issues
On Sun, Oct 29, 2023 at 03:24:00PM +0530, Susmita/Rajib wrote: Rajib, Please note the change of subject. > I have had a conversation with the Team ThinkPenguin for the wireless > N model model. Their USB WiFi dongle is only for WiFi connectivity. > Not for Bluetooth. > > The team has been very transparent with sharing information, and I > thank you for letting me know about such an empowering team surviving > within the proprietary universe. > The WiFi and Bluetooth connectivity for your laptop is almost certainly all provided by the Broadcom chipset and the firmware it requires. If not, it may be provided by the main laptop chipset - so maybe Intel? You have been given (off list) a method for configuring kernel modules and using DKMS to provide support when each kernel is updated. You may need to download a firmware "blob" and place that in /lib/firmware The method you've been given is by using module-assistant to automate the process of building the kernel modules > Since the wl module already has configured and restored the WiFi > connectivity for my laptop, I wouldn't require the said dongle. > > Shortly, I will post for configuring the Bluetooth connectivity for my > HP laptop. > So - you already have some of that in place: https://wiki.debian.org/wl As root, you can run the command dmesg to see what the kernel finds at boot. It produces a lot of output, so you can use grep to filter that. What does the output of: dmesg | grep Bluetooth | less produce for you - some of that should give you a clue as to what firmware is found or is missing. > So your support is all the more expected. > > Best wishes, > Rajib > With best wishes, as always Andy Cater [amaca...@debian.org]
Re: Please help configure to activate Bluetooth networking for "Network controller: Broadcom Inc. and subsidiaries BCM43142 802.11b/g/n (rev 01)" card
Dear Mr. ullrich, I am so concerned by the Biblical God-like Commandment of some of the senior members of this mailing list that I have to ask you a second time: have you meticulously perused all my posts relating to this problematic hardware?: "Network controller: Broadcom Inc. and subsidiaries BCM43142 802.11b/g/n (rev 01)" card The relevant posts begin at: (1) https://lists.debian.org/debian-user/2019/10/msg00493.html (2) https://lists.debian.org/debian-user/2023/10/msg00452.html (3) https://lists.debian.org/debian-user/2023/10/msg00649.html (4) https://lists.debian.org/debian-user/2023/10/msg00650.html Also, I assume you have noted that I still continue to use the oldstable system: [Official Debian GNU/Linux Live 11.6.0 lxde 2022-12-17T11:46]/ bullseye Sometimes I feel that some posters are actually planted here on the Mailing List, and are heavily paid for their disruptions, by the Proprietary Universe, to make Free and Open Source users like me lose hope on the FSF ecosystem, feel frustrated and compel us to return to the Proprietary Universe, turning away from the FSF/OpenSource system and the Social Contract. Then again, there are some who express their goodness and then vanish. The latter, like Mr. Davidson, Mr. Curt, et al, are the ones who keep my hope on humanity and the social contract intact. I still believe that man could admire the best way forward: the positive non-zero sum cooperative games, if he chose wisely. You appear to be here since May 2011 in the debian-user ML. So you appear to be a fairly senior member. Also, it appears that you have been suggesting module-assistant since Jul 2011, thus experienced in using module-assistant. I have installed the m-a package, but not the rest, yet. I hope that I will hear from you a second time. If I don't, then still ... Best wishes, Rajib Etc.
Re: Please help configure to activate Bluetooth networking for "Network controller: Broadcom Inc. and subsidiaries BCM43142 802.11b/g/n (rev 01)" card
Am Samstag, 28. Oktober 2023, 13:08:21 CEST schrieb Susmita/Rajib: > BCM43142A0 Try the following. Building kernel modue: 1. Install the packages module-assistant, broadcom-sta, broadcom-dkms and broadcom-sta- source 2. start module-assistant, command: m-a 3. In GUI enter UPDATE 4. In GUI enter PREPARE 5. In GUI enter SELECT 6. In SELECT menu choose broadcom-sta and click ok 7. In GUI enter GET 8. In GUI enter BUILD 9. In GUI enter INSTALL After finish enter BACK and EXIT. You will need the firmware. The firmware is distribution independent, so you can get it from other distributions, like here from AUR: https://aur.archlinux.org/packages/bcm43142a0-firmware[1] Get it and put it manually into /lib/firmware Now try again. Hope this helps. Best regards Hans [1] https://aur.archlinux.org/packages/bcm43142a0-firmware
Re: Please help configure to activate Bluetooth networking for "Network controller: Broadcom Inc. and subsidiaries BCM43142 802.11b/g/n (rev 01)" card
On Wed, 25 Oct 2023 at 08:31, Susmita/Rajib wrote: [ ... ] > > Install the package firmware-b43-installer and follow the prompts. > > > > I'm fairly sure that's all it takes. You may need to uninstall wl > > and / or any other changes you've made. > [ ... ] > > Ok, I will gradually try to learn about this firmware, > "firmware-b43-installer". [ ... ] Dear Mr. Cater, I took time to go through the list/description of Wireless network cards in the package Description for which the driver is suitable. The list is as follows: ... Supported chipsets: * BCM4306/3 (chip revision 3 only); * BCM4311 (NOT PCI Id 14e4:4313); * BCM4312; * BCM43131; * BCM4318; * BCM4321 (only partial support, not all versions tested); * BCM43217; * BCM4322 (only partial support for some versions, not all versions tested); * BCM43222 (not all versions tested); * BCM43224 (not all versions tested); * BCM43225; * BCM43227; * BCM43228; * BCM4331; * BCM47xx (detection not reliable, may not support all versions). If observed carefully, the card which my laptop has is: BCM43142 802.11b/g/n (rev 01) None of the list-items has the said card mentioned. So I am doubtful if this driver would even work. Further, the webpage https://wireless.wiki.kernel.org/en/users/drivers/b43#contact for the "firmware-b43-installer" may please be perused: On the webpage the list with the following columns has the following entries for the said chipset: PCI-ID Supported? Chip ID Modes PHY version Alternative 14e4:4365 no BCM43142 b/g/n LCN40 (r3) wl So it can be seen that the driver isn't suitable for my laptop's said card. I again post my query to all Senior Members of the debian-user Mailing List: If senior members have gone through this ML subject thread, your experience is invited on the issue. Once again the detailed dmesg output for the "bluetooth" section for the said card is at the post: https://lists.debian.org/debian-user/2023/10/msg00649.html. Particularly: # dmesg | grep -i -e "bluetooth" [191884.268151] Bluetooth: hci0: BCM: chip id 70 [191884.269117] Bluetooth: hci0: BCM: features 0x06 [191884.285185] Bluetooth: hci0: BCM43142A [191884.285195] Bluetooth: hci0: BCM43142A0 (001.001.011) build [191884.286140] bluetooth hci0: firmware: failed to load brcm/BCM43142A0-0a5c-216d.hcd (-2) [191884.286161] bluetooth hci0: firmware: failed to load brcm/BCM-0a5c-216d.hcd (-2) [191884.286165] Bluetooth: hci0: BCM: firmware Patch file not found, tried: [191884.286168] Bluetooth: hci0: BCM: 'brcm/BCM43142A0-0a5c-216d.hcd' [191884.286171] Bluetooth: hci0: BCM: 'brcm/BCM-0a5c-216d.hcd' [191886.293688] Bluetooth: hci0: command 0x1003 tx timeout [191886.295091] Bluetooth: hci0: unexpected event for opcode 0x1003 The wifi section works perfectly well. Therefore, I would again return to my earlier post at: https://lists.debian.org/debian-user/2023/10/msg00650.html That is, the thread with the Subject: Which Network Controller Card handling Wi-Fi, Bluetooth, etc., connectivities, is GNU/Linux Approved/certified, and would be (1) compatible with my HP laptop's motherboard, and (2) could replace the "Network controller: Broadcom Inc. and subsidiaries BCM43142 802.11b/g/n (rev 01)" I desire a Debian approved list for perfectly compatible Wireless-Bluetooth Cards. Like the PCI list, with the heading: DeviceDatabase/PCI - Debian Wiki at https://wiki.debian.org/DeviceDatabase/PCI Best wishes, Rajib, Etc.
Re: Please help configure to activate Bluetooth networking for "Network controller: Broadcom Inc. and subsidiaries BCM43142 802.11b/g/n (rev 01)" card
From: "Andrew M.A. Cater" Date: Tue, 24 Oct 2023 17:12:41 + Message-id: <[🔎] ztf7cq23nikqt...@einval.com> In-reply-to: <[🔎] CAEG4cZW87bzq6SMO0HPJAfh+UcgJFEJ=jo6ahbrwecp22yb...@mail.gmail.com> References: <[🔎] caeg4czxgp3wqszgsps5erwcvxyf1wdm-mjnbx+ehvybqrr-...@mail.gmail.com> <[🔎] CAEG4cZW87bzq6SMO0HPJAfh+UcgJFEJ=jo6ahbrwecp22yb...@mail.gmail.com> Dear Mr. Cater, thank you for your kind reply. > On Tue, Oct 24, 2023 at 08:19:03PM +0530, Susmita/Rajib wrote: [ ... ] > Please ensure that your /etc/apt/sources.list includes entries > for main contrib and non-free > > See, for example, the version for Debian Bullseye (oldstable) in this > link: https://wiki.debian.org/SourcesList > > Then do an apt update ; apt upgrade to bring yourself up to date. [ ... ] It was already done, as recorded earlier and elsewhere. So otherwise, I am ready. [ ... ] > Install the package firmware-b43-installer and follow the prompts. > > I'm fairly sure that's all it takes. You may need to uninstall wl > and / or any other changes you've made. [ ... ] Ok, I will gradually try to learn about this firmware, "firmware-b43-installer". [ ... ] > As the author of the FAQ posting made here every month; > Please do not post political / nationalistic / controversial > points here - Debian is worldwide and Bharat nationalism may be > misplaced as not everyone will appreciate what you are writing. [ ... ] Sure. One note: the correct phrase would be "Inclusive Globalism", not "Bharatiya Nationalism". In the said post, as a reply to Mr. Dan Purgert -'s post dated: Tue, 24 Oct 2023 07:45:13 -0400, I couldn't help identify the global anglo-Saxon ploy to enslave the world embedded within his sentences. I immediately remembered the information on the "The Creature From Jekyll Island, G Edward Grifin", "The Tower Of Basel, Adam LaBor", "Committee Of 300", the "Corporation Of London", et al. I was just networking the extreme evil that ensues from a trans-generational scarcity of resources, and my thought flowed to the tropics, where ample sunlight and rainfall ensured a bewilderingly rich biome with plenty of diverse foods, merriment and festivals round the year. I remembered that the public is only 3 meals away from a revolution. >From there the Maslow-ian hierarchy of needs arrived ... and the rest Control, Covid19, planned eradication of global population, Control of Resources by Global Corporations, End of Freedoms, including Free air and water ... Readers interested to know the real story of Bharat could contact for a text download link. Best wishes, Rajib Etc.
Re: Please help configure to activate Bluetooth networking for "Network controller: Broadcom Inc. and subsidiaries BCM43142 802.11b/g/n (rev 01)" card
On Tue, Oct 24, 2023 at 08:19:03PM +0530, Susmita/Rajib wrote: > From: "Andrew M.A. Cater" > Date: Tue, 24 Oct 2023 10:50:48 + > Message-id: <[🔎] ztehic-dyzpii...@einval.com> > In-reply-to: <[🔎] > caeg4czxgp3wqszgsps5erwcvxyf1wdm-mjnbx+ehvybqrr-...@mail.gmail.com> > > Dear Mr. Cater, > > Once again, thank you for your post. > > But Mr. Cater, I would have to request you to appreciate my > limitations to follow your advice, given the gap in our competence > levels. > Dear Rajib, I can't help you because I don't have such a card / chipset. Please ensure that your /etc/apt/sources.list includes entries for main contrib and non-free See, for example, the version for Debian Bullseye (oldstable) in this link: https://wiki.debian.org/SourcesList Then do an apt update ; apt upgrade to bring yourself up to date. Install the package firmware-b43-installer and follow the prompts. I'm fairly sure that's all it takes. You may need to uninstall wl and / or any other changes you've made. As the author of the FAQ posting made here every month; Please do not post political / nationalistic / controversial points here - Debian is worldwide and Bharat nationalism may be misplaced as not everyone will appreciate what you are writing. With every good wish, as ever, Andy Cater (amaca...@debian.org) > But I will try to learn more about b43-fwcutter. > > Fortunately for me, I had opened the casing to check that the said > wireless network card is inserted into a slot on the motherboard > internally and could be removed and reinserted. > > So, you could guide me a little further on b43-fwcutter and let us see > if I could carry the mission a little further. > > Best wishes, > Rajib > Etc. >
Re: Please help configure to activate Bluetooth networking for "Network controller: Broadcom Inc. and subsidiaries BCM43142 802.11b/g/n (rev 01)" card
From: "Andrew M.A. Cater" Date: Tue, 24 Oct 2023 10:50:48 + Message-id: <[🔎] ztehic-dyzpii...@einval.com> In-reply-to: <[🔎] caeg4czxgp3wqszgsps5erwcvxyf1wdm-mjnbx+ehvybqrr-...@mail.gmail.com> Dear Mr. Cater, Once again, thank you for your post. But Mr. Cater, I would have to request you to appreciate my limitations to follow your advice, given the gap in our competence levels. But I will try to learn more about b43-fwcutter. Fortunately for me, I had opened the casing to check that the said wireless network card is inserted into a slot on the motherboard internally and could be removed and reinserted. So, you could guide me a little further on b43-fwcutter and let us see if I could carry the mission a little further. Best wishes, Rajib Etc.
Re: Please help configure to activate Bluetooth networking for "Network controller: Broadcom Inc. and subsidiaries BCM43142 802.11b/g/n (rev 01)" card
On Tue, Oct 24, 2023 at 02:01:21PM +0530, Susmita/Rajib wrote: > My dear illustrious Team Leaders and Senior Members, Debian-User > group, debian-user@lists.debian.org > > I rephrase my earlier question posted at: > https://lists.debian.org/debian-user/2023/10/msg00452.html > which didn't receive an insightful reply or guidance. Yes, Mr. Cater > did advise on B43 series firmware along with his suggestion to update > and I thank him for that. But I have progressed a bit further than the > situation I faced then. In the end, if we fail, I will change the > Wireless Network Card. > Hi Rajib, I don't think you quite got the point I was making. wl is one way round the problem. b43-fwcutter is the other, and more usual way round this problematic Broadcom chipset. If you go the b43 way, then you need to remove wl, I think. The catch is that you need network access to download the Broadcom firmware to make use of b43-fwcutter. If you're unlucky, the wireless network card may actually be built into the laptop chipset and not easily able to be changed. You may also find that HP expect particular models and have deny-listed others. > Any advice with usual codes and inputs will be welcome. > > > The LAN interface is: > 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL810xE > PCI Express Fast Ethernet controller (rev 07) > Subsystem: Hewlett-Packard Company RTL810xE PCI Express Fast Ethernet > controller > Flags: bus master, fast devsel, latency 0, IRQ 18 > I/O ports at 4000 [size=256] > Memory at c070 (64-bit, non-prefetchable) [size=4K] > Memory at c040 (64-bit, prefetchable) [size=16K] > Capabilities: [40] Power Management version 3 > Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+ > Capabilities: [70] Express Endpoint, MSI 01 > Capabilities: [b0] MSI-X: Enable+ Count=4 Masked- > Capabilities: [d0] Vital Product Data > Capabilities: [100] Advanced Error Reporting > Capabilities: [140] Virtual Channel > Capabilities: [160] Device Serial Number 01-00-00-00-36-4c-e0-00 > Capabilities: [170] Latency Tolerance Reporting > Kernel driver in use: r8169 > Kernel modules: r8169 > This is stock Realtek and should work without a problem. > However, with the output of # dmesg | grep -i -e "bluetooth" > > [191884.268151] Bluetooth: hci0: BCM: chip id 70 > [191884.269117] Bluetooth: hci0: BCM: features 0x06 > [191884.285185] Bluetooth: hci0: BCM43142A > [191884.285195] Bluetooth: hci0: BCM43142A0 (001.001.011) build > [191884.286140] bluetooth hci0: firmware: failed to load > brcm/BCM43142A0-0a5c-216d.hcd (-2) > [191884.286161] bluetooth hci0: firmware: failed to load > brcm/BCM-0a5c-216d.hcd (-2) > [191884.286165] Bluetooth: hci0: BCM: firmware Patch file not found, tried: > [191884.286168] Bluetooth: hci0: BCM: 'brcm/BCM43142A0-0a5c-216d.hcd' > [191884.286171] Bluetooth: hci0: BCM: 'brcm/BCM-0a5c-216d.hcd' > [191886.293688] Bluetooth: hci0: command 0x1003 tx timeout > [191886.295091] Bluetooth: hci0: unexpected event for opcode 0x1003 > > > So, brcm/BCM-0a5c-216d.hcd firmware isn't working properly. > > I reached the ubuntu thread and the post: > https://ubuntuforums.org/showthread.php?t=2489817&p=14156420#post14156420 > talks about the Bluetooth driver brcm. > > I searched the internet with the firmware "BCM-0a5c-216d.hcd" and reached: > https://wiki.debian.org/BCMHybridBTFirmware#Missing_Firmware_Filename > > Used: > #pkexec dmidecode -t01 > > Outputs: > # dmidecode 3.3 > Getting SMBIOS data from sysfs. > SMBIOS 2.8 present. > > Handle 0x0001, DMI type 1, 27 bytes > System Information > Manufacturer: Hewlett-Packard > Product Name: HP Notebook > Version: Type1ProductConfigId > Serial Number: **edited** > UUID: **edited** > Wake-up Type: Power Switch > SKU Number: **edited** > Family: 103C_5335KV G=N L=CON B=HP > > Went to github. Read the page README.md at: > https://github.com/winterheart/broadcom-bt-firmware/blob/master/brcm/BCM43142A0-0a5c-216d.hcd > > Instruction raed and followed: "... Place required .hcd file to > /lib/firmware/brcm ..." > > But there appears to be a problem: > #sudo dmesg | grep -i -e "bluetooth" > > Outputs: > [ 16.740380] Bluetooth: Core ver 2.22 > [ 16.740410] Bluetooth: HCI device and connection manager initialized > [ 16.740414] Bluetooth: HCI socket layer initialized > [ 16.740418] Bluetooth: L2CAP socket layer initialized > [ 16.740423] Bluetooth: SCO socket layer initia
Please help configure to activate Bluetooth networking for "Network controller: Broadcom Inc. and subsidiaries BCM43142 802.11b/g/n (rev 01)" card
My dear illustrious Team Leaders and Senior Members, Debian-User group, debian-user@lists.debian.org I rephrase my earlier question posted at: https://lists.debian.org/debian-user/2023/10/msg00452.html which didn't receive an insightful reply or guidance. Yes, Mr. Cater did advise on B43 series firmware along with his suggestion to update and I thank him for that. But I have progressed a bit further than the situation I faced then. In the end, if we fail, I will change the Wireless Network Card. Any advice with usual codes and inputs will be welcome. I have reached the post at https://wiki.debian.org/DeviceDatabase/PCI The lspci -v for the Wireless Network Interface card is: 04:00.0 Network controller: Broadcom Inc. and subsidiaries BCM43142 802.11b/g/n (rev 01) Subsystem: Hewlett-Packard Company BCM43142 802.11b/g/n Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at c050 (64-bit, non-prefetchable) [size=32K] Capabilities: [40] Power Management version 3 Capabilities: [58] Vendor Specific Information: Len=78 Capabilities: [48] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [d0] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [13c] Virtual Channel Capabilities: [160] Device Serial Number 00-00-b8-ff-ff-dc-ac-d1 Capabilities: [16c] Power Budgeting Kernel driver in use: wl Kernel modules: bcma, wl The LAN interface is: 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL810xE PCI Express Fast Ethernet controller (rev 07) Subsystem: Hewlett-Packard Company RTL810xE PCI Express Fast Ethernet controller Flags: bus master, fast devsel, latency 0, IRQ 18 I/O ports at 4000 [size=256] Memory at c070 (64-bit, non-prefetchable) [size=4K] Memory at c040 (64-bit, prefetchable) [size=16K] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [70] Express Endpoint, MSI 01 Capabilities: [b0] MSI-X: Enable+ Count=4 Masked- Capabilities: [d0] Vital Product Data Capabilities: [100] Advanced Error Reporting Capabilities: [140] Virtual Channel Capabilities: [160] Device Serial Number 01-00-00-00-36-4c-e0-00 Capabilities: [170] Latency Tolerance Reporting Kernel driver in use: r8169 Kernel modules: r8169 However, with the output of # dmesg | grep -i -e "bluetooth" [191884.268151] Bluetooth: hci0: BCM: chip id 70 [191884.269117] Bluetooth: hci0: BCM: features 0x06 [191884.285185] Bluetooth: hci0: BCM43142A [191884.285195] Bluetooth: hci0: BCM43142A0 (001.001.011) build [191884.286140] bluetooth hci0: firmware: failed to load brcm/BCM43142A0-0a5c-216d.hcd (-2) [191884.286161] bluetooth hci0: firmware: failed to load brcm/BCM-0a5c-216d.hcd (-2) [191884.286165] Bluetooth: hci0: BCM: firmware Patch file not found, tried: [191884.286168] Bluetooth: hci0: BCM: 'brcm/BCM43142A0-0a5c-216d.hcd' [191884.286171] Bluetooth: hci0: BCM: 'brcm/BCM-0a5c-216d.hcd' [191886.293688] Bluetooth: hci0: command 0x1003 tx timeout [191886.295091] Bluetooth: hci0: unexpected event for opcode 0x1003 So, brcm/BCM-0a5c-216d.hcd firmware isn't working properly. I reached the ubuntu thread and the post: https://ubuntuforums.org/showthread.php?t=2489817&p=14156420#post14156420 talks about the Bluetooth driver brcm. I searched the internet with the firmware "BCM-0a5c-216d.hcd" and reached: https://wiki.debian.org/BCMHybridBTFirmware#Missing_Firmware_Filename Used: #pkexec dmidecode -t01 Outputs: # dmidecode 3.3 Getting SMBIOS data from sysfs. SMBIOS 2.8 present. Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: Hewlett-Packard Product Name: HP Notebook Version: Type1ProductConfigId Serial Number: **edited** UUID: **edited** Wake-up Type: Power Switch SKU Number: **edited** Family: 103C_5335KV G=N L=CON B=HP Went to github. Read the page README.md at: https://github.com/winterheart/broadcom-bt-firmware/blob/master/brcm/BCM43142A0-0a5c-216d.hcd Instruction raed and followed: "... Place required .hcd file to /lib/firmware/brcm ..." But there appears to be a problem: #sudo dmesg | grep -i -e "bluetooth" Outputs: [ 16.740380] Bluetooth: Core ver 2.22 [ 16.740410] Bluetooth: HCI device and connection manager initialized [ 16.740414] Bluetooth: HCI socket layer initialized [ 16.740418] Bluetooth: L2CAP socket layer initialized [ 16.740423] Bluetooth: SCO socket layer initialized [ 17.477920] Bluetooth: hci0: BCM: chip id 70 [ 17.478903] Bluetooth: hci0: BCM: features 0x06 [ 17.494925] Bluetooth: hci0: ***edited*** [ 17.494929] Bluetooth: hci0: BCM43142A0 (001.001.011) build [ 17.719998] bluet
Re: ntrollIf Network Controller Chipset handles Wi-Fi, then shouldn't it handle Bluetooth too? Advice required on "Network controller: Broadcom Inc. and subsidiaries BCM43142 802.11b/g/n (rev 01)" for
On Sat, Oct 21, 2023 at 08:18:30AM +0530, Susmita/Rajib wrote: > To, > The Team User, > debian-user@lists.debian.org, > Debian.org > > My dear illustrious Team Leaders, > > Good morning. > > May please my first post at > https://lists.debian.org/debian-user/2019/10/msg00493.html with the > subject, "Appears to be a problem with Debian Stretch 9.11.0 regarding > WAN non-allocation ..." be perused. > Hi Rajib, > Following the short post by Mr. Curt at: > https://lists.debian.org/debian-user/2019/10/msg00497.html, a solution > was found and the Complete Solution was posted at: > http://forums.debian.net/viewtopic.php?f=7&t=143930 > The above posts don't give much information. As requested beFore, please don't refer to forum posts without giving the information here on the mailing list. > In Brief: > I used Debian wiki page of wl. Added the sources.list line: > deb http://deb.debian.org/debian bullseye contrib non-free > Updated. Uninstalled broadcom installed package. Installed > broadcom-sta-dkms package.from synaptic. After the rest steps the > Wi-Fi worked, and works, perfectly. > > For example: > > (1) # dmesg | grep -e "wl" > > [output] > [0.00] DMI: Hewlett-Packard HP Notebook/80C4, BIOS F.02 03/24/2015 > [ 15.567967] wl: loading out-of-tree module taints kernel. > [ 15.567973] wl: module license 'MIXED/Proprietary' taints kernel. > [ 15.571378] wl: module verification failed: signature and/or > required key missing - tainting kernel > [ 15.607781] wlan0: Broadcom BCM4365 802.11 Hybrid Wireless > Controller 6.30.223.271 (r587334) > [ 15.751248] wl :04:00.0 wlp4s0: renamed from wlan0 > [ 44.867147] IPv6: ADDRCONF(NETDEV_CHANGE): wlp4s0: link becomes ready > [ 436.593766] IPv6: ADDRCONF(NETDEV_CHANGE): wlp4s0: link becomes ready > [ 7107.206153] IPv6: ADDRCONF(NETDEV_CHANGE): wlp4s0: link becomes ready > [10536.901498] IPv6: ADDRCONF(NETDEV_CHANGE): wlp4s0: link becomes ready > [10791.043627] IPv6: ADDRCONF(NETDEV_CHANGE): wlp4s0: link becomes ready > [17994.815848] IPv6: ADDRCONF(NETDEV_CHANGE): wlp4s0: link becomes ready > [/output] > I'm assuming that you are using Debian 11 bullseye. Check your /etc/apt/sources.list file - I assume that it has main contrib and non-free. The usual method of installing broadcom wifi firmware has been to use the b43-fwcutter package I think. e (2) # dmesg | grep -e "bluetooth" > > [output] > [ 17.284222] bluetooth hci0: firmware: failed to load > brcm/BCM43142A0-0a5c-216d.hcd (-2) > [ 17.284331] bluetooth hci0: firmware: failed to load > brcm/BCM-0a5c-216d.hcd (-2) > [ 6815.629661] bluetooth hci0: firmware: failed to load > brcm/BCM43142A0-0a5c-216d.hcd (-2) > [ 6815.629675] bluetooth hci0: firmware: failed to load > brcm/BCM-0a5c-216d.hcd (-2) > [/output] > > # dmesg | grep -e "broadcom" has not output. > > With my inability to pair my bluetooth headphone following > instructions at https://wiki.debian.org/BluetoothUser, > /usr/share/doc/bluez/README.Debian.gz and installing the necessary > packages, like bluetooth, bluez and blueman my doubt again arises. > > So my Necessary Question: Has the broadcom and wl created a > conflicting situation? > Possibly, yes. I would suggest getting hold of the broadcom firmware using the b43 package. For various reasons, the original Broadcom firmware is not distributable by Debian - the fwcutter downloads a file and extracts the requisite firmware You might find it worthwhile to update to Debian 12 bookworm at some point. The installer includes most firmware and you can adapt the apt/sources.list to include the non-free firmware repository but I think the B43 series firmware can still not be included directly. > Best wishes, > Rajib > Etc. > With every good wish, Andy Cater
If Network Controller Chipset handles Wi-Fi, then shouldn't it handle Bluetooth too? Advice required on "Network controller: Broadcom Inc. and subsidiaries BCM43142 802.11b/g/n (rev 01)" for controlli
To, The Team User, debian-user@lists.debian.org, Debian.org My dear illustrious Team Leaders, Good morning. May please my first post at https://lists.debian.org/debian-user/2019/10/msg00493.html with the subject, "Appears to be a problem with Debian Stretch 9.11.0 regarding WAN non-allocation ..." be perused. Following the short post by Mr. Curt at: https://lists.debian.org/debian-user/2019/10/msg00497.html, a solution was found and the Complete Solution was posted at: http://forums.debian.net/viewtopic.php?f=7&t=143930 In Brief: I used Debian wiki page of wl. Added the sources.list line: deb http://deb.debian.org/debian bullseye contrib non-free Updated. Uninstalled broadcom installed package. Installed broadcom-sta-dkms package.from synaptic. After the rest steps the Wi-Fi worked, and works, perfectly. For example: (1) # dmesg | grep -e "wl" [output] [0.00] DMI: Hewlett-Packard HP Notebook/80C4, BIOS F.02 03/24/2015 [ 15.567967] wl: loading out-of-tree module taints kernel. [ 15.567973] wl: module license 'MIXED/Proprietary' taints kernel. [ 15.571378] wl: module verification failed: signature and/or required key missing - tainting kernel [ 15.607781] wlan0: Broadcom BCM4365 802.11 Hybrid Wireless Controller 6.30.223.271 (r587334) [ 15.751248] wl :04:00.0 wlp4s0: renamed from wlan0 [ 44.867147] IPv6: ADDRCONF(NETDEV_CHANGE): wlp4s0: link becomes ready [ 436.593766] IPv6: ADDRCONF(NETDEV_CHANGE): wlp4s0: link becomes ready [ 7107.206153] IPv6: ADDRCONF(NETDEV_CHANGE): wlp4s0: link becomes ready [10536.901498] IPv6: ADDRCONF(NETDEV_CHANGE): wlp4s0: link becomes ready [10791.043627] IPv6: ADDRCONF(NETDEV_CHANGE): wlp4s0: link becomes ready [17994.815848] IPv6: ADDRCONF(NETDEV_CHANGE): wlp4s0: link becomes ready [/output] (2) # dmesg | grep -e "bluetooth" [output] [ 17.284222] bluetooth hci0: firmware: failed to load brcm/BCM43142A0-0a5c-216d.hcd (-2) [ 17.284331] bluetooth hci0: firmware: failed to load brcm/BCM-0a5c-216d.hcd (-2) [ 6815.629661] bluetooth hci0: firmware: failed to load brcm/BCM43142A0-0a5c-216d.hcd (-2) [ 6815.629675] bluetooth hci0: firmware: failed to load brcm/BCM-0a5c-216d.hcd (-2) [/output] # dmesg | grep -e "broadcom" has not output. With my inability to pair my bluetooth headphone following instructions at https://wiki.debian.org/BluetoothUser, /usr/share/doc/bluez/README.Debian.gz and installing the necessary packages, like bluetooth, bluez and blueman my doubt again arises. So my Necessary Question: Has the broadcom and wl created a conflicting situation? Best wishes, Rajib Etc.
Re: ntrollIf Network Controller Chipset handles Wi-Fi, then shouldn't it handle Bluetooth too? Advice required on "Network controller: Broadcom Inc. and subsidiaries BCM43142 802.11b/g/n (rev 01)" for
Please DON'T post your reply on this Post. Subject Line Ill-formed.
ntrollIf Network Controller Chipset handles Wi-Fi, then shouldn't it handle Bluetooth too? Advice required on "Network controller: Broadcom Inc. and subsidiaries BCM43142 802.11b/g/n (rev 01)" for con
To, The Team User, debian-user@lists.debian.org, Debian.org My dear illustrious Team Leaders, Good morning. May please my first post at https://lists.debian.org/debian-user/2019/10/msg00493.html with the subject, "Appears to be a problem with Debian Stretch 9.11.0 regarding WAN non-allocation ..." be perused. Following the short post by Mr. Curt at: https://lists.debian.org/debian-user/2019/10/msg00497.html, a solution was found and the Complete Solution was posted at: http://forums.debian.net/viewtopic.php?f=7&t=143930 In Brief: I used Debian wiki page of wl. Added the sources.list line: deb http://deb.debian.org/debian bullseye contrib non-free Updated. Uninstalled broadcom installed package. Installed broadcom-sta-dkms package.from synaptic. After the rest steps the Wi-Fi worked, and works, perfectly. For example: (1) # dmesg | grep -e "wl" [output] [0.00] DMI: Hewlett-Packard HP Notebook/80C4, BIOS F.02 03/24/2015 [ 15.567967] wl: loading out-of-tree module taints kernel. [ 15.567973] wl: module license 'MIXED/Proprietary' taints kernel. [ 15.571378] wl: module verification failed: signature and/or required key missing - tainting kernel [ 15.607781] wlan0: Broadcom BCM4365 802.11 Hybrid Wireless Controller 6.30.223.271 (r587334) [ 15.751248] wl :04:00.0 wlp4s0: renamed from wlan0 [ 44.867147] IPv6: ADDRCONF(NETDEV_CHANGE): wlp4s0: link becomes ready [ 436.593766] IPv6: ADDRCONF(NETDEV_CHANGE): wlp4s0: link becomes ready [ 7107.206153] IPv6: ADDRCONF(NETDEV_CHANGE): wlp4s0: link becomes ready [10536.901498] IPv6: ADDRCONF(NETDEV_CHANGE): wlp4s0: link becomes ready [10791.043627] IPv6: ADDRCONF(NETDEV_CHANGE): wlp4s0: link becomes ready [17994.815848] IPv6: ADDRCONF(NETDEV_CHANGE): wlp4s0: link becomes ready [/output] (2) # dmesg | grep -e "bluetooth" [output] [ 17.284222] bluetooth hci0: firmware: failed to load brcm/BCM43142A0-0a5c-216d.hcd (-2) [ 17.284331] bluetooth hci0: firmware: failed to load brcm/BCM-0a5c-216d.hcd (-2) [ 6815.629661] bluetooth hci0: firmware: failed to load brcm/BCM43142A0-0a5c-216d.hcd (-2) [ 6815.629675] bluetooth hci0: firmware: failed to load brcm/BCM-0a5c-216d.hcd (-2) [/output] # dmesg | grep -e "broadcom" has not output. With my inability to pair my bluetooth headphone following instructions at https://wiki.debian.org/BluetoothUser, /usr/share/doc/bluez/README.Debian.gz and installing the necessary packages, like bluetooth, bluez and blueman my doubt again arises. So my Necessary Question: Has the broadcom and wl created a conflicting situation? Best wishes, Rajib Etc.
Re: Patch broadcom-sta for kernel 5.18
Muhammad Akbar Yanuar Mantari wrote: > Dear Debian Developer, > > Please patch broadcom-sta for kernel 5.18 from arch linux > > https://github.com/archlinux/svntogit-community/commits/packages/broadcom-wl-dkms/trunk This is the Debian Users' list, not developers. In any case, you want to talk to the maintainer of the right package, which is: $ apt search broadcom wl Sorting... Done Full Text Search... Done broadcom-sta-dkms/stable 6.30.223.271-17 all dkms source for the Broadcom STA Wireless driver ... $ apt show broadcom-sta-dkms Package: broadcom-sta-dkms Version: 6.30.223.271-17 Priority: optional Section: non-free/kernel Source: broadcom-sta Maintainer: Eduard Bloch ... But you don't want to talk to Eduard directly right now; that would be a little rude. Instead, file a bug against the package broadcom-sta-dkms at wishlist priority. -dsr-
Re: Help setting up Broadcom WiFi on a Dell Inspiron 1501 laptop
Thanks, that is a very helpful page. I send a response to your earlier email to the list, and I'm going to do the same with this. On Thursday, August 24, 2017 12:12:47 PM Wim Michels wrote: > Hi, > > have a look at this webpage: > > https://wiki.debian.org/WiFi/HowToUse > > for usefull info. > > On Wednesday, 23 August at 21:40, rhkra...@gmail.com wrote: > >On Sunday, August 20, 2017 03:00:28 PM Wim Michels wrote: > >> Hi, > >> all you need to install is the package: > >> > >> firmware-b43-installer > >> > >> from 'contrib' to get BCM4311 chip to work. > > > >Thanks, that worked!
Re: Help setting up Broadcom WiFi on a Dell Inspiron 1501 laptop
On Wednesday, August 23, 2017 03:40:07 PM rhkra...@gmail.com wrote: > On Sunday, August 20, 2017 03:00:28 PM Wim Michels wrote: > > Hi, > > all you need to install is the package: > > > > firmware-b43-installer > > > > from 'contrib' to get BCM4311 chip to work. > > Thanks, that worked! Just wanted to add one thing--that worked for me in Wheezy, but not in Jessie. It's possible that I did something wrong while in Jessie (I might have typed nonfree instead of non-free in /etc/apt/sources.list). I haven't tried to reinstall Jessie to retry--I plan to live with Wheezy (unless I get very ambitious in the near future. Oh, and I meant to send / keep this on the list, so sending to the list. > > I do need to learn more about how wireless networking and/or Network > Manager work, but I did get connected. > > I did have to reboot after doing the install (as it didn't work before I > rebooted, using about the same things that did work after the reboot). I > suppose if I knew more I might have avoided the reboot, maybe by stopping > and restarting some network related service. (But, this was a new > install, and rebooting did not cause any problems.) > > Thanks again! > > Aside: There were, iirc, three other methods I was thinking of trying to > get it to work (all basically headed in the same direction)--I have some > notes about those in my off-line wiki-like thing and may try experimenting > with those sometime (but, probably not ;-)
Re: Help setting up Broadcom WiFi on a Dell Inspiron 1501 laptop
Thanks to all who replied! I found enough clues here to (1) find ucode5.fw, and (2) to start to develop the enthusiasm to make another attempt. It may be a few days though. Thanks again! Oh, but don't be surprised if I have some followup questions ;-) On Friday, August 18, 2017 04:29:13 PM Celejar wrote: > On Fri, 18 Aug 2017 12:56:28 -0400 > rhkra...@gmail.com wrote: > > ... > > >* All of the Linuxes somehow indicated that I had to load some other > >files > > > > to get the Broadcom working. I eventually realized they were talking > > about firmware that has to be installed on the card. > > Yes, you'll need firmware. > > > I think all of them (or at least Wheezy, iirc, identified those files as > > b43/ucode5.fw and b43-open/ucode5.fw. (Are those two different files, > > and, do I need both or either??). So far, I have not located those > > files anywhere, either using google or searching the (Wheezy) packages > > (including contrib and non-free). > > There is Broadcom's own [proprietary] firmware, and (possibly?) an open > source version. I don't know the state of the OSS version, but the last > time I looked into it, it wasn't entirely stable / reliable. Just use > Broadcom's, unless you know what you're doing and / or have strong > ideological / moral views on the subject. > > Broadcom's version is definitely not included in Debian, even in > non-free. There is, however, the firmware cutter utility and package, > which can download and extract the firmware for and put it in the right > place. Just follow the instructions here: > > http://linuxwireless.org/en/users/Drivers/b43/#Ubuntu.2FDebian > > > I downloaded some packages from the Wheezy repository (after adding > > contrib and non-free): > > > > The downloaded packages: > > firmware-b43-installer version 1:015-14.1 > > That's the one that you want. > > > firmware-brcm80211 version 0.36+wheezy.1 > > I don't think you want / need this one. Again, just follow the > directions here: > > http://linuxwireless.org/en/users/Drivers/b43/ > https://wireless.wiki.kernel.org/en/users/drivers/b43 > > > There were other packages I could have downloaded and tried, but didn't, > > so far. > > > > Those packages provided me with (among other files): > > > > /lib/firmware/brcm/bcm43xx-0.fw > > /lib/firmware/brcm/bcm43xx_hdr-0.fw > > b43-fwcutter > > ... > > > The main questions: So, where do I go from here? Is ucode5.fw an > > obsolete file name? Or maybe that is the name for the Broadcom > > proprietary stuff but what I've found are open source replacements? Is > > ucode5.fw in one of the other Debian packages for Broadcom? Has anyone > > ever got WiFi working with Wheezy and this Broadcom device? > > So what's the problem? Does the card work? Is the driver module > inserted into the kernel? What does dmesg say when you insert it? > [Try "modprobe -r b43" followed by "modprobe b43" and see what dmesg > says.] > > ... > > >* Somewhere I found a blurb that identified it as a "Broadcom Wireless > >1390 > > > > WLAN Mini card" > > Marketing name, not particularly important for us. > > >* Using =lspci -vnn -d 14e4:=, I get the following information: > > PCI-ID Supported? Chip ID Modes PHY version Alternative > > 14e4:4311 yes BCM4311 b/g G wl > > That's what we need - see here: > > http://linuxwireless.org/en/users/Drivers/b43/#Supported_devices > > > IIUC, that means I can use the non-legacy driver (and Wheezy package) > > Correct. > > >* The tag on the bottom of the computer identifies the WiFi device as > > > > BRCM94311MCG, FCC ID: QDS-BRCM1020 > > Not important. > > [I used to use Broadcom wireless, not necessarily this exact card, but > something similar. I haven't had a machine with one for years, but the > instructions are good, and they work when followed.] > > Celejar
Re: Help setting up Broadcom WiFi on a Dell Inspiron 1501 laptop
On Fri, 18 Aug 2017 12:56:28 -0400 rhkra...@gmail.com wrote: ... >* All of the Linuxes somehow indicated that I had to load some other files > to get the Broadcom working. I eventually realized they were talking about > firmware that has to be installed on the card. Yes, you'll need firmware. > I think all of them (or at least Wheezy, iirc, identified those files as > b43/ucode5.fw and b43-open/ucode5.fw. (Are those two different files, and, > do I > need both or either??). So far, I have not located those files anywhere, > either using google or searching the (Wheezy) packages (including contrib and > non-free). There is Broadcom's own [proprietary] firmware, and (possibly?) an open source version. I don't know the state of the OSS version, but the last time I looked into it, it wasn't entirely stable / reliable. Just use Broadcom's, unless you know what you're doing and / or have strong ideological / moral views on the subject. Broadcom's version is definitely not included in Debian, even in non-free. There is, however, the firmware cutter utility and package, which can download and extract the firmware for and put it in the right place. Just follow the instructions here: http://linuxwireless.org/en/users/Drivers/b43/#Ubuntu.2FDebian > I downloaded some packages from the Wheezy repository (after adding contrib > and non-free): > > The downloaded packages: > firmware-b43-installer version 1:015-14.1 That's the one that you want. > firmware-brcm80211 version 0.36+wheezy.1 I don't think you want / need this one. Again, just follow the directions here: http://linuxwireless.org/en/users/Drivers/b43/ https://wireless.wiki.kernel.org/en/users/drivers/b43 > There were other packages I could have downloaded and tried, but didn't, so > far. > > Those packages provided me with (among other files): > > /lib/firmware/brcm/bcm43xx-0.fw > /lib/firmware/brcm/bcm43xx_hdr-0.fw > b43-fwcutter ... > The main questions: So, where do I go from here? Is ucode5.fw an obsolete > file > name? Or maybe that is the name for the Broadcom proprietary stuff but what > I've found are open source replacements? Is ucode5.fw in one of the other > Debian packages for Broadcom? Has anyone ever got WiFi working with Wheezy > and this Broadcom device? So what's the problem? Does the card work? Is the driver module inserted into the kernel? What does dmesg say when you insert it? [Try "modprobe -r b43" followed by "modprobe b43" and see what dmesg says.] ... >* Somewhere I found a blurb that identified it as a "Broadcom Wireless > 1390 > WLAN Mini card" Marketing name, not particularly important for us. >* Using =lspci -vnn -d 14e4:=, I get the following information: > > PCI-ID Supported? Chip ID Modes PHY version Alternative > 14e4:4311 yes BCM4311 b/g G wl That's what we need - see here: http://linuxwireless.org/en/users/Drivers/b43/#Supported_devices > IIUC, that means I can use the non-legacy driver (and Wheezy package) Correct. >* The tag on the bottom of the computer identifies the WiFi device as > BRCM94311MCG, FCC ID: QDS-BRCM1020 Not important. [I used to use Broadcom wireless, not necessarily this exact card, but something similar. I haven't had a machine with one for years, but the instructions are good, and they work when followed.] Celejar
Re: Help setting up Broadcom WiFi on a Dell Inspiron 1501 laptop
On Fri, Aug 18, 2017 at 12:56:28PM -0400, rhkra...@gmail.com wrote: > >... > > Other information: > >* WiFi works fine in Vista > > Identification: > >* Using =lspci -vnn -d 14e4:=, I get the following information: > > PCI-ID Supported? Chip ID Modes PHY version Alternative > 14e4:4311 yes BCM4311 b/g G wl > > > Thanks! > Maybe this package can help? it is for a BCM4311 chipset (debian testing) $ apt-cache show broadcom-sta-common Package: broadcom-sta-common Source: broadcom-sta Version: 6.30.223.271-7 Installed-Size: 33 Description-en: Common files for the Broadcom STA Wireless driver Broadcom STA is a binary-only device driver to support the following IEEE 802.11a/b/g/n wireless network cards: BCM4311-, BCM4312-, BCM4313-, ^^^ Greetings
Help setting up Broadcom WiFi on a Dell Inspiron 1501 laptop
I've decided to ask for help, even though I haven't exhausted all the things I might try on my own--I'm getting too old for this s%#@ This is, in addition to being a request for help, sort of a brain dump, which might even help me realize where I am and find a way forward. Overview: I got a Dell Inspiron 1501 at an estate sale for a very good price, and would like give it to a friend, but would like to have Linux working on it so she can at least consider using Linux. As far as her needs are concerned, if it doesn't work on WiFi it is no good to her. (Aside--Ignore this unless you're very bored: It came with Vista installed, but no password or recovery disk. That was a whole other oddyssey, but I finally managed to get the password by writing to the author of Ophcrack with the NT hash of the password. I had downloaded several different Vista install / recovery ISOs and none of them would boot, the closest I got was a message that said "Bootmgr is missing" even though I could plainly see a bootmgr on the DVD. (I also learned (I think) that although a Linux install can boot from a USB pendrive, apparently (iiuc), a Windows install / recovery disk cannot (but I can't be entirely sure of that because I never got a Windows recovery / install DVD to boot, either.)) Linuxes I have tried: I've tried to install Linuxmint 17.3 and 18.1, and Debian Wheezy and Jessie--all seem to have about the same problem (discussed further below). The laptop currently has only 1 GB of memory and a fairly slow (1.7 or so GHz) dual core processor, so I'm not sure how well it will work with anything newer. (The memory is expandable to either 2 or 4 GB (forget which, atm), and I will probably upgrade it when I have a Linux working with WiFi.) Other "plans": I have ordered a USB WiFi dongle (from eBay / Taiwan, ordered when I thought the WiFi "card" was not included with the laptop). When I get it, I could consider disabling the internal Broadcom device (is it easily physically removable?) and utilizing the dongle. Of course, the delivery of that could be a month or more away. What I think I've learned about the Inspiron, Broadcom, and Linux: * Somebody on this list fairly recently mentioned the problems with Broadcom WiFi devices and i inferred from what they said that LinuxMInt 17.3 might be the easiest Linux distro to get it working, which is why I tried it. * All of the Linuxes somehow indicated that I had to load some other files to get the Broadcom working. I eventually realized they were talking about firmware that has to be installed on the card. I think all of them (or at least Wheezy, iirc, identified those files as b43/ucode5.fw and b43-open/ucode5.fw. (Are those two different files, and, do I need both or either??). So far, I have not located those files anywhere, either using google or searching the (Wheezy) packages (including contrib and non-free). I downloaded some packages from the Wheezy repository (after adding contrib and non-free): The downloaded packages: firmware-b43-installer version 1:015-14.1 firmware-brcm80211 version 0.36+wheezy.1 There were other packages I could have downloaded and tried, but didn't, so far. Those packages provided me with (among other files): /lib/firmware/brcm/bcm43xx-0.fw /lib/firmware/brcm/bcm43xx_hdr-0.fw b43-fwcutter Using the -l option of b43-fwcutter, I see the following (exactly the same for either of the 2 fw files): root@s19:~# b43-fwcutter -l /lib/firmware/brcm/bcm43xx_hdr-0.fw b43-fwcutter version 015 Extracting firmware is possible from these binary driver files. Please read http://linuxwireless.org/en/users/Drivers/b43#devicefirmware b43legacy wl_apsta.o 295.14 e08665c5c5b66beb9c3b2dd54aa80cb3 b43 wl_apsta.o 351.126 9207bc565c2fc9fa1591f6c7911d3fc0 b43 wl_apsta_mimo.o 351.126 722e2e0d8cc04b8f118bb5afe6829ff9 b43 wl_apsta_mimo.o 410.2160 cb8d70972b885b1f8883b943c0261a3c b43 wl_apsta.o 478.104 bb8537e3204a1ea5903fe3e66b5e2763 b43 wl_prebuilt.o 508.1084 490d4e149ecc45eb1a91f06aa75be071 b43 wl_apsta.o 508.1107 f06c8aa30ea549ce21872d10ee9a7d48 b43 wl_apsta.o 508.10872 e413c0017b99195f3231201c53f314d1 b43 wl_apsta.o 508.154 023fafbe4918e384dd531a046dbc03e8 b43 wl_apsta.o 644.1001 68f38d139b1f69f3ea12393fb645c6f9 b43 wl_apsta.o 666.2 e1b05e268bcdbfef3560c28fc161f30e The main questions: So, where do I go from here? Is ucode5.fw an obsolete file name? Or maybe that is the name for the Broadcom proprietary stuff but what I've found are open sourc
SOLVED: Broadcom BCM43225 Wireless Shows Not Connected then Hardware Disabled
It was more of a hardware maintenance issue than a kernel driver issue. Opening the back laptop cover, removing the mini PCI-E WLAN WiFi board and firmly re-seating it solved the problem. Also took the opportunity to blow dry (without the heater element) all the dust inside the laptop. On Fri, Apr 15, 2016 at 8:22 PM Alphonse Ogulla wrote: > The output of the "wireless-info" script when wireless disconnects then > becomes "hardware disabled" is pasted below. > > > ## wireless info START ## > > Report from: 08 Apr 2016 14:21 EAT +0300 > > Booted last: 08 Apr 2016 13:58 EAT +0300 > > Script from: 27 Sep 2015 00:34 UTC + > > # release ### > > Distributor ID: Debian > Description: Debian GNU/Linux 8.4 (jessie) > Release: 8.4 > Codename: jessie > > # kernel > > Linux 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt25-1 (2016-03-06) x86_64 > unknown unknown GNU/Linux > > Parameters: ro, quiet > > # desktop ### > > sed: can't read /root/.dmrc: No such file or directory > > Could not be determined. > > # lspci # > > 02:00.0 Ethernet controller [0200]: Qualcomm Atheros AR8151 v1.0 Gigabit > Ethernet [1969:1073] (rev c0) > Subsystem: Acer Incorporated [ALI] Device [1025:0463] > Kernel driver in use: atl1c > > 03:00.0 Network controller [0280]: Broadcom Corporation BCM43225 > 802.11b/g/n [14e4:4357] (rev 01) > Subsystem: Foxconn International, Inc. T77H103.00 Wireless Half-size Mini > PCIe Card [105b:e021] > Kernel driver in use: bcma-pci-bridge > > # lsusb # > > Bus 002 Device 003: ID 0489:e011 Foxconn / Hon Hai > Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub > Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Bus 001 Device 005: ID 0955:7002 NVidia Corp. > Bus 001 Device 004: ID 0461:4d20 Primax Electronics, Ltd HP Optical Mouse > Bus 001 Device 003: ID 0402:9665 ALi Corp. Gateway Webcam > Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > > # PCMCIA card info ## > > 'pccardctl' is not installed (package "pcmciautils"). > > # rfkill > > 0: acer-wireless: Wireless LAN > Soft blocked: no > Hard blocked: no > 1: acer-bluetooth: Bluetooth > Soft blocked: no > Hard blocked: no > 2: phy0: Wireless LAN > Soft blocked: no > Hard blocked: yes > 3: hci0: Bluetooth > Soft blocked: no > Hard blocked: no > > # lsmod # > > brcmsmac 515930 0 > cordic 12352 1 brcmsmac > brcmutil 13093 1 brcmsmac > acer_wmi 30174 0 > mac80211 474216 1 brcmsmac > sparse_keymap 12818 1 acer_wmi > cfg80211 405538 2 brcmsmac,mac80211 > rfkill 18867 5 cfg80211,acer_wmi,bluetooth > mxm_wmi12515 1 nouveau > bcma 37206 1 brcmsmac > wmi17339 3 acer_wmi,mxm_wmi,nouveau > video 18096 2 acer_wmi,nouveau > > # interfaces > > source /etc/network/interfaces.d/* > > auto lo > iface lo inet loopback > > # ifconfig ## > > eth0 Link encap:Ethernet HWaddr > 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:1000 > RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) > > wlan0 Link encap:Ethernet HWaddr > BROADCAST MULTICAST MTU:1500 Metric:1 > RX packets:8224 errors:0 dropped:0 overruns:0 frame:0 > TX packets:7239 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:355 (6.3 MiB) TX bytes:1346735 (1.2 MiB) > > # iwconfig ## > > eth0 no wireless extensions. > > lono wireless extensions. > > wlan0 IEEE 802.11bgn ESSID:off/any > Mode:Managed Access Point: Not-Associated Tx-Power=off > Retry short limit:7 RTS thr:off Fragment thr:off > Encryption key:off > Power Management:off > > > # route # > > Kernel IP routing table > Destination Gateway Genmask Flags Metric RefUse > Iface > >
Re: Instralling from offline sources: broadcom
On Tue 26 Jul 2016 at 14:24:15 -0700, Alan E. Davis wrote: > I need to install the broadcom-wl wireless adaptor drivers. I have no This was the first thing that struck me - there is no broadcom-wl package. > connection to the internet on this new installation. So it's either this This was the second thing. What did you do to install Debian? > or tethering the iphone to get this package installed. > > Both of these pathways require a plethora of steps to install various > dependencies for dependencies. I was a debian user in the early 90s, and > remember alarm at the penchant of devels to split everything into packages; > now I can remembery why > > Anyway, I need build-depends. Make, of all things, is one of the most > difficult things to install. The third thing is that you appear to be going off on a tangent. > I have installed stretch. Up to this point, it's a fantastic process of > installation. As of now, several problems have kept me back. > > 1. I used a usb of HD medium, so many packages are on this usb drive, but > it's beyond me how to get apt-get to recognize the USB drive as a rep, and > go ahead and complete the update. Probably I need a list of packages. Is "usb of HD medium" some indication of how you installed? Please explain. > 2. I cannot find make on this USB drive in pool. > > 3. I cannot find patch on this USB drive. What is on the drive? How did it get there?
Re: Instralling from offline sources: broadcom
On 7/26/2016 4:24 PM, Alan E. Davis wrote: I need to install the broadcom-wl wireless adaptor drivers. I have no connection to the internet on this new installation. So it's either this or tethering the iphone to get this package installed.[snip] Might apt-offline address some of your issues?
Instralling from offline sources: broadcom
I need to install the broadcom-wl wireless adaptor drivers. I have no connection to the internet on this new installation. So it's either this or tethering the iphone to get this package installed. Both of these pathways require a plethora of steps to install various dependencies for dependencies. I was a debian user in the early 90s, and remember alarm at the penchant of devels to split everything into packages; now I can remembery why Anyway, I need build-depends. Make, of all things, is one of the most difficult things to install. I have installed stretch. Up to this point, it's a fantastic process of installation. As of now, several problems have kept me back. 1. I used a usb of HD medium, so many packages are on this usb drive, but it's beyond me how to get apt-get to recognize the USB drive as a rep, and go ahead and complete the update. Probably I need a list of packages. 2. I cannot find make on this USB drive in pool. 3. I cannot find patch on this USB drive. 4. Individually I have installed a bunch of development packages. 5. Tethering is a huge problem because of ifuse, I think, and other dependency hells. This is enough for now. I would very much appreciate some advice on any of these topics. Once I have broadcom-wl installed it's all downhill I think. I do have the package, but the dependencies are driving me bats. Thank you. Alan Davis -- [I do not] carry such information in my mind since it is readily available in books. …The value of a college education is not the learning of many facts but the training of the mind to think. ---Albert Einstein "Sweet instruments hung up in cases. . . keep their sounds to themselves." ---Shakespeare, _Timon of Athens_
Re: Broadcom BCM43225 Wireless Shows Not Connected then Hardware Disabled
The output of the "wireless-info" script when wireless disconnects then becomes "hardware disabled" is pasted below. ## wireless info START ## Report from: 08 Apr 2016 14:21 EAT +0300 Booted last: 08 Apr 2016 13:58 EAT +0300 Script from: 27 Sep 2015 00:34 UTC + # release ### Distributor ID: Debian Description: Debian GNU/Linux 8.4 (jessie) Release: 8.4 Codename: jessie # kernel Linux 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt25-1 (2016-03-06) x86_64 unknown unknown GNU/Linux Parameters: ro, quiet # desktop ### sed: can't read /root/.dmrc: No such file or directory Could not be determined. # lspci # 02:00.0 Ethernet controller [0200]: Qualcomm Atheros AR8151 v1.0 Gigabit Ethernet [1969:1073] (rev c0) Subsystem: Acer Incorporated [ALI] Device [1025:0463] Kernel driver in use: atl1c 03:00.0 Network controller [0280]: Broadcom Corporation BCM43225 802.11b/g/n [14e4:4357] (rev 01) Subsystem: Foxconn International, Inc. T77H103.00 Wireless Half-size Mini PCIe Card [105b:e021] Kernel driver in use: bcma-pci-bridge # lsusb # Bus 002 Device 003: ID 0489:e011 Foxconn / Hon Hai Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 005: ID 0955:7002 NVidia Corp. Bus 001 Device 004: ID 0461:4d20 Primax Electronics, Ltd HP Optical Mouse Bus 001 Device 003: ID 0402:9665 ALi Corp. Gateway Webcam Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub # PCMCIA card info ## 'pccardctl' is not installed (package "pcmciautils"). # rfkill 0: acer-wireless: Wireless LAN Soft blocked: no Hard blocked: no 1: acer-bluetooth: Bluetooth Soft blocked: no Hard blocked: no 2: phy0: Wireless LAN Soft blocked: no Hard blocked: yes 3: hci0: Bluetooth Soft blocked: no Hard blocked: no # lsmod # brcmsmac 515930 0 cordic 12352 1 brcmsmac brcmutil 13093 1 brcmsmac acer_wmi 30174 0 mac80211 474216 1 brcmsmac sparse_keymap 12818 1 acer_wmi cfg80211 405538 2 brcmsmac,mac80211 rfkill 18867 5 cfg80211,acer_wmi,bluetooth mxm_wmi12515 1 nouveau bcma 37206 1 brcmsmac wmi17339 3 acer_wmi,mxm_wmi,nouveau video 18096 2 acer_wmi,nouveau # interfaces source /etc/network/interfaces.d/* auto lo iface lo inet loopback # ifconfig ## eth0 Link encap:Ethernet HWaddr 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:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) wlan0 Link encap:Ethernet HWaddr BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:8224 errors:0 dropped:0 overruns:0 frame:0 TX packets:7239 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:355 (6.3 MiB) TX bytes:1346735 (1.2 MiB) # iwconfig ## eth0 no wireless extensions. lono wireless extensions. wlan0 IEEE 802.11bgn ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=off Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:off # route # Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface # resolv.conf ### # network managers ## Installed: NetworkManager Running: root 709 1 0 13:58 ?00:00:00 /usr/sbin/NetworkManager --no-daemon # NetworkManager info ### GENERAL.DEVICE: eth0 GENERAL.TYPE: ethernet GENERAL.VENDOR: Qualcomm Atheros GENERAL.PRODUCT:AR8151 v1.0 Gigabit Ethernet GENERAL.DRIVER: atl1c GENERAL.DRIVER-VERSION: 1.0.1.1-NAPI GENERAL.FIRMWARE-VERSION: GENERAL.HWADDR: GENERAL.MTU:1500 GENERAL.STATE: 20 (unavailable) GENERAL.REASON: 2 (Device is now managed) GENERAL.UDI: /sys/devices/pci:00/:00:1c.0/:02:00.0/net/eth0 GENERAL.IP-IFACE: GENERAL.NM-MANAGED: yes GENERAL.AUTOCONNECT:yes GENERAL.FIRMWARE
Broadcom BCM43225 Wireless Shows Not Connected then Hardware Disabled
Greetings. I'm running Jessie on an Acer Aspire 5745DG laptop with a Broadcom BCM43225 wireless chip. Wireless LAN has always worked flawlessly until recently when it started disconnecting abruptly, showing not connected, hardware disabled then disappearing from Network Manager. The laptop only has FN+F3 WiFi on/off toggling. This can happen anytime form 10 minutes to 1 week of working with the only way of recovering being a reboot. Both the open-source "bcma" and proprietary "wl" kernel driver modules produce the same results. I have since purchased a USB WiFi adaptor (Realtek RT8188eu) as a fall back measure but would prefer to have the inbuilt PCI WiFi adaptor working again. Any help will be greatly appreciated. My System. a) Network controller: Broadcom Corporation BCM43225 802.11b/g/n (rev 01) b) Driver Modules: brcmsmac, mac80211, cfg80211, bcma, brcmutil, cordic c) Kernel: Linux 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt20-1+deb8u4 (2016-02-29) x86_64 GNU/Linux What I have Tried a) Restart Network Manager b) Unloading and reloading the drivers c) Trying the proprietary wl driver d) Setting REGDOMAIN in /etc/default/crda to KE, IN, US etc. e) Installing rfkill and ensuring Wireless is NOT soft or hard blocked. f) Googling and trying instructions at http://askubuntu.com/questions/503936/wireless-randomly-becoming-phantom-hardblocked-only-fixed-by-reboot Dmesg Snippet > > [75536.589575] brcmsmac bcma0:0: brcms_ops_bss_info_changed: qos enabled: > false (implement) > [75536.589588] brcmsmac bcma0:0: brcms_ops_config: change power-save mode: > false (implement) > [75536.590676] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready > [75539.587022] wlan0: authenticate with e0:69:95:xx.xx.xx > [75539.587103] wlan0: send auth to e0:69:95:xx.xx.xx (try 1/3) > [75539.589717] wlan0: authenticated > [75539.589961] wlan0: associate with e0:69:95:38:38:d3 (try 1/3) > [75539.592452] wlan0: RX AssocResp from e0:69:95:38:38:d3 (capab=0x411 > status=0 aid=4) > [75539.593092] brcmsmac bcma0:0: brcmsmac: brcms_ops_bss_info_changed: > associated > [75539.593097] brcmsmac bcma0:0: brcms_ops_bss_info_changed: qos enabled: > true (implement) > [75539.593108] wlan0: associated > [75539.593121] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready > [75539.596486] brcmsmac bcma0:0: wl0: brcms_c_d11hdrs_mac80211: \xffd8sۚ > txop exceeded phylen 159/256 dur 1778/1504 > [75539.602524] brcmsmac bcma0:0: wl0: brcms_c_d11hdrs_mac80211: \xffd8sۚ > txop exceeded phylen 137/256 dur 1602/1504 > [75563.605657] brcmsmac bcma0:0: brcms_ops_bss_info_changed: arp filtering: 1 > addresses (implement) > [81755.330981] brcmsmac bcma0:0: wl0: brcms_c_watchdog: dead chip > [81755.462986] brcmsmac bcma0:0: ops->tx called while down > [81755.988124] brcmsmac bcma0:0: brcmsmac: brcms_ops_bss_info_changed: > disassociated > [81755.988136] brcmsmac bcma0:0: brcms_ops_bss_info_changed: arp filtering: 1 > addresses (implement) > [81755.988140] brcmsmac bcma0:0: brcms_ops_bss_info_changed: qos enabled: > false (implement) > [81755.988145] brcmsmac bcma0:0: wl0: brcms_c_wme_setparams : no-clock > [81755.988148] brcmsmac bcma0:0: wl0: brcms_c_wme_setparams : no-clock > [81755.988151] brcmsmac bcma0:0: wl0: brcms_c_wme_setparams : no-clock > [81755.988153] brcmsmac bcma0:0: wl0: brcms_c_wme_setparams : no-clock > [81755.995598] cfg80211: Calling CRDA to update world regulatory domain > [81756.115171] brcmsmac bcma0:0: ops->tx called while down > [81756.115183] brcmsmac bcma0:0: ops->tx called while down > ... > ... > [81756.283287] brcmsmac bcma0:0: ops->tx called while down > [81756.330413] cfg80211: World regulatory domain updated: > [81756.330419] cfg80211: DFS Master region: unset > [81756.330421] cfg80211: (start_freq - end_freq @ bandwidth), > (max_antenna_gain, max_eirp), (dfs_cac_time) > [81756.330426] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (N/A, > 2000 mBm), (N/A) > [81756.330429] cfg80211: (2457000 KHz - 2482000 KHz @ 4 KHz), (N/A, > 2000 mBm), (N/A) > [81756.330433] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (N/A, > 2000 mBm), (N/A) > [81756.330437] cfg80211: (517 KHz - 525 KHz @ 8 KHz, 16 KHz > AUTO), (N/A, 2000 mBm), (N/A) > [81756.330441] cfg80211: (525 KHz - 533 KHz @ 8 KHz, 16 KHz > AUTO), (N/A, 2000 mBm), (0 s) > [81756.330444] cfg80211: (549 KHz - 573 KHz @ 16 KHz), (N/A, > 2000 mBm), (0 s) > [81756.330447] cfg80211: (5735000 KHz - 5835000 KHz @ 8 KHz), (N/A, > 2000 mBm), (N/A) > [81756.330451] cfg80211: (5724 KHz - 6372 KHz @ 216 KHz), (N/A, > 0 mBm), (N/A) > [81756.339190] brcmsmac bcma0:0: ops->tx called while down > [81756.339202] brcmsmac bcma0:0: ops->tx called while down > ... > ... > [81756.395272] brcmsmac bcma0:0: ops->tx called while down -- Thanks & Regards
Re: Unable to connect to higher wifi channels with Broadcom BCM4360
Try changing your regulatory. One should not, but that's the solution. I am using it. Try "iw reg set uk".
Unable to connect to higher wifi channels with Broadcom BCM4360
Hi everyone, I have a Broadcom BCM4360 wireless card (Archer T8E), which uses the wl module (version 6.30.223.248 on jessie). I am unable to connect to channel 100 or higher on the 5GHz band. The problem seems to be: `iwlist wlan0 chan` returns: wlan0 32 channels in total; available frequencies : Channel 01 : 2.412 GHz [snip] Channel 64 : 5.32 GHz Channel 66 : 5.33 GHz Channel 68 : 5.34 GHz Channel 96 : 5.48 GHz Current Frequency:5.22 GHz (Channel 44) `iw reg get` gives me: country DE: DFS-ETSI (2400 - 2483 @ 40), (N/A, 20), (N/A) (5150 - 5250 @ 80), (N/A, 20), (N/A), NO-OUTDOOR (5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS (5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS (57000 - 66000 @ 2160), (N/A, 40), (N/A) Am I missing something or is the card and the module just not supporting higher channels? I would be thankful for any pointers. Cheers, Simon
Re: Broadcom TG3 network drops, cannot recover without reboot
On Wednesday 14 October 2015 12:04:27 Toan Pham wrote: > Justin, > > Have you found a solution to the NIC issue yet? > > FYI, I was working with Broadcom's test team but they pretty much > dropped the ball on me So it is all up to us to find a solution! > Please share if you know how to get the NIC not to drop out > intermitently. > > thank you, > > TP From my lengthy but 100% failed experinces with BC, including hacking up the ndiswrapper to use the winderz drivers, you would be far better off to vote with your wallet and change the brand name on the card. On my old HP lappy, which had XP on it as OEM, and a broadcom 4318 radio in it, one that would not connect for more than 15 seconds when running XP, so I plugged in a netgear USB radio, rebooted, and it just worked(tm). But I've upgraded the lappy to an XFCE vesion of Mint 17 now, and I've shut the wired relay router's radio off in the shop because a neighbor had managed the passphrase & was using my bandwidth. Shut it off hard by replacing the router with a small 4 port hub. :) They can't use what isn't available. I still don't think I have any neighbors that close AND that smart, but it happened. They could not get to me, but they could get to the internet thru it as it had access to the gateway router. That one is running dd-wrt, and the only one who has come thru it, I had to give him the username & pw. I used to watch the logs, but that was a boring waste of time. Nothing unwanted gets thru dd-wrt. YMMV of course, but some folks enjoy the challenge of trying to make broken by design stuff work. I do too, but there is a point too far that you can easily surpass with BC gear. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: Broadcom TG3 network drops, cannot recover without reboot
Justin, Have you found a solution to the NIC issue yet? FYI, I was working with Broadcom's test team but they pretty much dropped the ball on me So it is all up to us to find a solution! Please share if you know how to get the NIC not to drop out intermitently. thank you, TP On Thu, May 28, 2015 at 3:48 AM, Justin Catterall wrote: > > > On 27 May 2015, at 17:06, Toan Pham wrote: > > > > Justin, > > > > > > I've observed a similar symptom on the bcm5762 chip, not the 5720, and > > not sure if the bugs they are related. I've filed a bug report > > (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1447664), and > > actively working with Broadcom's engineering team to get this bug > > resolved. They are running multiple test cases but could not get this > > bug to surface in a short amount of time. > > > >> In the mean time I've made a bash-script to rmmod and modprobe as > appropriate. I'll set a cron job to ping a couple of other servers on the > LAN and execute the script and restart networking should the pings fail. > > > > This is a patch, not a fix. Have you tested on kernel 4.0? > > I've not tested with 4.0. This machine needs to be rock solid, it will be > Debian stable all the way, 4.x will only get on this machine when stable is > updated to that kernel. > > > > Alternatively, try to get yourself an Intel NIC that works with the igb > >> driver (don't get an Intel NIC that needs the e1000e driver) to replace > >> the hardlock-prone bcm5720 + tg3 combination. > > > > I ended up with an intel NIC instead, but with the e1000e driver. > > What's wrong with the e1000e driver by the way, please update. Thank > > you > > You'll have to hope Henrique is still following this, I don't have an > answer. > > Just thinking out-loud here: I've got an identical server with FreeNAS > installed, that's never disappeared off the network. Also I've had a server > for about 5 years at home with the same on-board NIC, (different mobo), > that's never locked up either, but I was able to force it to lock up with > "/etc/init.d/networking restart". It seems that, at home at least, I've > been fortunate so far. WRT to the FreeNAS, I have no idea how that's > driving the NIC, listing the modules there doesn't show anything I > recognise, and I've minimal experience with *BSD. > > -- > Justin C, by the sea. > > -- > To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact > listmas...@lists.debian.org > Archive: > https://lists.debian.org/a1e820dd-50c4-4708-8816-f9506ad1c...@masonsmusic.co.uk > >
Re: Broadcom 43121 wlan issue
On Sun, Oct 04, 2015 at 11:23:29AM +0200, Petter Adsen wrote: > > My guess is that it has problems with the newer kernel, but without > that file it's impossible to say why it failed to build. Another guess > would be that you haven't installed the kernel headers, which are > required to build that package. > > AFAICT a 4.1 kernel isn't (and shouldn't be, AIUI) in the Jessie repos, > you might be better off running a supported one. It's in Jessie backports.
Re: Broadcom 43121 wlan issue
On Sunday 04 October 2015 15:46:36 Himanshu Shekhar wrote: > apt-get upgrade possible upgraded openjdk 6 to openjdk7 (possibly because > backports are included in my sources, I don't know precisely), after which > libreoffice didn't start even from terminal. > After much guess work, I tried installing libreoffice5, which was available > in backports. > Now, libreoffice is working fine, without any issue. > > Also, please clarify about *using backports safely* http://backports.debian.org/Instructions/ Lisi > > On Sun, Oct 4, 2015 at 8:10 PM, Lisi Reisz wrote: > > On Sunday 04 October 2015 11:39:55 Himanshu Shekhar wrote: > > > infact after updating java.. > > > > How? You need to give a lot more detail. > > > > > libreoffice4 failed and i had to install > > > libreoffice5 from jessie backports. > > > > Lisi
Re: Broadcom 43121 wlan issue
On Sunday 04 October 2015 13:29:32 Himanshu Shekhar wrote: > Yup! got it. I attached my sources.list file in the very first message of > the thread. I would like to have suggestions on the same. Read: https://wiki.debian.org/SourcesList Then the following might be helpful - but beware, they are not official. But neither is the mess you have at the moment! (http://www.debianadmin.com/debian-sources-list-generator.html) This looks great, but didn't work for me. http://debgen.simplylinux.ch/ Out of date, but works fine if used carefully. Here is my wheezy sources.list: --- deb http://ftp.uk.debian.org/debian wheezy main contrib non-free deb-src http://ftp.uk.debian.org/debian wheezy main contrib non-free deb http://ftp.debian.org/debian/ wheezy-updates main contrib non-free deb-src http://ftp.debian.org/debian/ wheezy-updates main contrib non-free deb http://security.debian.org/ wheezy/updates main contrib non-free deb-src http://security.debian.org/ wheezy/updates main contrib non-free deb http://ftp.at.debian.org/debian wheezy-backports main contrib non-free deb http://mozilla.debian.net/ wheezy-backports iceweasel-release deb http://www.deb-multimedia.org wheezy main non-free You need the first, third and fifth (having changed wheezy to jessie). src is up to you. Use anything else with caution and having researched the caveats. Lisi > Also, I have installed few packages from tarballs, as my realtek r8101 > ethernet driver, skype. > That's all! > > On Sun, Oct 4, 2015 at 5:14 PM, Lisi Reisz wrote: > > On Sunday 04 October 2015 11:39:55 Himanshu Shekhar wrote: > > > thanks dude ! i upgraded my driver. But can you tell why some packages > > > break after updating to newer version and still debian stable version > > > is named so. > > > infact after updating java.. libreoffice4 failed and i had to install > > > libreoffice5 from jessie backports. > > > Is this normal or and issue? > > > Thanks for the help! > > > > There is not enough detail here, but it is probably something to do with > > the > > fact that you have jessie backports in your sources list. If you stick > > to Jessie, and only Jessie, things won't break after updating to a newer > > version. In fact, things normally won't update to a newer version. > > Basically, Stabel only gets security updates. > > > > I personally have never had a problem with backports, but you don't say > > how you are using backpprts or how you have got them pinned. And have > > you any packages installed from tarballs, or otherwise not in Debian's > > repos? > > > > You might want to sort out your security repos. > > > > Lisi
Re: Broadcom 43121 wlan issue
apt-get upgrade possible upgraded openjdk 6 to openjdk7 (possibly because backports are included in my sources, I don't know precisely), after which libreoffice didn't start even from terminal. After much guess work, I tried installing libreoffice5, which was available in backports. Now, libreoffice is working fine, without any issue. Also, please clarify about *using backports safely* On Sun, Oct 4, 2015 at 8:10 PM, Lisi Reisz wrote: > On Sunday 04 October 2015 11:39:55 Himanshu Shekhar wrote: > > infact after updating java.. > > How? You need to give a lot more detail. > > > libreoffice4 failed and i had to install > > libreoffice5 from jessie backports. > > Lisi > > -- Himanshu Shekhar IIIT-Allahabad IRM2015006
Re: Broadcom 43121 wlan issue
On Sunday 04 October 2015 11:39:55 Himanshu Shekhar wrote: > infact after updating java.. How? You need to give a lot more detail. > libreoffice4 failed and i had to install > libreoffice5 from jessie backports. Lisi
Re: Broadcom 43121 wlan issue
Hallo, * Himanshu Shekhar [Sun, Oct 04 2015, 04:09:55PM]: > thanks dude ! i upgraded my driver. But can you tell why some packages > break after updating to newer version and still debian stable version is > named so. > infact after updating java.. libreoffice4 failed and i had to install > libreoffice5 from jessie backports. > Is this normal or and issue? This is not the whole truth. You DELIBERATELY installed a kernel from backports, now you have to deal with consequences. Regards, Eduard. -- Fällt der Pfarrer in den Mist, lacht der Bauer, bis er pißt.
Re: Broadcom 43121 wlan issue
here's the sources.list file On Sun, Oct 4, 2015 at 5:59 PM, Himanshu Shekhar wrote: > Yup! got it. I attached my sources.list file in the very first message of > the thread. I would like to have suggestions on the same. > Also, I have installed few packages from tarballs, as my realtek r8101 > ethernet driver, skype. > That's all! > > On Sun, Oct 4, 2015 at 5:14 PM, Lisi Reisz wrote: > >> On Sunday 04 October 2015 11:39:55 Himanshu Shekhar wrote: >> > thanks dude ! i upgraded my driver. But can you tell why some packages >> > break after updating to newer version and still debian stable version is >> > named so. >> > infact after updating java.. libreoffice4 failed and i had to install >> > libreoffice5 from jessie backports. >> > Is this normal or and issue? >> > Thanks for the help! >> >> There is not enough detail here, but it is probably something to do with >> the >> fact that you have jessie backports in your sources list. If you stick to >> Jessie, and only Jessie, things won't break after updating to a newer >> version. In fact, things normally won't update to a newer version. >> Basically, Stabel only gets security updates. >> >> I personally have never had a problem with backports, but you don't say >> how >> you are using backpprts or how you have got them pinned. And have you any >> packages installed from tarballs, or otherwise not in Debian's repos? >> >> You might want to sort out your security repos. >> >> Lisi >> >> > > > -- > Himanshu Shekhar > IIIT-Allahabad > IRM2015006 > -- Himanshu Shekhar IIIT-Allahabad IRM2015006 sources.list Description: Binary data
Re: Broadcom 43121 wlan issue
Yup! got it. I attached my sources.list file in the very first message of the thread. I would like to have suggestions on the same. Also, I have installed few packages from tarballs, as my realtek r8101 ethernet driver, skype. That's all! On Sun, Oct 4, 2015 at 5:14 PM, Lisi Reisz wrote: > On Sunday 04 October 2015 11:39:55 Himanshu Shekhar wrote: > > thanks dude ! i upgraded my driver. But can you tell why some packages > > break after updating to newer version and still debian stable version is > > named so. > > infact after updating java.. libreoffice4 failed and i had to install > > libreoffice5 from jessie backports. > > Is this normal or and issue? > > Thanks for the help! > > There is not enough detail here, but it is probably something to do with > the > fact that you have jessie backports in your sources list. If you stick to > Jessie, and only Jessie, things won't break after updating to a newer > version. In fact, things normally won't update to a newer version. > Basically, Stabel only gets security updates. > > I personally have never had a problem with backports, but you don't say how > you are using backpprts or how you have got them pinned. And have you any > packages installed from tarballs, or otherwise not in Debian's repos? > > You might want to sort out your security repos. > > Lisi > > -- Himanshu Shekhar IIIT-Allahabad IRM2015006
Re: Broadcom 43121 wlan issue
On Sunday 04 October 2015 11:39:55 Himanshu Shekhar wrote: > thanks dude ! i upgraded my driver. But can you tell why some packages > break after updating to newer version and still debian stable version is > named so. > infact after updating java.. libreoffice4 failed and i had to install > libreoffice5 from jessie backports. > Is this normal or and issue? > Thanks for the help! There is not enough detail here, but it is probably something to do with the fact that you have jessie backports in your sources list. If you stick to Jessie, and only Jessie, things won't break after updating to a newer version. In fact, things normally won't update to a newer version. Basically, Stabel only gets security updates. I personally have never had a problem with backports, but you don't say how you are using backpprts or how you have got them pinned. And have you any packages installed from tarballs, or otherwise not in Debian's repos? You might want to sort out your security repos. Lisi
Re: Broadcom 43121 wlan issue
thanks dude ! i upgraded my driver. But can you tell why some packages break after updating to newer version and still debian stable version is named so. infact after updating java.. libreoffice4 failed and i had to install libreoffice5 from jessie backports. Is this normal or and issue? Thanks for the help! On Sun, Oct 4, 2015 at 3:35 PM, Eduard Bloch wrote: > Hallo, > * Himanshu Shekhar [Sun, Oct 04 2015, 03:06:34PM]: > > I have no idea of what has happened to my system. My sources.list is > > attached along with make.log. If I need to downgrade my kernel, please > > provide a fix. > > Thanks for replying... I was waiting! > > Downgrade the kernel or upgrade the driver, your choice. > > https://packages.debian.org/sid/broadcom-sta-dkms > https://packages.debian.org/sid/broadcom-sta-common > https://packages.debian.org/sid/broadcom-sta-source > > Regards, > Eduard. > -- Himanshu Shekhar IIIT-Allahabad IRM2015006
Re: Broadcom 43121 wlan issue
Hallo, * Himanshu Shekhar [Sun, Oct 04 2015, 03:06:34PM]: > I have no idea of what has happened to my system. My sources.list is > attached along with make.log. If I need to downgrade my kernel, please > provide a fix. > Thanks for replying... I was waiting! Downgrade the kernel or upgrade the driver, your choice. https://packages.debian.org/sid/broadcom-sta-dkms https://packages.debian.org/sid/broadcom-sta-common https://packages.debian.org/sid/broadcom-sta-source Regards, Eduard.
Re: Broadcom 43121 wlan issue
I have no idea of what has happened to my system. My sources.list is attached along with make.log. If I need to downgrade my kernel, please provide a fix. Thanks for replying... I was waiting! I would appreciate any help! On Sun, Oct 4, 2015 at 2:53 PM, Petter Adsen wrote: > On Sun, 4 Oct 2015 13:22:44 +0530 > Himanshu Shekhar wrote: > > > I updated my system last night after which I was not able to use network > on > > my laptop. I tried to install ethernet driver as I had it locally but > could > > not make the wifi work. > > Earlier the /lib/modules folder had 3.16* directory only, now I could see > > some 4.1* alongside. Also, the driver in use was *wl* which was working > > fine, but now I couldn't install wl. The installation reports are in the > > attachments. > > The first time I installed Debian 8.1, I had the same issue, traversed > > Synaptic and installed broadcom-sta-dkms which fixed the issue. > > Your 'wl' issue is a red herring, that package is a mail client for > Emacs, not a driver. broadcom-sta-dkms failed to build, if you read the > final line of output it advises you on your next course of action: > > "Consult /var/lib/dkms/broadcom-sta/6.30.223.248/build/make.log for > more information." > > My guess is that it has problems with the newer kernel, but without > that file it's impossible to say why it failed to build. Another guess > would be that you haven't installed the kernel headers, which are > required to build that package. > > AFAICT a 4.1 kernel isn't (and shouldn't be, AIUI) in the Jessie repos, > you might be better off running a supported one. > > Petter > > -- > "I'm ionized" > "Are you sure?" > "I'm positive." > > -- Himanshu Shekhar IIIT-Allahabad IRM2015006 DKMS make.log for broadcom-sta-6.30.223.248 for kernel 4.1.0-0.bpo.2-amd64 (x86_64) Sun Oct 4 12:46:39 IST 2015 /bin/sh: 1: [: Illegal number: /bin/sh: 1: [: Illegal number: Wireless Extension is the only possible API for this kernel version Using Wireless Extension API KBUILD_NOPEDANTIC=1 make -C /lib/modules/4.1.0-0.bpo.2-amd64/build M=`pwd` make[1]: Entering directory '/usr/src/linux-headers-4.1.0-0.bpo.2-amd64' CFG80211 API is prefered for this kernel version Using CFG80211 API Kernel architecture is X86_64 LD /var/lib/dkms/broadcom-sta/6.30.223.248/build/built-in.o CC [M] /var/lib/dkms/broadcom-sta/6.30.223.248/build/src/shared/linux_osl.o CC [M] /var/lib/dkms/broadcom-sta/6.30.223.248/build/src/wl/sys/wl_linux.o CC [M] /var/lib/dkms/broadcom-sta/6.30.223.248/build/src/wl/sys/wl_iw.o CC [M] /var/lib/dkms/broadcom-sta/6.30.223.248/build/src/wl/sys/wl_cfg80211_hybrid.o /var/lib/dkms/broadcom-sta/6.30.223.248/build/src/wl/sys/wl_cfg80211_hybrid.c: In function ‘wl_cfg80211_get_key’: /var/lib/dkms/broadcom-sta/6.30.223.248/build/src/wl/sys/wl_cfg80211_hybrid.c:1390:9: warning: passing argument 1 of ‘memcpy’ discards ‘const’ qualifier from pointer target type memcpy(params.key, key.data, params.key_len); ^ In file included from /usr/src/linux-headers-4.1.0-0.bpo.2-common/arch/x86/include/asm/string.h:4:0, from /usr/src/linux-headers-4.1.0-0.bpo.2-common/include/linux/string.h:17, from /usr/src/linux-headers-4.1.0-0.bpo.2-common/include/linux/bitmap.h:8, from /usr/src/linux-headers-4.1.0-0.bpo.2-common/include/linux/cpumask.h:11, from /usr/src/linux-headers-4.1.0-0.bpo.2-common/arch/x86/include/asm/cpumask.h:4, from /usr/src/linux-headers-4.1.0-0.bpo.2-common/arch/x86/include/asm/msr.h:10, from /usr/src/linux-headers-4.1.0-0.bpo.2-common/arch/x86/include/asm/processor.h:20, from /usr/src/linux-headers-4.1.0-0.bpo.2-common/arch/x86/include/asm/thread_info.h:49, from /usr/src/linux-headers-4.1.0-0.bpo.2-common/include/linux/thread_info.h:54, from /usr/src/linux-headers-4.1.0-0.bpo.2-common/arch/x86/include/asm/preempt.h:6, from /usr/src/linux-headers-4.1.0-0.bpo.2-common/include/linux/preempt.h:18, from /usr/src/linux-headers-4.1.0-0.bpo.2-common/include/linux/spinlock.h:50, from /usr/src/linux-headers-4.1.0-0.bpo.2-common/include/linux/seqlock.h:35, from /usr/src/linux-headers-4.1.0-0.bpo.2-common/include/linux/time.h:5, from /usr/src/linux-headers-4.1.0-0.bpo.2-common/include/linux/stat.h:18, from /usr/src/linux-headers-4.1.0-0.bpo.2-common/include/linux/module.h:10, from /var/lib/dkms/broadcom-sta/6.30.223.248/build/src/include/linuxver.h:40, from /var/lib/dkms/broadcom-sta/6.30.223.248/build/src/wl/sys/wl_cfg80211_hybrid.c:26: /usr/src/linux-headers-4.1.0-0.b
Re: Broadcom 43121 wlan issue
On Sun, 4 Oct 2015 13:22:44 +0530 Himanshu Shekhar wrote: > I updated my system last night after which I was not able to use network on > my laptop. I tried to install ethernet driver as I had it locally but could > not make the wifi work. > Earlier the /lib/modules folder had 3.16* directory only, now I could see > some 4.1* alongside. Also, the driver in use was *wl* which was working > fine, but now I couldn't install wl. The installation reports are in the > attachments. > The first time I installed Debian 8.1, I had the same issue, traversed > Synaptic and installed broadcom-sta-dkms which fixed the issue. Your 'wl' issue is a red herring, that package is a mail client for Emacs, not a driver. broadcom-sta-dkms failed to build, if you read the final line of output it advises you on your next course of action: "Consult /var/lib/dkms/broadcom-sta/6.30.223.248/build/make.log for more information." My guess is that it has problems with the newer kernel, but without that file it's impossible to say why it failed to build. Another guess would be that you haven't installed the kernel headers, which are required to build that package. AFAICT a 4.1 kernel isn't (and shouldn't be, AIUI) in the Jessie repos, you might be better off running a supported one. Petter -- "I'm ionized" "Are you sure?" "I'm positive."
Broadcom 43121 wlan issue
I updated my system last night after which I was not able to use network on my laptop. I tried to install ethernet driver as I had it locally but could not make the wifi work. Earlier the /lib/modules folder had 3.16* directory only, now I could see some 4.1* alongside. Also, the driver in use was *wl* which was working fine, but now I couldn't install wl. The installation reports are in the attachments. The first time I installed Debian 8.1, I had the same issue, traversed Synaptic and installed broadcom-sta-dkms which fixed the issue. -- Himanshu Shekhar IIIT-Allahabad IRM2015006 dkms-install Description: Binary data lspci Description: Binary data modprobe_wl Description: Binary data wl_install Description: Binary data
Re: Broadcom 4311 network adapter doesn't work under Jessie (was debian-user-digest Digest V2015 #1143)
You can search for respective driver on kernel.org, and also Google it. Also, you can search for the required firmware on your manufacturer's website. Good luck! On Fri, Sep 25, 2015 at 5:28 AM, Jose Martinez wrote: > On Wed, 2015-09-23 at 19:08 -0400, Stephen Powell wrote: > > On Wed, 23 Sep 2015 08:23:39 -0400 (EDT), Edward Lukacs wrote: > > > > > > Oh, yes ... I can't get the ... Broadcom 4311 internal card > > > running under Jessie. ... Strange, but up to and including Ubuntu > > > 10.04, it ran right out of the box without any fuss ... > > > > Sounds like missing firmware. Do you have the non-free and contrib > > sections of the Debian archive enabled in /etc/apt/sources.list? > > Do you have Debian package firmware-b43-installer installed? > > > > After installing it, and rebooting, issue > > > >dmesg|less > > > > and search for the string "firmware" to see if the firmware loaded > > properly this time, and to see if there are any other missing firmware > > files for other hardware that requires firmware. > > > > By the way, please choose a more appropriate subject line in your posts > > to this list. It's more likely to get attention that way. > > > > I am CCing you because the subject line implies that you are not > > subscribed to the main list. Please do not CC me back; just reply to > > the list, since I am subscribed to the list. > > > I'm also using an old laptop with an old B43 wireless NIC. I have also > had a little trouble making it work, but after some effort have got it > pretty well figured out. Make sure that the b43 driver package is > installed (firmware-b43legacy-installer). You will also need the > b43-fwcutter package to obtain and install the proprietary firmware for > the NIC. Installation of the firmware package will require internet > access as it downloads the firmware from Broadcom. As I recall, the > b43-fwcutter package is automatically installed when you install the > firmware-b43legacy-installer package, but you might want to make sure > that that is true. > > Once you install these packages, reboot the system!! (I forgot to do > this once, and spent quite a bit of time scratching my head wondering > why my NIC didn't come up.) When the system boots up, it will load the > firmware into the NIC and you should be good to go. Be sure to be > patient when booting the system, the wireless card may not come up until > just about the time the login dialog appears on the screen. That's the > way mine works, so don't get worried if the light for the wireless card > doesn't come on right away when the system starts booting, it may be > nearly login time before it does. > > > -- Himanshu Shekhar IIIT-Allahabad IRM2015006
Re: Broadcom 4311 network adapter doesn't work under Jessie (was debian-user-digest Digest V2015 #1143)
On Wed, 2015-09-23 at 19:08 -0400, Stephen Powell wrote: > On Wed, 23 Sep 2015 08:23:39 -0400 (EDT), Edward Lukacs wrote: > > > > Oh, yes ... I can't get the ... Broadcom 4311 internal card > > running under Jessie. ... Strange, but up to and including Ubuntu > > 10.04, it ran right out of the box without any fuss ... > > Sounds like missing firmware. Do you have the non-free and contrib > sections of the Debian archive enabled in /etc/apt/sources.list? > Do you have Debian package firmware-b43-installer installed? > > After installing it, and rebooting, issue > >dmesg|less > > and search for the string "firmware" to see if the firmware loaded > properly this time, and to see if there are any other missing firmware > files for other hardware that requires firmware. > > By the way, please choose a more appropriate subject line in your posts > to this list. It's more likely to get attention that way. > > I am CCing you because the subject line implies that you are not > subscribed to the main list. Please do not CC me back; just reply to > the list, since I am subscribed to the list. > I'm also using an old laptop with an old B43 wireless NIC. I have also had a little trouble making it work, but after some effort have got it pretty well figured out. Make sure that the b43 driver package is installed (firmware-b43legacy-installer). You will also need the b43-fwcutter package to obtain and install the proprietary firmware for the NIC. Installation of the firmware package will require internet access as it downloads the firmware from Broadcom. As I recall, the b43-fwcutter package is automatically installed when you install the firmware-b43legacy-installer package, but you might want to make sure that that is true. Once you install these packages, reboot the system!! (I forgot to do this once, and spent quite a bit of time scratching my head wondering why my NIC didn't come up.) When the system boots up, it will load the firmware into the NIC and you should be good to go. Be sure to be patient when booting the system, the wireless card may not come up until just about the time the login dialog appears on the screen. That's the way mine works, so don't get worried if the light for the wireless card doesn't come on right away when the system starts booting, it may be nearly login time before it does.
Re: Broadcom 4311 network adapter doesn't work under Jessie (was debian-user-digest Digest V2015 #1143)
Good morning Edward I had similar problems. My work around was to wire conect the laptops into the modem for the install, then dkpg -ì the firmware. Good luck On 24 September 2015 9:08:11 am AEST, Stephen Powell wrote: >On Wed, 23 Sep 2015 08:23:39 -0400 (EDT), Edward Lukacs wrote: >> >> Oh, yes ... I can't get the ... Broadcom 4311 internal card >> running under Jessie. ... Strange, but up to and including Ubuntu >> 10.04, it ran right out of the box without any fuss ... > >Sounds like missing firmware. Do you have the non-free and contrib >sections of the Debian archive enabled in /etc/apt/sources.list? >Do you have Debian package firmware-b43-installer installed? > >After installing it, and rebooting, issue > > dmesg|less > >and search for the string "firmware" to see if the firmware loaded >properly this time, and to see if there are any other missing firmware >files for other hardware that requires firmware. > >By the way, please choose a more appropriate subject line in your posts >to this list. It's more likely to get attention that way. > >I am CCing you because the subject line implies that you are not >subscribed to the main list. Please do not CC me back; just reply to >the list, since I am subscribed to the list. > >-- > .''`. Stephen Powell > : :' : > `. `'` > `- -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Broadcom 4311 network adapter doesn't work under Jessie (was debian-user-digest Digest V2015 #1143)
On Wed, 23 Sep 2015 08:23:39 -0400 (EDT), Edward Lukacs wrote: > > Oh, yes ... I can't get the ... Broadcom 4311 internal card > running under Jessie. ... Strange, but up to and including Ubuntu > 10.04, it ran right out of the box without any fuss ... Sounds like missing firmware. Do you have the non-free and contrib sections of the Debian archive enabled in /etc/apt/sources.list? Do you have Debian package firmware-b43-installer installed? After installing it, and rebooting, issue dmesg|less and search for the string "firmware" to see if the firmware loaded properly this time, and to see if there are any other missing firmware files for other hardware that requires firmware. By the way, please choose a more appropriate subject line in your posts to this list. It's more likely to get attention that way. I am CCing you because the subject line implies that you are not subscribed to the main list. Please do not CC me back; just reply to the list, since I am subscribed to the list. -- .''`. Stephen Powell : :' : `. `'` `-
Re: Broadcom bluetooth on ASUS Z97-Pro WiFi ac
On 9/12/15, Len Berman wrote: > I'm running jessie on an ASUS z97-pro wifi ac motherboard and can't get > bluetooth working. This doesn't surprise me since the log message shows: > > kernel: [76077.598420] Bluetooth: hci0: BCM: patch > brcm/2070BCM2A0-0b05-17cf.hcd not found > > I've googled this but haven't found anything that I can understand and I've > no idea how to proceed. > > Would greatly appreciate any suggestions. (Please copy me as I don't > subscribe to this list.) Ok, I've got a partial possible lead until someone with better insight comes across this. I tried two Internet searches. Both ended up at Ubuntu Forums. Since I'm not clear on the protocol re posting links directly to their site, I found both via these two searches that were broken pieces of your error message: Bluetooth: hci0: BCM: patch brcm brcm/2070BCM2A0-0b05-17cf.hcd The first one's search returned a solved page where they were able to "wget" theirs off the Net. It unfortunately was slightly different from yours. They then copied it over to where it belongs, modprobe'd btusb (looks like remove and [reinstate]), and off they went. For the second search, I received back ONE entry. That one involved the user obtaining kernel source, editing, and then recompiling/reinstalling btusb. Basically I'm regurgitating from the Net with the experience of having seen similar terminology bantered about here and there. Give me a couple weeks, and it may be that I had to do this myself firsthand, too. Time will tell.. *grin* Hope this helps at least a little.. If nothing else, maybe it at least helped short track someone else's answer... or something. :) Cindy :) -- Cindy-Sue Causey Talking Rock, Pickens County, Georgia, USA * runs... into brick walls on occasion. figuratively only, of course. *
Broadcom bluetooth on ASUS Z97-Pro WiFi ac
I'm running jessie on an ASUS z97-pro wifi ac motherboard and can't get bluetooth working. This doesn't surprise me since the log message shows: kernel: [76077.598420] Bluetooth: hci0: BCM: patch brcm/2070BCM2A0-0b05-17cf.hcd not found I've googled this but haven't found anything that I can understand and I've no idea how to proceed. Would greatly appreciate any suggestions. (Please copy me as I don't subscribe to this list.) Thanks for your time. --Len On the chance that it is relevant, I'm including the output of lspci here: 00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller (rev 06) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06) 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06) 00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06) 00:14.0 USB controller: Intel Corporation 9 Series Chipset Family USB xHCI Controller 00:16.0 Communication controller: Intel Corporation 9 Series Chipset Family ME Interface #1 00:19.0 Ethernet controller: Intel Corporation Ethernet Connection (2) I218-V 00:1a.0 USB controller: Intel Corporation 9 Series Chipset Family USB EHCI Controller #2 00:1b.0 Audio device: Intel Corporation 9 Series Chipset Family HD Audio Controller 00:1c.0 PCI bridge: Intel Corporation 9 Series Chipset Family PCI Express Root Port 1 (rev d0) 00:1c.3 PCI bridge: Intel Corporation 9 Series Chipset Family PCI Express Root Port 4 (rev d0) 00:1c.6 PCI bridge: Intel Corporation 9 Series Chipset Family PCI Express Root Port 7 (rev d0) 00:1d.0 USB controller: Intel Corporation 9 Series Chipset Family USB EHCI Controller #1 00:1f.0 ISA bridge: Intel Corporation 9 Series Chipset Family Z97 LPC Controller 00:1f.2 SATA controller: Intel Corporation 9 Series Chipset Family SATA Controller [AHCI Mode] 00:1f.3 SMBus: Intel Corporation 9 Series Chipset Family SMBus Controller 03:00.0 PCI bridge: ASMedia Technology Inc. Device 1184 04:01.0 PCI bridge: ASMedia Technology Inc. Device 1184 04:03.0 PCI bridge: ASMedia Technology Inc. Device 1184 04:05.0 PCI bridge: ASMedia Technology Inc. Device 1184 04:07.0 PCI bridge: ASMedia Technology Inc. Device 1184 05:00.0 Network controller: Broadcom Corporation BCM4352 802.11ac Wireless Network Adapter (rev 03) 08:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 02) 09:00.0 USB controller: ASMedia Technology Inc. ASM1042A USB 3.0 Host Controller
Re: Broadcom b43 drivers
On 06/05/2015 03:25 AM, Darac Marjal wrote: On Thu, Jun 04, 2015 at 05:41:27PM -0500, Jose Martinez wrote: OK, I probably have my system all messed up. Here's the sequence of events: Discovered errors with the nouveau driver (I'm using NVIDIA GeForce 7130 chipset) and did some research, nvidia-detect recommended the legacy 304xx driver, so I followed all the instructions on the wiki for installing said driver. This broke the system. X would not start, I have only command line. Not being really up to speed on everything needed to fix the system, and having tried several thing to no avail, I boot to rescue mode, using the installer environment so that previous root is not mounted. I deleted everything, except /root and /home, wherein I have data I do not want to lose, in order to start with a basically clean slate. I download and burn the jessie net-install CD and boot to that and install jessie. My broadcom wireless (using the BC4321 AG chipset) will not come up. This is not unexpected, there is no firmware installed as of yet for that NIC. I follow all of the instructions on wiki for obtaining the firmware and installing it to bring the card up (which worked in a previous incarnation of the system). The card still will not come up. Check the syslog and/or dmesg. The kernel SHOULD log a message to the effect that it has found the firmware and loaded it. I pulled out the old driver I was using which I got from broadcom, and had installed it in the past to get everything working. I attempted to install it using the instructions provided with the driver (which had worked in the past). The card still will not come up. I do an lspci | grep Network command and the controller does show up (03:00.0). As an interim measure, are you able to install using a different (e.g. wired) adapter. You may find getting the firmware to work on an installed system easier than on the installer. What the devil am I doing wrong, and how do I get my wifi adapter back?? Note that I had used the firmware-b43-installer package in a past jessie incarnation and it worked great. -- JM Sven, Darac, Thank you for your input. The driver was not compiled for the current Jessie kernel. It had been compiled for Wheezy back in August. What threw me off was the fact that if I had a Wheezy system and updated to Jessie, the driver was happy. This time, however, was a clean install of Jessie with no upgrade from Wheezy. I don't understand all the ins and outs of the situation, but I suspect that there is a little difference in the compile between the two distributions, but that if Wheezy is already installed, the kernel is maintained through the upgrade. But, with a fresh install of Jessie with no previous kernel, the kernel installed isn't quite the same and so causes the error. I'm basically guessing at that, but I suspect I'm not far off the mark. In any event, I did have a wired option, I have a second adapter on this laptop that is wired, so I was able to connect up to the router using that nic, which incidentally was how I was sending messages on this list. Ultimately, I did get it working, and am now using it. I had forgotten the necessary step of rebooting after installing the firmward package in contrib, so the firmware didn't get uploaded. As a result, I thought it wasn't working (and started tramping around in things better left alone) when in fact all I needed to do is reboot. This of course made for a whole lot more work to get back to the virgin state and get the contrib package in again. I really need to be slapped, I think. :-[ -- JM -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/55721b86.8070...@gmail.com
Re: Broadcom b43 Drivers
On 06/05/2015 02:16 AM, to...@tuxteam.de wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, Jun 04, 2015 at 05:54:40PM -0500, Jose Martinez wrote: I forgot to mention in my last post, when I attempted to install the old driver from broadcom which I have used before, I get the message: insmod: ERROR: could not insert module wl.ko: Invalid module format This has not happened in the past, it just installed and worked fine.] This means that the module was compiled for a different version (or for a significantly different configuration) of the kernel you're trying to feed the module to. You can look int that with modinfo (lives in /sbin): tomas@rasputin:~$ /sbin/modinfo /lib/modules/3.2.0-3-amd64/kernel/drivers/net/ethernet/atheros/atlx/atl1.ko filename: /lib/modules/3.2.0-3-amd64/kernel/drivers/net/ethernet/atheros/atlx/atl1.ko version:2.1.3 license:GPL author: Xiong Huang , Chris Snook , Jay Cliburn description:Atheros L1 Gigabit Ethernet Driver srcversion: 21557C61B6BC6DA20309204 alias: pci:v1969d1048sv*sd*bc*sc*i* depends:mii intree: Y vermagic: 3.2.0-3-amd64 SMP mod_unload modversions parm: int_mod_timer:Interrupt moderator timer (array of int) parm: debug:Message level (0=none,...,16=all) (int) HTH - -- tomás -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlVxTL0ACgkQBcgs9XrR2kY2LgCfXE3YhQ+K5h7SkT3TzuWZP1TE otQAnRNKAyY8DuXes+L0zaL656RsDvyV =mXfq -END PGP SIGNATURE- I understand. It is true that this driver was compiled back in August under Wheezy. What I do find interesting is that I know that this driver was working on a system upgraded from Wheezy to Jessie. However, with a clean install of Jessie, it does not. Nevertheless, the problem was solved when I got the original Jessie kernel, without my tramping around messing it up, and installed the firmware-b43-install package. I didn't think that that had worked because I forgot the necessary step of rebooting after the installation. The driver automatically uploads the firmware to the chip at boot up, and since I didn't reboot, the firmware did not get uploaded and it did not work. Once I rebooted, everything came out fine. In fact, this post is being sent through that BC4321 chip to my wireless network. (I was wired yesterday.) -- JM -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/55721838.8080...@gmail.com
Re: Broadcom b43 drivers
On Thu, 2015-06-04 at 17:41 -0500, Jose Martinez wrote: > My broadcom wireless (using the BC4321 AG chipset) will not come > up. This is not unexpected, there is no firmware installed as of > yet for that NIC. > > I follow all of the instructions on wiki for obtaining the firmware > and installing it to bring the card up (which worked in a previous > incarnation of the system). The card still will not come up. Is it the same as the BMC4321? If so, have you followed this? https://wiki.debian.org/wl -- Cheers, Sven Arvidsson http://www.whiz.se PGP Key ID 6FAB5CD5 signature.asc Description: This is a digitally signed message part
Re: Broadcom b43 drivers
On Thu, Jun 04, 2015 at 05:41:27PM -0500, Jose Martinez wrote: >OK, I probably have my system all messed up. Here's the sequence of >events: > > Discovered errors with the nouveau driver (I'm using NVIDIA GeForce 7130 > chipset) and did some research, nvidia-detect recommended the legacy > 304xx driver, so I followed all the instructions on the wiki for > installing said driver. This broke the system. X would not start, I > have only command line. > > Not being really up to speed on everything needed to fix the system, and > having tried several thing to no avail, I boot to rescue mode, using the > installer environment so that previous root is not mounted. I deleted > everything, except /root and /home, wherein I have data I do not want to > lose, in order to start with a basically clean slate. > > I download and burn the jessie net-install CD and boot to that and > install jessie. > > My broadcom wireless (using the BC4321 AG chipset) will not come up. > This is not unexpected, there is no firmware installed as of yet for > that NIC. > > I follow all of the instructions on wiki for obtaining the firmware and > installing it to bring the card up (which worked in a previous > incarnation of the system). The card still will not come up. Check the syslog and/or dmesg. The kernel SHOULD log a message to the effect that it has found the firmware and loaded it. > > I pulled out the old driver I was using which I got from broadcom, and > had installed it in the past to get everything working. I attempted to > install it using the instructions provided with the driver (which had > worked in the past). The card still will not come up. > > I do an lspci | grep Network command and the controller does show up > (03:00.0). As an interim measure, are you able to install using a different (e.g. wired) adapter. You may find getting the firmware to work on an installed system easier than on the installer. > >What the devil am I doing wrong, and how do I get my wifi adapter back?? >Note that I had used the firmware-b43-installer package in a past jessie >incarnation and it worked great. > > -- > JM -- For more information, please reread. signature.asc Description: Digital signature
Re: Broadcom b43 Drivers
> On 4 Jun 2015, at 23:54, Jose Martinez wrote: > > I forgot to mention in my last post, when I attempted to install the old > driver from broadcom which I have used before, I get the message: > insmod: ERROR: could not insert module wl.ko: Invalid module format > This has not happened in the past, it just installed and worked fine.] If you've downloaded the module from Broadcom are you sure it's compiled for the kernel you have? Is the driver not available in linux-firmware-nonfree? -- Justin C -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1bafeffb-9195-414b-b85b-71528301d...@masonsmusic.co.uk
Re: Broadcom b43 Drivers
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, Jun 04, 2015 at 05:54:40PM -0500, Jose Martinez wrote: > I forgot to mention in my last post, when I attempted to install the > old driver from broadcom which I have used before, I get the > message: > >insmod: ERROR: could not insert module wl.ko: Invalid module format > > This has not happened in the past, it just installed and worked fine.] This means that the module was compiled for a different version (or for a significantly different configuration) of the kernel you're trying to feed the module to. You can look int that with modinfo (lives in /sbin): tomas@rasputin:~$ /sbin/modinfo /lib/modules/3.2.0-3-amd64/kernel/drivers/net/ethernet/atheros/atlx/atl1.ko filename: /lib/modules/3.2.0-3-amd64/kernel/drivers/net/ethernet/atheros/atlx/atl1.ko version:2.1.3 license:GPL author: Xiong Huang , Chris Snook , Jay Cliburn description:Atheros L1 Gigabit Ethernet Driver srcversion: 21557C61B6BC6DA20309204 alias: pci:v1969d1048sv*sd*bc*sc*i* depends:mii intree: Y vermagic: 3.2.0-3-amd64 SMP mod_unload modversions parm: int_mod_timer:Interrupt moderator timer (array of int) parm: debug:Message level (0=none,...,16=all) (int) HTH - -- tomás -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlVxTL0ACgkQBcgs9XrR2kY2LgCfXE3YhQ+K5h7SkT3TzuWZP1TE otQAnRNKAyY8DuXes+L0zaL656RsDvyV =mXfq -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150605071613.gb26...@tuxteam.de
Broadcom b43 driver
Problem fixed... Rebooting is a wondrous thing!! I ended up re-installing the original jessie kernel to get rid of my bull in the china shop hacking, then re-installed the firmware-b43-installer. Then with things back the way they should be, I rebootedLife is good, wifi is on the air. I really shouldn't be messing around with things when I don't know what I'm doing:-! -- JM -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5570ebbf.9080...@gmail.com
Broadcom b43 Drivers
I forgot to mention in my last post, when I attempted to install the old driver from broadcom which I have used before, I get the message: insmod: ERROR: could not insert module wl.ko: Invalid module format This has not happened in the past, it just installed and worked fine.] -- JM
Broadcom b43 drivers
OK, I probably have my system all messed up. Here's the sequence of events: Discovered errors with the nouveau driver (I'm using NVIDIA GeForce 7130 chipset) and did some research, nvidia-detect recommended the legacy 304xx driver, so I followed all the instructions on the wiki for installing said driver. This broke the system. X would not start, I have only command line. Not being really up to speed on everything needed to fix the system, and having tried several thing to no avail, I boot to rescue mode, using the installer environment so that previous root is not mounted. I deleted everything, except /root and /home, wherein I have data I do not want to lose, in order to start with a basically clean slate. I download and burn the jessie net-install CD and boot to that and install jessie. My broadcom wireless (using the BC4321 AG chipset) will not come up. This is not unexpected, there is no firmware installed as of yet for that NIC. I follow all of the instructions on wiki for obtaining the firmware and installing it to bring the card up (which worked in a previous incarnation of the system). The card still will not come up. I pulled out the old driver I was using which I got from broadcom, and had installed it in the past to get everything working. I attempted to install it using the instructions provided with the driver (which had worked in the past). The card still will not come up. I do an lspci | grep Network command and the controller does show up (03:00.0). What the devil am I doing wrong, and how do I get my wifi adapter back?? Note that I had used the firmware-b43-installer package in a past jessie incarnation and it worked great. -- JM
Re: Broadcom TG3 network drops, cannot recover without reboot
On Wed, May 27, 2015, at 13:06, Toan Pham wrote: > > Alternatively, try to get yourself an Intel NIC that works with the igb > > driver (don't get an Intel NIC that needs the e1000e driver) to replace > > the hardlock-prone bcm5720 + tg3 combination. > > I ended up with an intel NIC instead, but with the e1000e driver. > What's wrong with the e1000e driver by the way, please update. It is not that the NICs that need e1000e are "bad news". It is that they're outdated and less capable than the more recent Intel designs that use the igb driver (or igbx, for 10GbE). Also there is certainly something very wrong with any motherboard of recent design that uses an outdated NIC. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique de Moraes Holschuh -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1432810960.10471.280287409.5b486...@webmail.messagingengine.com
Re: Broadcom TG3 network drops, cannot recover without reboot
> On 27 May 2015, at 17:06, Toan Pham wrote: > > Justin, > > > I've observed a similar symptom on the bcm5762 chip, not the 5720, and > not sure if the bugs they are related. I've filed a bug report > (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1447664), and > actively working with Broadcom's engineering team to get this bug > resolved. They are running multiple test cases but could not get this > bug to surface in a short amount of time. > >> In the mean time I've made a bash-script to rmmod and modprobe as >> appropriate. I'll set a cron job to ping a couple of other servers on the >> LAN and execute the script and restart networking should the pings fail. > > This is a patch, not a fix. Have you tested on kernel 4.0? I've not tested with 4.0. This machine needs to be rock solid, it will be Debian stable all the way, 4.x will only get on this machine when stable is updated to that kernel. > Alternatively, try to get yourself an Intel NIC that works with the igb >> driver (don't get an Intel NIC that needs the e1000e driver) to replace >> the hardlock-prone bcm5720 + tg3 combination. > > I ended up with an intel NIC instead, but with the e1000e driver. > What's wrong with the e1000e driver by the way, please update. Thank > you You'll have to hope Henrique is still following this, I don't have an answer. Just thinking out-loud here: I've got an identical server with FreeNAS installed, that's never disappeared off the network. Also I've had a server for about 5 years at home with the same on-board NIC, (different mobo), that's never locked up either, but I was able to force it to lock up with "/etc/init.d/networking restart". It seems that, at home at least, I've been fortunate so far. WRT to the FreeNAS, I have no idea how that's driving the NIC, listing the modules there doesn't show anything I recognise, and I've minimal experience with *BSD. -- Justin C, by the sea. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/a1e820dd-50c4-4708-8816-f9506ad1c...@masonsmusic.co.uk
Re: Broadcom TG3 network drops, cannot recover without reboot
Justin, I've observed a similar symptom on the bcm5762 chip, not the 5720, and not sure if the bugs they are related. I've filed a bug report (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1447664), and actively working with Broadcom's engineering team to get this bug resolved. They are running multiple test cases but could not get this bug to surface in a short amount of time. > In the mean time I've made a bash-script to rmmod and modprobe as > appropriate. I'll set a cron job to ping a couple of other servers on the LAN > and execute the script and restart networking should the pings fail. This is a patch, not a fix. Have you tested on kernel 4.0? > Alternatively, try to get yourself an Intel NIC that works with the igb > driver (don't get an Intel NIC that needs the e1000e driver) to replace > the hardlock-prone bcm5720 + tg3 combination. I ended up with an intel NIC instead, but with the e1000e driver. What's wrong with the e1000e driver by the way, please update. Thank you -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/cagnmleofs1aackvgktfhmes+e1l4z3d3pzvo1et-txqzrne...@mail.gmail.com
Re: Broadcom TG3 network drops, cannot recover without reboot
[Sorry, Henrique, for replying directly to you]
> On 26 May 2015, at 15:39, Henrique de Moraes Holschuh wrote:
>
> On Tue, May 26, 2015, at 09:24, Justin Catterall wrote:
>> At irregular times, and apparently for no reason at all, networking
>> drops and cannot be restarted without reboot on a fresh install of
>> Jessie. The NIC is a Broadcom NetXtreme BCM5720.
>>
>> ifconfig thinks networking is still up because I can:
>> ifconfig eth0 down
>>
>> I find this when I try 'ifconfig eth0 up':
>> tg3_abort_hw timed out TX_MODE_ENABLE will not clear MAC_TX_MODE=
>
> Hmm, it is either a kernel issue, or a hardware issue.
>
>> Any suggestions on where to look for a solution?
>
> Yes.
>
> First, disable all hardware offloading using ethtool. See if that
> helps.
Was able to disable all except:
rx-vlan-offload: on [fixed]
tx-vlan-offload: on [fixed]
Now, if I "/etc/init.d/networking restart" the system doesn't report any error,
but networking is still dead. However, I can rmmod tg3|ptp|libphy, then
"modprobe tg3" and "/etc/init.d/networking start" and all works (I have done
this a handful of times with no need to reboot to re-enable networking). So
that's some progress.
> Also, if this NIC is in the system mainboard, make sure you are using
> the latest firmware ("BIOS update") from your motherboard vendor: it is
> usual to have the motherboard NICs use a data block in the shared system
> FLASH for vital product data and firmware. The motherboard vendor will
> bundle up updates for the NIC firmware with the BIOS updates when both
> are in the same FLASH chip.
I've read the documentation for the latest firmware and there is no mention of
changes for the NIC, only a "power-on delay option" to allow longer/shorter
period of time to hit the key to access the BIOS. And a change to boot device
detection to better detect devices with invalid boot records. No other changes
mentioned in the firmware.
Here's a link to the page:
http://h20565.www2.hp.com/hpsc/swd/public/detail?sp4ts.oid=5390291&swItemId=MTX_a21cee44c55643598fb2f52bc2&swEnvOid=4144#tab4
I don't like tinkering with firmware if I can help it, in this case they don't
say there are changes to the NIC so do you think I should still upgrade? The
description says no bugs fixed, only enhancements.
> Make sure you have the latest linux firmware file for the tg3 driver as
> well. If the initramfs image has the tg3.ko module inside, it must also
> have the firmware file. A workaround for any initramfs-related tg3
> firmware loading issues is to "rmmod tg3 ; modprobe tg3" after the
> system booted (and before the NIC hardlocks).
See above, even after rmmod'ing I can still force network restart to fail
without error, though it is recoverable if noticed.
> If all of the above failed, get yourself familiar with building a custom
> Debian-compatible kernel using pristine upstream kernels from
> www.kernel.org. Wait until 3.18.15 and 4.0.5 are released in
> www.kernel.org, and build custom kernels based on them. Alternatively,
> wait until a debian-packaged version of kernel 4.0.5 is available. DO
> NOT use 4.0 kernels before 4.0.5 on pain of possible data loss.
Data loss? On a "stable" kernel? WTF are they doing these days? I notice that
stable/dev are no longer even/odd major numbers - took me a bit of Googling to
get caught up!
> If either the 3.18.15 or 4.0.5 kernel fixes the issue with your bcm5720,
> please tell us so that we can try to isolate the fix and backport it to
> the Debian kernel.
In the mean time I've made a bash-script to rmmod and modprobe as appropriate.
I'll set a cron job to ping a couple of other servers on the LAN and execute
the script and restart networking should the pings fail.
> If that fails, you will have to engage the kernel community itself for a
> fix. Please file a bug on bugzilla.kernel.org, and good luck. There are
> several hardware hang reports open against BCM57xx + tg3.
Damn crap hardware. I remember having issues with tg3 at least six or seven
years ago. I can believe it's still being incorporated into motherboards when
there are obviously problems with the chipset. Depending on speed of progress
on the kernel front I may just stick a PCI NIC in there - I think I still have
some 3c509's around somewhere...
> Alternatively, try to get yourself an Intel NIC that works with the igb
> driver (don't get an Intel NIC that needs the e1000e driver) to replace
> the hardlock-prone bcm5720 + tg3 combination.
Thanks for the pointers. I at least have a situation now where I don't need a
reboot to get networking functioning after it fails. It's far from perfect, but
it's much, much better.
--
Justin C, by the sea.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
https://lists.debian.org/3bcb9e79-8988-475e-b801-e5fccd423...@masonsmusic.co.uk
Re: Broadcom TG3 network drops, cannot recover without reboot
On Tue, May 26, 2015, at 09:24, Justin Catterall wrote:
> At irregular times, and apparently for no reason at all, networking
> drops and cannot be restarted without reboot on a fresh install of
> Jessie. The NIC is a Broadcom NetXtreme BCM5720.
>
> ifconfig thinks networking is still up because I can:
> ifconfig eth0 down
>
> I find this when I try 'ifconfig eth0 up':
> tg3_abort_hw timed out TX_MODE_ENABLE will not clear MAC_TX_MODE=
Hmm, it is either a kernel issue, or a hardware issue.
> Any suggestions on where to look for a solution?
Yes.
First, disable all hardware offloading using ethtool. See if that
helps.
Also, if this NIC is in the system mainboard, make sure you are using
the latest firmware ("BIOS update") from your motherboard vendor: it is
usual to have the motherboard NICs use a data block in the shared system
FLASH for vital product data and firmware. The motherboard vendor will
bundle up updates for the NIC firmware with the BIOS updates when both
are in the same FLASH chip.
Make sure you have the latest linux firmware file for the tg3 driver as
well. If the initramfs image has the tg3.ko module inside, it must also
have the firmware file. A workaround for any initramfs-related tg3
firmware loading issues is to "rmmod tg3 ; modprobe tg3" after the
system booted (and before the NIC hardlocks).
If all of the above failed, get yourself familiar with building a custom
Debian-compatible kernel using pristine upstream kernels from
www.kernel.org. Wait until 3.18.15 and 4.0.5 are released in
www.kernel.org, and build custom kernels based on them. Alternatively,
wait until a debian-packaged version of kernel 4.0.5 is available. DO
NOT use 4.0 kernels before 4.0.5 on pain of possible data loss.
If either the 3.18.15 or 4.0.5 kernel fixes the issue with your bcm5720,
please tell us so that we can try to isolate the fix and backport it to
the Debian kernel.
If that fails, you will have to engage the kernel community itself for a
fix. Please file a bug on bugzilla.kernel.org, and good luck. There are
several hardware hang reports open against BCM57xx + tg3.
Alternatively, try to get yourself an Intel NIC that works with the igb
driver (don't get an Intel NIC that needs the e1000e driver) to replace
the hardlock-prone bcm5720 + tg3 combination.
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique de Moraes Holschuh
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
https://lists.debian.org/1432651192.1585308.278340249.2dc14...@webmail.messagingengine.com
Broadcom TG3 network drops, cannot recover without reboot
At irregular times, and apparently for no reason at all, networking drops and cannot be restarted without reboot on a fresh install of Jessie. The NIC is a Broadcom NetXtreme BCM5720. ifconfig thinks networking is still up because I can: ifconfig eth0 down I find this when I try 'ifconfig eth0 up': tg3_abort_hw timed out TX_MODE_ENABLE will not clear MAC_TX_MODE= If I: rmmod tg3; insmod tg3 the problem does not resolve. It seems the card needs a hard reset. Searching the web there are various issues with the TG3, and most are resolved by installing firmware-linux-nonfree. I have this module installed but I can re-create the problem by running /etc/init.d/networking restart. The networking stops working completely, I can't ping the machine nor can I ping from the machine. Any suggestions on where to look for a solution? -- Justin C, by the sea. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/ba8a1c4c-a677-4c53-8b91-2b675991e...@masonsmusic.co.uk
Re: custom kernel - disabling devices - broadcom qlogic NetXtremeII
OK, found make localmodconfig. Looks like a much better starting point. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAOsGNSSUjy-+qe+sZ5WnM+Ex6f2GzF=rgsapjo5jim+r3a4...@mail.gmail.com
Re: custom kernel - disabling devices - broadcom qlogic NetXtremeII
On 8/18/14, Darac Marjal wrote:
> On Mon, Aug 18, 2014 at 09:48:50PM +1000, Zenaan Harkness wrote:
>> I am using "make xconfig" (the kernel qt configurator).
>>
>> How is it that I cannot disable:
>> Network device support
>> -> Ethernet driver support
>> -> Broadcom devices
>> -> Broadcom QLogic NetXtremeII driver?
>>
>> I can only select it as a module, or permanently built into the kernel. It
>> says:
>> Selected by: CNIC [=m] && NETDEVICES [=y] && ETHERNET [=y] &&
>> NET_VENDOR_BROADCOM [=y] && PCI [=y]
>
> As I understand it, the module you want to disable is being selected
> (for build) because of the boolean logic shown here. If you have CNIC
> *and* NETDEVICES *and* ETHERNET *and* ... (and so on), then you must
> also have the Broadcom QLogic NetXtreme II driver.
>
> Now, a quick check on the first of those (I searched the internet for
> 'linux kernel CNIC', no quotes and took the first link) shows me [1]
> that the CNIC driver "supports offload features of Broadcom NetXtreme II
> gigabit Ethernet cards".
>
> So, at the moment, you're trying to build the offloading driver for that
> card as a module ("CNIC=m") but not the main driver for the card. I
> doubt that's going to work.
>
> I would suggest saying no to CNIC and you should then be able to disable
> the other driver.
>
> [1] http://cateee.net/lkddb/web-lkddb/CNIC.html
Thank you.
"QLogic CNIC support" is the option immediately below that NetXtremeII
option, and it too can only be set to m or yes. It says:
SCSI_BNX2_ISCSI [=m] && SCSI_LOWLEVEL [=y] && SCSI [=m] && NET [=y] &&
PCI [=y] || SCSI_BNX2X_FCOE [=m] && SCSI_LOWLEVEL [=y] && SCSI [=m] &&
PCI [=y]
When I set it to module, NetXtremeII can be set to m; when I set it to
yes, NetXtremeII cannot be disabled. I would like both to be disabled
- I am able to disable the other "Broadcom devices" drivers, just not
these two.
And there is no general disable switch for "Broadcom devices" section
(at the moment at least), whereas, for example, there is for the
"Atheros devices" section.
I enabled menu Option -> Show Name, and went through all the items I
could find in:
Device drivers -> SCSI device support
and could not find SCSI_BNX2_ISCSI.
Finally I found the Edit -> Find menu, and these two devices options are under
SCSI device support -> SCSI low-level drivers
-> Qlogic...
where they can be disabled.
Could that be considered a bug of sorts? That seems rather awkward to
search around, to disable something you're looking at, to then have to
come back to where you were - surely it should just disable from where
I am in the first instance?
There seem to be at least a number of such instances around - the
kernel config tool is not intuitive, or doesn't seem to work very well
from this dum user's perspective. It's going to take a really long
time to disable things I don't need, at least with this user
interface.
Thanks again,
Zenaan
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
https://lists.debian.org/caosgnsqzexcnk0cfuw9_4nlh1wtwzsnjj5h+fh9xox6gva4...@mail.gmail.com
Re: custom kernel - disabling devices - broadcom qlogic NetXtremeII
On Mon, Aug 18, 2014 at 09:48:50PM +1000, Zenaan Harkness wrote:
> I am using "make xconfig" (the kernel qt configurator).
>
> How is it that I cannot disable:
> Network device support
> -> Ethernet driver support
> -> Broadcom devices
> -> Broadcom QLogic NetXtremeII driver?
>
> I can only select it as a module, or permanently built into the kernel. It
> says:
> Selected by: CNIC [=m] && NETDEVICES [=y] && ETHERNET [=y] &&
> NET_VENDOR_BROADCOM [=y] && PCI [=y]
As I understand it, the module you want to disable is being selected
(for build) because of the boolean logic shown here. If you have CNIC
*and* NETDEVICES *and* ETHERNET *and* ... (and so on), then you must
also have the Broadcom QLogic NetXtreme II driver.
Now, a quick check on the first of those (I searched the internet for
'linux kernel CNIC', no quotes and took the first link) shows me [1]
that the CNIC driver "supports offload features of Broadcom NetXtreme II
gigabit Ethernet cards".
So, at the moment, you're trying to build the offloading driver for that
card as a module ("CNIC=m") but not the main driver for the card. I
doubt that's going to work.
I would suggest saying no to CNIC and you should then be able to disable
the other driver.
[1] http://cateee.net/lkddb/web-lkddb/CNIC.html
>
> I would like to disable it.
>
> Seems strange.
>
> TIA,
> Zenaan
>
>
> --
> To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Archive:
> https://lists.debian.org/CAOsGNSRr2yWC4giPvUbukV9uCsgYT8-PsSMxw2A=zvs4etg...@mail.gmail.com
>
signature.asc
Description: Digital signature
custom kernel - disabling devices - broadcom qlogic NetXtremeII
I am using "make xconfig" (the kernel qt configurator). How is it that I cannot disable: Network device support -> Ethernet driver support -> Broadcom devices -> Broadcom QLogic NetXtremeII driver? I can only select it as a module, or permanently built into the kernel. It says: Selected by: CNIC [=m] && NETDEVICES [=y] && ETHERNET [=y] && NET_VENDOR_BROADCOM [=y] && PCI [=y] I would like to disable it. Seems strange. TIA, Zenaan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAOsGNSRr2yWC4giPvUbukV9uCsgYT8-PsSMxw2A=zvs4etg...@mail.gmail.com
Re: Broadcom 4312 apt-get package for Debian 7.0?
On Sat 13 Jul 2013 at 13:44:43 -0700, John Conover wrote: > > Where is the firmware-b43-installer package? There is a packages section on the Debian home page. I trust you need no help to find the website. :) -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/13072013222945.0fc595bcc...@desktop.copernicus.demon.co.uk
Re: Broadcom 4312 apt-get package for Debian 7.0?
On Sat, Jul 13, 2013 at 01:44:43PM -0700, John Conover wrote: > > Where is the firmware-b43-installer package? > > Thanks, > > John > > -- > > John Conover, cono...@rahul.net, http://www.johncon.com/ In contrib, you need to add it to your sources.lst. http://packages.debian.org/wheezy/firmware-b43-installer -- staticsafe O< ascii ribbon campaign - stop html mail - www.asciiribbon.org Please don't top post. Please don't CC! I'm subscribed to whatever list I just posted on. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130713211909.gb17...@uriel.asininetech.com
Broadcom 4312 apt-get package for Debian 7.0?
Where is the firmware-b43-installer package? Thanks, John -- John Conover, cono...@rahul.net, http://www.johncon.com/ -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130713204443.30793.qm...@rahul.net
Wheezy issue with broadcom 5720 nic on new dell PowerEdge
Hello list, I know the subject has been already discussed on the list, but without any real solution... It seems that there is a real problem with the 12th Dell generation poweredge and Wheezy about the Broadcom NIC. In my case I'm using Dell R420 server and an up-to-date Wheezy. During my test in our development network everything was fine. Yesterday I decide to rack the server in your production network, and I was unable to use the eth0: Jul 11 15:38:13 xxx kernel: [ 15.962677] [ cut here ] Jul 11 15:38:13 xxx kernel: [ 15.962685] WARNING: at /build/linux-s5x2oE/linux-3.2.46/net/sched/sch_generic.c:256 dev_watchdog+0xf2/0x151() Jul 11 15:38:13 xxx kernel: [ 15.962687] Hardware name: PowerEdge R420 Jul 11 15:38:13 xxx kernel: [ 15.962689] NETDEV WATCHDOG: eth0 (tg3): transmit queue 0 timed out Jul 11 15:38:13 xxx kernel: [ 15.962691] Modules linked in: ipmi_si ipmi_devintf ipmi_msghandler dell_rbu autofs4 nfsd nfs nfs_acl auth_rpcgss fscache lockd sunrpc loop joydev usbhid hid shpchp iTCO_wdt dcdbas sb_edac snd_pcm edac_core snd_page_alloc snd_timer snd soundcore iTCO_vendor_support evdev pcspkr coretemp crc32c_intel ghash_clmulni_intel aesni_intel aes_x86_64 aes_generic cryptd acpi_power_meter wmi button processor thermal_sys ext4 crc16 jbd2 mbcache dm_mod sg sr_mod cdrom sd_mod ses crc_t10dif enclosure ahci libahci ehci_hcd tg3 libphy libata usbcore usb_common megaraid_sas scsi_mod [last unloaded: ipmi_si] Jul 11 15:38:13 xxx kernel: [ 15.962733] Pid: 3576, comm: dsm_sa_datamgrd Tainted: GW3.2.0-4-amd64 #1 Debian 3.2.46-1 Jul 11 15:38:13 xxx kernel: [ 15.962736] Call Trace: Jul 11 15:38:13 xxx kernel: [ 15.962737] [] ? warn_slowpath_common+0x78/0x8c Jul 11 15:38:13 xxx kernel: [ 15.962746] [] ? warn_slowpath_fmt+0x45/0x4a Jul 11 15:38:13 xxx kernel: [ 15.962749] [] ? netif_tx_lock+0x40/0x75 Jul 11 15:38:13 xxx kernel: [ 15.962754] [] ? dev_watchdog+0xf2/0x151 Jul 11 15:38:13 xxx kernel: [ 15.962757] [] ? run_timer_softirq+0x19a/0x261 Jul 11 15:38:13 xxx kernel: [ 15.962760] [] ? netif_tx_unlock+0x49/0x49 Jul 11 15:38:13 xxx kernel: [ 15.962765] [] ? timekeeping_get_ns+0xd/0x2a Jul 11 15:38:13 xxx kernel: [ 15.962769] [] ? __do_softirq+0xb9/0x177 Jul 11 15:38:13 xxx kernel: [ 15.962773] [] ? call_softirq+0x1c/0x30 Jul 11 15:38:13 xxx kernel: [ 15.962777] [] ? do_softirq+0x3c/0x7b Jul 11 15:38:13 xxx kernel: [ 15.962780] [] ? irq_exit+0x3c/0x99 Jul 11 15:38:13 xxx kernel: [ 15.962784] [] ? smp_apic_timer_interrupt+0x74/0x82 Jul 11 15:38:13 xxx kernel: [ 15.962787] [] ? apic_timer_interrupt+0x6e/0x80 Jul 11 15:38:13 xxx kernel: [ 15.962788] [] ? __schedule+0x5f9/0x610 Jul 11 15:38:13 xxx kernel: [ 15.962795] [] ? delay_tsc+0x33/0x5e Jul 11 15:38:13 xxx kernel: [ 15.962798] [] ? pci_vpd_pci22_wait+0xb9/0xdd Jul 11 15:38:13 xxx kernel: [ 15.962802] [] ? should_resched+0x5/0x23 Jul 11 15:38:13 xxx kernel: [ 15.962804] [] ? pci_vpd_pci22_read+0xa9/0x121 Jul 11 15:38:13 xxx kernel: [ 15.962806] [] ? should_resched+0x5/0x23 Jul 11 15:38:13 xxx kernel: [ 15.962811] [] ? read+0x102/0x182 Jul 11 15:38:13 xxx kernel: [ 15.962815] [] ? vfs_read+0x9f/0xe6 Jul 11 15:38:13 xxx kernel: [ 15.962817] [] ? sys_read+0x45/0x6b Jul 11 15:38:13 xxx kernel: [ 15.962820] [] ? system_call_fastpath+0x16/0x1b Jul 11 15:38:13 xxx kernel: [ 15.962823] ---[ end trace fde705cbad5d6bde ]--- Jul 11 15:38:13 xxx kernel: [ 15.962825] tg3 :02:00.0: eth0: transmit timed out, resetting Jul 11 15:38:14 xxx kernel: [ 17.219582] tg3 :02:00.0: eth0: 0x: 0x165f14e4, 0x00100406, 0x0200, 0x00800010 Jul 11 15:38:14 xxx kernel: [ 17.219728] tg3 :02:00.0: eth0: 0x0010: 0xd90a000c, 0x, 0xd90b000c, 0x Jul 11 15:38:14 xxx kernel: [ 17.219873] tg3 :02:00.0: eth0: 0x0020: 0xd90c000c, 0x, 0x, 0x04f81028 Jul 11 15:38:14 xxx kernel: [ 17.220017] tg3 :02:00.0: eth0: ... Whereas the eth1 was working. Then, I've decided to came back to your development network, (20km ...!) with the server, and I was unable to reproduce. Everything is fine. During kernel boot I always found this (in working and not working cases): Jul 11 11:33:05 xxx kernel: [0.629277] pci :02:00.1: address space collision: [mem 0xdd00-0xdd03 pref] conflicts with :02:00.0 [mem 0xdd00-0xdd03 pref] I don't know if this can be related, and how to solve it. Is anyone have suggestions ? Many thanks -- Erwan Loaec -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51e021a8.80...@cgin.fr
Re: Wheezy issue with broadcom 5720 nic on new dell PowerEdge R720
Am 03.05.2013 um 09:01 schrieb Stan Hoeppner: On 5/2/2013 8:24 AM, Lukáš Zíta wrote: I can not think another way to handle this, so I will have to switch toa card from Intel. To those people who may wonder why/how others often end up with boxes full of brand new 'perfectly good' hardware that may never be used... ... expensive parts not used. In my case the two Dell Poweredge R520 have the built in BCM5716 (2 heads), and an Intel 82576 (2 heads). For more performance I ordered additional 2 Intel 82576. But two Intel 82576 do not work in one machine (AFAIK a known kernel module problem of kernel 2.6.32. So I use these expensive NICs in spare/testing machines;-) BTW: Is there an easy way to get the version of a kernel module directly from kernel source tree? I.e. without installing the kernel. Helmut Wollmersdorfer -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4a5be648-2b1f-42bd-81e1-91609f161...@fixpunkt.de
Re: Wheezy issue with broadcom 5720 nic on new dell PowerEdge R720
On 5/2/2013 8:24 AM, Lukáš Zíta wrote: > After some more tests, I have discovered, that those missing > patches are part of BQL backport to 3.2 kernel (therefore their absence > in upstream 3.2). In the end it turned out, that the NIC is buggy even > with BQL disabled. Strange thing is, that the bug only appears on newer > types of Dell servers, namely R820 and R720. Same card (I have even > switched them between machines) although do work on R320 and R620 with > same version of the kernel. > > I can not think another way to handle this, so I will have to > switch toa card from Intel. To those people who may wonder why/how others often end up with boxes full of brand new 'perfectly good' hardware that may never be used... -- Stan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/518360e2.3040...@hardwarefreak.com
Re: Wheezy issue with broadcom 5720 nic on new dell PowerEdge R720
After some more tests, I have discovered, that those missing patches are part of BQL backport to 3.2 kernel (therefore their absence in upstream 3.2). In the end it turned out, that the NIC is buggy even with BQL disabled. Strange thing is, that the bug only appears on newer types of Dell servers, namely R820 and R720. Same card (I have even switched them between machines) although do work on R320 and R620 with same version of the kernel. I can not think another way to handle this, so I will have to switch toa card from Intel. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51826920.7060...@archa.cz
Re: Wheezy issue with broadcom 5720 nic on new dell PowerEdge R720
Dne 26.4.2013 19:13, Lukas Zita napsal(a): Then I have noticed small patch in 3.2.43: "tg3: fix length overflow in VPD firmware parsing", so I have compiled vanilla kernel and got the NIC working correctly. I will yet try to apply this patch on stock Wheezy kernel, but I believe that the problem lies there. So I have finished more tests with compilation of Wheezy kernel and unfortunately applying mentioned fix didn't solve the problem. But after comparing Wheezy source of tg3.c with vanilla 3.2.44 and some searching, I have found that these patches: http://patchwork.ozlabs.org/patch/108859/ http://patchwork.ozlabs.org/patch/144848/ Are applied in Wheezy, but not in vanilla. Can't find why, but maybe because the support for queue limit was buggy? It is beyond my knowledge of current kernel development to do more debugging and try to find why these calls fail only on some NIC, but maybe it could be safe to remove those two patches from Wheezy? It's just a guess based on their absence in upstream. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/517bad63.5080...@archa.cz
Re: Wheezy issue with broadcom 5720 nic on new dell PowerEdge R720
I have encountered exactly the same problem. Got four new Dell servers (2xR820, 2xR620), all with Broadcom 5720. I have installed Wheezy on all of them, including Xen. But only on two of them, I have installed firmware-linux-nonfree and only on ONE of them (namely R820), the NIC behaves like Casper described. Which leads me to assumption, that it is not related to Debian firmware package, but I can't confirm that, because i don't know for sure if the problem has existed before the installation. To clarify: it gets more complicated, because if I run Lifecycle Manager, the NIC initializes to some state where it can be used in Wheezy, until next complete power disconnect. And before first installation I was of course in LCM. I have spent last few days with thorough testing and got to these conclusions: - downgrading/upgrading firmware through Dell firmware utility didn't help for me - under 2.6.32 kernel (tested with Centos), NIC works ok - under 3.x.x kernel NIC fails (tested with stock kernel in Wheezy, Ubuntu 12.04 and ELREPO kernel 3.8.8 in Centos) - drivers ver.3.124 directly from Broadcom compiled against Wheezy kernel, behave the same Then I have noticed small patch in 3.2.43: "tg3: fix length overflow in VPD firmware parsing", so I have compiled vanilla kernel and got the NIC working correctly. I will yet try to apply this patch on stock Wheezy kernel, but I believe that the problem lies there. Hard to tell why only one card from four tested should return bad value to break the driver, but who knows. -- View this message in context: http://debian.2.n7.nabble.com/Wheezy-issue-with-broadcom-5720-nic-on-new-dell-PowerEdge-R720-tp2892237p2922675.html Sent from the Debian User mailing list archive at Nabble.com. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1366996406918-2922675.p...@n7.nabble.com
Re: Debian Wheezy - Kernel 3.2.X - Broadcom 57766 driver support
On 13-04-2013 09:41, didier gaumet wrote: Le 12/04/2013 18:24, terr1-li...@linuxgeek.dk a écrit : Hey I'm running debian wheezy with custom 3.7.1 kernel to support my Broadcom 57766 netcard. However since this is a server (Mac Mini Server) I would rather use a longterm kernel like 3.2.43, also since grsecurity is supported as stable. Do anyone have a patch or something similar to enable boardcom 57766 on 3.2.X? I cannot reuse my 3.7.1 stuff since alot more have changed. It's beyond my skill level to re-engineer this to work :/ Is this hardware not supported by the tg3 mainline linux module? (provided you have also installed the firmware-linux-nonfree package) No, I just re-tested to sure, no-go.. (I have firmware-linux-nonfree installed). I even had to patch 3.7.1 to get it working.. only 1 line thou :) I read somewhere that its on Ben Hutchings (debian-kernel maintainer) TODO list for 3.2, no idea of status.. Just thought maybe I was lucky and some user had created a patch for tg3.h/tg3.c to back port the support.. But it isent easy since much code has changed.. :/ Would just prefer to have debian auto-updated kernel on a server, compared to manual patching to keeping up-to-date.. Also if you need the grsecurity patch, you have to use their testing release instead of stable if using the newer kernels. I'm not sure this is production material (its my own private server nothing enterprise of cause). -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51693e84.40...@linuxgeek.dk
Re: Debian Wheezy - Kernel 3.2.X - Broadcom 57766 driver support
Le 12/04/2013 18:24, terr1-li...@linuxgeek.dk a écrit : > Hey > > I'm running debian wheezy with custom 3.7.1 kernel to support my > Broadcom 57766 netcard. > > However since this is a server (Mac Mini Server) I would rather use a > longterm kernel like 3.2.43, > also since grsecurity is supported as stable. > > Do anyone have a patch or something similar to enable boardcom 57766 on > 3.2.X? > > I cannot reuse my 3.7.1 stuff since alot more have changed. It's beyond > my skill level to re-engineer this to work :/ Is this hardware not supported by the tg3 mainline linux module? (provided you have also installed the firmware-linux-nonfree package) -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/kkb26c$1as$1...@ger.gmane.org
Debian Wheezy - Kernel 3.2.X - Broadcom 57766 driver support
Hey I'm running debian wheezy with custom 3.7.1 kernel to support my Broadcom 57766 netcard. However since this is a server (Mac Mini Server) I would rather use a longterm kernel like 3.2.43, also since grsecurity is supported as stable. Do anyone have a patch or something similar to enable boardcom 57766 on 3.2.X? I cannot reuse my 3.7.1 stuff since alot more have changed. It's beyond my skill level to re-engineer this to work :/ -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5168353f.1010...@linuxgeek.dk
Re: Wheezy issue with broadcom 5720 nic on new dell PowerEdge R720
On 3/18/2013 2:44 PM, Casper Langemeijer wrote: > On 03/18/2013 02:23 PM, Casper Langemeijer wrote: >> >> It gets even more weird: I had the NIC daughter card replaced, and the >> problem still exists. I think I will use the machine in production as >> it is now. Since I'm not using 4 ethernet ports, for me the issue is >> not blocking. I hope someday someone encounters the same problem and >> finds a solution. >> > This story has a happy end. I fixed it by running the firmware > installer. The firmware installer is in the 'Lifecycle controller' BIOS. > It can download the firmware from a dell ftp server, and allows a > firmware 'upgrade' even if the newest firmware version is the same as > currently installed. > > Now that I can restore the situation, I could replay this again if > anyone is interested. I could install the firmware-linux-nonfree package > and see if the problem occurs again. I will have physical access to this > machine on Wednesday only. After that, it's co-located. There are two different, or should I say separate, firmware. One is permanent, either in EPROM or flash, and one is volatile. The permanent one is what you upgraded from FTP. I'd guess that what happened here is that the version of the volatile firmware loaded by the Xen kernel isn't compatible with this permanent firmware rev, for one reason or another, or the wrong volatile firmware was loaded due to device mis-identification, i.e. volatile firmware for one of the other Broadcomm NICs was loaded. Some of the output you posted seemed to suggest this may have been the case. I have seen such a problem before but it is pretty rare. -- Stan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5147ef9d.1030...@hardwarefreak.com
Re: Wheezy issue with broadcom 5720 nic on new dell PowerEdge R720
On 03/18/2013 02:23 PM, Casper Langemeijer wrote: It gets even more weird: I had the NIC daughter card replaced, and the problem still exists. I think I will use the machine in production as it is now. Since I'm not using 4 ethernet ports, for me the issue is not blocking. I hope someday someone encounters the same problem and finds a solution. This story has a happy end. I fixed it by running the firmware installer. The firmware installer is in the 'Lifecycle controller' BIOS. It can download the firmware from a dell ftp server, and allows a firmware 'upgrade' even if the newest firmware version is the same as currently installed. Now that I can restore the situation, I could replay this again if anyone is interested. I could install the firmware-linux-nonfree package and see if the problem occurs again. I will have physical access to this machine on Wednesday only. After that, it's co-located. Greetings, Casper -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51476eab.90...@langemeijer.eu
Re: Wheezy issue with broadcom 5720 nic on new dell PowerEdge R720
On 03/18/2013 12:57 PM, Stan Hoeppner wrote: On 3/18/2013 3:57 AM, Casper Langemeijer wrote: If I ifup both eth0 and eth1, ifconfig shows both interfaces. No difference between output for them. (except ip/mac of course) The counters get reset every few seconds for the broken eth0. Also: ethtool shows nothing out off the ordinary except that it cannot detect Speed and Duplex. Do you see link flapping in dmesg, something like this, continuously? kernel: e100 :00:0d.0: eth0: NIC Link is Down kernel: e100 :00:0d.0: eth0: NIC Link is Up 100 Mbps Full Duplex It's beginning to like you simply have a port that failed, and that loading the firmware blob was coincidental. Remember the old maxim: If ICs are going to fail in normal operation, they typically do so within 72 hours. Which is why custom shops for years advertised that they burn their servers in with real workloads for 72 hours (though few actually did). With the information I have so far, I'd guess the transceiver for port0 on the card failed. It's a $0.25 IC. This would tend to explain why you can't get link/duplex status. Every 5 seconds, the NIC is Down and Up again. It gets even more weird: I had the NIC daughter card replaced, and the problem still exists. I think I will use the machine in production as it is now. Since I'm not using 4 ethernet ports, for me the issue is not blocking. I hope someday someone encounters the same problem and finds a solution. I will receive a second server any day now. I will not be installing the firmware-linux-nonfree package on that one... Thank you for your time. If anyone else stumbles on this issue and wants to contact me: Please do so off-list via personal email. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51471565.9080...@langemeijer.eu
Re: Wheezy issue with broadcom 5720 nic on new dell PowerEdge R720
On 3/18/2013 3:57 AM, Casper Langemeijer wrote: > If I ifup both eth0 and eth1, ifconfig shows both interfaces. No > difference between output for them. (except ip/mac of course) The > counters get reset every few seconds for the broken eth0. Also: ethtool > shows nothing out off the ordinary except that it cannot detect Speed > and Duplex. Do you see link flapping in dmesg, something like this, continuously? ...kernel: e100 :00:0d.0: eth0: NIC Link is Down ...kernel: e100 :00:0d.0: eth0: NIC Link is Up 100 Mbps Full Duplex It's beginning to like you simply have a port that failed, and that loading the firmware blob was coincidental. Remember the old maxim: If ICs are going to fail in normal operation, they typically do so within 72 hours. Which is why custom shops for years advertised that they burn their servers in with real workloads for 72 hours (though few actually did). With the information I have so far, I'd guess the transceiver for port0 on the card failed. It's a $0.25 IC. This would tend to explain why you can't get link/duplex status. -- Stan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51470126.6040...@hardwarefreak.com
Re: Wheezy issue with broadcom 5720 nic on new dell PowerEdge R720
On 03/17/2013 05:12 PM, Stan Hoeppner wrote: Which has alway been my understanding of it until so far. But I like to repeat from my first email: "I tried the debian installer again, but even then it's not able to get a DHCP IP address using eth0. eth1 is working fine." This is after a cold boot. Evidently the NIC has some non-volatile state, it's not just RAM. It could well be that the firmware in RAM did something to the NIC that brought it into this broken state. The firmware blob could even have fried it, but I think that's unlikely. Bottom line is that installing the firmware blob for the network card is breaking it. Have you performed sufficient troubleshooting to make this claim? I ruled out a faulty cable or switch. What do you mean by your question? I run two racks of servers, I'm a full-time linux professional. I do stuff like linux interface bonding, have setup linux bridging, advanced firewalling. I know my stuff. If the firmware is the problem conventional wisdom says it will brick all 4 ports, not just one. You've never mentioned the other two ports eth2/3. Are they working? eth2 and eth3 are working fine, as is eth1. Also, dhclient not receiving a lease doesn't mean eth0 is dead or broken. What does ifconfig tell you? How about /etc/network/interfaces? If I ifup both eth0 and eth1, ifconfig shows both interfaces. No difference between output for them. (except ip/mac of course) The counters get reset every few seconds for the broken eth0. Also: ethtool shows nothing out off the ordinary except that it cannot detect Speed and Duplex. /etc/network/interfaces is configured as following: auto lo iface lo inet loopback auto eth0 iface eth0 inet static address 172.24.2.241 netmask 255.255.0.0 auto eth1 iface eth1 inet static address 172.24.2.242 netmask 255.255.0.0 gateway 172.24.1.1 Gateway is missing for eth0. That is intentional. I don't need it for local operation. Also, all modern servers retain power while the cord is jacked in. This is what enables wake-on-LAN, etc. As long as the daughterboard has standby power it will retain the firmware in its onboard RAM. Pull the power cord and wait 60 seconds, then plug it back in. I was pretty sure I did that, but just to be sure this morning I pulled the power cord. No change in the situation. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5146d6ea.7010...@langemeijer.eu
Re: Wheezy issue with broadcom 5720 nic on new dell PowerEdge R720
On 3/17/2013 10:34 AM, Casper Langemeijer wrote: > Which has alway been my understanding of it until so far. But I like to > repeat from my first email: "I tried the debian installer again, but > even then it's not able to get a DHCP IP address using eth0. eth1 is > working fine." This is after a cold boot. > > Evidently the NIC has some non-volatile state, it's not just RAM. It > could well be that the firmware in RAM did something to the NIC that > brought it into this broken state. The firmware blob could even have > fried it, but I think that's unlikely. > > Bottom line is that installing the firmware blob for the network card is > breaking it. Have you performed sufficient troubleshooting to make this claim? If the firmware is the problem conventional wisdom says it will brick all 4 ports, not just one. You've never mentioned the other two ports eth2/3. Are they working? Also, dhclient not receiving a lease doesn't mean eth0 is dead or broken. What does ifconfig tell you? How about /etc/network/interfaces? Also, all modern servers retain power while the cord is jacked in. This is what enables wake-on-LAN, etc. As long as the daughterboard has standby power it will retain the firmware in its onboard RAM. Pull the power cord and wait 60 seconds, then plug it back in. -- Stan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5145eb7e.6050...@hardwarefreak.com
Re: Wheezy issue with broadcom 5720 nic on new dell PowerEdge R720
On 03/16/2013 07:19 PM, Brian wrote: From that moment on eth0 is not working anymore. I get these kernel messages: [ 1796.583881] tg3 :01:00.0: eth0: transmit timed out, resetting A search with "tg3 transmit timed out resetting" turns up some possibilities for you to investigate. Seriously? Are to telling me to f* off too google? No, I am assuming you are trying to be helpful in suggesting that I could find a solution that is already documented online somewhere. Well, I looked around, read all there is to know about the "tg3 transmit timed out resetting" subject. Nothing relevant to my issue. I spent a good half day looking for relevant sources. Then it loads that firmware blob onto the network card, breaking it. And now what? I have a bricked eth0. I really like to repair before the machine goes into production. Suggestions anyone? You are suggesting the loading of firmware has permanently damaged the network card but I wonder whether this can be so. My understanding is similar to what is expressed in this post: http://lists.debian.org/debian-user/2013/01/msg00028.html >> 2) What happens with the firmware when card becomes operational? I >> mean by definition it should be written to device non-volatile >> memory(for example flash memory), but I doubt that this is the case >> for Wi-Fi adapters.. Or is it? > No. The image is simply loaded into the adapter's ram. After the > device loses power the memory evaporates. When power is applied again > the device is once again blank or back to the default power on state > and the firmware must be loaded again. Which has alway been my understanding of it until so far. But I like to repeat from my first email: "I tried the debian installer again, but even then it's not able to get a DHCP IP address using eth0. eth1 is working fine." This is after a cold boot. Evidently the NIC has some non-volatile state, it's not just RAM. It could well be that the firmware in RAM did something to the NIC that brought it into this broken state. The firmware blob could even have fried it, but I think that's unlikely. Bottom line is that installing the firmware blob for the network card is breaking it. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5145e275.5070...@langemeijer.eu
Re: Wheezy issue with broadcom 5720 nic on new dell PowerEdge R720
On Sat 16 Mar 2013 at 12:08:19 +0100, Casper Langemeijer wrote: [Snip] > From that moment on eth0 is not working anymore. I get these kernel > messages: > > [ 1796.583881] tg3 :01:00.0: eth0: transmit timed out, resetting A search with "tg3 transmit timed out resetting" turns up some possibilities for you to investigate. [Snip] > Then it loads that firmware blob onto the network card, breaking it. > > And now what? > > I have a bricked eth0. I really like to repair before the machine > goes into production. Suggestions anyone? You are suggesting the loading of firmware has permanently damaged the network card but I wonder whether this can be so. My understanding is similar to what is expressed in this post: http://lists.debian.org/debian-user/2013/01/msg00028.html >> 2) What happens with the firmware when card becomes operational? I >> mean by definition it should be written to device non-volatile >> memory(for example flash memory), but I doubt that this is the case >> for Wi-Fi adapters.. Or is it? > No. The image is simply loaded into the adapter's ram. After the > device loses power the memory evaporates. When power is applied again > the device is once again blank or back to the default power on state > and the firmware must be loaded again. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130316181950.GS32477@desktop
Wheezy issue with broadcom 5720 nic on new dell PowerEdge R720
Hi List, I've run into an issue trying to install a new PowerEdge R720 server that arrived this week. It is equipped with a broadcom 5720 quad port network interface daughter card. I installed wheezy on it. No problems! The network interface works, and does not require any non-free firmware. Then I installed a xen kernel, and because of that update-initramfs was ran. I noticed these warnings: root@server:~# update-initramfs -uk all update-initramfs: Generating /boot/initrd.img-3.2.0-4-amd64 W: Possible missing firmware /lib/firmware/tigon/tg3_tso5.bin for module tg3 W: Possible missing firmware /lib/firmware/tigon/tg3_tso.bin for module tg3 W: Possible missing firmware /lib/firmware/tigon/tg3.bin for module tg3 These files are listed in the firmware-linux-nonfree package description for squeeze, I thought I'd give this package a try and install it. From that moment on eth0 is not working anymore. I get these kernel messages: [ 1796.583881] tg3 :01:00.0: eth0: transmit timed out, resetting [ 1797.840909] tg3 :01:00.0: eth0: 0x: 0x165f14e4, 0x00100406, 0x0200, 0x00800010 [ 1797.841066] tg3 :01:00.0: eth0: 0x0010: 0xd91a000c, 0x, 0xd91b000c, 0x [ 1797.935588] tg3 :01:00.0: eth0: 0x7030: 0x000e, 0x486c, 0x00170030, 0x [ 1797.935745] tg3 :01:00.0: eth0: 0: Host status block [0005:0003:(::):(:)] [ 1797.935911] tg3 :01:00.0: eth0: 0: NAPI info [0003:0003:(::01ff)::(00e9:::)] [ 1797.936070] tg3 :01:00.0: eth0: 1: Host status block [0001:001c:(::):(001b:)] [ 1797.936226] tg3 :01:00.0: eth0: 1: NAPI info [000c:000c:(::01ff):000b:(000b:000b::)] [ 1797.936383] tg3 :01:00.0: eth0: 2: Host status block [0001:0003:(0002::):(:)] [ 1797.936540] tg3 :01:00.0: eth0: 2: NAPI info [0001:0001:(0001::01ff)::(:::)] [ 1797.936697] tg3 :01:00.0: eth0: 3: Host status block [0001:000e:(::):(:)] [ 1797.936853] tg3 :01:00.0: eth0: 3: NAPI info [000c:000c:(::01ff):000b:(000b:000b::)] [ 1797.937012] tg3 :01:00.0: eth0: 4: Host status block [0001:0011:(::0010):(:)] [ 1797.937168] tg3 :01:00.0: eth0: 4: NAPI info [000c:000c:(::01ff):000b:(000b:000b::)] [ 1797.980164] tg3 :01:00.0: eth0: Link is down [ 1802.092252] tg3 :01:00.0: eth0: Link is up at 1000 Mbps, full duplex [ 1802.092257] tg3 :01:00.0: eth0: Flow control is on for TX and on for RX [ 1802.092261] tg3 :01:00.0: eth0: EEE is disabled [ 1807.591630] tg3 :01:00.0: eth0: transmit timed out, resetting ... and so on I tried the debian installer again, but even then it's not able to get a DHCP IP address using eth0. eth1 is working fine. I booted back into the machine, purged the firmware-linux-nonfree package and am currently using eth1, that is still working: [ 1856.825856] tg3 :01:00.1: eth1: Link is up at 1000 Mbps, full duplex Now what happened? My *guess* is that the Broadcom 5720 for some reason is detected as one of these cards * Broadcom BCM5703/BCM5704 TSO firmware for tigon/tg3_tso.bin) * Broadcom BCM5701A0 firmware (tigon/tg3.bin) * Broadcom BCM5705 TSO firmware (tigon/tg3_tso5.bin) Then it loads that firmware blob onto the network card, breaking it. And now what? I have a bricked eth0. I really like to repair before the machine goes into production. Suggestions anyone? Should a debian package be fixed? It appears that the Broadcom 5720 does not need a firmware blob to operate. http://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/tree/tigon has the same files as the firmware-linux-nonfree package plus one added 7 days ago for '57766 cards'. So nothing important there. There must be some code somewhere that decides what firmware to use. Possibly the tg3.ko driver in linux-image-3.2.0-4-amd64? Hope you can help me and avoid more broken Broadcom 5720's. Greetings, Casper
Re: Broadcom Corporation BCM43224 802.11a/b/g/n (rev 01) without proprietary firmware
On Mi, 29 feb 12, 23:57:14, Stayvoid wrote: > > "To make the firmware work properly you need at least 2 more files that > > must be extracted from original Broadcom drivers: b0g0bsinitvals5.fw and > > b0g0initvals5.fw." > Could you provide an installation guide for OpenFWWF? > I want to test it myself. Maybe those guys didn't have a chance to > test my card. Nope, I just copy-pasted something from the links you mentioned in your previous posts. Besides, the only Broadcom hardware here is my trusty Asus WL500 gPv2 :p Kind regards, Andrei -- Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic signature.asc Description: Digital signature
Re: Broadcom Corporation BCM43224 802.11a/b/g/n (rev 01) without proprietary firmware
> "To make the firmware work properly you need at least 2 more files that > must be extracted from original Broadcom drivers: b0g0bsinitvals5.fw and > b0g0initvals5.fw." Could you provide an installation guide for OpenFWWF? I want to test it myself. Maybe those guys didn't have a chance to test my card. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cak5fs_gxmdjwly88ixymknf-qwi8wyz1r8jlibgwtjkjzup...@mail.gmail.com
Re: Broadcom Corporation BCM43224 802.11a/b/g/n (rev 01) without proprietary firmware
On Mi, 22 feb 12, 16:45:28, Stayvoid wrote: > Hi there! > > I'm trying to configure wlan on my laptop. I've found several guides > on the topic, but all of them require to install non-free software. > [1, 2] I'm looking for a way to make it work without proprietary > software. Someone told me that it's possible with OpenFWWF. [3] "To make the firmware work properly you need at least 2 more files that must be extracted from original Broadcom drivers: b0g0bsinitvals5.fw and b0g0initvals5.fw." It seems to me that even this solution is not 100% free (yet?). I think the only option is to look for Atheros cards, as they do not need non-free firmware. Kind regards, Andrei -- Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic signature.asc Description: Digital signature
Broadcom Corporation BCM43224 802.11a/b/g/n (rev 01) without proprietary firmware
Hi there! I'm trying to configure wlan on my laptop. I've found several guides on the topic, but all of them require to install non-free software. [1, 2] I'm looking for a way to make it work without proprietary software. Someone told me that it's possible with OpenFWWF. [3] But I have no experience in patching. Could you help me with this? What should I do? I'm using gNewSense (it's a Debian-based distro) with the latest Linux-libre kernel (3.2.4). (I'll send a BCC to the gnewsense-users list too.) [1] http://wiki.debian.org/brcm80211#Squeeze [2] http://wireless.kernel.org/en/users/Drivers/b43#Device_firmware_installation [3] http://www.ing.unibs.it/~openfwwf/ Cheers -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cak5fs_gavtrncfieqfd6dzhosdjb5tqtpbosc5ieykro7yw...@mail.gmail.com
Re: Ethernet driver package for broadcom bcm5700/5754
On Sat, 17 Dec 2011 01:05:07 -0500, Sushil Mantri wrote: > I need the driver for broadcom bcm5754. You ethernet card should be supported by "tg3.ko" module. What's the ouput of "lspci -nn"? > I found the source in debian repository, but compiling it has been > painful. Can i get a debian package for the driver? What package are you seeking? Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2011.12.17.15.30...@gmail.com
Ethernet driver package for broadcom bcm5700/5754
Hi, I need the driver for broadcom bcm5754. I found the source in debian repository, but compiling it has been painful. Can i get a debian package for the driver? Thanks, Sushil -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/caffta87zhythpzfsptwjpvyyxwdpdsw-8k6vqhmhtmg+2bk...@mail.gmail.com
Re: setting up WiFi adapter (Broadcom BCM4321 14e4:4328 chipset) in latest version of Debian
Colin Reinhardt schreef: On Sat, Dec 3, 2011 at 12:09 PM, steef wrote: Colin Reinhardt schreef: Im new to Debian/Linux... I have tried following the Debian Wireless-HowTo and other related Linux WiFi HowTos. I downloaded and installed the firmware-b43-installer and b43-fwcutter, (synaptic shows them as installed packages now). In Gnome, using network-manager (applet) there is nothing about wireless networks shown at all, only my wired LAN ethernet network is an option. How can I tell if my PCI card is being detected and firmware loaded correctly, and what are the next steps to get WiFi working? Thanks, Colin maybe this one could be of some help (if you did not already see or found it) with this i got the broadcom chip working on my hp netbook (wl.ko) http://wiki.debian.org/wl regards, steef Steef, that DID IT! I love you :-) (in a platonic computer-geek way). Thanks again, I'm wireless in Debian! Goodbye silly windows, forever! you are welcome, regards, steef -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4edb2f33.4000...@home.nl
Re: setting up WiFi adapter (Broadcom BCM4321 14e4:4328 chipset) in latest version of Debian
On Sat, Dec 3, 2011 at 12:09 PM, steef wrote: > Colin Reinhardt schreef: > >> Im new to Debian/Linux... >> I have tried following the Debian Wireless-HowTo and other related >> Linux WiFi HowTos. >> >> I downloaded and installed the firmware-b43-installer and >> b43-fwcutter, (synaptic shows them as installed packages now). >> >> In Gnome, using network-manager (applet) there is nothing about >> wireless networks shown at all, only my wired LAN ethernet network is >> an option. >> >> How can I tell if my PCI card is being detected and firmware loaded >> correctly, and what are the next steps to get WiFi working? >> Thanks, Colin >> >> > > > maybe this one could be of some help (if you did not already see or found > it) with this i got the broadcom chip working on my hp netbook (wl.ko) > > > http://wiki.debian.org/wl > > > regards, > > steef > Steef, that DID IT! I love you :-) (in a platonic computer-geek way). Thanks again, I'm wireless in Debian! Goodbye silly windows, forever! -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAOJ5kvtrRNXhBzFxO=gjv+hxf9nnk4fwqat6kkahhbxjru+...@mail.gmail.com
