[Solved] Bananapi M1 doesn't boot when Wireless Desktop Reciever is plugged in

[Elric]

Armbianmonitor:

http://ix.io/3vLE

I supose the armbianmonitor output doesn't help much. But here is an output from serial console:

 

3 times reseting before....

 

resetting ...

U-Boot SPL 2021.04-armbian (May 06 2021 - 20:01:01 +0000)
DRAM: 1024 MiB
CPU: 912000000Hz, AXI/AHB/APB: 3/2/2
Trying to boot from MMC1

U-Boot 2021.04-armbian (May 06 2021 - 20:01:01 +0000) Allwinner Technology

CPU:   Allwinner A20 (SUN7I)
Model: LeMaker Banana Pi
I2C:   ready
DRAM:  1 GiB
MMC:   mmc@1c0f000: 0
Loading Environment from FAT... Unable to use mmc 0:1... HDMI connected: Setting up a 1920x1080 hdmi console (overscan 0x0)
In:    serial
Out:   vga
Err:   vga
Net:   eth0: ethernet@1c50000
230454 bytes read in 28 ms (7.8 MiB/s)
starting USB...
Bus usb@1c14000: USB EHCI 1.00
Bus usb@1c14400: USB OHCI 1.0
Bus usb@1c1c000: USB EHCI 1.00
Bus usb@1c1c400: USB OHCI 1.0
scanning bus usb@1c14000 for devices... 1 USB Device(s) found
scanning bus usb@1c14400 for devices... 2 USB Device(s) found
scanning bus usb@1c1c000 for devices... 1 USB Device(s) found
scanning bus usb@1c1c400 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Autoboot in 1 seconds, press <Space> to stop
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
3967 bytes read in 7 ms (552.7 KiB/s)
## Executing script at 43100000
U-boot loaded from SD
Boot script loaded from mmc
203 bytes read in 6 ms (32.2 KiB/s)
11526673 bytes read in 1290 ms (8.5 MiB/s)
7975912 bytes read in 751 ms (10.1 MiB/s)
Found mainline kernel configuration
43645 bytes read in 29 ms (1.4 MiB/s)
5532 bytes read in 27 ms (199.2 KiB/s)
Applying kernel provided DT fixup script (sun7i-a20-fixup.scr)
## Executing script at 45000000
## Loading init Ramdisk from Legacy Image at 43300000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    11526609 Bytes = 11 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 43000000
   Booting using the fdt blob at 0x43000000
data abort
pc : [<7ef9673c>]          lr : [<00000011>]
reloc pc : [<4a01373c>]    lr : [<cb07d011>]
sp : 7af57c18  ip : 7efde6ec     fp : 7efde6cc
r10: 00000020  r9 : 7af62ec0     r8 : 7efeab8c
r7 : 6c616972  r6 : 00000010     r5 : e75b616a  r4 : 7af9f7f0
r3 : 7af9f7f8  r2 : 7af9f7e8     r1 : 7afa90b8  r0 : 00000019
Flags: nzCv  IRQs off  FIQs off  Mode SVC_32 (T)
Code: d005 f027 0501 441d (686d) 07ed
Resetting CPU ...

resetting ...

U-Boot SPL 2021.04-armbian (May 06 2021 - 20:01:01 +0000)
DRAM: 1024 MiB
CPU: 912000000Hz, AXI/AHB/APB: 3/2/2
Trying to boot from MMC1

U-Boot 2021.04-armbian (May 06 2021 - 20:01:01 +0000) Allwinner Technology

CPU:   Allwinner A20 (SUN7I)
Model: LeMaker Banana Pi
I2C:   ready
DRAM:  1 GiB
MMC:   mmc@1c0f000: 0
Loading Environment from FAT... Unable to use mmc 0:1... HDMI connected: Setting up a 1920x1080 hdmi console (overscan 0x0)
In:    serial
Out:   vga
Err:   vga
Net:   eth0: ethernet@1c50000
230454 bytes read in 28 ms (7.8 MiB/s)
starting USB...
Bus usb@1c14000: USB EHCI 1.00
Bus usb@1c14400: USB OHCI 1.0
Bus usb@1c1c000: USB EHCI 1.00
Bus usb@1c1c400: USB OHCI 1.0
scanning bus usb@1c14000 for devices... 1 USB Device(s) found
scanning bus usb@1c14400 for devices... 2 USB Device(s) found
scanning bus usb@1c1c000 for devices... 1 USB Device(s) found
scanning bus usb@1c1c400 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Autoboot in 1 seconds, press <Space> to stop
ERROR:  USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did
not provide a handshake (OUT) (5)
ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did
not provide a handshake (OUT) (5)
ERROR:  USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did
not provide a handshake (OUT) (5)
ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did
not provide a handshake (OUT) (5)
ERROR:  USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did
not provide a handshake (OUT) (5)
ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did
not provide a handshake (OUT) (5)
ERROR:  USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did
not provide a handshake (OUT) (5)
ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did
not provide a handshake (OUT) (5)
ERROR:  USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did
not provide a handshake (OUT) (5)
ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did
not provide a handshake (OUT) (5)
ERROR:  USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did
not provide a handshake (OUT) (5)
ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did
not provide a handshake (OUT) (5)
ERROR:  USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did
not provide a handshake (OUT) (5)
ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did
not provide a handshake (OUT) (5)
ERROR:  USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did
not provide a handshake (OUT) (5)
ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did
not provide a handshake (OUT) (5)
ERROR:  USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did
not provide a handshake (OUT) (5)
ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did
not provide a handshake (OUT) (5)
ERROR:  USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did
not provide a handshake (OUT) (5)
ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did
not provide a handshake (OUT) (5)
ERROR:  USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did
not provide a handshake (OUT) (5)
ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did
not provide a handshake (OUT) (5)
ERROR:  USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did
not provide a handshake (OUT) (5)
ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did
not provide a handshake (OUT) (5)
ERROR:  USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did
not provide a handshake (OUT) (5)
ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did
not provide a handshake (OUT) (5)
ERROR:  USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did
not provide a handshake (OUT) (5)
ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did
not provide a handshake (OUT) (5)
ERROR:  USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did
not provide a handshake (OUT) (5)
ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did
not provide a handshake (OUT) (5)
switch to partitions #0, OK
mmc0 is current device
ERROR:  USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did
not provide a handshake (OUT) (5)
ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did
not provide a handshake (OUT) (5)
Scanning mmc 0:1...
ERROR:  USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did
not provide a handshake (OUT) (5)
ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did
not provide a handshake (OUT) (5)
ERROR:  USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did
not provide a handshake (OUT) (5)
ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did
not provide a handshake (OUT) (5)
Found U-Boot script /boot/boot.scr
3967 bytes read in 7 ms (552.7 KiB/s)
## Executing script at 43100000
U-boot loaded from SD
Boot script loaded from mmc
203 bytes read in 6 ms (32.2 KiB/s)
11526673 bytes read in 1189 ms (9.2 MiB/s)
7975912 bytes read in 703 ms (10.8 MiB/s)
Found mainline kernel configuration
43645 bytes read in 29 ms (1.4 MiB/s)
5532 bytes read in 30 ms (179.7 KiB/s)
Applying kernel provided DT fixup script (sun7i-a20-fixup.scr)
## Executing script at 45000000
## Loading init Ramdisk from Legacy Image at 43300000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    11526609 Bytes = 11 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 43000000
   Booting using the fdt blob at 0x43000000
data abort
pc : [<7ef961a8>]          lr : [<7ef968b5>]
reloc pc : [<4a0131a8>]    lr : [<4a0138b5>]
sp : 7af57c08  ip : 006c6168     fp : 7efde6cc
r10: 00000020  r9 : 7af62ec0     r8 : 7efeab8c
r7 : 72657370  r6 : 7b6644a8     r5 : 614e6e65  r4 : 7efde6cc
r3 : 7af9e350  r2 : 00000000     r1 : 72d1d4c8  r0 : 6b6f545f
Flags: Nzcv  IRQs off  FIQs off  Mode SVC_32 (T)
Code: e7d1 2201 e7cf 68f5 (60c5) 60a8
Resetting CPU ...

resetting ...

U-Boot SPL 2021.04-armbian (May 06 2021 - 20:01:01 +0000)
DRAM: 1024 MiB
CPU: 912000000Hz, AXI/AHB/APB: 3/2/2
Trying to boot from MMC1

U-Boot 2021.04-armbian (May 06 2021 - 20:01:01 +0000) Allwinner Technology

CPU:   Allwinner A20 (SUN7I)
Model: LeMaker Banana Pi
I2C:   ready
DRAM:  1 GiB
MMC:   mmc@1c0f000: 0
Loading Environment from FAT... Unable to use mmc 0:1... HDMI connected: Setting up a 1920x1080 hdmi console (overscan 0x0)
In:    serial
Out:   vga
Err:   vga
Net:   eth0: ethernet@1c50000
230454 bytes read in 28 ms (7.8 MiB/s)
starting USB...
Bus usb@1c14000: USB EHCI 1.00
Bus usb@1c14400: USB OHCI 1.0
Bus usb@1c1c000: USB EHCI 1.00
Bus usb@1c1c400: USB OHCI 1.0
scanning bus usb@1c14000 for devices... 1 USB Device(s) found
scanning bus usb@1c14400 for devices... 1 USB Device(s) found
scanning bus usb@1c1c000 for devices... 1 USB Device(s) found
scanning bus usb@1c1c400 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Autoboot in 1 seconds, press <Space> to stop
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
3967 bytes read in 7 ms (552.7 KiB/s)
## Executing script at 43100000
U-boot loaded from SD
Boot script loaded from mmc
203 bytes read in 6 ms (32.2 KiB/s)
11526673 bytes read in 1188 ms (9.3 MiB/s)
7975912 bytes read in 705 ms (10.8 MiB/s)
Found mainline kernel configuration
43645 bytes read in 29 ms (1.4 MiB/s)
5532 bytes read in 30 ms (179.7 KiB/s)
Applying kernel provided DT fixup script (sun7i-a20-fixup.scr)
## Executing script at 45000000
## Loading init Ramdisk from Legacy Image at 43300000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    11526609 Bytes = 11 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 43000000
   Booting using the fdt blob at 0x43000000
EHCI failed to shut down host controller.
   Loading Ramdisk to 49501000, end 49fff1d1 ... OK
   Loading Device Tree to 4948d000, end 49500fff ... OK

Starting kernel ...

[   18.912230] phy id_det change to device

 

during the second boot (here in the log)  I unplugged the Unifying Reciever

The next boot (without the reciever plugged in) brings the system up and running. After kernel started you may plug the reciever back in.

 

lsusb-output:

Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub 

 

I did some investigation, and tried buster instead of focal. No difference. 

 

But I have another pi running:

 

root@pipyload:~# uname -a
Linux pipyload 5.4.20-sunxi #20.02.1 SMP Mon Feb 17 02:09:41 CET 2020 armv7l GNU/Linux
root@pipyload:~# lsusb
Bus 004 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

 

booting this pi is workling fine. Since years...

 

So it seems to me, that the problem is somewhere in the newer kernel.

Does someone has a glue what to do? Perhaps disabling usb during u-boot? 

[Elric]

Downloaded new image Armbian_21.08.1_Bananapi_buster_current_5.10.60.img today, flashed it to sdcard and started with a Unifying reciever plugged-in. Everything was fine, kernel starts without any troubles. Thanks for providing a new installation image!

[Elric]

to shorten the issue:

 

Banana Pi M1 hangs on endless boot when a keyboard / mouse reciever is plugged in. Tried with an old Logitech DZL-C-U0006 (MK 250 Desktop), 2 different Unifying reciever (K400+ & K330) and Microsoft 2.4GHz Transceiver 7.0 (MS Wireless Keyboard 3000 v2.0). The result having one of them plugged in while booting is the same:

 

U-Boot SPL 2021.04-armbian (May 06 2021 - 20:01:01 +0000)
DRAM: 1024 MiB
CPU: 912000000Hz, AXI/AHB/APB: 3/2/2
Trying to boot from MMC1

U-Boot 2021.04-armbian (May 06 2021 - 20:01:01 +0000) Allwinner Technology

CPU:   Allwinner A20 (SUN7I)
Model: LeMaker Banana Pi
I2C:   ready
DRAM:  1 GiB
MMC:   mmc@1c0f000: 0
Loading Environment from FAT... Unable to use mmc 0:1... HDMI connected: Setting up a 1920x1080 hdmi console (overscan 0x0)
In:    serial
Out:   vga
Err:   vga
Net:   eth0: ethernet@1c50000
230454 bytes read in 32 ms (6.9 MiB/s)
starting USB...
Bus usb@1c14000: USB EHCI 1.00
Bus usb@1c14400: USB OHCI 1.0
Bus usb@1c1c000: USB EHCI 1.00
Bus usb@1c1c400: USB OHCI 1.0
scanning bus usb@1c14000 for devices... 1 USB Device(s) found
scanning bus usb@1c14400 for devices... 1 USB Device(s) found
scanning bus usb@1c1c000 for devices... 1 USB Device(s) found
scanning bus usb@1c1c400 for devices... 2 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Autoboot in 1 seconds, press <Space> to stop
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
3967 bytes read in 8 ms (483.4 KiB/s)
## Executing script at 43100000
U-boot loaded from SD
Boot script loaded from mmc
203 bytes read in 7 ms (28.3 KiB/s)
11526673 bytes read in 1566 ms (7 MiB/s)
7975912 bytes read in 980 ms (7.8 MiB/s)
Found mainline kernel configuration
43645 bytes read in 31 ms (1.3 MiB/s)
5532 bytes read in 36 ms (149.4 KiB/s)
Applying kernel provided DT fixup script (sun7i-a20-fixup.scr)
## Executing script at 45000000
## Loading init Ramdisk from Legacy Image at 43300000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    11526609 Bytes = 11 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 43000000
   Booting using the fdt blob at 0x43000000
EHCI failed to shut down host controller.
data abort
pc : [<7ef9673c>]          lr : [<00000011>]
reloc pc : [<4a01373c>]    lr : [<cb07d011>]
sp : 7af57c18  ip : 7f817000     fp : 7efde6cc
r10: 00000020  r9 : 7af62ec0     r8 : 7efeab8c
r7 : 6c616972  r6 : 00000010     r5 : e75b5d92  r4 : 7af9f418
r3 : 7af9f420  r2 : 7af9f410     r1 : 7afa91e0  r0 : 00000019
Flags: nzCv  IRQs off  FIQs off  Mode SVC_32 (T)
Code: d005 f027 0501 441d (686d) 07ed
Resetting CPU ...

resetting ...

 

I'm aware, that it is faulty hardware. I unpacked my last Banani Pi M1 (from a Renkforce Advanced Set, which I kept in spare for testing for hardware faults) switched sdcard, monitor cable and receiver, plugged power in and ended up up in the same boot loop.
As I wrote before: booting without any reciever works fine and it's a problem which occurs in new armbian 5.10.xx NOT in 5.4.20.

I understand that this issue is not on top, due the old hardware and my recommendation having mouse and keyboard plugged in. It would be great, if someone could help with a workaround. Is there something to turn off usb during u-boot? I (and most of the Banana Pi user) have no use for booting via usb, when there is a sata hdd installed.

[guidol]

Reinstalled my BP-M1 today with a fresh compiled bullseye kernel 5.12.x and updated to kernel 5.13.10

(for testing pihole under bullseye with kernel 5.13.10)

 

While the BPi1-M1 was running I inserted the Logitech Unifying Receiver and got:
 

Spoiler

[ 1805.162178] usb 5-1: new full-speed USB device number 2 using ohci-platform
[ 1805.395187] usb 5-1: New USB device found, idVendor=046d, idProduct=c52b, bcdDevice=12.10
[ 1805.395235] usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 1805.395257] usb 5-1: Product: USB Receiver
[ 1805.395274] usb 5-1: Manufacturer: Logitech
[ 1805.411887] input: Logitech USB Receiver as /devices/platform/soc/1c1c400.usb/usb5/5-1/5-1:1.0/0003:046D:C52B.0001/input/input2
[ 1805.471824] hid-generic 0003:046D:C52B.0001: input,hidraw0: USB HID v1.11 Keyboard [Logitech USB Receiver] on usb-1c1c400.usb-1/input0
[ 1805.482433] input: Logitech USB Receiver Mouse as /devices/platform/soc/1c1c400.usb/usb5/5-1/5-1:1.1/0003:046D:C52B.0002/input/input3
[ 1805.483411] input: Logitech USB Receiver Consumer Control as /devices/platform/soc/1c1c400.usb/usb5/5-1/5-1:1.1/0003:046D:C52B.0002/input/input4
[ 1805.543061] input: Logitech USB Receiver System Control as /devices/platform/soc/1c1c400.usb/usb5/5-1/5-1:1.1/0003:046D:C52B.0002/input/input5
[ 1805.544242] hid-generic 0003:046D:C52B.0002: input,hiddev0,hidraw1: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-1c1c400.usb-1/input1
[ 1805.560583] hid-generic 0003:046D:C52B.0003: hiddev1,hidraw2: USB HID v1.11 Device [Logitech USB Receiver] on usb-1c1c400.usb-1/input2
[ 1805.841494] logitech-djreceiver 0003:046D:C52B.0003: hiddev0,hidraw0: USB HID v1.11 Device [Logitech USB Receiver] on usb-1c1c400.usb-1/input2
[ 1805.966439] input: Logitech Wireless Device PID:4004 Keyboard as /devices/platform/soc/1c1c400.usb/usb5/5-1/5-1:1.2/0003:046D:C52B.0003/0003:046D:4004.0004/input/input7
[ 1805.982563] hid-generic 0003:046D:4004.0004: input,hidraw1: USB HID v1.11 Keyboard [Logitech Wireless Device PID:4004] on usb-1c1c400.usb-1/input2:1
[ 1806.003573] input: Logitech Wireless Device PID:4024 Keyboard as /devices/platform/soc/1c1c400.usb/usb5/5-1/5-1:1.2/0003:046D:C52B.0003/0003:046D:4024.0005/input/input11
[ 1806.014717] input: Logitech Wireless Device PID:4024 Mouse as /devices/platform/soc/1c1c400.usb/usb5/5-1/5-1:1.2/0003:046D:C52B.0003/0003:046D:4024.0005/input/input12
[ 1806.020657] hid-generic 0003:046D:4024.0005: input,hidraw2: USB HID v1.11 Keyboard [Logitech Wireless Device PID:4024] on usb-1c1c400.usb-1/input2:2
[ 1806.404167] input: Logitech K360 as /devices/platform/soc/1c1c400.usb/usb5/5-1/5-1:1.2/0003:046D:C52B.0003/0003:046D:4004.0004/input/input16
[ 1806.405600] logitech-hidpp-device 0003:046D:4004.0004: input,hidraw1: USB HID v1.11 Keyboard [Logitech K360] on usb-1c1c400.usb-1/input2:1
[ 1806.502419] input: Logitech K400 as /devices/platform/soc/1c1c400.usb/usb5/5-1/5-1:1.2/0003:046D:C52B.0003/0003:046D:4024.0005/input/input17
[ 1806.504051] logitech-hidpp-device 0003:046D:4024.0005: input,hidraw2: USB HID v1.11 Keyboard [Logitech K400] on usb-1c1c400.usb-1/input2:2

 

 

then I rebooted and got no problem - the BPi-M1 did reboot and start the system without problems:
System diagnosis information has been uploaded to http://ix.io/3w0L

Spoiler

[ 10.423392] usb 5-1: New USB device found, idVendor=046d, idProduct=c52b, bcdDevice=12.10 [ 10.423433] usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 10.423446] usb 5-1: Product: USB Receiver [ 10.423456] usb 5-1: Manufacturer: Logitech [ 10.435594] input: Logitech USB Receiver as /devices/platform/soc/1c1c400.usb/usb5/5-1/5-1:1.0/0003:046D:C52B.0001/input/input2 [ 10.452032] systemd[1]: Finished Armbian ZRAM config. [ 10.460524] systemd[1]: Starting Armbian memory supported logging... [ 10.498794] hid-generic 0003:046D:C52B.0001: input,hidraw0: USB HID v1.11 Keyboard [Logitech USB Receiver] on usb-1c1c400.usb-1/input0 [ 10.507232] input: Logitech USB Receiver Mouse as /devices/platform/soc/1c1c400.usb/usb5/5-1/5-1:1.1/0003:046D:C52B.0002/input/input3 [ 10.507920] input: Logitech USB Receiver Consumer Control as /devices/platform/soc/1c1c400.usb/usb5/5-1/5-1:1.1/0003:046D:C52B.0002/input/input4 [ 10.566966] input: Logitech USB Receiver System Control as /devices/platform/soc/1c1c400.usb/usb5/5-1/5-1:1.1/0003:046D:C52B.0002/input/input5 [ 10.576898] hid-generic 0003:046D:C52B.0002: input,hiddev0,hidraw1: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-1c1c400.usb-1/input1 [ 10.584084] hid-generic 0003:046D:C52B.0003: hiddev1,hidraw2: USB HID v1.11 Device [Logitech USB Receiver] on usb-1c1c400.usb-1/input2 [ 10.625073] EXT4-fs (zram1): mounted filesystem without journal. Opts: discard. Quota mode: none. [ 10.625166] ext4 filesystem being mounted at /var/log supports timestamps until 2038 (0x7fffffff) [ 10.895793] logitech-djreceiver 0003:046D:C52B.0003: hiddev0,hidraw0: USB HID v1.11 Device [Logitech USB Receiver] on usb-1c1c400.usb-1/input2 [ 11.048727] input: Logitech Wireless Device PID:4004 Keyboard as /devices/platform/soc/1c1c400.usb/usb5/5-1/5-1:1.2/0003:046D:C52B.0003/0003:046D:4004.0004/input/input7 [ 11.063912] hid-generic 0003:046D:4004.0004: input,hidraw1: USB HID v1.11 Keyboard [Logitech Wireless Device PID:4004] on usb-1c1c400.usb-1/input2:1 [ 11.068167] input: Logitech Wireless Device PID:4024 Keyboard as /devices/platform/soc/1c1c400.usb/usb5/5-1/5-1:1.2/0003:046D:C52B.0003/0003:046D:4024.0005/input/input11 [ 11.068919] input: Logitech Wireless Device PID:4024 Mouse as /devices/platform/soc/1c1c400.usb/usb5/5-1/5-1:1.2/0003:046D:C52B.0003/0003:046D:4024.0005/input/input12 [ 11.069481] hid-generic 0003:046D:4024.0005: input,hidraw2: USB HID v1.11 Keyboard [Logitech Wireless Device PID:4024] on usb-1c1c400.usb-1/input2:2 [ 11.518685] input: Logitech K360 as /devices/platform/soc/1c1c400.usb/usb5/5-1/5-1:1.2/0003:046D:C52B.0003/0003:046D:4004.0004/input/input16 [ 11.526640] logitech-hidpp-device 0003:046D:4004.0004: input,hidraw1: USB HID v1.11 Keyboard [Logitech K360] on usb-1c1c400.usb-1/input2:1 [ 11.628358] input: Logitech K400 as /devices/platform/soc/1c1c400.usb/usb5/5-1/5-1:1.2/0003:046D:C52B.0003/0003:046D:4024.0005/input/input17 [ 11.629659] logitech-hidpp-device 0003:046D:4024.0005: input,hidraw2: USB HID v1.11 Keyboard [Logitech K400] on usb-1c1c400.usb-1/input2:2

 

[Elric]

Thank you guidol for your answer. So, I'm not so deep into linux, and I would prefer stay on a LTS - kernel. I suppose 5.10 is LTS, 5.12 or 5.13 isn't.
If you want do me a favour, get the actual download image here from this site (5.10 focal or buster) flash it to sdcard, insert sd and reciever to you M1 pi and start it.
If you recieve other results than I did, let me know. Thank you

 

[guidol]

1 hour ago, Elric said:

If you want do me a favour, get the actual download image here from this site (5.10 focal or buster) flash it to sdcard, insert sd and reciever to you M1 pi and start it.

Sorry - at this time I got not second free "BIG" SDCard available for the BPI-M1
Here in Turkey the hardware-supply isnt as good as in other countrys (like Germany).
Mostly here are only very cheap brand for cards which have a short life

[Elric]

No problem, I found an additional sdcard. Flashed actual 5.10. Image to sd. Started BPi-M1 with this "brand new" sdcard and a plugged in receiver. Ended up in the same boot loop, as before with a full configured system.

If you don't have this problem with a 5.12 or 5.13, I suppose the problem (or bug) is fixed in the newer kernels, but the patch isn't backported to LTS kernel.

@guidol Thanks again for reading and helping. Do you have an idea how to turn-off usb in u-boot as workaround?

[guidol]

4 hours ago, Elric said:

 Thanks again for reading and helping. Do you have an idea how to turn-off usb in u-boot as workaround?

I dont know how to disable USB "only" in u-boot.

But on a Odroid C2 we had restart issues which did belong to the u-boot version which was installed on the flash of the SBC and this wasnt in every case the u-boot version which was installed as a .deb-package.
So maybe my BPi M1 has another u-boot version installed in flash?

[Elric]

@guidol I don't understand your last question. BPi-M1 doesn't have eMMC or am I wrong? Flash is, what will be found on sdcard. And on sdcard is the image provided by armbian.com on the page for banana pi m1. At the moment this is: Armbian_21.05.1_Bananapi_buster_current_5.10.34.img (or focal). But with your statement that the plugged-in receiver doesn't cause an endless boot loop, on 5.12 or 5.13, I decided to upgrade to 5.12.12. This worked as you described, after updating firmware and bootloader the problem was fixed.
 

After rolling back to 5.10.34 without updating bootloader the first work-around was done.

 

It only took a couple of hours playing around with armbian-config (System/Other&Firmware/Reboot) and balenaetcher on PC-side, and I found an acceptable workaround (and perhaps a solution).
On first run you have to start without the receiver, do you first login remotely via ssh or uart-console if you have one. First step is to run armbian-config to System/Others and select 5.10.43 . After the restart do "Firmware upgrade" (apt update && apt upgrade) and update bootloader. That's it!  I have 5.10.43 running and problem is gone.

The easiest and perhaps user friendliest way to solve this issue, would be providing 5.10.43 based install images for BPi-M1.

[Elric]

Before it's forgotten: I have to praise the work which is done in "armbian-config". Great job! Hours of upgrading / downgrading kernel and environment without having one error! That's what I call stable.