| View previous topic :: View next topic |
| Author |
Message |
GenHeDi
Tux's lil' helper
Joined: 02 Jan 2016
Posts: 132
|
 Posted: Sun Jun 25, 2017 3:47 pm Post subject: rtc-cmos module needs to be configured |
 |
|
Hello,
during booting OpenRC 0.26.3 is complaining:
| Code: | | The rtc-cmos module needs to be configured in /etc/conf.d/modules or built in. |
My /etc/conf.d/modules looks like below:
| Code: | cat /etc/conf.d/modules
# Linux users can define a list of modules for a specific kernel version,
# a released kernel version, a main kernel version or all kernel versions.
# The most specific versioned variable will take precedence.
# FreeBSD users can only use the modules="foo bar" setting.
#modules_2_6_23_gentoo_r5="ieee1394 ohci1394"
#modules_2_6_23="tun ieee1394"
#modules_2_6="tun"
#modules_2="ipv6"
#modules="ohci1394"
# Linux users can give modules a different name when they load - the new name
# will also be used to pick arguments below.
# This is not supported on FreeBSD.
#modules="dummy:dummy1"
# Linux users can give the modules some arguments if needed, per version
# if necessary.
# Again, the most specific versioned variable will take precedence.
# This is not supported on FreeBSD.
#module_ieee1394_args="debug"
#module_ieee1394_args_2_6_23_gentoo_r5="debug2"
#module_ieee1394_args_2_6_23="debug3"
#module_ieee1394_args_2_6="debug4"
#module_ieee1394_args_2="debug5"
# You should consult your kernel documentation and configuration
# for a list of modules and their options. |
Please advice what is best: build in or configured in /etc/conf.d/modules?
Regards
_________________
Nulla tenaci invia est via |
|
| Back to top |
|
 |
Ant P.
Watchman
Joined: 18 Apr 2009
Posts: 6920
|
| Posted: Sun Jun 25, 2017 9:11 pm Post subject: |
|
|
| /usr/src/linux/drivers/rtc/Kconfig: |
config RTC_DRV_CMOS
tristate "PC-style 'CMOS'"
depends on X86 || ARM || M32R || PPC || MIPS || SPARC64 || MN10300
default y if X86 |
The default is built-in, therefore you should leave it built in. A better question is why did you disable it? |
|
| Back to top |
|
|
GenHeDi
Tux's lil' helper
Joined: 02 Jan 2016
Posts: 132
|
| Posted: Mon Jun 26, 2017 6:54 pm Post subject: |
|
|
Hello Ant P.
Well, I did not disable it intentionally.
I had a look at /usr/src/linux/drivers/rtc/Kconfig:
| Code: | config RTC_DRV_CMOS
tristate "PC-style 'CMOS'"
depends on X86 || ARM || M32R || PPC || MIPS || SPARC64 || MN10300
default y if X86
select RTC_MC146818_LIB |
I had a look for "RTC_MC146818_LIB" in my .config file of the current running Linux/x86 4.9.16 kernel:
| Code: | cat .config | grep RTC_MC146818_LIB
CONFIG_RTC_MC146818_LIB=y |
A search on "CMOS" in "make menuconfig" shows:
| Code: | Symbol: GENERIC_CMOS_UPDATE [=y]
Type : boolean
Defined at kernel/time/Kconfig:51
Selected by: X86 [=y]
Symbol: RTC_DRV_CMOS [=m]
Prompt: PC-style 'CMOS'
Location:
-> Device Drivers
-> Real Time Clock (RTC_CLASS [=y])
Defined at drivers/rtc/Kconfig:827
Depends on: RTC_CLASS [=y] && (X86 [=y] || ARM || M32R || PPC || MIPS || SPARC64 || MN10300)
Selects: RTC_MC146818_LIB [=y] |
As far as my knowledge is concerned, the driver should be built in the kernel.
Please correct me if I am wrong.
_________________
Nulla tenaci invia est via |
|
| Back to top |
|
|
krinn
Watchman
Joined: 02 May 2003
Posts: 7470
|
| Posted: Tue Jun 27, 2017 1:08 am Post subject: |
|
|
That's how it is in that kernel config, it doesn't mean the running kernel use that config still.
You could either check the running config of your kernel or dmesg for cmos clue (as easy as dmesg | grep cmos). |
|
| Back to top |
|
|
GenHeDi
Tux's lil' helper
Joined: 02 Jan 2016
Posts: 132
|
| Posted: Thu Jun 29, 2017 6:34 pm Post subject: |
|
|
| Code: | dmesg | grep cmos
[ 23.778134] rtc_cmos 00:03: RTC can wake from S4
[ 23.778267] rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0
[ 23.778292] rtc_cmos 00:03: alarms up to one month, y3k, 242 bytes nvram, hpet irqs |
The info I provided, is the configuration of the running kernel.
_________________
Nulla tenaci invia est via |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54831
Location: 56N 3W
|
| Posted: Thu Jun 29, 2017 6:39 pm Post subject: |
|
|
GenHeDi,
| Code: | | [ 23.778134] rtc_cmos... |
That's very late for any kernel built ins to be initialised.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
GenHeDi
Tux's lil' helper
Joined: 02 Jan 2016
Posts: 132
|
| Posted: Fri Jun 30, 2017 4:08 pm Post subject: |
|
|
how can I speed this up?
_________________
Nulla tenaci invia est via |
|
| Back to top |
|
|
krinn
Watchman
Joined: 02 May 2003
Posts: 7470
|
| Posted: Sat Jul 01, 2017 2:48 am Post subject: |
|
|
for ref:
| Code: | | [ 0.547709] rtc_cmos 00:02: RTC can wake from S4 |
as you see, it's not really about speed it up, but more about finding and fixing the real issue.
you could start with dmesg output no? |
|
| Back to top |
|
|
GenHeDi
Tux's lil' helper
Joined: 02 Jan 2016
Posts: 132
|
| Posted: Sat Jul 01, 2017 2:42 pm Post subject: |
|
|
Hello Krinn
Thanks for your reply.
I definitely agree on finding and fixing the real issue.
Do I understand you correctly that I should provide the complete dmesg output?
If so, what is a proper way to do this? Because it is a huge amount of text. Copy / paste into this topic is a bit over the top I suppose.
Regards,
GenHeDi
_________________
Nulla tenaci invia est via |
|
| Back to top |
|
|
Hu
Administrator
Joined: 06 Mar 2007
Posts: 23091
|
| Posted: Sat Jul 01, 2017 4:12 pm Post subject: |
|
|
| Put the output of dmesg onto a pastebin site, then post here the URL of the pasted content. You can use app-text/wgetpaste to simplify this. |
|
| Back to top |
|
|
GenHeDi
Tux's lil' helper
Joined: 02 Jan 2016
Posts: 132
|
| Posted: Sat Jul 01, 2017 9:01 pm Post subject: |
|
|
Hello,
I did put my dmesg on https://pastebin.com/7zuDuK15
Regards
_________________
Nulla tenaci invia est via |
|
| Back to top |
|
|
GenHeDi
Tux's lil' helper
Joined: 02 Jan 2016
Posts: 132
|
| Posted: Sat Jul 08, 2017 8:05 am Post subject: |
|
|
How can I definitly be sure if the right module is build in, in the right way?
_________________
Nulla tenaci invia est via |
|
| Back to top |
|
|
GenHeDi
Tux's lil' helper
Joined: 02 Jan 2016
Posts: 132
|
| Posted: Wed Aug 23, 2017 5:56 pm Post subject: |
|
|
I solved the problem with following step:
In section | Code: | | → Device Drivers → Real Time Clock |
I changed | Code: | | <M> PC-style 'CMOS' |
into | Code: | | <*> PC-style 'CMOS' |
My rc.log shows:
| Code: | * Setting hardware clock using the system clock [Local Time] ...
[ ok ] |
And:
| Code: | dmesg | grep cmos
[ 2.840449] rtc_cmos 00:03: RTC can wake from S4
[ 2.840612] rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0
[ 2.840692] rtc_cmos 00:03: alarms up to one month, y3k, 242 bytes nvram, hpet irqs
[ 2.841886] rtc_cmos 00:03: setting system clock to 2017-08-23 19:41:45 UTC (1503517305) |
I think this is the solution.
Regards
GenHedi
_________________
Nulla tenaci invia est via |
|
| Back to top |
|
|
|
Kernel & Hardware
