Bug 28572 - aarch64 Mga8 on RPi3b+ reaches CLI login with no working keyboard
Summary: aarch64 Mga8 on RPi3b+ reaches CLI login with no working keyboard
Status: NEW
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 8
Hardware: aarch64 Linux
Priority: Normal major
Target Milestone: ---
Assignee: Kernel and Drivers maintainers
QA Contact:
URL: aarch64/install/images/Mageia-8-rpi-a...
Whiteboard:
Keywords:
: 29560 (view as bug list)
Depends on:
Blocks: 32166
  Show dependency treegraph
 
Reported: 2021-03-09 23:34 CET by Barry Jackson
Modified: 2023-08-11 15:38 CEST (History)
8 users (show)

See Also:
Source RPM:
CVE:
Status comment: Mageia-8-rpi-aarch64-noDE.img and other from feb 21th build.


Attachments
journal output (47.67 KB, text/plain)
2021-03-09 23:37 CET, Barry Jackson
Details
Last boot logs (48.40 KB, text/plain)
2021-10-16 14:30 CEST, Guillaume Royer
Details

Description Barry Jackson 2021-03-09 23:34:41 CET
Description of problem:
As Summary.
The keyboard is working at grub2 menu, but when the boot reaches CLI login the keyboard fails to work.

Tested with wired and radio keyboards which both work with raspbian.

I see exactly the same with both graphical images as well.

I see no network activity and cannot detect a new IP on the LAN, so obviously cannot ssh in.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. extract image and checksum file & verify checksum
2. dd onto a 32GB SD card
3. Boot using SD card.
Comment 1 Barry Jackson 2021-03-09 23:37:03 CET
Created attachment 12438 [details]
journal output

Journal from SD card.
Barry Jackson 2021-03-09 23:48:18 CET

URL: (none) => aarch64/install/images/Mageia-8-rpi-aarch64-noDE.img.gz

Filip Komar 2021-03-10 10:57:02 CET

CC: (none) => filip.komar

Comment 2 Aurelien Oudelet 2021-03-12 11:13:29 CET
rpi4b 8 GB.

Same issue. Keyboard not functioning and USB timeout while booting.

my rpi4b seems to reach final booting. But, can't have interaction.
Don't even know default login to try a ssh connection...

CC: sysadmin-bugs => j.biernacki+mga, ouaurelien, pterjan
Component: Release (media or process) => RPM Packages
Source RPM: Mageia-8-rpi-aarch64-noDE.img => (none)
Status comment: (none) => Mageia-8-rpi-aarch64-noDE.img and other from feb 21th build.

Comment 3 Jybz 2021-03-12 11:19:14 CET
Default login : root (there is by default no other user, for security reason.)
There is no default password : at first root login, a new password will be asked.

As it is, NO rpi users would have the same root-password / user-default password, it enhance the security.
Comment 4 Thomas Backlund 2021-03-12 12:38:41 CET
does it help to unplug / replug usb keyboard after system is fully booted ?
Comment 5 Aurelien Oudelet 2021-03-12 12:49:13 CET
It does not. Will add later today a journal output by putting the sd card in a reader on main computer.
Comment 6 Pascal Terjan 2021-03-12 12:57:53 CET
It may be caused by my u-boot patches putting things in a wrong state, but there is definitely something wrong with keyboard handling.

It used to crash u-boot due a NULL pointer which I fixed with http://svnweb.mageia.org/packages/cauldron/u-boot/current/SOURCES/0001-Fix-a-crash-when-any-USB-device-is-present-on-RPi4.patch?revision=1662661&view=markup

I tried to handle it better in http://svnweb.mageia.org/packages/cauldron/u-boot/current/SOURCES/0003-xhci-Don-t-queue-for-halted-devices.patch?revision=1662661&view=markup which worked for me when I tried but may try to drop. I'll try to test more at the week-end now that I have a local machine again.
Comment 7 Aurelien Oudelet 2021-03-13 16:53:36 CET
Really assigning.

Assignee: bugsquad => kernel

Comment 8 Pascal Terjan 2021-03-14 21:41:50 CET
So I tried the mga8 image and it is actually worse for me on rpi4:
- If keyboard at boot I don't get to grub, it loops on .WARN Endpoint halted
- If I plug it in while on GRUB menu, it doesn't work there (not surprising), or don't plug it in, the boot gets stuck detecting USB devices (it stops after detecting internal USB hubs)
- If I plug it in after the USB hubs are detected by the kernel, boot resumes and the keyboard works fine...
Comment 9 Pascal Terjan 2021-03-15 14:32:31 CET
I tired again later and didn't have the first problem anymore.

For the last part I think it was just timing luck, keyboard or not it still waits about 2 minutes after USB detection and plugging it in or unplugging/re-plugging it doesn't help. It may be a dracut problem.

[   10.064158] input: USB USB Keyboard as /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.3/1-1.3:1.0/0003:1A2C:0C21.0001/input/input0
[   10.133660] hid-generic 0003:1A2C:0C21.0001: input,hidraw0: USB HID v1.10 Keyboard [USB USB Keyboard] on usb-0000:01:00.0-1.3/input0
[   10.140427] input: USB USB Keyboard Mouse as /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.3/1-1.3:1.1/0003:1A2C:0C21.0002/input/input1
[   10.146280] input: USB USB Keyboard System Control as /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.3/1-1.3:1.1/0003:1A2C:0C21.0002/input/input2
[   10.213605] input: USB USB Keyboard Consumer Control as /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.3/1-1.3:1.1/0003:1A2C:0C21.0002/input/input3
[   10.219579] hid-generic 0003:1A2C:0C21.0002: input,hidraw1: USB HID v1.10 Mouse [USB USB Keyboard] on usb-0000:01:00.0-1.3/input1
[   37.603035] usb 1-1.3: USB disconnect, device number 3
[   46.893313] usb 1-1.3: new low-speed USB device number 4 using xhci_hcd
[   47.050563] usb 1-1.3: New USB device found, idVendor=1a2c, idProduct=0c21, bcdDevice= 1.10
[   47.056434] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[   47.062205] usb 1-1.3: Product: USB Keyboard
[   47.067978] usb 1-1.3: Manufacturer: USB
[   47.077022] input: USB USB Keyboard as /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.3/1-1.3:1.0/0003:1A2C:0C21.0003/input/input4
[   47.143598] hid-generic 0003:1A2C:0C21.0003: input,hidraw0: USB HID v1.10 Keyboard [USB USB Keyboard] on usb-0000:01:00.0-1.3/input0
[   47.157094] input: USB USB Keyboard Mouse as /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.3/1-1.3:1.1/0003:1A2C:0C21.0004/input/input5
[   47.163818] input: USB USB Keyboard System Control as /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.3/1-1.3:1.1/0003:1A2C:0C21.0004/input/input6
[   47.233568] input: USB USB Keyboard Consumer Control as /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.3/1-1.3:1.1/0003:1A2C:0C21.0004/input/input7
[   47.240409] hid-generic 0003:1A2C:0C21.0004: input,hidraw1: USB HID v1.10 Mouse [USB USB Keyboard] on usb-0000:01:00.0-1.3/input1
[  156.300316] dracut: Scanning for all btrfs devices
[  156.652915] EXT4-fs (mmcblk0p2): INFO: recovery required on readonly filesystem
[  156.659807] EXT4-fs (mmcblk0p2): write access will be enabled during recovery
[  157.067697] EXT4-fs (mmcblk0p2): recovery complete
[  157.084101] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[  157.259037] dracut: Mounted root filesystem /dev/mmcblk0p2
[  157.575667] dracut: Switching root

But when boot completes, keyboard works fine here.
Rolf Pedersen 2021-03-15 14:51:06 CET

CC: (none) => rolfpedersen

Jybz 2021-03-15 16:01:09 CET

See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=26277

Comment 10 Filip Komar 2021-04-06 02:12:28 CEST
Keyboard (wireless USB) seems to work nicely on my RPi4 4G.
At least in grub, terminal and xfce ;).

$ dmesg | egrep -i keyboard
[   11.235078] hid-generic 0003:046D:C52B.0001: input,hidraw0: USB HID v1.11 Keyboard [Logitech USB Receiver] on usb-0000:01:00.0-1.4/input0
[   12.022076] input: Logitech Wireless Device PID:404d Keyboard as /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.4/1-1.4:1.2/0003:046D:C52B.0003/0003:046D:404D.0004/input/input5
[   12.066031] hid-generic 0003:046D:404D.0004: input,hidraw1: USB HID v1.11 Keyboard [Logitech Wireless Device PID:404d] on usb-0000:01:00.0-1.4/input2:1
[   14.651831] logitech-hidpp-device 0003:046D:404D.0004: input,hidraw1: USB HID v1.11 Keyboard [Logitech K400 Plus] on usb-0000:01:00.0-1.4/input2:1

I used Mageia-8-rpi-aarch64-noDE.img.gz image as a start.
Marja Van Waes 2021-05-25 13:08:01 CEST

CC: (none) => marja11

Comment 11 Guillaume Royer 2021-10-16 14:30:28 CEST
Created attachment 12954 [details]
Last boot logs

CC: (none) => guillaume.royer

Comment 12 Guillaume Royer 2021-10-16 14:33:46 CEST
I tried to boot MGA8 on my RPI 3B+. 

I had same issue with keyboard. Neither keyboard nor network card works.

You can find in attachment logs, as you can see it won't help much
Comment 13 Ezequiel Partida 2022-02-17 00:38:23 CET
I have the same issue and I haven´t been able to solve it.

I hope new image will be out soon.

Regards

CC: (none) => ezequiel_partida

Barry Jackson 2022-04-13 22:12:53 CEST

Severity: normal => major

Comment 14 Ezequiel Partida 2023-07-14 04:23:43 CEST
It would be great that the image had openssh-server enabled to access the rpi and see if someone can find the solution on this, probably new updates will solve it but we won´t know without an updated image.
Comment 15 Ezequiel Partida 2023-07-14 04:24:41 CEST
Btw, this problem is also on mga9 beta.
Comment 16 Jybz 2023-08-11 15:36:04 CEST
*** Bug 29560 has been marked as a duplicate of this bug. ***
Jybz 2023-08-11 15:38:57 CEST

Blocks: (none) => 32166


Note You need to log in before you can comment on or make changes to this bug.