Beryl on Puppy(Installation guide for nvidia gfx cards.)
-
- Posts: 56
- Joined: Fri 19 Jan 2007, 14:06
- Contact:
could you add all needed dotpups to a tar.gz and upload them? (without Xorg72 and python)
This would make it easier to mirror them.
It would be great, if you could upload it here:
http://murga-linux.com/puppy/viewtopic. ... 9400#99400
I can extract it on the server then.
Mark
This would make it easier to mirror them.
It would be great, if you could upload it here:
http://murga-linux.com/puppy/viewtopic. ... 9400#99400
I can extract it on the server then.
Mark
It's too soon, I need to do more tests, remove some unnecessary dependences, etc. For now It got Beryl working with cairo-1.4[with svg] instead of cairo-1.3[with svg, glitz and xcb].MU wrote:It would be great, if you could upload it here:
http://murga-linux.com/puppy/viewtopic. ... 9400#99400
Mark
[url=http://www.puppylinux.com][img]http://i.imgur.com/M4OyHe1.gif[/img][/url]
*edit - Nevermind. I think I found the answer here, at the bottom:
http://wiki.x.org/wiki/CompileXserverManually
etc...
Is this what Mark is talking about when he says '3D modules (DRI)'? How do I compile all these?
I've never compile x before and I'm a bit lost. Thanks for any tips.
http://wiki.x.org/wiki/CompileXserverManually
I built up xorg7.1 with packages/xorg directory out of the latest T2 trunk and I get a bunch of errors like this in /tmp/xorgprobe.txt when I try to run xorg.MU wrote:But note:
If you upgrade Xorg, 3D modules (DRI) from Xorg 7.0 might no longer work!
But I'm not shure about this.
Code: Select all
(EE) module ABI major version (0) doesn't match the server's version (1)
(EE) Failed to load module "apm" (module requirement mismatch, 0)
(EE) module ABI major version (0) doesn't match the server's version (1)
(EE) Failed to load module "ark" (module requirement mismatch, 0)
(EE) module ABI major version (0) doesn't match the server's version (1)
(EE) Failed to load module "ati" (module requirement mismatch, 0)
Is this what Mark is talking about when he says '3D modules (DRI)'? How do I compile all these?
I've never compile x before and I'm a bit lost. Thanks for any tips.
another issue
Just to confirm, Gxine crashes after install the x11-7.2 upgrade. This mostly happens when you resize the window.
[url=http://www.puppylinux.com][img]http://i.imgur.com/M4OyHe1.gif[/img][/url]
I'm not at home, can't give you more detailed info at this moment.John Doe wrote:Is this what Mark is talking about when he says '3D modules (DRI)'? How do I compile all these?
I've never compile x before and I'm a bit lost. Thanks for any tips.
Video drivers for x11-7.1(sources):
http://ftp.x.org/pub/X11R7.1/src/driver/
And look for:
xf86-video-ati-X11R7.1-6.6.0.tar.bz2
To replace Puppy's Xorg you may compile everything adding these options to the configure script:
<your arguments/options/parameters/whatever> --prefix=/usr/X11R7/ --bindir=/usr/X11R7/bin --libdir=/usr/X11R7/lib --includedir=/usr/X11R7/include --sysconfdir=/etc --localstatedir=/var
Or take a look at the content of any .pc file at: /usr/X11R7/lib/pkgconfig
Video modules for my x11-7.2 dotpup are available at:
http://hosted.filefront.com/rockinfreak/1921409
But beware I compiled Xorg without the glx extension, so you won't have 3D acceleration. I compiled Xorg while the nvidia drivers were installed and I forgot to enable a generic GLX extension. To solve it Xorg needs to be compiled specifying the Mesa's source path(I'm not sure).
Also I've tested some of the video modules and seems to work fine, but without hardware acceleration.
[url=http://www.puppylinux.com][img]http://i.imgur.com/M4OyHe1.gif[/img][/url]
Could a request be made to the beryl devs that icewm compatability be in the next release? Not to mention more graphics card compatability. Is an sfs module planed I think WhoDo said that proprietary codecs can be included in sfs modules since they are not part of the main distro you might want to check that out.
I don't think so. JWM, IceWM, Fluxbox and Beryl are window managers. They have the same purpose. Beryl needs a desktop environment to work properly since it replaces only the window manager(xfwm for xfce or kwin for kde) and you can only have one WM running at a time.
[url=http://www.puppylinux.com][img]http://i.imgur.com/M4OyHe1.gif[/img][/url]
Really interesting this, very nice work.
I've also read that DRI will need to be updated if you change Xorg.
One request, as a byproduct, if someone could build an updated overall Xorg package that installs the required components and deps in order, that would be very nice. Also headers. I need an updated Xorg for compiling another module.
In the meantime I'll have a go at compiling my own.
I've also read that DRI will need to be updated if you change Xorg.
One request, as a byproduct, if someone could build an updated overall Xorg package that installs the required components and deps in order, that would be very nice. Also headers. I need an updated Xorg for compiling another module.
In the meantime I'll have a go at compiling my own.
I'm thinking on post this xorg upgrade to the "Additional Software" section after recompile xorg with the GLX extension. Then, ATI and Intel users will be able to run Beryl on Puppy with AIGLX. For the moment everything here is only for testers, I recommend don't use it on your main Puppy installation.wdef wrote:One request, as a byproduct, if someone could build an updated overall Xorg package that installs the required components and deps in order, that would be very nice. Also headers
Xorg upgrade needs(in this order):
EDIT:Before install x11-7.2-upd.pup you must install the xf86VideoModule for your card.
- xcb-proto-1.0.pup
libxcb-1.0.pup
libdrm-2.3.0.pup
x11-7.2-upd.pup (and follow its instructions)
Last edited by wow on Tue 17 Apr 2007, 00:03, edited 1 time in total.
[url=http://www.puppylinux.com][img]http://i.imgur.com/M4OyHe1.gif[/img][/url]
Wow, I'm having trouble with the new i810 module. New Xorg's not finding it. Instead it tries to load the old module => no X.
EDIT: The new i810 driver seems to be in a weird location
EDIT: Good, vesa driver's working though. Seamonkey doesn't seem to want to work with it?
UPDATE FIXED: new i810 *is* installed in a weird location. Doing this and editing xorg.conf fixed it:
So the package needs fixing.
EDIT: The new i810 driver seems to be in a weird location
EDIT: Good, vesa driver's working though. Seamonkey doesn't seem to want to work with it?
UPDATE FIXED: new i810 *is* installed in a weird location. Doing this and editing xorg.conf fixed it:
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
Last edited by wdef on Sun 15 Apr 2007, 21:46, edited 1 time in total.
PS: Sorry to be a pest, wow.
Does your Xorg contain fontsproto?
I'm trying to compile a patched version of the nsc driver and ./configure can't seem to find it in your Xorg.
EDIT: Actually it wants all of these:
configure: error: Package requirements (xorg-server >= 1.0.99.901 xproto fontsproto randrproto renderproto videoproto xextproto xf86dgaproto) were not met
UPDATE: I compiled and installed fontsproto ok but ./comfigure still can't see it. Setting
seems to make no difference.
Did you compile this Xorg on Puppy or was it Slackware or something?
From tarballs, with jhbuild ...???
Does your Xorg contain fontsproto?
I'm trying to compile a patched version of the nsc driver and ./configure can't seem to find it in your Xorg.
EDIT: Actually it wants all of these:
configure: error: Package requirements (xorg-server >= 1.0.99.901 xproto fontsproto randrproto renderproto videoproto xextproto xf86dgaproto) were not met
UPDATE: I compiled and installed fontsproto ok but ./comfigure still can't see it. Setting
Code: Select all
export PKG_CONFIG_PATH=/usr/X11R7/lib/pkgconfig
Did you compile this Xorg on Puppy or was it Slackware or something?
From tarballs, with jhbuild ...???
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)
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.
@wdef: How did you compile fontsproto?
(That is, the things you typed in for configure, even if it's before the "./configure")
The reason I'm asking is that if you just typed "./configure" it probably installed the "pc" file somewhere else, so configure can't find it. (usually if im right installs in /usr/local/lib/pkgconfig/)
Try that. Type:
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
Or to tell them here:
From the link above:
(their way of saying it @ http://wiki.beryl-project.org/wiki/Building_Beryl)
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.
@wdef: How did you compile fontsproto?
(That is, the things you typed in for configure, even if it's before the "./configure")
The reason I'm asking is that if you just typed "./configure" it probably installed the "pc" file somewhere else, so configure can't find it. (usually if im right installs in /usr/local/lib/pkgconfig/)
Try that. Type:
(Yes, type it EXACTLY like that. export doesn't work for me, so I set the PKG_CONFIG_PATH variable, then space, then ./configure)PKG_CONFIG_PATH="/usr/local/lib/pkgconfig" ./configure
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
Or to tell them here:
From the link above:
Hope this helps....[/quote]
The following components are needed to compile Beryl:
* intltool
* libdbus-1-dev
* libdbus-glib-1-2
* libgl1-mesa-dev
* libglu1-mesa
* libglu1-mesa-dev
* libglu1-xorg-dev
* libice-dev
* libjpeg62-dev
* libpng12-dev
* librsvg2-dev
* libsm-dev
* libstartup-notification0-dev
* libwnck-dev
* libxcomposite-dev
* libxdamage-dev
* libxinerama-dev
* libxrandr-dev
* x11proto-gl-dev
* autoconf (HAVE, WHEN HAVING dev_21x.sfs in /mnt/home/)
* autogen
* automake (preferably version 1.4 or higher) (HAVE, WHEN HAVING dev_21x.sfs in /mnt/home/)
* dbus >= 1.0.2
* gcc >= 4 .1 (HAVE, WHEN HAVING dev_21x.sfs in /mnt/home/)
* libgconf2-dev
* gettext (HAVE)
* glibc >= 2.5 (Puppy 2.14 version is 2.3.5!!! Must find way to upgrade...)
* glitz
* GTK (HAVE)
* libglib2.0-dev
* libtool (HAVE, WHEN HAVING dev_21x.sfs in /mnt/home/)
* MesaLib-6.5.2 Last development release
* nVidia binary drivers - nvidia-0.9631 (slight frame speed up), ati-amd, ati drivers, or xf86-Intel *drivers, etc.
* pango
* python-dbus >= 0.80.1
* python-gtk2-dev >= 2.10.3
* python-pyrex
* subversion
* Xorg 7.1 or higher recommended, preferably AIGLX enabled (HAVE, NOT SURE ON OLDER VERSIONS OF PUPPY below 2.14)
*edit, references to "your" and the "thanks" is directed at "wow". Sorry about my stupidity. The rest is for everyone.
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.
I built xorg up using T2 updating the xorg trunk (and one X11 trunk package [mesa]), thanks to your post in the first thread.
Took detailed notes while building a script. Perhaps it could save Barry some time in possibly integrating an xorg upgrade.
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.
*Thanks for all the help and sorry on the delay in responding. I stuck somewhere between the two hemisphere's of my brain.
CODE:
First delete the xorg trunk in t2 and copy in the latest trunk.
Then update the mesa package in x11 trunk.
(maybe you emerge here, I can't figure all that out)
Made this little script to compile all the extracted drivers I downloaded:
Also have a list to do them with T2 but haven't tested it. Not sure where Kirk got the synaptec touchpad driver.
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.
I built xorg up using T2 updating the xorg trunk (and one X11 trunk package [mesa]), thanks to your post in the first thread.
Took detailed notes while building a script. Perhaps it could save Barry some time in possibly integrating an xorg upgrade.
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.
*Thanks for all the help and sorry on the delay in responding. I stuck somewhere between the two hemisphere's of my brain.
CODE:
First delete the xorg trunk in t2 and copy in the latest trunk.
Then update the mesa package in x11 trunk.
(maybe you emerge here, I can't figure all that out)
Code: Select all
#!/bin/sh
#Careful with this one.
#./scripts/Cleanup
./scripts/Build-Pkg -cfg puppy21x compositeproto
./scripts/Build-Pkg -cfg puppy21x fixesproto
./scripts/Build-Pkg -cfg puppy21x xproto
./scripts/Build-Pkg -cfg puppy21x libxau
./scripts/Build-Pkg -cfg puppy21x libxaw
./scripts/Build-Pkg -cfg puppy21x libxcomposite
./scripts/Build-Pkg -cfg puppy21x libxcursor
./scripts/Build-Pkg -cfg puppy21x damageproto
./scripts/Build-Pkg -cfg puppy21x libxdamage
./scripts/Build-Pkg -cfg puppy21x libxevie
./scripts/Build-Pkg -cfg puppy21x libxext
./scripts/Build-Pkg -cfg puppy21x libxfixes
./scripts/Build-Pkg -cfg puppy21x libxfont
./scripts/Build-Pkg -cfg puppy21x libxinerama
./scripts/Build-Pkg -cfg puppy21x libxpm
./scripts/Build-Pkg -cfg puppy21x libxrender
./scripts/Build-Pkg -cfg puppy21x scrnsaverproto
./scripts/Build-Pkg -cfg puppy21x xdm
./scripts/Build-Pkg -cfg puppy21x xextproto
./scripts/Build-Pkg -cfg puppy21x xineramaproto
./scripts/Build-Pkg -cfg puppy21x xkbcomp
./scripts/Build-Pkg -cfg puppy21x glproto
./scripts/Build-Pkg -cfg puppy21x libdrm
./scripts/Build-Pkg -cfg puppy21x kbproto
./scripts/Build-Pkg -cfg puppy21x makedepend
./scripts/Build-Pkg -cfg puppy21x mesa #x11
./scripts/Build-Pkg -cfg puppy21x libx11
#this keeps xorg-server build from bombing half way through
mkdir /etc/profile.d
touch /etc/profile.d/windowmanager
./scripts/Build-Pkg -cfg puppy21x xorg-server
Code: Select all
#!/bin/sh
DIRENTRIES="`ls -1 | tr "\n" " "`"
for ONEENTRY in $DIRENTRIES
do
cd $ONEENTRY
make clean
./configure --prefix=/usr/X11R7
make
make install
# make install DESTDIR=/xorg-server-7.1
cd ../
done
@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]