Network problem solved. I've overseen, that eth0 was renamed to enp1s0. [ 10.634048] r8169 0000:01:00.0 enp1s0: renamed from eth0 So I modified /etc/network/interfaces and everything's ok now... But the other question(s) - can I flash new U-boot from serial console? Do I need it actually? Should I care about envs bad CRC or bad blocks?by mari8b - uBoot
bodhi Wrote: ------------------------------------------------------- > Since you have serial console, you can wait until > my next kernel release (4.18.x) to have this > capability. But let me know if you need it sooner, > I'll recompile the new NSA310 DTB for you. So long I'm able to boot new Debian (with new kernel) with my current U-boot, I don't need it noby mari8b - uBoot
I prepared me an USB drive with Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi.tar.bz2 following this instructions. Now I can boot Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi.tar.bz2 (uImage and uinitrd read from USB, the rest read from HDD), but mtd0 partition is read only. How can I mount it writeable? U-Boot 2013.07 (Sep 20 2013 - 15:45:03) ZyXEL NSA310 1-Bay Power Media Server SoC: Kby mari8b - uBoot
Thank you for your support, but it doesn't help... I give up. I have another NAS - Zyxel NSA310. I would like to install Debian onto this device. Would you help me please? I make another thread...by mari8b - uBoot
bodhi Wrote: > My guess is DaveP flashed (using dd): > > - SPL image to Stage-1 Bootloader > - new u-boot image to U-Boot > - new u-boot env image to U-Boot environment > > But that is only an educated guess. That's what I > would do if I have serial console and not afraid > of bricking the box, and have cloned the HDD to > another HDD as backup.by mari8b - uBoot
I think, I'm starting to understand... There's no NAND flash on the Iomega Home Media CE (HMNHDCE). Everything (including U-boot) is written on the HDD. So if I understand it right, there's no need for MTD partitions support... Description of the first 32MB of the HDD: start/sector size content 0 512 Legacy MBR 1 1536 GPT Partition table 34 8736 Stage-1 Bootby mari8b - uBoot
I have an empty HDD, so I don't care about touching my current HDD rootfs, I don't need to boot from USB now, but if it's necessary, I would do it. I have read many threads, but didn't find instructions to boot the Iomega HMNHDCE another way than the first 32MB. Here is described, what is stored in the first 32MB of the HDDby mari8b - uBoot
bodhi Wrote: ------------------------------------------------------- > ... > Time to try booting with > Debian-4.4.54-oxnas-tld-1-rootfs-bodhi.tar.bz2, as > I mentioned... But I think, that booting another kernel is not possible without new U-boot... On my device are the 'uImage' (kernel) and 'initrd' image written in the first 32MB on the HDD. These newerby mari8b - uBoot
Nothing has changed - no MTD partitions... setenv bootargs 'root=/dev/sda1 console=ttyS0,115200 mtdparts=41000000.nand:14m(boot),-(data)' PLX>>printenv bootcmd=run select0 load1 load_rd1 boot || run lightled select0 load2 load_rd2 extinguishled boot || lightled bootdelay=3 baudrate=115200 ethaddr=00:30:e0:00:00:01 ipaddr=172.31.0.128 serverip=172.31.0.100 autoload=nby mari8b - uBoot
Hi bodhi, thank you very much for your support, but no MTD partitions was created... Now it looks like this: 1. root@debian:~# cat /proc/mtd dev: size erasesize name 2. PLX>>printenv bootcmd=run select0 load1 load_rd1 boot || run lightled select0 load2 load_rd2 extinguishled boot || lightled bootdelay=3 baudrate=115200 ethaddr=00:30:e0:00:00:01 ipaddr=172.31.0.128 seby mari8b - uBoot
1. cat /proc/mtd (none MTD partitions) root@debian:~# cat /proc/mtd dev: size erasesize name 2. printenv (is it what you need?) PLX>>printenv bootcmd=run select0 load1 load_rd1 boot || run lightled select0 load2 load_rd2 extinguishled boot || lightled bootdelay=3 baudrate=115200 ethaddr=00:30:e0:00:00:01 ipaddr=172.31.0.128 serverip=172.31.0.100 autoload=n netmask=255by mari8b - uBoot