Welcome! Log In Create A New Profile

Advanced

Linux kernel 3.2.28 Kirkwood package

Posted by bodhi 
Re: Linux kernel 3.2.28 Kirkwood package
March 21, 2013 10:38AM
syong,

What is the size comparing to LZMA?

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: Linux kernel 3.2.28 Kirkwood package
March 21, 2013 10:49AM
bodhi,

uImage is much smaller for LZMA.

The reason I use gzip is that the build got `out of memory' for LZMA.

Here is what I have:

(%3)(10:44)(punk)/boot> ll
total 18344
-rw-r--r-- 1 root root 1178004 Mar 21 07:13 System.map-3.2.28-20130320-232852
-rw-r--r-- 1 root root  105867 Mar 20 23:31 config-3.2.28-20130320-232852
-rw-r--r-- 1 root root 6507728 Mar 21 08:51 initrd.img-3.2.28-20130320-232852
-rw-r--r-- 1 root root 2219048 Mar 21 08:59 uImage
-rw-r--r-- 1 root root 6507792 Mar 21 09:00 uInitrd
-rw-r--r-- 1 root root 2218984 Mar 21 07:13 vmlinuz-3.2.28-20130320-232852

Sorry, I already removed old uImage which I remember is around 1.6M as I use a 2g usb stick.

-syong
Re: Linux kernel 3.2.28 Kirkwood package
March 26, 2013 10:53AM
bodhi,

FYI, I just did a native compile with your kernel patch on 3.2.30 kernel.

The build worked fine and solved the problem of almost 1min delay when mounting a 2T ext4 drive.

-syong
Re: Linux kernel 3.2.28 Kirkwood package
March 27, 2013 12:04AM
Cool! good to know.
Re: Linux kernel 3.2.28 Kirkwood package
May 15, 2013 08:16AM
bodhi,

unfortunately, your package does not boot on the Zyxel NSA320, as it does not recognize the machine id (arcNumber = 3956; machid=f74). What must be done to remedy this?

Like davy's 3.3.2 kernel, it should not really be a problem to use your's, I think.

---
Standart ist der Standardfehler
Re: Linux kernel 3.2.28 Kirkwood package
May 15, 2013 03:01PM
chessplayer Wrote:
-------------------------------------------------------
> bodhi,
>
> unfortunately, your package does not boot on the
> Zyxel NSA320, as it does not recognize the machine
> id (arcNumber = 3956; machid=f74). What must be
> done to remedy this?
>
> Like davy's 3.3.2 kernel, it should not really be
> a problem to use your's, I think.

Chessplayer,
It does not have the patch for NSA320! Because I dont own one. I could build with the patch, but can't test it. So if you or somebody resquest then I will build with Nsa320 and somebody else will have to do the test.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: Linux kernel 3.2.28 Kirkwood package
May 15, 2013 03:02PM
bodhi,

I would be interested and I would also be willing to do the test.

---
Standart ist der Standardfehler
Re: Linux kernel 3.2.28 Kirkwood package
May 16, 2013 12:11AM
@chessplayer,

Unfortunately I can't find the individual patch for NSA320! there is a consolidated patch for Arch (by moonman) which has NSA320:
https://github.com/archlinuxarm/PKGBUILDs/blob/master/core/linux-kirkwood/archlinuxarm.patch

But it will take some works to extract it.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: Linux kernel 3.2.28 Kirkwood package
May 16, 2013 03:19AM
@bodhi,

that's ok, I will just wait for when you have found time for this.

---
Standart ist der Standardfehler
Re: Linux kernel 3.2.28 Kirkwood package
June 10, 2013 05:32PM
@chessplayer,

Please try this kernel 3.8.11 and let me know if you can run it on NSA320. Once you have verified that it works, I will update the 3.8.11 thread to include it.

Update - see main thread for link:
http://forum.doozan.com/read.php?2,12096

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



Edited 1 time(s). Last edit at 06/11/2013 04:01PM by bodhi.
Re: Linux kernel 3.2.28 Kirkwood package
June 11, 2013 03:31AM
@bodhi,

I will do that, but it may take until tomorrow night.At the same time, I will try your advice concerning the wheezy upgrade.

In any case: thanks a real lot for your efforts!

---
Standart ist der Standardfehler
Re: Linux kernel 3.2.28 Kirkwood package
June 11, 2013 01:03PM
@bodhi,

you are my hero. Things worked out with some gotchas:

First, I downloaded the file from your link above. However, the archive manager complained, that this was not a bzip-file and would not open it. By sheer coincidence, I renamed it to ...gz2 (instead of ...bz2) and voilá, it opened. So I repacked and transferred to the USB-Stick, where I unpacked it. Then I did the following:

└──> dpkg -i linux-image-3.8.11-kirkwood-tld-2_2.0_armel.deb 
Selecting previously unselected package linux-image-3.8.11-kirkwood-tld-2.
(Reading database ... 13410 files and directories currently installed.)
Unpacking linux-image-3.8.11-kirkwood-tld-2 (from linux-image-3.8.11-kirkwood-tld-2_2.0_armel.deb) ...
Examining /etc/kernel/preinst.d/
Done.
Setting up linux-image-3.8.11-kirkwood-tld-2 (2.0) ...

 Hmm. There is a symbolic link /lib/modules/3.8.11-kirkwood-tld-2/build
 However, I can not read it: No such file or directory
 Therefore, I am deleting /lib/modules/3.8.11-kirkwood-tld-2/build


 Hmm. The package shipped with a symbolic link /lib/modules/3.8.11-kirkwood-tld-2/source
 However, I can not read the target: No such file or directory
 Therefore, I am deleting /lib/modules/3.8.11-kirkwood-tld-2/source

Running depmod.
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.8.11-kirkwood-tld-2 /boot/vmlinuz-3.8.11-kirkwood-tld-2
update-initramfs: Generating /boot/initrd.img-3.8.11-kirkwood-tld-2
run-parts: executing /etc/kernel/postinst.d/zz-flash-kernel 3.8.11-kirkwood-tld-2 /boot/vmlinuz-3.8.11-kirkwood-tld-2

Question: what about the symlinks dpkg is complaining about? Do I need to do anything about it for things to come in the future? For the time being, it did not make a difference. I followed up with:

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

and

cd /
ln -s boot/vmlinuz-3.8.11-kirkwood-tld-2 vmlinuz
ln -s boot/initrd.img-3.8.11-kirkwood-tld-2 initrd.img

Watching reboot in netconsole gave:

U-Boot 2011.12 (May 03 2012 - 17:04:23)
ZyXEL NSA320 2-Bay Power Media Server
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 
(Re)start USB...
USB:   Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 3 USB Device(s) found
       scanning bus for storage devices... 1 Storage Device(s) found
stopping USB..
(Re)start USB...
USB:   Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 3 USB Device(s) found
       scanning bus for storage devices... 1 Storage Device(s) found
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
1 bytes read
Found bootable drive on usb 0:1
bootargs=console=ttyS0,115200 root=LABEL=USB-Root rootdelay=10 rootfstype=ext4 mtdparts=orion_nand:1M(u-boot),512K(uboot_env),512K(key_store),512K(info),10M(etc),10M(kernel_1),48896K(rootfs1),10M(kernel_2),-(rootfs2)
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
1805696 bytes read
Loading file "/boot/uInitrd" from usb device 0:1 (usbda1)
6900416 bytes read
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-3.8.11-kirkwood-tld-2
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1805632 Bytes = 1.7 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs-3.8.11-kirkwood-tld-2
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    6900352 Bytes = 6.6 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

So, this looked good. SSH yielded:

         _sudZUZ#Z#XZo=_         DDDD   EEEEEE BBBB   IIIIII  AAAA   NN   NN
      _jmZZ2!!~---~!!X##wa       DD DD  EE     BB BB    II   AA  AA  NNN  NN
   .<wdP~~            -!YZL,     DD  DD EEEEE  BBBBB    II   AAAAAA  NNNN NN
  .mX2'       _%aaa__     XZ[.   DD DD  EE     BB  BB   II   AA  AA  NN NNNN
  oZ[      _jdXY!~?S#wa   ]Xb;   DDDD   EEEEEE BBBBB  IIIIII AA  AA  NN   NN
 _#e'     .]X2(     ~Xw|  )XXc 
.2Z`      ]X[.       xY|  ]oZ(   Linux Version 3.8.11-kirkwood-tld-2
.2#;      )3k;     _s!~   jXf`   Compiled #1 PREEMPT Sun Jun 9 17:36:05 PDT 2013
 1Z>      -]Xb/    ~    __#2(    One ARM  Processor, 512M RAM
 -Zo;       +!4ZwaaaauZZXY'      1196.85 Bogomips Total
  *#[,        ~-?!!!!!!-~        my-hostname
   XUb;.                       
    )YXL,,                     
      +3#bc,                   
        -)SSL,,                
           ~~~~~               
[Tue Jun 11 19:42:21 CEST 2013]
 19:42:21 up 1 min,  1 user,  load average: 0.12, 0.05, 0.02
USER     TTY      FROM             LOGIN@   IDLE   JCPU   PCPU WHAT
root     pts/0    xxx.xxx.xxx.xxx  19:42    1.00s  0.04s  0.01s w

Filesystem                   Size  Used Avail Use% Mounted on
rootfs                       3.2G  573M  2.5G  19% /
udev                          10M     0   10M   0% /dev
/dev/disk/by-label/USB-Root  3.2G  573M  2.5G  19% /
/dev/sdb1                    190M   48M  133M  27% /boot
┌─[root@my-hostname]─[~]
└──>

Great, running 3.8.11 kernel on the Zyxel. Tried as well on Dockstar, Pogo E02, GoFlex Net and GoFlex Home: all working!!!

THANK YOU, bodhi!

---
Standart ist der Standardfehler



Edited 2 time(s). Last edit at 06/17/2013 12:18PM by chessplayer.
Re: Linux kernel 3.2.28 Kirkwood package
June 11, 2013 03:34PM
@chessplayer,

Awesome! and sorry about the gz2/bz2, I got it mixed up sometime (it must be a mental block somewhere :)). I'll re-archive the tarball properly.

The symlinks warning is not a problem, dpkg just looks for the source and build directories and can't find them. It does not effect the kernel installation at all.

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

Your Email:


Subject:


Spam prevention:
Please, enter the code that you see below in the input field. This is for blocking bots that try to post this form automatically. If the code is hard to read, then just try to guess it right. If you enter the wrong code, a new image is created and you get another chance to enter it right.
Message: