[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: No audio on PowerBook G4 for kernels > 2.6.22



Elimar

Thanks for responding, and Sorry for my real late answer.

On Mon, Aug 25 2008, at 09:47 +0200, Elimar Riesebieter wrote:
> On Sun, 24 Aug 2008 the mental interface of
> Wolfgang Pfeiffer told:
> 
> [...]
> > be warned tho': just realized that something went wrong with /dev/rtc
> > with this kernel/config ... or at least I don't see any rtc being
> > usable for hwclock ... And so far I don't know how to fix that ..
> 
> CONFIG_RTC_LIB=y

selected here as a module

> CONFIG_RTC_CLASS=y

... selected as module

> CONFIG_RTC_HCTOSYS=y

... not selected

> CONFIG_RTC_INTF_SYSFS=y

... selected 

> CONFIG_RTC_INTF_PROC=y

.. selected

> CONFIG_RTC_INTF_DEV=y

... selected

> CONFIG_RTC_DRV_PPC=y

.... missing


So it looks I tried to set up the RTC system for that kernel, but
failed to do so because of a missing RTC_DRV_PPC driver, or perhaps
because of deselecting CONFIG_RTC_HCTOSYS ...

Funny tho' that the hw clock still seems to get read at boot time,
although the system complained last boot time, that (excerpt from
/var/log/boot):


Thu Jun 12 11:49:01 2008: Cannot access the Hardware Clock via any known method.
Thu Jun 12 11:49:01 2008: Use the --debug option to see the details of our search for an access method.
Thu Jun 12 11:49:01 2008: Setting the system clock..
Thu Jun 12 11:49:01 2008: Cannot access the Hardware Clock via any known method.
Thu Jun 12 11:49:01 2008: Use the --debug option to see the details of our search for an access method.
Thu Jun 12 11:49:01 2008: System Clock set. Local time: Thu Jun 12 09:48:57 UTC 2008.


See? The clock is set up fine, as it seems. Ditto for the system time
here. That's probably why it took so long until I realized the missing
RTC device ... :)

Whatever: I pulled the latest kernel sources, and at least they now
seem to have RTC_DRV_PPC ... let's see ..

Thanks again, Elimar

Best Regards
Wolfgang

-- 
Amy. Queen. Right Now.
http://heelsbroke.blogspot.com/


Reply to: