[How-To] update DStar/PP/GFlex to new uBoot for kernel>3.2

This forum is for Marvell Kirkwood devices such as the GoFlex Home/Net, PogoPlug v1/v2, SheevaPlug, and ZyXEL devices.

Re: [How-To] update DStar/PP/GFlex to new uBoot for kernel>3

Postby shinji257 » Thu Nov 29, 2012 2:41 am

Well I followed the directions here --> http://archlinuxarm.org/platforms/armv5 ... 2-pinkgray

It doesn't mention setting an arcNumber. I'll have to see what it is set to when I get into work and check it then.
shinji257
 
Posts: 8
Joined: Thu Feb 16, 2012 3:43 am

Re: [How-To] update DStar/PP/GFlex to new uBoot for kernel>3

Postby nnslick » Sun Dec 09, 2012 4:39 pm

Hi All,

Just a note on LED color from my experience...

With help and inspiration from moonman (thanks moonman!), I was able to roll my own customized kernels for my Dockstar, Pogoplug V2 and Goflex Home :D . I configured my kernels to bare minimum and specific to the target machine and the LED color works as designed, e.g. green after successful boot-up. So it looks like there are some conflicts in the kernel logic for LED when it is configured to support multiple types of Kirkwood, or the machine type was not correctly detected at boot time.

I am OK with multiple 'make', one of each of my machines, since it takes only about one hour to make kernel packages from scratch on my Pogoplug E02 (with kernel source version 3.6.4-1 from github).

I notice that moonman posted about newer kernel version but it looks like it is not available for ALARM kirkwood yet on github. How do I get the PKGBUILDs info for new kernel releases to build kernels for kirkwood machines?

Thanks and happy Linux'ing :) !

nnSlick
nnslick
 
Posts: 11
Joined: Fri Feb 03, 2012 3:11 pm

Re: [How-To] update DStar/PP/GFlex to new uBoot for kernel>3

Postby shinji257 » Sun Dec 09, 2012 4:41 pm

How did you compile the kernels?
shinji257
 
Posts: 8
Joined: Thu Feb 16, 2012 3:43 am

Re: [How-To] update DStar/PP/GFlex to new uBoot for kernel>3

Postby WarheadsSE » Sun Dec 09, 2012 4:42 pm

LED control is based on the arcNumber until dts.
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6807
Joined: Mon Oct 18, 2010 2:12 pm

Re: [How-To] update DStar/PP/GFlex to new uBoot for kernel>3

Postby moonman » Sun Dec 09, 2012 4:55 pm

$this->bbcode_second_pass_quote('', 'I') notice that moonman posted about newer kernel version but it looks like it is not available for ALARM kirkwood yet on github. How do I get the PKGBUILDs info for new kernel releases to build kernels for kirkwood machines?


The link is in the thread: I've just cloned the archlinuxarm github repo and updated it:
Thread: viewtopic.php?f=18&t=3671
Github: https://github.com/moonman/PKGBUILDs/tr ... x-kirkwood
Pogoplug V4 | GoFlex Home | Raspberry Pi 4 4GB | CuBox-i4 Pro | ClearFog | BeagleBone Black | Odroid U2 | Odroid C1 | Odroid XU4
-----------------------------------------------------------------------------------------------------------------------
[armv5] Updated U-Boot | [armv5] NAND Rescue System
moonman
Developer
 
Posts: 3387
Joined: Sat Jan 15, 2011 3:36 am

Re: [How-To] update DStar/PP/GFlex to new uBoot for kernel>3

Postby shinji257 » Sun Dec 09, 2012 5:55 pm

$this->bbcode_second_pass_quote('WarheadsSE', 'L')ED control is based on the arcNumber until dts.


For a PogoPlug E02 what should the arcNumber be set to? Currently mine is set to 2097. I tried 3542 but I seemed to get the same result.

P.S. For additional data.
Running kernel 3.6.4 using newest uBoot. Booted back into stock PogoPlug OS and LED works normally even when arcNumber is 2097 but it may not be relevant.
shinji257
 
Posts: 8
Joined: Thu Feb 16, 2012 3:43 am

Re: [How-To] update DStar/PP/GFlex to new uBoot for kernel>3

Postby WarheadsSE » Sun Dec 09, 2012 6:37 pm

The CE kernel is hard-coded to use the right ones.
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6807
Joined: Mon Oct 18, 2010 2:12 pm

Re: [How-To] update DStar/PP/GFlex to new uBoot for kernel>3

Postby nnslick » Sun Dec 09, 2012 7:19 pm

@shinji257
I just follow this post:
viewtopic.php?f=18&t=3837

I edited the PKGBUILD file to uncomment make nconfig to configure the kernel before issuing the makepkg --asroot command.

@moonman
Thanks much! I will try to built the newest kernels using your git hub branch.
nnslick
 
Posts: 11
Joined: Fri Feb 03, 2012 3:11 pm

Re: [How-To] update DStar/PP/GFlex to new uBoot for kernel>3

Postby BDX » Fri Dec 14, 2012 11:51 pm

Just what the heck I do wrong? I have GoFlex Home and I followed the instructions step-by-step.

I get this:
$this->bbcode_second_pass_code('', 'U-Boot 2011.12 (Apr 18 2012 - 23:08:20)
Seagate GoFlexNet
arm-none-linux-gnueabi-gcc (Sourcery G++ Lite 2009q3-67) 4.4.1
GNU ld (Sourcery G++ Lite 2009q3-67) 2.19.51.20090709
Hit any key to stop autoboot: 0

Reset IDE: Bus 0: OK Bus 1: not available
Device 0: Model: ST2000DL001-9VT156 Firm: CC98 Ser#: 5YD9PS0R
Type: Hard Disk
Supports 48-bit addressing
Capacity: 1907729.0 MB = 1863.0 GB (-387938128 x 512)
Loading file "/boot/uImage" from ide device 0:1 (hda1)
2856016 bytes read
Loading file "/boot/uInitrd" from ide device 0:1 (hda1)
** File not found /boot/uInitrd
## Booting kernel from Legacy Image at 00800000 ...
Image Name: Linux-3.1.10-13-ARCH
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2855952 Bytes = 2.7 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK

Starting kernel ...')

$this->bbcode_second_pass_code('', '[ 23.892508] VFS: Cannot open root device "sda1" or unknown-block(0,0)
[ 23.899001] Please append a correct "root=" boot option; here are the available partitions:
[ 23.907449] 1f00 1024 mtdblock0 (driver?)
[ 23.912585] 1f01 4096 mtdblock1 (driver?)
[ 23.917691] 1f02 32768 mtdblock2 (driver?)
[ 23.922808] 1f03 224256 mtdblock3 (driver?)
[ 23.927909] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[ 23.936270] [<c000d290>] (unwind_backtrace+0x0/0xe0) from [<c03c6d14>] (panic+0x58/0x198)
[ 23.944529] [<c03c6d14>] (panic+0x58/0x198) from [<c052ac2c>] (mount_block_root+0x230/0x280)
[ 23.953051] [<c052ac2c>] (mount_block_root+0x230/0x280) from [<c052af3c>] (prepare_namespace+0x160/0x1c0)
[ 23.962701] [<c052af3c>] (prepare_namespace+0x160/0x1c0) from [<c052a8c8>] (kernel_init+0x11c/0x14c)
[ 23.971904] [<c052a8c8>] (kernel_init+0x11c/0x14c) from [<c000945c>] (kernel_thread_exit+0x0/0x8)')

And stuck. Please help me.
BDX
 
Posts: 10
Joined: Tue Sep 18, 2012 7:13 pm

Re: [How-To] update DStar/PP/GFlex to new uBoot for kernel>3

Postby moonman » Sat Dec 15, 2012 2:22 am

What steps exactly did you do?

$this->bbcode_second_pass_code('', 'Please append a correct "root=" boot option; here are the available partitions:
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)')

interrupt the uboot and show the output of "printenv"
Pogoplug V4 | GoFlex Home | Raspberry Pi 4 4GB | CuBox-i4 Pro | ClearFog | BeagleBone Black | Odroid U2 | Odroid C1 | Odroid XU4
-----------------------------------------------------------------------------------------------------------------------
[armv5] Updated U-Boot | [armv5] NAND Rescue System
moonman
Developer
 
Posts: 3387
Joined: Sat Jan 15, 2011 3:36 am

PreviousNext

Return to Marvell Kirkwood

Who is online

Users browsing this forum: No registered users and 13 guests