Date: Thu, 2 Jul 2009 06:39:11 +0000 From: Da Rock <rock_on_the_web@hotmail.com> To: <freebsd-questions@freebsd.org> Subject: X fails to start Message-ID: <BAY143-W1650E4647EAFA7A6968FF8D2F0@phx.gbl>
next in thread | raw e-mail | index | archive | help
I'm still having intermittent troubles with getting the freebsd servers see= ing my mail servers for my normal maillist subscription=2C so if I could be= cc'd... I'm struggling to get my head around a reasonably severe problem with Xorg = - I'm wondering if anyone else is having the same. I've installed Xorg=2C g= ot it working=2C started to refine some settings with the wm and other apps= for it=2C and then Xorg refuses to work. My xorg log has only a couple of errors=2C for reference I'm using the i915= ko with drm: startx: X.Org X Server 1.6.1 Release Date: 2009-4-14 X Protocol Version 11=2C Revision 0 Build Operating System: FreeBSD 7.2-RELEASE-p1 i386 ... (EE) [drm] Could not set DRM device bus ID. (EE) intel(0): [dri] DRIScreenInit failed. Disabling DRI. Setting master=20 MIT-SHM extension disabled due to lack of kernel support Xorg.0.log: ... drmGetBusid returned '' (II) [drm] DRM interface version 1.0 (EE) [drm] Could not set DRM device bus ID. (EE) intel(0): [dri] DRIScreenInit failed. Disabling DRI ... (WW) intel(0): drmDropMaster failed: Unknown error: -1 ... (WW) intel(0): PRB0_CTL (0x0001f001) indicates ring buffer enabled (WW) intel(0): Existing errors found in hardware state. ... MIT-SHM extension disabled due to lack of kernel support ... (WW) intel(0): drmDropMaster failed: Unknown error: -1 Because of my communications issues I've been trying to resolve this myself= - with no luck. I've been trying to get some more info on this=2C and it se= ems to be a huge bug on a lot of linux distros=2C but noone has a clear res= ponse- it all seems to be a secondary issue to whatever their problem is. S= O=2C I then tried to find out how to debug=2C and ran into ANOTHER issue. I= 've rebuilt xorg-server with debug (ccflags=3D'-O0 -g3' as per xorg wiki) w= ith no real success=2C so then I moved to dri and hit this wall: ../../../src/mesa/main/dispatch.o(.text+0xbb90):../../../src/mesa/glapi/gla= pitemp.h:4951: first defined here ../../../src/mesa/x86/glapi_x86.o(.text+0x4130): In function `glPointParame= teri': ../../../src/mesa/x86/glapi_x86.S:1270: multiple definition of `glPointPara= meteri' ../../../src/mesa/main/dispatch.o(.text+0xc8e0):../../../src/mesa/glapi/gla= pitemp.h:5256: first defined here ../../../src/mesa/x86/glapi_x86.o(.text+0x4140): In function `glPointParame= teriv': ../../../src/mesa/x86/glapi_x86.S:1271: multiple definition of `glPointPara= meteriv' ../../../src/mesa/main/dispatch.o(.text+0xc940):../../../src/mesa/glapi/gla= pitemp.h:5266: first defined here mklib: Installing libGL.so.1 libGL.so in ../../../lib mv: rename libGL.so.1 to ../../../lib/libGL.so.1: No such file or directory gmake[2]: *** [../../../lib/libGL.so] Error 1 gmake[2]: Leaving directory `/usr/ports/graphics/dri/work/Mesa-7.4.4/src/gl= x/x11' gmake[1]: *** [subdirs] Error 1 gmake[1]: Leaving directory `/usr/ports/graphics/dri/work/Mesa-7.4.4/src' gmake: *** [default] Error 1 *** Error code 1 Stop in /usr/ports/graphics/dri. The various warnings are in the gallon=2C but my main problem lay with the = mklib error. So I tried to simply copy or rename libGL.so(.1) to make it ha= ppy (I couldn't find references in the Makefile(s) after half an hour of ex= amination=2C so I took a little shortcut). It did=2C but then the gallon of= warnings came back to hit me again- but harder=2C and so I get another sto= p in the build. So now I can't get dri back=2C I can't get X working and I'm losing my pati= ence fast! :) What I can't figure out is what started all this in the first place=2C beca= use it was working. Unfortunately I was in the midst of several things happ= ening at once=2C so I can't remember if I rebuilt the kernel=2C upgraded xo= rg or both before X failed. As far as I can tell that is only secondary at = any rate=2C as I need to prevent this happening again during upgrades/updat= es whatever. My main questions here are: 1. How do debug Xorg? The debug flags haven't provided much at all so far (= maybe I've done it wrong?) 2. Why can I get the busid failure and Xorg keep going? How do I force it? = Where is this problem lying (kmod=2C driver=2C server)? Is it critical? 3. Is the MIT-SHM error the cause of my problems? (Or a contributor) 4. What do I need to do about the Mesa library? Is this related to the core= issue? Is this a known bug in the port build? I've considered manually debugging the drmGetBusID failure=2C but I don't e= xactly relish the idea of going through that much code. I could easily foll= ow the procedures in the wiki=2C but I'd rather go through ports. I've also just completely removed xorg and started again with the cflags=2C= but it has failed again at the dri port. I hope someone help here... :/ Cheers _________________________________________________________________ Get the latest news=2C goss and sport Make ninemsn your homepage! http://windowslive.ninemsn.com.au/article.aspx?id=3D813730=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BAY143-W1650E4647EAFA7A6968FF8D2F0>