Using the Ookla speedtest site on a browser, my current laptop gets about 40-60 
Mbps; the EliteBook gets about 0.2 - 0.4 Mbps. So I wasn't kidding about 2 
orders of magnitude. Using simple pings around the local network, the EliteBook 
seems ok; ping response time is in line with the other machines, packets aren't 
getting dropped during the ping tests.

It may be coincidental, but I noticed that twice during the times I was running 
the speedtest on the EliteBook, the Internet connection on other devices in the 
house dropped. Other times I ran the test, the connections were fine. So I 
wonder if there is some kind of interference going on, at least sometimes.

I'm using 2.4GHz for the all the laptops in the house because the 2.4 signal 
seems to degrade much less with distance from the router than the 5Ghz.



--
- David Fleck


On Tuesday, September 24th, 2024 at 12:32 PM, Russell Senior 
<russ...@personaltelco.net> wrote:

> On Tue, Sep 24, 2024 at 8:37 AM Michael Ewan michaelewa...@gmail.com wrote:
>
> > Could this be something as simple as channel interference from a neighbor?
>
>
> Probably not, because other clients are probably connecting to the
> same access points and the access points are defining which channela
> are in use. So, neighbor interference would apply equally to other
> clients. If the slow client is connecting on 2.4GHz and not 5GHz,
> though, interference might be more of an issue.
>
> The other missing piece of diagnositic information is: what counts as
> slow? How is the slowness measured and what are the measurements,
> numerically?
>
> --
> Russell Senior
> russ...@personaltelco.net
>
> > On Mon, Sep 23, 2024 at 8:41 PM Russell Senior russ...@personaltelco.net
> > wrote:
> >
> > > Another useful command is:
> > >
> > > $ iw phy0 info | less
> > >
> > > Which will tell you a bunch of information about what channels are
> > > tunable and the modes (and combinations) the the radio supports.
> > >
> > > E.g.:
> > >
> > > Wiphy phy0
> > > wiphy index: 0
> > > max # scan SSIDs: 20
> > > max scan IEs length: 422 bytes
> > > max # sched scan SSIDs: 20
> > > max # match sets: 11
> > > Retry short limit: 7
> > > Retry long limit: 4
> > > Coverage class: 0 (up to 0m)
> > > Device supports RSN-IBSS.
> > > Device supports AP-side u-APSD.
> > > Supported Ciphers:
> > > * WEP40 (00-0f-ac:1)
> > > * WEP104 (00-0f-ac:5)
> > > * TKIP (00-0f-ac:2)
> > > * CCMP-128 (00-0f-ac:4)
> > > * CMAC (00-0f-ac:6)
> > > Available Antennas: TX 0x3 RX 0x3
> > > Configured Antennas: TX 0x3 RX 0x3
> > > Supported interface modes:
> > > * IBSS
> > > * managed
> > > * AP
> > > * AP/VLAN
> > > * monitor
> > > * P2P-client
> > > * P2P-GO
> > > * P2P-device
> > > Band 1:
> > > Capabilities: 0x11ef
> > > RX LDPC
> > > HT20/HT40
> > > SM Power Save disabled
> > > RX HT20 SGI
> > > RX HT40 SGI
> > > TX STBC
> > > RX STBC 1-stream
> > > Max AMSDU length: 3839 bytes
> > > DSSS/CCK HT40
> > > Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
> > > Minimum RX AMPDU time spacing: 4 usec (0x05)
> > > HT Max RX data rate: 300 Mbps
> > > HT TX/RX MCS rate indexes supported: 0-15
> > > Bitrates (non-HT):
> > > * 1.0 Mbps
> > > * 2.0 Mbps (short preamble supported)
> > > * 5.5 Mbps (short preamble supported)
> > > * 11.0 Mbps (short preamble supported)
> > > * 6.0 Mbps
> > > * 9.0 Mbps
> > > * 12.0 Mbps
> > > * 18.0 Mbps
> > > * 24.0 Mbps
> > > * 36.0 Mbps
> > > * 48.0 Mbps
> > > * 54.0 Mbps
> > > Frequencies:
> > > * 2412 MHz [1] (22.0 dBm)
> > > * 2417 MHz [2] (22.0 dBm)
> > > * 2422 MHz [3] (22.0 dBm)
> > > * 2427 MHz [4] (22.0 dBm)
> > > * 2432 MHz [5] (22.0 dBm)
> > > * 2437 MHz [6] (22.0 dBm)
> > > * 2442 MHz [7] (22.0 dBm)
> > > * 2447 MHz [8] (22.0 dBm)
> > > * 2452 MHz [9] (22.0 dBm)
> > > * 2457 MHz [10] (22.0 dBm)
> > > * 2462 MHz [11] (22.0 dBm)
> > > * 2467 MHz [12] (22.0 dBm)
> > > * 2472 MHz [13] (22.0 dBm)
> > > * 2484 MHz [14] (disabled)
> > > Band 2:
> > > Capabilities: 0x11ef
> > > RX LDPC
> > > HT20/HT40
> > > SM Power Save disabled
> > > RX HT20 SGI
> > > RX HT40 SGI
> > > TX STBC
> > > RX STBC 1-stream
> > > Max AMSDU length: 3839 bytes
> > > DSSS/CCK HT40
> > > Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
> > > Minimum RX AMPDU time spacing: 4 usec (0x05)
> > > HT Max RX data rate: 300 Mbps
> > > HT TX/RX MCS rate indexes supported: 0-15
> > > VHT Capabilities (0x039071b0):
> > > Max MPDU length: 3895
> > > Supported Channel Width: neither 160 nor 80+80
> > > RX LDPC
> > > short GI (80 MHz)
> > > TX STBC
> > > SU Beamformee
> > > MU Beamformee
> > > VHT RX MCS set:
> > > 1 streams: MCS 0-9
> > > 2 streams: MCS 0-9
> > > 3 streams: not supported
> > > 4 streams: not supported
> > > 5 streams: not supported
> > > 6 streams: not supported
> > > 7 streams: not supported
> > > 8 streams: not supported
> > > VHT RX highest supported: 0 Mbps
> > > VHT TX MCS set:
> > > 1 streams: MCS 0-9
> > > 2 streams: MCS 0-9
> > > 3 streams: not supported
> > > 4 streams: not supported
> > > 5 streams: not supported
> > > 6 streams: not supported
> > > 7 streams: not supported
> > > 8 streams: not supported
> > > VHT TX highest supported: 0 Mbps
> > > Bitrates (non-HT):
> > > * 6.0 Mbps
> > > * 9.0 Mbps
> > > * 12.0 Mbps
> > > * 18.0 Mbps
> > > * 24.0 Mbps
> > > * 36.0 Mbps
> > > * 48.0 Mbps
> > > * 54.0 Mbps
> > > Frequencies:
> > > * 5180 MHz [36] (22.0 dBm)
> > > * 5200 MHz [40] (22.0 dBm)
> > > * 5220 MHz [44] (22.0 dBm)
> > > * 5240 MHz [48] (22.0 dBm)
> > > * 5260 MHz [52] (22.0 dBm) (no IR, radar detection)
> > > * 5280 MHz [56] (22.0 dBm) (no IR, radar detection)
> > > * 5300 MHz [60] (22.0 dBm) (no IR, radar detection)
> > > * 5320 MHz [64] (22.0 dBm) (no IR, radar detection)
> > > * 5340 MHz [68] (disabled)
> > > * 5360 MHz [72] (disabled)
> > > * 5380 MHz [76] (disabled)
> > > * 5400 MHz [80] (disabled)
> > > * 5420 MHz [84] (disabled)
> > > * 5440 MHz [88] (disabled)
> > > * 5460 MHz [92] (disabled)
> > > * 5480 MHz [96] (disabled)
> > > * 5500 MHz [100] (22.0 dBm) (no IR, radar
> > > detection)
> > > * 5520 MHz [104] (22.0 dBm) (no IR, radar
> > > detection)
> > > * 5540 MHz [108] (22.0 dBm) (no IR, radar
> > > detection)
> > > * 5560 MHz [112] (22.0 dBm) (no IR, radar
> > > detection)
> > > * 5580 MHz [116] (22.0 dBm) (no IR, radar
> > > detection)
> > > * 5600 MHz [120] (22.0 dBm) (no IR, radar
> > > detection)
> > > * 5620 MHz [124] (22.0 dBm) (no IR, radar
> > > detection)
> > > * 5640 MHz [128] (22.0 dBm) (no IR, radar
> > > detection)
> > > * 5660 MHz [132] (22.0 dBm) (no IR, radar
> > > detection)
> > > * 5680 MHz [136] (22.0 dBm) (no IR, radar
> > > detection)
> > > * 5700 MHz [140] (22.0 dBm) (no IR, radar
> > > detection)
> > > * 5720 MHz [144] (22.0 dBm) (no IR, radar
> > > detection)
> > > * 5745 MHz [149] (22.0 dBm)
> > > * 5765 MHz [153] (22.0 dBm)
> > > * 5785 MHz [157] (22.0 dBm)
> > > * 5805 MHz [161] (22.0 dBm)
> > > * 5825 MHz [165] (22.0 dBm)
> > > * 5845 MHz [169] (disabled)
> > > * 5865 MHz [173] (disabled)
> > > * 5885 MHz [177] (disabled)
> > > * 5905 MHz [181] (disabled)
> > > Supported commands:
> > > * new_interface
> > > * set_interface
> > > * new_key
> > > * start_ap
> > > * new_station
> > > * new_mpath
> > > * set_mesh_config
> > > * set_bss
> > > * authenticate
> > > * associate
> > > * deauthenticate
> > > * disassociate
> > > * join_ibss
> > > * join_mesh
> > > * remain_on_channel
> > > * set_tx_bitrate_mask
> > > * frame
> > > * frame_wait_cancel
> > > * set_wiphy_netns
> > > * set_channel
> > > * start_sched_scan
> > > * probe_client
> > > * set_noack_map
> > > * register_beacons
> > > * start_p2p_device
> > > * set_mcast_rate
> > > * connect
> > > * disconnect
> > > * channel_switch
> > > * set_qos_map
> > > * add_tx_ts
> > > * set_multicast_to_unicast
> > > WoWLAN support:
> > > * wake up on disconnect
> > > * wake up on magic packet
> > > * wake up on pattern match, up to 20 patterns of 16-128
> > > bytes,
> > > maximum packet offset 0 bytes
> > > * can do GTK rekeying
> > > * wake up on GTK rekey failure
> > > * wake up on EAP identity request
> > > * wake up on 4-way handshake
> > > * wake up on rfkill release
> > > * wake up on network detection, up to 11 match sets
> > > software interface modes (can always be added):
> > > * AP/VLAN
> > > * monitor
> > > valid interface combinations:
> > > * #{ managed } <= 1, #{ AP, P2P-client, P2P-GO } <=
> > > 1, #{ P2P-device } <= 1,
> > > total <= 3, #channels <= 2
> > > HT Capability overrides:
> > > * MCS: ff ff ff ff ff ff ff ff ff ff
> > > * maximum A-MSDU length
> > > * supported channel width
> > > * short GI for 40 MHz
> > > * max A-MPDU length exponent
> > > * min MPDU start spacing
> > > Device supports TX status socket option.
> > > Device supports HT-IBSS.
> > > Device supports SAE with AUTHENTICATE command
> > > Device supports low priority scan.
> > > Device supports scan flush.
> > > Device supports per-vif TX power setting
> > > P2P GO supports CT window setting
> > > P2P GO supports opportunistic powersave setting
> > > Driver supports full state transitions for AP/GO clients
> > > Driver supports a userspace MPM
> > > Driver/device bandwidth changes during BSS lifetime (AP/GO mode)
> > > Device adds DS IE to probe requests
> > > Device can update TPC Report IE
> > > Device supports static SMPS
> > > Device supports dynamic SMPS
> > > Device supports WMM-AC admission (TSPECs)
> > > Device supports configuring vdev MAC-addr on create.
> > > Device supports randomizing MAC-addr in scans.
> > > Device supports randomizing MAC-addr in sched scans.
> > > Device supports randomizing MAC-addr in net-detect scans.
> > > max # scan plans: 2
> > > max scan plan interval: 65535
> > > max scan plan iterations: 254
> > > Supported TX frame types:
> > > * IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80
> > > 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
> > > * managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70
> > > 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
> > > * AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80
> > > 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
> > > * AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70
> > > 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
> > > * mesh point: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70
> > > 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
> > > * P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70
> > > 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
> > > * P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70
> > > 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
> > > * P2P-device: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70
> > > 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
> > > Supported RX frame types:
> > > * IBSS: 0x40 0xb0 0xc0 0xd0
> > > * managed: 0x40 0xb0 0xd0
> > > * AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
> > > * AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
> > > * mesh point: 0xb0 0xc0 0xd0
> > > * P2P-client: 0x40 0xd0
> > > * P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
> > > * P2P-device: 0x40 0xd0
> > > Supported extended features:
> > > * [ VHT_IBSS ]: VHT-IBSS
> > > * [ RRM ]: RRM
> > > * [ MU_MIMO_AIR_SNIFFER ]: MU-MIMO sniffer
> > > * [ SCAN_START_TIME ]: scan start timestamp
> > > * [ BSS_PARENT_TSF ]: BSS last beacon/probe TSF
> > > * [ FILS_STA ]: STA FILS (Fast Initial Link Setup)
> > > * [ FILS_MAX_CHANNEL_TIME ]: FILS max channel
> > > attribute override with dwell time
> > > * [ ACCEPT_BCAST_PROBE_RESP ]: accepts broadcast probe
> > > response
> > > * [ OCE_PROBE_REQ_HIGH_TX_RATE ]: probe request TX at
> > > high rate (at least 5.5Mbps)
> > > * [ OCE_PROBE_REQ_DEFERRAL_SUPPRESSION ]: probe
> > > request tx deferral and suppression
> > > * [ CONTROL_PORT_OVER_NL80211 ]: control port over nl80211
> > > * [ TXQS ]: FQ-CoDel-enabled intermediate TXQs
> > > * [ EXT_KEY_ID ]: Extended Key ID support
> > > * [ CONTROL_PORT_NO_PREAUTH ]: disable pre-auth over
> > > nl80211 control port support
> > > * [ DEL_IBSS_STA ]: deletion of IBSS station support
> > > * [ SCAN_FREQ_KHZ ]: scan on kHz frequency support
> > > * [ CONTROL_PORT_OVER_NL80211_TX_STATUS ]: tx status
> > > for nl80211 control port support
> > >
> > > On Mon, Sep 23, 2024 at 7:02 PM Russell Senior
> > > russ...@personaltelco.net wrote:
> > >
> > > > It says 802.11a (amongst others "802.11a/b/g/n") which implies it also
> > > > can tune 5GHz channels.
> > > >
> > > > On Mon, Sep 23, 2024 at 7:00 PM Tomas Kuchta
> > > > tomas.kuchta.li...@gmail.com wrote:
> > > >
> > > > > I noticed that the wifi card is 2.4GHz - if I have not overlooked the
> > > > > 5GHz
> > > > > part, it may not even have 5GHZ antena to plug into the new wifi 6e
> > > > > (ax)
> > > > > card. That could spoil the replacement idea.
> > > > >
> > > > > I suggest to open the laptop and look for the 5GHz antena. It may be
> > > > > there
> > > > > unplugged or taped to some safe spot.
> > > > >
> > > > > Tomas
> > > > >
> > > > > On Mon, Sep 23, 2024, 20:08 Russell Senior russ...@personaltelco.net
> > > > > wrote:
> > > > >
> > > > > > Broadcom wifi is famously bad on Linux because of hostility from
> > > > > > Broadcom to open source software. Broadcom is the NVidia of the
> > > > > > networking world. In theory, you might be able to replace the wifi
> > > > > > radio with an Intel wifi radio. Although, sometimes the radios are
> > > > > > locked by BIOS checks. Also, it seems to be limited to 802.11n 
> > > > > > (which
> > > > > > is a couple generations old), which could also explain the speed
> > > > > > differences.
> > > > > >
> > > > > > Maybe something like this would work:
> > > > > > https://www.amazon.com/dp/B09CDFV2CL/
> > > > > >
> > > > > > On Mon, Sep 23, 2024 at 4:48 PM David Fleck dcfl...@protonmail.ch
> > > > > > wrote:
> > > > > >
> > > > > > > Output of command:
> > > > > > >
> > > > > > > 25:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries
> > > > > > > BCM43224 802.11a/b/g/n [14e4:4353] (rev 01)
> > > > > > > Subsystem: Hewlett-Packard Company WMIB-275N Half-size
> > > > > > > Mini PCIe
> > > > > > > Card [103c:1509]
> > > > > > > Flags: bus master, fast devsel, latency 0, IRQ 19
> > > > > > > Memory at d4100000 (64-bit, non-prefetchable) [size=16K]
> > > > > > > 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-7a-ff-ff-2b-20-10
> > > > > > > Capabilities: [16c] Power Budgeting <?>
> > > > > > > Kernel driver in use: bcma-pci-bridge
> > > > > > > Kernel modules: bcma
> > > > > > >
> > > > > > > --
> > > > > > > - David Fleck
> > > > > > >
> > > > > > > On Monday, September 23rd, 2024 at 2:27 PM, Russell Senior <
> > > > > > > russ...@personaltelco.net> wrote:
> > > > > > >
> > > > > > > > e.g.:
> > > > > > > >
> > > > > > > > $ lspci | grep Network | awk '{ print $1}' | while read d ; do
> > > > > > > > lspci
> > > > > > > > -s $d -v -nn ; done
> > > > > > > > aa:00.0 Network controller [0280]: Intel Corporation Wi-Fi 6
> > > > > > > > AX210/AX211/AX411 160MHz [8086:2725] (rev 1a)
> > > > > > > > Subsystem: Intel Corporation Wi-Fi 6 AX210 160MHz [8086:0024]
> > > > > > > > Flags: bus master, fast devsel, latency 0, IRQ 16, IOMMU group 
> > > > > > > > 17
> > > > > > > > Memory at 7a200000 (64-bit, non-prefetchable) [size=16K]
> > > > > > > > Capabilities: <access denied>
> > > > > > > >
> > > > > > > > Kernel driver in use: iwlwifi
> > > > > > > > Kernel modules: iwlwifi
> > > > > > > >
> > > > > > > > On Mon, Sep 23, 2024 at 9:24 AM Russell Senior
> > > > > > > > russ...@personaltelco.net wrote:
> > > > > > > >
> > > > > > > > > On Mon, Sep 23, 2024 at 5:51 AM David Fleck
> > > > > > > > > dcfl...@protonmail.ch
> > > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > So far, my laptop quest has lead me to an HP EliteBook 8560p
> > > > > > > > > > cast
> > > > > > > > > > off by my employer. So, yay, free!
> > > > > > > > > >
> > > > > > > > > > Installed OpenSuse Leap 15.6, everything seems to just work,
> > > > > > > > > > except: battery is dead (easily fixed) and the wifi is
> > > > > > > > > > molasses-in-January
> > > > > > > > > > slow, as in 2 orders of magnitude slower than other laptops 
> > > > > > > > > > in the
> > > > > > > > > > house.
> > > > > > > > >
> > > > > > > > > A good place to start is to figure out what the wifi interface
> > > > > > > > > is.
> > > > > > > > > What does lspci call the wifi interface?
> > > > > > > > >
> > > > > > > > > --
> > > > > > > > > Russell Senior
> > > > > > > > > russ...@personaltelco.net

Reply via email to