blackdevil, That's strange. Because this apparently modifiable. The bootcmd: bootcmd=setenv bootargs $(bootargs_console) $(bootargs_root); run bootcmd_scsi Try setenv bootcmd 'setenv bootargs $(bootargs_console) $(bootargs_root) earlyprintk=serial; run bootcmd_scsi'by bodhi - Debian
dexter is correct. The bootargs need to be reset in the bootcmd_lede. setenv bootargs_lede setenv bootargs $console $mtdpartsby bodhi - Rescue System
Gravelrash, > has anyone tried this on there plug? I have been > looking around to see if I can find the minimum > spec to run it and either my google-fu or aged > eyes havent allowed me to find it. I'm not aware of that min spec, either. > Im interested in attempting to run this on my last > remaining kirkwood device. just for fun i would > like to createby bodhi - Off-Topic
@Mark, Which BlackArmor box do you have, could you post the model number? I thought all Seagate BlackArmor have Marvel SoC, not Cavium SoC. Apparently you have one with Cavium!by bodhi - Debian
blackdevil, > Maybe I should not boot from a 2.5" disk in the > USM port? That's OK. The kernel has loaded and run so the disk can be used. You need to specify earlyprink=serial in bootargs to see more why it seems to hang. At serial console, list the envs printenv and post output here in code tag.by bodhi - Debian
All, Quote> The modprobe/kernel paging issue still exists: It's the same kernel as before! so it is expected. Quote4.14.24-cns3xxx-tld-1.with-native-rootfs.boot.log (13.1 KB) This log is interesting! we got a lot further, even with stock rootfs. Quote4.14.24-cns3xxx-tld-1.with-bodhi-sda1.boot.log (11.7 KB) This log also showed basically the same thing, but with same knownby bodhi - Debian
I've uploaded the rootfs Debian-4.14.24-cns3xxxx-tld-1-rootfs-bodhi.tar.bz2. Please see 1st post for download link.by bodhi - Debian
doblecero, > I understand steps will be, being in u-boot > command line: > > > flash_erase /dev/mtd0 0 4 > nandwrite /dev/mtd0 mtd0_backup_uboot > > > mtd0_backup_uboot -> contains the back taken with > > nanddump --noecc --omitoob -l 0x80000 -f mtd0 > /dev/mtd0 > > will the above also restore environment as it > previously was?by bodhi - uBoot
So I changed the subject title for this sticky thread to "General Discussion". Please post whatever come to your mind, or that can be an improvement to the forum.by bodhi - Off-Topic
Whatever Jeff does is fine with me! When spams come in as individual threads, where I clean up that up a few times a day, it is fine for me to manage. When it got through with hundred of posts in hundreds of existing threads, I notify Jeff and he would delete the account therefore its associated posts. It's a break from the forum duty once in a while for me :) Just let it be.by bodhi - Off-Topic
I am uploading the basic rootfs for Cavium CNS3xxx with kernel 4.14.24-cns3xxx-tld-1.by bodhi - Debian
MarkTurner Wrote: ------------------------------------------------------- > MarkTurner Wrote: > ------------------------------------------------------- > > Actually, I just remembered the QEMU ARM > emulation > > trick! I've used this before to use my laptop > to > > compile apps for my RPi. > > > https://hblok.net/blog/posts/2014/02/06/chrootby bodhi - Debian
tommy, > I have no luck going past "booting kernel" message > with the new images from bodhi. > Mark, could you please share your uImage and > initrd or at last least provide some info how did > you created it? You need to install the kernel with dpkg. But I think I can see why there is confusion. The kernel need to be installed on a rootfs. So to avoiby bodhi - Debian
Mark Don't use 3.18.5. Generate the new uInird for 4.14.24 using this format. mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs-4.15.2-kirkwood-tld-1 -d initrd.img-4.15.2-kirkwood-tld-1 uInitrdby bodhi - Debian
doblecero, > Any help to restore the ability to boot the stock > zyxel image is greatly appreciated. I need to boot > up that one one last time to recover data I have > in the JOBD partition before going with OMV. You need to flash the orginal u-boot back to mtd0 to boot stock OS. When you installed new uboot, did you do step 3? Quote3. Be sure to save your current uBoot iby bodhi - uBoot
doblecero, Please continue to post after I've merged your post to a different thread. This thread is not appropriate to get help with problem.by bodhi - uBoot
Mark, Post your mkimage commands to generate the uImage and uInitrd mkimage -A arm -O linux -T kernel -C none -a ............. mkimage -A arm -O linux -T ramdisk -C gzip -a ............by bodhi - Debian
Mark's log showed a familiar kernel panic. I think the kernel config needs more switches enabled for this ARM11 specifically.by bodhi - Debian
blackdevil Wrote: ------------------------------------------------------- > seems good. But where do I get the uInitrd file? > It it is not in the your start post isnt it? You would create it and the uImage the same way as in other kernels. For example, the Kirkwood kernel: https://forum.doozan.com/read.php?2,12096 mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x000by bodhi - Debian
Hi Mark, Please try: 1. With a USB drive attached, and a HDD attached. Power up, interrupt serial console and list the envs and also the commands available. bdinfo usb reset ide reset printenv help 2. And then set up the envs to boot the same way you did. Boot. Please post the boot log here in code tags.by bodhi - Debian
@Mark, Excellent! So we know the kernel has started and run. You've got pretty far :) SATA seems to work too. I will take a closer look at the log. @blackdevil, This stock u-boot has FDT supports, as Mark verified in his log. The boot command is Whitney # bootm 0x2000000 0x5100000 0x5000000 So you can boot with the DTB separately, and should boot with with uImage and uInitby bodhi - Debian
joerg_999 Wrote: ------------------------------------------------------- > hallo bodhi, > i´ve tried your suggestion and it > worked also without any arcNumber.... > LEDE and debian > > -- joerg_999 Cool!by bodhi - Rescue System
Damn! this spam wave is pretty bad, too. Looks like it is coming back.by bodhi - Off-Topic
I've upload the linux-4.14.24-cns3xxxx-tld-1 package. Please see 1st post for download link. This is an experimental release. So if it boots then it is a big step forward :)by bodhi - Debian
tommy, > think we still would need to fit those drivers to > the kernel source (as they are not included in the > mainline), right? What I understand the DTS file > is only the instruction for the kernel which > drivers to load, but those drivers need to be > present in the kernel. The DTS file really > substitutes the device-specific initialization > files in arby bodhi - Debian
Kuzma, > Where i can find > initrd.img-4.15.2-kirkwood-tld-1? Yes, like butaford said. You did not install the kernel with dpkg -i. It is automatically generated in step 3. QuoteUpdated 11 Feb 2018: Kernel linux-4.15.2-kirkwood-tld-1 package has been uploaded. The following features were added/updated: - Added HP T5325 flash type mx25l8005. - Added USBIP supports.by bodhi - Debian
Eslon, New U-Boot was installed OK. The rootfs Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi.tar.bz2 creation has problem. When you create this rootfs, note this step 4: Quote4. Create uImage with embedded DTB for booting with older u-boots (2012 or earlier). Skip this step if you have installed the latest U-Boot for Kirkwood (or are installing this u-boot at the same time). Please replaby bodhi - uBoot
blackdevil, ------------------------------------------------------- > I didnt get kernel 3.18 to work. I got only 4.4 to > work, but some things are missing. May we can have > a look at the patches which I posted earlier and > build a dts file from it? > > Is FDT support just a kernel switch? It is a combination of a few switches. And those will activate and compilby bodhi - Debian
joerg, Try remove arcNumber temorarily in serial console setenv arcNumber And boot boot See it will boot into LEDE. By the way, this is not needed to do. setenv bootargs_lede ' ' And these 2 should not be done, because you want to keep these envs for booting with Debian on USB. In booting LEDE, the env set_bootargs_lede is enough. setenv bootargs setenv consolby bodhi - Rescue System
So basically we need to rebuild the kernel with FDT support. And use a new DTS written for Cavium CNS3xxxx SoC.by bodhi - Debian