public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marvin <marvin24@gmx.de>
To: Fabiano Manoel de Andrade <fabianoma@gmail.com>
Cc: linux-kernel@vger.kernel.org, cbe-oss-dev@ozlabs.org,
	linuxppc-dev@ozlabs.org
Subject: Re: RTC problem in PS3
Date: Mon, 17 Nov 2008 21:02:11 +0100	[thread overview]
Message-ID: <200811172102.12286.marvin24@gmx.de> (raw)
In-Reply-To: <1226875490.6597.11.camel@lottar>

forward to a better place...

On Sunday 16 November 2008 23:44:50 Fabiano Manoel de Andrade wrote:
> 	Hi I've compiled the latest version of linux kernel (2.6.27.6) in my
> PS3 running debian and get a warning message listed here
>
> 	Setting the system clock.
>   	Cannot access the Hardware Clock via any known method.
>   	Use the --debug option to see the details of our search for an access
> method. * Unable to set System Clock to: Sun Nov 16 20:33:06 UTC 2008
>
>
> 	The problem can be reproduced with the commands
>
> 	# hwclock --debug
>  	hwclock from util-linux-ng 2.13.1.1
>   	hwclock: Open of /dev/rtc failed, errno=2: No such file or directory.
>   	No usable clock interface found.
>   	Cannot access the Hardware Clock via any known method.
>   	# ls -l /dev/rtc*
>   	ls: cannot access /dev/rtc*: No such file or directory
>
> 	Loading the rtc-ppc module solve the problem, but after restart
> the system I still have the problem. Looking at kernel config I change the
> rtc-ppc to be build into kernel and this solve totally the problem. So the
> ps3_defconfig must set the rtc-ppc to be build into kernel.
>
> 	Thanks in advance.
> 	Fabiano.


  reply	other threads:[~2008-11-17 20:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-16 22:44 RTC problem in PS3 Fabiano Manoel de Andrade
2008-11-17 20:02 ` Marvin [this message]
2008-12-02 22:22   ` Geoff Levand

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200811172102.12286.marvin24@gmx.de \
    --to=marvin24@gmx.de \
    --cc=cbe-oss-dev@ozlabs.org \
    --cc=fabianoma@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox