I’m trying to run manjaro-kde-21.2.6 on an HP Envy (15-aq005na), booting from USB.
Using an external keyboard works without issue. The internal keyboard works fine in GRUB, but there is seemingly zero input from the internal keyboard once manjaro has loaded.
I plugged the same USB into another laptop and the internal keyboard works fine. I had this exact issue trying to run LMDE 4, 5 and LM 20.3 - except with LM the touchpad wasn’t working either, in manjaro the touchpad functions fine.
I’ve tried both open and proprietary. As well as enabling/disabling legacy mode in BIOS.
Manjaro was loaded onto a USB using rufus with partition: MBR, target system: BIOS or UEFI.
This is my first attempt at using linux altogether, so I’m not 100% sure on what logs to offer without being requested.
provide formated (click 3x this icon: </>) output of this: inxi -Fazy lsusb lspci
and also install the following kernels (system settings/ kernel):
5.17.1-3
5.15.32-1
5.10.109-1
5.4.188-1
reboot, and try booting with each one, and check your keyboard
@brahma You seem to have misunderstood the OP: they are booting from usb.
One cannot change the kernel for usb boot via package management.
You can try downloading another ISO with another kernel, latest stable announcement post has several minimal isos for each DE featuring 5.15, 5.10 or 5.4 kernel:
I installed Manjaro on an external sata SSD from a USB live boot. This HP Envy I’m working with had some issues, I couldn’t get it to boot from the HDD, or SSD (both operate fine independently when checked on another device) with windows or linux. So I think the HP has issue reading from internal drives. This is my friends computer, I was given it as a ‘play’ computer, due to it being faulty, which I decided I’d start my linux journey on. Prior to the internal drive failures, the keyboard and touch pad were working fine. Obviously this device is having some hardware issues, but given the keyboard works fine in BIOS and manjaro GRUB, I thought I may be able to solve it.
I tried kernels:
5.17.1-3
5.15.32-1
5.10.109-1
5.4.188-1
Ensuring all were running, not just installed and restarted / checked the keypad with each trial. No success unfortunately. Interestingly the touchpad couldn’t move the cursor on 5.10, but it worked fine with all other kernels. When I tried mint (20.2, LMDE 4 & 5) the touchpad nor keyboard worked either.
So. I’m currently running manjaro installed on an external sata SSD, kernel 5.15.32-1. Touchpad is moving the cursor, no feedback from keyboard but on a live boot the keyboard works in GRUB. When I boot installed manjaro I get /dev/sda2: clean, 285112/7798784 files, 3015368/31181161 blocks, before showing the login screen.
/dev/sda2: clean, 285112/7798784 files, 3015368/31181161 blocks - this message is normal, so ignore it…
go to etc/mkinitcpio.conf and post the line HOOKS=" … " here
really have no idea… you could try putting in /etc/default/grub and in this line: GRUB_CMDLINE_LINUX_DEFAULT inside the " " quotes this paramater: acpi=off - dont delete anything from the line, just add it there…
run this: sudo update-grub
reboot and check
I ran the grub update and now I actually have grub when booting manjaro, a nicer feel than the files and blocks message. Thanks for that.
acpi=off didn’t fix the HP keyboard, unfortunately, despite the keyboard still working in grub. Interestingly acpi=offdisabled my internal keyboard on my acer predator too. I deleted this and now the predator keyboard is back to working.
No worries at all, your help is greatly appreciated. I’m going to proceed my linux journey using my predator, booting manjaro (installed) from an external ssd. I don’t know much, at all, of what you wrote/suggested so my next steps are to learn about what you offered.
that acpi off was a one solution i found that one had with the exact same pc as you, and it did work for him … you can search for internal keyboard not working linux manjaro arch ubuntu …
This is a wild guess, since the laptop could have some issues it might be a interesting experiment to disable as much as possible in the BIOS. This thread on HP’s site seems a solution for one type of machine where disabling integrated sensors enabled the keyboard.