Yup with flatpak
Are you able to access the Recovery Menu rather than tty?
Tap the esc key vigorously after seeing the motherboard splash screen, then select Advanced Options for Zorin
From the grub menu, first enable networking. Then back out to the grub menu and arrow key down to Drop to Prompt.
flatpak uninstall com.leinardi.gwe
I am not sure if that above flatpak remove command is correct... I do not use flatpak.
Maybe it is su
How did you install your Nvidia Drivers directly?
To try to regain access to the desktop, you can try:
sudo nano /boot/grub/grub.cfg
Read Through looking for something similar to
linux /boot/vmlinuz-5.15.0-52-generic root=UUID=stuffsomethingandmorestuff ro quiet splash $vt_handoff
You may need to scroll a bit.
This is the part you want to pay attention to: quiet splash $vt_handoff Remove the $vt_handoff to make it just end with quiet splash
ctrl+x to exit, then the y key then the `enter key.
Run
sudo update-grub
Once done, reboot and test...
I forgot to mention i had changed /etc/default/grub to 'quiet splash nomodeset" ' but now it's stuck in the loading screen after I've reset that change
Which Nvidia card are you using?
In regards to the keyboard; do you have any BIOS Power settings such as Wake on Keyboard or mouse enabled or disabled?
Which ASUS laptop are you using?
1 Like
so i went to recovery mode, in root cmd line and removed that nvidia driver. My Computer booted up with the default gnome nvidida-driver and could set my driver in "Software & Update".
Also my graphics card is the Nvidia GeForce 3080, 16gb (Laptop-GPU).
oh i will have to look at that
Reboot the laptop and read the screen. It wll tell you what key to hit to enter the BIOS. Usually it is F2, or F12, or delete.
Once in BIOS the setting is usually under the POWER screen. If you download the manual from ASUS for your laptop, it will very likely show how to enter the BIOS and where the POWER screen is. I don't own an ASUS laptop so I can not be any more helpful than the above, sorry.
You attached image did not show up for me, maybe a bad link or something on my end.
Well...It could be under any of the tabs to be honest. Use your Tab or Arrow key and tab over to Advance and see what is in that tab.
The entry will be "Wake on keyboard input" or similar. Would be the same for the mouse and the touchpad if those are listed. Also look at any Power entry that may do with "suspend".
2 Likes
Hello im back again, after some time
i had done some distro hopping and noticed, that this error is not a ubuntu problem, it is just a grub problem. no reset would help in the grub code, as grub doesnt recognize my keyboard at the beginnig, it is just the bios which gives the information about the keyboard to the system. After relog, the bios service wont give any infos and grub fails initializing the keyboard in the first place.
My father suggested giving grub the driver based on how the keyboard is connected to the main board (for example: usb) based on the individual laptop.
1 Like
And im going back to Zorin, because I had the best Linux Gaming in here. Nvidia is the worst computing company i am dealing with. It just works on Zorin.
1 Like
A very sloppy AskUbuntu-Topic had a severe run out on tips and tricks, and myself I recall, as ex support point of Ubuntu Belgium, something of a very rare but nucky Lenovo that did not work on Keyboard after a suspend of the system.
Long story short:
sudo nano /etc/default/grub
Modify this line as edit to the correct Grub-line (NOT DEFAULT !!!)
If you do not like nano, you can of course use any other editor.
GRUB_CMDLINE_LINUX="i8042.reset i8042.nomux i8042.nopnp i8042.noloop"
Of course after the edit do this little magic :
sudo update-grub
And as a real pro type sudo reboot for the real test --- suspend --- Keyboard working or not.
I remember well that this really did the trick on the rare Lenovo ... I hope this is for that Asus a solution as well.
If this does not work well reverse the tip and re-edit the line to original state.
Remeber this very well : Gaming and Laptops are NEVER a good match at all. If you really like gaming go for a console such as PlayStation or X-box to name a few. These machines can run games for hours in a row ..... a laptop can't. Unless you are using forced extra cooling, and so on. But even then such laptops dry out in their electronics because of cummulated heat. Linux is great for games to run, but the hardware itself is simply not really capable at all, regardless the marketing, the big promisses, the lies on internet and commercials.
1 Like
well this didnt work either
when i reversed the change and updated grub, i received that output:
$ sudo update-grub
Sourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/init-select.cfg'
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/zorin/theme.txt
Found background image: /home/admindavid/Downloads/589590 Cropped.jpg
Found linux image: /boot/vmlinuz-5.15.0-60-generic
Found initrd image: /boot/initrd.img-5.15.0-60-generic
Found linux image: /boot/vmlinuz-5.15.0-56-generic
Found initrd image: /boot/initrd.img-5.15.0-56-generic
device-mapper: remove ioctl on osprober-linux-nvme0n1p13 failed: Device or resource busy
Command failed.
Found EndeavourOS Linux (rolling) on /dev/nvme0n1p9
Adding boot menu entry for UEFI Firmware Settings
done
well my father wanted a high end "portable" computer, which would last long, for him, gaming wasnt really inteded.
ive tried booting on a more bleeding edge system, this is the log of my kernel 6.1 version, to ensure that the drivers are the newest and therefor hopefully more fitting for my laptop:
$ sudo dmesg --level=err,warn,crit,alert,emerg -f kern
[sudo] password for admindavid:
[ 0.000000] [Firmware Bug]: TSC ADJUST: CPU0: -946224050 force to 0
[ 0.010138] [Firmware Bug]: TSC ADJUST differs within socket(s), fixing all errors
[ 0.137149] #2 #3 #4 #5 #6 #7 #8 #9 #10 #11 #12 #13 #14 #15
[ 0.169724] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
[ 0.556200] pnp 00:03: disabling [mem 0xc0000000-0xcfffffff] because it overlaps 0000:00:02.0 BAR 9 [mem 0x00000000-0xdfffffff 64bit pref]
[ 0.624114] hpet_acpi_add: no address or irqs in _CRS
[ 0.968067] wmi_bus wmi_bus-PNP0C14:00: WQ00 data block query control method not found
[ 0.970895] i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
[ 0.979111] pci 10000:e0:06.0: Primary bus is hard wired to 0
[ 0.979421] pci 10000:e0:06.0: Primary bus is hard wired to 0
[ 1.173073] pcieport 10000:e0:06.0: can't derive routing for PCI INT D
[ 1.173076] pcieport 10000:e0:06.0: PCI INT D: no GSI
[ 1.198572] pcieport 10000:e0:06.0: can't derive routing for PCI INT A
[ 1.198581] nvme 10000:e1:00.0: PCI INT A: not connected
[ 3.429904] ACPI BIOS Error (bug): Could not resolve symbol [\CTDP], AE_NOT_FOUND (20220331/psargs-330)
[ 3.430443] ACPI Error: Aborting method \_SB.IETM.IDSP due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
[ 3.431049] ACPI Warning: \_SB.IETM._TRT: Return Package has no elements (empty) (20220331/nsprepkg-94)
[ 3.459792] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN1._CRT.S1CT], AE_NOT_FOUND (20220331/psargs-330)
[ 3.460307] ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN1._CRT due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
[ 3.460887] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN1._HOT.S1HT], AE_NOT_FOUND (20220331/psargs-330)
[ 3.461427] ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN1._HOT due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
[ 3.461945] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN1._PSV.S1PT], AE_NOT_FOUND (20220331/psargs-330)
[ 3.462577] ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN1._PSV due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
[ 3.463381] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN1._AC0.S1AT], AE_NOT_FOUND (20220331/psargs-330)
[ 3.464028] ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN1._AC0 due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
[ 3.472386] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN2._CRT.S2CT], AE_NOT_FOUND (20220331/psargs-330)
[ 3.473254] ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN2._CRT due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
[ 3.474109] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN2._HOT.S2HT], AE_NOT_FOUND (20220331/psargs-330)
[ 3.474894] ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN2._HOT due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
[ 3.475795] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN2._PSV.S2PT], AE_NOT_FOUND (20220331/psargs-330)
[ 3.476714] ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN2._PSV due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
[ 3.477333] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN2._AC0.S2AT], AE_NOT_FOUND (20220331/psargs-330)
[ 3.478133] ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN2._AC0 due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
[ 3.480813] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN3._CRT.S3CT], AE_NOT_FOUND (20220331/psargs-330)
[ 3.481474] ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN3._CRT due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
[ 3.482320] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN3._HOT.S3HT], AE_NOT_FOUND (20220331/psargs-330)
[ 3.483159] ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN3._HOT due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
[ 3.483918] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN3._PSV.S3PT], AE_NOT_FOUND (20220331/psargs-330)
[ 3.484804] ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN3._PSV due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
[ 3.485992] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN4._CRT.S4CT], AE_NOT_FOUND (20220331/psargs-330)
[ 3.487007] ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN4._CRT due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
[ 3.487861] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN4._HOT.S4HT], AE_NOT_FOUND (20220331/psargs-330)
[ 3.488548] ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN4._HOT due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
[ 3.489104] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN4._PSV.S4PT], AE_NOT_FOUND (20220331/psargs-330)
[ 3.489664] ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN4._PSV due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
[ 3.490215] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN4._AC0.S4AT], AE_NOT_FOUND (20220331/psargs-330)
[ 3.490749] ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN4._AC0 due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
[ 3.573263] resource sanity check: requesting [mem 0xfedc0000-0xfedcdfff], which spans more than pnp 00:03 [mem 0xfedc0000-0xfedc7fff]
[ 3.573271] caller __uncore_imc_init_box+0xc4/0x120 [intel_uncore] mapping multiple BARs
[ 3.641282] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[ 3.864265] Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported.
[ 3.871350] ACPI Warning: \_SB.PC00.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20220331/nsarguments-61)
[ 3.871388] ACPI Warning: \_SB.PC00.PEG1.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20220331/nsarguments-61)
[ 4.161737] Bluetooth: hci0: AOSP quality report is not supported
[ 4.570389] asus 0003:0B05:19B6.0002: Asus input not registered
[ 4.570415] asus: probe of 0003:0B05:19B6.0002 failed with error -12
[ 464.771058] ntfs3: Unknown parameter 'windows_names'
@Aravisian can you work with this?
The AE not found and ACPI errors can be ignored. They are harmless and refer to the acpi table not matching the expected descriptions. It sounds complicated, but is not really. The kernel just uses fallback.
Does this machine have an Nvidia Card?
Your original issue is still present - Keyboard not working on Wake, Correct?