Joined: Sep. 2005
||Posted: Oct. 04 2007,17:12
|Try setting it to setgid root too..|
- does the drive have an effect on this, if the file is set suid & guid root?
|Could be related to the same problem before (i.e. symlinking build dir to hd). Try running it off somewhere on /ramdisk ?|
- this was built on /ramdisk against the xorg72 extension and headers. I'll copy it to /opt/xorg72/bin and try again. Since sudo make install did not copy the kdrives, it is possible make did not set the correct permissions.
|Also, what happens if you try to run it with root privileges?|
- I couldn't do this as I was using LD_LIBRARY_PATH to point to the xorg72 libs (the kdrive needs libXfont.so.1, not in base dsl).
I tried this on another machine:
|Code Sample |
|$ exec /opt/xorg72/bin/Xmga -3button -mouse /dev/psaux -screen 1280x1024x16 -nolisten tcp|
Fatal server error - no matching cards found
$ lspci | grep Matrox
01:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA 2164W [Millennium II] AGP
[This required libs libXfont.so.1, libXau.so.6, libfontenc.so.1, libxdmcp.so.6]
|Code Sample |
|$ exec /opt/xorg72/bin/Xvesa -3button -mouse /dev/psaux -screen 1280x1024x16 -nolisten tcp|
Error cannot find /opt/xorg72/lib/xserver/security.policy
various font errors
fixed font error
Thus it would seem the kdrives require additional libs vs the base dsl and they need to be compiled with the same prefix as the original Xvesa kdrive and they don't seem to recognise i810 and mga video cards.
Does it make sense to carry on?
I tried Curaga's Xvesa extension - this started a grey screen with just the cursor. After exiting, there were various "could not init font" errors.