GoFlex Net and 2.6.39 kernel?

Hi,

I wonder if someone managed to boot GoFlex Net (with arcNumber 3089) with a self compiled 2.6.39 vanilla kernel.

I'm currently using this patch and if I compile a 2.6.38 vanilla kernel everything works just fine. But a 2.6.39 kernel always fails to boot. Are there some new patches necessary?

PS I'm using the usual Jeff's guide, nothing special concerning toolchain etc.

EDIT: I've just checked the 2.6.38.8 out: GoFlex Net boots flawlessly. So what's wrong about 2.6.39? :((



Edited 2 time(s). Last edit at 08/16/2011 03:46PM by Vlad.

I had compiled 2.6.39.2 and 2.6.38.8 few weeks back and it seemed to work fine. Maybe you can try it? Here are the links

http://www.varkey.in/files/kernel-goflex-dockstar-2.6.39.2-varkey.deb
http://www.varkey.in/files/kernel-goflex-dockstar-2.6.38.8-varkey.deb

Hi varkey,

I've just tried out your 2.6.39.2 kernel with the same sad result -> no boot. Via netconsole I can set that it goes up to "Starting kernell ..." but when I check "nc -lu 10.10.10.4 6666" for the kernel messages to appear it stays empty. As I've already mentioned all 2.6.38.x self-compiled kernels work just fine.

Since you also have a GoFlex Net which does boot 2.6.39 kernels , the only thing I can think about is UBIT. I'm using UBIT v0.6. Do you have it too, or are you still on v0.5?



Edited 1 time(s). Last edit at 08/17/2011 07:32AM by Vlad.

You won't get any netconsole messages from the kernel unless you also add netconsole configuration to the kernel parameter list. This even requires that you specify the destination MAC address as there's no ARP resolution available yet.

kraqh3d Wrote:
-------------------------------------------------------
> You won't get any netconsole messages from the
> kernel unless you also add netconsole
> configuration to the kernel parameter list. This
> even requires that you specify the destination MAC
> address as there's no ARP resolution available
> yet.

I do get netconsole messages when a kernel is booting properly and netconsole is in my bootargs. I was talking about 2.6.39 kernels only that don't boot and thus don't produce any netconsole messages.

Ok I was just checking. If you don't add netconsole to the kernel parameters, you won't get anything after "Starting Kernel..." from u-Boot.

No problem. Well, it looks like guys from the Archlinux ARM Project have managed to run the 3.0.1 kernel on GoFlex Net.
https://github.com/archlinuxarm/PKGBUILDs/tree/22366d0b3f3734d82346b3d4c1f987364936bdca/core/linux
Perhaps I should try to apply their patch to a vanilla 3.0.1 and check whether that one boots. The good thing is that archers seem to use Ubit v0.6 just like me.

SUCCESS!!!
The 3.0.1 vanilla kernel with that Archlinux ARM Project patch boots. The only thing is that if you use their config (as I did) you should better replace

CONFIG_LOCALVERSION="-ARCH"

by

CONFIG_LOCALVERSION="-ubit"

Don't know why but until I did this, make-kpkg always failed with that weird "wrong file name" error.