Thanks again for your replies.
I downloaded the 3.9-rc5 kernel from kernel.org
and it seems to have armada 370 support
(which is my mirabox) so I started with the .config from the 220.127.116.11 debian mirabox
kernel and did "make olddefconfig", then make, etc.
"make uImage" complained about a missing LOADADDR so I did "make
LOADADDR=0x0008000 uImage". Everything compiled nicely and then I booted with it, and
the bootlog is as follows:
3460464 bytes read
## Booting kernel from Legacy Image at 06400000 ...
Image Name: Linux-3.9.0-rc5
Created: 2013-04-07 10:10:29 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3460400 Bytes = 3.3 MB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
Starting kernel ...
... and then nothing more. I tried to ping but to no avail.
In my .config are (amongst others):
# CPU Core family selection
# CONFIG_ARCH_MULTI_V6 is not set
# CONFIG_ARCH_MULTI_CPU_AUTO is not set
# Marvell SOC with device tree
# CONFIG_MACH_ARMADA_XP is not set
# CONFIG_ARCH_BCM is not set
# CONFIG_GPIO_PCA953X is not set
# CONFIG_ARCH_HIGHBANK is not set
# CONFIG_ARCH_MXC is not set
# CONFIG_ARCH_OMAP2PLUS is not set
# CONFIG_ARCH_SOCFPGA is not set
# CONFIG_ARCH_SUNXI is not set
You also gave as an option:
Subject: Re: [opensuse-arm] OpenSUSE 12.3 for armv7 on
Date: Sat, 6 Apr 2013 23:21:30 +0200
> Oh, I just realized that you're running on 2.6.35. There's a good chance
your kernel is simply too old, which probably is why udev is failing.
> Are there any more recent kernels available for your machine?
no, not that I know of.
Compile the kernel as zImage, then the device tree
that comes with Linux (arch/arm/boot/dts/armada-370-mirabox.dts) to a dtb and then load
both from u-boot? You just pass the dtb as 3rd parameter to the bootz command. If you run
without an initrd, just pass "-" to bootz to tell it you don't want one.
I'd assume that should just work, and should also get you something properly working
with openSUSE 12.3. No guarantees that all your hardware components will be supported by
the upstream code however :). Traditionally, we've had quite a bit of trouble getting
I think I understand what you write (except for the dts/dtb) but my uboot loader
doesn't have a bootz, so I don't know how to continue with this suggestion.
Any more suggestions are highly appreciated,
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org