TC Xorg installation strategy

[Yleisajattelija]

HD3000 and HD2000 suppose to be very close relatives, but it is of course possibility that 3000 works and 2000 not.

I will oad again TC base system, set local keyboard and load only Xorg7.6 package. Deps should be OK, so lot of stuff should install with Xorg.

Probably it crashes again, I try get all logs to find out problem.

I will update motherboard BIOS, too.

[Yleisajattelija]

Xorg for core 5i is installed succesfully.

But, only when graphics package is istalled first and then Xor package froma command line. Probably that graphics package pre-installation is not the key, but that command line installation is.

Anyway, it is MUCH better idea always load drivers from command line (typically runlevel 3), and that is real Unix way too.

Is that so in TinyCore?

Next HD2000, let's see what happens.

[bmarkus]

There are no runlevels in TC.

[Yleisajattelija]

That was core-i5 arrendale, didn't find Sandy Bridge

Let's try this exellent quote system:

There are no runlevels in TC.

a) I did look foor TC init boot secuence documentation
b) I found one
c) I have read it now (several days)
d) I like this TC boot VERY MUCH
e) After carefully analyze, I found couple of extra words in that document
f) I cannot find explanation for tho extra words
g) So, I have to admit, there is good quality and simple boot in this Unix.
h) Yes, I have to admit, that documentation is plentiful, too.
i) I assume that those few extra words are gift for mankind.

Anyway, should I load those Xorg drivers from command or not?

 
 

[Juanito]

Anyway, should I load those Xorg drivers from command or not?

I have Xorg-7.6 loaded "onboot" with the hd3000 and things work fine.

[Yleisajattelija]

Sorry delay, HD2000 installation is now OK.

Just read TC Xorg installation docs, Xorg extension have to be loaded from command line.

Get rid of X with <ctrl><alt><backspace>, and then "tce-load -wi Xorg7.6.tcz", restart X with "startx", should load without crash.

[Juanito]

BTW, just to be clear, 3d doesn't work with any hardware requiring the intel driver at the moment...

A bit late to pick this thread up again I know, but it just occurred to me to use the "script" command to get something on permanent storage before the crash using 3d acceleration with intel hardware and, on two different machines:

Code: [Select]

$ script /mnt/sda4/tmp/test
$ glxinfo
[crash, reboot]
$ cat /mnt/sda4/tmp/test | grep -i "opengl\|direct\|server\|client"
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.4
server glx extensions:
client glx vendor string: Mesa Project and SGI
client glx version string: 1.4
client glx extensions:
OpenGL vendor string: Tungsten Graphics, Inc
OpenGL renderer string: Mesa DRI Intel(R) Sandybridge Mobile  x86/MMX/SSE2
OpenGL version string: 2.1 Mesa 7.10.3
OpenGL shading language version string: 1.20
..and:

Code: [Select]

$ cat /mnt/sdb1/tmp/test | grep -i "opengl\|direct\|server\|client"
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.4
server glx extensions:
client glx vendor string: Mesa Project and SGI
client glx version string: 1.4
client glx extensions:
OpenGL vendor string: Tungsten Graphics, Inc
OpenGL renderer string: Mesa DRI Intel(R) 945GM  x86/MMX/SSE2
OpenGL version string: 1.4 Mesa 7.10.3
..so the 3d graphics is starting up and then crashing - kind of strange that this happens on old hardware - i945 - which worked with Xorg-7.5

[Yleisajattelija]

TC "ideology" owns two spesific problems with Xorg:

a) TC is missing runlevels -> no proprietary state-machine for installation
b) Xvesa is needed before Xorg -> have to load and unload Xvesa driver modules before loading Xorg

Seems that Xvesa module-unload-cleaning process is not solid, and Xorg modules cannot load after Xvesa without total X-init. This is probably untested situation, because "normal distroes" does Xvesa load OR Xorg load, not both.

a) + b) means that there is no way to change Xvesa to Xorg without manual X shutdown.


That GPU-core on Sandbridge architechture is awful mess, I think only way is to wait until Intel get that 3D driver stabile.

That is very diffucult task to get Core-i family uP/GPU internal bus traffic to syncronize without lockups etc. on multicore environment.

Nowdays Intel is putting lot of effort to Linux-port, so I think that will eventually work flawless.

[Juanito]

b) Xvesa is needed before Xorg -> have to load and unload Xvesa driver modules before loading Xorg

'Not totally sure I've understood your point, but I run an intel hd3000 machine with core64 and Xorg-7.6 without using/loading Xvesa (which will not work with core64 anyway)

That GPU-core on Sandbridge architechture is awful mess, I think only way is to wait until Intel get that 3D driver stabile.

I've tried several combinations of intel driver/mesa/libdrm all without 3d success - agreed.

That is very diffucult task to get Core-i family uP/GPU internal bus traffic to syncronize without lockups etc. on multicore environment.

Again not sure what is meant by this, but the machine above - quad core i7/hd3000 works for weeks at a time without problems...

[curaga]

a) + b) means that there is no way to change Xvesa to Xorg without manual X shutdown.

This situation is not special. The same happens when your distro is running the FOSS radeon driver and you install the AMD binary driver. You need a full reboot in that case, though, an X restart is not enough.

[Yleisajattelija]

Again not sure what is meant by this, but the machine above - quad core i7/hd3000 works for weeks at a time without problems...

If driver works, it works. When one tries to get it to working is BIG difference if API is simple or not. I'm not 3-D accel expert, but seems that when developing faster 3-D chip it is "easy though" that complexity makes power. The eternal CISC/RISC -diskussion is here again.

I'm HW-dude -> simple is better.

'Not totally sure I've understood your point, but I run an intel hd3000 machine with core64 and Xorg-7.6 without using/loading Xvesa (which will not work with core64 anyway)

I think TC approach is to load linux from scratch. First load base system to get to cloud, then load applications you need. It's good way to start with Xvesa, because it works for sure. If you have not display at first, you cannot proceed. When you have xvesa, there is display, and you have possibiilty to fix Xorg problems.   

P.S I don't understand with these ¤%# [quates], hex editor etc. badly needed!

[Juanito]

It's good way to start with Xvesa, because it works for sure. If you have not display at first, you cannot proceed. When you have xvesa, there is display, and you have possibiilty to fix Xorg problems.

OK, but what I'm saying is don't start with Xvesa.

Boot with only core/core64 and no other extensions loaded, then load graphics-KERNEL, Xorg-7.6 (not Xorg-7.6-3d) and your choice of window manager and then "startx" and things should "just work"

[Yleisajattelija]

Xvesa Xorg loading problem disappeared with TC4.5, congratulations!

Sorry, I cannot pinpoint any reason for that previous crash, I hope you already did localize it.