![]() Model name : Intel(R) Core(TM) i9-9900K CPU 3. M 3dnowprefetch invpcid_single pti fsgsbase bmi1 hle avx2 bmi2 erms invpcid rtm rdseed xsaveopt arat md_clearīugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs taa itlb_multihit srbdsĪddress sizes : 39 bits physical, 48 bits virtual _good nopl xtopology nonstop_tsc cpuid pni pclmulqdq dtes64 ds_cpl ssse3 sdbg fma cx16 xtpr pcid sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand hypervisor lahf_lm ab Model name : Intel(R) Core(TM) i9-9900K CPU 3.60GHzįlags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss ht pbe syscall nx pdpe1gb rdtscp lm constant_tsc rep Last login: Wed Nov 3 20:30:53 2021 from cat /proc/cpuinfo Individual files in /usr/share/doc/*/copyright.ĭebian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent The exact distribution terms for each program are described in the The programs included with the Debian GNU/Linux system are free software I've thought that the cause was that my monitor was very very old,but I've used another monitor and I saw the same error. Xinit: unable to connect to X server: Connection refused (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. Please consult the The X.Org Foundation support You can start the desktop environment using the startx command. (EE) AddScreen/ScreenInit failed for driver 0 If you restart the server, it will open the terminal again. can open an SSH session to your RPi, you will be able to access it without a screen. (=) Using system config directory "/usr/share/X11/" You are using your Raspberry Pi as an internet. (WW) warning, (EE) error, (NI) not implemented, (?) unknown. (++) from command line, (!!) notice, (II) informational, Markers: (-) probed, (**) from config file, (=) default setting, To make sure that you have the latest version. # nvidia-xconfig: X configuration file generated by nvidia-xconfigĬurrent Operating System: Linux marietto-BHYVE 5.10.0-9-amd64 #1 SMP Debian 5.10.70-1 () x86_64 New X configuration file written to nano /etc/X11/nf WARNING: Unable to locate/open X configuration file. It appears that in the above situations, Linux does not correctly report graphical updates to be captured by VNC Server. UUID : GPU-74c6f81e-9e6c-f279-2878-2d28f4333f6b The issue is most commonly seen when connecting to a computer with no monitors attached (headless), or a monitor using HDMI/DisplayPort is connected but powered off. I’ve attached an old monitor to the HDMI port of the graphic card and I tried to run “startx” from the Linux terminal and this is what happened : nvidia-xconfig -query-gpu-info ![]() Sorry for going so much into the details - but I hope a rather long description helps someone who has the same issue as I did.Screenshot_20211102_191816 1920×1080 447 KB I do not know of the consequences kicking out the driver, but at least the desktop was back up and I could connect with VNC again.īTW: On the same thread somebody mentions that one can get the fbturbo working with this tutorial, but I did not try (yet). Looking around with apt-cache I can see the currently install module is xorg-video-abi-24 and the demanded xorg-video-abi-23 does not exist for buster.ĭownloaded the package here and installed it manually.Įventually found the solution here : Remove the fbturbo driver with sudo mv /usr/share/X11//nf ~ Tried sudo apt-get install xserver-xorg-video-fbturbo but no success. Sudo apt full-upgrade completed without error.īut still no X server, still no display found in the Xorg.0.log, still the "Failed to load module 'fbturbo'" error. ![]() My root cause was, that I forgot to update the: /etc/apt//raspi.list from stretch to busterĪfter replacing 'stretch' in the raspi.list, sudo apt update reported an additional ~ 200 packages that could be upgraded. (I copy the essential information from there) With that info I stumbled upon this post. So I tried out all the ways to config the pi in headless modeĮditing the config.txt for fixed hdmi modes (see here), fiddeling with raspi-config, updating the firmware - nothing worked.Įventuall a look into the Xorg.0.log (in /var/log/) showed this: "Failed to load module 'fbturbo'". After enabling ssh, I could figure out that the xserver did not start.
0 Comments
Leave a Reply. |