SamyGO

Samsung TV Firmware on the GO
http://forum.samygo.tv/

[SOLVED] Set Date/Time: Bad address

http://forum.samygo.tv/viewtopic.php?t=3975

Page 3 of 4

Re: Set Date/Time: Bad address

Posted: Sun May 13, 2012 7:31 am
by juusso
Just recompilled latest available ntpclient (ntpclient_2010_365.tar.gz). Grab here (webif module).

btw, we always can use built in busybox rdate script

Code: Select all

SERVER="193.110.137.171"
busybox rdate -s $SERVER
EDIT: to set time zone, we just need to export TZ environment variable.

Code: Select all

#date
Sun May 13 06:31:07 2012
#export TZ='EET-2EEST-3,M3.5.0/3,M10.5.0/4'
#date
Sun May 13 08:36:49 EEST 2012
List of TZ database timezones:

Code: Select all

TZ Subregion: GB-Eire
Existing Rule: GB-Eire GMT0BST-1,M3.5.0/1,M10.5.0/1
Changed Rule: (US DST Extension): GMT0BST-1,M3.5.0/1,M10.5.0/2

TZ Subregion: WET
Existing Rule: WET0WET_DST-1,M3.5.0/1,M9.5.0/1
Changed Rule: WET0WEST-1,M3.5.0/1,M10.5.0/2

TZ Subregion: Iceland
WET0
GMT0

TZ Subregion: MET
Existing Rule: MET-1MET_DST-2,M3.5.0/2,M10.5.0/3
Changed Rule: MET-1MEST-2,M3.5.0/2,M10.5.0/3

TZ Subregion: Poland
Existing Rule: MET-1MET_DST-2,M3.5.0/1,M9.5.0/1
Changed Rule: CET-1CEST-2,M3.5.0/1,M10.5.0/2

TZ Subregion: EET
Existing Rule: EET-2EET_DST-3,M3.5.0/3,M10.5.0/4
Changed Rule: EET-2EEST-3,M3.5.0/3,M10.5.0/4

TZ Subregion: Turkey
Existing Rule: EET-3EET_DST-4,M3.5.0/1,M9.5.0/1
Changed Rule: EET-2EEST-3,M3.5.0/3,M10.5.0/4

TZ Subregion: US/Eastern
Existing Rule: EST5EDT4,M4.1.0/2,M10.5.0/2
Changed Rule: EST5EDT4,M3.2.0/02,M11.1.0/02

TZ Subregion: US/East-Indiana
Existing Rule: EST5
Changed Rule: EST5EDT4,M3.2.0/02,M11.1.0/02

TZ Subregion: US/Central
Existing Rule: CST6CDT5,M4.1.0/2,M10.5.0/2
Changed Rule: CST6CDT5,M3.2.0/02,M11.1.0/02

TZ Subregion: US/Mountain
Existing Rule: MST7MDT6,M4.1.0/2,M10.5.0/2
Changed Rule: MST7MDT6,M3.2.0/02,M11.1.0/02

TZ Subregion: US/Pacific
Existing Rule: PST8PDT7,M4.1.0/2,M10.5.0/2
Changed Rule: PST8PDT7,M3.2.0/02,M11.1.0/02

TZ Subregion: US/Alaska
Existing Rule: AKST9AKDT8,M4.1.0/2,M10.5.0/2
Changed Rule: AKST9AKDT8,M3.2.0/02,M11.1.0/02

TZ Subregion: US/Navajo
Existing Rule: MST7MDT6,M4.1.0/2,M10.5.0/2
Changed Rule: MST7MDT6,M3.2.0/02,M11.1.0/02

TZ Subregion: US/Michigan
Existing Rule: EST5EDT4,M4.1.0/2,M10.5.0/2
Changed Rule: EST5EDT4,M3.2.0/02,M11.1.0/02

TZ Subregion: US/Aleutian
Existing Rule: HAST10HAST9,M4.1.0/2,M10.5.0/2
Changed Rule: HAST10HADT9,M3.2.0/02,M11.1.0/02

TZ Subregion: Canada/Newfoundland
Existing Rule: NST3:30NDT2:30,M4.1.0/2,M10.5.0/2
Changed Rule: NST3:30NDT2:30,M3.2.0/0:01,M11.1.0/0:01

TZ Subregion: Canada/Atlantic
Existing Rule: AST4ADT3,M4.1.0/2,M10.5.0/2
Changed Rule: AST4ADT3,M3.2.0/2,M11.1.0/2

TZ Subregion: Canada/Eastern
Existing Rule: EST5EDT4,M4.1.0/2,M10.5.0/2
Changed Rule: EST5EDT4,M3.2.0/2,M11.1.0/2

TZ Subregion: Canada/Central
Existing Rule: CST6CDT5,M4.1.0/2,M10.5.0/2
Changed Rule: CST6CDT5,M3.2.0/2,M11.1.0/2

TZ Subregion: Canada/Mountain
Existing Rule: MST7MDT6,M4.1.0/2,M10.5.0/2
Changed Rule: MST7MDT6,M3.2.0/2,M11.1.0/2

TZ Subregion: Canada/Pacific
Existing Rule: PST8PDT7,M4.1.0/2,M10.5.0/2
Changed Rule: PST8PDT7,M3.2.0/2,M11.1.0/2

TZ Subregion: Canada/Yukon
Existing Rule: YST9YDT8,M4.1.0/2,M10.5.0/2
Changed Rule: PST8PDT7,M3.2.0/2,M11.1.0/2

TZ Subregion: Mexico/BajaSur
Existing Rule: MST7
Changed Rule: MST7MDT6,M4.1.0/2,M10.5.0/2

TZ Subregion: Mexico/General
Existing Rule: CST6
Changed Rule: CST6MDT5,M4.1.0/2,M10.5.0/2

TZ Subregion: Cuba
Existing Rule: CST5CDT4,M5.2.0/0,M10.2.0/0
Changed Rule: CST5CDT4,M4.1.0/0,M10.5.0/1

TZ Subregion: Jamaica
Existing Rule: EST5EDT4,M4.1.0/2,M10.5.0/2
Changed Rule: EST5

TZ Subregion: Brazil/East
Existing Rule: EST3EDT2,M10.2.0/2,M2.3.0/2
Changed Rule: BRT3BTST2,M10.3.0/0,M2.3.0/0

TZ Subregion: Brazil/West
Existing Rule: WST4WDT3,M10.4.6/2,M2.2.6/2
Changed Rule: AMT4

TZ Subregion: Brazil/Acre
Existing Rule: AST5ADT4,M10.4.6/2,M2.2.6/2
Changed Rule: ACT5

TZ Subregion: Brazil/DeNoronha
Existing Rule: FST2FDT1,M10.4.6/2,M2.2.6/2
Changed Rule: FNT2

TZ Subregion: Chile/Continental
Existing Rule: CST4CDT3,M10.2.0/0,M3.2.0/0
Changed Rule: CLT4CLST3,M10.2.0/0,M3.2.0/0

TZ Subregion: Chile/Easter Island
Existing Rule: EST6EDT5,M10.2.0/0,M3.2.0/0
Changed Rule: EAST6EASST5,M10.2.0/0,M3.2.0/0

TZ Subregion: Egypt
Existing Rule: EET-2EET_DST-3,J152/2,J305/2
Changed Rule: EET-2EEST-3,M4.5.5/0,M9.5.4/24

TZ Subregion: Libya
Existing Rule: EET-2EET_DST-3,J121/2,J303/2
Changed Rule: EET-2

TZ Subregion: PRC
Existing Rule: CST-8CDT-9,M4.2.0/2,M9.2.0/3
Changed Rule: CST-8

TZ Subregion: ROK
Existing Rule: KST-9KDT-10,M5.2.0/2,M10.2.0/3
Changed Rule: KST-9

TZ Subregion: Israel
Existing Rule: IST-2IDT-3,M4.3.0/2,M8.4.6/2
Changed Rule: IST-2IDT-3,M3.5.5/2,M9.3.0/2

TZ Subregion: Iran
Existing Rule: IST-3:30IDT-4:30,M3.5.0/2,M9.3.0/2
Changed Rule: IRST-3:30

TZ Subregion: Singapore
Existing Rule: SST-8
Changed Rule: SGT-8

TZ Subregion: Australia/YANCOWINNA
Existing Rule: EST-9:30EST-10:30,M10.5.0/2,M3.5.0/3
Changed Rule: CST-9:30CST-10:30,M10.5.0/2,M3.5.0/3
EDIT2: or just experiment with:

Code: Select all

export TZ='GMT-3'
@arris, perhaps TZ must be global variable set from SGO.env or profile? Because ftp time doesn`t react to TZ value.

topic changed to SOLVED ;)

Re: [SOLVED] Set Date/Time: Bad address

Posted: Thu May 02, 2013 5:51 am
by nobody
busybox date and rdate don't work for me. Bad address. But I wonder why and how to correct it in busybox.

Code: Select all

$ ntpd -n -d -p time.ien.it
ntpd: sending query to 193.204.114.105
ntpd: reply from 193.204.114.105: offset:+1367467563.324029 delay:0.022805 statu
s:0x24 strat:1 refid:0x00445443 rootdelay:0.000000 reach:0x01
ntpd: sending query to 193.204.114.105
ntpd: reply from 193.204.114.105: offset:+1367467563.322088 delay:0.018538 statu
s:0x24 strat:1 refid:0x00445443 rootdelay:0.000000 reach:0x03
ntpd: sending query to 193.204.114.105
ntpd: reply from 193.204.114.105: offset:+1367467563.321997 delay:0.018745 statu
s:0x24 strat:1 refid:0x00445443 rootdelay:0.000000 reach:0x07
ntpd: sending query to 193.204.114.105
ntpd: reply from 193.204.114.105: offset:+1367467563.322042 delay:0.018755 statu
s:0x24 strat:1 refid:0x00445443 rootdelay:0.000000 reach:0x0f
ntpd: sending query to 193.204.114.105
ntpd: reply from 193.204.114.105: offset:+1367467563.322047 delay:0.018588 statu
s:0x24 strat:1 refid:0x00445443 rootdelay:0.000000 reach:0x1f
ntpd: settimeofday: Bad address
settimeofday library function is flawed somehow so, nothing (date,rdate,ntpd) works in busybox.
we need to change busybox or compile it with different features.
even samsung's busybox gives the same error..lol

Re: [SOLVED] Set Date/Time: Bad address

Posted: Thu May 02, 2013 6:13 am
by juusso
you've forgot to mention what tv are you trying to feed with ntpclient?
also have you tried attached binary?

Re: [SOLVED] Set Date/Time: Bad address

Posted: Thu May 02, 2013 12:11 pm
by nobody
I wish to understand things, not to use ready made things. About the tv it's a D8000. What binary? ntpclient? I don't want that. I wish to know why settimeofday fails. Nevermind, if (any of) you don't know this I will look at the source of busybox and try to understand the problem.

Re: Set Date/Time: Bad address

Posted: Sat Nov 16, 2013 4:52 pm
by miazza
juuso wrote: btw, we always can use built in busybox rdate script

Code: Select all

SERVER="193.110.137.171"
busybox rdate -s $SERVER
This is not working to me:

Code: Select all

VDLinux#> SERVER="193.110.137.171"
VDLinux#> busybox rdate -s $SERVER
rdate: timeout connecting to time server

Re: [SOLVED] Set Date/Time: Bad address

Posted: Sat Nov 16, 2013 5:04 pm
by juusso
try to use one of other time servers
http://www.timetools.co.uk/2013/07/25/ntp-server-uk/
http://tf.nist.gov/tf-cgi/servers.cgi
<google it :)>

Re: [SOLVED] Set Date/Time: Bad address

Posted: Sat Nov 16, 2013 6:24 pm
by miazza
Thank you juuso, but I tried it already.
It gives me an error like cannot connect to server (very fast this time of course).
Now I do not remember the clear message bu I will post it this evening.

Re: [SOLVED] Set Date/Time: Bad address

Posted: Sat Nov 16, 2013 11:48 pm
by miazza
This is the answer

Code: Select all

VDLinux#> SERVER="206.246.122.250"
VDLinux#> busybox rdate -s $SERVER
rdate: can't set time of day: Bad address

Re: [SOLVED] Set Date/Time: Bad address

Posted: Sun Dec 22, 2013 2:34 pm
by miazza
What I cannot understand is why ntpclient can set date and time while rdate gives back that error.
I am really getting crazy with that but most likely the rdate command on my build is not working.

Re: [SOLVED] Set Date/Time: Bad address

Posted: Sun Dec 22, 2013 3:03 pm
by bugficks
iirc i ve seen some comment in kernel that its blocked for some reason i cant remember :)
All times are UTC+01:00
Page 3 of 4

Powered by phpBB® Forum Software © phpBB Limited