On Sunday 15 March 2009, Dave Airlie wrote: > On Sun, Mar 15, 2009 at 12:34 AM, Frans Pop <elen...@planet.nl> wrote: > > I had the oops below today after I tried to start a second X.org > > session in a chroot using 'startx -- :1'. I think the problem here is > > that the driver was loaded, but that the corresponding device did not > > exist in /dev in the chroot (forgot to bind mount it). If that is the > > cause, it would be nice if it was handled more gracefully than this > > :-P > > Its a bug in userspace we can't do anything about at this point, > > The problem is we attach some information to the device inode and if > you starting using an alternate inode it screws up, I think Thomas had > suggested ways aruond this. > We could probably make it a WARN_ON and fail DRI setup.
Yes, that's what I'd expect. At least not allow it to hang the primairy X session. I understand that you cannot magically make DRI work in this situation. Note that I did start X.Org successfully in the chroot a bit earlier when I did have /dev/ bind mounted to /<mychroot>/dev/. ------------------------------------------------------------------------------ Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
