Linux 3.3.2 kernel for Dockstar, GoFlex and many others

All credits go to Jeff and Davygravy:
http://forum.doozan.com/read.php?2,524

But in newer crosscompile you'll need to use a workaround to compile armel packages... I'll try to find my steps to use tomorrow... (but I found it somewhere here or using Google...)

Just for the records: If compiling with make-kpkg fails, try the following command.

DEB_HOST_ARCH=armel fakeroot make-kpkg --arch arm --cross-compile arm-none-linux-gnueabi- --append-to-version=-kirkwood --revision=1.0 --initrd -j 2 kernel_image kernel_headers

Ok, here is the 3.8.4 kernel, compiled with ipv6 and netfilter (iptables) support:
http://download.prodigy7.de/files/packages/kirkwood/kernel/

Because I've changed the name from dockstar to kirkwood, the dpkg package manager detect the kernel type and install the kernel additionally with mkimage on pogo plug v2. So if the package is installed with dpkg, directly the uImage and uInitrd is refreshed in /boot and nothing more is to do!



Edited 1 time(s). Last edit at 05/14/2013 11:51AM by prodigy7.

prodigy7 Wrote:
-------------------------------------------------------
. So if the package is
> installed with dpkg, directly the uImage and
> uInitrd is refreshed in /boot and nothing more is
> to do!
... except maybe to save the old uImage and uInitrd before the installation. But thank you, I always had to look for the commands to create the files in the forum.

Hi,

I tried many kernels, including this 3.8.4 from prodigy7. But none of them will boot, my Goflex Net is stuck at "Starting kernel...". The 3.3.2-kirkwood-dg kernel boots fine from an ext2 usb stick and two SATA HDD attached. Any ideas what is wrong with my config? This is my environment:

ethact=egiga0
bootdelay=3
baudrate=115200
mainlineLinux=yes
console=ttyS0,115200
led_init=green blinking
led_exit=green off
led_error=orange blinking
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
mtdids=nand0=orion_nand
partition=nand0,2
stdin=serial
stdout=serial
stderr=serial
rescue_set_bootargs=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts $rescue_custom_params
rescue_bootcmd=if test $rescue_installed -eq 1; then run rescue_set_bootargs; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000; else run pogo_bootcmd; fi
pogo_bootcmd=if fsload uboot-original-mtd0.kwb; then go 0x800200; fi
force_rescue=0
force_rescue_bootcmd=if test $force_rescue -eq 1 || ext2load usb 0:1 0x1700000 /rescueme 1 || fatload usb 0:1 0x1700000 /rescueme.txt 1; then run rescue_bootcmd; fi
ubifs_mtd=3
ubifs_set_bootargs=setenv bootargs console=$console ubi.mtd=$ubifs_mtd root=ubi0:rootfs rootfstype=ubifs $mtdparts $ubifs_custom_params
ubifs_bootcmd=run ubifs_set_bootargs; if ubi part data && ubifsmount rootfs && ubifsload 0x800000 /boot/uImage && ubifsload 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; fi
usb_scan=usb_scan_done=0;for scan in $usb_scan_list; do run usb_scan_$scan; if test $usb_scan_done -eq 0 && ext2load usb $usb 0x800000 /boot/uImage 1; then usb_scan_done=1; echo "Found bootable drive on usb $usb"; setenv usb_device $usb; setenv usb_root /dev/$dev; fi; done
usb_scan_list=1 2 3 4
usb_scan_1=usb=0:1 dev=sda1
usb_scan_2=usb=1:1 dev=sdb1
usb_scan_3=usb=2:1 dev=sdc1
usb_scan_4=usb=3:1 dev=sdd1
usb_device=0:1
usb_root=/dev/sda1
usb_rootfstype=ext2
usb_rootdelay=10
usb_set_bootargs=setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts $usb_custom_params
usb_bootcmd=run usb_init; run usb_set_bootargs; run usb_boot
usb_boot=mw 0x800000 0 1; ext2load usb $usb_device 0x800000 /boot/uImage; if ext2load usb $usb_device 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
bootcmd=usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run rescue_bootcmd; run pogo_bootcmd; reset
ethaddr=00:10:75:26:69:81
rescue_installed=1
arcNumber=3089
serverip=10.11.11.20
ipaddr=10.11.11.30
if_netconsole=ping $serverip
preboot=run if_netconsole start_netconsole
start_netconsole=setenv ncip 10.11.11.20; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
usb_init=run usb_scan ; setenv usb_root LABEL=rootfs

Regards,
Wolfgang

Did you already update your uBoot?
http://forum.doozan.com/read.php?3,6965

But be careful - for some reason I needed to change my machid after this update to get any kernel up and running.
But I assume, you have a working serial console, don't you?

Yes the uBoot is recent. I am certain because i also tried a fresh install of wheezy with another usb stick. The install script did check the uBoot and reported an up-to-date one and did not flash a new one.

Sadly i don´t own a serial cable and can not provide any more info other than the netconsole output which stops at "Starting kernel...". What do you mean by changing the machid? I don´t even know what that is :-)

EDIT: Sorry, didn´t read the complete thread you posted. I will try the machid setting tomorrow..

EDIT 2: Did try "c11" for machid ( because of arcNumber=3089 ), did not boot. Tried "dd6", not even the rescue system from nand would boot anymore and i had to fix it via netconsole. What is the correct setting for a Goflex Net?



Edited 2 time(s). Last edit at 06/10/2013 06:37PM by wolfgangn.

@wolfgangn,

when updating to wheezy just the other day, I ran into a problem I had long since forgotten: when using the same stick on different machines, it seemingly leads to the second one not "booting", when, in fact, it just does not get an IP-Address. In netconsole, it will look as if it was stuck at "Starting kernel ..." The reason is the file

/etc/udev/rules.d/70-persistent-net.rules

which is newly generated via

/lib/udev/rules.d/75-persistent-net-generator.rules

Myself, I always remove these two files and never had any problem with that.

---
Standart ist der Standardfehler

Deleted the file, but still does not boot. I think I have to get a serial cable to see what fails...

Thank you for your reply!

Hi,
have you found kernel headers?

Thanks,
Mario

Hi again,

I got my serial cable, here is the output of a 3.8.4 kernel:

.........
[ 30.989456] md: ... autorun DONE.
[ 30.992888] VFS: Cannot open root device "LABEL=rootfs" or unknown-block(0,0): error -6
[ 31.000940] Please append a correct "root=" boot option; here are the available partitions:
[ 31.009337] 1f00 1024 mtdblock0 (driver?)
[ 31.014418] 1f01 4096 mtdblock1 (driver?)
[ 31.019510] 1f02 32768 mtdblock2 (driver?)
[ 31.024592] 1f03 224256 mtdblock3 (driver?)
[ 31.029686] 0800 3915776 sda driver: sd
[ 31.034333] 0801 3711697 sda1 99b8a5b2-01
[ 31.039252] 0802 203280 sda2 99b8a5b2-02
[ 31.044161] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[ 31.052488] [<c00142c8>] (unwind_backtrace+0x0/0xe0) from [<c0502cb4>] (panic+0x78/0x1d4)
[ 31.060718] [<c0502cb4>] (panic+0x78/0x1d4) from [<c06e7c80>] (mount_block_root+0x268/0x2bc)
[ 31.069204] [<c06e7c80>] (mount_block_root+0x268/0x2bc) from [<c06e7e54>] (prepare_namespace+0x120/0x180)
[ 31.078821] [<c06e7e54>] (prepare_namespace+0x120/0x180) from [<c05018bc>] (kernel_init+0x8/0xe4)
[ 31.087745] [<c05018bc>] (kernel_init+0x8/0xe4) from [<c000df30>] (ret_from_fork+0x14/0x24)

The USB stick is labeled "rootfs":
/dev/sda1: LABEL="rootfs" UUID="f260bcee-8c9d-4e41-a795-752752e9b152" TYPE="ext2"

And the environment is set up to "rootfs" label:
usb_init=run usb_scan ; setenv usb_root LABEL=rootfs

What did I miss?


*** THIS IS SOLVED, I tried SHYD´s 3.9.5 kernel and it worked out of the box, I have no idea what his kernel includes/excludes, but it works :-) ***



Edited 1 time(s). Last edit at 06/27/2013 12:26PM by wolfgangn.

Ben, I had the same error but continued and am now at 3.9.5 everything worked fine here

Hi, can someone post the kernel config again? The link in post #1 is not working anymore... Also, was this kernel built with any sort of patch files?

Thanks,



Edited 1 time(s). Last edit at 11/04/2013 09:19PM by gee-man.

gee-man Wrote:
-------------------------------------------------------
> Hi, can someone post the kernel config again? The
> link in post #1 is not working anymore... Also,
> was this kernel built with any sort of patch
> files?
>
> Thanks,

You can find the kernel config file in /boot directory. Should be something like this:
config-3.3.2.xx-kirkwood-xxx

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Just use the link Kirkwood Downloads from the first post and you can find everything you need.

- shv

Is it safe to apply the patch file from 3.3.2 to the 3.12 kernel source and then build it with the 3.3.2 kernel configuration?

The config file in the first post is not available .
Can someone upload it again ?
Thanks in advance.

Big Pogo Fan Wrote:
-------------------------------------------------------
> The config file in the first post is not available
> .
> Can someone upload it again ?
> Thanks in advance.


See this thread for newer kernel, if that's what you are looking for:
http://forum.doozan.com/read.php?2,12096

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)