'hwclock' not working? (ASU)
Hello, I'm running ASU on my FR. It seems that something is broken or missing for the 'hwclock' command to work: [EMAIL PROTECTED]:~# uname -a Linux om-gta02 2.6.24 #1 PREEMPT Wed Jul 23 08:50:28 CST 2008 armv4tl unknown [EMAIL PROTECTED]:~# [EMAIL PROTECTED]:~# hwclock --systohc hwclock: can't open '/dev/misc/rtc': No such file or directory [EMAIL PROTECTED]:~# hwclock -s hwclock: can't open '/dev/misc/rtc': No such file or directory [EMAIL PROTECTED]:~# hwclock --help BusyBox v1.11.1 (2008-07-18 00:49:01 CEST) multi-call binary Usage: hwclock [-r|--show] [-s|--hctosys] [-w|--systohc] [-l|--localtime] [-u|--utc] [-f FILE] -- Regards, Torfinn ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: 'hwclock' not working? (ASU)
Torfinn Ingolfsen wrote: > Hello, > > I'm running ASU on my FR. > > It seems that something is broken or missing for the 'hwclock' command to > work: > > [EMAIL PROTECTED]:~# uname -a > Linux om-gta02 2.6.24 #1 PREEMPT Wed Jul 23 08:50:28 CST 2008 armv4tl unknown > [EMAIL PROTECTED]:~# > [EMAIL PROTECTED]:~# hwclock --systohc > hwclock: can't open '/dev/misc/rtc': No such file or directory > [EMAIL PROTECTED]:~# hwclock -s > hwclock: can't open '/dev/misc/rtc': No such file or directory > [EMAIL PROTECTED]:~# hwclock --help > BusyBox v1.11.1 (2008-07-18 00:49:01 CEST) multi-call binary > > Usage: hwclock [-r|--show] [-s|--hctosys] [-w|--systohc] > [-l|--localtime] [-u|--utc] [-f FILE] quick fix is to run mkdir /dev/misc ln -s /dev/rtc /dev/misc/rtc -- Lorn 'ljp' Potter Software Engineer, Systems Group, Trolltech, a Nokia company ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: 'hwclock' not working? (ASU)
On Sat, 2008-07-26 at 22:56 +1000, Lorn Potter wrote: > Torfinn Ingolfsen wrote: > > I'm running ASU on my FR. > > > > It seems that something is broken or missing for the 'hwclock' command to > > work: > > > > [EMAIL PROTECTED]:~# hwclock --systohc > > hwclock: can't open '/dev/misc/rtc': No such file or directory > quick fix is to run > mkdir /dev/misc > ln -s /dev/rtc /dev/misc/rtc I ran into the same issue. After running the above link, I also had to stop the atd daemon which had /dev/rtc0 open: # opkg install lsof # lsof | grep rtc atd 1334 root3r CHR 254,0 1304 /dev/rtc0 # /etc/init.d/atd stop # /etc/init.d/atd stop Stopping at daemon: atd. # hwclock --systohc # /etc/init.d/atd start Starting at daemon: atd. ...cj ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: 'hwclock' not working? (ASU)
On Saturday 26 July 2008 20:55:15 Christopher White wrote: > I ran into the same issue. After running the above link, I also had to > stop the atd daemon which had /dev/rtc0 open: > > # opkg install lsof > # lsof | grep rtc > atd 1334 root3r CHR 254,0 > 1304 /dev/rtc0 > # /etc/init.d/atd stop > # /etc/init.d/atd stop > Stopping at daemon: atd. > # hwclock --systohc > # /etc/init.d/atd start > Starting at daemon: atd. We run atd on the ASU image on purpose. It allows to schedule any kind of alarms and will program the RTC for wakeup automatically. If you want atd to write the current time into the rtc then you have to write "W\n" into /var/spool/at/trigger. But on the other hand we provide a GUI application to set the Timezone and the Time and they work :) z. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: 'hwclock' not working? (ASU)
On Sat, 2008-07-26 at 22:33 +0200, Holger Freyther wrote: > On Saturday 26 July 2008 20:55:15 Christopher White wrote: > > > I ran into the same issue. After running the above link, I also had to > > stop the atd daemon which had /dev/rtc0 open: > We run atd on the ASU image on purpose. It allows to schedule any kind of > alarms and will program the RTC for wakeup automatically. If you want atd to > write the current time into the rtc then you have to write "W\n" > into /var/spool/at/trigger. > > But on the other hand we provide a GUI application to set the Timezone and > the > Time and they work :) Well...I was baffled by setting the time from this. I modified the hour, clicked "Back" and it skipped forward several hours. Went back and forth trying to figure out what I was missing. I suspect it was because I had changed the Timezone but not rebooted yet so I was in the limbo of /etc/localtime saying EDT, but date still reporting UTC. It now seems to work correctly, but this might need to be looked at. Next time I reflash, I'll try it again and see if I can't better figure out the issue. ...cj ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: 'hwclock' not working? (ASU)
Hello, On Sat, Jul 26, 2008 at 10:33 PM, Holger Freyther <[EMAIL PROTECTED]> wrote: > write the current time into the rtc then you have to write "W\n" > into /var/spool/at/trigger. Like this: echo "W\n" > /var/spool/at/trigger Or is th '\n' not needed in that case? I have already updated the wiki, and will fix the command example if needed. > But on the other hand we provide a GUI application to set the Timezone and the > Time and they work :) As someone else in this thread mentioned, there are issues with that application. When I tried to use it, it looked like it couldn't set the time correctly - I set correct timezone and input local time, but fter setting time, it was at utc instead of local time. And sometimes the years changed in odd ways. -- Regards, Torfinn ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
