On Wed, Jan 13, 2010 at 08:05:23PM +0100, Sascha Silbe wrote:
> On Tue, Jan 12, 2010 at 02:18:10PM +0100, Jordi Mallach wrote:
>
> >Sorry about this. I say close the bug and if I come back as a PPC
> >user, I'll
> >test 2.6.32-trunk to see what happens.
> I've been hit by this issue as well in the
On Tue, Jan 12, 2010 at 02:18:10PM +0100, Jordi Mallach wrote:
Sorry about this. I say close the bug and if I come back as a PPC
user, I'll
test 2.6.32-trunk to see what happens.
I've been hit by this issue as well in the past (on an eMac), but don't
have time to do any testing right now. It w
On Tue, Dec 29, 2009 at 04:38:51PM +0100, Moritz Muehlenhoff wrote:
> > - "hctosys: unable to read the hardware clock\n");
> > + "hctosys: unable to read the hardware clock (%d)\n",
> > err);
> Jordi, did you test the patch? Do current unstable kernels work for
On Tue, Sep 01, 2009 at 03:08:03AM +0100, Ben Hutchings wrote:
> On Tue, 2009-08-18 at 21:11 +0200, Jordi Mallach wrote:
> > Package: linux-image-2.6.30-1-powerpc
> > Version: 2.6.30-6
> > Severity: important
> >
> > When I boot my G4-based laptop, the hw clock can't be accessed and the
> > syste
On Tue, 2009-08-18 at 21:11 +0200, Jordi Mallach wrote:
> Package: linux-image-2.6.30-1-powerpc
> Version: 2.6.30-6
> Severity: important
>
> When I boot my G4-based laptop, the hw clock can't be accessed and the system
> time ends up being the epoch for the platform Jan 1st, 1904.
>
> Switching
Package: linux-image-2.6.30-1-powerpc
Version: 2.6.30-6
Severity: important
When I boot my G4-based laptop, the hw clock can't be accessed and the system
time ends up being the epoch for the platform Jan 1st, 1904.
Switching back to 2.6.26 fixes the problem. Although CONFIG_RTC_DRV_GENERIC
was co
6 matches
Mail list logo
