Page 3 of 12

Re: personal save file resize issue

Posted: Sun 06 Mar 2011, 23:16
by Q5sys
bwh1969 wrote:I am not sure if this is an issue particular to me or if anyone else sees this.

I went to increase my save file size, and it did increase the actual file size but not the filesystem on the save file. I fixed this running e2fsck then resize2fs on the save file and the save file indicator is showing the appropriate information (as is the command df -h)

Other than that, I am extremely impressed with this!

I made a post about that bug in this thread. You might want to add your info as well, as well as how you managed to fix it.

Posted: Mon 07 Mar 2011, 08:49
by Sylvander
@Q5sys

1. "You will see a listing of programs....Thats whats in the Mariner SFS."
OK, thanks, I think I get it.
I know some of those at least.

2. "As to what is an SFS, which Im assuming is your next question"
I think I have some level of understanding of what is an SFS file.

@tazoc

3. "I'm afraid it requires re-mastering the ISO"
I might have a go at that. :)

4. "I would stop smm, then close Sakura"
Duh, I guess that's what I should do.
Did I fail to think of that? :?

5. "Here is a diagram by Barry Kauler that helped me to visualize the Puppy Architecture"
I've read all of that stuff at various times.
Problem is, I tend to quickly skim.
In my older years I no longer focus intensely to absorb the tiniest detail.

savefile pt II

Posted: Mon 07 Mar 2011, 11:32
by bwh1969
Another way to increase the savefile size:

Alternatively in another linux distro, you could run

Code: Select all

e2fsck /path/to/savefile
dd if=/dev/zero bs=1M count=(additional_size-in_MB) >> /path/to/savefile

Code: Select all

resize2fs /path/to/savefile

Code: Select all

e2fsck /path/to/savefile
@ QSsys: I added to the post you referenced in case someone finds it. I also added the note about the boot flag pfix=fsck

digikam

Posted: Tue 08 Mar 2011, 23:28
by bwh1969
I use and love digikam/showphoto

I attempted to build this from source BUT it wanst automoc4 for kde... which I do not know how to get on my system.

http://www.digikam.org/drupal/download? ... ad/tarball

Re: realtek 8192se_pci, digiKam

Posted: Wed 09 Mar 2011, 03:03
by tazoc
bwh1969 wrote:driver for realtek 8192se_pci wireless driver

This card is in a lot of new netbooks. It complied fine. I'd make a pet out of it but I am unsure how to go about that.
Hi bwh1969 and thank you for compiling this driver. To make a Pet, extract or create the folder tree to be installed inside a new folder named <pet_name>-<version>, in this case maybe r8192se_pci-k2.6.33.2, with the directory tree

Code: Select all

lib/modules/2.6.33.2/kernel/drivers/net/wireless
inside. Then open a terminal in the folder that contains the new folder and type

Code: Select all

dir2pet r8192se_pci-k2.6.33.2
The prompts will guide you from there. You can make changes as needed inside the directory structure and repeat the dir2pet step. It will overwrite the old Pet when building the new version. dir2pet will create a pet.specs file just inside the new folder which is used by PPM. Along with the pet.specs file you can place the scripts pinstall.sh and puninstall.sh, to be run post install and post uninstall, respectively. Those scripts are optional.

I would also like to build this Pet for LHP Update, but I would like to know what steps were needed to use it. Although I don't have the WiFi card for this driver, I extracted it to /, then in a terminal

Code: Select all

bash-4.1# depmod-FULL -a
<root> ~
bash-4.1# modinfo r8192se_pci
filename:       /lib/modules/2.6.33.2/kernel/drivers/net/wireless/r8192se_pci.ko
license:        GPL
version:        0019.1207.2010
author:         Copyright(c) 2008 - 2010 Realsil Semiconductor Corporation <wlanfae@realtek.com>
description:    Linux driver for Realtek RTL819x WiFi cards
srcversion:     B35243106478C16B758F56E
alias:          pci:v000010ECd00008174sv*sd*bc*sc*i*
alias:          pci:v000010ECd00008173sv*sd*bc*sc*i*
alias:          pci:v000010ECd00008172sv*sd*bc*sc*i*
alias:          pci:v000010ECd00008171sv*sd*bc*sc*i*
alias:          pci:v000010ECd00008192sv*sd*bc*sc*i*
depends:        
vermagic:       2.6.33.2 SMP mod_unload modversions 486 
parm:           ifname: Net interface name, wlan%d=default (charp)
parm:           hwwep: Try to use hardware WEP support(default use hw. set 0 to use software security) (int)
parm:           channels: Channel bitmask for specific locales. NYI (int)
(The modinfo probably isn't necessary, just for my curiosity.) Then I used | Menu | System | BootManager | Click here to add a new module, added r8192se_pci and was instructed to reboot. Any shortcuts or is that how you used it?

Re: digiKam, I have not compiled any KDE apps successfully. digikam-2.0.0-beta3 has many dependencies, and requires both development and binary packages installed:
Name Version URL Remarks

CMake >= 2.8.x (LHP has this in Devx-LHP_503.sfs) http://www.cmake.org
libqt >= 4.6.x http://www.qtsoftware.com Including run-time SQLite3 and Mysql database plugin.
kdelibs >= 4.4.x http://www.kde.org Nepomuk support introduced with KDE 4.3.x.
libkipi >= 1.2.0 http://www.digikam.org/sharedlibs Version from trunk KDE svn repository.
libkexiv2 >= 1.2.0 http://www.digikam.org/sharedlibs Version from trunk KDE svn repository. Exiv2 >= 0.20.0 shared library recommended.
libkdcraw >= 1.2.0 http://www.digikam.org/sharedlibs Version from trunk KDE svn repository.
libkface >= 0.1.0 http://www.digikam.org/sharedlibs Version from trunk KDE svn repository.
libkmap >= 0.1.0 http://www.digikam.org/sharedlibs Version from trunk KDE svn repository.
liblcms >= 1.17.x http://www.littlecms.com liblcms >= 2.x not yet compatible.
libtiff >= 3.8.2 http://www.remotesensing.org/libtiff
libpng >= 1.2.x http://www.libpng.org/pub/png/libpng.html
libjpeg >= 6b http://www.ijg.org
libjasper >= 1.7.x http://www.ece.uvic.ca/~mdadams/jasper
LHP doesn't have some of these development packages and I couldn't find kdelibs5-dev_4.4.4. Rather than compiling, I think your best bet is binaries from either digikam - 2:1.4.0-0ubuntu1~lucid1~ppa1 or digikam-1.2.0-i486-1sl. I built an SFS of the latter, but haven't tested it yet. Requires Mariner and KDE SFS, maybe more. DigiKam-1.2.0-i486-L1.sfs
Regards,
TazOC

digikam -showfoto sfs works

Posted: Wed 09 Mar 2011, 21:10
by bwh1969
1. The digikam / Showfoto sfs works for the most part although for some reason digikam will not show image files in collection (known bug in several versions if it is searched for) , but showfoto will. Honestly I use showphoto more so it was still helpful.

I tired to do various tweaks with related lib files for the digikam issue and they seemed to revolve around kioslave issues.

2. As far as wireless-->


I did this:

extracted tar

Code: Select all

make

make install
so all of that was taken care of so I would think that

1. install pet
2. depmod-FULL -a
3. Bootmanager add module
4. reboot

I have attempted to bring up wlan0 before a reboot, but frisbee has issues loading it in to wireless (shows extension, but will not show essids). Rebooting fixes this.

Also, Frisbee works with this in getting an ip. The other net tools seem unable to do this.

Touch Pad problems

Posted: Thu 10 Mar 2011, 05:50
by nickdobrinich
Somewhere between 5.02 and 5.03, I lost my touchpad control and tapping on several Dell laptops with both Synaptics and Alps touch pads.
The fix is simple but you may need to hook up a USB mouse to do it.

Go to PupControl | Hardware | Touchpad to run flSynclient
Make sure Touchpad Mode is ON
Check Palm Detect.
You might want to adjust Touch Sensitivity > 14.
Then go to the Tapping tab.
Set One Finger to left button
Adjust Tap Time to 225
Adjust Double Tap Time to 100.
Go back to the General Tab and click Save.
Your settings will probably be different but can be fine tuned from these values.

Also, on 2 machines, if I clicked on Calibrate on the General tab, I was dumped to the black screen command prompt.
Just type xwin and try again without using Calibrate.
Things seemed to self calibrate once I got the touchpad working.

feedback

Posted: Thu 10 Mar 2011, 09:32
by Barburo
Hi TazOC,
I've got a couple of quirks with 503:

I tried the Frisbee for connecting to my wireless but I want to go back to using your "WirelessConnect" (it's faster). So I enabled it in Startup and KDE Autostart.
But now they both seem to be active. How do I stop Frisbee?

I only want to mount a couple of the partitions on my drive so I enabled Startmount.
Now every boot brings up this window. How can I stop it displaying each boot?

Boot

Posted: Sat 12 Mar 2011, 06:04
by helio58
Hi , thanks for this release.
I m new to linux.
I will like to boot my computer direct to LHP without cd or usbpendrive.
Is this possible and if yes what to do.
I have try to install grub but I got a error no linux on sda1

Regards
Helio

Posted: Sat 12 Mar 2011, 06:15
by puppyluvr
:D Hello
@helio58,
Menu / Setup / Puppy Universal Installer....

@Tazoc..
Still testing, but BRILLIANT as usual...
High expectations, and I`m sure, amazing results...
SFS`s at boot... 8)

The main Puppy lineage would do well to emulate some of your work...Just my opinion..... :roll:

Posted: Sat 12 Mar 2011, 06:40
by helio58
Hi puppyluvr,
have try that but get grub dont find linux on sda1

helio

Posted: Sat 12 Mar 2011, 07:06
by puppyluvr
:D Hello,
Post your /mnt/home/boot/grub/menu.lst file here...

Posted: Sat 12 Mar 2011, 11:07
by punkman
Dear all, a noob here. I used the Mariner iso and installed to usbdrive in the usbhdd mode. The sfs'es load automatically in the startup. But the included pet files in the pet files don't load automatically.Is it the expected behaviour?

Posted: Sat 12 Mar 2011, 14:30
by Q5sys
punkman wrote:Dear all, a noob here. I used the Mariner iso and installed to usbdrive in the usbhdd mode. The sfs'es load automatically in the startup. But the included pet files in the pet files don't load automatically.Is it the expected behaviour?
PET files are different than SFS Files. PET files are similar to Program Installation files in windows. In order for them to load, you have to double click them. Then that will install the program and it will be available from that point on.

Re: digikam -showfoto sfs works

Posted: Sat 12 Mar 2011, 21:14
by tazoc
bwh1969 wrote:1. The digikam / Showfoto sfs works for the most part although for some reason digikam will not show image files in collection (known bug in several versions if it is searched for) , but showfoto will. Honestly I use showphoto more so it was still helpful
Yes, I've fixed the digiKam bugs with an updated libgomp which is in the the LHP_5.03G-update-1.pet (see next post.) and an updated SFS: http://lhpup.org/sfs/503/DigiKam-1.2.0-i486-L2.sfs. It requires the update-1 Pet, Mariner SFS and KDE SFS.
2. As far as wireless-->
I did this:

extracted tar

Code: Select all

make
make install
so all of that was taken care of so I would think that

1. install pet [r8192se_pci-k2.6.33.2.pet]
2. depmod-FULL -a
3. Bootmanager add module
4. reboot

I have attempted to bring up wlan0 before a reboot, but frisbee has issues loading it in to wireless (shows extension, but will not show essids). Rebooting fixes this.

Also, Frisbee works with this in getting an ip. The other net tools seem unable to do this.
That's great news and helpful feedback, thank you!
Barburo wrote:I tried the Frisbee for connecting to my wireless but I want to go back to using your "WirelessConnect" (it's faster). So I enabled it in Startup and KDE Autostart.
But now they both seem to be active. How do I stop Frisbee?
Hi Barburo,
OK, I've updated ConnectWireless for Frisbee and other recent network updates, and included it in the 5.03 update-1 Pet, (see next post.) It will start during boot up instead of Frisbee, if ConnectWireless is added to /etc/rc.d/rc.local and the WEP parameters are pasted into the script, as described in the comments at the beginnning of /usr/local/bin/ConnectWireless. It is a bit faster than Frisbee, but ConnectWireless is only for a WEP WiFi connection, (so far doesn't work with WPA2) it cannot roam between profiles and is less reliable than Frisbee because it does not automatically reconnect--if the carrier is lost, after the initial connection succeeds. If you are only using one strong and reliable WEP connection, then ConnectWireless might be useful.
I only want to mount a couple of the partitions on my drive so I enabled Startmount.
Now every boot brings up this window. How can I stop it displaying each boot?
Open start-mount.sh in /Startup (/Autostart for KDE) with a text editor and comment out the last line like this

Code: Select all

#gtkdialog3 -p SPLASH ; unset SPLASH;exit 
@punkman,
Hello and welcome to the forum! Yes, the Pets in the Mariner ISO /pets folder are not installed automatically. Just click on the CD/DVD drive desktop icon, (usually sr0) or, if the CD isn't handy, click on the Mariner ISO file in ROX-Filer to mount it. Then click on the pets folder and left click on a Pet to install it.
-TazOC

LHP_5.03G-update-1.pet

Posted: Sat 12 Mar 2011, 21:15
by tazoc
Attached below is Update-1 for Lighthouse 5.03.
It contains the following bug fixes:

cupsview (CUPS printing web interface)

BootManager: Manage system services

BootManager: SFS Boot Settings

frugal-symlink (Move and Link Programs)

GCC OpenMP (GOMP) support library (for digiKam)

ConnectWireless (alternative to Frisbee for WEP connections)

ROX context menus for various text file types

CdKase themes (KDE desktop applet)

stripul and stripub (for developers, see /usr/local/LHPdev after installing)

This Pet updates the script ConnectWireless, but Frisbee still connects by default unless you have added ConnectWireless to /etc/rc.d/rc.local. (See previous post.)

I've also compiled GKrellM 2.3.5 in LHP and patched GKrellKam 2.0.0 to improve the image watcher / web cam plug in. This Pet should work with any Lighthouse. For a nice working Lighthouse web cam, add the new default,

Code: Select all

http://live.novascotiawebcams.com/peggyscove/current.jpg
to the image source box in the GKrellKam plug in panel configuration dialog. The old one in Mariner, Cape Hatteras, http://pinpoint.ecu.edu/cameras/hatcam.jpg is down and this Pet may replace it with Peggy's Cove Lighthouse.

A source package for both is attached as well, in case you wish to compile them yourself.
-TazOC

How to auto connect to internet

Posted: Sun 13 Mar 2011, 06:52
by fxjudy
I installed lighthouse, want to auto connect to Internet with frisbee,but always fail ,I use ADSL connection,anyone knows?thank you!

Posted: Sun 13 Mar 2011, 13:37
by punkman
Thanks for answering guys. Another question- How do I change which sfs files to load automatically? The flash sfs is not loaded by default, but I feel it would be very easy if it was loaded by default. So I have kept it in my pendrive . But at every live boot it asks for configuration if I want to load it. How is it possible to add it to automatic options?

Internet connection via Puppy Network Interface

Posted: Sun 13 Mar 2011, 14:05
by nickdobrinich
@fxjudy:
Hi and welcome to Lighthouse Puppy world.
I usually connect via Network or Wireless LAN (Puppy) the first time I am trying a new or unknown connection.
It is the smaller button right below the large Frisbee button on the Internet Connection Wizard screen reached through the Connect icon.

Are you connecting via wire or wirelessly?
Do you have a router, either separate or part of your ADSL modem?
Is it supplying DHCP addresses?
If fixed addressing, the address range will have been given to you by your provider.
It should also have DNS servers listed.
If not, try 8.8.8.8 which is Google's DNS server.

Failing that, I have had luck watching the pop up messages to see what connections the wizard is trying to connect to.
Then I try the Static IP option like this (these are dummy addresses):
IP address: 69.123.45.140
Subnet: 255.255.255.248
Gateway: 69.123.45.140 (same as the IP address)

After the initial connection is made, Frisbee seems to work well.
Good luck.

Latest LightHouse LiveDVD with SFS processing

Posted: Sun 13 Mar 2011, 16:57
by gcmartin
@TazOC
You opened a dialogue with me last summer, I believe, as you helped me in understanding a little about the LIveDVD boot process.

Since then, I have witnessed you structure the LiveDVD boot process in such a way as it far exceeds the older way of Puppy LiveDVD processing.

In my review, please confirm if my look at this process is accurate and meets your approval of my description.

It appears, to me, that you took a step back, reviewed the Puppy boot process, and built a smooth operational approach to LIghtHouse's LiveCD which addresses
  1. Initial boot supporting Mariner
  2. consistent operations after initial boot setup
LiveCD Initial Boot
You have incorporated a new feature allowing any SFS that is contained on the LiveCD to be a part of the booting system such that when the user arrives at desktop, the RAM based system has all of the additional applications to round out his system and the user's needs.

Consistent LiveDVD operations.
Once booted, configured, tailored, and tested, when the user reboots/poweroff, the session save function has been expanded in such a way that all of the additions are enclosed within save-session where on LiveDVD reboot, all elements present before shutdown come back to life in the running desktop system without the user needing to do anything.

If this is accurate, this is a marked advancement in your implementation compared to other PUPs in the arsenal. Reason2: (last point first) In the past for many PUPs, I have witnessed that if the users tailors his system with "too much", the save-session step will not work properly or on reboot, the processing of the LiveDVD's save-session will abort or panic. Reason1: No other PUP has made it as obvious and as simple to understand what one is doing at LightHouse startup.

This is a significant advancement in LiveDVD processing in the Puppy world. Further, if this is true, you MAY want to open a forum thread that, just, discusses the particulars of this accomplishment for it has far reaching implications to both developers and users in this community.

Hope I described this accurately.

Thanks again for your work.