Date: Thu, 2 Jul 2009 12:18:28 +0000 From: Da Rock <rock_on_the_web@hotmail.com> To: <onemda@gmail.com> Cc: freebsd-questions@freebsd.org Subject: RE: X fails to start Message-ID: <BAY143-W7FAADDFED8C87809F55368D2F0@phx.gbl> In-Reply-To: <3a142e750907020454w73d6cb01v8eba8893a66b2533@mail.gmail.com> References: <BAY143-W1650E4647EAFA7A6968FF8D2F0@phx.gbl> <3a142e750907020316o34095c68ua5581b201f206b28@mail.gmail.com> <BAY143-W2A139D5AE48FFF344A3F68D2F0@phx.gbl> <3a142e750907020454w73d6cb01v8eba8893a66b2533@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> Date: Thu=2C 2 Jul 2009 13:54:22 +0200 > Subject: Re: X fails to start > From: onemda@gmail.com > To: rock_on_the_web@hotmail.com > CC: freebsd-questions@freebsd.org >=20 > On 7/2/09=2C Da Rock <rock_on_the_web@hotmail.com> wrote: > >> Date: Thu=2C 2 Jul 2009 12:16:49 +0200 > >> Subject: Re: X fails to start > >> From: onemda@gmail.com > >> To: rock_on_the_web@hotmail.com > >> CC: freebsd-questions@freebsd.org > >> > >> On 7/2/09=2C Da Rock <rock_on_the_web@hotmail.com> wrote: > >> > > >> > I'm still having intermittent troubles with getting the freebsd serv= ers > >> > seeing 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 wit= h > >> > Xorg - > >> > I'm wondering if anyone else is having the same. I've installed Xorg= =2C > >> > got it > >> > working=2C started to refine some settings with the wm and other app= s for > >> > it=2C > >> > and then Xorg refuses to work. > >> > > >> > My xorg log has only a couple of errors=2C for reference I'm using t= he > >> > 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 > >> > 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 > >> > seems > >> > to be a huge bug on a lot of linux distros=2C but noone has a clear > >> > response- > >> > 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= ) with > >> > no > >> > real success=2C so then I moved to dri and hit this wall: > >> > > >> > ../../../src/mesa/main/dispatch.o(.text+0xbb90):../../../src/mesa/gl= api/glapitemp.h:4951: > >> > first defined here > >> > ../../../src/mesa/x86/glapi_x86.o(.text+0x4130): In function > >> > `glPointParameteri': > >> > ../../../src/mesa/x86/glapi_x86.S:1270: multiple definition of > >> > `glPointParameteri' > >> > ../../../src/mesa/main/dispatch.o(.text+0xc8e0):../../../src/mesa/gl= api/glapitemp.h:5256: > >> > first defined here > >> > ../../../src/mesa/x86/glapi_x86.o(.text+0x4140): In function > >> > `glPointParameteriv': > >> > ../../../src/mesa/x86/glapi_x86.S:1271: multiple definition of > >> > `glPointParameteriv' > >> > ../../../src/mesa/main/dispatch.o(.text+0xc940):../../../src/mesa/gl= api/glapitemp.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/glx/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 wi= th the > >> > mklib error. So I tried to simply copy or rename libGL.so(.1) to mak= e it > >> > happy (I couldn't find references in the Makefile(s) after half an h= our > >> > of > >> > examination=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 anoth= er > >> > stop in > >> > the build. > >> > > >> > So now I can't get dri back=2C I can't get X working and I'm losing = my > >> > patience fast! :) > >> > > >> > What I can't figure out is what started all this in the first place= =2C > >> > because > >> > it was working. Unfortunately I was in the midst of several things > >> > happening > >> > at once=2C so I can't remember if I rebuilt the kernel=2C upgraded x= org 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/updates whate= ver. > >> > > >> > My main questions here are: > >> > > >> > 1. How do debug Xorg? The debug flags haven't provided much at all s= o > >> > far > >> > (maybe I've done it wrong?) > >> > >> You can still use xf86-video-vesa even without dri. > >> Debug flags are useful only if Xorg crashed and dropped core. > >> > > > > Nuts! :( > > > >> > 2. Why can I get the busid failure and Xorg keep going? How do I for= ce > >> > it? > >> > Where is this problem lying (kmod=2C driver=2C server)? Is it critic= al? > >> > >> What kernel modules are loaded? What version of server=2C Mesa=2C driv= ers > >> are installed > >> and how are they installed? > >> > > > > KMods: > > i915.ko > > drm.ko > > > > Xorg Server: 1.6.1 (in the Xorg log) > > Mesa (not entirely sure now=2C was current I believe though- I'll have = to wait > > and see once I can build again...) > > Drivers: (installed or used?) used intel- xorg ports. Incidentally vesa= is > > available=2C and is failover in the conf=2C but it doesn't get there. I= ts also > > installed via ports. >=20 > You can use vesa if you specify alternative or modify default server layo= ut. > But anyway without xorg.conf I can't comment on this. >=20 > >> > 3. Is the MIT-SHM error the cause of my problems? (Or a contributor) > >> > >> You are using custom kernel without sysv* modules. Not a good idea for= X. > >> > > > > Interesting. Isn't this standard in GENERIC? I have built a kernel=2C b= ut only > > GENERIC=2C which I would have thought had the standard kit in it that c= omes > > with a distro on disk. >=20 > Than it is not problem=2C probably some Xorg way to report errors. >=20 > >> > 4. What do I need to do about the Mesa library? Is this related to t= he > >> > core > >> > issue? Is this a known bug in the port build? > >> > >> Your environment is highly polluted. > >> > > > > eh? I could use some explanation on this=2C especially considering my l= ast > > remedy used in this communication. As per my last comment in the OP=2C = I've > > run portsclean -C and then removed all ports (something I have the luxu= ry of > > doing being a new system install)=2C and started again- with the same r= esult. > > What exactly do I have to clean up to remove the pollution? (This is no > > reflection on your comment=2C I'm merely at a loss to know what could b= e > > getting in the way here given my situation) >=20 > Perhaps you forgot to run "make clean"? > Just remove whole /usr/local=2C/usr/ports=2C/var/db/pkg and update ports = tree. > Yes=2C this is very radical approach but I don't know any better way. >=20 And I thought I was radical! I didn't want to sound ruthless=2C but I ran p= kg_delete -f \* which I believe achieves the same result (and from what I u= nderstand so does portsclean -C - only available if you have installed port= upgrade as I found out once) and thats how I cleaned my system to start aga= in. For anyone else watching=2C be very careful if and when you do this- do= n't reboot or something until you have a grasp of what you have done! :) In my circumstances its impossible to actually blow away the ports system= =2C but I can kill the pkg db - I'm just not entirely sure why. Ports is up= to date - ran portsnap twice jic. My only other alternative is to blow awa= y usr/local- in case that may be getting in the way (I don't know exactly h= ow=2C but I AM getting desperate!). Before I do that I might run make clean in the ports (jic portsclean isn't = doing its job properly)=2C and blow away the ports db (hence the options sa= ved). I still don't hold much hope. As for the pollution factor=2C I'm not sure. This has to be one of the clea= nest systems I've setup yet- I'm starting small and building up from there= =2C but I haven't even reached the first landing yet! I've had a lot worse- in fact the system itself is a complete rebuild from = the major f***kup I committed before- don't ask what I was thinking=2C but = I did blow away the db dir for pkg AND ports=2C so updates were impossible= =2C and I didn't even know (or the system) what was actually installed (tha= nk god it was only a desktop!). Definitely a blonde moment... and I'm not e= ven blonde (or female)! Must have been a long day or a late night... :) > >> > I've considered manually debugging the drmGetBusID failure=2C but I = don't > >> > exactly relish the idea of going through that much code. I could eas= ily > >> > follow 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 can help here... :/ >=20 > --=20 > Paul _________________________________________________________________ Looking for a place to rent=2C share or buy this winter? Find your next pla= ce with Ninemsn=A0property http://a.ninemsn.com.au/b.aspx?URL=3Dhttp%3A%2F%2Fninemsn%2Edomain%2Ecom%2E= au%2F%3Fs%5Fcid%3DFDMedia%3ANineMSN%5FHotmail%5FTagline&_t=3D774152450&_r= =3DDomain_tagline&_m=3DEXT=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BAY143-W7FAADDFED8C87809F55368D2F0>