I just came back home tried to boot my system booted manjaro into black screen saying clean, numbers/**numbers files, numbers/numbers blocks, i waited normally like i always do, system didn’t boot into desktop, can only see text cursor flashing in the corner, can’t use FN with alt +2 or 1, or anything really, confused and is now panicking +scared that i might’ve done something wrong (didn’t mess with any system files) anything i can do to solve this?
Hi @kodashi,
Since you mentioned you can’t even switch to TTY2, for example, I’d recommend booting into a live environment, entering a chroot environment and synching/updating the system, or provide the info from How to provide good information.
I am going to point you to a normal/helpful routine:
Then I am going to say you can skip that if I can make assumptions about you having a problematic nvidia card:
If you havent sorted it - please provide system information.
2 Likes
Look man i use an nvidia gpu the driver is nvidia-video, my cpu is a ryzen one i tried the function key with ctrl alt+f2, 1 and it didn’t do anything i have a lot of data that I’m scared i might accidentally corrupt in some way and I’m sweating my ass so what are the available options that i can take to boot to my desktop and fix this i know I’m being a whiny baby but I’m really concerned and i don’t want to ■■■■ anything up, once again I’m sorry but I’m panicking
hello , keep calm
if you can get a TTY ( Ctrl +Alt F2 to F7) to login , check
in journals logs or X11 logs errors
if not boot on USB manjaro iso live ( do not select your disk )
and go in chroot for gets logs
sudo manjaro-chroot -a
journalctl -b -1 -p 4 ( or b -2 , etc ... )
exit ( to end chroot )If that is the case, I highly doubt it’s integrated. I might be wrong, but I doubt it.
Whatever’s happening, though, you’ll need to boot into a live environment, a live USB drive probably, and enter a chroot environment.
-
Boot into a live ISO environment. From there you can open a browser on this page and provide feedback as neccessary or just see what to do next.
-
Once in the live environment, open a terminal, elevate to root, and enter the
chrootenvironment:
sudo su -
If the live environment requires a password, use manjaro both for the USER
password as well as the ROOT password.
2.1. Once elevated, enter a chroot environment:
manjaro-chroot -a
- Once successful, from there, follow this tutorial and provide the required information: How to provide good information
VERY IMPORTANT: Stop what you’'re doing, and do something to stop panicking before attempting any of this. Because panicking doesn’t help anybody.
Edit:
As @stephane said, from the chroot environment, provide us with the output of the following commands:
journalctl -b -1 -p 4
for logs from the previous boot attempt. As well as:
mhwd-kernel --listinstalled
and
mhwd --listinstalled
1 Like
Ok I bought a usb and burnt a manjaro xfce iso on it, i looked up some things and heard that if i had windows installed it might mess a bit with grub, but i have it on another drive so idk if the problem might still be relevant, the fix for it was said to update grub, what should i do when i boot from the usb (I’m using a uefi system), please tell me what info to send here and what i need to do, i realise I’m being very childish and require hand holding but it’s my first time using Linux and i don’t want to ruin it or lose any data
Yeah, I won’t be the one to help you further, as it’s evening here, and I’m already in bed.
However, the instructions above would be what’s necessary to get the troubleshooting started. For any- and everyone trying to help.
Hope you manage!
1 Like
THANKS INTERNET PERSON <3, I’ll try my best
Did you get it right? i have the same problem.
This saved Me, thanks
I had the same problem i describe how i find the answer here.
1 Like
Same problem for me (no lightdm login screen, left at message saying sda1 is clean). Nvidia reinstallation also worked for me. But I had to remove linux510-rt as it prevented nvidia removal script.
-
alt + ctl + F2 for usable terminal, login
-
mhwd#get graphics hardware info -
sudo mhwd -r pci video-nvidia#remove nvidia drivers -
if 3. fails because of kernel:
sudo mhwd-kernel -r linux510-rt#remove problematic kernel (ensure other kernels are available to use), then 3. -
sudo mhwd -f -i pci video-nvidia-470xx#reinstall appropriate drivers -
reboot
Downloading drivers can take a a while (no download progress shown)
If you need to connect to network device: nmcli device wifi connect <SSID> password <password>
(having second device, to connect to internet, saved my ass).
2 Likes
okay so something cameup and i had to deal with manjaro later, and now i’m back, here is the output of journalctl
Nov 20 14:05:42 mommys-boy kernel: ata6.00: supports DRM functions and may not be fully accessible
Nov 20 14:05:42 mommys-boy kernel: ata6.00: NCQ Send/Recv Log not supported
Nov 20 14:05:42 mommys-boy kernel: ata6.00: supports DRM functions and may not be fully accessible
Nov 20 14:05:42 mommys-boy kernel: ata6.00: NCQ Send/Recv Log not supported
Nov 20 14:05:42 mommys-boy kernel: usb: port power management may be unreliable
Nov 20 14:05:42 mommys-boy kernel: xhci_hcd 0000:01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000e address=0xff00ffffffef>
Nov 20 14:05:41 mommys-boy systemd-modules-load[248]: Failed to find module 'vboxdrv'
Nov 20 14:05:41 mommys-boy systemd-modules-load[248]: Failed to find module 'vboxnetadp'
Nov 20 14:05:41 mommys-boy systemd-modules-load[248]: Failed to find module 'vboxnetflt'
Nov 20 14:05:47 mommys-boy kernel: xhci_hcd 0000:01:00.0: Abort failed to stop command ring: -110
Nov 20 14:05:47 mommys-boy kernel: xhci_hcd 0000:01:00.0: xHCI host controller not responding, assume dead
Nov 20 14:05:47 mommys-boy kernel: xhci_hcd 0000:01:00.0: HC died; cleaning up
Nov 20 14:05:47 mommys-boy kernel: xhci_hcd 0000:01:00.0: Error while assigning device slot ID
Nov 20 14:05:47 mommys-boy kernel: xhci_hcd 0000:01:00.0: Max number of devices this xHCI host supports is 127.
Nov 20 14:05:47 mommys-boy kernel: usb usb1-port1: couldn't allocate usb_device
Nov 20 14:05:58 mommys-boy kernel: kauditd_printk_skb: 1 callbacks suppressed
Nov 20 14:05:58 mommys-boy kernel: ACPI Warning: SystemIO range 0x0000000000000B00-0x0000000000000B08 conflicts with OpRegion 0x00>
Nov 20 14:05:58 mommys-boy kernel: acpi PNP0C14:01: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on>
Nov 20 14:05:58 mommys-boy kernel: nvidia: loading out-of-tree module taints kernel.
Nov 20 14:05:58 mommys-boy kernel: nvidia: module license 'NVIDIA' taints kernel.
Nov 20 14:05:58 mommys-boy kernel: Disabling lock debugging due to kernel taint
Nov 20 14:05:58 mommys-boy kernel:
Nov 20 14:05:58 mommys-boy kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module 470.63.01 Tue Aug 3 20:44:16 UTC 2021
Nov 20 14:05:58 mommys-boy kernel: kauditd_printk_skb: 5 callbacks suppressed
lines 1-25...skipping...
-- Journal begins at Sat 2021-10-30 20:16:52 GMT, ends at Sun 2021-11-21 12:32:47 GMT. --
Nov 20 14:05:42 mommys-boy kernel: ata6.00: supports DRM functions and may not be fully accessible
Nov 20 14:05:42 mommys-boy kernel: ata6.00: NCQ Send/Recv Log not supported
Nov 20 14:05:42 mommys-boy kernel: ata6.00: supports DRM functions and may not be fully accessible
Nov 20 14:05:42 mommys-boy kernel: ata6.00: NCQ Send/Recv Log not supported
Nov 20 14:05:42 mommys-boy kernel: usb: port power management may be unreliable
Nov 20 14:05:42 mommys-boy kernel: xhci_hcd 0000:01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000e address=0xff00ffffffef9000 flags=0x0000]
Nov 20 14:05:41 mommys-boy systemd-modules-load[248]: Failed to find module 'vboxdrv'
Nov 20 14:05:41 mommys-boy systemd-modules-load[248]: Failed to find module 'vboxnetadp'
Nov 20 14:05:41 mommys-boy systemd-modules-load[248]: Failed to find module 'vboxnetflt'
Nov 20 14:05:47 mommys-boy kernel: xhci_hcd 0000:01:00.0: Abort failed to stop command ring: -110
Nov 20 14:05:47 mommys-boy kernel: xhci_hcd 0000:01:00.0: xHCI host controller not responding, assume dead
Nov 20 14:05:47 mommys-boy kernel: xhci_hcd 0000:01:00.0: HC died; cleaning up
Nov 20 14:05:47 mommys-boy kernel: xhci_hcd 0000:01:00.0: Error while assigning device slot ID
Nov 20 14:05:47 mommys-boy kernel: xhci_hcd 0000:01:00.0: Max number of devices this xHCI host supports is 127.
Nov 20 14:05:47 mommys-boy kernel: usb usb1-port1: couldn't allocate usb_device
Nov 20 14:05:58 mommys-boy kernel: kauditd_printk_skb: 1 callbacks suppressed
Nov 20 14:05:58 mommys-boy kernel: ACPI Warning: SystemIO range 0x0000000000000B00-0x0000000000000B08 conflicts with OpRegion 0x0000000000000B00-0x0000000000000B0F (\GSA1.SMBI) (20210331/ut>
Nov 20 14:05:58 mommys-boy kernel: acpi PNP0C14:01: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:00)
Nov 20 14:05:58 mommys-boy kernel: nvidia: loading out-of-tree module taints kernel.
Nov 20 14:05:58 mommys-boy kernel: nvidia: module license 'NVIDIA' taints kernel.
Nov 20 14:05:58 mommys-boy kernel: Disabling lock debugging due to kernel taint
Nov 20 14:05:58 mommys-boy kernel:
Nov 20 14:05:58 mommys-boy kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module 470.63.01 Tue Aug 3 20:44:16 UTC 2021
Nov 20 14:05:58 mommys-boy kernel: kauditd_printk_skb: 5 callbacks suppressed
Nov 20 14:06:01 mommys-boy kernel: kauditd_printk_skb: 10 callbacks suppressed
Nov 20 14:06:10 mommys-boy kernel: NVRM: GPU 0000:06:00.0: RmInitAdapter failed! (0x24:0x59:1220)
Nov 20 14:06:10 mommys-boy kernel: NVRM: GPU 0000:06:00.0: rm_init_adapter failed, device minor number 0
Nov 20 14:06:10 mommys-boy kernel: NVRM: GPU 0000:06:00.0: RmInitAdapter failed! (0x24:0x59:1220)
Nov 20 14:06:10 mommys-boy kernel: NVRM: GPU 0000:06:00.0: rm_init_adapter failed, device minor number 0
Nov 20 14:06:11 mommys-boy kernel: NVRM: GPU 0000:06:00.0: RmInitAdapter failed! (0x24:0x59:1220)
Nov 20 14:06:11 mommys-boy kernel: NVRM: GPU 0000:06:00.0: rm_init_adapter failed, device minor number 0
Nov 20 14:06:11 mommys-boy kernel: NVRM: GPU 0000:06:00.0: RmInitAdapter failed! (0x24:0x59:1220)
Nov 20 14:06:11 mommys-boy kernel: NVRM: GPU 0000:06:00.0: rm_init_adapter failed, device minor number 0
Nov 20 14:06:11 mommys-boy systemd[1]: lightdm.service: Failed with result 'exit-code'.
Nov 20 14:06:11 mommys-boy kernel: NVRM: GPU 0000:06:00.0: RmInitAdapter failed! (0x24:0x59:1220)
Nov 20 14:06:11 mommys-boy kernel: NVRM: GPU 0000:06:00.0: rm_init_adapter failed, device minor number 0
Nov 20 14:06:12 mommys-boy kernel: NVRM: GPU 0000:06:00.0: RmInitAdapter failed! (0x24:0x59:1220)
Nov 20 14:06:12 mommys-boy kernel: NVRM: GPU 0000:06:00.0: rm_init_adapter failed, device minor number 0
as for mhwd-kernel it’s :
Currently running: 5.10.42-1-MANJARO (linux510)
The following kernels are installed in your system:
* linux414
* linux513
for mhwd --listinstalled it’s:
> Installed PCI configs:
--------------------------------------------------------------------------------
NAME VERSION FREEDRIVER TYPE
--------------------------------------------------------------------------------
video-nvidia 2020.11.30 false PCI
video-linux 2018.05.04 true PCI
Warning: No installed USB configs!
what can i do?
under chroot ,
first suppress theses config files
rm /etc/mhwd.d/nvidia.conf remove video-linux
mhwd -r pci video-linux remove first theses kernels
mhwd-kernel -r linux513
mhwd-kernel -r linux414add then theses kernel
mhwd-kernel -i linux510
mhwd-kernel -i linux514
mhwd-kernel -i linux515
then exit ( end chroot )and you can reboot
1 Like
Thanks.
Thanks(EN).
Obrigado(Pt-Br).
I tried to do mhwd-kernel -i linux510 514 and 515
With linux510 it installed normally but when it comes to linux 514 and 515 i thought it would work out the same but it says failed to synchronize all databases (ubanle to lock database) when i try to repond with y to do you want to continue anyway ? [y/N] it says that the target is not specified
I think I’m just going to make a new partition and install manjaro on it
I’ve done it myself. Sometimes, that’s quicker and easier, especially if no downtime, or troubleshoot, or struggling time can be afforded. Although, it’s NEVER as satisfying as fixing a problem.