Am 20.09.2007 01:28 schrieb Chuck Ebbert: > AFAICT the rtc problem is caused by misconfiguration: both the new > and old rtc driver have been built and they are both trying to load. Rats. Sorry. I remember now. That's not the first time I am hit by that one. I had even made a resolution to try and find out the correct options to set. So what are they? CONFIG_RTC=y and CONFIG_RTC_DRV_CMOS=n? Guess I should try that combination in my next round of tests. Anyway, shouldn't there be a warning or at least some clear instructions? As it is, both the old and the new driver claim in Kconfig that you need them in order to access your RTC, and none of them even mentions the other, so it's way too easy to end up enabling both of them. So are all my other woes a consequence of that one? Thanks, T. -- Tilman Schmidt E-Mail: [email protected] Bonn, Germany Diese Nachricht besteht zu 100% aus wiederverwerteten Bits. Ungeöffnet mindestens haltbar bis: (siehe Rückseite)
Attachment:
signature.asc
Description: OpenPGP digital signature
- Follow-Ups:
- Re: 2.6.23-rc6-mm1
- From: Tilman Schmidt <[email protected]>
- Re: 2.6.23-rc6-mm1
- References:
- 2.6.23-rc6-mm1
- From: Andrew Morton <[email protected]>
- Re: 2.6.23-rc6-mm1
- From: Tilman Schmidt <[email protected]>
- Re: 2.6.23-rc6-mm1
- From: Andrew Morton <[email protected]>
- Re: 2.6.23-rc6-mm1
- From: Chuck Ebbert <[email protected]>
- 2.6.23-rc6-mm1
- Prev by Date: Re: 2.6.23-rc6-mm1: failure to boot on HP nx6325, no sound when booted, USB-related WARNING
- Next by Date: Re: what is the difference between shutdown command and writing to /sys/power/state
- Previous by thread: Re: 2.6.23-rc6-mm1
- Next by thread: Re: 2.6.23-rc6-mm1
- Index(es):
 |