Sorry, been traveling and visiting. I'll try to look into it more this week._________________Between depriving a man of one hour from his life and depriving him of his life there exists only a difference of degree. --Muad'Dib

I'm not sure what's wrong. It works fine on my end. You said it only happens sometimes. Have you noticed any kind of patterns with when it happens, like maybe only after improper shutdowns? Or every other boot?

Just a heads-up: from this coming Monday until January 5 I probably won't have any internet access, so if I seem to vanish until January it isn't because I'm ignoring you._________________Between depriving a man of one hour from his life and depriving him of his life there exists only a difference of degree. --Muad'Dib

This time, I installed the pup412 with full hd. then installed the pebble1.0 for 4.12. But it also stoped at the image of "Booting Puppy Linux"!
After some tests, I found that problem occured with "bootsplash stop" by adding test-code to rc.sysinit. The code "bootsplash stop" could not return.
Why "bootsplash stop" could not return?

Finaly, I found that the "bootsplash stop" fall into the endless loop. It has paused in the loop of "while" beacuse the ASLEEP_FILE is not existed. I don't konwn which process has operated the file called "pebble_nowasleep". I had not discovered at least in pebble_deamon. So I posted the problem at here.

The file would be created by pebble-daemon, after it finishes shutting itself down. That way I can ensure that it's finished before cleaning up the screen. Otherwise there is a possibility that the script will clear the screen before the daemon finishes shutting down, leading to the daemon re-drawing the screen after it has been cleared.

The part that shuts down the pebble-daemon is the part above the while loop, that does the echo. What it does is output a "q" into a pipe. Pebble-daemon checks that pipe each cycle and reads anything inside. If it sees a "q" it interprets that as a command to shut down.

The modified version I posted for 4.11 adds some extra code so that it will only wait up to five seconds, and then continue anyways. That way if pebble-daemon doesn't shutdown for some reason, or the file doesn't get created properly, then the script won't get stuck in an infinite loop.

If that while loop is where it was hanging, installing the modified version should have fixed it. Did you perhaps forget to install the .pet file that was inside the tarball? Since the hang seems to be happening at the very end, the .pet would be the important part.

Try it again, being sure to use 4.11 and the modded package, and to use the .pet. If it works I'll rebuild and upload the packages for the other versions of Puppy with that added to them.

Of course, even if the modification "fixes" it, that's only a workaround. I need to see if I can figure out why the pebble-daemon is hanging.

james_liu wrote:

Good, the edition 4.11 first like this, did not know that 4.12 can also have such question

Sorry, but I don't understand what you're trying to say.

kranthi wrote:

one solution that seems to work for me is to replace
"bootsplash stop" with "killall pebble-daemon"

dont know if there are any side-effects though.

It could leave the cursor that you see when at the commandline invisible (the real one, not rxvt). Also, it might leave a couple files lying around in /tmp. And probably would leave the file /dev/console symlinked to the wrong place, causing any lines of code with a ">/dev/console" to not output to the screen like they should. So nothing life-threatening, just a couple small nuisances._________________Between depriving a man of one hour from his life and depriving him of his life there exists only a difference of degree. --Muad'Dib

I am also experiencing a freeze in puppy 4.1.2 (frugal install). The problem for me seems to happen around the switch-root. I mounted the drive on another machine and the last line I see in /initrd/tmp/boot-text.log is "Performing a 'switch-root' to the layered filesystem..."

If I remember and am not busy with more important things, I'll take another look over spring break. But what I really need to do is get some of my other projects finished so I can start the research I'll need in order to make Pebble 2.0. That's a project that will probably have to wait until summer break, but it will be much more usable than this one and implemented in a more stable way. I'll definitely be eliminating many of the weird quirks that this version has. Plus it will have a very important difference: a well integrated debug mode._________________Between depriving a man of one hour from his life and depriving him of his life there exists only a difference of degree. --Muad'Dib

Talking about future releases of Pebble:
Are there any plans to include the option to provide the commandline with a background image instead of hiding the output behind a JPEG (like bootsplash etc)? It would be really awesome to have a background image in the commandline all the time (just like GoblinX, Elive, you name it), even after the system finished booting.

I tried to compile splashy a few days ago, but not really being an expert with gcc, make always failed and exited with an error (it probably just requires a little adjustment for ./configure, but I'm a complete newbie when it comes to that. ^^').

Yeah, I intend to make version 2.x use split screen, and in the process I'll probably have to write code that would let me render the text myself, which means I could put it over an image, in a box, sandwiched between two images, etc. All of which could be animated...

I suppose if I can get it to handle input properly, I could theoretically set it up as something you can just run, outside of booting, to have those graphics. And if I make the interface properly, you should be able to almost control the graphics with an external program, so they could update in real time to match the state of your computer (i.e. turn redder based on how hard the cpu is cranking, or have penguins waddling around in the background with the number related to the cpu load...).

I hadn't thought about those possibilities before... Thanks for sparking them off.

At the moment, it's not looking like I'll start on Pebble 2.0 until Fall. I need to finish Retrovol, and I've neglected Project Carrot for the last couple months. I also want to start Project Onion this summer._________________Between depriving a man of one hour from his life and depriving him of his life there exists only a difference of degree. --Muad'Dib

You're welcome, pizzasgood. ^^
I'd love to help you with pebble, but unfortunately I can't.
The tools that I've written so far are in tcl/tk, or they use GtkDialog3 (but I want to move to tcl/tk completely, GtkDialog requires way too many dirty hacks for the simplest tasks if you want to show things in real-time). But if you need a few good pics for pebble, don't hesitate to ask, I can help you with that (I'm a 2D/3D artist, both traditional and digital).

Cool. I'll keep that in mind when I start working on it again. I used to do a good amount of art, but I've been too busy for the last several years. I did a little sketching the other day and was happy to see that my abilities haven't completely deteriorated But I generally prefer programming over art._________________Between depriving a man of one hour from his life and depriving him of his life there exists only a difference of degree. --Muad'Dib

I tried to compile splashy a few days ago, but not really being an expert with gcc, make always failed and exited with an error (it probably just requires a little adjustment for ./configure, but I'm a complete newbie when it comes to that. ^^').

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