Tiny Core Linux
Tiny Core Extensions => TCE Q&A Forum => Topic started by: floppy on December 20, 2011, 04:14:49 PM
-
hello,
the boot time on my desktop is increasing from 46s (xorg74) to 69s (xorg76).
xorg76 is good because it goes to 1000x700 (instead of 800x600 at xorg74).
Has somebody any idea how to speed up the xorg setup at boot?
It seems to be hanging a bit at a mga module loding.
see log file.
Any idea ist welcome.
(xorg74 is for allowing to receive skype video.
xvesa boot time is quicker and approx 36s but dont work with skype).
-
xorg76 is good because it goes to 1000x700 (instead of 800x600 at xorg74).
you should be able to get the same thing with the right xorg.conf in xorg74, no?
-
With the same conf file
- after long months of try with xorg74 I could not get a better resolution than 800x600
- xorg76 goes immediatly to higher definition (with the first cold start this morning, It needed only 54s: funny, probably the hardware has an influence)
Perhaps there is a solution; but did not find it. Except changing to xorg76.
Here is my conf file in the attachment (a bit dirty I must say..).
-
you could try xorg76 without a conf file at all and see if that's faster
-
According to the log, it's trying to load the DRM mga module. Make sure you have the graphics- extension loaded - it's only a dep of those drivers that absolutely require it.
edit: And the matrox firmware too (firmware.tcz).
-
Thanks to curaga and juanito.
a) correct: in Xorg76, the grafics.. extension has to be loaded. Time saving at boot approx 13s
b) in xorg76 the firmware.tcz at boot only make it slower by 2s (I could not see any advantage)
c) I had a look again at xorg74.
by looking at my screen specs I had in the xorg conf file
.... # HorizSync 27-96
# VertRefresh 50-160
and looking at the xorg76 log file
.... Default mode "1024x768": 65.0 MHz, 48.4 kHz, 60.0 Hz
Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz)
and looking at the xorg74 log file, I saw the xorg76 scanned automatically a larger frequency than xorg74.
so, I activated the parameters
.... HorizSync 27-96
VertRefresh 50-160
and it goes automaticcaly to a very large pixel (too large).
so, I reduced the scanning area in xorg.conf with
HorizSync 45-50
VertRefresh 55-65
(according some frequency informations which are in the xorg76 log file "Default mode "1024x768": 65.0 MHz, 48.4 kHz, 60.0 Hz")
and now, it goes automatically into 1024x768 for both xorg74 and 7.6.
Good.
I stay with xorg74: less RAM ressources and same boot time than xorg76 (no firmware.tcz loaded).
Boot time: from the "return" key activation in the grub menue, till the background appear on the screen: 51s.
Info: I did not test xorg76 without xorg.conf file because I remember xorg74 did not start without xorg.conf file.
-
Info: I did not test xorg76 without xorg.conf file because I remember xorg74 did not start without xorg.conf file.
xorg76 is much better in this regard, it's worth a try
-
Info: I did not test xorg76 without xorg.conf file because I remember xorg74 did not start without xorg.conf file.
xorg76 is much better in this regard, it's worth a try
interesting, I confirm, it works confless.
so, I learned something today.
xorg76 confless gives 4,8s according log file but it stay with us keyboard and I have a german keyboard. so I have to config. test was = I started with xorg76 and conf file.. deleted it .. and made startx at exit/prompt and had a look into the log file.
xorg76 with config gives 6,6s according log file.
links extension dont work similar than xorg74. bug...?
so, I would change to xorg76 if there is a way to have my -de- keyboard outside of the xorg configuration.
-
so, I would change to xorg76 if there is a way to have my -de- keyboard outside of the xorg configuration.
I'd think there's a way to only include the keyboard setting in a conf file and leave the rest up to xorg76, but I've never bothered to find out if it's possible or how to do it..
-
Yes, with recent Xorg you can only have some sections there, like the keyboard one.
Though, I prefer to always have full configs, just because it's usually faster to just read & do as the file says than to autoprobe.