Page 1 of 1

Keyboard stopped on booting

Posted: Thu Dec 19, 2024 7:04 pm
by punhan
My machine is ASUS Tuf Gaming A15 with Nvidia 4050. On standard version (not AHS version) live boot, when I begin to choose video card option, keyboard stops working. I have checked failsafe options, nothing helped.

Re: Keyboard stopped on booting

Posted: Thu Dec 19, 2024 7:22 pm
by j2mcgreg
punhan wrote: Thu Dec 19, 2024 7:04 pm My machine is ASUS Tuf Gaming A15 with Nvidia 4050. On standard version (not AHS version) live boot, when I begin to choose video card option, keyboard stops working. I have checked failsafe options, nothing helped.
From here:
https://forums.linuxmint.com/viewtopic.php?t=403886
Your laptop needs at least a 6.2.xxx kernel. Your best bet would be to download the AHS version of MX which ships with a 6.4.xxx kernel.

Re: Keyboard stopped on booting

Posted: Fri Dec 20, 2024 3:07 am
by punhan
Thank you very much for a quick reply, with AHS when I put "noxorg" on failsafe, AHS version boots. The problem is Desktop Envirorment. how can I download AHS version with KDE by default? Yes, I can install KDE Plasma later, but will it be on the same functionality level with the KDE by default?

Re: Keyboard stopped on booting

Posted: Fri Dec 20, 2024 6:26 am
by j2mcgreg
punhan wrote: Fri Dec 20, 2024 3:07 am Thank you very much for a quick reply, with AHS when I put "noxorg" on failsafe, AHS version boots. The problem is Desktop Envirorment. how can I download AHS version with KDE by default? Yes, I can install KDE Plasma later, but will it be on the same functionality level with the KDE by default?
Yes, our KDE version uses the AHS base by default.

Re: Keyboard stopped on booting

Posted: Fri Dec 20, 2024 6:37 am
by punhan
but on KDE booting, the same problem happened, on video card selection, I just cant due to keyboard.

Re: Keyboard stopped on booting

Posted: Fri Dec 20, 2024 6:43 am
by Kermit the Frog
punhan wrote: Fri Dec 20, 2024 3:07 am... The problem is Desktop Envirorment ...
Nope, both are AHS, just the Xfce one has a more recent kernel while KDE release has the default (6.1) kernel (the one used in regular MX and Debian).

In fact KDE also had more recent kernels in previous MXs but they later changed that.

Yes, of course one may install KDE like any DE but it won't be the same as the KDE release cause it''s also (MX tools like "MX Tweak" and sddm etc) are also adjusted according to Plasma (normally all are done according to Xfce).

If you like: You can boot on another pc (with KDE release) then install the most recent (while you're at it) Liquorix kernel from MX Package Installer with 2 clicks, then run:

"MX RemasterCC" and finally "Live Usb Kernel Updater" from menu (to make it permanent).

Re: Keyboard stopped on booting

Posted: Fri Dec 20, 2024 6:44 am
by Eadwine Rose
Moved to help, since you are not sharing a tip, nor a trick.

Attach a different keyboard to rule out the keyboard.

Re: Keyboard stopped on booting

Posted: Fri Dec 20, 2024 6:45 am
by Kermit the Frog
In the meantime:

If you mean you have dual cards and it asks you : Just try to boot with this parameter:

Code: Select all

vcard=off

Re: Keyboard stopped on booting

Posted: Fri Dec 20, 2024 7:00 am
by punhan
vcard=off really worked and screen opened, the problem now is keyboard not working to install.

Re: Keyboard stopped on booting

Posted: Fri Dec 20, 2024 7:09 am
by Kermit the Frog
punhan wrote: Fri Dec 20, 2024 7:00 am vcard=off really worked and screen opened
:number1:

Is it a bluetooth / wireless keyboard ?

Still a more recent kernel will be better.


In the meantime you can do this :

Boot with the AHS release, then post "Quick System Info" from menu. That will provide the best info rather than asking 101 questions.

Re: Keyboard stopped on booting

Posted: Fri Dec 20, 2024 7:27 am
by punhan
Image

Re: Keyboard stopped on booting

Posted: Fri Dec 20, 2024 7:29 am
by punhan
No, it is not external keyboard, built-in laptop. I can not even find virtual keyboard for typing during installation.

Re: Keyboard stopped on booting

Posted: Fri Dec 20, 2024 7:31 am
by Kermit the Frog
If the mouse is working you can start "Onboard" from menu.

(It's under "Accessories" on Xfce, you'll find in KDE somewhere like that)

Re: Keyboard stopped on booting

Posted: Fri Dec 20, 2024 7:51 am
by punhan
Touchpad is working. How can I solve this problem without onboard or usb enabled external keyboard?

Re: Keyboard stopped on booting

Posted: Fri Dec 20, 2024 7:57 am
by Kermit the Frog
You can do the above before installation:

Using the touchpad start "MX Package Installer" from menu (assuming you have internet connection. If you need to enter pw. then start onboard, too), then from the 1st tab, Kernels section tick the Liquorix 6.11.... and click install.. that's it.

But this won't be saved for next boots. Therefore start "MX RemasterCC" from menu after that.. proceed... Finally start "Live Usb Kernel Updater" from menu (You'll find them under "MX Tools" in menu)...

Now the new kernel is saved (permanent). Reboot with the live usb.

_________________________

Or just install but you'll need to enter user name and password (etc.) during installation. Therefore open "Onboard" as the first thing.. Later you can install the new kernel on the installed MX however you won't be able to type your pw. on login screen without Onboard (at first reboot).

P.S. "Onboard" is the name of the app. according to Xfce, on KDE it may have a different (similar) name.

Re: Keyboard stopped on booting

Posted: Fri Dec 20, 2024 8:11 am
by Eadwine Rose
Please do not share the QSI as image. Use the copy for forum button provided.

Re: Keyboard stopped on booting

Posted: Fri Dec 20, 2024 9:12 am
by punhan
I could not find virtual keyboard on kde, there is really no this kind of app on MX kde, I guess.

Re: Keyboard stopped on booting  [Solved]

Posted: Fri Dec 20, 2024 9:58 am
by Kermit the Frog
I've read "onboard" works on kde, too, both Wayland and X11

I'd tell the command but this time you won't be able to press Enter after you paste it :)

So, you can find in 2nd tab (Enabled Repos) in MX Package Installer:

Code: Select all

onboard-common
onboard-data
onboard
But the easiest is just doing the new kernel thing on a different pc that it boots fine...

Re: Keyboard stopped on booting

Posted: Fri Dec 20, 2024 10:01 am
by j2mcgreg
If I were you, I would download the AHS XFCE version of MX with its 6.4.xxx kernel to see if it solves the keyboard problem and also to discover if there are any other major hurdles with that laptop. Adding KDE with its 6.1 kernel is a complication you don't need at this point.

Re: Keyboard stopped on booting

Posted: Fri Dec 20, 2024 10:11 am
by Kermit the Frog
Post #3 sounded like that to me (keyboard also worked) but I may be wrong as it's not clear.

Just btw. @dolphin_oracle the vcard parameter may be buggy cause in this case none of the cards are Intel (Nvidia + AMD) and it disabled both cards (drivers) => black screen (as the default setting is on)

Code: Select all

vcard=on ... Detect hybrid graphics then disable the non-Intel video drivers

Re: Keyboard stopped on booting

Posted: Fri Dec 20, 2024 10:15 am
by punhan
Thank you all, the problem solved. Just curious how MX will help me to become better developer.

Re: Keyboard stopped on booting

Posted: Fri Dec 20, 2024 10:16 am
by Kermit the Frog
Glad to see it's solved.

But, what did you do? Installed?

Re: Keyboard stopped on booting

Posted: Fri Dec 20, 2024 10:20 am
by punhan
Yeah, I did not like KDE itself overall and installed xfce with ahs, first thing to do was to test hibernation, unfortunately, it did not work. on kernel 6.10, partially worked, but wifi disconnected. Plus, on kernel 6.11, it did not wake up, black screen. HIbernation is important for me, hope to find a solution.

Re: Keyboard stopped on booting

Posted: Fri Dec 20, 2024 10:28 am
by Kermit the Frog
You know, hibernation and suspend are different. (First one is to disk, the latter is to Ram).

However it's a long time known issue. This will remove the problematic screensaver and replace it with a decent screen locker (as in previous MXs):

Code: Select all

sudo apt purge xfce4-screensaver -y ; sudo apt update ; sudo apt install light-locker -y
Now try "suspend".

Or just this:

Code: Select all

sudo pm-suspend
(This command suspends without locking the screen)

Re: Keyboard stopped on booting

Posted: Fri Dec 20, 2024 10:31 am
by Kermit the Frog
In fact, you can open a new thread posting the current system's QSI (just click the "Copy For Forum" button, then paste in your post, code tags are ready, included in it)

Re: Keyboard stopped on booting

Posted: Fri Dec 20, 2024 10:35 am
by punhan
suspend is not an issue, hibernation is. what you recommended is just for suspend? Hibernation will be normally working after deleting xfce4 screensaver deletion? You know, opening new thread is in my mind, I am just a bit lazy for it.)

Re: Keyboard stopped on booting

Posted: Fri Dec 20, 2024 10:37 am
by punhan

Code: Select all

Snapshot created on: 20241215_1628
System:
  Kernel: 6.11.9-amd64 [6.11.9-1~mx23ahs] arch: x86_64 bits: 64 compiler: N/A
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.11.9-amd64 root=UUID=<filter> ro quiet splash
    resume=UUID=<filter> resume_offset=31023104
  Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 info: xfce4-panel wm: xfwm v: 4.18.0 vt: 7
    dm: LightDM v: 1.26.0 Distro: MX-23.4_x64 Libretto December 15  2024 base: Debian GNU/Linux 12
    (bookworm)
Machine:
  Type: Laptop System: ASUSTeK product: ASUS TUF Gaming A15 FA507NU_FA507NU v: 1.0
    serial: <superuser required>
  Mobo: ASUSTeK model: FA507NU v: 1.0 serial: <superuser required> UEFI: American Megatrends LLC.
    v: FA507NU.315 date: 10/18/2024
Battery:
  ID-1: BAT1 charge: 43.5 Wh (53.6%) condition: 81.1/90.2 Wh (89.8%) volts: 14.8 min: 15.9
    model: ASUS A32-K55 type: Li-ion serial: N/A status: discharging
CPU:
  Info: model: AMD Ryzen 7 7735HS with Radeon Graphics bits: 64 type: MT MCP arch: Zen 3+ gen: 4
    level: v3 note: check built: 2022 process: TSMC n6 (7nm) family: 0x19 (25) model-id: 0x44 (68)
    stepping: 1 microcode: 0xA404102
  Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache: L1: 512 KiB
    desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB desc: 8x512 KiB L3: 16 MiB desc: 1x16 MiB
  Speed (MHz): avg: 1918 high: 4784 min/max: 400/4829 boost: enabled scaling:
    driver: amd-pstate-epp governor: powersave cores: 1: 2128 2: 2374 3: 2124 4: 2269 5: 3732 6: 400
    7: 2555 8: 400 9: 2127 10: 400 11: 400 12: 4067 13: 2128 14: 400 15: 4784 16: 400
    bogomips: 102208
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow status: Vulnerable: Safe RET, no microcode
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Retpolines; IBPB: conditional; IBRS_FW; STIBP: always-on; RSB
    filling; PBRSB-eIBRS: Not affected; BHI: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: NVIDIA AD107M [GeForce RTX 4050 Max-Q / Mobile] vendor: ASUSTeK GN21-X2 driver: N/A
    alternate: nouveau non-free: 530.xx+ status: current (as of 2023-03) arch: Lovelace code: AD1xx
    process: TSMC n4 (5nm) built: 2022-23+ pcie: gen: 4 speed: 16 GT/s lanes: 8 bus-ID: 01:00.0
    chip-ID: 10de:28e1 class-ID: 0300
  Device-2: AMD Rembrandt [Radeon 680M] vendor: ASUSTeK driver: amdgpu v: kernel arch: RDNA-2
    code: Navi-2x process: TSMC n7 (7nm) built: 2020-22 pcie: gen: 4 speed: 16 GT/s lanes: 16 ports:
    active: eDP-1 empty: DP-1, DP-2, DP-3, DP-4, DP-5, DP-6, DP-7, DP-8, Writeback-1
    bus-ID: 35:00.0 chip-ID: 1002:1681 class-ID: 0300 temp: 47.0 C
  Device-3: Sonix USB2.0 HD UVC WebCam type: USB driver: uvcvideo bus-ID: 1-4:2
    chip-ID: 2b7e:b685 class-ID: 0e02
  Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X: loaded: amdgpu
    unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: amdgpu display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22") s-diag: 582mm (22.93")
  Monitor-1: eDP-1 mapped: eDP model: AU Optronics B156HAN15.H built: 2022 res: 1920x1080 hz: 144
    dpi: 142 gamma: 1.2 size: 344x193mm (13.54x7.6") diag: 394mm (15.5") ratio: 16:9 modes:
    max: 1920x1080 min: 640x480
  API: OpenGL v: 4.6 Mesa 24.2.2-1~mx23ahs renderer: AMD Radeon 680M (radeonsi rembrandt LLVM
    15.0.6 DRM 3.59 6.11.9-amd64) direct-render: Yes
Audio:
  Device-1: NVIDIA vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie: speed: Unknown lanes: 63
    link-max: gen: 6 speed: 64 GT/s bus-ID: 01:00.1 chip-ID: 10de:22be class-ID: 0403
  Device-2: AMD Rembrandt Radeon High Definition Audio driver: snd_hda_intel v: kernel pcie:
    gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 35:00.1 chip-ID: 1002:1640 class-ID: 0403
  Device-3: AMD ACP/ACP3X/ACP6x Audio Coprocessor vendor: ASUSTeK driver: snd_pci_acp6x v: kernel
    alternate: snd_pci_acp3x, snd_rn_pci_acp3x, snd_pci_acp5x, snd_rpl_pci_acp6x, snd_pci_ps,
    snd_sof_amd_rembrandt pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 35:00.5 chip-ID: 1022:15e2
    class-ID: 0480
  Device-4: AMD Family 17h/19h HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie:
    gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 35:00.6 chip-ID: 1022:15e3 class-ID: 0403
  API: ALSA v: k6.11.9-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK driver: r8169
    v: kernel pcie: speed: Unknown lanes: 63 link-max: gen: 6 speed: 64 GT/s port: e000
    bus-ID: 02:00.0 chip-ID: 10ec:8168 class-ID: 0200
  IF: eth0 state: down mac: <filter>
  Device-2: MEDIATEK MT7921 802.11ax PCI Express Wireless Network Adapter vendor: AzureWave
    driver: mt7921e v: kernel modules: wl pcie: gen: 2 speed: 5 GT/s lanes: 1 bus-ID: 03:00.0
    chip-ID: 14c3:7961 class-ID: 0280
  IF: wlan0 state: up mac: <filter>
Bluetooth:
  Device-1: IMC Networks Wireless_Device type: USB driver: btusb v: 0.8 bus-ID: 3-3:2
    chip-ID: 13d3:3563 class-ID: e001 serial: <filter>
  Report: hciconfig ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 3.0 lmp-v: 5.2
    sub-v: 2301 hci-v: 5.2 rev: 1717
  Info: acl-mtu: 1021:6 sco-mtu: 240:8 link-policy: rswitch sniff link-mode: peripheral accept
    service-classes: rendering, capturing, object transfer, audio, telephony
Drives:
  Local Storage: total: 476.94 GiB used: 26.8 GiB (5.6%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Micron model: 2400 MTFDKBA512QFM size: 476.94 GiB
    block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD serial: <filter>
    rev: V3MA003 temp: 34.9 C scheme: GPT
Partition:
  ID-1: / raw-size: 146 GiB size: 142.65 GiB (97.71%) used: 26.8 GiB (18.8%) fs: ext4
    dev: /dev/nvme0n1p6 maj-min: 259:6
  ID-2: /boot/efi raw-size: 500 MiB size: 499 MiB (99.80%) used: 288 KiB (0.1%) fs: vfat
    dev: /dev/nvme0n1p5 maj-min: 259:5
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: file size: 18.87 GiB used: 0 KiB (0.0%) priority: -2 file: /swap/swap
  ID-2: swap-2 type: zram size: 256 MiB used: 0 KiB (0.0%) priority: 100 dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 60.5 C mobo: 32.0 C gpu: amdgpu temp: 47.0 C
  Fan Speeds (RPM): cpu: 2100
Repos:
  Packages: pm: dpkg pkgs: 2127 libs: 1052 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
    pkgs: 0 pm: flatpak pkgs: 0
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
    1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
    2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb http://mirror.math.princeton.edu/pub/mxlinux/mx/repo/ bookworm main non-free
  Active apt repos in: /etc/apt/sources.list.d/mxpitemp.list
    1: deb http://mirror.math.princeton.edu/pub/mxlinux/mx/repo/ bookworm ahs
Info:
  Processes: 378 Uptime: 31m wakeups: 65168 Memory: 14.88 GiB used: 2.47 GiB (16.6%) Init: SysVinit
  v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
  Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI

Re: Keyboard stopped on booting

Posted: Fri Dec 20, 2024 10:43 am
by Kermit the Frog
You have the required parameters for hibernation:

Code: Select all

resume=UUID=<filter> resume_offset=31023104
However Nouveau (the open source Nvidia driver) is still not loaded for some reason:

Graphics:
Device-1: NVIDIA AD107M [GeForce RTX 4050 Max-Q / Mobile] vendor: ASUSTeK GN21-X2 driver: N/A



That screensaver is known to cause such issues, so remove it no matter you use it or not or even if it's already disabled.


To load the Nouveau we can force it:

"MX Boot Options" from menu, add:

Code: Select all

nouveau.modeset=1
into "Kernel Parameters" box (with a space before it).. Apply, reboot.


(Alternatively you can (if you like only) try to install the proprietary Nvidia driver: "Nvidia Driver Installer" from menu)

Re: Keyboard stopped on booting

Posted: Fri Dec 20, 2024 11:52 am
by punhan
I did what all you said, deleting screensaver, forcing gpu driver from boot options. But black screen is all I see during hibernation wake-up. What else is needed?

Re: Keyboard stopped on booting

Posted: Fri Dec 20, 2024 1:11 pm
by Kermit the Frog
For all other readers:

Goes on in this new thread: viewtopic.php?p=802266#p802266