Emergency help:
-p Automatic repair (no questions)
-n Make no changes to the filesystem
-y Assume "yes" to all questions
-c Check for bad blocks and add them to the badblock list
-f Force checking even if filesystem is marked clean
-v Be verbose-b superblock Use alternative superblock

Unless I had made some mistake (which I suspect I haven't), Puppy saw that there was another Puppy nearby and mixed things. In the partition in which the folders are located the are an opera and profile folders that were created when I installed Opera in Puppy 4.3. Maybe this confounded the boot process.

If you have been using a previous frugal install and decided to use a 4.3.1 live CD then I expect it would see the older savefile and ask did you wish to upgrade it to 4.3.1.

If you had puppy software on the HDD but outside the savefile then that software is accessible by any puppy. It may be advantageous to install additional browsers this way, so that you need to install only once and it can be used by your other puppies.

Hello,
When transparency enabled (/root/.xinitrc => #composite & transparency kcompmgr -n &), Xlock doesn't show both screen saver picture and text that prompts user to give the password. However I noticed this problem disappears if the option -grabserver is deleted in /usr/local/apps/Xlock/AppRunn lines n°34 et n°143 and in /.config/Xlock/xlockscreenparams...
My question: what is the option -grabserver used for and what kind of other problem(s) may this modification possibly cause?

I guess this may be a silly thing to write a bug report about, but it bugs me, so here it is..

The clock is reset each time I boot puppy 4.3.1 from my save file. I don't boot often from RAM, and I am not about to get this puppy running the way I want it to all over again just to fix the time.

I go to Menu > Desktop, Set Time Zone > Set to GMT +1 > OK -- time is still off. If I set it by going Menu > Desktop > Set time and date -- the clock only gives the correct time for that session, untill I power off/reboot.

Well, I gave it some time, and it seems to be completely random, no matter which method I use. Sometimes she will give the right time for a few days, and then it keeps setting it back to 5:30 AM for the next few days.

How is the clock updated, does it use a clock in my hardware or from the internet, or..? Maybe it's not puppy's fault but my computer?

Edit: Actually I gave up constantly resetting the time, but I just tried again, and no matter whether I use the GMT or the Country method, it doesn't change the time. Only using 'Set time and date' it will, but for this session only..

I forgot to mention I upgraded my 4.3.1 using rerwin's upgrade. I can't recall if the clock did do it's job properly before upgrading.

look for rtc-cmos,rtc_core,rtc_lib drivers are loaded using `lsmod | grep rtc` , put them into `bootmanager` if not ( I'll have to do this , too ) .
of course , check battery .
you could try something like

Time should be GMT +1
Clock is reset to 19:06 even though it was displaying the correct time(I told puppy what the right time was last time I posted, maybe that is why it shows. I'm too hungover to read a man page on a clock I'm afraid.

Can't seem to paste from rxvt selecting and pasting with middle mouse button, so here's an screenshot.

Changing the hwclock time didn't change the time on my desktop BTW.

Why 'so many seconds since 1969'? Is 1969 the year of the first HW clock?

I am running the 2.6.31.14 IDE kernel today and it is the same about "rtc"

And this is from the kernel source documentation rtc.txt :

Quote:

All PCs (even Alpha machines) have a Real Time Clock built into them.
Usually they are built into the chipset of the computer, but some may
actually have a Motorola MC146818 (or clone) on the board. This is the
clock that keeps the date and time while your computer is turned off.

ACPI has standardized that MC146818 functionality, and extended it in
a few ways (enabling longer alarm periods, and wake-from-hibernate).
That functionality is NOT exposed in the old driver.

However it can also be used to generate signals from a slow 2Hz to a
relatively fast 8192Hz, in increments of powers of two. These signals
are reported by interrupt number 8. (Oh! So *that* is what IRQ 8 is
for...) It can also function as a 24hr alarm, raising IRQ 8 when the
alarm goes off. The alarm can also be programmed to only check any
subset of the three programmable values, meaning that it could be set to
ring on the 30th second of the 30th minute of every hour, for example.
The clock can also be set to generate an interrupt upon every clock
update, thus generating a 1Hz signal.

The interrupts are reported via /dev/rtc (major 10, minor 135, read only
character device) in the form of an unsigned long. The low byte contains
the type of interrupt (update-done, alarm-rang, or periodic) that was
raised, and the remaining bytes contain the number of interrupts since
the last read. Status information is reported through the pseudo-file
/proc/driver/rtc if the /proc filesystem was enabled. The driver has
built in locking so that only one process is allowed to have the /dev/rtc
interface open at a time.

For the +-1 GMT confusion there is written some in the 5series projects threads also ; but /usr/sbin/timezone-set contains code to try to translate '-' to '+' and reverse for GMT but maybe grep sometimes likes +- escaped and sometimes not or there is missing a !not in the if-statement .

Ok, well, thanks. I tried those things, aside from the coding you posted at the end, here's the output again in a screenshot.

Another thing I did was follow the help in psync, which reads

Quote:

FIRST:
If you have not already done so via Menu/Desktop/Set Timezone, then you must first set your Timezone geographically.
i.e Europe/London - Europe/Madrid etc to match your nearest location. Scroll through the Puppy menu Timezone list to set it to nearest location.
NOT by GMT offset. This is because the built in commands use the locale settings.
You must now reboot to make the setting active. This is before running Psync
Locale zoneinfo contains information on offset plus DST etc. (Daylight Savings Time) allowing Psync to set time correctly according to your location.
Setting the timezone this way also allows the desktop clock to auto change for DST.
GMT file is just a numerical offset etc. which means Psync may ignore it and set your clock according to server location. Which may be set to UTC and cause your clock to be set up to 2 hours off.

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