javaJake
Jacob Godserv
This is a duplicate thread from the gp32x version here: http://www.gp32x.de/board/index.php?/topic/56596-clock-change/
Hey, I just realized why I've been having a terrible time getting wifi to work. It was the clock. (I think.)
Anyways, it's good for you guys to know, because it messed up a number of random systems in Gentoo. Gentoo was told to read and write the clock in Local time to match older revisions of the official firmware. What I didn't realize was the latest firmware adjusts so now it saves as UTC. Somehow, when Gentoo booted, ntp would try to fix the clock, or something would happen related to the clock (don't really know), and the end result is I was getting dbus-not-replying errors, wireless firmware errors, and a whole other range of lockups and strange, random things.
So, if anyone else is developing an OS for the Pandora, if you have the clock saving as Local time, adjust to UTC!
Everything is working now that I've switched to UTC.
Hey, I just realized why I've been having a terrible time getting wifi to work. It was the clock. (I think.)
Anyways, it's good for you guys to know, because it messed up a number of random systems in Gentoo. Gentoo was told to read and write the clock in Local time to match older revisions of the official firmware. What I didn't realize was the latest firmware adjusts so now it saves as UTC. Somehow, when Gentoo booted, ntp would try to fix the clock, or something would happen related to the clock (don't really know), and the end result is I was getting dbus-not-replying errors, wireless firmware errors, and a whole other range of lockups and strange, random things.
So, if anyone else is developing an OS for the Pandora, if you have the clock saving as Local time, adjust to UTC!
Everything is working now that I've switched to UTC.
Last edited by a moderator:
