[opensuse-arm] EfikaMX - Kernel 3.4.x - no /dev/rtc0
Hello all, after having successfully booted my EfikaMX with a Kernel 2.6.31 based openSUSE build, I wanted to move on to the most recent stuff, and used: LimeJeOS-openSUSE-12.2-ARM-efika.armv7l-1.12.2-Build6.1.raw.xz which I yesterday got from: http://download.opensuse.org/repositories/openSUSE:/Factory:/ARM/images/ Ignoring Graphics, there is only one real issue with this: the 3.4.4.3 kernel does not initialize the RTC device (/dev/rtc0), thus the system boots up on 1970-01-01. Looking into the Kernel configuration, there is no obvious option missing. Any ideas? Thanks in advance - so long - MgE -- Matthias G. Eckermann Senior Product Manager SUSE® Linux Enterprise SUSE LINUX Products GmbH Maxfeldstraße 5 90409 Nürnberg Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On 07/24/2012 09:58 AM, Matthias G. Eckermann wrote:
Hello all,
after having successfully booted my EfikaMX with a Kernel 2.6.31 based openSUSE build, I wanted to move on to the most recent stuff, and used:
LimeJeOS-openSUSE-12.2-ARM-efika.armv7l-1.12.2-Build6.1.raw.xz which I yesterday got from: http://download.opensuse.org/repositories/openSUSE:/Factory:/ARM/images/
Ignoring Graphics, there is only one real issue with this: the 3.4.4.3 kernel does not initialize the RTC device (/dev/rtc0), thus the system boots up on 1970-01-01. Looking into the Kernel configuration, there is no obvious option missing. Any ideas?
I had a look at the source code for it. There is a driver for the mc13xxx which is in there and it's enabled in our config. However, since you don't get a device, it apparently doesn't work properly. I guess the next step would be to throw debug printk's in the probing code and see if a) it gets executed at all b) if so, where it fails Alex -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 24.07.2012 09:58, schrieb Matthias G. Eckermann:
Hello all,
after having successfully booted my EfikaMX with a Kernel 2.6.31 based openSUSE build, I wanted to move on to the most recent stuff, and used:
LimeJeOS-openSUSE-12.2-ARM-efika.armv7l-1.12.2-Build6.1.raw.xz which I yesterday got from: http://download.opensuse.org/repositories/openSUSE:/Factory:/ARM/images/
Ignoring Graphics, there is only one real issue with this: the
3.4.4.3 kernel does not initialize the RTC device (/dev/rtc0), thus the system boots up on 1970-01-01. Looking into the Kernel configuration, there is no obvious option missing. Any ideas?
Thanks in advance - so long - MgE
I remember doing this config tweaking months ago. https://build.opensuse.org/package/files?package=kernel-imx51&project=home%3Abmwiedemann%3Abranches%3AopenSUSE%3AFactory%3AARM which I made based on some config from steev It has in the diff: +CONFIG_HAVE_SCHED_CLOCK=y +CONFIG_HAVE_SPARSE_IRQ=y +CONFIG_COMPAT_BRK=y +CONFIG_ARCH_MXC_AUDMUX_V2=y +CONFIG_BT_L2CAP=y +CONFIG_BT_SCO=y +CONFIG_MISC_DEVICES=y +CONFIG_REGULATOR_MC13XXX_CORE=y +CONFIG_REGULATOR_MC13892=y +CONFIG_AC97_BUS=m especially the REGULATOR configs are related to RTC Ciao Bernhard M. - -- (o_ //\ V_/_ http://www.suse.de/ SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlAW8C4ACgkQSTYLOx37oWQR9wCfdwH70YMS3C4gtNjr15Wo/qIM BooAn2psw+VYT5hDIfllxogiI8Rauazf =cpWf -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On 30.07.2012, at 22:35, Bernhard M. Wiedemann wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Am 24.07.2012 09:58, schrieb Matthias G. Eckermann:
Hello all,
after having successfully booted my EfikaMX with a Kernel 2.6.31 based openSUSE build, I wanted to move on to the most recent stuff, and used:
LimeJeOS-openSUSE-12.2-ARM-efika.armv7l-1.12.2-Build6.1.raw.xz which I yesterday got from: http://download.opensuse.org/repositories/openSUSE:/Factory:/ARM/images/
Ignoring Graphics, there is only one real issue with this: the
3.4.4.3 kernel does not initialize the RTC device (/dev/rtc0), thus the system boots up on 1970-01-01. Looking into the Kernel configuration, there is no obvious option missing. Any ideas?
Thanks in advance - so long - MgE
I remember doing this config tweaking months ago. https://build.opensuse.org/package/files?package=kernel-imx51&project=home%3Abmwiedemann%3Abranches%3AopenSUSE%3AFactory%3AARM
which I made based on some config from steev
It has in the diff: +CONFIG_HAVE_SCHED_CLOCK=y +CONFIG_HAVE_SPARSE_IRQ=y +CONFIG_COMPAT_BRK=y +CONFIG_ARCH_MXC_AUDMUX_V2=y +CONFIG_BT_L2CAP=y +CONFIG_BT_SCO=y +CONFIG_MISC_DEVICES=y +CONFIG_REGULATOR_MC13XXX_CORE=y +CONFIG_REGULATOR_MC13892=y +CONFIG_AC97_BUS=m
especially the REGULATOR configs are related to RTC
Right, but those are already set in our 3.4 kernel, no? Alex -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On 2012-07-30 T 22:39 +0200 Alexander Graf wrote:
On 30.07.2012, at 22:35, Bernhard M. Wiedemann wrote:
Am 24.07.2012 09:58, schrieb Matthias G. Eckermann:
Ignoring Graphics, there is only one real issue with this: the 3.4.4.3 kernel does not initialize the RTC device (/dev/rtc0), thus the system boots up on 1970-01-01. Looking into the Kernel configuration, there is no obvious option missing. Any ideas?
I remember doing this config tweaking months ago. https://build.opensuse.org/package/files?package=kernel-imx51&project=home%3Abmwiedemann%3Abranches%3AopenSUSE%3AFactory%3AARM
which I made based on some config from steev
It has in the diff: +CONFIG_HAVE_SCHED_CLOCK=y +CONFIG_HAVE_SPARSE_IRQ=y +CONFIG_COMPAT_BRK=y +CONFIG_ARCH_MXC_AUDMUX_V2=y +CONFIG_BT_L2CAP=y +CONFIG_BT_SCO=y +CONFIG_MISC_DEVICES=y +CONFIG_REGULATOR_MC13XXX_CORE=y +CONFIG_REGULATOR_MC13892=y +CONFIG_AC97_BUS=m
especially the REGULATOR configs are related to RTC
Right, but those are already set in our 3.4 kernel, no?
Not all. At least not in this one: 3.4.4-3-imx51 #2 Sun Jul 15 00:41:23 UTC 2012 I don't find: CONFIG_HAVE_SCHED_CLOCK CONFIG_HAVE_SPARSE_IRQ CONFIG_ARCH_MXC_AUDMUX_V2 CONFIG_BT_L2CAP CONFIG_BT_SCO CONFIG_MISC_DEVICES CONFIG_AC97_BUS And this one is obvious: # CONFIG_COMPAT_BRK is not set Loading the regulator modules does not solve the issue. so long - MgE -- Matthias G. Eckermann Senior Product Manager SUSE® Linux Enterprise Phone: +49 30 44315731 Mobile: +49 179 2949448 Twitter: mge1512 SUSE LINUX Products GmbH Maxfeldstraße 5 90409 Nürnberg Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
participants (3)
-
Alexander Graf -
Bernhard M. Wiedemann -
Matthias G. Eckermann