One amusing difference I've noticed in Tech-Savvy and non-Tech-Savvy computer users:
The newbie, when having diffucluties completing a task, says "I can't figure out how to do what I need to."
The geek, when having similar problems, says, "This program sucks. Its designer should be shot. It should do this, this, and this. It shouldn't be this hard to do this simple a task."
If you know how the technology behind the system works, you can easily find its flaws. If you don't, you're left feeling like the idiot when, very likely, you shouldn't be.
Already done. I've got it set to update the time on startup and at some point during the night. However, when I boot to other OSes, I have to reboot, enter BIOS, reset the time, save/exit/reboot. It's just a bit of tedium I'd rather do without.
In response to the other comments:
"What makes you think its a USB issue?" -- I'm not sure it is... but about the time I started using USB features to link w/ my Visor is when I noticed the problem.
"How do you know its not happening on startup?" -- If I disable my auto-ntpdate, set the BIOS time, and boot into Linux, it keeps the date just fine. I can read the software and hardware clocks, and they're both correct. However, after a reboot from Linux, I can hit [del] and check the BIOS clock (or allow it to boot into any OS) and it's back at 1998.
"When you shutdown you might want to make it set the hardware clock from the system clock." -- This seems redundant. I can check the hardware clock before shutdown, and it's fine. After reboot, it's not.
Info I probably should've given in my first post (duh):
Slackware 7.1
Kernel 2.4.5 (now) (No, didn't fix the problem.)
AMD K6-III
128M RAM. Though, I don't really think that's relevant.
I guess I can answer my own question by compiling and installing the new kernel, but I also wanted to know if anyone else has experienced the same thing:
Ever since the kernel has supported USB (I used the backport to 2.2.something too) I've had a problem with my system clock. When I reboot from Linux, the hardware clock goes back to 1998.
No, it's not the battery. I can reboot from Other OSes (Win9x/2k, BeOS) without resetting the clock. I've checked all of my shutdown scripts, and find nothing accessing the clock at all. All this leads me to think it's a kernel problem, and no one has been able to figure otherwise.
Slashdot Mirror
... When can I get one?
One amusing difference I've noticed in Tech-Savvy and non-Tech-Savvy computer users:
The newbie, when having diffucluties completing a task, says "I can't figure out how to do what I need to."
The geek, when having similar problems, says, "This program sucks. Its designer should be shot. It should do this, this, and this. It shouldn't be this hard to do this simple a task."
If you know how the technology behind the system works, you can easily find its flaws. If you don't, you're left feeling like the idiot when, very likely, you shouldn't be.
In response to the other comments:
"What makes you think its a USB issue?" -- I'm not sure it is... but about the time I started using USB features to link w/ my Visor is when I noticed the problem.
"How do you know its not happening on startup?" -- If I disable my auto-ntpdate, set the BIOS time, and boot into Linux, it keeps the date just fine. I can read the software and hardware clocks, and they're both correct. However, after a reboot from Linux, I can hit [del] and check the BIOS clock (or allow it to boot into any OS) and it's back at 1998.
"When you shutdown you might want to make it set the hardware clock from the system clock." -- This seems redundant. I can check the hardware clock before shutdown, and it's fine. After reboot, it's not.
Info I probably should've given in my first post (duh):
Slackware 7.1
Kernel 2.4.5 (now) (No, didn't fix the problem.)
AMD K6-III
128M RAM. Though, I don't really think that's relevant.
Thanks for the suggestions!
Ever since the kernel has supported USB (I used the backport to 2.2.something too) I've had a problem with my system clock. When I reboot from Linux, the hardware clock goes back to 1998.
No, it's not the battery. I can reboot from Other OSes (Win9x/2k, BeOS) without resetting the clock. I've checked all of my shutdown scripts, and find nothing accessing the clock at all. All this leads me to think it's a kernel problem, and no one has been able to figure otherwise.
So, when is someone (ThinkGeek, are you reading?) going to start printing this on t-shirts? That's some graffiti I wouldn't mind wearing. :)