Re: [opensuse-arm] JeOS image status (Beagle, Panda, Arndale and chromebook tested)

2014-09-09 Thread Guillaume Gardet
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

Re: [opensuse-arm] JeOS image status (Beagle, Panda, Arndale and chromebook tested)

2014-09-09 Thread Alexander Graf
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

Re: [opensuse-arm] JeOS image status (Beagle, Panda, Arndale and chromebook tested)

2014-09-09 Thread Andreas Schwab
Guillaume Gardet guillaume.gar...@free.fr writes: There is a Prefer: dracut in Factory project config and mkinitrd package have been removed from factory. So, I guess we should use dracut directly? The dracut package contains the mkinitrd wrapper. Andreas. -- Andreas Schwab, SUSE Labs,

Re: [opensuse-arm] JeOS image status (Beagle, Panda, Arndale and chromebook tested)

2014-09-09 Thread Guillaume Gardet
Le 09/09/2014 11:54, Andreas Schwab a écrit : Guillaume Gardet guillaume.gar...@free.fr writes: There is a Prefer: dracut in Factory project config and mkinitrd package have been removed from factory. So, I guess we should use dracut directly? The dracut package contains the mkinitrd

Re: [opensuse-arm] JeOS image status (Beagle, Panda, Arndale and chromebook tested)

2014-09-09 Thread Guillaume Gardet
Just tested last factory build (201.1) with omap loadaddr and arndale boot type fixes and new u-boot (2014.10-rc2). Dracut initrd is VERY long to generate on (first boot). Any idea why? Beagle has a working console on serial port, but no video output, no USB and no Ethernet (connected on

Re: [opensuse-arm] JeOS image status (Beagle, Panda, Arndale and chromebook tested)

2014-09-08 Thread Alexander Graf
On 08.09.14 15:26, Guillaume Gardet wrote: Hi, Fatcory:ARM repo has new JeOS (E17 and XFCE) images but there are some ghost files remaining. Pandaboard and Beagleboard boots u-boot but then hangs after Starting kernel Beagle should use a newer u-boot managing FDT for Beagle. Is

Re: [opensuse-arm] JeOS image status (Beagle, Panda, Arndale and chromebook tested)

2014-09-08 Thread Alexander Graf
On 08.09.14 17:50, Guillaume Gardet wrote: Le 08/09/2014 16:01, Alexander Graf a écrit : On 08.09.14 15:26, Guillaume Gardet wrote: Hi, Fatcory:ARM repo has new JeOS (E17 and XFCE) images but there are some ghost files remaining. Pandaboard and Beagleboard boots u-boot but then hangs

Re: [opensuse-arm] JeOS image status (Beagle, Panda, Arndale and chromebook tested)

2014-09-08 Thread Guillaume Gardet
Le 08/09/2014 17:57, Alexander Graf a écrit : On 08.09.14 17:50, Guillaume Gardet wrote: Le 08/09/2014 16:01, Alexander Graf a écrit : On 08.09.14 15:26, Guillaume Gardet wrote: Hi, Fatcory:ARM repo has new JeOS (E17 and XFCE) images but there are some ghost files remaining. Pandaboard