Slacko 533 works correctly, as does the latest Precise.
Slacko 5.4 - FINAL 2 Dec 2012
What version of grub4dos config is Precise using? (haven't time to boot into it ATM)
Puppy Linux Blog - contact me for access
I'm booting with legacy GRUB. I don't think that this is a GRUB issue. The vmlinuz and initrd.gz files are found OK by GRUB.01micko wrote:What version of grub4dos config is Precise using? (haven't time to boot into it ATM)
It feels more like a bug in the search logic of the init. Or one of those weird timing issues.
booting issue
@rcrsn51, 01micko
I cannot reproduce your issue. Relating hardware?
I am now posting from this boot.
I cannot reproduce your issue. Relating hardware?
Code: Select all
title Puppy slacko 5.3.5.3 (sdc2)
uuid df28a7f3-8257-42f2-b555-864fe0a6a64b
kernel /vmlinuz pmedia=atahd pfix=fsck
initrd /initrd.gz
Last edited by shinobar on Thu 13 Sep 2012, 01:16, edited 2 times in total.
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]
finding sfs
I remember old persisting bug in finding the main sfs.rcrsn51 wrote:At what stage would this bug have sneaked in?
It may occur when you have multiple puppy_slacko_5.3.5.3.sfs in your PC...
the release note of the Puppy 431JP (2009) says:
I do not surely remember, but we found some bug in the original and we modified the initrd to fix it.Differences from original version
2. Some reading rules of the main SFS file and additional SFS file are different from the original 4.3.1.
- When two or more main SFS files exist in PC, and which SFS file might likely to be adopted, it to be different in a Japanese version and an original version.
The logic in the recent woof is not the same of that time, but can remain some faults yet.
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]
5.3.5.3
UMplayer:
I found that a previous umplayer works properly (except for no menu entry) in 5.3.5.3
avplayersj2-slacko-i686.sfs
Everything works in this player but... you have to go to usr/local/bin/umplayer and drag it onto your desktop then give it an icon (use 'pfind file finder' to locate umplayer, it will list several icons in .png format, I used a 32x32 and it looks good.)
Hope this helps until someone can get the thumbnail graphics working in Mic's new version!
On further testing of 5.3.5.3 I find it to be a distro with a lot of potential for both new and seasoned users, googleearth is still extremely fast and the best I've used to date.
If pwidgets isn't going to be maintained, maybe we could get a new 'conky' with all the goodies in the PPM?
>>>---Indian------>
I found that a previous umplayer works properly (except for no menu entry) in 5.3.5.3
avplayersj2-slacko-i686.sfs
Everything works in this player but... you have to go to usr/local/bin/umplayer and drag it onto your desktop then give it an icon (use 'pfind file finder' to locate umplayer, it will list several icons in .png format, I used a 32x32 and it looks good.)
Hope this helps until someone can get the thumbnail graphics working in Mic's new version!
On further testing of 5.3.5.3 I find it to be a distro with a lot of potential for both new and seasoned users, googleearth is still extremely fast and the best I've used to date.
If pwidgets isn't going to be maintained, maybe we could get a new 'conky' with all the goodies in the PPM?
>>>---Indian------>
Cloud Computing For Every Puppy (a .pet)
[url]http://murga-linux.com/puppy/viewtopic.php?t=69192[/url]
[url]http://murga-linux.com/puppy/viewtopic.php?t=69192[/url]
Re: finding sfs
It's not that. But I moved the sfs file to the root of a different partition than the boot partition and it WORKED!shinobar wrote:I remember old persisting bug in finding the main sfs.
It may occur when you have multiple puppy_slacko_5.3.5.3.sfs in your PC...
I will have to set up some other machines to test this more.
Re: booting issue
@rcrsn51, 01micko
Don't you have another full installed slacko in the same PC?
Don't you have another full installed slacko in the same PC?
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]
Does using the UUID help?
Code: Select all
blkid /dev/sda8 #replace drive id to suit
Puppy Linux Blog - contact me for access
Re: booting issue
Mines an old spup, that I keep updatingshinobar wrote:@rcrsn51, 01micko
Don't you have another full installed slacko in the same PC?
Puppy Linux Blog - contact me for access
Re: booting issue
No. I have a frugal install of 533 in another partition. But deleting it didn't change anything.shinobar wrote:@rcrsn51, 01micko
Don't you have another full installed slacko in the same PC?
Re: booting issue
@rcrsn51, 01micko
I have made some tests.
And i made another frugal install on sda3/slacko-pae.
In this case, booted off from the sdc2 but the puppy took the sfs from sda3/slacko-pae.
Next, i removed the main sfs from sda3/slacko-pae but left the vmlinuz and initrd.gz there.
That is, there are two vmlinuz, sdc2 and sda3/slacko-pae, but the sfs is only at sdc2.
In this case, same booting off from the sdc2, the puppy maybe found the vmlinuz at sda3/slacko-pae, but failed to find the sfs.
I got 'puppy_slacko-5.3.5.3.sfs not found!'.
I have made some tests.
Code: Select all
title Puppy slacko 5.3.5.3 (sdc2)
uuid df28a7f3-8257-42f2-b555-864fe0a6a64b
kernel /vmlinuz pmedia=atahd pfix=fsck
initrd /initrd.gz
In this case, booted off from the sdc2 but the puppy took the sfs from sda3/slacko-pae.
Next, i removed the main sfs from sda3/slacko-pae but left the vmlinuz and initrd.gz there.
That is, there are two vmlinuz, sdc2 and sda3/slacko-pae, but the sfs is only at sdc2.
In this case, same booting off from the sdc2, the puppy maybe found the vmlinuz at sda3/slacko-pae, but failed to find the sfs.
I got 'puppy_slacko-5.3.5.3.sfs not found!'.
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]
Re: booting issue
Exactly! I just found the same thing in my setup. I routinely have subfolders with backup copies of vmlinuz and initrd.gz. Their presence is keeping 5353 from finding its sfs file. If I delete them so the only copies are at the root, it works.shinobar wrote:Next, i removed the main sfs from sda3/slacko-pae but left the vmlinuz and initrd.gz there. That is, there are two vmlinuz, sdc2 and sda3/slacko-pae, but the sfs is only at sdc2.In this case, same booting off from the sdc2, the puppy maybe found the vmlinuz at sda3/slacko-pae, but failed to find the sfs.I got 'puppy_slacko-5.3.5.3.sfs not found!'.
But this is the only Puppy I have ever seen that works this way. Even the latest Precise doesn't care about the extra copies.
Re: booting issue
It occurs when you have a copy of the vmlinuz in a subfolder sdxn/foo/vmlinz, where x is the drive number and n as the partition number, and only if the sdxn is earlier than the one of the booting partition. I am not sure it occurs or not even if you specify the 'psubdir'.rcrsn51 wrote:Exactly! I just found the same thing in my setup. I routinely have subfolders with backup copies of vmlinuz and initrd.gz. Their presence is keeping 5353 from finding its sfs file. If I delete them so the only copies are at the root, it works.shinobar wrote:Next, i removed the main sfs from sda3/slacko-pae but left the vmlinuz and initrd.gz there. That is, there are two vmlinuz, sdc2 and sda3/slacko-pae, but the sfs is only at sdc2.In this case, same booting off from the sdc2, the puppy maybe found the vmlinuz at sda3/slacko-pae, but failed to find the sfs.I got 'puppy_slacko-5.3.5.3.sfs not found!'.
But this is the only Puppy I have ever seen that works this way. Even the latest Precise doesn't care about the extra copies.
For example, suppose a full install on sda3, which has sda3/boot/vmlinuz but no main sfs.
No problem with another frugal install on sda2. But a frugal install on sda5 will fail.
The bug is in the function 'search_func' in the initrd introduced on 2011-04-25 and persists still now. I don't know about the older woof.
Last edited by shinobar on Thu 13 Sep 2012, 02:15, edited 1 time in total.
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]
I stand corrected about Slacko 533 - it has the same bug. If the three core files are at the root and the first two files are also in a subfolder, it fails.
But if you move everything one level deeper, it works, ie. the three core files are in a subfolder and the backups are in a sub-sub-folder. But in that case, there would be a psubdir argument.
I'm guessing that the search logic goes like this:
If no psubdir argument is used, start looking in subfolders FIRST.
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.
If you can't find the two files in any subfolders, then go back to the root and look there next.
Maybe there are other Puppies that work this way, I just never had that particular setup.
But if you move everything one level deeper, it works, ie. the three core files are in a subfolder and the backups are in a sub-sub-folder. But in that case, there would be a psubdir argument.
I'm guessing that the search logic goes like this:
If no psubdir argument is used, start looking in subfolders FIRST.
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.
If you can't find the two files in any subfolders, then go back to the root and look there next.
Maybe there are other Puppies that work this way, I just never had that particular setup.
Re: boot issue
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.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.
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]
Re: boot issue
I think the precise beta has the same initrd dated 2012-03-28 and the same issue as the slacko beta has.rcrsn51 wrote:At the moment, Precise is the only one that does it in the "right" order.
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]
boot isse of the presice
Confirm the copy of the vmlinuz is the same.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.
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
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
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]