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 Tue 11 Dec 2018, 22:52
All times are UTC - 4
 Forum index » Advanced Topics » Cutting edge
TazPuppy Beta 12
Moderators: Flash, Ian, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 48 of 49 [730 Posts]   Goto page: Previous 1, 2, 3, ..., 46, 47, 48, 49 Next
Author Message
thinkpadfreak

Joined: 17 Oct 2016
Posts: 46

PostPosted: Sun 11 Nov 2018, 12:35    Post subject:  

mistfire wrote:
> By the way i will try to investigate also the fdrv in sfs_load. But based on your screenshot, it is likely the culprit because the filename contains whitespaces

As for the spaces of the filename, I think the font is responsible. I added a Japanese font set, and strangely there are cases where underscores are invisible.
There are at least several people in the Puppy Linux Japanese Forum who confirm the failure to boot: when fdrv sfs and an extra sfs exist, beta 8 is unable to boot.

As a test, I joined the contents of fdrv and zdrv, and made a new zdrv. Since there doesn't exsist fdrv, beta 8 boots successfully. It seems that fdrv and an extra sfs conflict, and the layers cannot be configured. Please do investigate this issue.


> I cannot no longer push beyond 4.17.6 because it cannot compiled by my host puppy X-Slacko Slim. So I will resort to the latest 4.9.x backport, If the linux kernel source code has builitin aufs that will be no problem.

Unfortunately, I do not know much about kernel compilation. 4.17.6 kernel seems good in itself, though it is too new for my machine.
Back to top
View user's profile Send private message 
mistfire

Joined: 04 Nov 2008
Posts: 1002
Location: PH

PostPosted: Sun 11 Nov 2018, 19:22    Post subject:  

@thinkpadfreak what sfs file did you load aside the fdrv that was loaded. Can you try to rename that fdrv as ydrv_tazpup_5.0.sfs then boot it to see what happens whether it will boot sucessfully or not?
Back to top
View user's profile Send private message 
thinkpadfreak

Joined: 17 Oct 2016
Posts: 46

PostPosted: Sun 11 Nov 2018, 20:17    Post subject:  

@mistfire
The following is a summary of what I have tried so far.

main sfs + fdrv + zdrv ... OK
main sfs + fdrv + zdrv + an extra sfs (firefox) .... failure
main sfs + zdrv (the content is fdrv and zdrv merged) + an extra sfs ... OK


> Can you try to rename that fdrv as ydrv_tazpup_5.0.sfs then boot it to see what happens whether it will boot sucessfully or not?

I will try later.
Back to top
View user's profile Send private message 
thinkpadfreak

Joined: 17 Oct 2016
Posts: 46

PostPosted: Sun 11 Nov 2018, 21:56    Post subject:  

I tried renaming fdrv to ydrv.

main sfs + ydrv + zdrv + extra sfs ... OK

ydrv is not listed in sfs_load. The mount point of ydrv is /dev/loop3, while the mount point of fdrv is /dev/loop5, which seems to conflict with that of an extra sfs.

In case of UpupBB, for example, the configuration of the layers is very different. I wonder if the init script defines the configuration. (I am just an ordinary user, and don't know in detail.)
Back to top
View user's profile Send private message 
mistfire

Joined: 04 Nov 2008
Posts: 1002
Location: PH

PostPosted: Mon 12 Nov 2018, 03:25    Post subject:  

@thinkpadfreak I finally found the bug on loop5. It is the big flaw in the init script code upon loading extra sfs. It is now fixed. I made some revisions on sfs_load script.

To mitigate this problem on beta 8 or below rename the fdrv_tazpup_5.0.sfs to ydrv_tazpup_5.0.sfs
Back to top
View user's profile Send private message 
belham2

Joined: 15 Aug 2016
Posts: 1628

PostPosted: Mon 12 Nov 2018, 09:04    Post subject:  

Hi Mistfire and all,

Congrats on keeping this going for so long now? Especially since a novice like me can finally play it and get somewhere.

Can I ask a question of anyone here?

What is the exact order, when booting occurs, that the various *drv sfses are loaded?

I assume the main.sfs always comes, at the first layer so-to-speak, but what comes or is "officially" loaded next? An adrv? A zdrv? A fdrv? A ydrv?? (assuming we have these when we are booting up)

I guess what I am asking, what is the official order that puppy loads all these *drv sfses??

Reason I am asking because it seems if you are not careful, like when I started renaming *drv files, some stuff I had modded in one *drv was getting written over by a later *drv and messing up stuff.

Thanks for any response(s) explaining this.
Back to top
View user's profile Send private message 
mistfire

Joined: 04 Nov 2008
Posts: 1002
Location: PH

PostPosted: Mon 12 Nov 2018, 11:20    Post subject:  

@belham2 based on boot observation, loading sequence are here as follows:
main sfs
zdrv sfs
adrv sfs
ydrv sfs
fdrv sfs

only loading fdrv was the problem due to /dev/loop5 assignment which was used also by zdrv sfs. That problem is now fixed
Back to top
View user's profile Send private message 
thinkpadfreak

Joined: 17 Oct 2016
Posts: 46

PostPosted: Mon 12 Nov 2018, 11:59    Post subject:  

@mistfire

I am glad that the cause of the problem has been identified.

I posted to the Japanese Forum about the workaround.
Back to top
View user's profile Send private message 
mistfire

Joined: 04 Nov 2008
Posts: 1002
Location: PH

PostPosted: Mon 12 Nov 2018, 21:25    Post subject:  

I made an update on firmware drivers, the result was the fdrv file size was increased by 10Mb so it is now 20Mb.
Back to top
View user's profile Send private message 
mistfire

Joined: 04 Nov 2008
Posts: 1002
Location: PH

PostPosted: Thu 15 Nov 2018, 22:17    Post subject:  

TazPuppy Beta 9 released

Changes:
* Linux kernel 4.9.124
* A bug on initrd which both zdrv and fdrv failed to load is fixed
* Autoconfig also work if the kernel version changes
* Some fixes on boot scripts

Download: https://drive.google.com/file/d/1DszXd7Hvx7Pzhifxr_pmE4Tzuz2dsZ79/view?usp=sharing
MD5 Checksum: 851882385a390eb0a88712970e29a918

Build Kit: https://drive.google.com/file/d/1zDoX3XzhzhDD9_lAGy3I-KnQhD5X5Rwv/view?usp=sharing
Back to top
View user's profile Send private message 
thinkpadfreak

Joined: 17 Oct 2016
Posts: 46

PostPosted: Fri 16 Nov 2018, 08:29    Post subject:  

I have installed beta 9. (It is a frugal installation and the save file is newly created.)

Auto-configuration of sound cards worked at first boot.
Kernel 4.9 seems to be more suitable for my machine, though I did not expect that the kernel would be changed.

Thanks a lot!
Back to top
View user's profile Send private message 
mistfire

Joined: 04 Nov 2008
Posts: 1002
Location: PH

PostPosted: Sat 17 Nov 2018, 07:46    Post subject:  

@thinkpadfreak youre welcome

Right now I'm attempting to make the tazpup-builder architecture independent. It means it can easily to build tazpuppy either 32 or 64-bit. At present, tazpup builder builds 32-bit only. I gradually remove binary files in the core folder. In the future it was all bash scripts which is my ultimate goal.

vercmp and cddetect is now bash script, elspci is now removed (with a cost of modifying the script). Next to remove was dc command as well as freememtray_applet and will be replaced by yad and bash
Back to top
View user's profile Send private message 
mistfire

Joined: 04 Nov 2008
Posts: 1002
Location: PH

PostPosted: Thu 22 Nov 2018, 19:41    Post subject:  

I succesfully created the freememtray_applet using bash and yad. dc command is now dropped. On my latest experiment it now works nicely.
Back to top
View user's profile Send private message 
mistfire

Joined: 04 Nov 2008
Posts: 1002
Location: PH

PostPosted: Sat 24 Nov 2018, 05:03    Post subject:  

TazPuppy Beta 10 released:

Changes:
* busybox is now upgradable on tazpkg
* freememtray_applet is now bash script
* builtin make-devx script to make devx module from slitaz packages (experimental)

NOTE: To use make-devx script to create devx module, type this command to terminal
Code:
make-devx [working folder to creating devx module]


Download: https://drive.google.com/file/d/1eXdzGhs5S_-xn7VF2d_RaAERgHVYFiFK/view?usp=sharing
MD5 checksum: afb03b61cd2937bac4a47e7bf71be86f

Build kit: https://drive.google.com/file/d/1h3-En87eSjgbi2VlHBPEk970hreTfgyz/view?usp=sharing
Back to top
View user's profile Send private message 
don570


Joined: 10 Mar 2010
Posts: 5203
Location: Ontario

PostPosted: Sat 24 Nov 2018, 13:16    Post subject:  

I suggest that the password for tazpuppy be listed in the first post.
______________________________________________________
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 48 of 49 [730 Posts]   Goto page: Previous 1, 2, 3, ..., 46, 47, 48, 49 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Cutting edge
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.1428s ][ Queries: 13 (0.0750s) ][ GZIP on ]