Arch Linux

jghodd

Member

Registered: 2013-02-10

Posts: 180

wl/b43 drivers conflict with tg3

I'm currently running linux-6.3.7, but the problem started with v6.3.5. In this case, my wifi suddenly went out, but my ethernet connection remained solid. I've since discovered that if I disconnect my ethernet line, the wifi comes up. If I plug the ethernet cable back in, my wifi goes away. I have a bcm4312 wireless card (wls1) and a bcm5787m internal ethernet adapter (tg3).

# lshw -c network
  *-network                 
       description: Wireless interface
       product: BCM4312 802.11b/g LP-PHY
       vendor: Broadcom Inc. and subsidiaries
       physical id: 0
       bus info: pci@0000:02:00.0
       logical name: wls1
       version: 01
       serial: 00:21:00:1f:7e:60
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
       configuration: broadcast=yes driver=wl0 driverversion=6.30.223.271 (r587334) ip=192.168.1.107 latency=0 multicast=yes wireless=IEEE 802.11
       resources: irq:17 memory:d8700000-d8703fff
  *-network
       description: Ethernet interface
       product: NetLink BCM5787M Gigabit Ethernet PCI Express
       vendor: Broadcom Inc. and subsidiaries
       physical id: 0
       bus info: pci@0000:85:00.0
       logical name: ens5
       version: 02
       serial: 00:25:b3:7e:92:81
       size: 100Mbit/s
       capacity: 1Gbit/s
       width: 64 bits
       clock: 33MHz
       capabilities: pm vpd msi pciexpress bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=tg3 driverversion=6.3.7-arch1-1 duplex=full firmware=sb v2.13 ip=192.168.2.100 latency=0 link=yes multicast=yes port=twisted pair speed=100Mbit/s
       resources: irq:31 memory:d0600000-d060ffff

I've tried all the solutions offered up online, to the best of my ability, and the issue still remains. I even went ahead and installed/tried both broadcom-wl and broadcom-wl-dkms, both of which activated the wireless adapter, but didn't solve the issue. It is apparent, though, that this conflict is real and there are postings which reflect that fact.

Any ideas? Any other information needed?

I need to run both adapters - the internal ethernet adapter is needed for file sharing (this particular system is the file server), and the wireless adapter is needed for doing system updates, etc.

ewaller

Administrator

From: Pasadena, CA

Registered: 2009-07-13

Posts: 20,634

Re: wl/b43 drivers conflict with tg3

Do these both connect to the same network segment?  (are they both connected to the same router?)

---

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 75,652

Re: wl/b43 drivers conflict with tg3

configuration: broadcast=yes driver=wl0 driverversion=6.30.223.271 (r587334) ip=192.168.1.107 latency=0 multicast=yes wireless=IEEE 802.11
configuration: autonegotiation=on broadcast=yes driver=tg3 driverversion=6.3.7-arch1-1 duplex=full firmware=sb v2.13 ip=192.168.2.100 latency=0 link=yes multicast=yes port=twisted pair speed=100Mbit/s

The issue does not exist w/ the LTS kernel?
Pull the rj45 and dumpt the outputs of "ip a; ip r", then plug the rj45 and then after the wifi is gone for a minute or so, dump the outputs of "ip a; ip r; sudo journalctl -b" and post them.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

jghodd

Member

Registered: 2013-02-10

Posts: 180

Re: wl/b43 drivers conflict with tg3

@ewaller - no. they're on two separate network segments - 192.168.1.x and 192.168.2.x - and connect to different routers. Wireless, of course, connects to my household wireless router, and I run a 3-system nfs backbone across a 100mbit ethernet-only 4 port switch. It's a Linksys switch that has no connection to the internet.

Last edited by jghodd (2023-06-15 04:32:55)

jghodd

Member

Registered: 2013-02-10

Posts: 180

Re: wl/b43 drivers conflict with tg3

@seth - I'm currently using linux-6.3.7. It's important for me to stay on the most current path.

anyway, here's the output:

with rj45 - ip a

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: ens5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 00:25:b3:7e:92:81 brd ff:ff:ff:ff:ff:ff
    altname enp133s0
    inet 192.168.2.100/24 brd 192.168.2.255 scope global noprefixroute ens5
       valid_lft forever preferred_lft forever
    inet6 fe80::f7b3:175d:4835:1d61/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
3: wls1: <NO-CARRIER,BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state DORMANT group default qlen 1000
    link/ether de:f1:b7:28:e5:19 brd ff:ff:ff:ff:ff:ff permaddr 00:21:00:1f:7e:60
    altname wlp2s0
4: docker_gwbridge: <BROADCAST,MULTICAST> mtu 1500 qdisc noqueue state DOWN group default 
    link/ether 02:42:80:06:89:7f brd ff:ff:ff:ff:ff:ff
    inet 172.18.0.1/16 brd 172.18.255.255 scope global docker_gwbridge
       valid_lft forever preferred_lft forever
5: docker0: <BROADCAST,MULTICAST> mtu 1500 qdisc noqueue state DOWN group default 
    link/ether 02:42:f7:31:c3:ec brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
       valid_lft forever preferred_lft forever

with rj45 - ip r

192.168.2.0/24 dev ens5 proto kernel scope link src 192.168.2.100 metric 100

with rj45 - journalctl -b
uploaded to here - it's a lot of output:
https://sourceforge.net/projects/bluest … jctl-b.txt

no rj45 (wireless) - ip a

# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: ens5: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 00:25:b3:7e:92:81 brd ff:ff:ff:ff:ff:ff
    altname enp133s0
3: wls1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 00:21:00:1f:7e:60 brd ff:ff:ff:ff:ff:ff
    altname wlp2s0
    inet 192.168.1.107/24 brd 192.168.1.255 scope global dynamic noprefixroute wls1
       valid_lft 86388sec preferred_lft 86388sec
    inet6 fe80::c711:fd53:9f3b:481c/64 scope link 
       valid_lft forever preferred_lft forever
    inet6 fe80::aa68:8ef8:9ce9:5/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
4: docker_gwbridge: <BROADCAST,MULTICAST> mtu 1500 qdisc noqueue state DOWN group default 
    link/ether 02:42:80:06:89:7f brd ff:ff:ff:ff:ff:ff
    inet 172.18.0.1/16 brd 172.18.255.255 scope global docker_gwbridge
       valid_lft forever preferred_lft forever
5: docker0: <BROADCAST,MULTICAST> mtu 1500 qdisc noqueue state DOWN group default 
    link/ether 02:42:f7:31:c3:ec brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
       valid_lft forever preferred_lft forever

no rj45 (wireless) - ip r

default via 192.168.1.1 dev wls1 proto dhcp src 192.168.1.107 metric 600 
192.168.1.0/24 dev wls1 proto kernel scope link src 192.168.1.107 metric 600

Sorry it;s backwards from your request - it was just how it worked best from a remote terminal. I hope there's some insight into this - it's driving me crazy having to pull the plug to do updates, and unable to remotely connect. I've done some serious looking around and am still baffled.

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 75,652

Re: wl/b43 drivers conflict with tg3

It's important for me to stay on the most current path.

The point is to see whether this is a kernel regression, so please check the LTS behavior…

But first:

… 'cause you're running dhcpcd and NM concurrently ==> start by disabling dhcpcd and then reboot
If that doesn't fix it by itself, disable https://wiki.archlinux.org/title/Networ … domization and if that also doesn't help, lock the BSSID, https://wiki.archlinux.org/title/Networ … ets_(WiFi)

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

jghodd

Member

Registered: 2013-02-10

Posts: 180

Re: wl/b43 drivers conflict with tg3

@seth - ok. first of all, you were correct about dhcpcd - i don't need it and when the wifi came up (after disconnecting the rj45), it initialized just fine. didn't fix the issue, though. i then disabled mac randomization, and that achieved nothing (or at least i noted no changes). i then locked the bssid. also, no change. i was able to update the kernel to 6.3.8 and test it, but it didn't fix anything. lastly, i installed linux-lts and linux-lts-headers, and that changed nothing either.

so, still stuck in the same place.

anything else i can provide? or further advice?

btw, i am still running the lts kernel on this system. i left it installed for now.

Last edited by jghodd (2023-06-16 18:14:59)

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 75,652

Re: wl/b43 drivers conflict with tg3

anything else i can provide?

An updated ("clean") journal w/o dhcpcd and w/ locked BSSID, covering the incident (kernel version doesn't matter)

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

jghodd

Member

Registered: 2013-02-10

Posts: 180

Re: wl/b43 drivers conflict with tg3

@seth - https://sourceforge.net/projects/bluest … tl-b-2.txt

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 75,652

Re: wl/b43 drivers conflict with tg3

Jun 01 14:26:19 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:26:19 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Flow control is on for TX and on for RX
Jun 01 14:26:19 bslxhp64 NetworkManager[582]: <info>  [1685643979.1522] device (ens5): carrier: link connected
** ens5 up

Jun 01 14:26:19 bslxhp64 root[997]: ACPI group/action undefined: 95F24279-4D7B- / 00000080
Jun 01 14:26:19 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:26:19 bslxhp64 root[999]: ACPI group/action undefined: 95F24279-4D7B- / 00000080
** ens5 down (IMMEDIATELY)

Jun 01 14:26:19 bslxhp64 wpa_supplicant[701]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 01 14:26:19 bslxhp64 kernel: ERROR @wl_cfg80211_scan : 
Jun 01 14:26:19 bslxhp64 kernel: WLC_SCAN error (-22)
** scan failed

Jun 01 14:26:20 bslxhp64 NetworkManager[582]: <info>  [1685643980.4358] device (wls1): supplicant interface state: disconnected -> scanning
** scan initiated

Jun 01 14:26:20 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:26:20 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Flow control is on for TX and on for RX
Jun 01 14:26:20 bslxhp64 NetworkManager[582]: <info>  [1685643980.8315] device (ens5): carrier: link connected
** ens5 up

Jun 01 14:26:20 bslxhp64 root[1003]: ACPI group/action undefined: 95F24279-4D7B- / 00000080
Jun 01 14:26:20 bslxhp64 wpa_supplicant[701]: wls1: Trying to associate with e8:6f:f2:ec:a6:32 (SSID='HODDNET' freq=2412 MHz)
Jun 01 14:26:20 bslxhp64 NetworkManager[582]: <info>  [1685643980.9685] device (wls1): supplicant interface state: scanning -> associating
Jun 01 14:26:21 bslxhp64 wpa_supplicant[701]: wls1: Associated with e8:6f:f2:ec:a6:32
Jun 01 14:26:21 bslxhp64 wpa_supplicant[701]: wls1: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Jun 01 14:26:21 bslxhp64 wpa_supplicant[701]: wls1: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=US
Jun 01 14:26:21 bslxhp64 NetworkManager[582]: <info>  [1685643981.0321] device (wls1): supplicant interface state: associating -> associated
Jun 01 14:26:21 bslxhp64 NetworkManager[582]: <info>  [1685643981.0383] device (wls1): supplicant interface state: associated -> 4way_handshake
Jun 01 14:26:21 bslxhp64 wpa_supplicant[701]: wls1: WPA: Key negotiation completed with e8:6f:f2:ec:a6:32 [PTK=CCMP GTK=CCMP]
Jun 01 14:26:21 bslxhp64 wpa_supplicant[701]: wls1: CTRL-EVENT-CONNECTED - Connection to e8:6f:f2:ec:a6:32 completed [id=0 id_str=]
Jun 01 14:26:21 bslxhp64 NetworkManager[582]: <info>  [1685643981.0478] device (wls1): supplicant interface state: 4way_handshake -> completed
** wls1 connected

Jun 01 14:26:21 bslxhp64 wpa_supplicant[701]: wls1: CTRL-EVENT-DISCONNECTED bssid=e8:6f:f2:ec:a6:32 reason=0
Jun 01 14:26:21 bslxhp64 wpa_supplicant[701]: wls1: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Jun 01 14:26:21 bslxhp64 NetworkManager[582]: <info>  [1685643981.5654] device (wls1): supplicant interface state: completed -> disconnected
** wls1 disconnected (IMMEDIATELY)

Jun 01 14:26:21 bslxhp64 wpa_supplicant[701]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 01 14:26:21 bslxhp64 kernel: ERROR @wl_cfg80211_scan : 
Jun 01 14:26:21 bslxhp64 kernel: WLC_SCAN error (-22)
** scan failed

wls1 fails all by itself after ens5 went up/down/up again.

1. make sure the rj45 isn't flaky but firmly sits in the slot
2. try to connect to the BSSID (MAC of the AP) not the SSID to (hopefully) prevent NMs scanning spree.

Alternatively you can try to just configure/run dhcpcd on all NICs and associate wls1 w/ wpa_supplicant or iwd to provide a carrier.
This smells like there's an issue w/ the rj45 connection, your wifi NIC isn't as scan-happy has NM and/or there's some cyclic script (nm dispatcher) logic at play.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

jghodd

Member

Registered: 2013-02-10

Posts: 180

Re: wl/b43 drivers conflict with tg3

@seth - i'm positive that the rj45 is securely in its slot. as for whether or not it's flaky, if it was i'd be seeing flaky behavior with nfs, and i'm not. i even share /var/cache/pacman/pkg off of this machine to 2 other systems, and i've never seen even a ripple in the performance, or a read error or any other kind of nfs error or timeout. what's bugging me most is that this was working flawlessly for... well, years, until either linux635 or 636. there's a bug somewhere.

i'll look into how to connect to the ap using its mac address, and see if that helps any. and i'll let you know how it turns out.

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 75,652

Re: wl/b43 drivers conflict with tg3

The log is obviously older, but

Jun 01 14:25:52 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:25:52 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:25:54 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:25:56 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:25:57 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:25:57 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:25:59 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:26:05 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:26:06 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:26:17 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:26:19 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:26:19 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:26:20 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:26:34 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:26:36 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:26:38 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:26:39 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:26:43 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:26:44 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:27:04 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:27:06 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:27:09 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:27:11 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:27:14 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:27:16 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:27:32 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:27:34 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:27:34 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:27:36 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:27:36 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:27:37 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:27:37 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:27:39 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:27:39 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:27:41 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:27:42 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:27:44 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:27:44 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:27:46 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:27:46 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:27:47 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:27:47 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:27:49 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:27:49 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:27:51 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:27:51 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:27:52 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:27:52 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:27:54 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:27:54 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:27:56 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:28:09 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:28:10 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:28:10 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:28:12 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:28:12 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:28:14 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:28:14 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:28:15 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:28:15 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:28:17 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:28:17 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:28:19 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:28:19 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:28:20 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:28:20 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:28:22 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:28:55 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:28:57 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:28:57 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:28:58 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:29:00 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:29:02 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:29:05 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:29:07 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:29:07 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:29:08 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:29:28 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:29:29 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:29:29 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:29:31 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:29:53 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:29:55 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:29:55 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:29:57 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:30:07 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:30:09 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:30:16 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:30:18 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:30:33 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:30:35 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:30:35 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:30:37 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:30:37 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:30:38 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:30:54 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:30:56 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:30:56 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:30:57 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:31:01 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:31:02 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:31:02 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:31:04 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:31:04 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:31:06 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:31:06 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:31:07 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:31:09 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:31:11 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:31:11 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:31:12 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:31:12 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:31:14 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:31:14 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:31:16 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:31:16 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:31:18 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:31:19 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:31:21 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:31:24 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:31:26 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:31:30 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:31:32 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:31:32 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:31:33 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:31:33 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:31:35 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:31:35 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:31:37 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:31:37 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:31:38 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:31:38 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:31:40 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:31:40 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:31:42 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:31:42 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:31:43 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:31:43 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:31:45 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:31:45 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:31:47 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:31:48 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:31:50 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:31:50 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:31:52 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:31:53 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:31:55 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:31:55 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:31:57 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:31:57 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:31:58 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:31:59 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:32:00 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:32:02 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:32:04 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:32:04 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:32:05 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:32:05 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:32:07 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:32:09 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:32:10 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:32:22 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:32:23 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:32:23 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:32:25 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:32:25 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:32:27 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:32:29 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:32:30 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:32:32 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:32:34 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:32:34 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:32:36 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:32:38 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:32:39 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:32:49 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:32:51 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:32:54 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:32:56 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:32:56 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:32:58 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:33:06 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:33:08 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:34:12 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:34:14 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:34:43 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:34:45 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:35:51 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:35:53 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:36:47 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:36:48 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:36:50 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:36:52 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:37:05 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:37:06 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:37:29 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:37:30 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:37:48 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:37:49 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:37:58 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:38:00 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:38:00 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:38:01 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:38:28 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:38:29 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:38:36 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:38:37 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 01 14:39:41 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 01 14:39:43 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex

unless you rapidly pulled/plugged the cable that day, to ethernet connection flickered A LOT… there're more than 100 reconnects within 15 minutes and it's not evenly distributes, there're several reconnects with the same second. Also it's a 1000Base-T chip, but you only get a 100 Mbps connection.

I'd take two or three very close looks at the cable and the plugs (on both ends).

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

jghodd

Member

Registered: 2013-02-10

Posts: 180

Re: wl/b43 drivers conflict with tg3

@seth - thanks for pointing that out - that is some rapid cycling. i don't get why that's happening, but i agree that that's pretty dodgy. just an fyi, though - my switch is 100mbps, so all the rj45 connections are running at 100mbps. wish i had a faster one, but that's all i've got. it should not be an issue, though. i can certainly swap out the cable and try a different port on the switch... which didn't make any difference.

i have an intel 512an_mmw wifi card, which i already tried, but which came up hard blocked (rfkill list all). I was never able to unblock it, despite the rc.local entry that explicitly calls 'rfkill unblock all' during startup. no attempts to unblock it are working and this system has no specific switch beyond the little wifi light. the bcm4312/4315 is the only one that comes up unblocked, but obviously it's conflicting with tg3 - not sure why tigon3 and not broadcom, even though some of the sites i've visited have suggested that broadcom-wl should be able to drive both devices. i have tried blacklisting tg3 and that just results in no ethernet (rj45).

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 75,652

Re: wl/b43 drivers conflict with tg3

intel 512an_mmw wifi card, which i already tried, but which came up hard blocked … bcm4312/4315 is the only one that comes up unblocked

Vendor locks aren't uncommon.

obviously it's conflicting with tg3

wls1 fails all by itself after ens5 went up/down/up again.

I'm pretty sure this is the setup and I'd be less shocked if the flaky rj45 + NM's response to that was the cause.
Did you try dhcpcd + wpa_supplicant yet?

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

jghodd

Member

Registered: 2013-02-10

Posts: 180

Re: wl/b43 drivers conflict with tg3

@seth - this wasn't a case of vendor lock - the intel card was the original wifi card for this laptop, so it should have come up unblocked, as it did for so many years. as for the conflict, i'm reading in a lot of places that broadcom and tg3 don't play nice together. their solution invariably includes blacklisting tg3, which kills my ethernet (rj45).

this is the modprobe config file that comes with broadcom-wl:

# wl module from Broadcom conflicts with the following modules:
blacklist b43
blacklist b43legacy
blacklist b44
blacklist bcma
blacklist brcm80211
blacklist brcmfmac
blacklist brcmsmac
blacklist ssb
blacklist tg3

i've tried un-blacklisting them one at a time, and selectively, and still the issue continues. i'm trying to figure out, too, if i can get the intel card going again. for now, the only card that 1) allowed the system to boot and 2) wasn't hard blocked is the bcm4312/5, but it seems to require the broadcom-wl driver which conflicts with tg3. when it was running (flawlessly) with the 512an (intel) it came with, it was using the iwlwifi driver which suddenly stopped working - or seemed to until i discovered that rfkill was showing the card suddenly hard blocked. is the issue rfkill? i feel like if i can get around the hard block, i could potentially get the wifi running again using the intel 512an.

i'll try the intel card again and maybe downgrade the kernel (not ideal, but might show what's gone wrong).

i do need some clarification on dhcpcd and wpa_supplicant. are you saying i should now re-enable dhcpcd? and wpa_supplicant is already running on my system, so we'd just be returning to the state we were in from the start. full circle. or did you mean something else?

also, i'm still not convinced the rj45 has any real issues. it's been working as expected without error for years. that doesn't mean the tg3 driver might not have some newly introduced issues. you can see from the ifconfig dump for the rj45 interface (ens5), that there have been no transmission or reception errors, no overruns, no carrier errors, nothing dropped and no collisions:

ens5: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.2.100  netmask 255.255.255.0  broadcast 192.168.2.255
        inet6 fe80::f7b3:175d:4835:1d61  prefixlen 64  scopeid 0x20<link>
        ether 00:25:b3:7e:92:81  txqueuelen 1000  (Ethernet)
        RX packets 1402458  bytes 1018893709 (971.6 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 1762907  bytes 2197678091 (2.0 GiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 17

very puzzling.

Last edited by jghodd (2023-06-19 23:32:10)

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 75,652

Re: wl/b43 drivers conflict with tg3

i do need some clarification on dhcpcd and wpa_supplicant. are you saying i should now re-enable dhcpcd? and wpa_supplicant is already running on my system, so we'd just be returning to the state we were in from the start. full circle. or did you mean something else?

You should predominantly stop and disable networkmanager.
You'll then have to use wpa_supplicant (or iwd) explicitly to gain a wifi carrier and (eg.) dhcpcd to obtain a lease.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

jghodd

Member

Registered: 2013-02-10

Posts: 180

Re: wl/b43 drivers conflict with tg3

@seth - ah. i get it. ok, it's a learning experience at worst, so it's worth a try. i'll post once i get there. it is a little daunting to get rid of networkmanager, since it and its related tools are what i'm accustomed to, but i'll check the wiki for guidance on what's needed to set up wpa_supplicant - i'm sure there must be a config file somewhere. i'll find it.

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 75,652

Re: wl/b43 drivers conflict with tg3

https://wiki.archlinux.org/title/Wpa_su … th_wpa_cli
Don't uninstall NM, you only have to stop it.

You can probably also use https://wiki.archlinux.org/title/Netctl (use wifi-menu to create the wireless profile, write the wired one and start both)

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

jghodd

Member

Registered: 2013-02-10

Posts: 180

Re: wl/b43 drivers conflict with tg3

@seth - just to catch you up, and so that this thread stays fresh since i have some other pressing things taking up my time at the moment, just adding a couple of things to the mix.

here's a link to a bug report that describes this issue - https://bugs.archlinux.org/task/70476

if i blacklist tg3, i get full wireless on reboot, but when i modprobe tg3 at that point in time, i get my rj45 wired ethernet back, but i lose the wifi.

while i'm losing my wifi (as described in the last line) i'm getting an error message - "Authorization supplicant timed out".

now that you're caught up, i'll take another look at switching from networkmanager to wpa_supplicant.

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 75,652

Re: wl/b43 drivers conflict with tg3

That bug is about installing broadcom-wl blacklisting tg3 what's not the case for you.
The bug also rather illustrates that a bunch of people are using wl and tg3 happily along each other.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

jghodd

Member

Registered: 2013-02-10

Posts: 180

Re: wl/b43 drivers conflict with tg3

@seth - ok. i created 2 netctl profiles - wls1-HODDNET and ens5-WIRENET:

wls1-HODDNET

Description='Automatically generated profile by wifi-menu'
Interface=wls1
Connection=wireless
Security=wpa
ESSID=HODDNET
IP=dhcp
Key=XXXXXXXXXXXXXXXX

ens5-WIRENET

Description='A basic static ethernet connection'
Interface=ens5
Connection=ethernet
IP=static
Address=('192.168.2.100/24')

i started both, although there were errors with ens5-WIRENET, but both appeared to be connected when checking their status with ifconfig:

ens5: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.2.100  netmask 255.255.255.0  broadcast 192.168.2.255
        inet6 fe80::f7b3:175d:4835:1d61  prefixlen 64  scopeid 0x20<link>
        ether 00:25:b3:7e:92:81  txqueuelen 1000  (Ethernet)
        RX packets 526  bytes 76751 (74.9 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 437  bytes 61059 (59.6 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 17  

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 1004  bytes 81092 (79.1 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 1004  bytes 81092 (79.1 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wls1: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 192.168.1.107  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 fe80::221:ff:fe1f:7e60  prefixlen 64  scopeid 0x20<link>
        ether 00:21:00:1f:7e:60  txqueuelen 1000  (Ethernet)
        RX packets 19457  bytes 28684075 (27.3 MiB)
        RX errors 0  dropped 0  overruns 0  frame 105087
        TX packets 10044  bytes 885612 (864.8 KiB)
        TX errors 420  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 17

...but, neither interface was actually working!

so, i've gone back to networkmanager for now, because i need this nfs server to be online and at least visible to my nfs clients.

jghodd

Member

Registered: 2013-02-10

Posts: 180

Re: wl/b43 drivers conflict with tg3

@seth - but that is the case for me. i'm trying to bring up my wireless with broadcom-wl and my wired connection (bcm5787m) with tg3, so it's exactly the same case. and as you pointed out, some aren't experiencing the conflict, but that also means that others are, especially given the related-bug link in this bug report.

anyway, i was going to add to that list of things that i also tested against linux 6.3.9 which was released today - still, no go.

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 75,652

Re: wl/b43 drivers conflict with tg3

neither interface was actually working!

Please don't paraphrase, https://bbs.archlinux.org/viewtopic.php?id=57855

How did you test them and what was the actual outcome? (There're no package errors or packages dropped)
Also look at the resulting routing table.

(You can do so if and when it suits you, this here is running by your pace)

Edit:

but that is the case for me.

I suspect that's a misunderstanding.
The complaint in the bug was that the tg3 module would not be loaded because it got blacklisted by the wl package.

modprobe -c | grep tg3 | grep -v alias

Does this show that tg3 is blacklisted?

Last edited by seth (2023-06-22 19:36:24)

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

jghodd

Member

Registered: 2013-02-10

Posts: 180

Re: wl/b43 drivers conflict with tg3

@seth - just as an fyi, the tigon3 code limits my 5787m rj45 adapter to 10/100 mbits, so gigabit mode is not available.

{PCI_DEVICE_SUB(PCI_VENDOR_ID_BROADCOM, TG3PCI_DEVICE_TIGON3_5787M,
			PCI_VENDOR_ID_LENOVO,
			TG3PCI_SUBDEVICE_ID_LENOVO_5787M),
	 .driver_data = TG3_DRV_DATA_FLAG_10_100_ONLY}

Edit: also, to be clear, what that bug report said to me was that some combinations of broadcom rj45 adapter(s) and broadcom wireless adapter(s) work just fine, while other combinations conflict with one another. my combination of bcm5787m + bcm4312/15 doesn't play nice together. my guess is that a different combination of adapters will probably work just fine. one thing i am going to do today is search my storage room for yet another wireless adapter. keeping my fingers crossed that i might find one that works and doesn't conflict with the rj45 driver.

Last edited by jghodd (2023-06-25 18:07:57)

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 75,652

Re: wl/b43 drivers conflict with tg3

Afaiu the bug, tg3 was blacklisted simply by accident because it's a broadcom driver.
You could also try to blacklist tg3 on your system and see whether broadcom-wl indeed picks up the device.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc