Linux Kernel 6.8.7 Kirkwood package and Debian rootfs
Posted by bodhi
|
Re: Linux Kernel 4.16.1 Kirkwood package and Debian rootfs April 18, 2018 02:50AM |
Admin Registered: 13 years ago Posts: 18,555 |
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
dpkg installs the kernel and put these kernel files in /boot.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> 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 (buy bodhi a beer)
|
Re: Linux Kernel 4.16.1 Kirkwood package and Debian rootfs April 18, 2018 02:53AM |
Registered: 7 years ago Posts: 21 |
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
>
>
> dpkg installs the kernel and put these kernel
> files in /boot.
>
>
I did dpkg the packages :), all but the initrd was installed, it's very odd!
---
NSA310s, NSA310, C.H.I.P, Banana Pi, Orange Pi PC & Zero, RPI 1,2Bx8
-------------------------------------------------------
> 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!
---
NSA310s, NSA310, C.H.I.P, Banana Pi, Orange Pi PC & Zero, RPI 1,2Bx8
|
Re: Linux Kernel 4.16.1 Kirkwood package and Debian rootfs April 18, 2018 03:12AM |
Admin Registered: 13 years ago Posts: 18,555 |
> 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!
And you can always reinstall the same kernel on top of the same running one.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 04/18/2018 03:12AM by bodhi.
> 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 (buy bodhi a beer)
Edited 1 time(s). Last edit at 04/18/2018 03:12AM by bodhi.
|
Re: Linux Kernel 4.16.1 Kirkwood package and Debian rootfs April 18, 2018 04:07AM |
Registered: 7 years ago Posts: 21 |
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)
---
NSA310s, NSA310, C.H.I.P, Banana Pi, Orange Pi PC & Zero, RPI 1,2Bx8
|
Re: Linux Kernel 4.17.2 Kirkwood package and Debian rootfs June 23, 2018 07:46PM |
Admin Registered: 13 years ago Posts: 18,555 |
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 (buy bodhi a beer)
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Christopher
Re: Linux Kernel 4.17.2 Kirkwood package and Debian rootfs July 24, 2018 08:19PM |
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
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 08:37PM |
Admin Registered: 13 years ago Posts: 18,555 |
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 (buy bodhi a beer)
|
Christopher
Re: Linux Kernel 4.17.2 Kirkwood package and Debian rootfs July 25, 2018 04:58PM |
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
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 07:10PM |
Registered: 7 years ago Posts: 366 |
|
Re: Linux Kernel 4.17.2 Kirkwood package and Debian rootfs July 25, 2018 09:23PM |
Admin Registered: 13 years ago Posts: 18,555 |
daviddyer Wrote:
-------------------------------------------------------
> My downloading / md5sum / sha256sum is the same as
> bodhi's
David, thanks for confirming!
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-------------------------------------------------------
> My downloading / md5sum / sha256sum is the same as
> bodhi's
David, thanks for confirming!
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Linux Kernel 4.17.2 Kirkwood package and Debian rootfs July 26, 2018 04:05AM |
Admin Registered: 13 years ago Posts: 18,555 |
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 (buy bodhi a beer)
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 (buy bodhi a beer)
|
Christopher
Re: Linux Kernel 4.17.2 Kirkwood package and Debian rootfs July 26, 2018 05:47AM |
|
Re: Linux Kernel 4.17.2 Kirkwood package and Debian rootfs July 26, 2018 01:52PM |
Admin Registered: 13 years ago Posts: 18,555 |
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 (buy bodhi a beer)
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 (buy bodhi a beer)
|
Re: Linux Kernel 4.17.2 Kirkwood package and Debian rootfs July 31, 2018 11:27PM |
Admin Registered: 13 years ago Posts: 18,555 |
Last post moved here:
https://forum.doozan.com/read.php?2,64079,64079
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
https://forum.doozan.com/read.php?2,64079,64079
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Linux Kernel 4.17.2 Kirkwood package and Debian rootfs August 01, 2018 03:47PM |
Registered: 7 years ago Posts: 90 |
|
Derek
Re: Linux Kernel 4.17.2 Kirkwood package and Debian rootfs August 04, 2018 05:25AM |
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)
It boots, but now get stuck. At the end, LED goes from solid Orange to solid Green.
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)
Perhaps it is the old and new mixed together and screwed up?
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?
|
Derek
Re: Linux Kernel 4.17.2 Kirkwood package and Debian rootfs August 04, 2018 05:39AM |
After reading more, tried
Not sure if this helps.... but at the end still stuck at Starting kernel with a solid green light....
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 11:11AM |
Admin Registered: 13 years ago Posts: 18,555 |
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 (buy bodhi a beer)
Edited 1 time(s). Last edit at 10/27/2018 05:34PM by bodhi.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 10/27/2018 05:34PM by bodhi.
|
Re: Linux Kernel 4.17.2 Kirkwood package and Debian rootfs October 27, 2018 05:33PM |
Admin Registered: 13 years ago Posts: 18,555 |
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 (buy bodhi a beer)
Edited 1 time(s). Last edit at 10/27/2018 05:36PM by bodhi.
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 (buy bodhi a beer)
Edited 1 time(s). Last edit at 10/27/2018 05:36PM by bodhi.
|
Re: Linux Kernel 4.19.0 Kirkwood package and Debian rootfs November 13, 2018 08:41AM |
Registered: 11 years ago Posts: 1,303 |
bodhi Wrote:
-------------------------------------------------------
> Updated 24 Jul 2017:
>
> Basic Debian stretch Kirkwood rootfs for most Kirwood plugs:
>
> - tarball size: 188M
> - install size: 488M
> - The init system used in this rootfs is sysvinit. To boot with systemd, see note 2 below.
> - Installed packages: nano, avahi, ntp, busybox-syslogd (log to RAM), htop, isc-dhcp-client, dialog, bzip2, nfs server/client, iperf, ethtool, sysvinit-core, sysvinit, and sysvinit-utils.
> - see LED controls in /etc/rc.local, and /etc/init.d/halt
> - see some useful aliases in /root/.profile
> - root password: root
>
> Download at Dropbox:
>
> Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi.tar.bz2
>
>
> md5: bf3d29569943875df348fb5ca03b348c
> sha256: 4ed5714fdb123cdb40e973f3d0754e91cd199b75a9874018f2b5dc9cfa8ae8bb
>
> And remember to check the hash of what you download, as always.
>
I just clicked the above link and it took me to a dropbox page with an empty list. Did I do something wrong?
-------------------------------------------------------
> Updated 24 Jul 2017:
>
> Basic Debian stretch Kirkwood rootfs for most Kirwood plugs:
>
> - tarball size: 188M
> - install size: 488M
> - The init system used in this rootfs is sysvinit. To boot with systemd, see note 2 below.
> - Installed packages: nano, avahi, ntp, busybox-syslogd (log to RAM), htop, isc-dhcp-client, dialog, bzip2, nfs server/client, iperf, ethtool, sysvinit-core, sysvinit, and sysvinit-utils.
> - see LED controls in /etc/rc.local, and /etc/init.d/halt
> - see some useful aliases in /root/.profile
> - root password: root
>
> Download at Dropbox:
>
> Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi.tar.bz2
>
>
> md5: bf3d29569943875df348fb5ca03b348c
> sha256: 4ed5714fdb123cdb40e973f3d0754e91cd199b75a9874018f2b5dc9cfa8ae8bb
>
> And remember to check the hash of what you download, as always.
>
I just clicked the above link and it took me to a dropbox page with an empty list. Did I do something wrong?
|
Re: Linux Kernel 4.19.0 Kirkwood package and Debian rootfs November 13, 2018 11:24AM |
Registered: 9 years ago Posts: 226 |
|
Re: Linux Kernel 4.19.0 Kirkwood package and Debian rootfs November 14, 2018 09:33AM |
Registered: 11 years ago Posts: 1,303 |
|
Re: Linux Kernel 4.19.0 Kirkwood package and Debian rootfs November 15, 2018 05:35PM |
Admin Registered: 13 years ago Posts: 18,555 |
This thread is temporary closed until the next release.
Please create a new Debian thread for question or problem with your box.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Please create a new Debian thread for question or problem with your box.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Linux Kernel 4.19.0 Kirkwood package and Debian rootfs February 03, 2019 12:33PM |
Admin Registered: 13 years ago Posts: 18,555 |
Kernel linux-4.20.6-kirkwood-tld-1 package has been uploaded. Please 1st post for download link.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 02/03/2019 12:34PM by bodhi.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 02/03/2019 12:34PM by bodhi.
|
Re: Linux Kernel 4.19.0 Kirkwood package and Debian rootfs February 05, 2019 07:21AM |
Admin Registered: 13 years ago Posts: 18,555 |
Last post moved here:
https://forum.doozan.com/read.php?2,77489,77489#msg-77489
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
https://forum.doozan.com/read.php?2,77489,77489#msg-77489
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Linux Kernel 4.20.6 Kirkwood package and Debian rootfs February 19, 2019 04:12PM |
Registered: 5 years ago Posts: 4 |
Hi Bodhi,
First of all I want to than you for your amazing work on this project.
I recently updated kernel to v4.20 and I fall into problem with it. The network interface on my NSA-310 is not present anymore. I had to revert to kernel 4.19.
Please find enclosed boot logs from both versions.
Here are some suspicious entries from 4.20
while in 4.19 it is:
First of all I want to than you for your amazing work on this project.
I recently updated kernel to v4.20 and I fall into problem with it. The network interface on my NSA-310 is not present anymore. I had to revert to kernel 4.19.
Please find enclosed boot logs from both versions.
Here are some suspicious entries from 4.20
[ 9.417625] scsi host2: usb-storage 1-1.3:1.0 [ 9.422994] r8169 0000:01:00.0 (unnamed net_device) (uninitialized): rtl_phyar_cond == 0 (loop: 20, delay: 25). [ 9.500599] r8169: probe of 0000:01:00.0 failed with error -5 [ 9.923003] usbcore: registered new interface driver uas Begin: Loading essential drivers ... done.
while in 4.19 it is:
[ 9.241677] scsi host2: usb-storage 1-1.3:1.0 [ 9.287800] libphy: r8169: probed [ 9.293316] r8169 0000:01:00.0 eth0: RTL8168d/8111d, 00:00:00:00:00:30, XID 283000c0, IRQ 35 [ 9.338351] r8169 0000:01:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko] [ 9.769993] usbcore: registered new interface driver uas [ 9.808411] r8169 0000:01:00.0 enp1s0: renamed from eth0 Begin: Loading essential drivers ... done.
|
Re: Linux Kernel 4.20.6 Kirkwood package and Debian rootfs February 19, 2019 05:40PM |
Admin Registered: 13 years ago Posts: 18,555 |
drakulis Wrote:
-------------------------------------------------------
> Hi Bodhi,
>
> First of all I want to than you for your amazing
> work on this project.
>
> I recently updated kernel to v4.20 and I fall into
> problem with it. The network interface on my
> NSA-310 is not present anymore. I had to revert to
> kernel 4.19.
>
> Please find enclosed boot logs from both
> versions.
>
> Here are some suspicious entries from 4.20
>
> while in 4.19 it is:
>
Thanks for the report and confirmation!
It looks like mainline is having this problem. See arti reported it here:
https://forum.doozan.com/read.php?2,77609
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-------------------------------------------------------
> Hi Bodhi,
>
> First of all I want to than you for your amazing
> work on this project.
>
> I recently updated kernel to v4.20 and I fall into
> problem with it. The network interface on my
> NSA-310 is not present anymore. I had to revert to
> kernel 4.19.
>
> Please find enclosed boot logs from both
> versions.
>
> Here are some suspicious entries from 4.20
>
> [ 9.417625] scsi host2: usb-storage 1-1.3:1.0 > [ 9.422994] r8169 0000:01:00.0 (unnamed > net_device) (uninitialized): rtl_phyar_cond == 0 > (loop: 20, delay: 25). > [ 9.500599] r8169: probe of 0000:01:00.0 failed > with error -5 > [ 9.923003] usbcore: registered new interface > driver uas > Begin: Loading essential drivers ... done. >>
> while in 4.19 it is:
>
> [ 9.241677] scsi host2: usb-storage 1-1.3:1.0 > [ 9.287800] libphy: r8169: probed > [ 9.293316] r8169 0000:01:00.0 eth0: > RTL8168d/8111d, 00:00:00:00:00:30, XID 283000c0, > IRQ 35 > [ 9.338351] r8169 0000:01:00.0 eth0: jumbo > features [frames: 9200 bytes, tx checksumming: > ko] > [ 9.769993] usbcore: registered new interface > driver uas > [ 9.808411] r8169 0000:01:00.0 enp1s0: renamed > from eth0 > Begin: Loading essential drivers ... done. >
Thanks for the report and confirmation!
It looks like mainline is having this problem. See arti reported it here:
https://forum.doozan.com/read.php?2,77609
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Linux Kernel 5.1.0 Kirkwood package and Debian rootfs May 13, 2019 03:39AM |
Admin Registered: 13 years ago Posts: 18,555 |
Kernel linux-5.1.0-kirkwood-tld-1 package has been uploaded. Please see 1st post for download link.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Linux Kernel 5.1.0 Kirkwood package and Debian rootfs May 16, 2019 08:24PM |
Registered: 11 years ago Posts: 1,303 |
bodhi Wrote:
-------------------------------------------------------
> Kernel linux-5.1.0-kirkwood-tld-1 package has been uploaded. Please see 1st post for download link.
>
Bodhi,
My Seagate Dockstar has the following u-boot and I believe it has a support for FDT. As such, I should use option 4a to upgrade to linux-5.1.0-kirkwood-tld-1, shouldn't I?
-------------------------------------------------------
> Kernel linux-5.1.0-kirkwood-tld-1 package has been uploaded. Please see 1st post for download link.
>
Bodhi,
My Seagate Dockstar has the following u-boot and I believe it has a support for FDT. As such, I should use option 4a to upgrade to linux-5.1.0-kirkwood-tld-1, shouldn't I?
DockStar> version U-Boot 2017.07-tld-1 (Oct 24 2017 - 22:32:36 -0700) Seagate FreeAgent DockStar gcc (Debian 6.3.0-18) 6.3.0 20170516 GNU ld (GNU Binutils for Debian) 2.28 DockStar>
|
Re: Linux Kernel 5.1.0 Kirkwood package and Debian rootfs May 16, 2019 08:43PM |
Admin Registered: 13 years ago Posts: 18,555 |
habibie Wrote:
-------------------------------------------------------
> bodhi Wrote:
> -------------------------------------------------------
> > Kernel linux-5.1.0-kirkwood-tld-1 package has
> been uploaded. Please see 1st post for download
> link.
> >
> Bodhi,
>
> My Seagate Dockstar has the following u-boot and I
> believe it has a support for FDT. As such, I
> should use option 4a to upgrade to
> linux-5.1.0-kirkwood-tld-1, shouldn't I?
>
>
4a is correct. If you run into problem, create a new thread for it.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-------------------------------------------------------
> bodhi Wrote:
> -------------------------------------------------------
> > Kernel linux-5.1.0-kirkwood-tld-1 package has
> been uploaded. Please see 1st post for download
> link.
> >
> Bodhi,
>
> My Seagate Dockstar has the following u-boot and I
> believe it has a support for FDT. As such, I
> should use option 4a to upgrade to
> linux-5.1.0-kirkwood-tld-1, shouldn't I?
>
>
DockStar> version > > U-Boot 2017.07-tld-1 (Oct 24 2017 - 22:32:36 > -0700) > Seagate FreeAgent DockStar > gcc (Debian 6.3.0-18) 6.3.0 20170516 > GNU ld (GNU Binutils for Debian) 2.28 > DockStar>
4a is correct. If you run into problem, create a new thread for it.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Sorry, you can't reply to this topic. It has been closed.