Re: Xvesa on FC2 and xcompmgr

I'm not sure but i think this is nor selinux related, but i'm not sure.
I have disabled selinux in the grub by adding to selinux=0 to the
kernel, but i had the same problem after rebooting. 

I have noticed to that if i jump to the kernel-2.6.1-1.65 Xvesa just
works fine, but if i try out with kernel-2.6.3-2.1.253.2.1 than i can't
run it.

Btw, Xfbdev works fine with the 2.6.1 and 2.6.3 kernel too.

Thanks,
Julius

On Wed, 2004-03-31 at 21:39 -0600, Brent Cook wrote:

> On Wed, 31 Mar 2004, Douglas McMorris wrote:
> 
> > On Wed, 2004-03-31 at 17:17 -0600, Brent Cook wrote:
> > > On Wed, 31 Mar 2004, Douglas McMorris wrote:
> > >
> > > > >> > 1: Xvesa -verbose returns this:
> > > > >> > Mode requested 640x480x4
> > > > >> >     0x0012: 640x480x4 Planer (4 planes) (no linear framebuffer)
> > > > >> >     Static color bpp 4 depth 4
> > > > >> > Previous modes: VBE 0x4148 BIOS 0x48
> > > > >> > Enable BIOS mode 0x12
> > > > >> > Segmentation fault
> > > > >>
> > > > >> I have the same problem.  It was fine until i updgraded to FC2-test2 (i
> > > > >> was on test1 before).
> > > > >>
> >
> > Just did some testing... it seems to be specific to kernel 2.6.3... when
> > i upgraded from 2.6.1 to 2.6.3 the problem showed itself. Hopefully that
> > narrows your bug search a bit.
> >
> 
> OK, I was unable to reproduce a fix with 2.6.1 or 2.4.25, so I think my
> hanging problem is unrelated to the fedora issue. Fedora now uses SELinux
> I believe; this is sounding more like a SELinux permissions issue with the
> X server accessing /dev/mem. I don't know what Fedora's default
> permissions are, but you might consult this page for info about how to
> modify your security policy to allow Xvesa to access enough resources:
> 
> http://www.crypt.gen.nz/selinux/faq.html#CP.6
> 
>  - Brent