Lighthouse Pup 4.43 Gu2 215M
The 3D-Demo runs perfectly fine @ 30.3 FPS with a Load of 35% (polys @ 106) on a Dual Core Pentium 1.86Ghz w/ 4Gb ram and an Intel GM965 Integrated Graphics Chipset.tazoc wrote:Hi shankargopal, xorg.conf indicates an Intel graphics adapter was detected. If this is correct, it may not be possible to enable Desktop Effects with the Xorg driver in LHP. However some have had success with MU's Alternative Xorg/xserver 1.6.3/Intel pets, available here (experimental). Boot off your LHP CD with 'puppy pfix=ram', making a clean pupsave before trying this, just in case...shankargopal wrote:Hi Tazoc and friends,
1) I have downloaded the Mariner ISO with the KDE SFS built in. I'd like to try using KDE 4 Desktop Effects on one of the systems which I use Puppy on (the xorg.conf of this system is attached). KDE Desktop Effects has worked before on this system in other distros (e.g. Sidux). In LH it says effects are disabled as xcomposite and xdamage extensions are not available. Is there a way I can set these up? The xorg.conf file is attached, it's not a zip, just renamed to xorg.conf.zip to allow posting. Or do I need to download the Compiz Fusion SFS?
NB: Tried running "3D-Demo" from the menu (glxgears, I presume?), got "DRI enabled should run fast", and then X crashed and dropped me to a command prompt.
If I get time this coming week, I'll do some testing with compiz on my kit. Im running F so far, if I have no luck I might try an update to G to see if that helps out.tazoc wrote:I don't know if anyone has been able to use Compiz with an Intel display adapter in LHP. I don't have an Intel box to test with. Some have had success with MU's Alternative Xorg/xserver 1.6.3/Intel pets but I haven't seen anything re: Compiz and those pets. I think you'll need the Mariner SFS for DRI and 3D, but again I don't know if Compiz will work for you. It is a hit-and-miss proposition with Compiz...
-TazOC
Lighthouse Pup 4.43 Gu1 released
Lighthouse Pup 4.43 Gu1 released
Updated init and shutdown scripts with choice of ext2 or ext3 pupsave on an ext3/4/reiserfs host partition, or ext2 on vfat/ntfs. Mounts spupsave.3fs as ext3 and skips non-version 4.0 SFS files during bootup
Updated the save-to-flash script (snapmergepuppy) today. New script also available here
Updated to Wine 1.1.40 more release notes here
-TazOC
Updated init and shutdown scripts with choice of ext2 or ext3 pupsave on an ext3/4/reiserfs host partition, or ext2 on vfat/ntfs. Mounts spupsave.3fs as ext3 and skips non-version 4.0 SFS files during bootup
Updated the save-to-flash script (snapmergepuppy) today. New script also available here
Updated to Wine 1.1.40 more release notes here
-TazOC
[url=http://www.lhpup.org/][b][size=100]lhpup.org[/size][/b] [img]http://www.lhpup.org/gallery/images/favicon.png[/img][/url] [url=http://www.lhpup.org/release-lhp.htm#602]Lighthouse 64 6.02[/url]
-
- Posts: 295
- Joined: Sat 03 Dec 2005, 11:30
As noted earlier somewhere, I'm one of those who had success with MU's alternative dotpets with an Intel chip (though that was with KDE Desktop Effects, not Compiz, but I presume if the one works the other should?). Incidentally, I complained of slow speeds, but that may be because that was a 512M RAM system. About to to try on one with 3G RAM (I'm in dpup at the moment). But even the "slow" speeds were definitely usable, and worked well.tazoc wrote:I don't know if anyone has been able to use Compiz with an Intel display adapter in LHP. I don't have an Intel box to test with. Some have had success with MU's Alternative Xorg/xserver 1.6.3/Intel pets but I haven't seen anything re: Compiz and those pets. I think you'll need the Mariner SFS for DRI and 3D, but again I don't know if Compiz will work for you. It is a hit-and-miss proposition with Compiz...
-TazOC
The fix was, as said in my post there, being incorporated into LHP by TazOC, and as he has reported above it has been put in now. May want to try with the latest LHP.pemasu wrote:Well, I checked your threads, but there was not ongoing solutions or debate. So for me dead thread Sad
I will just report and I if there is something spesific I will tell....
Thanks for the gender clarification incidentally - and who told nooby that women don't code? I'm a man, but I know plenty of women coders, distro developers etc. They may be less in number than the men, but that's something we men should think about...
-
- Posts: 295
- Joined: Sat 03 Dec 2005, 11:30
That's a good idea, the vmlinuz and initrd.gz are small so I uploaded the new full versions and an xdelta3 update F to Gu1 for the main file, spup-443.sfs. Please check the Readme for instructions.
http://lhpup.org/release/lhp443/inside-iso/443Gu1/
Let me know if you have G but not F and I'll up that one too.
TazOC
http://lhpup.org/release/lhp443/inside-iso/443Gu1/
Let me know if you have G but not F and I'll up that one too.
TazOC
[url=http://www.lhpup.org/][b][size=100]lhpup.org[/size][/b] [img]http://www.lhpup.org/gallery/images/favicon.png[/img][/url] [url=http://www.lhpup.org/release-lhp.htm#602]Lighthouse 64 6.02[/url]
success
TazOC,q5sys wrote:If I get time this coming week, I'll do some testing with compiz on my kit. Im running F so far, if I have no luck I might try an update to G to see if that helps out.tazoc wrote:I don't know if anyone has been able to use Compiz with an Intel display adapter in LHP. I don't have an Intel box to test with. Some have had success with MU's Alternative Xorg/xserver 1.6.3/Intel pets but I haven't seen anything re: Compiz and those pets. I think you'll need the Mariner SFS for DRI and 3D, but again I don't know if Compiz will work for you. It is a hit-and-miss proposition with Compiz...
-TazOC
I was bored so I went ahead and tested G with Compiz on my kit with an Intel card. As I mentioned previous in other posts in this thread I've been using MU's Intel driver Pet.
I went ahead and updated to G before testing, without much trouble (will describe later)... But after it was all said and done, I fired up KDE, and sure enough while the GUI was loading I saw that wonderful compiz fusion splash screen. Tested around with a few of the effects and it works fine. Not perfectly seamless on my system considering the integrated graphics, but it works fine none the less.
Dont know if others will be able to replicate my results as I have installed a slew of other things that might be affecting my ability to run it. But as for now, you have one confirmed case of Compiz running on LHP-G with MU's pet.
If you ever have any other testing you need done on an Intel GPU system, just let me know, I'll be happy to beta test stuff for you.
As for my upgrading troubles, I installed fresh to a USB stick, threw my pupsave on there, and it booted... X started and then X promptly crashed. Then it hit me that my savefile was trying to load the old SFS files that I used to have (the F versions which were not currently on my stick. So I threw them on it, rebooted; and got the little alert about upgrading to the G versions. Copied the G ones over, changed which ones would load at Reboot, and everything worked fine. I figured the system would just fail to load those sfs and them move on, but on my system at least the entire system came to a crashing halt without them.
Hi Q5sys,
Thanks for the testing and good results with MU's Intel pets. I've experienced the same difficulty with missing KDE SFS, though I was still able to switch to JWM by typing 'xwin jwm' at the command line, then use Boot Manager to get the new SFS files mounted.
Have you tried it without the v4l-extension-0.1.1.pet? Once you've determined that maybe you could try them in LHP with a clean pupsave and if it works, I'll try to include them in the next release.
Thanks,
TazOC
Thanks for the testing and good results with MU's Intel pets. I've experienced the same difficulty with missing KDE SFS, though I was still able to switch to JWM by typing 'xwin jwm' at the command line, then use Boot Manager to get the new SFS files mounted.
Hi edoc,edoc wrote:I loaded MPlayer-extra-libs.pet from here:
http://www.murga-linux.com/puppy/viewtopic.php?t=26511
Then I loaded http://minipc.org/ipup/download/MPlayer-1.0rc2.pet
Then I loaded Xorg7.3-v4l-extension-0.1.1.pet from this thread:
http://www.murga-linux.com/puppy/viewto ... 407#271407
Have you tried it without the v4l-extension-0.1.1.pet? Once you've determined that maybe you could try them in LHP with a clean pupsave and if it works, I'll try to include them in the next release.
Thanks,
TazOC
[url=http://www.lhpup.org/][b][size=100]lhpup.org[/size][/b] [img]http://www.lhpup.org/gallery/images/favicon.png[/img][/url] [url=http://www.lhpup.org/release-lhp.htm#602]Lighthouse 64 6.02[/url]
If I understood Tempestuous correctly I need that module:
http://murga-linux.com/puppy/viewtopic.php?t=36066
http://murga-linux.com/puppy/viewtopic.php?t=36066
[b]Thanks! David[/b]
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
tazoc , lighthouse G works well on my set up here.
I did not test with nVidia despite me have that because I fail to do such things.
So I used the normal xorgwizard settings.
Edit Corrections
I have to test more. Since I wrote the original text below I ahve tested with pfix=ram on puppy431std and it behaves as well as Lighthouse on sr.se live music.
And even on firefox with full codex so I have to wait until I find the 31% again to know what caused that different figure. Standard Puppy in my machine draw only 5 to 7 % when listening to radio.
original text below
The best thing about Lighthouse is that it takes less resourses.
The standard puppy431 takes some 28 to 31 % if one use top
if one look at x :0 -br -nolisten tcp so hopefully LH can survive better on computers with only 500;MB?
Just me guessing.
I did not test with nVidia despite me have that because I fail to do such things.
So I used the normal xorgwizard settings.
Edit Corrections
I have to test more. Since I wrote the original text below I ahve tested with pfix=ram on puppy431std and it behaves as well as Lighthouse on sr.se live music.
And even on firefox with full codex so I have to wait until I find the 31% again to know what caused that different figure. Standard Puppy in my machine draw only 5 to 7 % when listening to radio.
original text below
The best thing about Lighthouse is that it takes less resourses.
The standard puppy431 takes some 28 to 31 % if one use top
if one look at x :0 -br -nolisten tcp so hopefully LH can survive better on computers with only 500;MB?
Just me guessing.
Last edited by nooby on Sat 13 Mar 2010, 10:03, edited 1 time in total.
I use Google Search on Puppy Forum
not an ideal solution though
not an ideal solution though
edoc,
TazOC
OK, are you using the v4l or v4l2 driver? Did the v4l2 driver require editing xorg.conf also?After installing this dotpet, it needs to be enabled. Open /etc/X11/xorg.conf in Geany.
In Section "Module" add this lineCode: Select all
Load "v4l"
TazOC
[url=http://www.lhpup.org/][b][size=100]lhpup.org[/size][/b] [img]http://www.lhpup.org/gallery/images/favicon.png[/img][/url] [url=http://www.lhpup.org/release-lhp.htm#602]Lighthouse 64 6.02[/url]
Hi nooby,nooby wrote:tazoc , lighthouse G works well on my set up here.
I did not test with nVidia despite me have that because I fail to do such things.
So I used the normal xorgwizard settings.
The best thing about Lighthouse is that it takes less resourses.
The standard puppy431 takes some 28 to 31 % if one use top
if one look at x :0 -br -nolisten tcp so hopefully LH can survive better on computers with only 500;MB?
Thank you for the good results. Interesting, I will have to do the same comparison with Puppy 4.3.1. I would have thought Puppy would have been a bit lower on X usage. I'm assuming that's LHP 4.43G Base, in JWM you have there (not with Mariner, KDE SFS, etc.?) How much RAM are you testing on? For most accurate comparison I would test with a clean pupsave on each with no extra pets, SFS files, etc.
Lighthouse Base and Mariner should boot and run all WM's except KDE with 256-512M RAM
-TazOC
[url=http://www.lhpup.org/][b][size=100]lhpup.org[/size][/b] [img]http://www.lhpup.org/gallery/images/favicon.png[/img][/url] [url=http://www.lhpup.org/release-lhp.htm#602]Lighthouse 64 6.02[/url]
Hi TazOC,
As usual, you've provided us a fine solid distribution, however, I ran into problems immediately when trying to use Wine. These problems did not exist in the original 443G.
1. Directory .wine includes drive_c directory, however, opening the Program Files and windows directories, both are empty. Installed wine-1.1.40-i486.pet to correct the problem, but it also required OLEAUT32.dll since the one installed was incorrect size and did not work when trying to install setup951.exe for e-Sword.
2. When you correct the problems with wine, please consider these additions which will make e-Sword installation easier. Before installation, two missing files, needed by e-Sword, MFC42.DLL and msls31.dll must be located and copied to /root/.wine "C:\\windows\\system32\", otherwise the installation file will not work properly. Next in order for the graphics to work properly, use Wine configuration (in console winecfg) to set riched20.dll and oleaut32.dll to native. Press the Libraries tab > type riched20.dll > press add > press edit > choose Native (windows). Do the same for oleaut32.dll.
Still testing, next, I'll be checking out KDE4, although I find myself booting more frequently into IceWM.
Thanks again,
Jim
As usual, you've provided us a fine solid distribution, however, I ran into problems immediately when trying to use Wine. These problems did not exist in the original 443G.
1. Directory .wine includes drive_c directory, however, opening the Program Files and windows directories, both are empty. Installed wine-1.1.40-i486.pet to correct the problem, but it also required OLEAUT32.dll since the one installed was incorrect size and did not work when trying to install setup951.exe for e-Sword.
2. When you correct the problems with wine, please consider these additions which will make e-Sword installation easier. Before installation, two missing files, needed by e-Sword, MFC42.DLL and msls31.dll must be located and copied to /root/.wine "C:\\windows\\system32\", otherwise the installation file will not work properly. Next in order for the graphics to work properly, use Wine configuration (in console winecfg) to set riched20.dll and oleaut32.dll to native. Press the Libraries tab > type riched20.dll > press add > press edit > choose Native (windows). Do the same for oleaut32.dll.
Still testing, next, I'll be checking out KDE4, although I find myself booting more frequently into IceWM.
Thanks again,
Jim
- abushcrafter
- Posts: 1418
- Joined: Fri 30 Oct 2009, 16:57
- Location: England
- Contact:
My favorite Desktop Environments /Window Managers are:
- LXDE is a nice package.
- KDE is very nice but it is a resource hog and so I am only going to use it on one or two computers which I still need to setup.
- IceWM is something I am looking into but it looks very promising.
- JWM is not bad but I do miss some features like being able to dock GkrellM to the side of my screen.
- XFCE is also quite/raver good.
Hi Jim,
The directories are empty because they are auto-magically filled as needed by simply running Wine Configuration, any of the links in /root/.wine/drive_c, Wine entries in the Menus, or by clicking on an .exe in ROX. So no need to install another Wine.pet, in fact I recommend against that because there could be conflicts with the Wine in Lighthouse. I've read that when installing a Wine pet it is best to uninstall a previous version.
My understanding is the dlls are governed by a Microsoft EULA and therefore I cannot include them in Lighthouse. They can be downloaded with the Winetricks GUI in LHP or copied from a Windows install. I believe the only ones I'm allowed to include are those 'fake' dlls that are part of Wine. The same applies to Windows fonts.
I also prefer not to change any of the default settings in Wine because what works for one Windows application in Wine may not work for another. I appreciate the idea that there would be fewer steps to install e-Sword but I don't want to create more problems for other users.
If you have dlls that are not governed by a EULA or settings that are recommended for all applications by Winehq.org or that other distros include in Wine I would definitely consider adding them. I wish we could make a PET or SFS for e-Sword with everything set up for the user.
-TazOC
The directories are empty because they are auto-magically filled as needed by simply running Wine Configuration, any of the links in /root/.wine/drive_c, Wine entries in the Menus, or by clicking on an .exe in ROX. So no need to install another Wine.pet, in fact I recommend against that because there could be conflicts with the Wine in Lighthouse. I've read that when installing a Wine pet it is best to uninstall a previous version.
My understanding is the dlls are governed by a Microsoft EULA and therefore I cannot include them in Lighthouse. They can be downloaded with the Winetricks GUI in LHP or copied from a Windows install. I believe the only ones I'm allowed to include are those 'fake' dlls that are part of Wine. The same applies to Windows fonts.
I also prefer not to change any of the default settings in Wine because what works for one Windows application in Wine may not work for another. I appreciate the idea that there would be fewer steps to install e-Sword but I don't want to create more problems for other users.
If you have dlls that are not governed by a EULA or settings that are recommended for all applications by Winehq.org or that other distros include in Wine I would definitely consider adding them. I wish we could make a PET or SFS for e-Sword with everything set up for the user.
-TazOC
[url=http://www.lhpup.org/][b][size=100]lhpup.org[/size][/b] [img]http://www.lhpup.org/gallery/images/favicon.png[/img][/url] [url=http://www.lhpup.org/release-lhp.htm#602]Lighthouse 64 6.02[/url]
What is your favorite desktop / window manager?
Hi abushcrafter,
Thank you for the feedback, you must have seen the new poll question! For the benefit of those who haven't it asks, "What is your favorite desktop / window manager?" and is at the beginning of the first post. I used Xfce 4 for a while when I was working on the new SFS but I'm back in KDE4 so that was my vote... results are not scientific as I imagine one could vote more that once!
[Edit: oh my, it looks like the poll appears on every page. Hmm, I wasn't expecting that.]
TazOC
Thank you for the feedback, you must have seen the new poll question! For the benefit of those who haven't it asks, "What is your favorite desktop / window manager?" and is at the beginning of the first post. I used Xfce 4 for a while when I was working on the new SFS but I'm back in KDE4 so that was my vote... results are not scientific as I imagine one could vote more that once!
[Edit: oh my, it looks like the poll appears on every page. Hmm, I wasn't expecting that.]
TazOC
[url=http://www.lhpup.org/][b][size=100]lhpup.org[/size][/b] [img]http://www.lhpup.org/gallery/images/favicon.png[/img][/url] [url=http://www.lhpup.org/release-lhp.htm#602]Lighthouse 64 6.02[/url]
The reason, I installed the wine .pet is that when I clicked on setup951.exe nothing happened. I also tried one other exe which didn't work so I installed the Wine pet. It still wouldn't work, so I executed in a console and found that it needed the OLEAUT32.dll. So I located it and copied it over the existing file which was newer. The older file did work. I'll try it again, with a fresh install and something other than e-Sword, and let you know. Their may be a problem with latest Wine.tazoc wrote:The directories are empty because they are auto-magically filled as needed by simply running Wine Configuration, any of the links in /root/.wine/drive_c, Wine entries in the Menus, or by clicking on an .exe in ROX.
Thanks,
Jim
Multiple screens with KDE
TazOC,
So I've been playing around in KDE a bit more since I tested Compiz, and I noticed that under settings it has the bit there for display. Now I can run my laptop with an external adapter but its a clone of my screen, there is the option there for extending a single desktop across two screens but I get the message that this module has not been included.
What exactly would need to be included in KDE to allow this ability? When I ran Fedora and Suse, I ran dual screens without a single problem through KDE. So Im assuming it has something to do with how KDE has been rigged to work with Puppy, do you know the details on this? If I could get Puppy to work across my screens... i'd be in heaven.
So I've been playing around in KDE a bit more since I tested Compiz, and I noticed that under settings it has the bit there for display. Now I can run my laptop with an external adapter but its a clone of my screen, there is the option there for extending a single desktop across two screens but I get the message that this module has not been included.
What exactly would need to be included in KDE to allow this ability? When I ran Fedora and Suse, I ran dual screens without a single problem through KDE. So Im assuming it has something to do with how KDE has been rigged to work with Puppy, do you know the details on this? If I could get Puppy to work across my screens... i'd be in heaven.
Tried with a different exe, worked as you described. No problem with Wine. After all .wine files were populated, e-Sword installed without problem using these procedures.Earlier post by Jim wrote:I'll try it again, with a fresh install and something other than e-Sword, and let you know. Their may be a problem with latest Wine.
Thanks,
Jim