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_deamo...

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...

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

Hi Pizzasgood, I too tried this with Puppy 4.1. I can confirm that this only happens with pebble. Unfortunately, your modified version did not work as well... it hung at the boot screen. Good luck, and thanks for this great program! Edit: Also, is it possible that pebble modified a script that prev...

Well, I'm not sure what's wrong, but I do know there are a couple spots where there is a potential for it to get stuck in an infinite loop if something breaks. They were spots where the script waits for the daemon to finish doing something before continuing. I adjusted the code so that now they won...

Pizzasgood wrote:Thanks. I'll see if I can track it down tomorrow.

Waits for your good news !

I can not get the X sometimes. Does the bootsplash go away and leave you at the commandline, so that you have to run xwin ? Does it do that, but without clearing the image? Or does it hang, requiring a reboot? What kind of install? Full, frugal, USB? -------- FYI, I've now uploaded packages for 4.1...

After installed the pebble_p411-1.0 for puppy4.1.1-k2.6.25.16, I can not get the X sometimes. But is not like this, sometimes has been normal. The screen has paused in the last image. I thought maybe the x have not started.
How to solve it?

The resolution question I had already solved, the question left in screen refurbishing rate. It is not unnecessary to use 915resolution. modify xorg.conf: change HorizSync 31.0-80.0 VertRefresh 50.0-72.0 to HorizSynv 31.0-50.0 VertRefresh 40.0-72.0 then restart x,the resolution is changed to your ho...

the modes can set very specific things for the monitor, like frequencies. For LCD monitors, this usually is not needed, only for few models, that cannot sync with the graficscard by default. To set the permanent resolution, you must edit /etc/rc.d/rc.local as written in the readme. Mark Do not have...

Can I write the "Modes" to xorg.conf and set it to take effect?

yes, I think so. Readme from Muppylinux: 915resolution sets a video bios mode for intel graficscards. It must be run before X starts. For example add a line like this to /etc/rc.d/rc.local 915resolution 45 1024 600 (mode width height) use: 915resolution -l to see available modes http://www.geocitie...

the intel chips seem to ignore the resolution in xorg.conf, as the resolution is set in the graficscard. So you must use instead "915resolution". That utility seems to set the resolotion in the graficscard itself. Mark According to the http://www.murga-linux.com/puppy/viewtopic.php?t=3246...

MU wrote:I think this should work:
http://www.murga-linux.com/puppy/viewtopic.php?t=32462
Mark

Thank you for your reply, I will try this way.
Can tell me why when I run xorgwinzard to choose any screen resolution when, xsever always automatically set to the largest screen resolution?

Change the resolution null and void, no matter what I set the value, such as 1024x768 or 800x600, It always displayed as a screen resolution of the biggest 1280x1024.
My chipset is intel 945gm, and Puppy is 400. How to solution it? Thansk for any help!

This problem occurs with the Intel 810 as well and I took the driver from Puppy 3.01. If the Intel 945 can work with the 810 driver then the following link to my procedure could be useful: http://www.murga-linux.com/puppy/viewtopic.php?t=29144 Thanks for your replay! In Puppy 4.00, the 810 dirver i...

This question already puzzled my many days, hoped that the person of good intention may help me to solve

When I start from CD to puppy400, cannot use xorg to start X. Examines Xorg.0.log, discovers some mistakes . (EE) GARTInit: Unable to open /dev/agpgart (No such device) (WW) intel(0): /dev/agpgart is either not available, or no memory is available for allocation. Using pre-allocated memory only. (==...

#Special base config file used in Puppy Linux. # ********************************************************************** # Module section -- this section is used to specify # which dynamically loadable modules to load. # ********************************************************************** # Sectio...

Below is my Xorg.0.log and xorg.conf: X Window System Version 1.3.0 Release Date: 19 April 2007 X Protocol Version 11, Revision 0, Release 1.3 Build Operating System: UNKNOWN Current Operating System: Linux puppypc 2.6.21.7 #1 Sat Aug 30 18:33:20 GMT-8 2008 i686 Build Date: 28 November 2007 Before r...