Same Procedure Every Few Month, Any Plans >r121

[Martin]

Hi ...

I'm thinking about my c860 ...

is there a new release after r121 in near future (maybe end nov. or december 2006) ...

I have problems on r121 with ....
- ethernet over usbd
- getting my wlan card to work ...
- console trouble after exit x
- date / time setting after reboot
many described in forum before (some with solutions) but after reinstall (reflash) or reboot  I have to do many manual work again ...

Thanks to Sazh and all other developers, testers for their great work
Martin

[svs57]

About date & time after reboot
Two scripts:
/usr/sbin/savedate
#!/bin/sh
date +%m%d%H%M%y > /etc/sysconfig/date

/usr/sbin/restoredate
date `cat /etc/sysconfig/date`

[InSearchOf]

Sash has been pretty busy with his real job... and I'm working on getting all the bug fixes implemented into the next release and making a lot of changes to the "Settings Apps"... and this may take a little bit...

but, it defiently wont be end of November... because today is the last day of Nov. :-)

But hopefully soon...

Late

[InSearchOf]

About date & time after reboot
Two scripts:
/usr/sbin/savedate
#!/bin/sh
date +%m%d%H%M%y > /etc/sysconfig/date

/usr/sbin/restoredate
date `cat /etc/sysconfig/date`
[div align=\"right\"][a href=\"index.php?act=findpost&pid=147582\"][{POST_SNAPBACK}][/a][/div]

That will be fixed in the next release...

It is due to the cxxx series rom not having "hwclock" not on it...
There is a script that runs at shutdown that syncs the realtime clock to hardware clock and vice versa at boot... :-)

Late

[ZDevil]

About date & time after reboot
Two scripts:
/usr/sbin/savedate
#!/bin/sh
date +%m%d%H%M%y > /etc/sysconfig/date

/usr/sbin/restoredate
date `cat /etc/sysconfig/date`
[div align=\"right\"][a href=\"index.php?act=findpost&pid=147582\"][{POST_SNAPBACK}][/a][/div]

That will be fixed in the next release...

It is due to the cxxx series rom not having "hwclock" not on it...
There is a script that runs at shutdown that syncs the realtime clock to hardware clock and vice versa at boot... :-)

Late
[div align=\"right\"][a href=\"index.php?act=findpost&pid=147587\"][{POST_SNAPBACK}][/a][/div]

Actually my C1000 suffers from exactly the same thing after flashing Beta3 for a while. After suspend, not even reboot, the clock will revert back to a far earlier time (looks like the time of flashing, but i can't verify here).
Already read the posts here but the problem remained unresolved.
Tried sethwclock & hwclock (with --debug and --systoch) and sltime -set after date --set, but the problem persists. A not-so-big bug, but rather annoying.
So In Search Of can you give me the pointer to the script you mention?
Thanks!

[InSearchOf]

Actually my C1000 suffers from exactly the same thing after flashing Beta3 for a while. After suspend, not even reboot, the clock will revert back to a far earlier time (looks like the time of flashing, but i can't verify here).
Already read the posts here but the problem remained unresolved.
Tried sethwclock & hwclock (with --debug and --systoch) and sltime -set after date --set, but the problem persists. A not-so-big bug, but rather annoying.
So In Search Of can you give me the pointer to the script you mention?
Thanks!
[div align=\"right\"][a href=\"index.php?act=findpost&pid=147591\"][{POST_SNAPBACK}][/a][/div]

I was actually referring to rc121... but I will check on that for you... I may take a little because currently I'm running rc121 doing beta testing and debugging...

Late

[ZDevil]

Thanks a lot!

Just a sidenote: this has never happened to my C860 running Beta1.

And let me reproduce the outputs here:

Code: [Select]

# sethwclock
Cannot access the Hardware Clock via any known method.
Use the --debug option to see the details of our search for an access method.
# sethwclock --systohc
Cannot access the Hardware Clock via any known method.
Use the --debug option to see the details of our search for an access method.
# sethwclock --debug
Cannot access the Hardware Clock via any known method.
Use the --debug option to see the details of our search for an access method.
# hwclock
Cannot access the Hardware Clock via any known method.
Use the --debug option to see the details of our search for an access method.
# hwclock --systohc
Cannot access the Hardware Clock via any known method.
Use the --debug option to see the details of our search for an access method.
# hwclock --debug
hwclock from util-linux-2.12j
hwclock: Open of /dev/rtc failed, error=16: Device or resource busy.
No usable clock interface found.
Cannot access the Hardware Clock via any known method.
I forgot since when, but I also began to see the same error message upon exiting X.  

[InSearchOf]

I will load beta3 back on my Z tonight and look at this...  (I'm at work... but I can ssh into my Z...)

Late

[InSearchOf]

ZDevil... try this

Do a

Code: [Select]

hwclock --directisa
This will bypass /dev/rtc

Let me know what you get...

LAte

[ZDevil]

In Search Of:

Same story:  

Code: [Select]

# hwclock --directisa
Cannot access the Hardware Clock via any known method.
Use the --debug option to see the details of our search for an access method.
But thanks anyway.

[InSearchOf]

ok... sorry that was a wasted command... only works on ALPHA and ISA hardware :-)...

I will look into it tonight

[karlto]

In Search Of:

Same story: 

Code: [Select]

# hwclock --directisa
Cannot access the Hardware Clock via any known method.
Use the --debug option to see the details of our search for an access method.
But thanks anyway.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=147596\"][{POST_SNAPBACK}][/a][/div]

Are you sure the clock isn't locked/in use by something like atd?

[InSearchOf]

Ohh and sorry Martin for hi-jacking your thread :-(

Please post your problems at
https://www.oesf.org/forums/index.php?showtopic=22119&hl=

So we can have to documented as bugs that need fixed.

Late

[ZDevil]

In Search Of:

Same story: 

Code: [Select]

# hwclock --directisa
Cannot access the Hardware Clock via any known method.
Use the --debug option to see the details of our search for an access method.
But thanks anyway.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=147596\"][{POST_SNAPBACK}][/a][/div]

Are you sure the clock isn't locked/in use by something like atd?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=147619\"][{POST_SNAPBACK}][/a][/div]

You are right!! I forgot I installed atd in order to get the alarm working for KO/Pi.
Uninstalling atd sethwclock works again.
So how does atd cause such as problem?
Is there a way to resolve the conflict between atd and the system clock?
If not, then I will have to give up using KO/Pi...

[karlto]

You are right!! I forgot I installed atd in order to get the alarm working for KO/Pi.
Uninstalling atd sethwclock works again.
So how does atd cause such as problem?
Is there a way to resolve the conflict between atd and the system clock?
If not, then I will have to give up using KO/Pi...
[div align=\"right\"][a href=\"index.php?act=findpost&pid=147628\"][{POST_SNAPBACK}][/a][/div]

You don't need to uninstall atd (or give up ko/pi) - just stop the service ('/etc/rc.d/init.d/atd stop') before running sethwclock, then start it ('/etc/rc.d/init.d/atd start') again after. You probably want to add this to the scripts that run sltime, sethwclock etc.

atd locks the clock because it is constantly using it - stopping it for a second to access the clock and starting it again shouldn't be a hassle.