Quantcast
Channel: Linux Device Hacking
Viewing all articles
Browse latest Browse all 3247

Problem booting Linux Kernel 4.4.79 Oxnas (OX820) Pogo V3 (1 reply)

$
0
0
bodhi,

I have just updated the kernel image on my Pogo Pro to 4.4.79-oxnas-tld-1 and it fails to boot. After attaching a serial port to the device I see that it hangs after showing the following text:

U-Boot SPL 2013.10-tld-4 (Sep 07 2014 - 14:10:12)
  Boot device: NAND
Attempting to set PLLA to 850 MHz ...
  plla_ctrl0 : 0000020a
  plla_ctrl1 : 00330000
  plla_ctrl2 : 0065008b
  plla_ctrl3 : 000000f1

PLLA Set


U-Boot 2015.10-tld-1 (Nov 21 2015 - 01:17:59 -0800)
OXNAS OX820

DRAM:  128 MiB
NAND:  128 MiB
In:    serial
Out:   serial
Err:   serial
Net:   dwmac.40400000
Hit any key to stop autoboot:  0 

Reset IDE: Bus 0: OK 
  Device 0: Model: FUJITSU MHZ2250BH G1 Firm: 0040020C Ser#: K61DT942DF7V
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 238475.1 MB = 232.8 GB (488397168 x 512)
starting USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found

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

Part	Start Sector	Num Sectors	UUID		Type
  1	2048      	478150656 	a68080b4-01	83
  2	478152704 	10244464  	a68080b4-02	82
loading envs from ide 0 ...
** File not found /boot/uEnv.txt **

no USB devices available
running scan_disk ...
Scan device ide

Reset IDE: Bus 0: OK 
  Device 0: Model: FUJITSU MHZ2250BH G1 Firm: 0040020C Ser#: K61DT942DF7V
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 238475.1 MB = 232.8 GB (488397168 x 512)
device ide 0:1
1 bytes read in 92 ms (0 Bytes/s)
Found bootable drive on ide 0
loading uImage ...
4619104 bytes read in 3514 ms (1.3 MiB/s)
loading uInitrd ...
4236902 bytes read in 3155 ms (1.3 MiB/s)
loading DTB /boot/dts/ox820-pogoplug-pro.dtb ...
7067 bytes read in 97 ms (70.3 KiB/s)
## Booting kernel from Legacy Image at 60500000 ...
   Image Name:   Linux-4.4.79-oxnas-tld-1
   Created:      2017-08-06  20:40:20 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    4619040 Bytes = 4.4 MiB
   Load Address: 60008000
   Entry Point:  60008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 60e00000 ...
   Image Name:   initramfs-4.4.79-oxnas-tld-1
   Created:      2017-08-06  20:40:26 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    4236838 Bytes = 4 MiB
   Load Address: 60000000
   Entry Point:  60000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 62c00000
   Booting using the fdt blob at 0x62c00000
   Loading Kernel Image ... OK
   Loading Ramdisk to 67a21000, end 67e2b626 ... OK
   Loading Device Tree to 67a1c000, end 67a20b9a ... OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

I also noted that the updated installation instructions append the appropriate flattened device tree image to the end of the kernel, but I don't know if that's really necessary. My Pogo's u-boot loads the .dtb file off the boot device, as shown above, so why does it need to be included in the kernel image loaded by u-boot? I tried booting the Pogo with a kernel image with the .dtb file appended to it and with a kernel image without the .dtb file appended to it and both times my Pogo failed to boot.

Viewing all articles
Browse latest Browse all 3247

Trending Articles