Nirmal, 1. Your HDD partitions were not recognized by u-boot. You will need to repartition the HDD. And create the rootfs again. Scan device ide Reset IDE: Bus 0: OK Bus 1: not available Device 0: Model: ST1000LM024 HN-M101MBB Firm: 2AR20002 Ser#: S2ZPJ9AD343686 Type: Hard Disk Supports 48-bit addressing Capacity: 953869.7 MB = 931.5 GB (195352by bodhi - Debian
Jxjhheric, > How can I get USB boot first, and if there is on > USB, Boot NFS? This is quite easy, but to make sure I give you the correct intruction, please repost your evns. Log into Debian (you don't need to do this in serial console anymore), list the envs, and post here. fw_printenvby bodhi - uBoot
Jxjhheric Wrote: ------------------------------------------------------- > Wrote: > ------------------------------------------------------- > > Look at this post: > > https://forum.doozan.com/read.php?2,28351 > > > > See my uboot env to boot NFS rootfs at the end > of > > the post. > > can't login now > > > [....] Initiaby bodhi - uBoot
QuoteThe main thing which doesn't work so far is the ethernet connection. All commands are send through serial at the moment. I guess this is due to the fact that a generic dove.dtb file was used to embed in the uImage. Is there a way to create a better dtb file by analysing the original / stock system? Look for what network chip is in this box. And then a new DTS for this box must be be cby bodhi - Debian
Nirmal, If you have serial console or netconsole, please post the entire boot log.by bodhi - Debian
Koen, > Success! The recovery method has worked and the > device has booted into Debian as shown by the > serial output below. Cool :) The boot log looks very good. > I'm not getting any graphics > on the screen and I'm sure there will be other > issues but this feels like a mayor step forward. The bootargs probably needs more adjustment to see graphby bodhi - Debian
Look at this post: https://forum.doozan.com/read.php?2,28351 See my uboot env to boot NFS rootfs at the end of the post.by bodhi - uBoot
Koen Wrote: ------------------------------------------------------- > OK the method of changing kernel parameters > through the wloader program seems to work OK. I've > changed the kernel boot args to the following: > > > rootdelay=20 root=/dev/sdb1 pm_disable > usb0Mode=host usb1Mode=host > video=dovefb:lcd0:1024x768-32@60,lcd1:1024x768-32@60 > clcd.lcby bodhi - Debian
Try: setenv console ‘ttyS0,115200’ bootby bodhi - uBoot
krzysiek Wrote: ------------------------------------------------------- > Hello > I have a different but similar problem. > during the uploading of the uboot by the COM > (serial) there was no power. > after this fact, the stora is cold. I am not sure what you described. Did you run kwboot and got no response from the box? If you did, please post the log here (kwboot cby bodhi - uBoot
Your u-boot envs are messed up. Power up, interrupt serial console and: printenv And post the serial boot log here.by bodhi - uBoot
Koen Wrote: ------------------------------------------------------- > It seems that I've reached a dead end for now. If > I have time I will try to read the spi chip using > a raspberry pi this weekend. If that works I can > write new kernel boot parameters to spi using the > spi-w command and use the raspberry pi to restore > the spi if it ends up locking me out ofby bodhi - Debian
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).by bodhi - Debian
Christopher, David has confirmed that the hashes are OK. It must be some mistake you've made. Download and try again.by bodhi - Debian
daviddyer Wrote: ------------------------------------------------------- > My downloading / md5sum / sha256sum is the same as > bodhi's David, thanks for confirming!by bodhi - Debian
Awesome! Thanks Martin.by bodhi - uBoot
Derek, > root@pogoplug:~# cat /etc/fw_env.config > # MTD device name Device offset Env. size Flash > sector size Number of sectors > /dev/mtd0 0xc0000 0x20000 0x20000 > root@pogoplug:~# cat /proc/mtd > dev: size erasesize name > mtd0: 00200000 00020000 "u-boot" > mtd1: 00300000 00020000 "uImage" > mtd2: 00300000 00020000 "uImaby bodhi - uBoot
Koen > Is there a way to get any additional info from > deconstructing the .img files I've extracted from > the device? Or is that not possible? There is no value in doing that. This kernel is too old, so nothing in there would be of interest. We already know the SoC, and the kernel DTB that will boot this SoC.by bodhi - Debian
rayknight Wrote: ------------------------------------------------------- > bodhi Wrote: > ------------------------------------------------------- > > > BTW, it is best if you can find GPL for this > Dell > > FW. They must provide it somewhere as legally > > required. When we see GPL, we'll know for sure > > what to do. > > > > Gby bodhi - Debian
Martin, > 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-2 (Oct 21 2017 - 22:00:02 > -0700) > OXNAS OX820 > Cool! &gby bodhi - uBoot
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-by bodhi - Debian
Koen, BTW, it is best if you can find GPL for this Dell FW. They must provide it somewhere as legally required. When we see GPL, we'll know for sure what to do. > OK I've created the rootfs USB and tried to boot > it but it doesn't work yet. It is difficult to > know what is happening without serial console > output. True. > There is a quick message oby bodhi - Debian
ExtremelyCassidy, There is not enough information to tell what went on in this rootfs! So the first thing you should do is getting info about your Debian installation on this this drive. - Plug in the USB rootfs to another Linux box. - If it is automounted then umount it and run check disk to fix errors (if the drive as assigned sdb1): e2fsck /dev/sdb1 - Mount it again and (assby bodhi - uBoot
Koen, Quote- look for why the bootargs is different from the boot_normal.scr and the actual bootargs. IOW, are the actual parameters hard coded in the kernel or somehow was changed on top of the boot script. So we know where the bootargs was taken from. Now we need to see the boot sequence to make sure we know how to boot the Debian USB. Information you posted so far seems to point to theby bodhi - Debian
The next step: - look for why the bootargs is different from the boot_normal.scr and the actual bootargs. IOW, are the actual parameters hard coded in the kernel or somehow was changed on top of the boot script. - Change boot script to make it slightly different cat boot-normal.txt fatload ide 0:1 0x200000 /uImage setenv bootargs pm_disable root=/dev/sda3 vmalloc=384M mimas quiet rby bodhi - Debian
QuoteThe standard operating system doesn't have the fw_printenv command. However it does contain the command fconfig which seems to be related to redboot. Could it be that the system uses the redboot bootloader instead of uboot? It could be. But not likely.by bodhi - Debian
> I'm not sure if this is useful but this is the > output when the system is booted normally from the > internal memory. > > > root@LWT008064aa7d6c:~# cat /proc/mtd > dev: size erasesize name > root@LWT008064aa7d6c:~# cat /etc/fw_env.config > # MTD device offset size erase_size > /dev/mtd0 0xc0000 0x10000 0x10000 > It means u-boot is onby bodhi - Debian
Ok. It is very promising. However, boot-normal.scr is not what used when the kernel was actually booted. root@LWT008064aa7d6c:/mnt/temp1# cat boot-normal.scr fatload ide 0:1 0x200000 /uImage setenv bootargs pm_disable root=/dev/sda3 vmalloc=384M mimas quiet bootm 0x200000 Kernel command line: root=/dev/sda3 pm_disable usb0Mode=host usb1Mode=host video=dovefb:lcd0:1024x768-32@60,lcdby bodhi - Debian
Koen, There are quite a bit of info to digest! I'm busy right now, will take a look at your posts and fill in my observation in this post. - This is an ARM box so there should be no BIOS. - Apparently serial console is working. I need to recall what key sequence that might work when the secure boot is implemented.by bodhi - Debian
Martin, > no i didn't flash anything. Then blparam is the correct command to use. > /tmp # blparam > current_envs.txt > -sh: blparam: not found > /tmp # ./fw_printenv > current_envs.txt > Cannot read bad block mark: Invalid argument > /tmp # ./fw_printenv > Cannot read bad block mark: Invalid argument > The above erorrs aby bodhi - uBoot