Tiny Core Linux

Tiny Core Base => Raspberry Pi => Topic started by: beerstein on March 11, 2026, 04:44:24 PM

Title: failed in wait for X piCore16.0 on Raspi2,3,4 and 5
Post by: beerstein on March 11, 2026, 04:44:24 PM

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: [Select]

Xorg -nolisten tcp &
export XPID=$!
waitforX || ! echo failed in waitforX || exit

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

Title: Re: failed in wait for X piCore16.0 on Raspi2,3,4 and 5
Post by: Juanito on March 11, 2026, 06:35:47 PM

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

Edit: correct command above

Title: Re: failed in wait for X piCore16.0 on Raspi2,3,4 and 5
Post by: beerstein on March 12, 2026, 05:22:16 AM

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

Code: [Select]

$ Xorg-nolisten tcp
-sh: Xorg-nolisten: not found

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: [Select]

[    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.

Drivers might be missing?

What do you think?

[Edit]: Added code tags. Rich

Title: Re: failed in wait for X piCore16.0 on Raspi2,3,4 and 5
Post by: Juanito on March 12, 2026, 05:56:59 AM

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

If you reboot and do the following:

Code: [Select]

tce-load -i Xorg-3d flwm aterm wbar
startx

..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

Title: Re: failed in wait for X piCore16.0 on Raspi2,3,4 and 5
Post by: Rich on March 12, 2026, 09:02:52 AM

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]

It will appear like this in your post:

Code: [Select]

[   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 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.

Title: Re: failed in wait for X piCore16.0 on Raspi2,3,4 and 5
Post by: MrPorcine on March 13, 2026, 04:42:41 PM

I use X without a display manager as well. Here is how I start up my app (dviii_m)

Code: [Select]

#wait for framebuffer
Timeout=0
while [ $Timeout -lt 40 ] ; do
	[ -c /dev/fb0 ] && break 
	Timeout=$(($Timeout + 1 ))
	sleep 0.25
done
export DISPLAY=":0.0"
/usr/local/bin/Xorg -retro -s 0 vt07 &
sleep 2
/opt/DynaViewIII/bin/dviii_m /dev/ttyAMA0 &>/opt/dviii.log &

X takes a while to start up, I have to use the sleep command to make sure it's ready. I've used

Code: [Select]

/usr/local/bin/startx /opt/DynaViewIII/bin/dviii_m /dev/ttyAMA0 -- -retro -s 0 vt07

And it sometimes works. :(
This script is run in the init process, so everything is as root. It works on a pi 3 and pi 4, I don't know about others.

Title: Re: failed in wait for X piCore16.0 on Raspi2,3,4 and 5
Post by: beerstein on March 16, 2026, 11:28:31 AM

Thank you mrporcine:
I do not understand your response.
How does your script look like?
What is the name of the script ?
Where does the script go within the file system?

BTW: I switched to piCore 15.0..0 and here I can install a GUI using the TC.tcz

I have no idea what the problem with piCore 16.0.0 might be.

Title: Re: failed in wait for X piCore16.0 on Raspi2,3,4 and 5
Post by: MrPorcine on March 16, 2026, 12:05:08 PM

I should have said before that I am using a Raspberry Pi display (the original, not the Display 2).
A startup script would normally be in /etc/init.d and have a link in /etc/rc3.d. In my case I keep all my private scripts in /opt, so the chain is like this:
/etc/rc3.d/S80startdv -> /etc/init.d/startdv -> /opt/startdv
where each file is a symbolic link to the next.
The actual startdv is as follows

Code: [Select]

 #!/bin/bash
export DISPLAY=":0.0"
Xorg -retro -s 0 vt07 &
sleep 2
/opt/DynaViewIII/bin/dviii_m /dev/ttyAMA0 >/opt/dviii.log 2>&1 &

This is a real shortcut and does not follow the normal guidelines for startup scripts in /etc/init.d. You might want to look at other scripts in init.d and follow their pattern. A more normal way of starting an X11 app would be:

Code: [Select]

startx /opt/DynaViewIII/bin/dviii_m /dev/ttyAMA0 >/opt/dviii.log 2>&1 -- -retro -s 0 vt07 &You need the ampersand ("&") as startx normally does not return until the app quits. As I mentioned before, startx doesn't always work for me. I have another system where I have using a Display 2 and using xrandr to rotate it. In this case startx works but calling Xorg directly doesn't rotate the screen. So YMMV.