Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Sun 28 May 2017, 14:55
All times are UTC - 4
 Forum index » Advanced Topics » Puppy Projects
Slacko32/64 700 BETA 2
Moderators: Flash, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 3 of 33 [494 Posts]   Goto page: Previous 1, 2, 3, 4, 5, ..., 31, 32, 33 Next
Author Message
James C


Joined: 26 Mar 2009
Posts: 6695
Location: Kentucky

PostPosted: Mon 29 Aug 2016, 15:20    Post subject:  

gyro wrote:
@James C,

I notice most of your kernel lines have a pdev1=sdb1, but 1 shown doesn't.
If you use a kernel line that doesn't specify a pdev1 (or pupsfs) it will go looking on all partitions.

So what kernel line did you use?

Got error messages, what were they?

gyro



Used the one shown, only changed the title.

Error messages were something about ext4 errors on sdb7,sdb8 and sdb9 which are now occupied by AntiX, Trisquel and Devuan and not being able to find the slacko64 sfs on sdb9.

http://www.murga-linux.com/puppy/viewtopic.php?p=920447#920447
Back to top
View user's profile Send private message 
gyro

Joined: 28 Oct 2008
Posts: 1326
Location: Brisbane, Australia

PostPosted: Mon 29 Aug 2016, 15:27    Post subject:  

@James C,
Sorry, I didn't pay close enoough attention.
Yes, the one for pup15.
Nothing unusual there, so still got nothing.
gyro
Back to top
View user's profile Send private message 
James C


Joined: 26 Mar 2009
Posts: 6695
Location: Kentucky

PostPosted: Mon 29 Aug 2016, 15:52    Post subject:  

gyro wrote:
@James C,
Sorry, I didn't pay close enoough attention.
Yes, the one for pup15.
Nothing unusual there, so still got nothing.
gyro



I took a quick,quick glance in the initrd,didn't notice anything obvious and just switched to the initrd out of 6.3.0 since I knew it worked.
Back to top
View user's profile Send private message 
jlst

Joined: 23 Nov 2012
Posts: 571

PostPosted: Mon 29 Aug 2016, 17:55    Post subject:  

I can't reproduce the issue. Maybe some debug code can shed light on the situation. Maybe implement pfix=debug and restore syslogd and klogd for that pfix (output goes to /tmp)..
Back to top
View user's profile Send private message 
jlst

Joined: 23 Nov 2012
Posts: 571

PostPosted: Mon 29 Aug 2016, 21:13    Post subject:  

"debugsave" script

If you're having problems booting puppy, this can help
save debug info to a partition for further analysis,
assuming a kernel panic does not occur.

Just type:

debugsave

and follow the instructions

Last edited by jlst on Tue 30 Aug 2016, 11:09; edited 6 times in total
Back to top
View user's profile Send private message 
smokey01


Joined: 30 Dec 2006
Posts: 2529
Location: South Australia

PostPosted: Mon 29 Aug 2016, 21:44    Post subject:  

Gyro I compiled zarfy which works fine but the changes are not persistent. As soon as I run zarfy again the monitors are swapped back but on next restart all reverts to original wrong way round.
_________________
Software <-> Distros <-> Tips <-> Newsletters
Back to top
View user's profile Send private message Visit poster's website 
jlst

Joined: 23 Nov 2012
Posts: 571

PostPosted: Tue 30 Aug 2016, 01:07    Post subject:  

nice app smokey01. it's really old.

apparently there's no switch to make it apply settings, so i was searching
for a config file and found it. i identified some values usable by xrandr.

usage:

run zarfy
change settings
click on OK (maybe Apply first)
restart X/reboot/etc

(and it will apply basic settings)

Last edited by jlst on Tue 30 Aug 2016, 11:55; edited 1 time in total
Back to top
View user's profile Send private message 
gyro

Joined: 28 Oct 2008
Posts: 1326
Location: Brisbane, Australia

PostPosted: Tue 30 Aug 2016, 04:32    Post subject:  

smokey01 wrote:
Gyro I compiled zarfy which works fine but the changes are not persistent. As soon as I run zarfy again the monitors are swapped back but on next restart all reverts to original wrong way round.
Thats why I put a little script in /root/Startup.
gyro
Back to top
View user's profile Send private message 
gyro

Joined: 28 Oct 2008
Posts: 1326
Location: Brisbane, Australia

PostPosted: Tue 30 Aug 2016, 05:03    Post subject:  

@boot fails with relsase initrd.gz folk.

Just to start on the same page, could you please do test booting with the following configuration:
Do a non uefi boot of a frugal install on an ext partition containing only these 4 files, initrd.gz, puppy_slacko64_6.9.5.sfs, vmlinuz, zdrv_slacko64_6.9.5.sfs.
With these boot paramaters "pmedia=atahd", "pfix=fsckp", and appropriate "pdev1=" and "psubdir=".

Note: the pfix=fsckp, this tells the new init to fsck every ext partition before just before mounting it. The important thing for testing is that it displays the output of e2fsck on the console, so it should be obvious if the "pdev1=" parameter is not being honoured.

We need to try to reduce the variation, in order to pinpoint the significant difference.

Oh, by all means use the debug version produced by jlist.

If this does not provide a resolution, then I can produce a series of init scripts that sinply stop and display significant variables, (then reboot with ctrl+alt+del, it's ok no partitions are mounted when it stops).
The first version would do this very early to establish that the boot parameters have been correctly interpreted, and then subquent versions move this further down the code, until we find something that is not right.
Quite tedious, but it's pretty much the method I used to build the thing.

gyro
Back to top
View user's profile Send private message 
gyro

Joined: 28 Oct 2008
Posts: 1326
Location: Brisbane, Australia

PostPosted: Tue 30 Aug 2016, 07:20    Post subject:  

I'm working on an init which has several breakout points, controled by "pdebug=n" boot parameter.
"pdebug=0" will dropout very early, "debug=1" will dropout later, and so on...
So downloading a single initrd.gz will provide many testing points.
Even just seeing which debug point you get to before a problem occurs, will give us a starting clue.
gyro
Back to top
View user's profile Send private message 
01micko


Joined: 11 Oct 2008
Posts: 8629
Location: qld

PostPosted: Tue 30 Aug 2016, 07:24    Post subject:  

Thanks @gyro for joining the discussion.

Hopefully this weekend I can build a 32 bit version with the latest 'rationalise' at that time and further the discussion/findings/fixes in a new thread.

Cheers!

_________________
Puppy Linux Blog - contact me for access
Back to top
View user's profile Send private message Visit poster's website 
gyro

Joined: 28 Oct 2008
Posts: 1326
Location: Brisbane, Australia

PostPosted: Tue 30 Aug 2016, 08:59    Post subject:  

I have atached a debgug init for this slacko64, as init.gz.
It's also available as an updated initrd.gz from http://www.fishprogs.software/puppy/slacko64/initrd.gz.
This init accepts "pdebug=" boot parameters.
"pdebug=0" drops out to the console just after intepreting boot parameters.
"pdebug=3" drops out just before getting the no puppy...sfs message.
1,2 are in between. There is no "pdebug=4".
At each pdebug point it displays a message showing significant init variables at that point. The different pdebug points show different messages.
At the console you can run commands like "mount" to confirm that no partitions are still mounted.
Use ctrl+alt+del keys to reboot.

How to use:
Start by booting with "pdebug=0", and then "pdebug=1" etc.. noting the last pdebug point that was successful.
Please report what was the last successful pdebug point number and the contents of the line above showing the init variables.

Edit: This version has been replaced, see later post

gyro

Last edited by gyro on Tue 30 Aug 2016, 12:44; edited 1 time in total
Back to top
View user's profile Send private message 
gyro

Joined: 28 Oct 2008
Posts: 1326
Location: Brisbane, Australia

PostPosted: Tue 30 Aug 2016, 09:42    Post subject:  

An example of successful boots using pdebug.

grub4dos kernel line:
Code:
kernel /puppy/slacko64/vmlinuz libata.noacpi=1 pmedia=atahd pupsfs=49baa82d-8c69 psubdir=/puppy/slacko64 pfix=fsckp pdebug=0
produces this variables display line:
Code:
PMEDIA=atahd PUPSYS=49baa82d-8c69 PSUBDIR=/puppy/slacko64 pfix=fsckp
Using pdebug=1 produces:
Code:
PUPSYS= P_BP_ID=49baa82d-8c69
Using pdebug=2 produces:
Code:
ONE_PART=sdb4 ONE_FN=/puppy/slacko64/puppy_slacko64_6.9.5.sfs LOOK_PUP= LOOK_SAVE=
Using pdebug=3 produces:
Code:
ONE_PART=sdb4 ONE_TRY_FN=/puppy/slacko64/puppy_slacko64_6.9.5.sfs PDRV=sdb4,ext4,/puppy/slacko64/puppy_slacko64_6.9.5.sfs
And pdebug=4 results in boot to desktop.

gyro
Back to top
View user's profile Send private message 
jlst

Joined: 23 Nov 2012
Posts: 571

PostPosted: Tue 30 Aug 2016, 11:50    Post subject:  

haha silly me. zarfy is awesome. it should be included in all puppies. it's really tiny.

so it has the -l option, at first thought it didn't work.

so i tested with 2 monitors and now i think puppy remembers that last settings and will apply them everytime X starts...
xinitrc__zarfy-1.0.pet
Description 
pet

 Download 
Filename  xinitrc__zarfy-1.0.pet 
Filesize  3.11 KB 
Downloaded  33 Time(s) 
Back to top
View user's profile Send private message 
gyro

Joined: 28 Oct 2008
Posts: 1326
Location: Brisbane, Australia

PostPosted: Tue 30 Aug 2016, 12:41    Post subject:  

A new version of an init script with debug support is attached.
An updated initrd.gz is available at http://www.fishprogs.software/puppy/slacko64/initrd.gz.

This a a slightly refined version, in that the debug messages are always written if any value of pdebug is set. i.e. if you boot with "pdebug=y" all debug messages will be appended to bootinit.log.
If "pdebug=" is set to 0,1,2,3 init will drop out as per previous version.

So, for initial testing boot "pdebug=y". If the boot works, there's a few extra lines in "/initrd/tmp/bootinit.log". If it fails, all the messages should appear on the screen following the "bootinit.log" line.

Example debug lines from a successful boot:
Code:
0: PMEDIA=atahd PDRV=49baa82d-8c69 PSUBDIR=/puppy/slacko64 pfix=fsckp
1: PDRV= P_BP_ID=49baa82d-8c69 P_BP_FN=
2: ONE_PART=sdb4 ONE_FN=/puppy/slacko64/puppy_slacko64_6.9.5.sfs ONE_MP=/mnt/pdrv
3: ONE_PART=sdb4 ONE_TRY_FN=/puppy/slacko64/puppy_slacko64_6.9.5.sfs PDRV=sdb4,ext4,/puppy/slacko64/puppy_slacko64_6.9.5.sfs

Edit: Attachemnt deleted, superceeded by later version, see later post.

gyro

Last edited by gyro on Wed 31 Aug 2016, 07:23; edited 1 time in total
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 3 of 33 [494 Posts]   Goto page: Previous 1, 2, 3, 4, 5, ..., 31, 32, 33 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Puppy Projects
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.0883s ][ Queries: 14 (0.0056s) ][ GZIP on ]