Hi all,
Neither the 12.3 and 13.1 image boot on Pandaboard-ES Rev B3 because
the Modification of Elpida DDR2 RAM
Here follows the serial port messages:
U-Boot SPL 2013.04 (Jan 08 2014 - 14:33:37) OMAP4460 ES1.1 SDRAM:
identified size not same as expected size identified: 0 expected:
40000000
Regards,
SunYu
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
Is the JEOS for the Beaglebone suitable for the
Beaglebone Black? Specifically as found on this page.
> http://download.opensuse.org/ports/armv7hl/distribution/13.1/appliances/
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
Hi,
I'm currently trying to bring up a uEVM board, and have what I believe
all the correct components for it [0]. Regardless of having a dtb
package and using kernel 3.14-rc2 it still fails to boot, with u-boot
complaining. Below is my boot log, does anyone have ideas/tips to
resolve this?
U-Boot SPL 2014.01 (Feb 25 2014 - 21:55:07)
OMAP5432 ES2.0
U-Boot 2014.01 (Feb 25 2014 - 21:55:07)
CPU : OMAP5432 ES2.0
Board: OMAP5432 uEVM
I2C: ready
DRAM: 2 GiB
MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
Using default environment
SATA link 0 timeout.
AHCI 0001.0300 32 slots 1 ports 3 Gbps 0x1 impl SATA mode
flags: 64bit ncq stag pm led clo only pmp pio slum part ccc apst
scanning bus for devices...
Found 0 device(s).
Net: No ethernet found.
Hit any key to stop autoboot: 0
mmc0 is current device
SD/MMC found on device 0
** Unrecognized filesystem type **
4713776 bytes read in 271 ms (16.6 MiB/s)
** File not found /boot/omap5-uevm.dtb **
Booting from mmc0 ...
Kernel image @ 0x80200000 [ 0x000000 - 0x47ed30 ]
ERROR: Did not find a cmdline Flattened Device Tree
Could not find a valid device tree
mmc1(part 0) is current device
SD/MMC found on device 1
** Unrecognized filesystem type **
** No partition table - mmc 1 **
I'm hoping to be able to demo this at Linaro Connect next week with Xen
running ontop.
Thanks,
Andy
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
I tried to replace both of the files in Factory image by:
cp arch/arm/boot/zImage /MySdcard/boot/zImage
cp arch/arm/boot/dts/omap4-panda-es.dtb /MySdcard/boot/dtb/omap4-panda-es.dtb
still sticks at Starting kernel ...
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
Hi,
I'm hoping to create a new image for testing on the OMAP5 powered uEVM
board. I've successfully built the kernel and dtb packages (using
3.14-rc3) and would now like to get it all into a usable package. I
was thinking of creating a new image called OMAP5 to prevent any
confusion. I've got a copy of the JeOS package but I'm not 100% sure
on which files I need to edit.
Am I correct in thinking I need to edit Images.kiwi.in and pre_checkin.sh?
My understanding is that I can re-use the panda components, just
replace the dtb-omap4 with dtb-omap5 as kernel and u-boot packages
should be fine.
Thanks,
Andy
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
I know I've been grumbling about this for at least today on IRC, but
I'm aware that not everyone is on IRC. At present I'm trying to reboot
my Arndale board using the Factory image, and failing :(
Firstly, neither shutdown, reboot or init 0, init 6 commands work.
Secondly, if I do a hard poweroff and poweron the system fails to boot
properly and drops me to the maintenance shell as it can't find the
root device, it cant find the disk by id.
Has anyone else replicated this issue, doesn't have to be on an Arndale?
Also if anyone has any clues, as to how to resolve it I'd appreciate it.
Thanks,
Andy
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
Hi,
are the latest Chromebook images supposed to work? I tried the most recent
Factory-ARM-XFCE-chromebook.armv7l-1.12.1-Build169.2 (of today) and got
-----
** File not found uEnv.txt
Loading file "boot.scr" from mmc device 1:2 (lxboot)
2138 bytes read
Running bootscript ...
## Executing script at 40007000
mmc_init err 0, time 101923
mmc0(part 0) is current deuice
Loading file "boot/linux.vmx" from mmc deuice 0:2 (KERN-A)
Failed to mount ext2 filesystem ...
** Bad ext2 partition or disk — mmc 0:2 **
mmc1 is current device
Loading file "boot/linux.vmx" from mmc device 1:2 (lxboot)
3568304 bytes read
Loading file "boot/initrd.uboot" from mmc device 1:2 (lxboot)
** ext2fs doesn't support tripple indirect blocks. **
** Unable to read "boot/initrd.uboot" from mmc 1:2 **
Loading file "dtb/exynos5250—snow.dtb" from mmc device 1:2 (lxboot)
34150 bytes read
## Booting kernel from Legacy Image at 40007000 ...
Image Name: Linux—3.4.0—2—chromebook
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3568240 Bytes = 3.4 MiB
Load address: 40008000
Entry Point: 40008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 4f000000 ...
Image Name: Initrd
Image Type: ARM Linux RAMDisk Image (uncompressed)
Data Size: 156490936 Bytes = 149.2 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... Bad Data CRC
Ramdisk image is corrupt or invalid
mmc0(part 0) is current device
** Block device usb 0 not supported
mmc1 is current device
** Block device usb 1 not supported
(Re)start USB...
USB: Register 1313 NbrPorts 3
[USB] usb_lowlevel_init:852 0
[USB] usb_lowlevel_init:852 1
USB EHCI 1.00
1 USB Device(s) found
scanning bus for storage devices ... 0 Storage Device(s) found
Tring USB on device
** Block device usb 0 not supported
** Block device usb 0 not supported
SMDK5250 #
-----
on initial boot. Same result with most recent 13.1 images.
Best regards,
--D.B.
--
Daniel Bischof <suse-bugz(a)bischof.org>
Hi,
Could you, trigger rebuild of openSUSE:Factory:ARM > ImageMagick.
It will fix E17 and XFCE images in factory (especially for chromebook) because libwebp has been update from version 4 to version 5.
OBS should really trigger a rebuild if package deps are rebuilt.
Guillaume
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
I could not find the package clamav on the openSUSE 13.1 repository for
armv6hl (Raspberry Pi).
Checking the openSUSE build service it appears that clamav is locked, so no
longer build, in that repository, but in a security repository, which does not
do a build for armv6hl. In the security repository the package is build OK for
the enabled architectures.
How can I be of help to make it build for armv6hl and other architectures?
--
fr.gr.
member openSUSE
Freek de Kruijf
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org