Lighthouse Pup 4.4.2 Final SMP 194M
pfix=fsck in Lighthouse Pup
Hi Jim,
Back in February I was editing the init script and noticed that Puppy mounts all partitions looking for Puppy files, unless the pdev1= parameter is used to specify which partition has the puppy files. Along the same philosophy of other distros I thought it was wise to run e2fsck on those Linux partitions prior to mounting, but only if 'pfix=fsck' was specified.
However I tested today without the pdev1= parameter and my machine takes nearly 30 secs longer to boot with 4 Linux partitions when using pfix=fsck. (Or much longer if the drives have been mounted a certain number of times without being checked.) So maybe I should remove the extra checks for the next release.
In the meantime insert ' pdev1=sda8 ' in your menu.lst, on the same line and before your 'pfix=fsck', replacing 'sda8' with the partition that has your pup_save. That will eliminate the extra file system checks (and extra mounts,) decreasing boot time.
-TazOC
Back in February I was editing the init script and noticed that Puppy mounts all partitions looking for Puppy files, unless the pdev1= parameter is used to specify which partition has the puppy files. Along the same philosophy of other distros I thought it was wise to run e2fsck on those Linux partitions prior to mounting, but only if 'pfix=fsck' was specified.
However I tested today without the pdev1= parameter and my machine takes nearly 30 secs longer to boot with 4 Linux partitions when using pfix=fsck. (Or much longer if the drives have been mounted a certain number of times without being checked.) So maybe I should remove the extra checks for the next release.
In the meantime insert ' pdev1=sda8 ' in your menu.lst, on the same line and before your 'pfix=fsck', replacing 'sda8' with the partition that has your pup_save. That will eliminate the extra file system checks (and extra mounts,) decreasing boot time.
-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,
In my case, I never checked my partitions, so it took a long time to check all my partitions which was a good thing since they needed a check. Other distributions such as ubuntu do a check after so many boots, don't know why puppy doesn't.
What prompted me to do this was that I had done a check on several pup_save.2fs files using code "es2fsck -f" and had discovered numerous errors. Incidently, the LH pup_save.2fs has the least errors, possibly due to your file cleanup on shutdown.
I've also been converting some pup_save.2fs files to pup_save.3fs files since my partitions are ext3 to see if that reduces the errors. Possibly, you could consider switching back to using pup_save.3fs files since your distribution continues to be on the leading edge. I find it too easy to trash pup_save.2fs files and I know that they aren't any faster, if as fast as 3fs. 2fs files, based on my limited experience, do crash more often than 3fs.
Thanks,
Jim
I suspected that this was the case since other pups don't run these checks. This philosophy is good, I hope that you keep it this way. It gives a choice for an important check. Just mention it in your release notes.Along the same philosophy of other distros I thought it was wise to run e2fsck on those Linux partitions prior to mounting, but only if 'pfix=fsck' was specified.
In my case, I never checked my partitions, so it took a long time to check all my partitions which was a good thing since they needed a check. Other distributions such as ubuntu do a check after so many boots, don't know why puppy doesn't.
What prompted me to do this was that I had done a check on several pup_save.2fs files using code "es2fsck -f" and had discovered numerous errors. Incidently, the LH pup_save.2fs has the least errors, possibly due to your file cleanup on shutdown.
I've also been converting some pup_save.2fs files to pup_save.3fs files since my partitions are ext3 to see if that reduces the errors. Possibly, you could consider switching back to using pup_save.3fs files since your distribution continues to be on the leading edge. I find it too easy to trash pup_save.2fs files and I know that they aren't any faster, if as fast as 3fs. 2fs files, based on my limited experience, do crash more often than 3fs.
Thanks,
Jim
Hi TazOC,
Thanks,
Jim
I tried this but it didn't work, also tried "pdev1=/dev/sdb7" which also failed. No problem though, I like this check so much that I am going to set up a separate psubdir with LH booting just for the purpose of checking my partitions periodically.In the meantime insert ' pdev1=sda8 ' in your menu.lst, on the same line and before your 'pfix=fsck', replacing 'sda8' with the partition that has your pup_save. That will eliminate the extra file system checks (and extra mounts,) decreasing boot time.
Thanks,
Jim
Have you tried 'pdev1=sdb7'? (with no /, and one space separating parameters.) Here's my relevant grub line:Jim1911 wrote:I tried this but it didn't work, also tried "pdev1=/dev/sdb7" which also failed.
Code: Select all
kernel /lhp442/vmlinuz pmedia=atahd pdev1=sda8 pfix=fsck psubdir=lhp442
-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]
Yes, I used "pdev=sdb7" with appropriate spaces, my relevant line is now
which was my last try. DUMB, I know to doublecheck code, left off "1".
Jim
Code: Select all
kernel /Test/vmlinuz pdev=/dev/sdb7 pfix=fsck pmedia=idehd psubdir=Test
Jim
pup_442.sfs not found?
Just downloaded newest Lighthouse and can't get it to boot?
on usb, fat32 or ext2
4.4.2.c iso
http://www.lhpup.org/download.htm
I tried variuos methods to boot
no luck?
help!
on usb, fat32 or ext2
4.4.2.c iso
http://www.lhpup.org/download.htm
I tried variuos methods to boot
no luck?
help!
linus1972,
Thank you for trying Lighthouse Pup. Be sure you've checked the md5sums by clicking on 'click-to-verify-LHP' in Linux. And try booting from CD if possible. Or try official Puppy on a flash drive.
Some machines have a BIOS that makes booting from USB very hard. There was another on this thread who was unable to boot from USB flash drive. We couldn't sort it out. I have tested LHP with Puppy Universal Installer to a flash drive and it's slow but otherwise ok.
-TazOC
Thank you for trying Lighthouse Pup. Be sure you've checked the md5sums by clicking on 'click-to-verify-LHP' in Linux. And try booting from CD if possible. Or try official Puppy on a flash drive.
Some machines have a BIOS that makes booting from USB very hard. There was another on this thread who was unable to boot from USB flash drive. We couldn't sort it out. I have tested LHP with Puppy Universal Installer to a flash drive and it's slow but otherwise ok.
-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]
Hello tazok
not being snippish, but I have many pc's and many many distro's runinng on pc's that won't evevn boot from usb
I am almost an expert at bootloaders, etc
I haven't had this issue with any other puppy?
For reference I am booting about 10 distrop's off my fat32 usb now
including 3 puppys, pmagic, sidux, tinycore, clonezilla, ubuntu and more:)
I was wondering, if when you remastered, that the .sfs name was changed or ?
here is my site for reference
note I am multidistro
http://multidistro.com/
I will check md5sum and try again to download
also, the previous lighthouse pup I got the other day, the one I'm hosting at my site
does not have this issue either??
not being snippish, but I have many pc's and many many distro's runinng on pc's that won't evevn boot from usb
I am almost an expert at bootloaders, etc
I haven't had this issue with any other puppy?
For reference I am booting about 10 distrop's off my fat32 usb now
including 3 puppys, pmagic, sidux, tinycore, clonezilla, ubuntu and more:)
I was wondering, if when you remastered, that the .sfs name was changed or ?
here is my site for reference
note I am multidistro
http://multidistro.com/
I will check md5sum and try again to download
also, the previous lighthouse pup I got the other day, the one I'm hosting at my site
does not have this issue either??
linus1972,
I tried booting off USB Flash drive formatted Fat32 and also got "pup_442.sfs not found". Same when I renamed 'pup_442c_lighthouse.sfs to pup_442.sfs.
'/tmp/bootinit.log' said mounting /dev/sdb1 failed. Am trying to figure out why it couldn't mount the vfat partition.
vg1, yes this seems to be a bug affecting vfat. I studied the init script and can't find the reason.
-TazOC
I tried booting off USB Flash drive formatted Fat32 and also got "pup_442.sfs not found". Same when I renamed 'pup_442c_lighthouse.sfs to pup_442.sfs.
'/tmp/bootinit.log' said mounting /dev/sdb1 failed. Am trying to figure out why it couldn't mount the vfat partition.
vg1, yes this seems to be a bug affecting vfat. I studied the init script and can't find the reason.
-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]
Thanks vg1
it does work great off ext3 hd!
I simply extracted iso to folder
renamed that folder "LPup"
placed lpup folder in root of my Ubuntu drive
edited my menu.lst
like so
and it works!
it does work great off ext3 hd!
I simply extracted iso to folder
renamed that folder "LPup"
placed lpup folder in root of my Ubuntu drive
edited my menu.lst
like so
Code: Select all
title LighthousePup
root (hd0,5)
kernel /LPup/vmlinuz acpi=force root=/dev/ram0 pmedia=atahd initrd=/LPup/initrd.gz psubdir=LPup max_loop=40
initrd /LPup/initrd.gz
linus1972,
Glad it works. Although, I thought that psubdir code needed to be on the kernal line as is in my menu.lst. I learn something every day. Also, why is the extra initrd line needed? Is it because of the unneeded code "initrd=/LPup/initrd.gz? It probably should be: "initrd /LPup/initrd.gz psubdir=LPup max_loop=40" and delete the next line.
Jim
Glad it works. Although, I thought that psubdir code needed to be on the kernal line as is in my menu.lst. I learn something every day. Also, why is the extra initrd line needed? Is it because of the unneeded code "initrd=/LPup/initrd.gz? It probably should be: "initrd /LPup/initrd.gz psubdir=LPup max_loop=40" and delete the next line.
Code: Select all
# Linux bootable partition config begins
title Lighthouse (on /dev/sdb6)
root (hd1,5)
kernel /Lighthouse/vmlinuz pmedia=idehd psubdir=Lighthouse
initrd /Lighthouse/initrd.gz
# Linux bootable partition config ends
-
- Posts: 67
- Joined: Thu 21 May 2009, 16:13
I tried booting off USB Flash drive formatted Fat32 and also got "pup_442.sfs not found"
Same over here.
Could that please be fixed or told what boot parameters
I could put into syslinux.cfg
so that it will find the *.sfs file on my USB stick ?
Many thanks.
[url=http://www.overunity.com]overunity.com open source free energy research forum[/url]
[url=http://www.overunity.de]overunity.de Deutsches free energy research forum[/url]
[url=http://www.overunity.de]overunity.de Deutsches free energy research forum[/url]
-
- Posts: 67
- Joined: Thu 21 May 2009, 16:13
Could it run from an USB stick
formated to Ext2 or Ext3 file system ?
How would I boot from this one ?
I really need to test , if this system will support
the WIFI WPA2 encryption with my RTL8180 based
PCMCIA WLAN card.
Many thanks in advance.
formated to Ext2 or Ext3 file system ?
How would I boot from this one ?
I really need to test , if this system will support
the WIFI WPA2 encryption with my RTL8180 based
PCMCIA WLAN card.
Many thanks in advance.
[url=http://www.overunity.com]overunity.com open source free energy research forum[/url]
[url=http://www.overunity.de]overunity.de Deutsches free energy research forum[/url]
[url=http://www.overunity.de]overunity.de Deutsches free energy research forum[/url]
Fix for LHP not booting from Fat32
linus1972,
I got mine to boot off a Fat32 Flash drive by inserting these two lines at ~line 288 of init script:Updated initrd.gz is attached.
[Update: works for Fat32 hard drive also. This will be in the next release.]
[Update 2: Included updated versions for LHP412f and LHP442c; be sure to d/l the correct file for your version of Lighthouse Pup.]
TazOC
I got mine to boot off a Fat32 Flash drive by inserting these two lines at ~line 288 of init script:
Code: Select all
modprobe nls_cp850 # TazOC need for vfat k2.6.28.5
modprobe nls_utf8 # TazOC need for vfat k2.6.28.5
[Update: works for Fat32 hard drive also. This will be in the next release.]
[Update 2: Included updated versions for LHP412f and LHP442c; be sure to d/l the correct file for your version of Lighthouse Pup.]
TazOC
Last edited by tazoc on Wed 12 Aug 2009, 17:14, edited 5 times in total.
[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]
hartiberlin,
Should work on ext3 formatted USB Flash drive without the new initrd.gz in previous post. Just run the Puppy Universal Installer.
I don't know whether your WiFi will work. Maybe you could boot off a Lighthouse Pup CD first to test with your hardware.
-TazOC
Should work on ext3 formatted USB Flash drive without the new initrd.gz in previous post. Just run the Puppy Universal Installer.
I don't know whether your WiFi will work. Maybe you could boot off a Lighthouse Pup CD first to test with your hardware.
-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: 67
- Joined: Thu 21 May 2009, 16:13
Tazoc,
many thanks for fixing it this fast.
Now with the new initrd.gz
it works great from the Fat32 formatted USB stick.
I am just using this now to post this over here.
Youtube fullscreen and HD also works due toflash 10.
Very good.
Why dont you include Firefox 3.5.1instead of the old Seamonkey 1.1.7 ?
I heard also Seamonkey 2.x is already out, so why use an outdated browser ?
Well, unfortuately the Realtek RTL 8110 Lighthouse recognizes
for my PCMCIA WLAN card does not work with WPA2..
It finds the router and I can add my key, but then the WPA2
connection fails... Damn... Scanning...ascociate....failed...
Hmm, too bad...
I am really looking for a no fiddle pupplet distribution, that
works with my Realtek WLan card with WPA2.
Is there any out that works out of the box ?
ALready tried to patch browserlinux.com pupplet to
patch for 15 hours the last days and did not get the WPA2 to work...
Damn..
Will now try Fatdog2 beta..
many thanks for fixing it this fast.
Now with the new initrd.gz
it works great from the Fat32 formatted USB stick.
I am just using this now to post this over here.
Youtube fullscreen and HD also works due toflash 10.
Very good.
Why dont you include Firefox 3.5.1instead of the old Seamonkey 1.1.7 ?
I heard also Seamonkey 2.x is already out, so why use an outdated browser ?
Well, unfortuately the Realtek RTL 8110 Lighthouse recognizes
for my PCMCIA WLAN card does not work with WPA2..
It finds the router and I can add my key, but then the WPA2
connection fails... Damn... Scanning...ascociate....failed...
Hmm, too bad...
I am really looking for a no fiddle pupplet distribution, that
works with my Realtek WLan card with WPA2.
Is there any out that works out of the box ?
ALready tried to patch browserlinux.com pupplet to
patch for 15 hours the last days and did not get the WPA2 to work...
Damn..
Will now try Fatdog2 beta..
[url=http://www.overunity.com]overunity.com open source free energy research forum[/url]
[url=http://www.overunity.de]overunity.de Deutsches free energy research forum[/url]
[url=http://www.overunity.de]overunity.de Deutsches free energy research forum[/url]