[KERNEL] Kirkwood kernel 3.11 for testing. No aufs.

[moonman]

Here's the new kernel if anybody wants to test.

Kernel:
$this->bbcode_second_pass_code('', 'pacman -U http://dl.dropboxusercontent.com/u/15043728/ArchLinuxArm/kernels/3.11.0/linux-kirkwood-3.11-1-arm.pkg.tar.xz')

Headers:
$this->bbcode_second_pass_code('', 'pacman -U http://dl.dropboxusercontent.com/u/15043728/ArchLinuxArm/kernels/3.11.0/linux-headers-kirkwood-3.11-1-arm.pkg.tar.xz')

Patch:
$this->bbcode_second_pass_code('', 'https://dl.dropboxusercontent.com/u/15043728/ArchLinuxArm/kernels/3.11.0/archlinuxarm.patch')

[wiley]

Neither this kernel nor the linux-kirkwood kernel in the repositories will boot on my Dreamplug. I'm currently running a custom 3.11 kernel, so I don't think it's because of an old U-Boot version.

I'll try to compare the configs tonight and see if anything sticks out, but are you aware of any problems with Dreamplug support?

[moonman]

Did you use the same patch to build your own kernel? Also a bootlog would be helpful to pinpoint the problem.

[wiley]

My current kernel is an unpatched mainline 3.11.
As for linux-kirkwood, there is no bootlog - the system hangs after U-Boot uncompresses the kernel.

I did notice that if I don't set machid in U-Boot, it defaults to 3550, and the linux-kirkwood kernel gives me a nice error about an unrecognized machine ID. My own kernel just hangs and doesn't produce any output.
I've always set it to 2659 in the past (which apparently makes my Dreamplug pretend to be a Guruplug?), and with that, my own kernel boots but linux-kirkwood hangs as described.

[moonman]

So your kernel doesn't work, but in the previous post you said it did. I'm confused. What was the last kernel that did work?

[wiley]

Sorry, I was unclear. I went back and edited my post.

[moonman]

Ok it makes sense now. But i would still like to know the last linux-kirkwood that worked. Or did it ever?

[moonman]

See if this one works:
$this->bbcode_second_pass_code('', 'http://dl.dropboxusercontent.com/u/15043728/ArchLinuxArm/kernels/3.11-dreamplug/linux-kirkwood-3.11-2-arm.pkg.tar.xz')
This was specifically patched for dreamplug so you need to use arcnumber=3550

[wiley]

Yes, that boots with arcNumber=3550. Thanks!
The kernel boot logs are less verbose, though I think that's included in the Arch kernel patch?

Edit: LEDs are partially present and a bit broken.
Here's the correspondence between the Guruplug LED names I was using and the Dreamplug LEDs:
guruplug:green:wmode -> dreamplug:blue:ap
These *should* match based on the Dreamplug name, but if I try to change the trigger mode on the Dreamplug LED, the box reboots instantly.

guruplug:red:wmode -> dreamplug:green:wifi
Working normally.

guruplug:green:health -> ???
There is no matching LED for this. If I follow the previous naming scheme, this LED would be dreamplug:blue:bt.


I doubt it matters now, but I don't really know how long it's been since linux-kirkwood ran on this box. Shortly after moving from Debian to ALARM, I started compiling kernels from the wireless-testing tree to get improvements to the mwifiex driver because I wanted to use my plug as an AP. I've basically given up on that now - Marvell seems incapable of building anything stable.

Anyway, if you could put up the patch somewhere, I'd be interested in fiddling with LED support.

Thanks again.

[moonman]

$this->bbcode_second_pass_code('', 'http://dl.dropboxusercontent.com/u/15043728/ArchLinuxArm/kernels/3.11-dreamplug/archlinuxarm.patch')
That's the patch. I was going to include it in the official, but since you say not all things work I won't for now. When you figure out LEDs, post back with the changes and I'll integrate it with the rest. The boardfile is the same for guruplug and dreamplug so look in arch/arm/mach-kirkwood/guruplug-setup.c