Re: [opensuse-arm] openSUSE 13.1 beagle and panda images status

2013-11-08 Thread Guillaume Gardet
Hi,


Le 07/11/2013 18:56, Guillaume Gardet a écrit :
> Le 07/11/2013 14:00, Guillaume Gardet a écrit :
>> Le 07/11/2013 13:34, Alexander Graf a écrit :
>>> On 07.11.2013, at 13:19, Guillaume Gardet  wrote:
>>>
 Le 07/11/2013 11:17, Alexander Graf a écrit :
> On 07.11.2013, at 11:14, Guillaume Gardet  
> 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.
> I added '' to driver list in kiwi since MMC0 
> uses TWL4030 GPIOs and now MMC is tried to be detected but fails:
> 
> [8.125213] 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.410552] twl4030_gpio twl4030_gpio: can't dispatch IRQs from modules
> [   13.683227] ehci-omap ehci-omap.0: Can't get PHY device for port 1: -6
> [   14.136383] omap_hsmmc omap_hsmmc.0: Unable to grab MMC CD IRQ
> [   14.142791] omap_hsmmc: probe of omap_hsmmc.0 failed with error -22
> [437097413.135681] Starting boot shell on /dev/tty2
> [   15.306274] hub 1-0:1.0: Cannot enable port 1.  Maybe the USB cable is bad?
> [437097414.536286] Including oem partition info file
> [437097414.647187] Searching for boot device...
> [   16.506408] hub 1-0:1.0: Cannot enable port 1.  Maybe the USB cable is bad?
> [   17.706542] hub 1-0:1.0: Cannot enable port 1.  Maybe the USB cable is bad?
> [   18.906585] hub 1-0:1.0: Cannot enable port 1.  Maybe the USB cable is bad?
> [   18.914001] hub 1-0:1.0: unable to enumerate USB device on port 1
> [437097442.617462] Failed to find boot device !
> 
>
> The main problem seems to be:
> "twl4030_gpio: can't dispatch IRQs from modules"
>
> and as said here: 
> http://lists.infradead.org/pipermail/linux-arm-kernel/2012-February/085111.html
> "twl4030_gpio: can't dispatch IRQs from modules
> ... apparently because there is no way to unregister a irq once the
> module is unloaded.
>
> That makes sdmmc pretty much unusable if twl gpio is built as a module."
>
> I will try to add more kernel drivers but I think we should have TWL4030 GPIO 
> built-in and not as a module.

Adding TWL4030 gpio as built-in instead of module does help to boot on MMC.

What would be the best way to add this patch? I would say:
* Adding kernel-default (and kernel-source?) to 13.1:Ports to fix current 
version
* Adding it to 13.1/master GIT repo for futur versions


Guillaume

-- 
To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org
To con

[opensuse-arm] Factory ARM images: packages to rebuild + kiwi/OBS problem?

2013-11-08 Thread Guillaume Gardet
Hi,

Could you trigger rebuild of:
* libyui-ncurses-pkg : to fix libzypp dep which has a newer version now.
* glib2-branding-openSUSE : to fix gio-branding-openSUSE dep.

This will fix JeOS image deps.
I think there is a problem in spec file because we should rebuild them 
automatically. No?

Moreover, non rootfs images have another error, related to kiwi:
"nothing provides ERROR_NO_BOOT_CONFIG_FILE_FOUND needed by 
kiwi-desc-oemboot-requires, nothing provides ERROR_NO_DEPENDENCIES_FOUND needed 
by kiwi-desc-oemboot-requires"

Any idea why? I know we already had this error in the past. Cannot remember if 
it was due to an OBS config or a kiwi problem.


Guillaume

-- 
To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org
To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org