Welcome! Log In Create A New Profile

Advanced

4.14.1 kernel kernel panic

Posted by Jeffrccar 
4.14.1 kernel kernel panic
December 29, 2017 10:39AM
this is not a big deal.
so i have a pogoplug v4 and i have the newest uboot and env on it.
i'm running rootfs 4.12.1 but a tried 4.14.1 kernel and it will not boot. i get a kernel panic.
i guess need to hook up serial to it for dmesg.

-----
Mod edit: please post problem in separate thread.



Edited 1 time(s). Last edit at 12/29/2017 12:36PM by bodhi.
Re: 4.14.1 kernel kernel panic
December 30, 2017 10:48AM
Jeffrccar,

> i'm running rootfs 4.12.1 but a tried 4.14.1
> kernel and it will not boot. i get a kernel
> panic.

Do you have the log of this kernel panic (dmeg output)?

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: 4.14.1 kernel kernel panic
January 01, 2018 02:48PM
dmesg:
U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:34:01 -0700)
Pogoplug V4

SoC:   Kirkwood 88F6192_A1
DRAM:  128 MiB
WARNING: Caches not enabled
NAND:  128 MiB
MMC:   MVEBU_MMC: 0
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
Hit any key to stop autoboot:  0 
starting USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found

Reset IDE: ide_preinit failed

MMC rescan: current device # 0 initialized OK
## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0
loading envs from usb 0 ...
** Bad device usb 0 **

no IDE devices available

Partition Map for MMC device 0  --   Partition Type: DOS

Part    Start Sector    Num Sectors     UUID            Type
  1     2048            62550016        bfeec2e3-01     83
loading envs from mmc 0 ...
79 bytes read in 86 ms (0 Bytes/s)
importing envs ...
running scan_disk ...
Scan device mmc

MMC rescan: current device # 0 initialized OK
device mmc 0:1
1 bytes read in 33 ms (0 Bytes/s)
Found bootable drive on mmc 0
loading uImage ...
3876600 bytes read in 156 ms (23.7 MiB/s)
loading uInitrd ...
7245696 bytes read in 262 ms (26.4 MiB/s)
loading DTB /boot/dts/kirkwood-pogoplug_v4.dtb ...
10284 bytes read in 69 ms (145.5 KiB/s)
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-4.14.1-kirkwood-tld-1
   Created:      2017-12-08  17:05:15 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3876536 Bytes = 3.7 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs-4.12.1-kirkwood-tld-1
   Created:      2017-07-24   0:18:23 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    7245632 Bytes = 6.9 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 01c00000
   Booting using the fdt blob at 0x1c00000
   Loading Kernel Image ... OK
   Loading Ramdisk to 07420000, end 07b08f40 ... OK
   Loading Device Tree to 0741a000, end 0741f82b ... OK
Using machid 0xf78 from environment

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 4.14.1-kirkwood-tld-1 (root@tldDebian) (gcc version 6.3.0 20170516 (Debian 6.3.0-18)) #1 PREEMPT Wed Nov 22 23:38:14 PST 2017
[    0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f
[    0.000000] CPU: VIVT data cache, VIVT instruction cache
[    0.000000] OF: fdt: Machine model: Pogoplug v4
[    0.000000] Memory policy: Data cache writeback
[    0.000000] random: fast init done
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 32512
[    0.000000] Kernel command line: console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=orion_nand:2M(u-boot),3M(uImage),3M(uImage2),8M(failsafe),112M(root)
[    0.000000] PID hash table entries: 512 (order: -1, 2048 bytes)
[    0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
[    0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
[    0.000000] Memory: 109428K/131072K available (8192K kernel code, 714K rwdata, 2040K rodata, 1024K init, 285K bss, 21644K reserved, 0K cma-reserved)
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
[    0.000000]     vmalloc : 0xc8800000 - 0xff800000   ( 880 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xc8000000   ( 128 MB)
[    0.000000]     modules : 0xbf000000 - 0xc0000000   (  16 MB)
[    0.000000]       .text : 0xc0008000 - 0xc0900000   (9184 kB)
[    0.000000]       .init : 0xc0c00000 - 0xc0d00000   (1024 kB)
[    0.000000]       .data : 0xc0d00000 - 0xc0db2aec   ( 715 kB)
[    0.000000]        .bss : 0xc0db94b0 - 0xc0e00a4c   ( 286 kB)
[    0.000000] Preemptible hierarchical RCU implementation.
[    0.000000]  Tasks RCU enabled.
[    0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[    0.000000] clocksource: orion_clocksource: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 11467562657 ns
[    0.000011] sched_clock: 32 bits at 166MHz, resolution 6ns, wraps every 12884901885ns
[    0.000057] Switching to timer-based delay loop, resolution 6ns
[    0.000684] Console: colour dummy device 80x30
[    0.000730] Calibrating delay loop (skipped), value calculated using timer frequency.. 333.33 BogoMIPS (lpj=1666666)
[    0.000760] pid_max: default: 32768 minimum: 301
[    0.000978] Security Framework initialized
[    0.001157] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.001186] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.002302] CPU: Testing write buffer coherency: ok
[    0.003544] Setting up static identity map for 0x100000 - 0x100058
[    0.003871] mvebu-soc-id: MVEBU SoC ID=0x6281, Rev=0x3
[    0.004173] Hierarchical SRCU implementation.
[    0.008161] devtmpfs: initialized
[    0.013073] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.013107] futex hash table entries: 256 (order: -1, 3072 bytes)
[    0.013597] prandom: seed boundary self test passed
[    0.018618] prandom: 100 self tests passed
[    0.018633] pinctrl core: initialized pinctrl subsystem
[    0.019988] NET: Registered protocol family 16
[    0.020696] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.022548] cpuidle: using governor ladder
[    0.022634] cpuidle: using governor menu
[    0.023212] Feroceon L2: Enabling L2
[    0.023263] Feroceon L2: Cache support initialised.
[    0.023686] [Firmware Info]: /ocp@f1000000/ethernet-controller@72000/ethernet0-port@0: local-mac-address is not set
[    0.029106] No ATAGs?
[    0.038284] vgaarb: loaded
[    0.038645] SCSI subsystem initialized
[    0.039136] usbcore: registered new interface driver usbfs
[    0.039202] usbcore: registered new interface driver hub
[    0.039285] usbcore: registered new device driver usb
[    0.040487] clocksource: Switched to clocksource orion_clocksource
[    0.148381] VFS: Disk quotas dquot_6.6.0
[    0.148482] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    0.158369] NET: Registered protocol family 2
[    0.159255] TCP established hash table entries: 1024 (order: 0, 4096 bytes)
[    0.159285] TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
[    0.159310] TCP: Hash tables configured (established 1024 bind 1024)
[    0.159411] UDP hash table entries: 256 (order: 0, 4096 bytes)
[    0.159439] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[    0.159652] NET: Registered protocol family 1
[    0.160136] RPC: Registered named UNIX socket transport module.
[    0.160152] RPC: Registered udp transport module.
[    0.160160] RPC: Registered tcp transport module.
[    0.160170] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.160458] Unpacking initramfs...
[    0.920575] Freeing initrd memory: 7076K
[    0.920757] NetWinder Floating Point Emulator V0.97 (double precision)
[    0.921635] audit: initializing netlink subsys (disabled)
[    0.922130] Initialise system trusted keyrings
[    0.922184] Key type blacklist registered
[    0.922294] audit: type=2000 audit(0.920:1): state=initialized audit_enabled=0 res=1
[    0.922402] workingset: timestamp_bits=30 max_order=15 bucket_order=0
[    0.922481] zbud: loaded
[    0.923530] NFS: Registering the id_resolver key type
[    0.923562] Key type id_resolver registered
[    0.923571] Key type id_legacy registered
[    0.923592] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    0.923603] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[    0.923917] jffs2: version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
[    0.924148] fuse init (API version 7.26)
[    0.924560] orangefs_debugfs_init: called with debug mask: :none: :0:
[    0.924775] orangefs_init: module version upstream loaded
[    0.924788] SGI XFS with ACLs, security attributes, realtime, no debug enabled
[    8.035535] Key type asymmetric registered
[    8.035554] Asymmetric key parser 'x509' registered
[    8.035629] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 249)
[    8.035643] io scheduler noop registered
[    8.035652] io scheduler deadline registered
[    8.035758] io scheduler cfq registered (default)
[    8.036696] kirkwood-pinctrl f1010000.pin-controller: unknown pinctrl group 47
[    8.036715] kirkwood-pinctrl f1010000.pin-controller: unknown pinctrl group 49
[    8.037118] kirkwood-pinctrl f1010000.pin-controller: registered pinctrl driver
[    8.039363] mvebu-pcie mbus@f1000000:pcie-controller@82000000: PCI host bridge to bus 0000:00
[    8.039387] pci_bus 0000:00: root bus resource [io  0x1000-0xfffff]
[    8.039404] pci_bus 0000:00: root bus resource [mem 0xe0000000-0xefffffff]
[    8.039420] pci_bus 0000:00: root bus resource [bus 00-ff]
[    8.039779] PCI: bus0: Fast back to back transfers disabled
[    8.039808] pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[    8.039985] PCI: bus1: Fast back to back transfers enabled
[    8.040047] pci 0000:00:01.0: PCI bridge to [bus 01]
[    8.041026] mv_xor f1060800.xor: Marvell shared XOR driver
[    8.101436] mv_xor f1060800.xor: Marvell XOR (Registers Mode): ( xor cpy intr )
[    8.101716] mv_xor f1060900.xor: Marvell shared XOR driver
[    8.161416] mv_xor f1060900.xor: Marvell XOR (Registers Mode): ( xor cpy intr )
[    8.161900] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[    8.163310] console [ttyS0] disabled
[    8.163386] f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 25, base_baud = 10416666) is a 16550A
[    8.832001] console [ttyS0] enabled
[    8.842749] loop: module loaded
[    8.846520] sata_mv f1080000.sata: slots 32 ports 2
[    8.854366] scsi host0: sata_mv
[    8.857931] scsi host1: sata_mv
[    8.861336] ata1: SATA max UDMA/133 irq 32
[    8.865415] ata2: SATA max UDMA/133 irq 32
[    8.870482] nand: device found, Manufacturer ID: 0xad, Chip ID: 0xf1
[    8.876934] nand: Hynix H27U1G8F2BTR-BC
[    8.880787] nand: 128 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[    8.888342] Scanning device for bad blocks
[    8.935343] Bad eraseblock 523 at 0x000004160000
[    8.980940] 5 cmdlinepart partitions found on MTD device orion_nand
[    8.987176] Creating 5 MTD partitions on "orion_nand":
[    8.992324] 0x000000000000-0x000000200000 : "u-boot"
[    8.998362] 0x000000200000-0x000000500000 : "uImage"
[    9.004347] 0x000000500000-0x000000800000 : "uImage2"
[    9.010342] 0x000000800000-0x000001000000 : "failsafe"
[    9.016516] 0x000001000000-0x000008000000 : "root"
[    9.024394] libphy: Fixed MDIO Bus: probed
[    9.029305] libphy: orion_mdio_bus: probed
[    9.038637] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
[    9.202065] ata1: SATA link down (SStatus 0 SControl F300)
[    9.541934] ata2: SATA link down (SStatus 0 SControl F300)
[    9.841226] mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC address 00:25:31:03:ee:6f
[    9.850032] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    9.856593] ehci-pci: EHCI PCI platform driver
[    9.861104] ehci-orion: EHCI orion driver
[    9.865345] orion-ehci f1050000.ehci: EHCI Host Controller
[    9.870871] orion-ehci f1050000.ehci: new USB bus registered, assigned bus number 1
[    9.878692] orion-ehci f1050000.ehci: irq 29, io mem 0xf1050000
[    9.910528] orion-ehci f1050000.ehci: USB 2.0 started, EHCI 1.00
[    9.916774] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    9.923572] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    9.930783] usb usb1: Product: EHCI Host Controller
[    9.935644] usb usb1: Manufacturer: Linux 4.14.1-kirkwood-tld-1 ehci_hcd
[    9.942333] usb usb1: SerialNumber: f1050000.ehci
[    9.947680] hub 1-0:1.0: USB hub found
[    9.951523] hub 1-0:1.0: 1 port detected
[    9.956158] usbcore: registered new interface driver usb-storage
[    9.962547] mousedev: PS/2 mouse device common for all mice
[   11.040521] rtc-mv f1010300.rtc: internal RTC not ticking
[   11.046074] i2c /dev entries driver
[   11.051064] hidraw: raw HID events driver (C) Jiri Kosina
[   11.056820] drop_monitor: Initializing network drop monitor service
[   11.063432] NET: Registered protocol family 17
[   11.067953] Key type dns_resolver registered
[   11.073046] registered taskstats version 1
[   11.077122] Loading compiled-in X.509 certificates
[   11.081999] zswap: loaded using pool lzo/zbud
[   11.109308] Key type big_key registered
[   11.123470] Key type encrypted registered
[   11.128970] hctosys: unable to open rtc device (rtc0)
[   11.138064] Freeing unused kernel memory: 1024K
Loading, please wait...
starting version 232
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... done.
Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
done.
Gave up waiting for root file system device.  Common problems:
 - Boot args (cat /proc/cmdline)
   - Check rootdelay= (did the system wait long enough?)
 - Missing modules (cat /proc/modules; ls /dev)
ALERT!  LABEL=rootfs does not exist.  Dropping to a shell!


BusyBox v1.22.1 (Debian 1:1.22.0-19+b3) built-in shell (ash)
Enter 'help' for a list of built-in commands.

(initramfs)
Re: 4.14.1 kernel kernel panic
January 01, 2018 10:02PM
Jeffrccar,

Your rootfs has problem. When you installed kernel 4.14.1-kirkwood-tld-1, you did not regenerate the uInitrd.

Mount the SD card rootfs on another Linux and examine your /boot. Assuming it was mounted at /media/sdb1,

Please post the output of
ls -lart /media/sdb1/boot

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: 4.14.1 kernel kernel panic
January 01, 2018 10:27PM
sorry, i'm not really sure how to regenerate the uInitrd i tried:
mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs-4.14.1-kirkwood-tld-1 -d initrd.img-4.14.1-kirkwood-tld-1 uInitrd
but i need initrd.img-4.14.1-kirkwood-tld-1.

/boot:
# ls -lart /media/jeff/rootfs/boot
total 72748
drwxr-xr-x 22 root root     4096 Dec 31  1969 ..
-rw-r--r--  1 root root  3876600 Dec 31  1969 uImage
drwxr-xr-x  2 root root     4096 Jul 15 18:14 dts
-rw-r--r--  1 root root   153501 Jul 15 23:21 config-4.12.1-kirkwood-tld-1
-rwxr-xr-x  1 root root  3821528 Jul 16 00:42 zImage-4.12.1-kirkwood-tld-1
-rw-------  1 root root  3821528 Jul 16 03:43 vmlinuz-4.12.1-kirkwood-tld-1
-rw-------  1 root root  2504031 Jul 16 03:43 System.map-4.12.1-kirkwood-tld-1
-rw-r--r--  1 root root  8435004 Jul 16 04:06 linux-headers-4.12.1-kirkwood-tld-1_1.0_armel.deb
-rw-r--r--  1 root root  7245632 Jul 23 20:15 initrd.img-4.12.1-kirkwood-tld-1
-rwxr-xr-x  1 root root  3876536 Nov 23 02:40 zImage.fdt
-rwxr-xr-x  1 root root  3876536 Nov 23 02:40 zImage-4.14.1-kirkwood-tld-1
-rw-r--r--  1 root root   155284 Nov 23 17:41 config-4.14.1-kirkwood-tld-1
-rw-r--r--  1 root root 18713922 Nov 23 18:38 linux-image-4.14.1-kirkwood-tld-1_1.0_armel.deb
-rw-r--r--  1 root root  8731958 Nov 23 18:56 linux-headers-4.14.1-kirkwood-tld-1_1.0_armel.deb
-rw-r--r--  1 root root  1280000 Nov 24 00:48 linux-dtb-4.14.1-kirkwood-tld-1.tar
-rw-r--r--  1 root root   143484 Nov 25 17:59 linux-4.14.1-kirkwood-tld-1.patch
-rw-r--r--  1 root root  3821592 Dec  5 12:55 uImage.orig
-rw-r--r--  1 root root       79 Dec  7 15:23 uEnv.txt
-rw-r--r--  1 root root  3876600 Dec  8 12:05 uImage.new
drwxr-xr-x  3 root root     4096 Dec  8 14:36 .
-rw-r--r--  1 root root        0 Jan  2 00:15 uInitrd
Re: 4.14.1 kernel kernel panic
January 01, 2018 11:15PM
Jeffrccar,

Quote

but i need initrd.img-4.14.1-kirkwood-tld-1.

That means you did not install kernel 4.14.1-kirkwood-tld-1 correctly. This is how we would upgrade to kernel 4.14.1-kirkwood-tld-1.


1. Start with the rootfs Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi.tar.bz2. Create a bootable system.

2. Boot in into this rootfs and then install new kernel. The instruction quote below is for 4.8.0-kirkwood-tld-1, so replace it with 4.14.1-kirkwood-tld-1. And use step 4a to boot with new u-boot (yours is new). Also the DTB should be for your box Pogoplug_V4.

Quote

Installation:


1. Backup your current uImage and uInitrd. In the /boot directory, these are files for your current kernel (xx.xx.xx is the version number):
uInitrd
uImage
initrd.img-xx.xx.xx-kirkwood-xxx
System.map-xx.xx.xx-kirkwood-xxx
vmlinuz-xx.xx.xx-kirkwood-xxx
config-xx.xx.xx-kirkwood-xxx
dts/

2. Extract the kernel and the DTB files in the archive:

cd /boot
tar -xjf linux-4.8.0-kirkwood-tld-1-bodhi.tar.bz2
tar -xf linux-dtb-4.8.0-kirkwood-tld-1.tar

3. And install it with dpkg. Remove flash-kernel first to avoid potential problem (It is much better to generate uImage and uInitrd manually anyway):

cd /boot
apt-get remove flash-kernel
dpkg -i linux-image-4.8.0-kirkwood-tld-1_1.0_armel.deb

4. Create uImage and uInitrd and setup for booting.

I'm using the GoFlex Net booting with USB drive as an example here. Please replace its name (kirkwood-goflexnet.dtb) with the box you are installing on (for example, kirkwood-pogo_e02.dtb). Please look inside /boot/dts/ for the correct DTB file name for your box.

Below are the 2 different alternatives in booting (method 4b is required for booting with older U-Boot that does not support FDT).

- Choose option 4a if you are going to use the current rootfs for many different Kirkwood boxes, as is. It should boot most of the Kirkwood boxes. And with the latest U-Boot for Kirkwood that suports FDT. This is the preferred method.

- Choose option 4b if you only use the current rootfs for the box you're installing on, and don't want to modify u-boot envs. This method is required for booting with older U-Boot that does not support FDT. Note that if you are installing from stock OS, u-boot envs must be modified to boot with USB or HDD (please post questions, since each box has a different flavor in setting up the envs).

4a. Boot with DTB file (standard way to boot FDT kernel). Recommended.


- Generate the uImage and uInitrd.
cd /boot
mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-4.8.0-kirkwood-tld-1 -d vmlinuz-4.8.0-kirkwood-tld-1 uImage
mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs-4.8.0-kirkwood-tld-1 -d initrd.img-4.8.0-kirkwood-tld-1 uInitrd

- Set U-Boot envs for booting. The u-boot envs below are for 1st time upgrading, you don't need to do this step if you've installed the latest U-Boot for Kirkwood. Just make sure the DTB file is the correct one for your box, replace kirkwood-goflexnet.dtb below with the correct DTB name for your box.

fw_setenv load_dtb 'ext2load usb 0:1 0x1c00000 /boot/dts/kirkwood-goflexnet.dtb'
fw_setenv load_initrd 'ext2load usb 0:1 0x1100000 /boot/uInitrd'
fw_setenv load_uimage 'ext2load usb 0:1 0x800000 /boot/uImage'
fw_setenv usb_boot 'run load_dtb; run load_uimage; if run load_initrd; then bootm 0x800000 0x1100000 0x1c00000; else bootm 0x800000 - 0x1c00000; fi'

4b. Boot with DTB file embedded in the kernel image (no U-Boot envs changes are needed if your system already booting on USB or HDD)

Again, please replace kirkwood-goflexnet.dtb below with the correct DTB name for your box.

Generate the uImage and uInitrd:
cd /boot
mv uImage uImage.orig
cp -a zImage-4.8.0-kirkwood-tld-1 zImage.fdt
cat dts/kirkwood-goflexnet.dtb >> zImage.fdt
mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-4.8.0-kirkwood-tld-1 -d zImage.fdt uImage
mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs-4.8.0-kirkwood-tld-1 -d initrd.img-4.8.0-kirkwood-tld-1 uInitrd

5. The new uImage and uInitrd files should be created in /boot directory now. You're ready to reboot the system:
sync
sync
sync
shutdown -r now

-bodhi
===========================
Forum Wiki
bodhi's corner



Edited 1 time(s). Last edit at 01/01/2018 11:16PM by bodhi.
Re: 4.14.1 kernel kernel panic
January 02, 2018 08:43AM
Linux plugandboltv4 4.14.1-kirkwood-tld-1 #1 PREEMPT Wed Nov 22 23:38:14 PST 2017 armv5tel GNU/Linux
Thanks, It works!! i like how the dts isn't embedded so, i can switch hardware without a problem.

cd /boot 
apt-get remove flash-kernel 
dpkg -i linux-image-4.14.1-kirkwood-tld-1_1.0_armel.deb
apparently, i missed this step.
Author:

Your Email:


Subject:


Spam prevention:
Please, solve the mathematical question and enter the answer in the input field below. This is for blocking bots that try to post this form automatically.
Question: how much is 23 plus 2?
Message: