You are not logged in.
http://www.phoronix.com/scan.php?page=n … &px=NzU3OQ
Since X11 is under heavy development, I can imagine there are quite a few people interested in this kind of news. Earlier this week mesa 7.6 and xorg-video-intel 2.9.0 were released.
Something I don't understand: what is the difference between Xorg (v7.5), xorg-server (v1.7) and mesa (v7.6) and where does the driver fit in? All I know is, I need them all to get more than a CLI on linux.
Zl.
Offline
Well I've just compiled xorg-server 1.7 and all deps from git and it's working just fine. Didn't notice any improvements though I'm sure there are many (XI2/Multi-Pointer X). Sadly because I havent used to pkgbuild I broke many deps on my arch wich is fine for me because I plan to reinstall arch once gnome 2.28, mesa 7.6 and xserver 1.7 hit the repos... In the meantime I promisse I will learn how to use pkgbuild, will save me a lot of trouble
Xorg is the entire collection of apps that consists of various modules, xserver, mesa, input and video drivers etc...
Offline
Okay. Here's how it works.
X Window System (note, not Windows, Window!): A defined protocol for graphical user interfaces. Developed at MIT in 1984. This is just a protocol -- hence, you don't install X, you install an implementation of X, in this case, X.Org (more on that below). This makes sense, if you look at ls -l `which X`, X is a symlink to Xorg.
X11R7.4: The current version of the X Window System protocol. Commonly referred to as just X11, as v11 was in the 80's and it's not likely to become X12 any time soon. X.Org is the reference implementation of X, so new versions of the protocol are timed with new versions of X.Org.
X Server: An X11 window server. This is the meat of an X11 implementation, that handles "clients" (windows) -- but not ALL of an X11 implementation.
XFree86: A Free Software implementation of X11. This fell out of favor after a licensing change, and it was forked into X.Org in 2004. Development appears to be stalled, and most OSes that used XFree86 have switched to X.Org. Note that this isn't just the server.
X.Org: Another Free Software implementation of X11, forked from XFree86. This is actively developed, and is the reference implementation, which means that X.Org is developed by a lot of the same people that work on the X11 protocol, so releases of each are usually timed together.
X.Org Server: See "X Server". This is the meat of X.Org, but not all of it. This news is for a new version of the server, which Arch will likely get. Some distros will wait for X11R7.5 though, which X.Org Server 1.7 (or later) will be a part of.
X.Org Foundation: A non-profit scientific charity that manages X.Org.
freedesktop.org: Formerly known as the X Desktop Group, aka XDG, this is a charity organization that provides hosting, monetary support, promotion, and development of standards, for Free software on the desktop. Projects who are beneficiaries of freedesktop.org include X.Org, Mesa, GStreamer (replacement for DirectShow), D-Bus, HAL, fontconfig, Xft, Cairo, DRI... mostly low-level desktop stuff.
OpenGL: A cross-platform open API for 2D and 3D graphics. Competes with Microsoft's Direct3D. Again, this is an API, not a piece of software: video card drivers either deliver their own OpenGL implementation (read: Catalyst/fglrx, and the NVIDIA blob), or rely on OpenGL provided by the system in the case of the latest Free Software graphics work (see Mesa and DRI). To get Direct3D under GNU/Linux, one uses Wine, which is actually translating Direct3D calls to OpenGL on-the-fly. It should be technically possible to create Linux apps that use Direct3D by linking with winelib, though not preferred.
Mesa: A Free Software implementation of OpenGL. Mesa uses the CPU by default, aka software rendering, which is why everything is dog-slow without a proper video card. Mesa supports OpenGL 2.1, and is working on later versions.
DRI: Direct Rendering Infastructure. Technically this is more powerful than what I describe here, but all that is really needed to know is that it lets Mesa access the power of hardware video cards. Newer Free Software drivers tend to rely on DRI for accelerated 3D, and contribute to it as a universal approach to accelerated 3D (Nouveau, Intel, and xf86-video-ati/radeonhd). Most video card drivers (again, the open-source ones like those just listed) can only use DRI to achieve a lower version of OpenGL than Mesa, but this is also being worked on quickly. DRI consists of the DRM (Direct Rendering Manager, not evul corporate strategy ) which is kernel-level, and a userland driver like xf86-video-{ati,nouveau,radeonhd}.
Whewh! That was a lot; I think that's it. There may be errors though, this is only from a long time puzzling over the complex situation of Free Software graphics. Let me know if you have any other questions
Last edited by Ranguvar (2009-10-15 20:04:30)
Offline
Thanks Ranguvar! that was a great summary.
"I know what you're thinking, 'cause right now I'm thinking the same thing. Actually, I've been thinking it ever since I got here:
Why oh why didn't I take the BLUE pill?"
Offline
Offline
I have wondered for a while, why there are a lot of packages in Arch repos that start xf86? For example the xf86-video-ati. Isn't xf86 the same as Xfree86? Seems strange to name X.org-packages as being Xfree86.
Offline
That's the upstream name....
Allan-Volunteer on the (topic being discussed) mailn lists. You never get the people who matters attention on the forums.
jasonwryan-Installing Arch is a measure of your literacy. Maintaining Arch is a measure of your diligence. Contributing to Arch is a measure of your competence.
Griemak-Bleeding edge, not bleeding flat. Edge denotes falls will occur from time to time. Bring your own parachute.
Offline
Thanks for info.
Last edited by bharani (2009-10-03 12:03:01)
Tamil is my mother tongue.
Offline
Yeah, the X.Org drivers kept the xf86-* names from XFree86
Offline
Well I've just compiled xorg-server 1.7 and all deps from git and it's working just fine. Didn't notice any improvements though I'm sure there are many (XI2/Multi-Pointer X)
For XI2/MPX, the window managers and toolkits need to take advantage of it. Currently there are two wms that do, the demo window manager created for mpx testing, and a patched compiz (this could easily e out of date)
Offline
wow this has to be put in wiki somewhere, good job Ranguvar and thanks
Acer Aspire V5-573P Antergos KDE
Offline
I too compile 1.7. What I noticed was a much faster startup of X. Although this might be because I also updated to the 2.9 intel drivers. flash runs with
much less CPU, which is a relieve. Beside that it runs stable no crash since two hours including WorldOfGoo, heavy browsing and youtube. It feels a lot snappier, but again maybe the new intel drivers.
greetings
Offline
You're welcome, but just to note, any of you could also put it in the wiki
I have yet to try the 1.7 server, I might if I get some time soon... time that I'm not using slacking on the forum
Offline
I too compile 1.7. What I noticed was a much faster startup of X.
Hi, do you think you can provide PKGBUILDs for compilation? I want to try 1.7 on my testing machine, but my skill to prepare all dependencies is not too high
Thanks
Offline
I bumped nearly 20 xorg packages, to get xorg 1.7 working. No git packages, I used the latest snapshot/tarball for everything.
I was thinking I could at least share the pkgbuilds somewhere (the packages are i686, compiled with testing repo enabled, and not in a chroot).
pacman roulette : pacman -S $(pacman -Slq | LANG=C sort -R | head -n $((RANDOM % 10)))
Offline
gregorburger wrote:I too compile 1.7. What I noticed was a much faster startup of X.
Hi, do you think you can provide PKGBUILDs for compilation? I want to try 1.7 on my testing machine, but my skill to prepare all dependencies is not too high
Thanks
![]()
Hi, I'm myself not a pacman magician but what i did was this:
$ sudo abs extra/xorg-server
this pulls in the currently used PKGBUILD und /var/abs/extra/xorg-server
- copy it somewhere (not to /tmp as I did and lost all the work so I can't
provide you the PKGBUILD )
- change the version number in the PKGBUILD and update the md5sums
using makepkg -g. (you can pipe them into the PKGBUILD using
makepkg -g >> PKGBUILD and the comment out the old sums)
- you need various proto packages to update. just do the same
with the proto packages (find here the latest versions of the protos
http://xorg.freedesktop.org/releases/individual/proto/)
- you need to also recompile xf86-input-keyboard, xf86-input- mouse
and xf86-input-evdev (this one is really important mouse and keyboard
won't work without it ).
thats roughly how i did it, as said before I can't provide you the PKGBUILDs
i lost them in tmpfs after painfully noticing the evdev is needed ;-)
cheers
Offline
@ Ranguvar:
Thanks for such a great refresher!!
Offline
Holy crap, 1.7 _is_ tons faster starting up Easily 2-3sec. faster.
NVIDIA binary drivers here, same version.
Offline
In testing now
pacman roulette : pacman -S $(pacman -Slq | LANG=C sort -R | head -n $((RANDOM % 10)))
Offline
Man, you don't know how that made my day, great. Mesa and entire xorg stack are in testing. Did Xorg 7.5 got released?
Offline
Might be a text DPI glitch.
Offline
It seems as everything is being scaled differently, smaller on my eee. However this is a good thing, because before I felt everything was to big!
I experience the same thing. Suddenly my screen feels much bigger. But if you don't like small fonts, I guess this could be a problem. For me, I think I like it
Offline
Well xserver and the rest from testing works just fine, with mesa upgrade I can run enemy territory now and warsow also, performance jumped but by a small margin (30 instead of 25fps under same conditions in extremetuxracer). Great upgrade
Offline
Thanks for the stuff in testing Shining
Got Leenucks? :: Arch: Power in simplicity :: Get Counted! Registered Linux User #392717 :: Blog thingy
Offline