Hi Alex,
Le 07/11/2013 14:19, Alexander Graf a écrit : > On 07.11.2013, at 14:15, Guillaume Gardet <guillaume.gar...@free.fr> wrote: > >> Le 07/11/2013 14:04, Alexander Graf a écrit : >>> On 07.11.2013, at 14:00, Guillaume Gardet <guillaume.gar...@free.fr> wrote: >>> >>>> Le 07/11/2013 13:34, Alexander Graf a écrit : >>>>> On 07.11.2013, at 13:19, Guillaume Gardet <guillaume.gar...@free.fr> >>>>> wrote: >>>>> >>>>>> Le 07/11/2013 11:17, Alexander Graf a écrit : >>>>>>> On 07.11.2013, at 11:14, Guillaume Gardet <guillaume.gar...@free.fr> >>>>>>> wrote: >>>>>>> >>>>>>>> Hi, >>>>>>>> >>>>>>>> here are some tests results of 13.1 images. Results are pretty bad >>>>>>>> ATM. :( >>>>>>>> >>>>>>>> >>>>>>>> * Beagleboard xM rev B : >>>>>>>> - Image fails to boot with the following error message: >>>>>>>> ******************************************************************************** >>>>>>>> [ 8.109588] Freeing unused kernel memory: 532K (c07e5000 - c086a000) >>>>>>>> setterm: cannot (un)set powersave mode: Inappropriate ioctl for device >>>>>>>> /usr/sbin/klogconsole >>>>>>>> Thu Nov 7 00:00:00 UTC 2013 >>>>>>>> [ 13.670684] ehci-omap ehci-omap.0: Can't get PHY device for port 1: >>>>>>>> -6 >>>>>>>> [ 15.271728] hub 1-0:1.0: Cannot enable port 1. Maybe the USB cable >>>>>>>> is bad? >>>>>>>> [437097081.923981] Including oem partition info file >>>>>>>> [437097082.043030] Searching for boot device... >>>>>>>> [ 16.471771] hub 1-0:1.0: Cannot enable port 1. Maybe the USB cable >>>>>>>> is bad? >>>>>>>> [ 17.671752] hub 1-0:1.0: Cannot enable port 1. Maybe the USB cable >>>>>>>> is bad? >>>>>>>> [ 18.925598] hub 1-0:1.0: Cannot enable port 1. Maybe the USB cable >>>>>>>> is bad? >>>>>>>> [ 18.933227] hub 1-0:1.0: unable to enumerate USB device on port 1 >>>>>>>> [437097110.607544] Failed to find boot device ! >>>>>>>> [437097110.639527] rebootException: reboot in 120 sec... >>>>>>>> ******************************************************************************** >>>>>>>> >>>>>>>> The USB problem seems to be known: >>>>>>>> http://www.spinics.net/lists/linux-omap/msg90670.html >>>>>>>> Is boot problem related? I do not know. >>>>>>>> >>>>>>>> D6 and D7 lights (related to MMC) are turned OFF when kernel start >>>>>>>> whereas it was ON with u-boot. >>>>>>>> So, MMC seems to be not working at all. It seems that kernel modules >>>>>>>> (at least omap mmc modules) from initrd are not loaded. Very strange. >>>>>>> If you boot with kiwidebug=1 you should be able to get a shell and >>>>>>> check whether the modules are loaded or not. >>>>>> Indeed, mmc modules are not loaded. But loading them manually does not >>>>>> help to get mmc device to appear. I think we are missing other drivers >>>>>> (maybe GPIO). >>>>> Could you quickly compare the defconfig for omap4 and the one we have to >>>>> see what we're missing? >>>> I think it is missing from initrd only, not rootfs, since initrd has only >>>> some of kernel modules. I will try to add some kernel modules to our >>>> initrd and see if it helps. >>>> >>>>>>>> * Pandaboard rev A3 : >>>>>>>> - Image hangs early with the following message: (Tested with 2 SD >>>>>>>> cards). >>>>>>>> ******************************************************************************** >>>>>>>> U-Boot SPL 2013.04 (Oct 21 2013 - 22:37:21) >>>>>>>> OMAP4430 ES2.2 >>>>>>>> OMAP SD/MMC: 0 >>>>>>>> ******************************************************************************** >>>>>>>> >>>>>>>> >>>>>>>> Is there anyone who could test those images on their baords, >>>>>>>> especially pandaboard? >>>>>>> Andrew reported the same issue. Could you please try with 12.3's SPL >>>>>>> (MLO) and/or u-boot.bin to boil down which component is at fault here? >>>>>> I managed to get u-boot working using old MLO (and copying u-boot.bin >>>>>> from boot/ folder to the root of the boot partition). >>>>> Does only replacing one of the two help already? >>>> Yes, replacing MLO only does help. I think our ext2 patch for MLO may be >>>> broken for 13.1 u-boot. Maybe we could bump u-boot version at the same >>>> time we check MLO patch? >>> Hrm. We're at rc2 here. Maybe it is a good idea to bump the version after >>> all. Sigh. >> Could you do it, please? I will not have time for that ATM. :( > I can try, but if I don't get around until Saturday it won't happen for at > least another week. Any update on u-boot? Another good point to bump u-boot version is new versions have full support for Device Tree. And (after workarounded MLO problem,) Pandaboard kernel start to boot boot when using a DTB (and then fails to find MMC for similar reasons as beagle xM failed, apparently) whereas without DTB I get the "undefined instruction" error. Guillaume (...) -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
