Slacko 5.4 - FINAL 2 Dec 2012

News, happenings
Message
Author
User avatar
shinobar
Posts: 2672
Joined: Thu 28 May 2009, 09:26
Location: Japan
Contact:

Re: boot issue

#151 Post by shinobar »

rcrsn51 wrote:If you find vmlinuz and initrd.gz in a subfolder, then expect to find the sfs file there too. If it's not, quit with an error.
In exact, if puppy finds vmlinuz in a subfolder, it sets the subfolder name as the PSUBDIR, then expect to find the sfs file in a subfolder with the same name.

It likely occurs when one has a full install, which has /boot/vmlinuz, and another frugal install at later partitions. Frugal install at earlier partitions than the full have no problem.
Last edited by shinobar on Thu 13 Sep 2012, 02:32, edited 1 time in total.
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#152 Post by rcrsn51 »

This is more common that I realized. Wary 522 does the same thing - looks in subfolders before it looks at the root.

At the moment, Precise is the only one that does it in the "right" order.

User avatar
shinobar
Posts: 2672
Joined: Thu 28 May 2009, 09:26
Location: Japan
Contact:

Re: boot issue

#153 Post by shinobar »

rcrsn51 wrote:At the moment, Precise is the only one that does it in the "right" order.
I think the precise beta has the same initrd dated 2012-03-28 and the same issue as the slacko beta has.
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#154 Post by rcrsn51 »

I checked Precise 5393 again and it does it right. If there is no psubdir argument, it finds the three files at the root and is not confused by other files in subfolders.

User avatar
shinobar
Posts: 2672
Joined: Thu 28 May 2009, 09:26
Location: Japan
Contact:

boot isse of the presice

#155 Post by shinobar »

rcrsn51 wrote:I checked Precise 5393 again and it does it right. If there is no psubdir argument, it finds the three files at the root and is not confused by other files in subfolders.
Confirm the copy of the vmlinuz is the same.

I tested the Precise 5393.
Note that the presice is installed in a subfolder, not at the root in my case.
'pmedia=ataflash' because the sda is a SSD. The uuid is that of sda3.

Code: Select all

title Puppy precise 5.3.93 (sda3/precise)
  uuid d644d8da-1cd0-4976-bbba-91fa6de4c170
  kernel /precise/vmlinuz  pmedia=ataflash psubdir=precise pfix=fsck
  initrd /precise/initrd.gz
I copied sda3/precise/vmlinuz to sda2/Backups/vmlinuz.
Booted off with the above parameter got success.

Next, i removed the 'psubdir' parameter.

Code: Select all

title Puppy precise 5.3.93 (sda3/precise)
  uuid d644d8da-1cd0-4976-bbba-91fa6de4c170
  kernel /precise/vmlinuz  pmedia=ataflash
  initrd /precise/initrd.gz
Booted off and failed... 'puppy_presice_5.3.93.sfs not found.'

In this case, the puppy found the sda2/Backups/vmlinuz and set the PSUBDIR to 'Backups' and failed to find the sda3/presice/puppy_presice_5.3.93.sfs.
The result may be the same if the frugal install was at root.
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#156 Post by rcrsn51 »

At the risk of beating this little exercise to death, I tried "psubdir=/". It worked! It picked the files at the root of the partition before looking in subfolders.

Which makes sense, except that psubdir doesn't usually need a leading slash.

User avatar
ETP
Posts: 1193
Joined: Tue 19 Oct 2010, 19:55
Location: UK

Re: boot issues

#157 Post by ETP »

It is evident that this forum is littered with posts relating to boot issues with typically either:

1. The main SFS or save-file not being found or
2. The incorrect sfs or save-file being loaded.

These issues generally crop up when multiple pups are in use or more advanced boot techniques are being used where the component parts of puppy are being held on different drives, sub-directories and partitions.

I am aware that BK's philosophy, with which I totally agree, is that Puppy should in the main (with the possible exception of pmedia=) be capable of booting without other boot codes & be clever enough to work things out for itself.
In addition new users should not have to concern themselves with complex boot codes.

Currently the additional codes are intended by him to provide hints/help to Puppy when more complex arrangements are deployed.

This is fine for non-advanced use as probably 90% of users will have all the puppy files together in one directory.

The current problem with advanced use seems to be that the boot codes can sometimes conflict with or undermine the search logic that hunts down the location of firstly the save-file(s) and then the main sfs & any additional sfs files that the selected save-file calls for to be loaded. Often removing a boot code can help but more often than not one has to hit on the right combination of codes by a process of trial and error.

A couple of real world working examples:

CASE 1: Kernel on 16 MEG Smartmedia with main sfs & savefile on NTFS HDD (sda1)

Code: Select all

LABEL 5332
MENU LABEL Slacko 5.3.3.2    05/07/12
KERNEL /p5332/vmlinuz
APPEND initrd=/p5332/initrd.gz pmedia=atahd pupsfs=sda1:/p5332/puppy_slacko_5.3.3.2.sfs pdev1=sda1
CASE 2: Kernel on first Fat32 partition of USB2 flash main sfs & save file on 2nd ext4 partition of stick.

Code: Select all

LABEL 5332
MENU LABEL Slacko 5.3.3.2    05/07/12
KERNEL /p5332/vmlinuz
APPEND initrd=/p5332/initrd.gz pmedia=usbflash pupsfs=sdb2:/p5332/puppy_slacko_5.3.3.2.sfs psavemark=2
Both of the above were a nightmare to get right. It is of course a matter for BK, but what I propose is a new boot code (say SEARCH=NO) that would totally override the search logic and codes to allow for the precise location of the following to be specified:

A: The location of vmlinuz & initrd
B: The drive, partition & directory containing the main sfs and any additional sfs files.
C: The drive, partition & directory containing the save-file(s)

This would, I believe, eliminate the uncertainty and knock this thorny issue on the head once and for all.
If UUIDs could also be adopted so much the better.
Regards ETP
[url=http://tinyurl.com/pxzq8o9][img]https://s17.postimg.cc/tl19y14y7/You_Tube_signature80px.png[/img][/url]
[url=http://tinyurl.com/kennels2/]Kennels[/url]

davec51
Posts: 530
Joined: Thu 13 Apr 2006, 22:31
Location: Virginia

"can't find Puppyxxx.sfs file"--Solved

#158 Post by davec51 »

I made a frugal install, put the .sfs file in both the root and subfolder where the other files were (slackobeta). Still, on boot the program can't find the meaty .sfs file.

The psubdir trick did it. I copies the file to the root and then directed the boot to that. I think my post was a bit premature, before I had carefully read the previous posts -- sorry.
Last edited by davec51 on Thu 13 Sep 2012, 19:31, edited 1 time in total.

nooby
Posts: 10369
Joined: Sun 29 Jun 2008, 19:05
Location: SwedenEurope

#159 Post by nooby »

I should have read all pages.

Some of you refer to Precise but the thread is about slacko
so both of them then search same way and thus get confused?

Would be helpful if you guys took it up with Barry then
so we get an official way to solve this once for all.
Just my sloppy suggestion
I use Google Search on Puppy Forum
not an ideal solution though

rodin.s
Posts: 344
Joined: Wed 22 Sep 2010, 19:50
Location: Ukraine

homebank icons, i18n in firewallstate

#160 Post by rodin.s »

Some Homebank icons are missing and I have made i18n-ed firewallstate.

User avatar
01micko
Posts: 8741
Joined: Sat 11 Oct 2008, 13:39
Location: qld
Contact:

#161 Post by 01micko »

**I think** the attached pet should fix homebank, please let me know

EDIT: I checked on a clean install, it does :)
Attachments
homebank-icons-1.fix.pet
(52.87 KiB) Downloaded 331 times
Last edited by 01micko on Fri 14 Sep 2012, 11:44, edited 1 time in total.
Puppy Linux Blog - contact me for access

User avatar
01micko
Posts: 8741
Joined: Sat 11 Oct 2008, 13:39
Location: qld
Contact:

#162 Post by 01micko »

rcrsn51 wrote:At the risk of beating this little exercise to death, I tried "psubdir=/". It worked! It picked the files at the root of the partition before looking in subfolders.

Which makes sense, except that psubdir doesn't usually need a leading slash.
I guess that is like when your current working dir is '/' pwd shows / but if you chnge to /root you typ "cd root".

BTW, here's my menu.lst from Mageia on one of my laptops, uses legacy grub, supports UUID.

Code: Select all

timeout 10
color black/cyan yellow/cyan
gfxmenu (hd0,4)/boot/gfxmenu
default 0

title linux
kernel (hd0,4)/boot/vmlinuz BOOT_IMAGE=linux root=UUID=2f6fb5b4-ce4d-45a4-9439-26af299a0d7f  splash quiet resume=UUID=9d0e347e-ef49-4a84-a88b-c7ba5620ab2e
initrd (hd0,4)/boot/initrd.img

title failsafe
kernel (hd0,4)/boot/vmlinuz BOOT_IMAGE=failsafe root=UUID=2f6fb5b4-ce4d-45a4-9439-26af299a0d7f  failsafe
initrd (hd0,4)/boot/initrd.img

title windows
root (hd0,0)
makeactive
chainloader +1
Puppy Linux Blog - contact me for access

User avatar
shinobar
Posts: 2672
Joined: Thu 28 May 2009, 09:26
Location: Japan
Contact:

legacy grub and UUID

#163 Post by shinobar »

01micko wrote:BTW, here's my menu.lst from Mageia on one of my laptops, uses legacy grub, supports UUID.

title linux
kernel (hd0,4)/boot/vmlinuz BOOT_IMAGE=linux root=UUID=2f6fb5b4-ce4d-45a4-9439-26af299a0d7f splash quiet resume=UUID=9d0e347e-ef49-4a84-a88b-c7ba5620ab2e
initrd (hd0,4)/boot/initrd.img
It does not mean the legacy grub supports UUID, but means the linux supports UUID.
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]

User avatar
01micko
Posts: 8741
Joined: Sat 11 Oct 2008, 13:39
Location: qld
Contact:

#164 Post by 01micko »

Thanks for the info shino

In that menu.lst I added:

Code: Select all

title slacko
rootnotify (hd0,5)
kernel (hd0,5)/vmlinuz
initrd (hd0,5)/initrd.gz
Boot starts up fine but fails when xwin is run. I edited the kernel line at the boot with pfix=ram and it booted fine. I then made a savefile and rebooted, fine again. Must be machine specific. It fails on my desktop, works on my fastest laptop, didn't try any others yet.

Here's contents of /etc/rc.d/PUPSTATE

Code: Select all

# cat /etc/rc.d/PUPSTATE
PUPMODE=12
PDEV1='sda6'
DEV1FS='ext4'
PUPSFS='sda6,ext4,/puppy_slacko_5.3.5.3.sfs'
PUPSAVE='sda6,ext4,/slackosave-zz.4fs'
PMEDIA=''
#ATADRIVES is all internal ide/pata/sata drives, excluding optical, excluding usb...
ATADRIVES='sda '
#ATAOPTICALDRIVES is list of non-usb optical drives...
ATAOPTICALDRIVES='sr0 '
#these directories are unionfs/aufs layers in /initrd...
SAVE_LAYER='/pup_rw'
PUP_LAYER='/pup_ro2'
#The partition that has the slackosave file is mounted here...
PUP_HOME='/mnt/dev_save'
#(in /initrd) ...note, /mnt/home is a link to it.
#this file has extra kernel drivers and firmware...
ZDRV=''
#complete set of modules in the initrd (moved to main f.s.)...
ZDRVINIT='no'
#Partition no. override on boot drive to which session is (or will be) saved...
PSAVEMARK=''
PSUBDIR=''
Attachments
capture16326.png
(30.19 KiB) Downloaded 1023 times
Puppy Linux Blog - contact me for access

User avatar
01micko
Posts: 8741
Joined: Sat 11 Oct 2008, 13:39
Location: qld
Contact:

#165 Post by 01micko »

For anyone who wants to play with filesystems, btrfs is already a module in this Slacko beta.

Code: Select all

# find /lib -name btrfs*
/lib/modules/3.2.28-4g/initrd/kernel/fs/btrfs
/lib/modules/3.2.28-4g/initrd/kernel/fs/btrfs/btrfs.ko
/lib/modules/3.2.28-4g/kernel/fs/btrfs
# modprobe btrfs
More about btrfs <--
https://btrfs.wiki.kernel.org/index.php/Main_Page
http://snarfu.com/slackware/slackware-btrfs-encryption/
https://help.ubuntu.com/community/btrfs
https://wiki.archlinux.org/index.php/Btrfs

Barry is introducing support at the userland level:
http://bkhome.org/blog/?viewDetailed=02992

and in the kernel:

Code: Select all

CONFIG_BTRFS_FS=m
CONFIG_BTRFS_FS_POSIX_ACL=y
NB: all you need is btrfs-progs from the slackware repo and it becomes supported in gparted. (BTW, I just compiled gparted-13.1 thinking that's why it didn't have support :oops: , anyway gparted gets an oops-update 8) )
Puppy Linux Blog - contact me for access

User avatar
James C
Posts: 6618
Joined: Thu 26 Mar 2009, 05:12
Location: Kentucky

#166 Post by James C »

Purely for informational purposes.......

Code: Select all

# glmark.sh
Let the test run or press ESC to abort. 
It will take a couple of minutes
width 400  height 400  depth 24  0
===================================================
    GLMark 08
===================================================
Enter screen width:  Enter screen height: Enter screen bpp:    Enter '1' for fullscreen '0' for windowed: ===================================================
    OpenGL Information
    GL_VENDOR:     Nouveau
    GL_RENDERER:   Mesa DRI nv18 x86/MMX+/3DNow!+/SSE
    GL_VERSION:    1.2 Mesa 8.0.4
===================================================
/usr/sbin/glmark.sh: line 35: 22833 Done                    echo "$W $H $D $param"
     22834 Segmentation fault      | ./glmark
# 

User avatar
01micko
Posts: 8741
Joined: Sat 11 Oct 2008, 13:39
Location: qld
Contact:

#167 Post by 01micko »

Oh well James.. I guess the code base for that app is a bit flakey :lol: . Not much chop as a benchmark!

-----------------------------------

Here's umplayer , patched for Youtube which apparently broke on 14/09/2012 (09/14/2012 US)

http://www.smokey01.com/01micko/pet_pac ... d-i686.pet

REQUIRES qt (see a few pages back)
Puppy Linux Blog - contact me for access

gcmartin

Boot logic issues with multiple bootmanagers in most PUPs

#168 Post by gcmartin »

This post is about Boot logic issues
I would agree with anyone about whether the issue of "standard" boot-logic in Puppy should be aired in this thread....BUT, it is shared here.

One of the problems this thread presents is whether its collaboration will produce results that Barry would entertain.

One result I remember was accomplished by @Shinobar several years ago when he produced his Puppy distro "QuickSET". When this Puppy distro was booted, he introduced
  1. booting directly to desktop,
  2. an Initial user tool for system tailoring, and
  3. a GRUB4DOS boot manager
....all from a simple CD boot.

At the time, there were several evolutionary startup system strategies introduced with his approach. Two of those strategies has tremendous adoption across the spectrum of Puppy distro development as is almost universally used by most of the mainstream developers.

One that remains is a kinda interesting startup feature. Here's why:
  • When one does a BootManager install using all Puppies from the Menu, it installs GRUB4DOS. Also, there is another PUP tool that makes use of GRUB4DOS as well.
GRUB4DOS offers some advantages, but, there is a disconnect between what we get from an initial ISO (syslinux) versus GRUB4DOS used thereafter in the system.

Since these are 2 different products, maybe its time for Barry and the community to consider "Which should be the 2012-2013 Bootmanager?" In other words, would the community benefit from just using one of these, versus,having to understand or have knowledge of 2/both of these 2 different tools and their individual behavior.s.

This would simplify community support to a single approach and provide consistency when reviewing operations and addressing usability and implementation issues. Since GRUB4DOS is proliferated within PUPPY after initial system boot, maybe, the initial system boot as @Shinobar demonstrated couple years ago should be the bootmanager which is not only available after system boot, but, maybe it also should replace the current bootmanager (syslinux) as well.

Then, when bootmanager issues are addressed and help is provided, it will work the same whether booting from ISO or booting after initial Puppy use.

I've always wondered about whether there are inhibitors to adopting a single GRUB4DOS tool's use. It merely appears that this would.could be something which is done at the WOOF level for all Puppy distro development. And, I am not sure if @Shinobar could offer an approach he used with his Quickset distro.

Here to help

futwerk
Posts: 397
Joined: Sat 07 May 2011, 22:04

#169 Post by futwerk »

a few backgrounds.
Attachments
pupse7,3r3.jpg
http://www.mediafire.com/?7v1msw26s6chb
(20.29 KiB) Downloaded 1391 times
pupse7,3r2.jpg
http://www.mediafire.com/?7v1msw26s6chb
(8 KiB) Downloaded 1451 times
pupse7,3r1.jpg
http://www.mediafire.com/?7v1msw26s6chb
(7.65 KiB) Downloaded 1400 times

tlchost
Posts: 2057
Joined: Sun 05 Aug 2007, 23:26
Location: Baltimore, Maryland USA
Contact:

#170 Post by tlchost »

Will there be a PAE version as a final? I'd be happy to test one here...
My system has a 2TB drive and 16 gigs of memory....very few puppies recognize both the drive and all the memory.

I run bootable USB systems

Thom

Post Reply