startx "no screens found" lfs 7.7

Mihail Zenkov · 09-23-2015, 04:36 AM

Wayne Sallee
You place xorg.conf to wrong dir - xorg-server just ignore it and use defaults:
[ 2043.173] (==) Using system config directory "/usr/share/X11/xorg.conf.d"

In my system I see:
[ 5.066] (==) Using config file: "/etc/xorg.conf"]

But this not standard path - I build xorg-server with --sysconfdir=/etc. You can find all standard path in 'man xorg.conf'.

Wayne Sallee · 09-24-2015, 11:05 AM

I moved the hard drive to another laptop that has Intel graphics.

When it booted up it started out with regular sized text, and then suddenly changed to smaller text. So I knew the graphics card was working. Then when I entered startx, it started up X.

I still want it to work on other laptops as well, but at least I have X now on this laptop.

It's good that Intel is more Linux friendly than AMD.

Wayne Sallee
Wayne@WayneSallee.com

Luridis · 09-24-2015, 12:42 PM

Quote:

Originally Posted by Wayne Sallee

I moved the hard drive to another laptop that has Intel graphics.

When it booted up it started out with regular sized text, and then suddenly changed to smaller text. So I knew the graphics card was working. Then when I entered startx, it started up X.

I still want it to work on other laptops as well, but at least I have X now on this laptop.

It's good that Intel is more Linux friendly than AMD.

Wayne Sallee
Wayne@WayneSallee.com

The issues with hardware & FOSS are more complicated than that I believe. Between industry consortia and hardware vendor's ambitions, it really is a wonder anything works at all. The fact that there is an open standard of any kind is miraculous and the existence of the "PC" platform completely the result of a tech giant's blunder and a young Harvard student's skill at playing poker.

anak_bawang · 10-01-2015, 11:16 PM

Quote:

Originally Posted by Wayne Sallee

After building X and getting to the instructions to startx I get:

Code:

(EE)
Fatal server error:
(EE) no screens Found (EE)

Wayne Sallee
Wayne@WayneSallee.com

I have same problem, and this works for me.
First, Added some line on -> /etc/X11/xorg.conf.d/xkb-defaults.conf

Code:

Section "InputClass"
    Identifier "XKB Defaults"
    MatchIsKeyboard "yes"
    Option "XkbOptions" "terminate:ctrl_alt_bksp"
EndSection

Section "Screen"
        Identifier "Screen0"
        Device     "Videocard0"
        SubSection "Display"
                Viewport   0 0
                Depth    32
                Modes "1024x768"
        EndSubSection
EndSection

Second, "comment" one line on -> /etc/X11/xorg.conf.d/server-layout.conf

Code:

Section "ServerLayout"
    Identifier     "DefaultLayout"
    Screen      0  "Screen0" 0 0
#    Screen      1  "Screen1" LeftOf "Screen0"
    Option         "Xinerama"
EndSection

Third, because my LFS on vmware -> /etc/X11/xorg.conf.d/videocard-0.conf

Code:

Section "Device"
    Identifier  "Videocard0"
    Driver      "vmware"
    VendorName  "VMWare Inc."
    BoardName   "VMware SVGA II Adapter"
    Option      "NoAccel" "true"
EndSection

Probably should make some adjustment, and I hope this also works for you.

Wayne Sallee · 10-02-2015, 08:25 AM

I deleted the unneeded xorg config files, and let xorg figure it out itself.

I got X to work by using a laptop that has Intel for graphics.

I still want to get other video drivers to work, but now I'm in a situation that I'm working through on the blfs mailing list where my system won't compile on a different computer. After I get that fully investigated, and fixed, I'll go back to getting more drivers to work, and more X functions. I'm no longer interested in having Virtualbox drivers.

I'm basically past the phase of running it inside a virtual environment, other than working through this compile snag.

Are you able to get Vesa or other generic video driver to work inside VMware?

Wayne Sallee
Wayne@WayneSallee.com

Luridis · 10-02-2015, 01:04 PM

In vmware several drivers work: vbe vgafb simplefb, etc. But, in the DRI subsystem only the vmware stack works.

The compile snag could be optimization. Even if you're not using -march=native, a lot of times GCC will automatically do that. If you need to make sure something you build one place is functional elsewhere use -mtune=generic or -march=i686. If you know the exact architecture of the target it's safe to tune for it if it's compatible. (Remember /tools gets executed on the build host, and is slowly replaced by what you're building in the chroot's bin folders.) For instance, my desktop is Haswell and my laptop is Ivy Bridge, so I can compile on the desktop for the laptop's native by -march=core-avx-i, but it will boot on either.

Luridis · 10-02-2015, 01:17 PM

Almost forgot, -march=x86_64 is the generic version for 64 bit builds.

anak_bawang · 10-03-2015, 12:39 AM

Quote:

Originally Posted by Wayne Sallee

I got X to work by using a laptop that has Intel for graphics.

Have you ever look at this site
http://xorg.freedesktop.org/archive/individual/driver/

and try the latest release intel video driver
http://xorg.freedesktop.org/archive/...99.917.tar.bz2

Quote:

Originally Posted by Wayne Sallee

Are you able to get Vesa or other generic video driver to work inside VMware?

Yes Vesa and VGA driver work inside vmware in low resolution, so I prefer using vmware driver.

But vmware mouse doesn't work, change to standard mouse driver, and works properly.
(http://xorg.freedesktop.org/archive/...e-1.9.1.tar.gz)
In this case I have to change some configuration

Code:

rm -vf $XORG_PREFIX/share/X11/xorg.conf.d/50-vmmouse.conf

cat > $XORG_PREFIX/share/X11/xorg.conf.d/50-mouse.conf << "EOF"
Section "InputClass"
        Identifier      "mouse"
        MatchIsPointer  "on"
        MatchTag        "mouse"
        Driver          "mouse"
EndSection
EOF