Difference between revisions of "How to resolve the "fatal server error: no screen found""

From GhostBSD Wiki
Jump to: navigation, search
m
 
m (4 revisions imported)
 
(3 intermediate revisions by one other user not shown)
Line 1: Line 1:
 
<noinclude>{{NavHeader|back=Using pkgsrc Package Management|forward=How to resolve the "fatal server error: no screen found"}}</noinclude>
 
<noinclude>{{NavHeader|back=Using pkgsrc Package Management|forward=How to resolve the "fatal server error: no screen found"}}</noinclude>
== Problem ==
+
<languages/>
 +
<translate>
 +
== Problem == <!--T:1-->
  
== Solution ==
+
== Solution == <!--T:2-->
  
 +
<!--T:3-->
 
The solution (written by the [http://forums.ghostbsd.org/memberlist.php?mode=viewprofile&u=161 user ''A-dog'' of the GhostBSD forums])<sup>[http://forums.ghostbsd.org/viewtopic.php?f=59&t=24&start=20#p511 forums: topic ''<nowiki>[</nowiki>Solved<nowiki>]</nowiki> Fatal server error - no screens found'']</sup> was successfully working on a ''HP&nbsp;Compaq&nbsp;NX&nbsp;6310'' (laptop of [[User:Paolo|Paolo]]).
 
The solution (written by the [http://forums.ghostbsd.org/memberlist.php?mode=viewprofile&u=161 user ''A-dog'' of the GhostBSD forums])<sup>[http://forums.ghostbsd.org/viewtopic.php?f=59&t=24&start=20#p511 forums: topic ''<nowiki>[</nowiki>Solved<nowiki>]</nowiki> Fatal server error - no screens found'']</sup> was successfully working on a ''HP&nbsp;Compaq&nbsp;NX&nbsp;6310'' (laptop of [[User:Paolo|Paolo]]).
  
===== becoming <code>root</code> =====
+
===== becoming <code>root</code> ===== <!--T:4-->
  
 +
<!--T:5-->
 
Load the cd/dvd and get to the cli to login.
 
Load the cd/dvd and get to the cli to login.
  
 +
<!--T:6-->
 
To becoming ''root'' by typing
 
To becoming ''root'' by typing
 
: <code>su</code>
 
: <code>su</code>
 
. Of course you have to use the passphrase for your root-account.
 
. Of course you have to use the passphrase for your root-account.
  
===== editing <code>/etc/X11/xorg.conf</code> =====
+
===== editing <code>/etc/X11/xorg.conf</code> ===== <!--T:7-->
  
 +
<!--T:8-->
 
To edit a file we need an editor. In this example we will use ''ee'', which is installed by default.
 
To edit a file we need an editor. In this example we will use ''ee'', which is installed by default.
  
 +
<!--T:9-->
 
Open the file with the editor ''[https://www.freebsd.org/cgi/man.cgi?query=ee ee]'' by typing
 
Open the file with the editor ''[https://www.freebsd.org/cgi/man.cgi?query=ee ee]'' by typing
 
: <code>ee /etc/X11/xorg.conf</code>
 
: <code>ee /etc/X11/xorg.conf</code>
 
.
 
.
  
 +
<!--T:10-->
 
Go down to where the driver is identified. This section of the file begins with
 
Go down to where the driver is identified. This section of the file begins with
 
<pre>
 
<pre>
Line 28: Line 36:
 
.
 
.
  
 +
<!--T:11-->
 
There you can change the driver to ''vesa'' by having
 
There you can change the driver to ''vesa'' by having
 
<pre>
 
<pre>
Line 34: Line 43:
 
in your file.
 
in your file.
  
 +
<!--T:12-->
 
For leaving ''ee'' and saving the file <code>xorg.conf</code>,
 
For leaving ''ee'' and saving the file <code>xorg.conf</code>,
 
* press the key <tt>esc</tt>,
 
* press the key <tt>esc</tt>,
Line 40: Line 50:
 
.
 
.
  
===== leaving <code>root</code> =====
+
===== leaving <code>root</code> ===== <!--T:13-->
  
 +
<!--T:14-->
 
End the session as root, type
 
End the session as root, type
 
: <code>[https://www.freebsd.org/cgi/man.cgi?query=exit exit]</code>
 
: <code>[https://www.freebsd.org/cgi/man.cgi?query=exit exit]</code>
 
and you are back as the formal user.
 
and you are back as the formal user.
  
===== starting x =====
+
===== starting x ===== <!--T:15-->
  
 +
<!--T:16-->
 
Initialize the X&nbsp;session by typing
 
Initialize the X&nbsp;session by typing
 
: <code>[https://www.freebsd.org/cgi/man.cgi?query=startx startx]</code>
 
: <code>[https://www.freebsd.org/cgi/man.cgi?query=startx startx]</code>
 
.
 
.
  
 +
<!--T:17-->
 
Now you need to wait until the X&nbsp;server load for you.
 
Now you need to wait until the X&nbsp;server load for you.
  
=== Additional info for the solution ===
+
=== Additional info for the solution === <!--T:18-->
  
 +
<!--T:19-->
 
On a ''Acer Aspire One 532'' (''GMA 3150'') you had to add the line 'Modes' to the <code>/etc/X11/xorg.conf</code>
 
On a ''Acer Aspire One 532'' (''GMA 3150'') you had to add the line 'Modes' to the <code>/etc/X11/xorg.conf</code>
 
<pre>
 
<pre>
Line 67: Line 81:
 
</pre>
 
</pre>
 
.
 
.
 +
</translate>

Latest revision as of 20:26, 8 October 2016

Previous: Using pkgsrc Package Management Return to Table of Contents Next: How to resolve the "fatal server error: no screen found"
How to resolve the "fatal server error: no screen found"


Problem[edit]

Solution[edit]

The solution (written by the user A-dog of the GhostBSD forums)forums: topic [Solved] Fatal server error - no screens found was successfully working on a HP Compaq NX 6310 (laptop of Paolo).

becoming root[edit]

Load the cd/dvd and get to the cli to login.

To becoming root by typing

su

. Of course you have to use the passphrase for your root-account.

editing /etc/X11/xorg.conf[edit]

To edit a file we need an editor. In this example we will use ee, which is installed by default.

Open the file with the editor ee by typing

ee /etc/X11/xorg.conf

.

Go down to where the driver is identified. This section of the file begins with

Section "Device"

.

There you can change the driver to vesa by having

        Driver      "vesa"

in your file.

For leaving ee and saving the file xorg.conf,

  • press the key esc,
  • press the key a and then
  • press the key a

.

leaving root[edit]

End the session as root, type

exit

and you are back as the formal user.

starting x[edit]

Initialize the X session by typing

startx

.

Now you need to wait until the X server load for you.

Additional info for the solution[edit]

On a Acer Aspire One 532 (GMA 3150) you had to add the line 'Modes' to the /etc/X11/xorg.conf

Section "Screen"
SubSection "Display"
	Depth	24
	Modes	"1024x600" "800x600"
EndSubSection 

.