(old)Puppy Linux Discussion Forum

artsown wrote:Barry, it looked to me like the code segment has a typo and a
missing fi instruction. Note the $PS I put in and the added fi in
the below code segment:

##w468 rox may not start old hardware, try again... 120517 bring this back...

$PS="`ps`"
if [ "`echo "$PS" | grep 'ROX\-Filer'`" = "" ];then
if ! busybox pidof ROX-Filer;then
touch /tmp/roxfilerstartupproblem #see /sbin/pup_event_frontend_d
sleep 3
fi
if ! busybox pidof ROX-Filer;then #check again.
rox -p /root/Choices/ROX-Filer/PuppyPin
fi
fi

I first tried this with sleep 3 as above and eventually changed it to
sleep 1. I've done a total of 17 hard machine reboots so far with
no black screens. I've counted seconds from the last text message
(starting x server) until a gui appears during startup. It has varied
from a low of 6 seconds to 31 seconds but most of the time it's
21 seconds (even with sleep 1).

BTW, I'm a old engineer-programmer who knows BASIC and
assembly language but I'm unfamiliar with the scripting language
used here ... just for your info. It appears that fi acts as a END IF
and one was missing.

I've mentioned before that all my test machines are similar, The
one I used for this test is a DELL Dimension 2350 having a 1.8 ghz
Pentium 4 and 768 meg RAM.

Art

##w468 rox may not start old hardware, try again... 120517 bring this back...
##PS="`ps`"
##if [ "`echo "$PS" | grep 'ROX\-Filer'`" = "" ];then
#if ! busybox pidof ROX-Filer;then
# touch /tmp/roxfilerstartupproblem #see /sbin/pup_event_frontend_d
# sleep 0.5
# if ! busybox pidof ROX-Filer;then #check again.
#  rox -p /root/Choices/ROX-Filer/PuppyPin
# fi
#fi

Argolance wrote:Hello,
I just finished an iso based on Puppy precise 5.4.1. I don't really understand how these releases numbers work indeed (big gaps!)...
My (silly) question: How could I upgrade Puppy precise 5.4.1 to Puppy 5.4.2? Is there a pet package? If yes, where could I download it?

Thank you!
Cordialement.

npierce wrote:This is a continuation of a Precise 5.4.2 discussion started on the Precise 5.4 thread.

(By the way, to avoid confusion, does the name of the Precise 5.4 thread (currently named "Precise Puppy 5.4 and 5.4.2") need to be corrected, and should this thread -- the real Precise 5.4.2 thread -- be made sticky?)

[url=http://www.murga-linux.com/puppy/viewtopic.php?p=669830#669830]On Sat 08 Dec 2012[/url], backi wrote:During process of downloading from repo the whole letters which are indicating download suddenly changed to lttles squares ,became unreadable .

[url=http://www.murga-linux.com/puppy/viewtopic.php?p=670074#670074]On Sun 09 Dec 2012[/url], backi wrote:I am using the latest version of Precise .

[url=http://www.murga-linux.com/puppy/viewtopic.php?p=670561#670561]On Tue 11 Dec 2012[/url], backi wrote:grep PUPMODE /etc/rc.d/PUPSTATE
PUPMODE=13

Hi backi,

Although there are a number of reports of the symptoms you are experiencing (text characters turning into little squares when installing a package) from folks running in PUPMODE 2 (full install), this is the first I have seen for PUPMODE 13.

Barry has a fix for users running PUPMODE 2, but it applies only to that mode.

Since many things could cause the text characters to be corrupted, your problem may be something totally unrelated to the problem PUPMODE 2 users ran into. But because it happens during package installation (as was the case for the other problem), it could well be related to the other problem.

That said, I have not yet found anything in the code that would explain what you are seeing in PUPMODE 13.

I have no experience with PUPMODE 13, so may not be able to help with this. But I can suggest a few items of information that you could provide which might help someone else figure this out.

1. The problem experienced by PUPMODE 2 users also caused the desktop icons to change. Did this also happen for you?

2. Do you remember what package you were installing when you ran into this problem?

3. What output do you get for these commands?

Code: Select all

ls -ld /lib/i386-linux-gnu
ls -ld /usr/lib/i386-linux-gnu

(This will tell us if those items are still symbolic links, as they should be, or if the installation of the package changed them to directories or removed them entirely.)

4. What output do you get for this command?

Code: Select all

grep -E "PUP_LAYER|SAVE_LAYER" /etc/rc.d/PUPSTATE

(These variables are used by the installation script, so we need to see if they are set correctly.)

666philb wrote:i compiled the rtl2832u driver for precise puppy, it's needed for various dvb usb devices
http://www.murga-linux.com/puppy/viewto ... h&id=62408

artsown wrote:Ok Barry. Deleted the old .2fs to start fresh. Started Precise 5.4.2
PAE and installed your 5422 upgrade. Did the save file for a fresh
frugal and began doing machine reboots. No black screens in
twenty reboots. Looks good. As I've said, the frequency of black
screens was about 1 in 5 so 20 in a row seems convincing that
you've fixed the problem. It was nice to see a consistent 13
seconds from the last startup screen message to the GUI. Has
the feeling of solidity now.