The time now is Thu 23 May 2013, 04:35
All times are UTC - 4 |
| Author |
Message |
tex
Joined: 23 Jan 2006 Posts: 12 Location: Richardson, Texas
|
Posted: Fri 19 Sep 2008, 00:10 Post subject:
same problem Subject description: missing files |
|
Compiz is working, but I cannot configure it. I am missing libtk8.5.so and libtel8.5.so which belong to: usr/lib/python2.5/lib-dynload/_tkinter.so. I too have looked and cannot find any info. I really appreciate this great how to!
|
|
Back to top
|
|
 |
tombh

Joined: 12 Jan 2007 Posts: 422 Location: Bristol, UK
|
Posted: Fri 19 Sep 2008, 07:31 Post subject:
|
|
@cb88: I've never tried that myself, but thanks for mentioning it.
@aoiyamoto: Great news! Thanks for persevering, it will inspire others I'm sure. The dbus error is just a warning and nothing to worry about, if you autostart CF at boot time then you won't see any errors. As far as I know the only other window-decorators, as they're called, that you can have with CF are the gtk-window-decorator and the kde-window-decorator, neither of which are included with my CF dotpet -- they need to be configured in at compile time. However, forum member wow has a CF dotpet for Puppy 4 that does have the gtk-window-decorator with it.
@tex: This is great news too! What graphics card do you have?
I'm going tohave to look into these missing python deps as I've not come across the problem before -- though I suspect it is to do with the fact that my How To links to the Puppy 3 version of Python. Ah! stevenbinion has compile python and essential modules for Puppy 4. You will need the python-cairo, python-gtk and python-gobject modules too remember. I think they'll already be included if you decide to use stevenbinion's SFS. I'm not sure whether installing this newer version will overwrite the older version. Please let me know how this goes, so I can update the How To, if there is success.
_________________ Colour-Memories Database
|
|
Back to top
|
|
 |
aoiyamoto
Joined: 16 Aug 2008 Posts: 29
|
Posted: Fri 19 Sep 2008, 16:45 Post subject:
|
|
Still missing those two files after installing all of his .pets.
Also, I don't know if I should or not, but I don't have a " /usr/lib/python2.5/site-packages/ccm/" directory.
|
|
Back to top
|
|
 |
Max Headroom

Joined: 28 Jun 2006 Posts: 181 Location: GodZone Kiwi
|
Posted: Fri 19 Sep 2008, 18:16 Post subject:
Sorry Tom I'm Feeling Soo Stupid! Subject description: But which is th' Correct NVidia Driver Package 4 My Card? |
|
My Card is NVidia GeForce FX5200, does that mean it is Gf5?
|
|
Back to top
|
|
 |
tex
Joined: 23 Jan 2006 Posts: 12 Location: Richardson, Texas
|
Posted: Fri 19 Sep 2008, 19:26 Post subject:
System and Graphics card |
|
I have a Dell 700m system with Intel(R) 82852/82855 GM/GME Graphics Controller. I am using SkinnyPup 4.0a. I installed XFCE-442-Dingo.pet and it needed zlibsCups.pet. I followed all your suggestions for installing Compiz. Adding modprobe -n i915 to rc.local fixed my dri problem.
Thanks again!
|
|
Back to top
|
|
 |
aoiyamoto
Joined: 16 Aug 2008 Posts: 29
|
Posted: Sat 20 Sep 2008, 00:30 Post subject:
|
|
Okay, so I managed to fix everything, or at least 90% of it by just taking the lib files I needed and other files I needed from wNOP. Anyway, I need help with a few things.
First off, when I have my windowmanager text file set to startxfce4 it loads up my icewm than my xfce4m also, it paints the icewm screen until I press a buttion, or until I click something. This does not happen if I type startxfce4 at the prompt though. So is there a way I can have it call startxfce4 instead of startx?
Secondly, Where do I put the line "LIBGL_ALWAYS_INDIRECT=1 compiz --replace --indirect-rendering --sm-disable ccp &" ?? I need to know exact placement, cause I didn't know where near the top to place it.
Thanks for all your help so far, by the way.
|
|
Back to top
|
|
 |
tex
Joined: 23 Jan 2006 Posts: 12 Location: Richardson, Texas
|
Posted: Sat 20 Sep 2008, 13:15 Post subject:
Tried .sfs and .pets Subject description: python missing files |
|
I was wondering where on the menu ccsm should be? It is not on my menu and will not start from the terminal with the ccsm command. Is that because of the missing python files? I uninstalled python for ccsm and installed the .sfs from Steve Binion, but that did not cause ccsm to work and my windows became huge. I tried installing all the .pets, but I came up with other missing files, libORBit-imodule-2.so.0 and libORBit-2.so.0. Compiz runs at start, but I cannot configure it.
Aoiyamoto, my .xinitrc file starts like this:
!/bin/sh
# $Xorg: xinitrc.cpp,v 1.3 2000/08/17 19:54:30 cpqbld Exp $
LIBGL_ALWAYS_INDIRECT=1 compiz --replace --indirect-rendering --sm-disable ccp &
sleep 3
|
|
Back to top
|
|
 |
37fleetwood

Joined: 09 Aug 2007 Posts: 403
|
Posted: Mon 22 Sep 2008, 02:05 Post subject:
|
|
ok, I'm here. I have an unaltered wNOP cd on my computer.what do we need to do first? tell me exactly what to do and I'll do it and we'll get this thing working. first order of business is to get 3d accelleration working without actually running it. I can either boot in with vesa or I can edit xorg.conf from the xorg wizard and remove
| Code: | # Needed for Compiz-Fusion to function
Load "dri" |
which will get xorg going but not 3d accelleration. which is best for you? also I understand from some of the reference threads that I need to be in 24 bit color which is no problem. xorg will let me run 1440 x 900 @ 24bit color with no problems. I've been reading the posts and none of them address what to do if you can't get the computer to run in xorg with 3d messed up. they all seem to assume the computer will at least run without the screen scrambled so I was lost as to what i should do. I can't really do the diagnostic stuff described as it requires dri to be loaded, doesn't it? also do you think the fact that I'm running on the DVI cable have any bearing on the situation? I know I tried suse once and it would go on svga but not on DVI. maybe I'll try restarting hooked the other way just for giggles.
Scott
Last edited by 37fleetwood on Tue 23 Sep 2008, 09:25; edited 1 time in total
|
|
Back to top
|
|
 |
tombh

Joined: 12 Jan 2007 Posts: 422 Location: Bristol, UK
|
Posted: Tue 23 Sep 2008, 04:12 Post subject:
|
|
@aoiyamoto: I reckon those missing files are part of the Tk toolkit (a widget library like GTK) which Barry stopped supporting by default in Puppy 4. I wonder though whether just installing all stevenbinion's pets will automatically replace the old python. What do you get when you type My feeling is that stevenbinion would have compiled his python in Puppy 4 without Tk, thus making his python pets non-Tk dependant. Anyway, CCSM works now, that's the main thing!
Does tex's advice for .xinitrc help?
| Quote: | Aoiyamoto, my .xinitrc file starts like this:
!/bin/sh
# $Xorg: xinitrc.cpp,v 1.3 2000/08/17 19:54:30 cpqbld Exp $
LIBGL_ALWAYS_INDIRECT=1 compiz --replace --indirect-rendering --sm-disable ccp &
sleep 3 |
@Max Headroom: I reckon it does -- go for it!
@tex: Fantastic! Compiz-Fusion running in SkinnyPup, you're paving the way to making any puplet wobbly-compatible So where are you now with CCSM? You've uninstalled python_for_CCSM and installed stevenbinion's SFS and pets? I would suggest only using one -- either the pets or the SFS. What happens when you type Yes, CCSM should have a menu entry, what happens when you type and what is the read out when you just type
@Scott: Hi there, we need to start with Puppy 4 here, remeber wNOP is based on Puppy 3 and is not applicable to this How To -- so get either the standard Puppy 4 Dingo or forum member grey's NOP 4.0. Then let me know how it goes following the instructions to set up DRI...
_________________ Colour-Memories Database
|
|
Back to top
|
|
 |
37fleetwood

Joined: 09 Aug 2007 Posts: 403
|
Posted: Tue 23 Sep 2008, 09:21 Post subject:
|
|
ok, running nop4.0 with xorg 1440 x 900 @24bit color boots fine.
installed "xorg_xorg_full_dri-7.3.pet" and made changes to "findhostbridge" and "rc.local" as directed, also made the changes to "xorg.conf" as directed.
saved to hard drive so I could still use the disc later after however many tries this takes. upon reboot same scrambled crap I've been getting with wNOP v0.2
Ctrl+Alt+Backspace and restart x in vesa.
downloaded "glxinfo" (which is a .pup by the way and NOP doesn't have the stuff to allow it to be installed, and I didn't feel like wading through all the forum to find it! it worked withought it anyway I think.)
ran
resulting in:
| Code: | Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Error: couldn't find RGB GLX visual
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
|
ran
| Code: | | cat /var/log/Xorg.0.log | grep dri |
resulting in:
| Code: | sh-3.00# cat /var/log/Xorg.0.log | grep dri
X.Org XInput driver : 0.7
(II) LoadModule: "dri"
(II) Loading /usr/X11R7/lib/xorg/modules/extensions//libdri.so
(II) Module dri: vendor="X.Org Foundation"
(II) Loading /usr/X11R7/lib/xorg/modules/drivers//ati_drv.so
ABI class: X.Org XInput driver, version 0.7
ABI class: X.Org XInput driver, version 0.7
(II) ATI: ATI driver wrapper (version 6.7.195) for chipsets: mach64, rage128, radeon
(II) Loading /usr/X11R7/lib/xorg/modules/drivers//radeon_drv.so
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: node name is /dev/dri/card0
(II) RADEON(0): [dri] Found DRI library version 1.3.0 and kernel module version 1.25.0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: node name is /dev/dri/card0
(II) RADEON(0): [drm] created "radeon" driver at busid "pci:0000:01:00.0"
(II) RADEON(0): [dri] Visual configs initialized
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: node name is /dev/dri/card0
(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/r200_dri.so
sh-3.00#
|
again, sorry I'm too new to know much about what this all means. I can however see clearly enough that something is saying it doesn't support something I have. please let me know what to do next.
thanks
Scott
|
|
Back to top
|
|
 |
aoiyamoto
Joined: 16 Aug 2008 Posts: 29
|
Posted: Tue 23 Sep 2008, 21:40 Post subject:
|
|
Okay, I almost got everything 100%, but there are a few problems.
If I load compiz on it's own at start up, than emerald doesn't work.
If I call emerald --replace before startxfce4 than startxfce4 doesn't work.
If I call startxfce4 before emerald --replace, than emerald --replace doesn't work.
Now after I get xfce4 running I caqn go to a terminal and type emerald --replace and it works. but than it gets stuck so I can't use that terminal anymore and have to open another one. I'm about 80% sure that the stuck terminal is the reason xfce4 doesn't work at startup. Anyone know how to fix that?
|
|
Back to top
|
|
 |
dinky

Joined: 19 Jan 2008 Posts: 699
|
Posted: Wed 24 Sep 2008, 17:25 Post subject:
|
|
Hi tombh, couple minutes free between babies and house-duties...lol...
here's the Xorg.0.log attached. What can you tell me? No longer working from unleashed, using Puppy 4 instead. The support for the eeepc screen res isn't bad... anyway, decided it's going to be much easier rebuilding once I figure how to get compiz-fusion running without making any changes. So followed your how too to a tee, and can't get thi running on the eeepc. Keep in mind this is the same laptop I built eeetiger for, which runs beautifully on it. That's basically a remaster of your wNOP.
My portable hard drive went kaput, so I've been unable to play around much. Oh yeah, and my daughter was born last Saturdat, computers are a very loow priority. Thinking about getting a 4Gb
flash card today, so should be a bit easier to play around. anyway, here's the log, what can you tell me?
p.s. can't seem to attach it. Have posted it on:
http://www.curiouslegends.com.au/tigerpup/Xorg.0.log
|
|
Back to top
|
|
 |
wow
Joined: 29 Jun 2006 Posts: 950
|
Posted: Wed 24 Sep 2008, 22:12 Post subject:
|
|
@37fleetwood: Try to change screen resolution to 800 x 600 @24bit, I'm not sure about this but seems that Open Source drivers can't get DRI working at 24bbp (except for intel and ati gpus) or higher resolutions.
_________________

|
|
Back to top
|
|
 |
37fleetwood

Joined: 09 Aug 2007 Posts: 403
|
Posted: Wed 24 Sep 2008, 23:10 Post subject:
|
|
@wow:
Ok, just tried and no go. I had tried all resolutions and all color depths and all refresh rates before but did it again because I hadn't tried it with puppy 4. any other ideas?
Scott
|
|
Back to top
|
|
 |
tombh

Joined: 12 Jan 2007 Posts: 422 Location: Bristol, UK
|
Posted: Thu 25 Sep 2008, 15:34 Post subject:
|
|
@aoiyamoto: I don't think that WINDOWMANAGER text file is supposed to be edited, my impression is that it is automatically updated when a new window manager is used in order to remember it for next boot. Thus it should suffice to exit to X, type startxfce4 then never do anything again because the new window manager has automatically been saved to the WINDOWMANAGER text file which is checked by the script at every boot.
Now, as for your emerald dilemma, what you want to do is open up CCSM, goto Window Decoration, then type in the "Command" field, "emerald --replace". This will automatically start emerald for you each time CF is started.
@dinky: A new little person, how exciting! Mmm, makes Compiz-Fusion look boring now. Anyway, you need to manually fetch the i915 module from zdrv_400.sfs. It's pretty easy to do, just type , or to automate it for every boot, add that code to the end of /etc/rc.d/rc.local
@Scott: What can I say!? We've been here so many times, a garbage screen and I just can't figure it out. Wow had a good idea there, but a shame that didn't work I have to say I'm at a loss, I'm very confident that it is not because you are doing something wrong. My only thought is that your graphics card is Kaput. Can you get 3D accelaration going in Windows I wonder? If Google Earth works in Windows then that means you're 3D acceleration is working. Could you somehow get a picture of what the garbage screen looks like?
_________________ Colour-Memories Database
|
|
Back to top
|
|
 |
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum You cannot attach files in this forum You can download files in this forum
|
Powered by phpBB © 2001, 2005 phpBB Group
|