Re: vmlinuz hang at "Loading Kernel Image ... "
On 01/07/2014 09:32, drEagle wrote:
> Hi hackers,
The problems is with make-kpkg, that I may use badly;
a working kernel is built with :
time KBUILD_DEBARCH=armhf ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- CC=arm-linux-gnueabihf-gcc STRIP=arm-linux-gnueabihf-strip DEB_HOST_ARCH=armhf CLEAN_SOURCE=no fakeroot make -j9 deb-pkg
a non working kernel is built with :
sudo make-kpkg --us --uc --rootcmd=fakeroot --arch=arm --subarch=armhf --cross-compile=arm-linux-gnueabihf- --append-to-version=-doukki2 --revision=201407-1 kernel_image
> I can't boot a custom kernel while it is debian packaged.
> With booting my dtb+zImage my netgear RN104 is booting fine.
> With a vmlinuz (from a custom make-kpkg deb) and a flash-kernel (from wheezy-backports) I get hang on the message
> "Loading Kernel Image ... "
>
> The boot.scr used is the same.
>
> Is there any missing step I lost ?
>
> The NetGear RN104 is an ARMADA370 (MVEBU) based and supported mainline.
>
> What are the differences and required adds to uboot or uboot env for booting vmlinuz kernel instead of zimage kernel ?
>
> Some logs;
>
> *The bootlog*
> ...
> reading /boot.scr
> 865 bytes read
> ## Executing script at 04000000
> Using egiga0 device
> host 192.168.1.254 is alive
> Using egiga1 device
> host 192.168.1.254 is alive
> reading /uImage
> .................................................................................................................................
> .................................................................................................................................
> ...........................................................................................................................
>
> 8278929 bytes read
> reading /uInitrd
> .................................................................................................................................
>
> 3023742 bytes read
> reading /dtb
> 12393 bytes read
> ## Booting kernel from Legacy Image at 06000000 ...
> Image Name: kernel 3.15.3-doukki2.rn104
> Created:2014-07-01 6:55:09 UTC
> Image Type: ARM Linux Kernel Image (uncompressed)
> Data Size: 8278865 Bytes = 7.9 MB
> Load Address: 00008000
> Entry Point: 00008000
> Verifying Checksum ... OK
> ## Loading init Ramdisk from Legacy Image at 12000000 ...
> Image Name: ramdisk 3.15.3-doukki2.rn104
> Created:2014-07-01 6:55:09 UTC
> Image Type: ARM Linux RAMDisk Image (gzip compressed)
> Data Size: 3023678 Bytes = 2.9 MB
> Load Address: 00000000
> Entry Point: 00000000
> Verifying Checksum ... OK
> Loading Kernel Image ...
>
> *The boot.script*
> setenv initrd_high "0xffffffff"
> setenv fdt_high "0xffffffff"
> setenv image_addr "0x06000000"
> setenv image_name "/uImage"
> setenv initrd_addr "0x12000000"
> setenv initrd_name "/uInitrd"
> setenv dtb_addr "0x02000000"
> setenv dtb_name "/dtb"
> setenv bootcmd "fatload usb 0:1 $image_addr $image_name;fatload usb 0:1 $initrd_addr $initrd_name; fatload usb 0:1 $dtb_addr $dtb_name; bootm $image_addr $initrd_addr $dtb_addr"
> setenv bootargs "console=tty1 console=ttyS0,115200 mtdparts=armada-nand:0x180000@0(u-boot),0x20000@0x180000(u-boot-env),0x600000@0x200000(uImage),0x400000@0x800000(minirootfs),-(ubi) bdtype=rn104 root=LABEL=ROOTFS rootwait ro panic=5"
> setenv ipaddr '192.168.1.77'
> setenv ethload "setenv ethact egiga0; ping 192.168.1.254; setenv ethact egiga1; ping 192.168.1.254"
> run ethload
> boot
>
>
Reply to: