Linux 3.3.2 kernel for Dockstar, GoFlex and many others

Re: Linux 3.3.2 kernel for Dockstar, GoFlex and many others

HellG — Wed, 15 May 2013 05:52:31 -0400

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.

Re: Linux 3.3.2 kernel for Dockstar, GoFlex and many others

prodigy7 — Tue, 14 May 2013 12:51:25 -0400

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!

Re: Linux 3.3.2 kernel for Dockstar, GoFlex and many others

prodigy7 — Tue, 14 May 2013 11:29:36 -0400

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

Re: Linux 3.3.2 kernel for Dockstar, GoFlex and many others

Sven — Mon, 13 May 2013 17:10:05 -0400

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...)

Re: Linux 3.3.2 kernel for Dockstar, GoFlex and many others

prodigy7 — Mon, 13 May 2013 11:14:25 -0400

Hi sven!

Thx for your quick response! Currently I compile a kernel with ipv6 enabled on my pogo plug (it takes a little bit time ;-) ). If so far it contains all I need, I would post the modified config file. If you could give me a quick how to, i would also generate a deb-Package!

prodigy7

Re: Linux 3.3.2 kernel for Dockstar, GoFlex and many others

Sven — Mon, 13 May 2013 11:10:40 -0400

I tried to keep it as small as possible, but you're right - I could have compiled it at least with IPv6 modules...

You could do so yourself using the provided DIFF to apply the changes to the original kernel:
https://www.kernel.org/pub/linux/kernel/v3.x/linux-3.8.4.tar.bz2

Otherwise please apply all your changes to the .config and send this, so I'll compile it for you.
If you are not familiar with all of this - do you want IPv6 modules, or included in the kernel?

Re: Linux 3.3.2 kernel for Dockstar, GoFlex and many others

prodigy7 — Mon, 13 May 2013 10:59:19 -0400

Sven Wrote:
-------------------------------------------------------
> You could try my 3.8.4 with NSA320 enabled:
> https://www.dropbox.com/sh/ifotsfsca9kqg7q/Dda2OXW
> SdZ

Hi Sven,

thank you very much for your refreshed kernel version. Could you maybe compile a ipv6 enabled version for me? For different reasons I can run the box only in a ipv6 network and currently I can't reach the box with your kernel because you've disabled the complete ipv6 support.
Would be very happy if that would be possible!

Thx!
prodigy7

Re: Linux 3.3.2 kernel for Dockstar, GoFlex and many others

HellG — Sat, 11 May 2013 03:16:48 -0400

I am using the uboot provided by davygravy in the first post here: http://forum.doozan.com/read.php?2,7806. Do you think the error could be uboot related?

Re: Linux 3.3.2 kernel for Dockstar, GoFlex and many others

gaogao — Sat, 11 May 2013 03:03:05 -0400

HellG Wrote:
-------------------------------------------------------
> Thank you, install in progress...
> Reboot... Works!
> ssh -l root nas.... Works!
> uname -a: "Linux nas 3.8.4-dockstar #2 Wed Mar 27
> 17:10:47 CET 2013 armv5tel GNU/Linux"
>
> So far, so good! I will see during the next days
> if I will have XFS errors again. Thanks again.

which uboot are you using?

Re: Linux 3.3.2 kernel for Dockstar, GoFlex and many others

HellG — Fri, 10 May 2013 13:59:15 -0400

Thank you, install in progress...
Reboot... Works!
ssh -l root nas.... Works!
uname -a: "Linux nas 3.8.4-dockstar #2 Wed Mar 27 17:10:47 CET 2013 armv5tel GNU/Linux"

So far, so good! I will see during the next days if I will have XFS errors again. Thanks again.

Re: Linux 3.3.2 kernel for Dockstar, GoFlex and many others

Sven — Fri, 10 May 2013 05:00:37 -0400

You could try my 3.8.4 with NSA320 enabled:
https://www.dropbox.com/sh/ifotsfsca9kqg7q/Dda2OXWSdZ

Re: Linux 3.3.2 kernel for Dockstar, GoFlex and many others

HellG — Thu, 09 May 2013 16:13:10 -0400

Hi,
does anybody use xfs filesystem with this kernel? I have my data on a xfs filesystem and face problems now and then that the filesystem cannot be mounted after reboot and I have to manually repair (with "-L" to wipe the journal) it. First I thought it is related to my old disks (WD10EACS, 5 years) on a GoFlex Net but after changing to a NSA320 with brand new harddisks (WD10EURX) I have the same problems.
Is there maybe another kernel version available for the NSA320 I could use and see if I still face the same errors?

HellG

Re: Linux 3.3.2 kernel for Dockstar, GoFlex and many others

bambo — Wed, 17 Apr 2013 08:49:34 -0400

ok, thanks a lot!
------------------

next problem, I wanted to boot 3.2.0 stock wheezy I had in /boot

so I tried to make it like this

mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-3.2.0-4 -d /boot/vmlinuz-3.2.0-4-kirkwood /boot/uImage
mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n Initrd-3.2.0-4 -d /boot/initrd.img-3.2.0-4-kirkwood /boot/uInitrd

netconsole output is ok, but Linux don't boot. How I can restore my last bootable kernel?
I was so euphoric so I didn't made a backup image of my system.

Re: Linux 3.3.2 kernel for Dockstar, GoFlex and many others

Sven — Wed, 17 Apr 2013 06:15:41 -0400

It just takes the files out of /dev/sda1 - and inside /boot/ dir.
But your boot is located on a separate partition:

Quote

/dev/sda1 on /boot

So a simple workaround to avoid these problems is to put a symbolic link named 'boot' to point to itself on this partition. Don't know why this was renamed to boot1 on your partition and there was another boot dir on it...

Re: Linux 3.3.2 kernel for Dockstar, GoFlex and many others

bambo — Wed, 17 Apr 2013 06:02:22 -0400

~Sven

root@pogo:/boot/# sfdisk -d /dev/sda
# partition table of /dev/sda
unit: sectors

/dev/sda1 : start=     2048, size=   450560, Id=83, bootable
/dev/sda2 : start=   452608, size=  5306368, Id=83
/dev/sda3 : start=  5758976, size=  2095104, Id=82
/dev/sda4 : start=        0, size=        0, Id= 0
root@pogo:/boot/# mount
none on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
none on /proc type proc (rw,nosuid,nodev,noexec,relatime)
none on /dev type devtmpfs (rw,relatime,size=125224k,nr_inodes=31306,mode=755)
none on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
/dev/sda2 on / type ext4 (rw,noatime,user_xattr,barrier=1,data=ordered)
tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=25552k,mode=755)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /run/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=260600k)
/dev/sda1 on /boot type ext2 (ro,relatime,errors=continue)
tmpfs on /tmp type tmpfs (rw,relatime)
root@pogo:~/# 
root@pogo:~/# cat /etc/fstab
# /etc/fstab: static file system information.
#
# 						
#/dev/root	/		ext2	noatime,errors=remount-ro 0	1
/dev/sda1	/boot		ext2	ro			0	0
/dev/sda2	/		ext4	noatime			0	1
/dev/sda3	none		swap	sw			0	0
tmpfs		/tmp		tmpfs	defaults		0	0

So I copy the stuff from /boot to /boot/boot and voilà 3.8.4 Kernel booted! I don't understand the mechanist why it's happen, but you guys are saints.

Why uBoot takes /boot/boot stuff for booting?

Re: Linux 3.3.2 kernel for Dockstar, GoFlex and many others

Sven — Wed, 17 Apr 2013 02:27:12 -0400

Well - but it still looks funny. 'mkimage' reports the same sizes as you can see in the listing, but uBoot does read other files:

Quote

Loading file "/boot/uImage" from usb device 0:1 (usbda1)
2081852 bytes read
Loading file "/boot/uInitrd" from usb device 0:1 (usbda1)
5035488 bytes read

What's the content of /boot/boot?
And can you additionally tell us something about your partitioning? The output of 'sfdisk -d /dev/sda' and 'mount'?

Maybe it's sufficient to change the link and dir inside your boot (partition?):

mv /boot/boot /boot/boot.dir
mv /boot/boot1 /boot/boot

Re: Linux 3.3.2 kernel for Dockstar, GoFlex and many others

bambo — Tue, 16 Apr 2013 18:00:41 -0400

~bodhi

root@pogo:~/# ls -latr /boot
total 67148
-rw-r--r--  1 root root 5035424 Jan  1  1970 initrd.img-3.0.32-dockstar-geekparadise.de
-rw-r--r--  1 root root  107468 Apr 24  2012 config-3.3.2-kirkwood-dg
-rw-r--r--  1 root root 2279192 Apr 24  2012 vmlinuz-3.3.2-kirkwood-dg
-rw-r--r--  1 root root 6610550 Apr 24  2012 vmlinux-3.3.2-kirkwood-dg
-rw-r--r--  1 root root 1220456 Apr 24  2012 System.map-3.3.2-kirkwood-dg
-rw-r--r--  1 root root   99493 Mai 24  2012 config-3.0.32-dockstar-geekparadise.de
-rw-r--r--  1 root root 2081788 Mai 24  2012 vmlinuz-3.0.32-dockstar-geekparadise.de
-rw-r--r--  1 root root 1138981 Mai 24  2012 System.map-3.0.32-dockstar-geekparadise.de
drwx------  2 root root    4096 Jun 18  2012 lost+found
lrwxrwxrwx  1 root root       1 Jun 18  2012 boot1 -> .
drwxr-xr-x  2 root root    4096 Jun 18  2012 boot
-rw-r--r--  1 root root   94709 Mär 27 17:10 config-3.8.4-dockstar
-rw-r--r--  1 root root 3717400 Mär 27 17:12 vmlinuz-3.8.4-dockstar
-rw-r--r--  1 root root 1916881 Mär 27 17:12 System.map-3.8.4-dockstar
-rw-r--r--  1 root root 1606512 Mär 27 20:40 vmlinuz-3.2.0-4-kirkwood
-rw-r--r--  1 root root 1207425 Mär 27 20:41 System.map-3.2.0-4-kirkwood
-rw-r--r--  1 root root  107503 Mär 27 20:41 config-3.2.0-4-kirkwood
-rw-r--r--  1 root root  101604 Mär 31 09:17 config-3.6.11-kirkwood-tld
-rw-r--r--  1 root root 1741016 Mär 31 15:00 vmlinuz-3.6.11-kirkwood-tld
-rw-r--r--  1 root root 1240893 Mär 31 15:00 System.map-3.6.11-kirkwood-tld
-rw-r--r--  1 root root 1605272 Apr  5 03:54 uImage.bak
-rw-r--r--  1 root root 6809332 Apr  5 03:55 uInitrd.bak
-rw-r--r--  1 root root 6811106 Apr  5 06:18 initrd.img-3.2.0-4-kirkwood
-rw-r--r--  1 root root 7217003 Apr 16 09:29 initrd.img-3.3.2-kirkwood-dg
drwxr-xr-x 22 root root    4096 Apr 16 21:03 ..
-rw-r--r--  1 root root 5855547 Apr 16 21:23 initrd.img-3.6.11-kirkwood-tld
-rw-r--r--  1 root root 3111997 Apr 16 21:32 initrd.img-3.8.4-dockstar
drwxr-xr-x  4 root root    4096 Apr 16 21:32 .
-rw-r--r--  1 root root 3717464 Apr 16 22:50 uImage
-rw-r--r--  1 root root 3112061 Apr 16 22:50 uInitrd

looks ok?

Re: Linux 3.3.2 kernel for Dockstar, GoFlex and many others

bodhi — Tue, 16 Apr 2013 17:44:21 -0400

What's the output of your USB /boot directory?
ls -latr /boot

Re: Linux 3.3.2 kernel for Dockstar, GoFlex and many others

bambo — Tue, 16 Apr 2013 17:14:46 -0400

~Sven

No, there are no USB devices on PogoPlug. I don't know why the first try fails by reading, I put my USB flash drive to each port, so netconsole shows me the same all the time.

mkimage magic, huh. I don't know how to try to check the success of it. I look for return value, it's zero.

root@pogo:~/# mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-3.8.4-dockstar -d /boot/vmlinuz-3.8.4-dockstar /boot/uImage
Image Name:   Linux-3.8.4-dockstar
Created:      Tue Apr 16 22:50:28 2013
Image Type:   ARM Linux Kernel Image (uncompressed)
Data Size:    3717400 Bytes = 3630.27 kB = 3.55 MB
Load Address: 00008000
Entry Point:  00008000
root@pogo:~/# echo $?
0
root@pogo:~/# mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs-3.8.4-dockstar -d /boot/initrd.img-3.8.4-dockstar /boot/uInitrd
Image Name:   initramfs-3.8.4-dockstar
Created:      Tue Apr 16 22:50:54 2013
Image Type:   ARM Linux RAMDisk Image (gzip compressed)
Data Size:    3111997 Bytes = 3039.06 kB = 2.97 MB
Load Address: 00000000
Entry Point:  00000000
root@pogo:~/# echo $?
0

This is depressing.

Re: Linux 3.3.2 kernel for Dockstar, GoFlex and many others

Sven — Tue, 16 Apr 2013 16:29:29 -0400

Quote

Loading file "/boot/uImage" from usb device 0:1 (usbda1)
1 bytes read
Found bootable drive on usb 0:1
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
2081852 bytes read
Loading file "/boot/uInitrd" from usb device 0:1 (usbda1)
5035488 bytes read
## Booting kernel from Legacy Image at 00800000 ...
Image Name: Linux-3.0.32

And you're sure the 'mkimage' succeeded?
It shows definitely "3.0.32" while booting - is there another USB drive in place?
(because of the first try and only loading 1 byte...)

Re: Linux 3.3.2 kernel for Dockstar, GoFlex and many others

bambo — Tue, 16 Apr 2013 15:48:48 -0400

~bodhi,
~Sven,
thanks for fast answers, I tried to install all 3 kernels, the packages installed well, made all mkimage voodoo, but PogoPlug booted my old 3.0.x kernel from Legacy Image. There is the same netconsole output as in my first post.

~shv
oh! that's nice, I put it to the download queue.

Re: Linux 3.3.2 kernel for Dockstar, GoFlex and many others

Sven — Tue, 16 Apr 2013 15:10:03 -0400

Bamboo,

you may also try my intermediate version:
https://www.dropbox.com/s/pyumlkft1tb5qu3/linux-image-3.8.4-dockstar_1.1_armel.deb

Although I did some more cut down to get a smaller kernel which I didn't upload so far, this one should work with all Kirkwood devices. I did a successful upgrade to Wheezy on my USB stick and it's still running fine... so give it a try!

Re: Linux 3.3.2 kernel for Dockstar, GoFlex and many others

shv — Tue, 16 Apr 2013 15:03:43 -0400

Did you try one of my rootfs from the previous post above yours?

Re: Linux 3.3.2 kernel for Dockstar, GoFlex and many others

bodhi — Tue, 16 Apr 2013 15:01:00 -0400

Try this:
http://forum.doozan.com/read.php?2,11601

or this:
http://forum.doozan.com/read.php?2,12096

Re: Linux 3.3.2 kernel for Dockstar, GoFlex and many others

bambo — Tue, 16 Apr 2013 14:54:22 -0400

Hi,

first I really sorry for my bad English, so I hope I can express myself right.

second I have a long painful story. I had a pink Pogoplug. I can't install wheezy (kernel to old), squeeze install script works fine but Pogoplug don't boot from the created usb flash drive. I put a rescue image I founded in your forum. Pogo booted it. Nice. Then I founded my old dockstar squeeze image with 3.0.32 dockstar-geekparadise.de Kernel and configured ext2 boot and ext4 root partitions. So I made some fw_env tweaks for booting it. It booted. Nice. I cleaned my squeeze from unnecessary stuff, updated sources.list, done a dist-upgrade to wheezy, all fine but my kernel did not upgraded, so PogoPlug boot old 3.0 kernel. Here some netconsole logs.

I tried all the stuff I found here in forum like:

flash-kernel
update-initramfs -u
mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-3.2.0-4 -d /boot/vmlinuz-3.2.0-4-kirkwood /boot/uImage
mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n Initrd-3.2.0-4 -d /boot/initrd.img-3.2.0-4-kirkwood /boot/uInitrd

I get stuck. So I tried the 3.3.2 kirkwood from that topic, but the installation failed. Damn, I need 3.2 or higher kernel.

Re: Linux 3.3.2 kernel for Dockstar, GoFlex and many others

shv — Sun, 14 Apr 2013 10:05:25 -0400

You can download a rootfs (Debian/Wheezy) with 3.3.2 kernel which is based on Davys kernel with the extension to additionally support Pogoplug E02, Mobile, Series4 arcNumber/machid from the following post: Link.

Re: Linux 3.3.2 kernel for Dockstar, GoFlex and many others

Sven — Tue, 09 Apr 2013 10:50:50 -0400

shv Wrote:
-------------------------------------------------------
> With the kernel of the rescue system and
> arcNumber/machid set to 3542/dd6 the LED is
> controled. The color is green if it is switched
> on. The same behaviour I have with bodhys kernel
> 3.2.28. With 3.3.2 kernel and arcNumber/machid set
> to 2097/831 this LED seam to be controled as well
> but the color is orange.

I played around a little with Davygravys kernel patch, because I needed to set up a new crosscompile env to get an I2C enabled (and working) kernel. I took his patches as a base to get the current 3.8.4 kernel to compile and work with my dockstar. I also took some time to investigate the LED problem:

Jeff's original kernel modified the kernel machine "Sheevaplug" (2097/0x831). But newer kernels do support the "Dockstar" (2998/0xBB6). If you set your machid environment to bb6, it will support the LEDs correct.

So, does anybody own a device with the original 831 machid?
Does this one have only one LED on GPIO 49?
If this machine is unused in our environment, I would simply patch the Sheevaplug support according to the Dockstar LEDs, as Jeff did.

I still play around a little with my final kernel config and will post the resulting Debian package along with my patch for 3.8.4 and the steps required to build it in a separate post later...

Re: Linux 3.3.2 kernel for Dockstar, GoFlex and many others

dubanks — Fri, 15 Mar 2013 12:27:08 -0400

Bodhi,

Yes I have the ralink-firmware installed:

root@debian:/tmp# apt-get install firmware-ralink
Reading package lists... Done
Building dependency tree
Reading state information... Done
firmware-ralink is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

This device should have driver file rt2870sta.ko.

I could compile the driver in earlier kernel versions, but seem like there was some gcc issue due to which the driver didn't load properly. I thought switching to latest kernel could help, since it may have these drivers pre-compiled.

This specific driver seem to be missing.

The driver package does have the firmware file (*.dat) file. Do you know if I can just copy that somewhere to get it recognized?

Thanks

Re: Linux 3.3.2 kernel for Dockstar, GoFlex and many others

shv — Fri, 15 Mar 2013 06:02:33 -0400

I think he just needs the kernel headers to compile the sources which are provided from Mediatek/Ralink.

Re: Linux 3.3.2 kernel for Dockstar, GoFlex and many others

bodhi — Fri, 15 Mar 2013 04:09:12 -0400

Did you try to intall ralink suite?
apt-get install firmware-ralink