Welcome! Log In Create A New Profile

Advanced

Linux Kernel 4.19.0 Kirkwood package and Debian rootfs

Posted by bodhi 
Re: Linux Kernel 4.16.1 Kirkwood package and Debian rootfs
April 18, 2018 01:50AM
mpmc,

> On the B however, it was a little harder as there
> was no "initrd.img-4.16.1-kirkwood-tld-1" included
> to the tars so couldn't generate the uinitrd.
> Thankfully I was able to copy it over from the S &
> it booted up fine!

Copy the initrd.img-4.16.1-kirkwood-tld-1 over from a running system would work, as you did! However, that 's is just a temporary work around. The correct thing to do is to install the kernel with dpkg.

https://forum.doozan.com/read.php?2,12096

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.16.1-kirkwood-tld-1_1.0_armel.deb

dpkg installs the kernel and put these kernel files in /boot.

-rw-r--r--  1 root root 154K Apr  9 00:49 config-4.16.1-kirkwood-tld-1
-rw-------  1 root root 2.6M Apr  9 06:34 System.map-4.16.1-kirkwood-tld-1
-rw-------  1 root root 3.9M Apr  9 06:34 vmlinuz-4.16.1-kirkwood-tld-1
-rw-r--r--  1 root root 7.9M Apr 11 17:12 initrd.img-4.16.1-kirkwood-tld-1

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: Linux Kernel 4.16.1 Kirkwood package and Debian rootfs
April 18, 2018 01:53AM
bodhi Wrote:
-------------------------------------------------------
> mpmc,
>
> > On the B however, it was a little harder as
> there
> > was no "initrd.img-4.16.1-kirkwood-tld-1"
> included
> > to the tars so couldn't generate the uinitrd.
> > Thankfully I was able to copy it over from the S
> &
> > it booted up fine!
>
> Copy the initrd.img-4.16.1-kirkwood-tld-1 over
> from a running system would work, as you did!
> However, that 's is just a temporary work around.
> The correct thing to do is to install the kernel
> with dpkg.
>
> https://forum.doozan.com/read.php?2,12096
>
>
> 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.16.1-kirkwood-tld-1_1.0_armel.deb
>
>
> dpkg installs the kernel and put these kernel
> files in /boot.
>
>
> -rw-r--r--  1 root root 154K Apr  9 00:49
> config-4.16.1-kirkwood-tld-1
> -rw-------  1 root root 2.6M Apr  9 06:34
> System.map-4.16.1-kirkwood-tld-1
> -rw-------  1 root root 3.9M Apr  9 06:34
> vmlinuz-4.16.1-kirkwood-tld-1
> -rw-r--r--  1 root root 7.9M Apr 11 17:12
> initrd.img-4.16.1-kirkwood-tld-1
>

I did dpkg the packages :), all but the initrd was installed, it's very odd!
Re: Linux Kernel 4.16.1 Kirkwood package and Debian rootfs
April 18, 2018 02:12AM
> I did dpkg the packages :), all but the initrd was
> installed, it's very odd!

List the /boot in chronological order. It must be there. If not, there is something wrong!

ls -lart /boot

And you can always reinstall the same kernel on top of the same running one.

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



Edited 1 time(s). Last edit at 04/18/2018 02:12AM by bodhi.
Re: Linux Kernel 4.16.1 Kirkwood package and Debian rootfs
April 18, 2018 03:07AM
mark@nsa310s:~$ ls -lart /boot
total 26348
drwxr-xr-x 21 root root    4096 Nov 29 20:12 ..
-rw-r--r--  1 root root  157130 Apr  9 08:49 config-4.16.1-kirkwood-tld-1
-rw-------  1 root root 2633202 Apr  9 14:34 System.map-4.16.1-kirkwood-tld-1
-rw-------  1 root root 4065544 Apr  9 14:34 vmlinuz-4.16.1-kirkwood-tld-1
drwxr-xr-x  2 root root    4096 Apr 10 06:56 dts
-rw-r--r--  1 root root 8016208 Apr 17 13:25 initrd.img-4.16.1-kirkwood-tld-1
-rw-r--r--  1 root root 4065608 Apr 17 13:26 uImage
drwxr-xr-x  3 root root    4096 Apr 17 13:26 .
-rw-r--r--  1 root root 8016272 Apr 17 13:26 uInitrd
mark@nsa310s:~$

mark@nsa310a:~$ ls -lart /boot
total 34444
drwxr-xr-x 21 root root    4096 Apr 27  2017 ..
-rw-r--r--  1 root root  157130 Apr  9 08:49 config-4.16.1-kirkwood-tld-1
-rw-------  1 root root 2633202 Apr  9 14:34 System.map-4.16.1-kirkwood-tld-1
-rw-------  1 root root 4065544 Apr  9 14:34 vmlinuz-4.16.1-kirkwood-tld-1
drwxr-xr-x  2 root root    3072 Apr 17 13:37 dts
-rwxr-xr-x  1 root root 4065544 Apr 17 13:40 zImage-4.16.1-kirkwood-tld-1
-rwxr-xr-x  1 root root 4077826 Apr 17 13:41 zImage.fdt
-rw-r--r--  1 root root 4077890 Apr 17 13:43 uImage
drwxr-xr-x  3 root root    1024 Apr 17 13:51 .
-rw-r--r--  1 root root 8016208 Apr 17 13:52 initrd.img-4.16.1-kirkwood-tld-1
-rw-r--r--  1 root root 8016272 Apr 17 13:52 uInitrd

(a = the b, I just haven't changed the hostname)
Re: Linux Kernel 4.17.2 Kirkwood package and Debian rootfs
June 23, 2018 06:46PM
Kernel linux-4.17.2-kirkwood-tld-1 package has been uploaded. Please see 1st post for download link.

-bodhi
===========================
Forum Wiki
bodhi's corner
I have a couple of Dockstars that I installed Debian on following the original posts in this forum, and I would like to update them to a later kernel and put them to work.

I have downloaded the 4.17 tarball, but when I apply md5sum or sha256sum to the download, I get a different digest than what you have posted here.

What are you using to generate the digests?

Christopher
Re: Linux Kernel 4.17.2 Kirkwood package and Debian rootfs
July 24, 2018 07:37PM
linux-4.17.2-kirkwood-tld-1-bodhi.tar.bz2 

md5: 
cba58ed6f52efe2ea3fffa7e397b725a 
sha256: 
d4a3558072982dd8663cc54cb863998e15708916ad04b874a584909a3cb376a6

md5sum or sha256sum should give you the hash correctly. I've just rerun it.

md5sum linux-4.17.2-kirkwood-tld-1-bodhi.tar.bz2
cba58ed6f52efe2ea3fffa7e397b725a  linux-4.17.2-kirkwood-tld-1-bodhi.tar.bz2

sha256sum linux-4.17.2-kirkwood-tld-1-bodhi.tar.bz2
d4a3558072982dd8663cc54cb863998e15708916ad04b874a584909a3cb376a6  linux-4.17.2-kirkwood-tld-1-bodhi.tar.bz2

-bodhi
===========================
Forum Wiki
bodhi's corner
Thanks for the reply - here is what I get:

md5sum linux-4.17.2-kirkwood-tld-1-bodhi.tar.bz2

5ffededfcc5947cb52ca137eb12fdd74 linux-4.17.2-kirkwood-tld-1-bodhi.tar.bz2

sha256sum linux-4.17.2-kirkwood-tld-1-bodhi.tar.bz2

cb325416d34c6575e894acd3410dac3643baff8ba418bb9809e73c712ab0b3df linux-4.17.2-kirkwood-tld-1-bodhi.tar.bz2

The download link (from the first page) resolves for me to:

https://bitly.com/2ltjz4P

- Christopher
Re: Linux Kernel 4.17.2 Kirkwood package and Debian rootfs
July 25, 2018 06:10PM
My downloading / md5sum / sha256sum is the same as bodhi's
Re: Linux Kernel 4.17.2 Kirkwood package and Debian rootfs
July 25, 2018 08:23PM
daviddyer Wrote:
-------------------------------------------------------
> My downloading / md5sum / sha256sum is the same as
> bodhi's

David, thanks for confirming!

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: Linux Kernel 4.17.2 Kirkwood package and Debian rootfs
July 26, 2018 03:05AM
Christopher,

David has confirmed that the hashes are OK. It must be some mistake you've made. Download and try again.

-bodhi
===========================
Forum Wiki
bodhi's corner
Bodhi, David:

Found the problem - apparently, Dropbox doesn't take kindly to using a right-click to download the target file from a shortened link.

When I followed the link, and downloaded directly from Dropbox, the file hashes match.

Thanks for your patience -

Regards,

Christopher
Re: Linux Kernel 4.17.2 Kirkwood package and Debian rootfs
July 26, 2018 12:52PM
Christopher,

Thanks for letting me know. That shortened link is a little troublesome! I am using it because Dropbox does not give download statistics (bitly gives me the ability to see the download count so I pay more attention to kernels that have most users).

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: Linux Kernel 4.17.2 Kirkwood package and Debian rootfs
July 31, 2018 10:27PM
Last post moved here:
https://forum.doozan.com/read.php?2,64079,64079

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: Linux Kernel 4.17.2 Kirkwood package and Debian rootfs
August 01, 2018 02:47PM
Thank you for the update, Bodhi! :)



Edited 1 time(s). Last edit at 08/01/2018 02:47PM by ElMariachi.
Help needed...

OK, long story short, I was running Pogoplug V4 using Qui's blog. And I was on 3.14.0 for a very long time.

Today, I decided to upgrade to 4.17.2 and also upgrade uboot at the same time. I pretty much followed all instructions, and "keep" some of the old env setting that make sense (or so I thought)

bootcmd=run bootcmd_mmc; run bootcmd_usb; run bootcmd_sata; run bootcmd_pogo; reset
bootcmd_mmc=run mmc_init; run set_bootargs_mmc; run mmc_boot
mmc_boot=mw 0x800000 0 1; run mmc_load_uimage; if run mmc_load_uinitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
mmc_init=mmc rescan
mmc_load_uimage=ext2load mmc $device 0x800000 /boot/uImage
mmc_load_uinitrd=ext2load mmc $device 0x1100000 /boot/uInitrd
mmc_root=/dev/mmcblk0p1

It boots, but now get stuck. At the end, LED goes from solid Orange to solid Green.

U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:34:01 -0700)
Pogoplug V4
gcc (Debian 6.3.0-18) 6.3.0 20170516
GNU ld (GNU Binutils for Debian) 2.28
Hit any key to stop autoboot:  0 

MMC rescan: current device # 0 initialized OK
4125458 bytes read in 131 ms (30 MiB/s)
6284004 bytes read in 195 ms (30.7 MiB/s)
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-4.17.2-kirkwood-tld-1
   Created:      2018-08-04   9:08:32 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    4125394 Bytes = 3.9 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs-4.17.2-kirkwood-tld-1
   Created:      2018-08-04   9:08:49 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    6283940 Bytes = 6 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK


Starting kernel ...

I tried to load the backed up 3.14 uImage and uInitrd but result is the same.

Here is the env (I think it is kind of a mess... and I only need to boot from SD card)

printenv
arcNumber=3960
bootcmd=run bootcmd_mmc; run bootcmd_usb; run bootcmd_sata; run bootcmd_pogo; reset
bootcmd_exec=run load_uimage; if run load_initrd; then if run load_dtb; then bootm $load_uimage_addr $load_initrd_addr $load_dtb_addr; else bootm $load_uimage_addr $load_initrd_addr; fi; else if run load_dtb; then bootm $load_uimage_addr - $load_dtb_addr; else bootm $load_uimage_addr; fi; fi
bootcmd_mmc=run mmc_init; run set_bootargs_mmc; run mmc_boot
bootcmd_uenv=run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi
bootdelay=10
bootdev=mmc
device=0:1
devices=usb ide mmc
disks=0 1 2 3
dtb_file=/boot/dts/kirkwood-pogoplug_v4.dtb
ethact=egiga0
ethaddr=00:25:31:XX:XX:XX
if_netconsole=ping $serverip
ipaddr=192.168.72.118
led_error=orange blinking
led_exit=green off
led_init=green blinking
load_dtb=echo loading DTB $dtb_file ...; load $bootdev $device $load_dtb_addr $dtb_file
load_dtb_addr=0x1c00000
load_initrd=echo loading uInitrd ...; load $bootdev $device $load_initrd_addr /boot/uInitrd
load_initrd_addr=0x1100000
load_uimage=echo loading uImage ...; load $bootdev $device $load_uimage_addr /boot/uImage
load_uimage_addr=0x800000
machid=F78
mainlineLinux=yes
mmc_boot=mw 0x800000 0 1; run mmc_load_uimage; if run mmc_load_uinitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
mmc_init=mmc rescan
mmc_load_uimage=ext2load mmc $device 0x800000 /boot/uImage
mmc_load_uinitrd=ext2load mmc $device 0x1100000 /boot/uInitrd
mmc_root=/dev/mmcblk0p1
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:2M(u-boot),3M(uImage),3M(uImage2),8M(failsafe),112M(root)
nc_ready=1
ncip=192.168.x.x
partition=nand0,2
preboot=run preboot_nc
preboot_nc=setenv nc_ready 0; for pingstat in 1 2 3 4 5; do; sleep 1; if run if_netconsole; then setenv nc_ready 1; fi; done; if test $nc_ready -eq 1; then run start_netconsole; fi
scan_disk=echo running scan_disk ...; scan_done=0; setenv scan_usb "usb start";  setenv scan_ide "ide reset";  setenv scan_mmc "mmc rescan"; for dev in $devices; do if test $scan_done -eq 0; then echo Scan device $dev; run scan_$dev; for disknum in $disks; do if test $scan_done -eq 0; then echo device $dev $disknum:1; if load $dev $disknum:1 $load_uimage_addr /boot/uImage 1; then scan_done=1; echo Found bootable drive on $dev $disknum; setenv device $disknum:1; setenv bootdev $dev; fi; fi; done; fi; done
serverip=192.168.x.y
set_bootargs=setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts $custom_params
set_bootargs_mmc=setenv bootargs console=$console root=$mmc_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
stderr=nc
stdin=nc
stdout=nc
uenv_addr=0x810000
uenv_import=echo importing envs ...; env import -t $uenv_addr $filesize
uenv_init_devices=setenv init_usb "usb start";  setenv init_ide "ide reset";  setenv init_mmc "mmc rescan"; for devtype in $devices; do run init_$devtype; done;
uenv_load=run uenv_init_devices; setenv uenv_loaded 0; for devtype in $devices;  do for disknum in 0; do run uenv_read_disk; done; done;
uenv_read=echo loading envs from $devtype $disknum ...; if load $devtype $disknum:1 $uenv_addr /boot/uEnv.txt; then setenv uenv_loaded 1; fi
uenv_read_disk=if test $devtype -eq mmc; then if $devtype part; then run uenv_read;  fi; else if $devtype part $disknum; then run uenv_read; fi;  fi
usb_ready_retry=15
usb_rootfstype=ext3

Environment size: 3578/131068 bytes

Perhaps it is the old and new mixed together and screwed up?
After reading more, tried
bootcmd=run bootcmd_uenv; sleep 2; run scan_disk; run set_bootargs; run bootcmd_exec; run bootcmd_pogo; reset

Not sure if this helps.... but at the end still stuck at Starting kernel with a solid green light....

Pogov4> boot
boot
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	63        	16015297  	00000000-01	83
loading envs from mmc 0 ...
** File not found /boot/uEnv.txt **
running scan_disk ...
Scan device usb
device usb 0:1
** Bad device usb 0 **
device usb 1:1
** Bad device usb 1 **
device usb 2:1
** Bad device usb 2 **
device usb 3:1
** Bad device usb 3 **
Scan device ide

Reset IDE: ide_preinit failed
device ide 0:1
** Bad device ide 0 **
device ide 1:1
** Bad device ide 1 **
device ide 2:1
** Bad device ide 2 **
device ide 3:1
** Bad device ide 3 **
Scan device mmc

MMC rescan: current device # 0 initialized OK
device mmc 0:1
1 bytes read in 13 ms (0 Bytes/s)
Found bootable drive on mmc 0
loading uImage ...
4125458 bytes read in 131 ms (30 MiB/s)
loading uInitrd ...
6284004 bytes read in 195 ms (30.7 MiB/s)
loading DTB /boot/dts/kirkwood-pogoplug_v4.dtb ...
9962 bytes read in 26 ms (374 KiB/s)
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-4.17.2-kirkwood-tld-1
   Created:      2018-08-04   9:08:32 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    4125394 Bytes = 3.9 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs-4.17.2-kirkwood-tld-1
   Created:      2018-08-04   9:08:49 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    6283940 Bytes = 6 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 01c00000
   Booting using the fdt blob at 0x1c00000


Starting kernel ...

Re: Linux Kernel 4.17.2 Kirkwood package and Debian rootfs
August 27, 2018 10:11AM
Kernel linux-4.18.4-kirkwood-tld-1 package has been uploaded. Please see 1st post for download link.

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



Edited 1 time(s). Last edit at 10/27/2018 04:34PM by bodhi.
Re: Linux Kernel 4.17.2 Kirkwood package and Debian rootfs
October 27, 2018 04:33PM
Kernel linux-4.19.0-kirkwood-tld-1 package has been uploaded. Please see 1st post for download link.


Note:

Please create a new Debian thread for question or problem with your box. This thread is for kernel release and questions that might arise during the new kernel installation.

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



Edited 1 time(s). Last edit at 10/27/2018 04:36PM by bodhi.
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: