From: shnaps <shnaps@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Network issues with dell e6330
Date: Fri, 21 Feb 2020 08:06:56 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-19340@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1157 bytes --]
New issue by shnaps on void-packages repository
https://github.com/void-linux/void-packages/issues/19340
Description:
I'm using an old laptop with an even older wifi card.
Here is _lspci -k_ for it
> 02:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4313 802.11bgn Wireless Network Adapter (rev 01)
>Subsystem: Dell Device 0015
>Kernel driver in use: bcma-pci-bridge
Current kernel version
>5.4.21_1
I have been using brcmsmac as a driver all the time. But it stopped working for last couple linux 5.4.* kernels(my guess). Not sure about the precise date but laptop been working at the end of january(25-31).
So basically it just stops sending/receiving packets and I'm getting 100% packets lost. Happening every 2 minutes. Restart/driver reload helps temporally only for the next couple minutes.
Changing drivers from brcmsmac to wl(broadcom-wl-dkms) helps to restore internet and stop packets loss. But in a long term perspective, it is unusable(it doesn't see wifi networks).
To make this driver work I need to :
>1. rmmod wl
2. modprobe brcmsmac
3. rmmod brcmsmac
4. modprobe wl
After that I'll see all anetworks.
next reply other threads:[~2020-02-21 7:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-21 7:06 shnaps [this message]
2020-02-21 7:37 ` Anachron
2020-02-21 7:41 ` shnaps
2020-02-21 8:05 ` shnaps
2021-01-21 15:17 ` ericonr
2022-04-15 2:13 ` github-actions
2022-04-29 2:13 ` [ISSUE] [CLOSED] " github-actions
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-19340@inbox.vuxu.org \
--to=shnaps@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).