El 2015-12-02 13:52, Andreas Färber escribió:
Hi,
Am 01.12.2015 um 08:08 schrieb Oscar C:
I'm trying to boot my udoo-quad (it's very similar to the cubox-i that we already support) using u-boot and kernel from mainline. Although it boots the kernel fine, it hangs somewhere in the middle without any error. The hang is not always in the same point, sometimes is goes further while others not. Using the same u-boot but with a downstream kernel works fine, so u-boot is not the problem here. Any idea?
It looks like it's recognizing mmcblk0 with p1 and p2, so I don't see an immediate reason for it not to boot into your root. The HDMI error should not be fatal.
Maybe some driver is missing in the initrd and needs to be added manually via some /etc/dracut.conf.d/udoo_modules.conf <<EOF add_drivers+=" foo" EOF
Another trivial thing to try is to add rootwait to your kernel command line, a good idea for SD cards but probably no solution here.
Regards, Andreas
Good news! After a lot of wasted time, using kernel 4.0.5 and a custom config I got it working! -> Welcome to openSUSE 20151118 "Tumbleweed" - Kernel 4.0.5-20.gd3f999c-vanilla (ttymxc1). Now I would like to debug why it doesn't work with a current kernel. First step (IMHO) is to try the same kernel version but with the default config. Is there a way in OBS to recover a package to a point in time? If that's not possible, what should I do now? -- Cheers -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org