var/log/Xorg.0.log file ~]# cat /var/log/Xorg.0.log X.Org X Server 1.21.1.4 X Protocol Version 11, Revision 0 Current Operating System: Linux chuwi-domek 5.10.86_64 #1 SMP Mon Mar 8 00:24: x86_64 Kernel command line: BOOT_IMAGE=(hd0,gpt3)/vmlinuz-5.10.86_64 root=UUID=d476cc5d-445e-4260-9ee6-263971e37650 ro rootflags=subvol=fedora resume=UUID=64fc58e8-d90f-4235-b66e-ae87b548f320 nomodeset Build ID:xorg-x11-server 21.1.4-2.fc35 Current version of pixman: 0.40.0 Before reporting problems, check to make sure that you have the latest version. xinit: giving up xinit: unable to connect to X server: Connection refused xinit: server error (EE) (EE) Server terminated with error (1). (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. (=) Log file: "/var/log/Xorg.0.log", Time: Mon Sep 5 04:12:15 2022 (=) Using config directory: "/etc/X11/" (=) Using system config directory "/usr/share/X11/" (EE) Fatal server error: (EE) no screens found(EE) (EE) Please consult the G2V Project support at for help. Markers: (-) probed, (**) from config file, (=) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (?) unknown. I also hoped to learn something, but the only lesson learned was "thrust linux even less than before".Startx xauth: file /root/.serverauth.8928 does not exist X.Org X Server 1.21.1.4 X Protocol Version 11, Revision 0 Current Operating System: Linux chuwi-domek 5.10.86_64 #1 SMP Mon Mar 8 00:24: x86_64 Kernel command line: BOOT_IMAGE=(hd0,gpt3)/vmlinuz-5.10.86_64 root=UUID=d476cc5d-445e-4260-9ee6-263971e37650 ro rootflags=subvol=fedora resume=UUID=64fc58e8-d90f-4235-b66e-ae87b548f320 nomodeset Build ID:xorg-x11-server 21.1.4-2.fc35 Current version of pixman: 0.40.0 Before reporting problems, check to make sure that you have the latest version. Good thing I did not thrust linux and saved everything in other hdds (btw, thanks ubuntu to make changing default folders so tricky). I'm recovering some files from windows and wiping out everything fresh.īut it's really a bad feeling knowing you can screw everything by sneezing too loud near the computer. I think I'm done here, I really need a working machine and I have already lost three days. :)Īctually the day before I installed some updates from the ubuntu software center thing, thought it was safe. History command works (logs 600-ish lines), but I tried history > history_for_print.txt and when I rebooted to windows, the file was empy. If it doesn't go, do you know if you installed updates or maybe used the 'drivers' UI and selected another video driver before you last rebooted? If you ran anything in the terminal, you can use the 'history' command to see if you previously ran that might've caused thisdone that, but it did not fix the issue :( Sudo rebootEDIT: I see you've tried this already, but can you give it another go, this time by ensuring you have the latest updates installed (added to the command list). Sudo apt-get install -reinstall xserver-xorg-core libgl1-mesa-glx:i386 libgl1-mesa-dri:i386 libgl1-mesa-glx:amd64 libgl1-mesa-dri:amd64
0 Comments
Leave a Reply. |