Beryl on Puppy(Installation guide for nvidia gfx cards.)
@jimhap
When compiling fontsproto I used the options wow was using for xorg:
--prefix=/usr/X11R7/ --bindir=/usr/X11R7/bin --libdir=/usr/X11R7/lib --includedir=/usr/X11R7/include --sysconfdir=/etc --localstatedir=/var
(though now I can't remember if I set --build=i386, probably should have)
and the .pc file installed in /usr/X11R7/lib/pkgconfig which is where the others seem to be.
My goal is to compile a patched nsc driver for wow's xorg. Since wow has compiled an nsc driver this must be straightforward enough.
Perhaps wow stripped xproto, fontsproto, etc out of his headers package? (There's no .pc files for these in the above dir either).
UPDATE - SUCCESS!!: I compiled and installed fontsproto and the rest of them => then my driver compiled. As they say: yay! The obvious solution is often the right one.
@wow: perhaps you could add these back into your xorg packages to prevent future suffering? That would be great! thx.
EDIT UPDATE - FAILURE!!: The driver only compiled statically. No shared object.
@johndoe:
Will you be posting your Xorg .pups somewhere in due course?
When compiling fontsproto I used the options wow was using for xorg:
--prefix=/usr/X11R7/ --bindir=/usr/X11R7/bin --libdir=/usr/X11R7/lib --includedir=/usr/X11R7/include --sysconfdir=/etc --localstatedir=/var
(though now I can't remember if I set --build=i386, probably should have)
and the .pc file installed in /usr/X11R7/lib/pkgconfig which is where the others seem to be.
My goal is to compile a patched nsc driver for wow's xorg. Since wow has compiled an nsc driver this must be straightforward enough.
Perhaps wow stripped xproto, fontsproto, etc out of his headers package? (There's no .pc files for these in the above dir either).
UPDATE - SUCCESS!!: I compiled and installed fontsproto and the rest of them => then my driver compiled. As they say: yay! The obvious solution is often the right one.
@wow: perhaps you could add these back into your xorg packages to prevent future suffering? That would be great! thx.
EDIT UPDATE - FAILURE!!: The driver only compiled statically. No shared object.
@johndoe:
Will you be posting your Xorg .pups somewhere in due course?
Last edited by wdef on Tue 17 Apr 2007, 12:35, edited 1 time in total.
@wow: mplayer-1.0rc1-nvidia doesn't seem to be working properly with this xorg either. Like gxine it launches but won't play:
Code: Select all
X11 error: BadAlloc (insufficient resources for operation)?,?% 0 0 77%
MPlayer interrupted by signal 6 in module: flip_page
- MPlayer crashed. This shouldn't happen.
It can be a bug in the MPlayer code _or_ in your drivers _or_ in your
gcc version. If you think it's MPlayer's fault, please read
DOCS/HTML/en/bugreports.html and follow the instructions there. We can't and
won't help unless you provide this information when reporting a possible bug.
mplayer: xcb_xlib.c:41: xcb_xlib_lock: Assertion `!c->xlib.lock' failed
Oops, thanks for that. I'll fix it ASAP.wdef wrote: UPDATE FIXED: new i810 *is* installed in a weird location. Doing this and editing xorg.conf fixed it:So the package needs fixing.Code: Select all
cp /usr/local/xf86-video-i810-X11R7.2-1.6.5/FiLESYSTEM/usr/X11R7/lib/xorg/modules/drivers/i810_drv.so /usr/X11R7/lib/xorg/modules/drivers
EDIT: fontsproto.pc can be found inside Puppy's devx_*.sfs, not in my dotpup because the latest version was already packed with Puppy. See unionfs bug(The bug)...wdef wrote: Does your Xorg contain fontsproto?
Did you compile this Xorg on Puppy or was it Slackware or something?
Yes, it must be inside the dev package x11-7.2-upd-dev.pup. To make the upgrade to x11-7.2, first I'd download, compile and install the x11-7.1's sources then x11-7.2. Everything was done in Puppy-2.13.
I experienced the same problem too due an unionfs bug.
The bug: If you install any package in the first boot, all the new folders will have a hidden file named .wh.* and when you reboot, those folders will became unable to display the contents of the SFS addons. Example: in the first boot a "xxx.pup" install files to /usr/include/ then you reboot but this time with the devx_*.sfs mounted, now if you go to the /usr/include/ folder you'll only see the files installed by "xxx.pup" and the contents from the SFS won't be in there.
To solve it try this(only for frugal installs or booting from the live CD):
Option 1 A new pup_save.
Boot Puppy in RAM mode
Don't install any dotpup/dotpet(this cause the bug in future sessions).
Save a new pup_save file in the same partition which the devx/ooo/etc addon is placed.
Now reboot and choose the new and clean pup_save file.
Option 2 Cleaning the save file (Requires konqueror).
Boot Puppy and open konqueror
Go to this folder: '/initrd/pup_rw' press 'Ctrl+F' and type: '.wh*' into the input box, then press the Find button.
Wait for the results, now select all and delete them.
Reboot.
Last edited by wow on Tue 17 Apr 2007, 02:01, edited 3 times in total.
[url=http://www.puppylinux.com][img]http://i.imgur.com/M4OyHe1.gif[/img][/url]
Not really. Beryl requires many updates to be compiled in Puppy, but it need less updates to run propertlyjimhap wrote:wow did you manage to put the "quarter-million" dependencies into the dotPups??
(their way of saying it @ http://wiki.beryl-project.org/wiki/Building_Beryl)
It was a painful work. Now I have my own Puppy remaster(with all these dependencies installed), ready to build future Beryl releases to build new releases since 0.1.4 I only have to compile the sources in alphabetical order.jimhap wrote:i tried to compile many times but ALWAYS hit an error about Xcomposite and other stuff.
What did you compile? I tried to compile beryl-core-0.2.1, then beryl-manager-0.2.1.
[url=http://www.puppylinux.com][img]http://i.imgur.com/M4OyHe1.gif[/img][/url]
It would be really good.John Doe wrote:Took detailed notes while building a script. Perhaps it could save Barry some time in possibly integrating an xorg upgrade.
Today I recompiled x11-7.2 with GLX extension, and I got a similar error((EE) AIGLX: DRI module not loaded). Something about DRI. I think that is something with the Mesa's DRI. I'm not using the proprietary driver from nVidia.John Doe wrote:Also, was able to get it running using your config instructions as well as with T2. But I'm still unable to get T2 to respect my config options for aiglx and I'm missing DRI when I do it manually. So I'm still only half way there.
Code: Select all
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
(II) Initializing built-in extension XEVIE
(EE) AIGLX: DRI module not loaded
(II) Loading local sub module "GLcore"
(II) LoadModule: "GLcore"
(II) Loading /usr/X11R7/lib/xorg/modules/extensions//libGLcore.so
(II) Module GLcore: vendor="X.Org Foundation"
compiled for 7.2.0, module version = 1.0.0
ABI class: X.Org Server Extension, version 0.3
(II) GLX: Initialized MESA-PROXY GL provider for screen 0
Last edited by wow on Tue 17 Apr 2007, 01:31, edited 1 time in total.
[url=http://www.puppylinux.com][img]http://i.imgur.com/M4OyHe1.gif[/img][/url]
Seems that gxine and mplayer must be recompiled with the new xorg's headers. I use xfmedia or VLC and they works fine with x11-7.2.wdef wrote:@wow: mplayer-1.0rc1-nvidia doesn't seem to be working properly with this xorg either.
Screenshot: VideoLAN(VLC) playing a .flv downloaded from http://www.youtube.com/watch?v=tB9ZhLBSoBQ is a song from Amplitude, PlayStation2 game.
I compiled xorg-server-X11R7.2-1.2.0 again but this time with the GLX extension(--with-mesa-source)
Code: Select all
./configure --build=i486-t2-linux-gnu --prefix=/usr/X11R7 --libdir=/usr/X11R7/lib --includedir=/usr/X11R7/include --localstatedir=/var --sysconfdir=/etc --enable-aiglx --with-mesa-source=/mnt/hdc9/sources/Mesa-6.5.2
[url=http://www.puppylinux.com][img]http://i.imgur.com/M4OyHe1.gif[/img][/url]
Ok, if you have some time to try beryl on your system read this:John Doe wrote:Best news first; my ATI 3D card (MOBILITY RADEON 9000) is running DRI using xorg 7.1 radeon driver and OpenGL. Confirmed using MU's script to see the ANTS (extracted 3D Control Panel manually and ran script to avoid version conflicts). I get ~50fps. Will try to dig up exact chipset again sometime.
Make sure these parameters are present at the end of /etc/X11/xorg.conf
Code: Select all
Section "Extensions"
Option "Composite" "Enable"
EndSection
[url=http://www.puppylinux.com][img]http://i.imgur.com/M4OyHe1.gif[/img][/url]
So .pups with headers effectively clobber .devx_*sfs headers on reboot. Not good.The bug: If you install any package in the first boot, all the new folders will have a hidden file named .wh.* and when you reboot, those folders will became unable to display the contents of the SFS addons. Example: in the first boot a "xxx.pup" install files to /usr/include/ then you reboot but this time with the devx_*.sfs mounted, now if you go to the /usr/include/ folder you'll only see the files installed by "xxx.pup" and the contents from the SFS won't be in there.
That might explain a lot of compile problems. Is this bug for all .pup n]header + devx_*sfs packages and all Puppies? If so it's pretty useless since headers will be vanishing on reboots ie defeats the purpose of the package. Barry is fixing, or not possible?
I'll take note of the fix for future reference.
So you're actually building two versions of xorg from scratch to get where you are -- sheeesh!To make the upgrade to x11-7.2, first I'd download, compile and install the x11-7.1's sources then x11-7.2.
[
Not really, they are not 'vanished', the're hidden. Deleting the .wh* files and then reboot fix it.wdef wrote:So .pups with headers effectively clobber .devx_*sfs headers on reboot. Not good.
That might explain a lot of compile problems. Is this bug for all .pup n]header + devx_*sfs packages and all Puppies? If so it's pretty useless since headers will be vanishing on reboots ie defeats the purpose of the package.
"...Those who have been following the discussion on Unionfs will know that there are problems with "whiteout" files..."wdef wrote:Barry is fixing, or not possible?
http://www.puppyos.net/news/index.php?m ... 419-082918
Last edited by wow on Fri 20 Apr 2007, 04:25, edited 1 time in total.
I compiled the MesaLibs-6.5.2 sources, DRI modules and MesaGlut-6.5.2 this fixed the 'xcb_xlib.c:50: xcb_xlib_unlock...' message.
Then I installed Beryl(on this test system, using a generic display driver for my nvidia card) to see what happens and !!!!! . . . I got a blank screen !!!! Checking the Xorg log I found this:
OMG (EE) AIGLX: Screen 0 is not DRI capable I don't have a nvidia DRI module. Later I burnt this Puppy+Beryl+mesa+etc and boot it on another PC with integrated graphic chips(ProSavage KM266/KL266), and a DRI module for that chipset. Now AIGLX is activated and the DRI module loaded , glxinfo reports:
After run Beryl I got the same blank screen. But is fine, this chipset is too old to run Beryl and the driver lack extensions.
Tomorrow(if I have the time) I'll boot this CD on another PC with a modern Intel graphic chipset, do more test and make dotpups.
Then I installed Beryl(on this test system, using a generic display driver for my nvidia card) to see what happens and !!!!! . . . I got a blank screen !!!! Checking the Xorg log I found this:
Code: Select all
(II) LoadModule: "glx"
(II) Loading /usr/X11R7/lib/xorg/modules/extensions//libglx.so
(II) Module glx: vendor="X.Org Foundation"
compiled for 7.2.0, module version = 1.0.0
ABI class: X.Org Server Extension, version 0.3
(==) AIGLX enabled
(II) Loading extension GLX
(II) LoadModule: "dri"
(II) Loading /usr/X11R7/lib/xorg/modules/extensions//libdri.so
(II) Module dri: vendor="X.Org Foundation"
compiled for 7.2.0, module version = 1.0.0
ABI class: X.Org Server Extension, version 0.3
...
(EE) AIGLX: Screen 0 is not DRI capable
(II) Loading local sub module "GLcore"
(II) LoadModule: "GLcore"
Code: Select all
display: :0 screen: 0
direct rendering: Yes
server glx vendor string: SGI
OpenGL renderer string: Mesa DRI ProSavageDDR 20061110 AGP 1x x86/MMX/SSE2
OpenGL version string: 1.2 Mesa 6.5.2
Tomorrow(if I have the time) I'll boot this CD on another PC with a modern Intel graphic chipset, do more test and make dotpups.
[url=http://www.puppylinux.com][img]http://i.imgur.com/M4OyHe1.gif[/img][/url]
@wdef: About that compile: can you give me the options of the configure? (by ./configure --help ) You should watch when configuring for "shared libraries".
@wow: That's some good news.... (last post)
Why does some other pup's header's eat up devx's headers? How can ".wh" files not let the sfs file load?
@wow: That's some good news.... (last post)
Why does some other pup's header's eat up devx's headers? How can ".wh" files not let the sfs file load?
Last edited by jimhap on Fri 20 Apr 2007, 04:44, edited 2 times in total.
i'm not sure, it just happens . And every sfs is loaded, its content is hidden to the user, but they all are mounted on /initrd/pup_ro*/jimhap wrote:Why does some other pup's header's eat up devx's headers? How can ".wh" files not let the sfs file load?
Read this:
"...Those who have been following the discussion on Unionfs will know that there are problems with "whiteout" files..."
http://www.puppyos.net/news/index.php?m ... 419-082918
[url=http://www.puppylinux.com][img]http://i.imgur.com/M4OyHe1.gif[/img][/url]
The following components are needed to compile Beryl:jimhap wrote:And Beryl wants more. Remember the word "dependencies"? Those may not be listed in the configure, but some may be dependenies of the other requirements.
Here's a list of the dependencies.....(now you'll get shocked)
http://wiki.beryl-project.org/wiki/Compile_requirements
* intltool dev_2*.sfs ?
* libdbus-1-dev disabled
* libdbus-glib-1-2 disabled
* libgl1-mesa-dev compiled and packed to dotpup
* libglu1-mesa compiled and packed to dotpup
* libglu1-mesa-dev compiled and packed to dotpup
* libglu1-xorg-dev compiled and packed to dotpup / Xorg
* libice-dev compiled and packed to dotpup / Xorg
* libjpeg62-dev devx_2*.sfs
* libpng12-dev devx_2*.sfs
* librsvg2-dev compiled and packed to dotpup http://www.murga-linux.com/puppy/viewto ... 90&t=16623
* libsm-dev compiled and packed to dotpup / Xorg
* libstartup-notification0-dev compiled and packed to dotpup
* libwnck-dev compiled and packed to dotpup
* libxcomposite-dev compiled and packed to dotpup / Xorg
* libxdamage-dev compiled and packed to dotpup / Xorg
* libxinerama-dev compiled and packed to dotpup / Xorg
* libxrandr-dev compiled and packed to dotpup / Xorg
* x11proto-gl-dev compiled and packed to dotpup / Xorg
* autoconf (HAVE, WHEN HAVING dev_21x.sfs in /mnt/home/)
* autogen devx_2*.sfs
* automake (preferably version 1.4 or higher) (HAVE, WHEN HAVING dev_21x.sfs in /mnt/home/)
* dbus >= 1.0.2 disabled
* gcc >= 4 .1 (HAVE, WHEN HAVING dev_21x.sfs in /mnt/home/)
* libgconf2-dev disabled
* gettext (HAVE)
* glibc >= 2.5 (Puppy 2.14 version is 2.3.5!!! Must find way to upgrade...) 2.3.5 did work
* glitz was compiled and packed to dotpup. Now disabled
* GTK (HAVE)
* libglib2.0-dev devx_2*.sfs
* libtool (HAVE, WHEN HAVING dev_21x.sfs in /mnt/home/)
* MesaLib-6.5.2 Last development release compiled and packed to dotpup few hours ago
* nVidia binary drivers - nvidia-0.9631 (slight frame speed up), ati-amd, ati drivers, or xf86-Intel *drivers, etc. have
* pango devx_2*.sfs
* python-dbus >= 0.80.1 disabled
* python-gtk2-dev >= 2.10.3 http://www.murga-linux.com/puppy/viewto ... 08&t=16424
* python-pyrex http://www.murga-linux.com/puppy/viewto ... 08&t=16424
* subversion not needed
* Xorg 7.1 or higher recommended, preferably AIGLX enabled (HAVE, NOT SURE ON OLDER VERSIONS OF PUPPY below 2.14) compiled and packed to dotpup / Xorg 7.2
text in blue is what I've done.
[url=http://www.puppylinux.com][img]http://i.imgur.com/M4OyHe1.gif[/img][/url]
@jimhap:
(c) Someone else has compiled it for me ;=)
(d) I'm sort of off-topic really (sorry) since my concern was getting a driver going with a new Xorg, not with Beryl per se.
Don't worry about it: (a) I wasn't aware of the hidden header unionfs thing, and (b) I've since learned that the patch for the driver I was trying to compile has a bug preventing it from working properly with new versions of Xorg.About that compile: can you give me the options of the configure? (by ./configure --help ) You should watch when configuring for "shared libraries".
(c) Someone else has compiled it for me ;=)
(d) I'm sort of off-topic really (sorry) since my concern was getting a driver going with a new Xorg, not with Beryl per se.
I've done more tests on the PC with the Savage chipset and found something interesting.
Xorg looks for the DRI modules at /usr/X11R7/lib/dri/:
But is 'libGL'(MesaLibs) who look for DRI hardware drivers. Here is where my Mesa-6.5.2 build is installed:
And glxinfo shows the DRI module as renderer(hardware):
After run beryl-manager:
Now, if I make a symlink to pass the (EE) AIGLX error.
Xorg.log won't have any error message after restart X. Though some warnings (WW):
Later, when I ran beryl-manager:
Was strange, Beryl had run on a mixed mode(software and hardware renderer?), but not in hardware mode since this card in no supported.
This test was done installing Dotpups, not booting from my Puppy+Beryl CD. All these DotPups are uploaded. I'll give instructions about how to install Beryl for Intel, ATI, and other cards soon, after check if this issue(running beryl on unsupported cards) can cause more problems.
Xorg looks for the DRI modules at /usr/X11R7/lib/dri/:
Code: Select all
(==) AIGLX enabled
(II) LoadModule: "dri"
(II) Loading /usr/X11R7/lib/xorg/modules/extensions//libdri.so
(II) Loading extension XFree86-DRI
(II) LoadModule: "savage"
(II) Loading /usr/X11R7/lib/xorg/modules/drivers//savage_drv.so
(EE) AIGLX error: dlopen of /usr/X11R7/lib/dri/savage_dri.so failed (/usr/X11R7/lib/dri/savage_dri.so: cannot open shared object file: No such file or directory)
(EE) AIGLX: reverting to software rendering
Code: Select all
# Installation directories (for make install)
INSTALL_DIR = /usr/X11R7
DRI_DRIVER_INSTALL_DIR = /usr/X11R7/lib/xorg/modules/dri
Code: Select all
display: :0 screen: 0
direct rendering: Yes
server glx vendor string: SGI
OpenGL renderer string: Mesa DRI ProSavageDDR 20061110 AGP 1x x86/MMX/SSE2
OpenGL version string: 1.2 Mesa 6.5.2
Code: Select all
sh-3.00# beryl-manager
sh-3.00# libGL warning: 3D driver claims to not support visual 0x4b
**************************************************************
* Beryl system compatiblity check *
**************************************************************
Detected xserver : AIGLX
Checking Display :0.0 ...
Checking for XComposite extension : passed (v0.3)
Checking for XDamage extension : passed
Checking for RandR extension : passed
Checking for XSync extension : passed
Checking Screen 0 ...
libGL warning: 3D driver claims to not support visual 0x4b
Checking for GLX_SGIX_fbconfig : passed
Checking for GLX_EXT_texture_from_pixmap : passed
Checking for non power of two texture support : passed
Checking maximum texture size : passed (2048x2048)
Now, if I make a symlink to pass the (EE) AIGLX error.
Code: Select all
ln -s /usr/X11R7/lib/xorg/modules/dri/ /usr/X11R7/lib/
Code: Select all
(==) AIGLX enabled
(II) LoadModule: "dri"
(II) Loading /usr/X11R7/lib/xorg/modules/extensions//libdri.so
(II) Loading extension XFree86-DRI
(II) SAVAGE(0): [drm] Enabling ShadowStatus for DRI.
(II) SAVAGE(0): [dri] visual configs initialized
(**) SAVAGE(0): DRI is enabled
(--) SAVAGE(0): Chose mode 115 at 85Hz.
(WW) AIGLX: 3D driver claims to not support visual 0x23
(WW) AIGLX: 3D driver claims to not support visual 0x24
(WW) AIGLX: 3D driver claims to not support visual 0x25
(WW) AIGLX: 3D driver claims to not support visual 0x26
(WW) AIGLX: 3D driver claims to not support visual 0x27
(WW) AIGLX: 3D driver claims to not support visual 0x28
(WW) AIGLX: 3D driver claims to not support visual 0x29
(WW) AIGLX: 3D driver claims to not support visual 0x2a
(WW) AIGLX: 3D driver claims to not support visual 0x2b
(WW) AIGLX: 3D driver claims to not support visual 0x2c
(WW) AIGLX: 3D driver claims to not support visual 0x2d
(WW) AIGLX: 3D driver claims to not support visual 0x2e
(WW) AIGLX: 3D driver claims to not support visual 0x2f
(WW) AIGLX: 3D driver claims to not support visual 0x30
(WW) AIGLX: 3D driver claims to not support visual 0x31
(WW) AIGLX: 3D driver claims to not support visual 0x32
(II) AIGLX: Loaded and initialized /usr/X11R7/lib/dri/savage_dri.so
(II) GLX: Initialized DRI GL provider for screen 0
Code: Select all
sh-3.00# beryl-manager
sh-3.00# libGL warning: 3D driver claims to not support visual 0x4b
** (beryl-manager:31066): WARNING **: Couldn't find a Selection Owner, perhaps n o WM running?
Otherwise, manually kill your wm, and report the bug to the developers, it doesn 't follow the standards.
Falling back to looking for a defined WM in xlsclients.
**************************************************************
* Beryl system compatiblity check *
**************************************************************
Detected xserver : AIGLX
Checking Display :0.0 ...
Checking for XComposite extension : passed (v0.3)
Checking for XDamage extension : passed
Checking for RandR extension : passed
Checking for XSync extension : passed
Checking Screen 0 ...
libGL warning: 3D driver claims to not support visual 0x4b
Checking for GLX_SGIX_fbconfig : passed
Checking for GLX_EXT_texture_from_pixmap : passed
Checking for non power of two texture support : failed
Support for non power of two textures missing
libGL warning: 3D driver claims to not support visual 0x4b
beryl: Support for non power of two textures missing
This test was done installing Dotpups, not booting from my Puppy+Beryl CD. All these DotPups are uploaded. I'll give instructions about how to install Beryl for Intel, ATI, and other cards soon, after check if this issue(running beryl on unsupported cards) can cause more problems.
[url=http://www.puppylinux.com][img]http://i.imgur.com/M4OyHe1.gif[/img][/url]
video capture plugin
The vidcap plugin is working Have you seen ubuntu+beryl videos? now we can make Puppy+Beryl videos!! dotpups soon...
EDIT: uploaded http://murga-linux.com/puppy/viewtopic. ... 469#114469
EDIT: uploaded http://murga-linux.com/puppy/viewtopic. ... 469#114469
[url=http://www.puppylinux.com][img]http://i.imgur.com/M4OyHe1.gif[/img][/url]