From owner-freebsd-mips@FreeBSD.ORG Wed Nov 17 10:42:03 2010 Return-Path: Delivered-To: freebsd-mips@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5DE4F1065673 for ; Wed, 17 Nov 2010 10:42:03 +0000 (UTC) (envelope-from freebsd-mips@dino.sk) Received: from loki.netlab.sk (loki.netlab.sk [84.245.65.11]) by mx1.freebsd.org (Postfix) with ESMTP id 1AD8B8FC0A for ; Wed, 17 Nov 2010 10:42:02 +0000 (UTC) Received: from door.dino.sk (fw1.dino.sk [84.245.95.252]) (AUTH: PLAIN milan, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by loki.netlab.sk with esmtp; Wed, 17 Nov 2010 11:50:09 +0100 id 00033C1D.4CE3B361.0000E301 From: Milan Obuch To: Luiz Otavio O Souza Date: Wed, 17 Nov 2010 11:42:19 +0100 User-Agent: KMail/1.13.5 (FreeBSD/8.1-STABLE; KDE/4.5.3; i386; ; ) References: <201011170007.57640.freebsd-mips@dino.sk> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201011171142.21067.freebsd-mips@dino.sk> Cc: freebsd-mips@freebsd.org Subject: Re: First RSPRO deployed ! X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2010 10:42:03 -0000 On Wednesday 17 November 2010 10:40:45 Luiz Otavio O Souza wrote: > On Nov 16, 2010, at 9:07 PM, Milan Obuch wrote: > > On Tuesday 16 November 2010 11:10:46 Monthadar Al Jaberi wrote: > >> Hi, > >> > >> Nice to see other people work on the same board! feels like RSPRO fever! > >> :P > >> > >> Thank you for sharing your files with us. I am running freebsd from > >> both flash (mdroot) and NFS. > >> In both cases I get the following error RTC after adding your diffs: > >> ... > >> Invalid time in real time clock. > >> Check and reset the date immediately! > >> ... > >> > >> Before your diffs I used to get: > >> ... > >> warning: no time-of-day clock registered, system time will not be set > >> accurately ... > >> > >> Do you have any ideas what the cause could be? I can't seem to change > >> the time with date also. > >> Thank you again. > > > > I saw this as well, but only first time after running kernel with rtc (or > > first time after longer period without power). Maybe after setting > > correct date it disappears? I use ntpdate to correct date/time, just a > > bit lazy to type long string of numbers... > > Exactly ! (or you have missed the rspro-rtc.diff patch which need to be > applied after ar71xx_spi_cs_mux.diff) > > But keep in your mind that the rspro rtc is not that great without a > battery backup :/ (it won't keep the time for too many days). > Well, in my case couple of hours is enough and time is invalid again :( But using ntpdate in a network is workaround good enough for me... Milan