<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns="http://www.w3.org/TR/REC-html40"> <head> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"> <meta name=Generator content="Microsoft Word 11 (filtered medium)">  <style>  </style>  </head> <body lang=EN-GB link=blue vlink=blue> <div class=Section1> Hi again,<o:p></o:p> <o:p> </o:p> Sorry – it’s been a long day and you just know you’ll spot your error about 5 seconds after pressing [send] – that was the wrong Xorg.0.log I attached. The correct one with the real problem I’m now facing is attached:<o:p></o:p> <o:p> </o:p> This one correctly reports:<o:p></o:p> <o:p> </o:p> X.Org X Server 1.6.99.1<o:p></o:p> Build Date: 17 December 2008 08:02:24PM<o:p></o:p> <o:p> </o:p> and<o:p></o:p> <o:p> </o:p> (==) FontPath set to:<o:p></o:p> built-ins<o:p></o:p> <o:p> </o:p> which is promising as the X system I built was configured for built-in fonts. Then the first lib appears to load without problem:<o:p></o:p> <o:p> </o:p> (II) LoadModule: "glx"<o:p></o:p> (II) Loading /root/X/lib/xorg/modules/extensions//libglx.so<o:p></o:p> (II) Module glx: vendor="X.Org Foundation"<o:p></o:p> compiled for 1.6.99.1, module version = 1.0.0<o:p></o:p> ABI class: X.Org Server Extension, version 2.0<o:p></o:p> <o:p> </o:p> But then the first sign of trouble is:<o:p></o:p> <o:p> </o:p> (II) LoadModule: "dri"<o:p></o:p> (II) Loading /root/X/lib/xorg/modules/extensions//libdri.so<o:p></o:p> dlopen: /root/X/lib/xorg/modules/extensions//libdri.so: undefined symbol: xf86LoadKernelModule<o:p></o:p> (EE) Failed to load /root/X/lib/xorg/modules/extensions//libdri.so<o:p></o:p> (II) UnloadModule: "dri"<o:p></o:p> (EE) Failed to load module "dri" (loader failed, 7)<o:p></o:p> <o:p> </o:p> So the problem appears to be the fact that this is trying to link to xf86LoadKernelModule() that does not exist. So which bit of the jigsaw is it that should be providing this and which I must, therefore, have not got up to date yet?<o:p></o:p> <o:p> </o:p> Cliff Lawson<o:p></o:p> <o:p> </o:p> <div> <div class=MsoNormal align=center style='text-align:center'> <hr size=2 width="100%" align=center tabindex=-1> </div> From: xorg-bounces@lists.freedesktop.org [mailto:xorg-bounces@lists.freedesktop.org] On Behalf Of Cliff Lawson Sent: 18 December 2008 17:31 To: xorg@lists.freedesktop.org Subject: RE: Building latest Intel support for 945G<o:p></o:p> </div> <o:p> </o:p> Hi,<o:p></o:p> <o:p> </o:p> Well it’s taken me a while (well a week) to get to this point as I had to learn all about using git and building the full Xorg set of code. But in an attempt to see whether Intel 2.5.1 would help the problems I’m seeing on a 945G based system I did the following:<o:p></o:p> <o:p> </o:p> <![if !supportLists]>1) <![endif]>Pulled/built the mainline 2.6.28-rc8 kernel from git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git so I could get 2.6.28-rc8 as I believe (?) this will have the latest drm.ko and i915.ko (or am I wrong about that?)<o:p></o:p> <![if !supportLists]>2) <![endif]>Followed the script on the end of the page: <a href="http://wiki.x.org/wiki/Development/git">http://wiki.x.org/wiki/Development/git</a> and slowly but surely fixed any missing dependencies on my system<o:p></o:p> <o:p> </o:p> I did all this first on an Ubunutu 8.04 machine running in a Vmware sandbox on a Windows machine first just to make sure that I could get everything to build. Eventually I got it booting 2.6.28-rc8 and running the X software stack I’d built this way. But clearly the video driver in this is the Vmware driver – not an Intel hardware driver. So everything worked in that environment which gave me confidence that I built everything OK.<o:p></o:p> <o:p> </o:p> I then moved over to the target machine and did it all again. At the end of this process I tried the same method to start my “private” copy of X but, as the attached Xorg.0.log shows this ends with:<o:p></o:p> <o:p> </o:p> (II) intel(0): [drm] mapped front buffer at 0x20000000, handle = 0x20000000<o:p></o:p> (II) intel(0): [drm] mapped back buffer at 0x20000000, handle = 0x14000000<o:p></o:p> (II) intel(0): [drm] mapped depth buffer at 0x20000000, handle = 0x14001000<o:p></o:p> (II) intel(0): [drm] mapped classic textures at 0x2dff5000, handle = 0x2dff5000<o:p></o:p> <o:p> </o:p> Backtrace:<o:p></o:p> 0: /usr/bin/X11/X(xf86SigHandler+0x7e) [0x80c780e]<o:p></o:p> 1: [0xb8031400]<o:p></o:p> 2: /usr/local/lib/xorg/modules/drivers//intel_drv.so [0xb7bcbc03]<o:p></o:p> 3: /usr/local/lib/xorg/modules/drivers//intel_drv.so [0xb7bcd3be]<o:p></o:p> 4: /usr/bin/X11/X(AddScreen+0x1fc) [0x8073d9c]<o:p></o:p> 5: /usr/bin/X11/X(InitOutput+0x21e) [0x80a9c4e]<o:p></o:p> 6: /usr/bin/X11/X(main+0x296) [0x8074526]<o:p></o:p> 7: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe0) [0xb7db6450]<o:p></o:p> 8: /usr/bin/X11/X(FontFileCompleteXLFD+0x201) [0x8073a91]<o:p></o:p> <o:p> </o:p> Fatal server error:<o:p></o:p> Caught signal 11. Server aborting<o:p></o:p> <o:p> </o:p> So can anyone offer any advice as to what I may have done wrong in the building of all this? Do I need to use special anholt or airlied kernel trees and if so how do I get them with git? Or is it OK to use the main Linus Torvalds tree for 2.6.28-rc8<o:p></o:p> <o:p> </o:p> Is there anything further I can do to diagnose what’s wrong? I’m guessing one of the components I’ve got does not inter-work with the rest but how do I check the various version numbers and identify which is too old (or too new?)<o:p></o:p> <o:p> </o:p> Should it be the case if I just get a 2.6.28-rc8 kernel and also all the git repositories listed in the script in (2) above that I should have up to date copies of everything or are there patches or update versions I need to pick up from elsewhere?<o:p></o:p> <o:p> </o:p> Cliff Lawson<o:p></o:p> <o:p> </o:p> <div> <div class=MsoNormal align=center style='text-align:center'> <hr size=2 width="100%" align=center tabindex=-1> </div> From: Mateusz Kaduk [mailto:mateusz.kaduk@gmail.com] Sent: 12 December 2008 13:52 To: Cliff Lawson Cc: xorg@lists.freedesktop.org Subject: Re: Building latest Intel support for 945G<o:p></o:p> </div> <o:p> </o:p> 2008/12/12 Cliff Lawson <<a href="mailto:cliff@amshold.com">cliff@amshold.com</a>> <o:p></o:p> <div> <blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt; margin-left:4.8pt;margin-top:5.0pt;margin-right:0cm;margin-bottom:5.0pt'> <div link=blue vlink=purple> <div> So I used GIT to get a libdrm that did include the linux-source part of the tree but when I built it the i915.ko did not build and looking at the Makefile it would appear to be because OS_HAS_GEM was not defined. It was a search for the solution to that which brought me to a post in the archive of this mailing list where I realised that a simple "export OS_HAS_GEM=1" before building was NOT the solution to use.<o:p></o:p> </div> </div> </blockquote> </div> You dont set that. drm/linux-core is out-dated. You get correct drm.ko and i915.ko from latest kernel or from for-airlied branch of eric's tree. Look at Eric's LJ <a href="http://anholt.livejournal.com/39544.html">http://anholt.livejournal.com/39544.html</a> first case as You dont need dri2. And after clone switch to for-airlied branch which is a bit more stable. I dont know if master xf86-intel does not need xserver 1.6 (here 1.6), but there is also origin/xf86-video-intel-2.5-branch which should compile fine with xserver 1.5.3 which is in debian/experiemtal packages and it should be possible to install it on Ubuntu.<o:p></o:p> Scanned by MailDefender - managed email security from intY - www.maildefender.net<o:p></o:p> No virus found in this incoming message. Checked by AVG - http://www.avg.com Version: 8.0.176 / Virus Database: 270.9.17/1844 - Release Date: 12/12/2008 09:02<o:p></o:p> </div> </body> </html> <center>Scanned by MailDefender - managed email security from intY - www.maildefender.net</center> <center>Scanned by MailDefender - managed email security from intY - www.maildefender.net</center> No virus found in this incoming message. Checked by AVG - http://www.avg.com Version: 8.0.176 / Virus Database: 270.9.18/1850 - Release Date: 17/12/2008 19:21 <center>Scanned by MailDefender - managed email security from intY - www.maildefender.net</center>