RE: SS4000E Kernel v3.4 Config
Do you think of this approach would work?
1. Load/boot ss4000e with the daily images kernel=v2.6.32-5
http://d-i.debian.org/daily-images/armel/daily/iop32x/netboot/ss4000e/
It boots/runs 2.6.32-5
2. Cross-build new 3.4 kernel
3. Save modules and compress
$ export INSTALL_MOD_PATH=../modules-3.4 #make/put modules in
../modules-3.4
$ make ARCH=arm CROSS_COMPILE=arm-unknown-linux-gnueabi- modules_install
$ cd ..
$ tar -zcvf modules-3.4.tar.gz modules-3.4 #compress
4. Fix zImage with Arnaud's devio trick to fix machine ID
$ ( devio 'wl 0xe3a01c04,4' 'wl 0xe38110bc,4'; cat zImage ) >
zImage-3.4.0-iop32x
5. Copy .config, System.map, zImage-3.4.0-iop32x, modules-3.4.tar.gz to tftp
server to upload them to ss4000e
6. Download these to a ss4000e working dir with tftp (needed to install
tftp)
7. Copy and rename downloaded to /boot per list below
8. Decompress modules-3.4.tar.gz. Copy the lib directory therein to /lib
9. Build initramfs in /boot
mkinitramfs -o initrd.img-3.4.0-iop32x 3.4.0
root@new-host:/boot# ls -l
total 10364
-rw-r--r-- 1 root root 81828 May 6 21:35 config-2.6.32-5-iop32x
-rw-r--r-- 1 root root 102426 Aug 17 10:08 config-3.4.0
lrwxrwxrwx 1 root root 26 Aug 16 17:34 initrd.img ->
initrd.img-2.6.32-5-iop32x
-rw-r--r-- 1 root root 2759115 Aug 16 17:59 initrd.img-2.6.32-5-iop32x
-rw-r--r-- 1 root root 2840619 Aug 17 10:09 initrd.img-3.4.0-iop32x
-rw-r--r-- 1 root root 945808 May 6 21:35 System.map-2.6.32-5-iop32x
-rw-r--r-- 1 root root 1127522 Aug 17 09:32 System.map-3.4.0-iop32x
lrwxrwxrwx 1 root root 23 Aug 16 17:34 vmlinuz ->
vmlinuz-2.6.32-5-iop32x
-rw-r--r-- 1 root root 1257376 May 6 21:34 vmlinuz-2.6.32-5-iop32x
-rw-r--r-- 1 root root 1450536 Aug 17 09:33 zImage-3.4.0-iop32x
All the 3.4.0 files are in /boot but they are not yet linked. The ss4000e
will still boot as 2.6.32-5
10. Remake the 2 links so that initrd.img points to initrd-3.4.0-iop32x and
vmlinuz points to zImage-3.4.0-iop32x
11. Run flash-kernel to save
is initrd.img-3.4.0-iop32x too big?
12. Reboot and it should boot into 3.4 kernel??
I didn't actually take the last 3 steps. I'm not sure I got all the file
naming correct.
Chris
-----Original Message-----
From: JF Straeten [mailto:jfstraeten@scarlet.be]
Sent: Wednesday, August 15, 2012 2:25 PM
To: debian-arm@lists.debian.org
Subject: Re: SS4000E Kernel v3.4 Config
Re,
On Wed, Aug 15, 2012 at 01:13:25PM -0400, Chris Wilkinson wrote:
> These tools seem to generate an initramfs for the host (AMD-64)
> system. I want to build one for the ss4000e ARM target. Is that
> possible?
Perhaps with a chroot in the directory where you cross compile ?
(Not sure.)
Hih,
--
JFS.
--
To UNSUBSCRIBE, email to debian-arm-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact
listmaster@lists.debian.org
Archive: [🔎] 20120815182507.GA9185@jones.jfs.dt">http://lists.debian.org/[🔎] 20120815182507.GA9185@jones.jfs.dt
Reply to: