search

morrownr / 8821au-20210708

Linux Driver for USB WiFi Adapters that are based on the RTL8811AU and RTL8821AU Chipsets - v5.12.5.2
Other
659 stars 98 forks source link

(solved) Problems with A6100 on RPI4 64 bit #31

Closed Musiker closed 2 years ago

Musiker commented 2 years ago

Hi, I am tinkering with a RPI4 and a A6100, but as soon as I plug in the A6100 things go downhill :-| - Basically any iw and uname command as requested for the issue report cause cause some lockup as seen in the syslog dump below. Anyone have experience with this kind of behavior? Is it my kernel version that is unsupported - Any tips for debugging?

I am using wlan0 for connecting to wlan - So I would like to keep that enabled and then use the A6100 for testing.

Info before plugging in:

Linux pi4hyper 5.15.32-v8+ #1538 SMP PREEMPT Thu Mar 31 19:40:39 BST 2022 aarch64 GNU/Linux
EFI variables are not supported on this system
Bus 002 Device 002: ID 152d:0562 JMicron Technology Corp. / JMicron USA Technology Corp. JMS567 SATA 6Gb/s bridge
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 3151:3000 YICHIP Wireless Device
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
1: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no
rtl8821au, 5.12.5.2, 5.15.32-v8+, aarch64: installed
phy#0
    Unnamed/non-netdev interface
        wdev 0x2
        addr de:a6:32:18:5d:4e
        type P2P-device
        txpower 31.00 dBm
    Interface wlan0
        ifindex 3
        wdev 0x1
        addr dc:a6:32:18:5d:4e
        ssid billebib
        type managed
        channel 100 (5500 MHz), width: 80 MHz, center1: 5530 MHz
        txpower 31.00 dBm

Log when plugging in the A6100:

Bus 002 Device 002: ID 152d:0562 JMicron Technology Corp. / JMicron USA Technology Corp. JMS567 SATA 6Gb/s bridge
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 3151:3000 YICHIP Wireless Device
Bus 001 Device 004: ID 0846:9052 NetGear, Inc. A6100 AC600 DB Wireless Adapter [Realtek RTL8811AU]
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
1: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no
2: phy1: Wireless LAN
    Soft blocked: no
    Hard blocked: no
rtl8821au, 5.12.5.2, 5.15.32-v8+, aarch64: installed

syslog:


Apr 10 21:11:12 pi4hyper PackageKit: daemon start
Apr 10 21:11:12 pi4hyper dbus-daemon[373]: [system] Successfully activated service 'org.freedesktop.PackageKit'
Apr 10 21:11:12 pi4hyper systemd[1]: Started PackageKit Daemon.
Apr 10 21:11:16 pi4hyper PackageKit: refresh-cache transaction /133_bccaabac from uid 1000 finished with success after 3573ms
Apr 10 21:11:17 pi4hyper dhcpcd[484]: wlan0: no IPv6 Routers available
Apr 10 21:11:20 pi4hyper kernel: [   31.710836] cam-dummy-reg: disabling
Apr 10 21:11:22 pi4hyper PackageKit: get-updates transaction /134_dccbaabc from uid 1000 finished with success after 5761ms
Apr 10 21:11:26 pi4hyper systemd[1]: systemd-fsckd.service: Succeeded.
Apr 10 21:11:36 pi4hyper systemd[1]: systemd-hostnamed.service: Succeeded.
Apr 10 21:17:01 pi4hyper CRON[1641]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Apr 10 21:22:39 pi4hyper kernel: [  711.185171] usb 1-1.3: new high-speed USB device number 4 using xhci_hcd
Apr 10 21:22:39 pi4hyper kernel: [  711.289837] usb 1-1.3: New USB device found, idVendor=0846, idProduct=9052, bcdDevice= 2.00
Apr 10 21:22:39 pi4hyper kernel: [  711.289869] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Apr 10 21:22:39 pi4hyper kernel: [  711.289882] usb 1-1.3: Product: 802.11ac WLAN Adapter 
Apr 10 21:22:39 pi4hyper kernel: [  711.289894] usb 1-1.3: Manufacturer: Realtek 
Apr 10 21:22:39 pi4hyper kernel: [  711.289904] usb 1-1.3: SerialNumber: 00e04c000001
Apr 10 21:22:39 pi4hyper mtp-probe: checking bus 1, device 4: "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.3"
Apr 10 21:22:39 pi4hyper mtp-probe: bus: 1, device: 4 was not an MTP device
Apr 10 21:22:39 pi4hyper kernel: [  711.358293] 8821au: loading out-of-tree module taints kernel.
Apr 10 21:22:39 pi4hyper kernel: [  711.390273] RTW: module init start
Apr 10 21:22:39 pi4hyper kernel: [  711.390299] RTW: rtl8821au v5.12.5.2-0-g70054197b.20210708_COEX20190509-6d6f
Apr 10 21:22:39 pi4hyper kernel: [  711.390307] RTW: rtl8821au BT-Coex version = COEX20190509-6d6f
Apr 10 21:22:39 pi4hyper kernel: [  711.475969] RTW: HW EFUSE
Apr 10 21:22:39 pi4hyper kernel: [  711.475998] RTW: 0x000: 29 81 00 7C  01 00 01 00  4C 00 04 00  10 00 00 00  
Apr 10 21:22:39 pi4hyper kernel: [  711.476081] RTW: 0x010: 31 31 31 31  31 35 35 35  35 35 35 02  FF FF FF FF  
Apr 10 21:22:39 pi4hyper kernel: [  711.476146] RTW: 0x020: FF FF 23 22  21 20 20 1E  1B 1A 1A 1B  1A 19 18 17  
Apr 10 21:22:39 pi4hyper kernel: [  711.476212] RTW: 0x030: 02 FF FF FF  FF FF 02 FF  FF FF FF FF  FF FF FF FF  
Apr 10 21:22:39 pi4hyper kernel: [  711.476276] RTW: 0x040: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
Apr 10 21:22:39 pi4hyper kernel: [  711.476341] RTW: 0x050: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
Apr 10 21:22:39 pi4hyper kernel: [  711.476406] RTW: 0x060: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
Apr 10 21:22:39 pi4hyper kernel: [  711.476470] RTW: 0x070: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
Apr 10 21:22:39 pi4hyper kernel: [  711.476535] RTW: 0x080: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
Apr 10 21:22:39 pi4hyper kernel: [  711.476599] RTW: 0x090: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
Apr 10 21:22:39 pi4hyper kernel: [  711.476664] RTW: 0x0A0: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
Apr 10 21:22:39 pi4hyper kernel: [  711.476729] RTW: 0x0B0: FF FF FF FF  FF FF FF FF  7F 23 20 00  01 00 FF 08  
Apr 10 21:22:39 pi4hyper kernel: [  711.476793] RTW: 0x0C0: FF 08 00 FF  00 00 00 55  00 FF FF FF  FF FF FF FF  
Apr 10 21:22:39 pi4hyper kernel: [  711.476858] RTW: 0x0D0: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
Apr 10 21:22:39 pi4hyper kernel: [  711.476923] RTW: 0x0E0: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
Apr 10 21:22:39 pi4hyper kernel: [  711.476987] RTW: 0x0F0: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
Apr 10 21:22:39 pi4hyper kernel: [  711.477052] RTW: 0x100: 46 08 52 90  FF FF 03 44  A5 6E 53 0F  4C 0A 03 52  
Apr 10 21:22:39 pi4hyper kernel: [  711.477116] RTW: 0x110: 65 61 6C 74  65 6B 20 18  03 38 30 32  2E 31 31 61  
Apr 10 21:22:39 pi4hyper kernel: [  711.477248] RTW: 0x120: 63 20 57 4C  41 4E 20 41  64 61 70 74  65 72 20 00  
Apr 10 21:22:39 pi4hyper kernel: [  711.477313] RTW: 0x130: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
Apr 10 21:22:39 pi4hyper kernel: [  711.477378] RTW: 0x140: FF FF FF FF  FF FF FF 0F  FF FF FF FF  FF FF FF FF  
Apr 10 21:22:39 pi4hyper kernel: [  711.477442] RTW: 0x150: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
Apr 10 21:22:39 pi4hyper kernel: [  711.477726] RTW: 0x160: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
Apr 10 21:22:39 pi4hyper kernel: [  711.477792] RTW: 0x170: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
Apr 10 21:22:39 pi4hyper kernel: [  711.477857] RTW: 0x180: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
Apr 10 21:22:39 pi4hyper kernel: [  711.477922] RTW: 0x190: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
Apr 10 21:22:39 pi4hyper kernel: [  711.477986] RTW: 0x1A0: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
Apr 10 21:22:39 pi4hyper kernel: [  711.478051] RTW: 0x1B0: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
Apr 10 21:22:39 pi4hyper kernel: [  711.478115] RTW: 0x1C0: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
Apr 10 21:22:39 pi4hyper kernel: [  711.478180] RTW: 0x1D0: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
Apr 10 21:22:39 pi4hyper kernel: [  711.478244] RTW: 0x1E0: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
Apr 10 21:22:39 pi4hyper kernel: [  711.478309] RTW: 0x1F0: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
Apr 10 21:22:39 pi4hyper kernel: [  711.478466] RTW: hal_com_config_channel_plan chplan:0x7F
Apr 10 21:22:39 pi4hyper kernel: [  711.479353] RTW: [RF_PATH] ver_id.RF_TYPE:RF_1T1R
Apr 10 21:22:39 pi4hyper kernel: [  711.479361] RTW: [RF_PATH] HALSPEC's rf_reg_trx_path_bmp:0x11, rf_reg_path_avail_num:1, max_tx_cnt:1
Apr 10 21:22:39 pi4hyper kernel: [  711.479367] RTW: [RF_PATH] PG's trx_path_bmp:0x00, max_tx_cnt:0
Apr 10 21:22:39 pi4hyper kernel: [  711.479372] RTW: [RF_PATH] Registry's trx_path_bmp:0x00, tx_path_lmt:0, rx_path_lmt:0
Apr 10 21:22:39 pi4hyper kernel: [  711.479377] RTW: [RF_PATH] HALDATA's trx_path_bmp:0x11, max_tx_cnt:1
Apr 10 21:22:39 pi4hyper kernel: [  711.479381] RTW: [RF_PATH] HALDATA's rf_type:RF_1T1R, NumTotalRFPath:1
Apr 10 21:22:39 pi4hyper kernel: [  711.479387] RTW: [TRX_Nss] HALSPEC - tx_nss:1, rx_nss:1
Apr 10 21:22:39 pi4hyper kernel: [  711.479392] RTW: [TRX_Nss] Registry - tx_nss:0, rx_nss:0
Apr 10 21:22:39 pi4hyper kernel: [  711.479397] RTW: [TRX_Nss] HALDATA - tx_nss:1, rx_nss:1
Apr 10 21:22:39 pi4hyper kernel: [  711.479403] RTW: txpath=0x1, rxpath=0x1
Apr 10 21:22:39 pi4hyper kernel: [  711.479408] RTW: txpath_1ss:0x1, num:1
Apr 10 21:22:39 pi4hyper kernel: [  711.480247] RTW: rtw_regsty_chk_target_tx_power_valid return _FALSE for band:0, path:0, rs:0, t:-1
Apr 10 21:22:39 pi4hyper kernel: [  711.482441] RTW: rtw_ndev_init(wlan1) if1 mac_addr=44:a5:6e:53:0f:4c
Apr 10 21:22:39 pi4hyper kernel: [  711.486174] usbcore: registered new interface driver rtl8821au
Apr 10 21:22:39 pi4hyper kernel: [  711.486197] RTW: module init ret=0
Apr 10 21:22:39 pi4hyper systemd[1]: Starting Load/Save RF Kill Switch Status...
Apr 10 21:22:39 pi4hyper mtp-probe: checking bus 1, device 4: "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.3"
Apr 10 21:22:39 pi4hyper mtp-probe: bus: 1, device: 4 was not an MTP device
Apr 10 21:22:39 pi4hyper systemd-udevd[1992]: Using default interface naming scheme 'v247'.
Apr 10 21:22:40 pi4hyper systemd[1]: Started Load/Save RF Kill Switch Status.
Apr 10 21:22:40 pi4hyper systemd[1]: Found device A6100 AC600 DB Wireless Adapter [Realtek RTL8811AU].
Apr 10 21:22:40 pi4hyper systemd[1]: Started ifup for wlan1.
Apr 10 21:22:45 pi4hyper systemd[1]: systemd-rfkill.service: Succeeded.
Apr 10 21:23:40 pi4hyper systemd-udevd[170]: mon1: Worker [2015] processing SEQNUM=1879 is taking a long time
Apr 10 21:24:55 pi4hyper kernel: [  846.827010] INFO: task systemd-udevd:2015 blocked for more than 120 seconds.
Apr 10 21:24:55 pi4hyper kernel: [  846.827048]       Tainted: G         C O      5.15.32-v8+ #1538
Apr 10 21:24:55 pi4hyper kernel: [  846.827061] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Apr 10 21:24:55 pi4hyper kernel: [  846.827073] task:systemd-udevd   state:D stack:    0 pid: 2015 ppid:   170 flags:0x00000800
Apr 10 21:24:55 pi4hyper kernel: [  846.827106] Call trace:
Apr 10 21:24:55 pi4hyper kernel: [  846.827116]  __switch_to+0x114/0x1c8
Apr 10 21:24:55 pi4hyper kernel: [  846.827151]  __schedule+0x30c/0x8e8
Apr 10 21:24:55 pi4hyper kernel: [  846.827174]  schedule+0x48/0x100
Apr 10 21:24:55 pi4hyper kernel: [  846.827193]  schedule_preempt_disabled+0x20/0x38
Apr 10 21:24:55 pi4hyper kernel: [  846.827213]  __mutex_lock.isra.15+0x2a4/0x5b0
Apr 10 21:24:55 pi4hyper kernel: [  846.827232]  __mutex_lock_slowpath+0x1c/0x28
Apr 10 21:24:55 pi4hyper kernel: [  846.827247]  mutex_lock+0x40/0x58
Apr 10 21:24:55 pi4hyper kernel: [  846.827261]  rtnl_lock+0x20/0x30
Apr 10 21:24:55 pi4hyper kernel: [  846.827281]  dev_ioctl+0x1f4/0x400
Apr 10 21:24:55 pi4hyper kernel: [  846.827297]  sock_do_ioctl+0xbc/0x100
Apr 10 21:24:55 pi4hyper kernel: [  846.827313]  sock_ioctl+0x2dc/0x3c0
Apr 10 21:24:55 pi4hyper kernel: [  846.827340]  __arm64_sys_ioctl+0xb0/0xf0
Apr 10 21:24:55 pi4hyper kernel: [  846.827368]  invoke_syscall+0x4c/0x110
Apr 10 21:24:55 pi4hyper kernel: [  846.827387]  el0_svc_common.constprop.3+0x98/0x120
Apr 10 21:24:55 pi4hyper kernel: [  846.827405]  do_el0_svc+0x2c/0x90
Apr 10 21:24:55 pi4hyper kernel: [  846.827422]  el0_svc+0x24/0x60
Apr 10 21:24:55 pi4hyper kernel: [  846.827438]  el0t_64_sync_handler+0x90/0xb8
Apr 10 21:24:55 pi4hyper kernel: [  846.827455]  el0t_64_sync+0x1a0/0x1a4
Apr 10 21:24:55 pi4hyper kernel: [  846.827473] INFO: task iw:2020 blocked for more than 120 seconds.
Apr 10 21:24:55 pi4hyper kernel: [  846.827488]       Tainted: G         C O      5.15.32-v8+ #1538
Apr 10 21:24:55 pi4hyper kernel: [  846.827500] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Apr 10 21:24:55 pi4hyper kernel: [  846.827510] task:iw              state:D stack:    0 pid: 2020 ppid:  2019 flags:0x00000008
Apr 10 21:24:55 pi4hyper kernel: [  846.827536] Call trace:
Apr 10 21:24:55 pi4hyper kernel: [  846.827545]  __switch_to+0x114/0x1c8
Apr 10 21:24:55 pi4hyper kernel: [  846.827565]  __schedule+0x30c/0x8e8
Apr 10 21:24:55 pi4hyper kernel: [  846.827584]  schedule+0x48/0x100
Apr 10 21:24:55 pi4hyper kernel: [  846.827601]  schedule_preempt_disabled+0x20/0x38
Apr 10 21:24:55 pi4hyper kernel: [  846.827620]  __mutex_lock.isra.15+0x2a4/0x5b0
Apr 10 21:24:55 pi4hyper kernel: [  846.827640]  __mutex_lock_slowpath+0x1c/0x28
Apr 10 21:24:55 pi4hyper kernel: [  846.827653]  mutex_lock+0x40/0x58
Apr 10 21:24:55 pi4hyper kernel: [  846.827666]  cfg80211_netdev_notifier_call+0x1f8/0x5a8 [cfg80211]
Apr 10 21:24:55 pi4hyper kernel: [  846.827882]  raw_notifier_call_chain+0x5c/0x80
Apr 10 21:24:55 pi4hyper kernel: [  846.827902]  call_netdevice_notifiers_info+0x60/0xb0
Apr 10 21:24:55 pi4hyper kernel: [  846.827920]  register_netdevice+0x388/0x400
Apr 10 21:24:55 pi4hyper kernel: [  846.827936]  cfg80211_rtw_add_virtual_intf+0x1e4/0x47c [8821au]
Apr 10 21:24:55 pi4hyper kernel: [  846.828269]  nl80211_new_interface+0x15c/0x448 [cfg80211]
Apr 10 21:24:55 pi4hyper kernel: [  846.828449]  genl_family_rcv_msg_doit.isra.15+0x114/0x158
Apr 10 21:24:55 pi4hyper kernel: [  846.828469]  genl_rcv_msg+0xf8/0x1e0
Apr 10 21:24:55 pi4hyper kernel: [  846.828485]  netlink_rcv_skb+0x64/0x128
Apr 10 21:24:55 pi4hyper kernel: [  846.828500]  genl_rcv+0x40/0x58
Apr 10 21:24:55 pi4hyper kernel: [  846.828515]  netlink_unicast+0x1c0/0x280
Apr 10 21:24:55 pi4hyper kernel: [  846.828530]  netlink_sendmsg+0x1d0/0x418
Apr 10 21:24:55 pi4hyper kernel: [  846.828545]  sock_sendmsg+0x54/0x60
Apr 10 21:24:55 pi4hyper kernel: [  846.828561]  ____sys_sendmsg+0x260/0x2a0
Apr 10 21:24:55 pi4hyper kernel: [  846.828576]  ___sys_sendmsg+0x8c/0xd0
Apr 10 21:24:55 pi4hyper kernel: [  846.828591]  __sys_sendmsg+0x74/0xc8
Apr 10 21:24:55 pi4hyper kernel: [  846.828607]  __arm64_sys_sendmsg+0x2c/0x38
Apr 10 21:24:55 pi4hyper kernel: [  846.828622]  invoke_syscall+0x4c/0x110
Apr 10 21:24:55 pi4hyper kernel: [  846.828640]  el0_svc_common.constprop.3+0xfc/0x120
Apr 10 21:24:55 pi4hyper kernel: [  846.828658]  do_el0_svc+0x2c/0x90
Apr 10 21:24:55 pi4hyper kernel: [  846.828675]  el0_svc+0x24/0x60
Apr 10 21:24:55 pi4hyper kernel: [  846.828693]  el0t_64_sync_handler+0x90/0xb8
Apr 10 21:24:55 pi4hyper kernel: [  846.828710]  el0t_64_sync+0x1a0/0x1a4
Apr 10 21:25:40 pi4hyper systemd-udevd[170]: mon1: Worker [2015] processing SEQNUM=1879 killed
morrownr commented 2 years ago

Hi @Musiker

I just happened to be testing the new RasPiOS 64 bit on a Pi4B. So I followed the Installation Steps here in the README.md and I could find no problem. In fact this message is going through my rtl8811au usb adapter acting as an AP.

So, same hardware and same OS, different result.

Can I get you to post the Installation Steps that you used?

Also, did you reboot after driver installation was completed?

Regards

Musiker commented 2 years ago

Hi Thanks for the swift reply - I followed the steps in the readme to the point: 1) installed all prerequisites. 2) ran the script to change the arch to ARM64 (Also verified it in Makefile) 3) Used the install script - No errors at all. had the behavior above, so I uninstalled and tried building with a few different options without luck - And yes I rebooted after each installation. If I plugged in the adapter before boot - The OS did not seem to boot up at all (Atleast I did not wait long enough)

Since it seems to work for you I will hunt the issue by looking at my RPI install. I thought my setup is pretty much out of the box (Some i2c control and wlan0 enabled) - I think I'll try to strip it out and see if I can get it to work at all. Maybe I should even try to do a clean install of the RPI OS.

morrownr commented 2 years ago

Hi @Musiker

Interesting. I rechecked to make sure your device ID is in the driver. Secure boot cannot be an issue because Pi's don't support it. One comment did get my attention:

If I plugged in the adapter before boot - The OS did not seem to boot up at all (Atleast I did not wait long enough)

The first thing that pops into mind here is maybe you are trying to pull too much power via the USB subsystem. Tell me everything you have plugged into USB ports and whether you have a power hub in use. The Pi4B USB subsystem can only supply up to 1200 ma of power.

Using another sd card with a fresh installation to test might be a good idea.

Regards

morrownr commented 2 years ago

Follow on:

ID 152d:0562 JMicron Technology Corp. / JMicron USA Technology Corp. JMS567 SATA 6Gb/s bridge

Somehow I skipped over this. Are you running an ssd directly from the Pi4B? If so, this single device could be taking nearly all available power, especially during boot. If you run an sdd, you really need to run it from an external powered usb hub. You need to be careful exactly which power hub you get a most do not run well with Pi's. I can suggest one if you want.

Musiker commented 2 years ago

Thanks again, You are correct I did have a 256GB SSD (M2) plugged in - I did try without it before reporting and just did again to be sure.. Still the same problem in syslog and when I try to execute e.g. ifconfig the command never returrns or show the state of the network devices - Without the A6100 plugged in it works as expected. The PI I tested on sofar also have a Thermal Camera and a 4" HyperPixel display attached, maybe one of these is causing some problem on the supply..

I'll I'll try on on another RPI4 - That is completly barebones and with a fresh install of RPIOS64 as well.. Probably not have time to do that until later this week - I'll update my findings as soon as I get time to test..

morrownr commented 2 years ago

Yes, testing on another Pi that is running from a sd card is a good idea. I have a little in-line power meter that allows me to test how much power each device uses. I also use a powered hub:

Transcend USB 3.0 4-Port Hub TS-HUB3K

I also lean toward using Mediatek based usb wifi adapters instead of Realtek based as the Mediatek based adapters use less power:

https://github.com/morrownr/USB-WiFi

Hopefully the information I have provided helps.

Regards

morrownr commented 2 years ago

I''m going to mark this issue solved for now as I am pretty sure your issue is related to trying to pull too much power from the usb subsystem. Please let me know how it goes and if I need to unmark this issue as solved, I will do so.

Regards

Musiker commented 2 years ago

Finally got around testing on a new RPI4 - without the HyperPixel display mounted and a clean install of the 64 Bit image and it worked without problems. So it could be the total powerdraw or some difference in installed drivers/sotware - Atleast now I have a working system to compare with. Thanks for the help!