Hi Carl, > As it is working fine, after you activated WOL > with ethtools. Sounds great! wonder if we have the same chip on your WD box and my NAS326?by bodhi - Debian
habibie, ls -lat /var/cache/man/*by bodhi - Debian
alexinc. Sorry I had used the wrong command! please try again: printenv bootargs printenv mtdparts run boot_ubiby bodhi - Rescue System
dietgert, I am not familiar with this u-boot version. Were it built by you? or where did you download it from? > U-Boot SPL 2013.10-g3a0f380-dirty (Jul 26 2014 - > 14:31:34) > U-Boot 2013.10-g3a0f380-dirty (Jul 26 2014 - > 10:18:57) for OXNAS But looks like the cause is right here > ** File not found /boot/bootargs.bin ** > [ 0.000000] Kernel panic - not synby bodhi - uBoot
bchen, No, that's not normal. Try this. Power up, interrupt serial console at countdown and setenv custom_params 'earlyprintk=serial' printenv boot Please post the entire serial console here.by bodhi - Debian
habibie, mount ls -alt /usr/bin/mandb/*by bodhi - Debian
Hi MM, The WOL did not really have any patch other than debug prints while we were trying it. I recall that I've concluded that the network chip has WOL built in and all we need was using ethtools to activate it. So I left the the debug prints in there to see the progress. However, this has not been finalized, WOL still does not work on my NAS326 either.by bodhi - Debian
echowarrior108, It looks like you did it correctly. But you did not post enough information so I can't tell for sure. You might have missed some steps. You could try schee installer to see if it works for you. If it does, then just install new u-boot to NAND and then format a USB rootfs to use as system drive. Once you can boot with NAND u-boot and USB rootfs, you can set up your Sby bodhi - Debian
alexinc, As I said, we are basically a Debian forum, so I can't be certain what's wrong. But I could answer some of your questions. > I fear my problem > may be related to partitioning nand the correct > way as if i recall rightly, cat /proc/mtd doesn't > result in showing any mtds which was the case > before (i have to check that again tonight). You miby bodhi - Rescue System
raffe, You misread the instruction. Booting with separate DTB is recommended only when you are running the new uboot that I released (there is no new LG N1T1 uboot yet). QuoteI try "Boot with DTB file" as you suggest in the post With stock uboot, you must boot with embedded DTB. And you dont really know how to post the log for trouble shooting purpose :) You have posted infby bodhi - Debian
alexinc, I am familiar with OXNAS. But we are only dealing with Debian here. Your problem is OpenWRT related. If you are looking for new uboot, you might want to take a look to see if you can use it: https://forum.doozan.com/read.php?3,16017 However, I dont recall your box was specifically tested or has been proven to work. So keep that in mind. I dont know if it will work.by bodhi - Rescue System
I have edited the post above.by bodhi - Debian
Here is what we should see in the log: copy and paste the terminal session that has all commands executed and its output, from step 1 to step 9 in this post: https://forum.doozan.com/read.php?2,32994,33021#msg-33021by bodhi - Debian
dietgert, 1. Moun the disk in a diffent Linux box and get some info. Assuming this HDD was mount at /media/sdb1. If there is more than 1 partition on the disk then make sure they are all mounted. mount fdisk -l /dev/sdb 2. At u-boot countdown, U-Boot 2013.10-g3a0f380-dirty (Jul 26 2014 - 10:18:57) for OXNAS DRAM: 128 MiB IDE: Bus 0: OK Device 0: Model: ST1500LM006 HN-by bodhi - uBoot
Sure! Let's do that in: https://forum.doozan.com/read.php?2,32994,32994#msg-32994 Post your entire log of the procedure there.by bodhi - Off-Topic
echowarrior108, I would suggest this change in the procedure. Step2: Prepare mbr partition table, and create a single partition type Ext3. sda1: rootfs including boot files with partition name rootfsby bodhi - Off-Topic
echowarrior108, sdf 8:80 0 698.7G 0 disk ├─sdf1 8:81 0 48.9G 0 part /media/russ/rootfs ├─sdf2 8:82 0 61.1G 0 part └─sdf3 8:83 0 588.7G 0 part The look of this structure raises a question. Did you prepare the HDD to boot as Direct SATA booting? As in formatting the disk with a special hex sequence (aka WarheadsSE's magic dust)? None of the partitions here is small enby bodhi - Off-Topic
Ben, > One more thing, I got this error message when I > ran apt-get update/upgrade. Do you know anything > about that? That error seems to cause systemd not > to run. Boot back to sysvinit, do apt-get update/upgrade. And then switch back to systemd.by bodhi - Debian
Ben, > Super! It's working now :D Cool :) > After that, I realized it may be able > to boot up directly using the USB SD card since > you said the wrong Uboot Envs supported USB > booting only. My guess worked it booted up via the > USB card reader. After that, the thing turned a > lot easier..... That's even better than loading uenv script solutionby bodhi - Debian
Tom, > I have installed the Linux-4.15.2-kirkwood-tld-1 > kernel image and what should I say it is working! > :) Excellent! > Now I have only some cosmetic issues from above. > How can I get rid of this warnings and errors? > Unknown command 'ide' - try 'help' > Unknown command 'mmc' - try 'help' Set it to USB only, Dby bodhi - Debian
raffe, > 7. So I try to boot with USB again and restore > backup > > Now it boot up again with the hdd :-) Cool! But too bad you've replaced the 2 new kernel files. We need to look at those files and the boot log at the same time to see clues why it did not boot. Please recreate them, cd /boot cp -a uImage uInitrd ./backup/2018-03-12/ mkimage -A arm -O linuxby bodhi - Debian
I see. Your envs are not good to boot from mmc automatially. You did not flash the default envs image when you went through the u-boot installation. Quote8. Flashing default u-boot envs image (if you are upgrading from 2016.05-tld-1 u-boot, you can skip this step 8). As described in step 1, u-boot envs must be defined in /etc/fw_env.config as # MTD device name Device offset Env. sizby bodhi - Debian
echowarrior108, Sounds like you've exhausted the possibilty. However, your best hope with this box is. 1. Making sure your CP2xxx module converter is working. Can you verify the connection works with a different box? or at least do the loop back TX-RX to see what you type is echoed back. 2. Direct SATA booting. Try this again and tell me what you did in details (best to post the logby bodhi - Off-Topic
Ben, Quotebodhi And then post the entire serial console log here That will tell the story.by bodhi - Debian
Good works, Tommy :)by bodhi - Debian
Ben, Yes, the rootfs is most like the reason. But the DTB file name is wrong, too. Here is what you need to do. 1. Recreate the rootfs, and make sure you follow the instruction closely. 2. Attach the rootfs to the box, power up. 3. Interrupt serial console at count down, and execute setenv devices mmc setenv dtb_file ‘/boot/dts/kirkwood-pogoplug_v4.dtb’ printenv boot Andby bodhi - Debian
raffe, > 6. Boot with DTB file embedded in the kernel > image > > cd /boot > mv uImage uImage.orig > cp -a zImage-4.15.2-kirkwood-tld-1 zImage.fdt > cat dts/kirkwood-goflexnet.dtb >> zImage.fdt The DTB file name is wrong. Should be n1t1. The rest looks OK.by bodhi - Debian
Ben, ------------------------------------------------------- > Hi bodhi, > > I can't believe I missed that typo! After fixing > that, I could get uboot updated using your > release. HOWEVER, my device couldn't boot after I > followed your instructions to upgrade the kernel > (this post, > https://forum.doozan.com/read.php?2,12096). > > I cby bodhi - Debian
rayknight Wrote: ------------------------------------------------------- > bodhi Wrote: > > > rootfs. Ext4 has been troublesome lately (it > does > > not play well with older u-boot Ext4 driver). > > > > When formatting use mkfs.ext4dev instead of > mkfs.ext4 to avoid the issues with older u-boot. Thanks Ray. Is that becasue mkfs.ext4dev defaultby bodhi - uBoot
doblecero, Cool! glad you got everything working. I've looked at the stock OS booting briefly. I was not able to boot the stock kernel with new u-boot (not yet). Perhaps it is time wasting to do this, because we already have a LEDE rescue system built for this box: https://forum.doozan.com/read.php?4,29966by bodhi - uBoot