Hi Deano, thanks for the reply - here is my hwinfo:
Code:
07: PCI 100.0: 0282 WLAN controller
[Created at pci.386]
Unique ID: y9sn.MxvvoCwdjwB
Parent ID: z8Q3.O8qDgKpXcV4
SysFS ID: /devices/pci0000:00/0000:00:1c.0/0000:01:00.0
SysFS BusID: 0000:01:00.0
Hardware Class: network
Device Name: "Ralink WLAN Ralink RT3290LE Roma 802.11bgn 1x1 Wi-Fi + BT4.0 co"
Model: "Hewlett-Packard Company Ralink RT3290LE 802.11bgn 1x1 Wi-Fi and Bluetooth 4.0 Combo Adapter"
Vendor: pci 0x1814 "Ralink corp."
Device: pci 0x3290 "RT3290 Wireless 802.11n 1T/1R PCIe"
SubVendor: pci 0x103c "Hewlett-Packard Company"
SubDevice: pci 0x18ec "Ralink RT3290LE 802.11bgn 1x1 Wi-Fi and Bluetooth 4.0 Combo Adapter"
Driver: "rt2800pci"
Driver Modules: "rt2800pci"
Device File: wlan0
Features: WLAN
Memory Range: 0x52510000-0x5251ffff (rw,non-prefetchable)
IRQ: 16 (no events)
HW Address: 68:94:23:a5:fb:e1
Permanent HW Address: 68:94:23:a5:fb:e1
Link detected: yes
WLAN channels: 1 2 3 4 5 6 7 8 9 10 11 12 13 14
WLAN frequencies: 2.412 2.417 2.422 2.427 2.432 2.437 2.442 2.447 2.452 2.457 2.462 2.467 2.472 2.484
WLAN encryption modes: WEP40 WEP104 TKIP CCMP
WLAN authentication modes: open sharedkey wpa-psk wpa-eap
Module Alias: "pci:v00001814d00003290sv0000103Csd000018ECbc02sc80i00"
Driver Info #0:
Driver Status: rt2800pci is active
Driver Activation Cmd: "modprobe rt2800pci"
Config Status: cfg=no, avail=yes, need=no, active=unknown
Attached to: #3 (PCI bridge)
I don't know if the Ralink adaptor is Broadcom related (and the responses in the article you posted seemed to indicate it was broadcom harsware that was the culprit).
The journalctl command is mainly handshake messages - other than this.
Code:
Dec 30 12:55:35 Linux-box NetworkManager[23358]: <warn> [1640868935.6492] sup-iface[0x55bef09ca110,wlan0]: connection disconnected (reason -4)
Magni