 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Jim Henderson <nos### [at] nospam com> wrote:
> On Wed, 10 Dec 2008 14:47:12 -0500, clipka wrote:
>
> > Now I notice that the Linux system timer is running WAY TOO FAST, about
> > twice the regular speed. I set the clock at ~19:45; at 20:20 it showed
> > 20:58, and at 20:43 it is showing 21:44 presently.
>
> With or without MegaPOV running?
Both.
To quickly asses how I'm doing regarding this, I set the Gnome clock to display
the time in unix timestamp format, so I can see it counting seconds.
Processor load does not seem to have any influence on this. Time seems to be
flying constantly at 200%.
I toyed around with BIOS settings and boot parameters a bit, only to find out
that "notsc" doesn't help a thing, and disabling the HPET in the BIOS was just
as futile.
Only thing I could find out was that it is in fact multi-processor related, as
"nosmp" gets the counter down to normal speed.
I also found out that Knoppix does fine with default settings. But then again, I
don't know whether it does SMP.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Follow the following steps:
1) Make a bug report to the Debian community.
2) If the bug is not fixed soon, remove Debian and try another distro. Maybe
it's a bug specific to Debian. I myself use OpenSUSE, and it's cool.
(I don't have a quadcore system, though.)
--
- Warp
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Hi !
The first thing to do is to reboot the machine and go in the BIOS.
Then set the clock correctly, save and shutdown the machine.
Wait for couple of minutes (15 - 30 minutes) and turn it on againt.
Go in the BIOS and check the time.
If time as gone twice as when running linux, shutdown the machine,
remove your motherboard and send it back to your resealer.
If not, you'll have to tweak kernel options manually.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Thierry CHARLES <thierry@_no_spam_les-charles.net> wrote:
> The first thing to do is to reboot the machine and go in the BIOS.
> Then set the clock correctly, save and shutdown the machine.
> Wait for couple of minutes (15 - 30 minutes) and turn it on againt.
> Go in the BIOS and check the time.
Hey, I may have no idea how to administer a Linux system, but I do know how to
tell a faulty RTC from an OS getting its own timekeeping wrong...
> If time as gone twice as when running linux, shutdown the machine,
> remove your motherboard and send it back to your resealer.
>
> If not, you'll have to tweak kernel options manually.
That was exactly where I was hoping some Linux Guru who might be experienced
enough to google this problem up in no time flat could go out of his way and
help me: HOW to tweak the damn system, and WHAT to tweak.
I was actually hoping for something more substantial than the usual "RTFM" type
of replies - that someone might be willing to invest maybe 15 minutes to save
me from spending half a day trying to dig up the very same information myself.
Well, I *did* dig it up by myself now, and I'm glad it took me "only" 3 and a
half hours spent on nothing but this single problem...
.... or was it 7 hours? I guess it depends on the frame of reference in this
case...
Anyway, sorry for letting off steam on you. I'm just very, very, *very* upset at
the moment, about how really, really, *really* badly open source stuff tends to
be documented, how many promising internet links lead to nowhere, how
distribution producers leave all the documentation and support to "the
community", and a lot more.
The solution? Just add a bloody "no_timer_check" at the right place in the right
file (actually it's the kernel boot options in the Grub boot loader settings, as
I have learned today). Documentation? Well, seems to be one of those occult
secrets circulated in "the community".
So I don't know what exactly that thing might do, and how it could possibly
wreck my system as a side effect - but at least the clock seems to run properly
now...
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Wed, 10 Dec 2008 16:33:39 -0500, clipka wrote:
> Both.
Then it's unlikely to be a POV-Ray or MegaPOV issue - so definitely I'd
suggest talking to some Linux kernel folks - you're likely to find much
more in-depth knowledge in that community.
Jim
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Wed, 10 Dec 2008 23:05:20 +0100, Thierry CHARLES wrote:
> If not, you'll have to tweak kernel options manually.
This *should* be unnecessary, though.
Jim
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
.... "top" now prints meaningful stats for the processes now, too (although it
gives CPU usage in % of a single core, not the whole CPU as the Gnome System
Monitor does).
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Wed, 10 Dec 2008 17:44:59 -0500, clipka wrote:
> That was exactly where I was hoping some Linux Guru who might be
> experienced enough to google this problem up in no time flat could go
> out of his way and help me: HOW to tweak the damn system, and WHAT to
> tweak.
I don't know that it takes a Linux guru, but here you go:
http://letmegooglethatforyou.com/?q=debian+clock+runs+fast
Try the third result, looked promising to me. :-)
Jim
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Wed, 10 Dec 2008 17:44:59 -0500, clipka wrote:
> I was actually hoping for something more substantial than the usual
> "RTFM" type of replies - that someone might be willing to invest maybe
> 15 minutes to save me from spending half a day trying to dig up the very
> same information myself.
And seeing that you got an answer, that's great - maybe you need to read
esr's article on how to ask smart questions? ( http://www.catb.org/~esr/
faqs/smart-questions.html )
I can understand your frustration and whatnot, but picking the proper
community to ask is often the first step in asking a good question. I
personally would tend to eliminate the factors I could (as I attempted to
do by asking if it seemed to be a MegaPOV problem or a kernel problem by
eliminating MegaPOV from the picture - something that wasn't clear to me
in your initial post).
As a reader of these forums and not recognizing your name, I (and Warp,
and Thierry, and anyone else reading here) have no idea what your level
of experience is with computers. We have to assume you know only what
you've told us.
Then asking us to do the work for you - well, what's our motivation
here? It took me 10 seconds to google your question (see my prior
response), and the first non-PDF response suggests a boot parameter that
probably would also solve the problem for you.
Seriously, have a look at Eric Raymond's essay on asking intelligent
questions. It's something anyone who works with computers and uses
online communities should understand. I distilled your question to "I
run Debian; my clock runs fast. How do I fix it?", googled "debian clock
runs fast" and got a result.
One of esr's points in his essay on asking intelligent questions is to
distill the problem to the simplest form and ask your question - don't
guess at the answer. He's got an excellent example of a bad question and
how it can be rewritten as a good question that will get you help.
Please *please* note that I'm not trying to attack you - I'm trying to
help you help yourself so you don't take so much time to get a problem
resolved.
Jim
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Jim Henderson <nos### [at] nospamcom> wrote:
> Then asking us to do the work for you - well, what's our motivation
> here?
Maybe nothing more than just helping others...?
> It took me 10 seconds to google your question (see my prior
> response), and the first non-PDF response suggests a boot parameter that
> probably would also solve the problem for you.
Notice something? Took me 3 hours 30 to google that bloody thing - not even
counting my *FIRST* attempt at it, which was probably somewhere between 30
minutes and an hour.
That's *THOUSAND* times the 10 seconds that you say it took *YOU*.
GEEZ! I *DID* search for that f*** sh** like "Debian clock fast", I'm telling
you! But me being primarily a Windows Jockey, I had *NO* idea whatsoever what
to keep my eyes peeled for! I didn't even *KNOW* there is something like boot
parameters; the seemingly more common term "kernel parameters" sounded to me
rather like "recompile your kernel" - which is *NOT* something I would have
wanted to do without anyone guiding me through that.
So, how do you imagine I should have recognized that the first non-PDF response
could possibly be just the thing I was looking for - in some freakin' 10
seconds? And how could I have possibly learned in those 10 seconds how to
actually *implement* a solution from the information in that PDF???
> One of esr's points in his essay on asking intelligent questions is to
> distill the problem to the simplest form and ask your question - don't
> guess at the answer. He's got an excellent example of a bad question and
> how it can be rewritten as a good question that will get you help.
Asking intelligent questions requires at least *SOME* knowledge about the thing
you're having problems with.
So here I am, having already googled for loads of different combinations of
"Linux", "Debian", "clock", "time", "fast" and whatever you can possibly
imagine, without finding anything *I* could comprehend, let alone actually put
to use - so how else should I have put it?
> Please *please* note that I'm not trying to attack you - I'm trying to
> help you help yourself so you don't take so much time to get a problem
> resolved.
Man, that's crap! This "hey, I can google it up in 10 seconds so please don't
pester me with that and instead read that f*** essay and go find out yourself
you lazy bum" - attitude is real bullshit. If you *can* google it up in 10
seconds, why don't you invest that time to help me, instead of wasting it by
writing a reply that's no help at all???
You know what? Technology didn't advance by everyone learning to do everything.
It advanced by people specializing on different things. Means that people
concentrate on things they're good at, and don't waste time on things others
can do with significantly less effort. Doesn't seem to have reached the "RTFM!"
advocates though.
I have no intention of becoming a Linux Guru myself, so why don't you just stop
trying to teach me to become one, and instead just go ahead and help me solve
my problem?!
(Well, it's a rethorical question, no need solving it anymore. Clock seems to be
running fine now.)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
|
|
