Tiny Core Base > Raspberry Pi

failed in wait for X piCore16.0 on Raspi2,3,4 and 5

(1/2) > >>

beerstein:
Hi:
No matter what I do, i am not able to get the small GUI running on my Rspis. I always get the message:
"failed in wait for X" after booting or after:
$ startx

I looked at the .xsession file:


--- Code: ---Xorg -nolisten tcp &
export XPID=$!
waitforX || ! echo failed in waitforX || exit
--- End code ---
and so on...

is this this right way the X server gets started?
The Xorg.0.log file generates a:

Fatal server  error
no screens found

There must be something missing here. Please can somebody help?

Have not posted for a while here, but recently I used piCore with an older Raspi and USB Wifi dongle
as an AC/P and WIF bridge.
Just via the CLI - Works great with this, but I can not a simple GUI. I installed he TC.tcz

    [Edit]: Added code tags.  Rich

Juanito:
Run just the command "Xorg -nolisten tcp" and see if you get an error.

Edit: correct command above

beerstein:
Thank you so much:.
Here is the result of the command:


--- Code: ---$ Xorg-nolisten tcp
-sh: Xorg-nolisten: not found
--- End code ---

When I type:
$ Xorg

I am getting screen messages similar to the info inside the Xorg.0.log log file. Below is part of it:


--- Code: ---[    54.215] (II) LoadModule: "modesetting"
[    54.215] (II) Loading /usr/local/lib/xorg/modules/drivers/modesetting_drv.so
[    54.216] (EE) Failed to load /usr/local/lib/xorg/modules/drivers/modesetting_drv.so: libgbm.so.1: cannot open shared object file: No such file or directory
[    54.216] (EE) Failed to load module "modesetting" (loader failed, 0)
[    54.216] (EE) No drivers available.
[    54.216] (EE) Fatal server error:
[    54.216] (EE) no screens found(EE)
[    54.216] (EE) Please consult the The X.Org Foundation support
at http://wiki.x.org for help.
[    54.216] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[    54.216] (EE)
[    54.216] (EE) Server terminated with error (1). Closing log file.
--- End code ---
Drivers might be missing?

What do you think?

    [Edit]: Added code tags.  Rich

Juanito:
Sorry, the command was mis-stated, it should have been "Xorg -nolisten tcp".

If you reboot and do the following:
--- Code: ---tce-load -i Xorg-3d flwm aterm wbar
startx
--- End code ---
..things should work

Note that you need to check that you have dtoverlay=vc4-kms-v3d in config.txt for the RPi you are using

Rich:
Hi beerstein

Please use  Code Tags  when posting commands and responses seen in a terminal. To use  Code Tags  click on the  #  icon
above the reply box and paste your text between the  Code Tags  as shown in this example:


--- Quote ---[code][   36.176529] pcm512x 1-004d: Failed to get supply 'AVDD': -517
[   36.176536] pcm512x 1-004d: Failed to get supplies: -517
[   36.191753] pcm512x 1-004d: Failed to get supply 'AVDD': -517[/code]
--- End quote ---

It will appear like this in your post:

--- Code: ---[   36.176529] pcm512x 1-004d: Failed to get supply 'AVDD': -517
[   36.176536] pcm512x 1-004d: Failed to get supplies: -517
[   36.191753] pcm512x 1-004d: Failed to get supply 'AVDD': -517
--- End code ---

Code Tags  serve as visual markers between what you are trying to say and the information you are posting. They also preserve
spacing so column aligned data displays properly. Code tags also automatically add horizontal and or vertical scrollbars
to accommodate long lines and listings.

Navigation

[0] Message Index

[#] Next page