troubleshooting Question

Desktop on Debian no longer accessible.

Avatar of Johnny
JohnnyFlag for United States of America asked on
Linux* VNCDisplays / Monitors* Debian
4 Comments1 Solution78 ViewsLast Modified:
I have a Debian 7 system.  On boot up it offers three choices, log into the server, log into the desktop, or the recovery console.
The Desktop option is the option typically used, and contains access to the program currently being used to print protective masks in the New Jersey area for
use in the Covid fight.  On selection of this, the system beings to load until it drops out to a blinking cursor.

The following is the contents of the Xorg.0.log file
Any thoughts would help.  I believe the client was running VNC of some flavor.  I am still looking to locate which version.
Please let me know what I can do to get the desktop to come back to life.

Thank you

[  3597.437] drmOpenDevice: node name is /dev/dri/card12
[  3597.441] drmOpenDevice: node name is /dev/dri/card13
[  3597.445] drmOpenDevice: node name is /dev/dri/card14
[  3597.449] drmOpenDevice: node name is /dev/dri/card15
[  3597.453] (EE) [drm] failed to open device
[  3597.453] vesa: Ignoring device with a bound kernel driver
[  3597.453] (WW) Falling back to old probe method for vesa
[  3597.453] (II) Loading sub module "fbdevhw"
[  3597.453] (II) LoadModule: "fbdevhw"
[  3597.453] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[  3597.454] (II) Module fbdevhw: vendor="X.Org Foundation"
[  3597.454]    compiled for 1.12.4, module version = 0.0.2
[  3597.454]    ABI class: X.Org Video Driver, version 12.1
[  3597.454] (EE) open /dev/fb0: No such file or directory
[  3597.454] (WW) Falling back to old probe method for fbdev
[  3597.454] (II) UnloadModule: "vesa"
[  3597.454] (II) UnloadModule: "fbdev"
[  3597.454] (II) UnloadSubModule: "fbdevhw"
[  3597.454] (EE) Screen(s) found, but none have a usable configuration.
[  3597.454]
Fatal server error:
[  3597.454] no screens found
[  3597.454]
Please consult the The X.Org Foundation support
         at http://wiki.x.org
 for help.
[  3597.454] Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[  3597.454]
[  3597.462] Server terminated with error (1). Closing log file.


[  3597.453] (EE) [drm] failed to open device
[  3597.453] vesa: Ignoring device with a bound kernel driver
[  3597.453] (WW) Falling back to old probe method for vesa
[  3597.453] (II) Loading sub module "fbdevhw"
[  3597.453] (II) LoadModule: "fbdevhw"
[  3597.453] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[  3597.454] (II) Module fbdevhw: vendor="X.Org Foundation"
[  3597.454]    compiled for 1.12.4, module version = 0.0.2
[  3597.454]    ABI class: X.Org Video Driver, version 12.1
[  3597.454] (EE) open /dev/fb0: No such file or directory
[  3597.454] (WW) Falling back to old probe method for fbdev
[  3597.454] (II) UnloadModule: "vesa"
[  3597.454] (II) UnloadModule: "fbdev"
[  3597.454] (II) UnloadSubModule: "fbdevhw"
[  3597.454] (EE) Screen(s) found, but none have a usable configuration.
[  3597.454]
Fatal server error:
[  3597.454] no screens found
[  3597.454]
Please consult the The X.Org Foundation support
         at http://wiki.x.org
 for help.
[  3597.454] Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[  3597.454]
[  3597.462] Server terminated with error (1). Closing log file.
Join the community to see this answer!
Join our exclusive community to see this answer & millions of others.
Unlock 1 Answer and 4 Comments.
Join the Community
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 1 Answer and 4 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros