Tiny Core Base > piCore Test Releases

piCore14.0 Beta

<< < (17/24) > >>

Rich:
Hi aus9

--- Quote from: aus9 on June 03, 2023, 01:06:56 AM ---Using the editted Timeout xsession settings from power on to failed in waitforX took 36 seconds.

 ----- Snip -----

Rich I have in that dir dmesg-timeout.txt and xorg-timeout.txt
this can be compared to a working dmesg-sleep.txt and xorg-sleep.txt ...
--- End quote ---
In the timeout version  /dev/dri/card0  is found but not used. It then tries to use  /dev/fb0
which does not exist and then gives up.

In the sleep version  /dev/dri/card0  is found, but so is  /dev/dri/card1  which is what Xorg
winds up using.

Try changing it to this so it tests for both of them:

--- Code: ---Timeout=40
while [ $Timeout -gt 0 ]
do
[ -e /dev/dri/card0 ] && [ -e /dev/dri/card1 ] && break
Timeout=$(($Timeout - 1))
sleep 0.25
done
--- End code ---

aus9:
Hi Rich
that worked well....acceleration proved using prev commands. Too late for me to upload files but it works. I will test again tomorrow thanks

aus9:
Hi Rich
time from power on to desktop with new .xsession as per last post is about the same. The dmesg timestamps give your TIMEOUT a one second lead to be the new winner

Whats a second between friends  :D

If interested I have uploaded dmesg-rich.txt and xorg-rich.txt to same dir
https://ln5.sync.com/dl/ab5f2e950/im3994fv-bvcpbmst-dxabzv4b-62dehkes

Obviously what TCEs I load, what I have in backup will impact on other members boot up time if I choose to load Xorg-3d instead of normal Xorg.

Rich:
Hi aus9

--- Quote from: aus9 on June 03, 2023, 10:47:16 PM --- ... The dmesg timestamps give your TIMEOUT a one second lead to be the new winner ...
--- End quote ---
The sleep method will always wait 6 seconds regardless of if or when the  /dev/dri/  entries show up.
The Timeout method will only wait as long the  /dev/dri/  entries are not present up to a max of 10 seconds.

If you want to see the actual time spent in the Timeout code, you can
add a command to save the elapsed time to a file:

--- Code: ---Timeout=40
while [ $Timeout -gt 0 ]
do
[ -e /dev/dri/card0 ] && [ -e /dev/dri/card1 ] && break
Timeout=$(($Timeout - 1))
sleep 0.25
done

calc '(40-'$Timeout')*.25' > Timeout.txt
--- End code ---
The  Timeout.txt  file in your home directory will contain how many seconds it
had to wait for the  /dev/dri/  entries to show up.

Remember, the time it takes for the  /dev/dri/  entries to show up can vary with
changes made to the contents and order of extensions in your  onboot.lst  file.

aus9:
thanks Rich

to anyone piCore64-14.x
I think we may have a missing dep for firefox-perf
I have loaded a new desktop not yet ready for submission and I notice

--- Code: ---tc@box:~$ firefox-perf
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: libpci missing (t=3.57427) [GFX1-]: glxtest: libpci missing
JavaScript error: resource://gre/modules/PromiseWorker.jsm, line 106: Error: Could not get children of file(/home/tc/.cache/mozilla/firefox/0npiijyc.default-default/thumbnails) because it does not exist
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: libpci missing (t=3.57427) |[1][GFX1-]: Unrecognized feature VIDEO_OVERLAY (t=11.075) [GFX1-]: Unrecognized feature VIDEO_OVERLAY
^CExiting due to channel error.

tce-load -i libpci
firefox-perf # runs as expected
--- End code ---

I may not have noticed before as I had inxi in my boot list which pulls pciutils dep of libpci?

Navigation

[0] Message Index

[#] Next page

[*] Previous page