Hello, I just tested openSUSE-Tumbleweed-ARM-JeOS-chromebook.armv7l-1.12.1-Build326.1.raw.xz: 1. On first boot screen still stays black, starts to work only after first reboot. Maybe we need to force_drivers for initial initrd also? 2. rtc_max77686 spam log and tty output with messages: rtc_max77686: RTC cannot handle the year 1970. Assume it's 2000. As i understand rtc drivers built-in inside kernel, but i2c driver which it use built as module and i2c driver init call happen too late for rtc on system power on? This is probably not chromebook specific issue but for all boards with i2c rtc drivers. On Wed, Sep 2, 2015 at 10:21 AM, Guillaume Gardet <guillaume.gardet@free.fr> wrote:
Le 01/09/2015 15:42, Andreas Färber a écrit :
Am 01.09.2015 um 15:37 schrieb Guillaume Gardet:
Le 01/09/2015 14:49, Misha Komarovskiy a écrit :
On Tue, Sep 1, 2015 at 3:35 PM, Misha Komarovskiy <zombah@gmail.com> wrote:
Kernel is fine now, but but required modules won't auto load even with force_drivers 8( If i run dracut -f manually output is: line 2: force_drivers: command not found but this fix worked for me before, maybe something changed in dracut itself?
It seems the problem that force_drivers line must not contain empty spaces, now it look like: force_drivers += "cros_ec_devs ptn3460 pwm-samsung" and correct one is force_drivers+="cros_ec_devs ptn3460 pwm-samsung"
with such line, dracut parse force_drivers fine.
Indded. Just tried it and I get the display! :D Thanks a lot!
SR #328325 is pending: https://build.opensuse.org/request/show/328325
Guillaume, I'm pretty sure I saw a comment in the JeOS script that says that add_drivers (or so) needs the string to start with a space, to avoid that being concatenated to a previously added driver. I imagine the same applies to force_drivers as well then.
Fixed in SR #328558.
Guillaume
Regards, Andreas
-- Best Regards, Misha Komarovskiy zombahatgmaildotcom -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org