On 09.09.14 11:14, Guillaume Gardet wrote:
Le 08/09/2014 17:57, Alexander Graf a écrit :
Arndale : Does boot u-boot but fails with a "Wrong Image Format" which should be fixed by SR #248024 (already accepted by Alex, thanks). I fixed it manually before the SR were accepted but I get lots of "cpufreq: __target_index: Failed to change cpu frequency: -22" errors logged but I finaly get a prompt. Yes, you can work around this by echo'ing "performance" into the governor sysfs file. I haven't quite figured out what's going wrong here. Ok. It seems that the CPU voltage cannot be adjusted ("exynos-cpufreq exynos-cpufreq: failed to set cpu voltage to 1100000"). Maybe we are missing a power chip driver in the kernel? Maybe - I have no idea about power chip drivers :). Can you take a look?
The power chip driver is included. So maybe just a broken cpu freq for exynos?
Maybe, or maybe it's missing infrastructure in the dt.
Serial console and USB2 work, but eth0 seems to have some problems. Second boot seems to be broken (I fallback to a dracut prompt). I though I had fixed that one. The problem is that dracut doesn't include all modules required to access the SD card. So I added them to INITRD_MODULES in /etc/sysconfig/kernel in config.sh.
Can you please check on first boot whether the line was properly updated? There is no /etc/sysconfig/kernel file on firstboot. O_o. There should be.
Using dracut prompt, I listed "/lib/modules/3.16.1-2.g2ab6585-lpae/kernel/drivers/mmc/host" folder and only got: mmci.ko omap.ko omap_hsmmc.ko sdhci-pltfm.ko sdhci-tegra.ko sdhci.ko
So, no dw_* mmc modules. But how those mmc modules get added?
According to dracut documentation: https://www.kernel.org/pub/linux/utils/boot/dracut/dracut.html#_adding_kerne...
We should use /etc/dracut.conf or /etc/dracut.conf.d/myconf.conf and NOT /etc/sysconfig/kernel Am I wrong?
It depends on how you generate the initrd. Usually it gets generated by a call to "mkinitrd" which is a wrapper script around dracut these days. That script reads /etc/sysconfig/kernel and adds the modules to the command line as parameters.
First boot is ok since kiwi adds dw_* mmc modules in initial initrd. But 2nd boot is broken because generated initrd does not include them.
Yes, exactly. That's why I added them to /etc/sysconfig/kernel. Meh. Alex -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org