Show all posts by user
Bootloader tips and tricks
Page 1 of 2 Pages: 12
Results 1 — 30 of 37
Re: LEDE on a dockstar device with now openwrt - Question - 6 years ago
I set these variables (ethaddr already set) on my dockstar: setenv mtdids=nand0=orion_nand setenv console 'console=ttyS0,115200' setenv mtdparts mtdparts=orion_nand:0x0xe0000(uboot),0x100000(uboot_env),0x0x200000(second_stage_uboot),0x0xfe00000(ubi) setenv bootargs_lede '' setenv bootcmd 'run bootargs_lede; ubi part ubi; ubi read 0x800000 kernel; bootm 0x800000by edinger - Rescue System
Re: LEDE on a dockstar device with now openwrt - Question - 6 years ago
Hi, is it possible to start the LEDE rescue system (for installing or upgrading LEDE) from USB instead of TFTP when using Bodhi's current uboot? I have working netconsole, but no installed TFTP server. thanks, Dieterby edinger - Rescue System
Re: Question about 2017.07 U-Boot Kirkwood for Dockstar - 6 years ago
Merry Christmas to you all :)by edinger - uBoot
Re: Question about 2017.07 U-Boot Kirkwood for Dockstar - 6 years ago
Thanks a lot. That worked for me also :)by edinger - uBoot
Re: Question about 2017.07 U-Boot Kirkwood for Dockstar - 6 years ago
sorry. I have only netconsole and that output I already posted. Bute maybe strace will help: root@nas:~# strace fw_setenv ethaddr 00:10:75:1A:DD:17 execve("/usr/bin/fw_setenv", ["fw_setenv", "ethaddr", "00:10:75:1A:DD:17"], [/* 14 vars */]) = 0 brk(0) = 0x8a1000 uname({sys="Linux", node="nas", ..by edinger - uBoot
Re: Question about 2017.07 U-Boot Kirkwood for Dockstar - 6 years ago
Ok. Then let's focus on changing ethaddr from within debian. I think this is the latest dtb: root@nas:~# ll /boot/dts/*dock* -rw-r--r-- 1 root root 10404 Nov 24 06:46 /boot/dts/kirkwood-dockstar.dtb root@nas:~# and as console output says it will be used: loading DTB /boot/dts/kirkwood-dockstar.dtb ... And I cannot change it: root@nas:~# fw_setenv ethaddr 00:10:75:1A:DD:17 Can�by edinger - uBoot
Re: Question about 2017.07 U-Boot Kirkwood for Dockstar - 6 years ago
I have a second dockstar and updated uboot from 2011.12 to 2017.07-tld-1. Same error when I try fw_setenv ethaddr. When I tried to set ethaddr directly in uboot (netcat) I got a strange output DockStar> setenv ethaddr 00:10:75:1A:D9:23 75s:et1eAnv: eDt9ha:dd23 r 00:10:DockStar> After poweroff/on i tried it again and it stuck after the last command - no feedback from uboot. Bootingby edinger - uBoot
Re: Question about 2017.07 U-Boot Kirkwood for Dockstar - 6 years ago
Hi bodhi, sorry, that I missed this step. I worked through your description and did step by step again: unpacking, installing, unpacking dts, building uImage, uInitrd. Now it uses the currents dts, but still the error occurs. root@nas:~# fw_setenv ethaddr 00:10:75:1A:DD:17 Can't overwrite "ethaddr" root@nas:~# ll /boot/dts/*dock* -rw-r--r-- 1 root root 10404 Nov 24 06:46by edinger - uBoot
Re: Question about 2017.07 U-Boot Kirkwood for Dockstar - 6 years ago
root@nas:~# dpkg -l | grep -i linux-image ii linux-image-3.17.0-kirkwood-tld-1 1 armel Linux kernel, version 3.17.0-kirkwood-tld-1 ii linux-image-4.14.1-kirkwood-tld-1 1.0 armel Linux kernel binary image for version 4.14.1-kirkwood-tld-1 root@nas:~# I installed your rootfs Debian-4.12.1-kirkwood-tldby edinger - uBoot
Re: Question about 2017.07 U-Boot Kirkwood for Dockstar - 6 years ago
Ok, I will proceed with this and keep you informed. Here the description differs. There is no 4a or 4b, just4 and I skipped it. 4. 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). Edit: I created uInitrd and uImage by 4a method without changinby edinger - uBoot
Re: Question about 2017.07 U-Boot Kirkwood for Dockstar - 6 years ago
I unpacked the dts files, build uImage with the following commands (as described in Step 4) again and rebooted. Same problem. Should I build it without dts file? It was unclear how, because when I skip step 4 I have no uImage file. Or do I simply have to skip the cat dts/... command? cp -a ~/zImage-4.14.1-kirkwood-tld-1 zImage.fdt cat dts/kirkwood-dockstar.dtb >> zImage.fdt mkimageby edinger - uBoot
Re: Question about 2017.07 U-Boot Kirkwood for Dockstar - 6 years ago
Ok, thanks. Here ist the requested output: =~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2017.12.21 19:17:45 =~=~=~=~=~=~=~=~=~=~=~= root@nas:~# dmesg [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 4.14.1-kirkwood-tld-1 (root@tldDebian) (gcc version 6.3.0 20170516 (Debian 6.3.0-18)) #1 PREEMPT Wed Nov 22 23:38:14 PST 2017 [ 0.000000] CPU: Feroceon 88FR131 [56251311]by edinger - uBoot
Re: Question about 2017.07 U-Boot Kirkwood for Dockstar - 6 years ago
reboot worked, but i get same error when setting ethaddr after booting into debian. I also tried with /boot/uEnv.txt. No effect. Then with update to newest kernel: root@nas:~# uname -a Linux nas 4.14.1-kirkwood-tld-1 #1 PREEMPT Wed Nov 22 23:38:14 PST 2017 armv5tel GNU/Linux root@nas:~# cat /boot/uEnv.txt ethaddr=00:10:75:1A:DD:17 dtb_file= ipaddr=192.168.178.107 serverip=192.168.178by edinger - uBoot
Question about 2017.07 U-Boot Kirkwood for Dockstar - 6 years ago
I have a dockstar and had an older version of your uboot - I assume from 2011. I installed this version. All steps worked including the writing of the environment except setting ethaddr root@nas:~/tmp# fw_setenv ethaddr '00:10:75:1A:DD:17' Can't overwrite "ethaddr" What can I do? Is it possible to set it with the /boot/uEnv.txt?by edinger - uBoot
Re: Automated Debian Installer for Zyxel nsa310, 320 and 325 - 9 years ago
Thanks for your work. It is running now on my dockstar! 1. I installed Jeff's uboot from here. 2. I unpacked your package in a single ext3 partition on my dockstar. 3. I took bodhi's 4.2 kernel from here , extracted the kernel files manually and used method 4.b. Works like a charm :).by edinger - Debian
Re: Use netconsole to troubleshoot uBoot without a serial cable - 9 years ago
When I start nc in foreground I can see the boot process of my dockstar until the kernel gets loaded - fine. But when I start nc in background and foreground in a terminal window as described I cannot interact. I'm using Ubuntu 14.04. Any idea?by edinger - uBoot
Re: Rescue V2.8.2 : many enhancements + full kernel support for GoFlexNet/Home, Zyxel NSA3x0 and many others - 9 years ago
Does the Rescue system work on NSA325V2?by edinger - Rescue System
Re: Automated Debian Installer for Zyxel nsa310, 320 and 325 - 9 years ago
After repairing the envs for the new u-boot as proposed here I installed your package manually in one ext3-partition and can boot it. Great! Now I can experiment with OMV. Thanks for your work!by edinger - Debian
Re: NSA 325 V2 Debian Is Possible! - 9 years ago
Thanks a lot. It works now. I wrote your environment-variables again after booting into debian + adjusting mdtpart and hwaddr values and renamed the uEnv.txt file. What do I have to change now to run a usb stick with 2 partitions (boot and rootfs) - possibly rootfs with ext4?by edinger - Debian
Re: NSA 325 V2 Debian Is Possible! - 9 years ago
Hi, it gets better...but complained about wrong machid, so I changed these values directly in uEnv.txt. I assume uEnv.txt will be read during boot, so I changed some values: root@ubuntu-dell:/media/dieter# diff /media/dieter/rootfs/boot/uEnv.txt uboot.2014.07-tld-2.environment 1,2c1,2 < arcNumber=4495 < machid= --- > arcNumber=2097 > machid=0x831 Now at least it finds kerneby edinger - Debian
Re: NSA 325 V2 Debian Is Possible! - 9 years ago
Here is the log. I created a new usb stick with 3.18.5.by edinger - Debian
Re: NSA 325 V2 Debian Is Possible! - 9 years ago
Can you tell me what's wrong? This is my usb with ext2 boot and ext4 rootfs which worked under the old mtd0. I plugged it into usb 1. The commands are identical to the one from bobafetthotmail except that I used them from u-boot with setenv instead of fw_setenv. root@ubuntu-dell:/home/dieter# fdisk -l /dev/sde Platte /dev/sde: 4184 MByte, 4184342528 Byte 129 Köpfe, 62 Sektoren/Spuby edinger - Debian
Re: NSA 325 V2 Debian Is Possible! - 9 years ago
Hi bobafetthotmail, hi bodhi @bobafetthotmail: it didn't work. I attached log on your post @bodhi: how can I restore old mtd0 when I cannot boot into any system (stock or linux). I tried to create one single ext3 usb stick with 8GB, but it didn't boot either. Regards, Dieterby edinger - Debian
Re: Automated Debian Installer for Zyxel nsa310, 320 and 325 - 9 years ago
Hi, I tried to install your package with new U-Boot as descibed here!, but no success - see attached log. Kind regards, Dieterby edinger - Debian
Re: NSA 325 V2 Debian Is Possible! - 9 years ago
bobafetthotmail Wrote: ------------------------------------------------------- > > With firmware 4.80 they killed the watchdog with > their own u-boot, then you can use my installer > scripts and debian package from here that sets > multiboot from usb, if no usb system is found it > boots its own firmware > http://forum.doozan.com/read.php?2,22432 > > mightby edinger - Debian
Re: 2014.07 U-Boot Kirkwood - GoFlexNet, GoFlexHome, PogoE02, Dockstar, iConnect, NetgearStora, PogoV4/Mobile, Sheevaplug, NSA325, NSA320 - 9 years ago
Hi bodhi, reboot worked, but u-boot cannot find kernel. The usb stick has 2 partitions sda1 (ext2 boot) and sda2 (ext4 root) So your default configuration does not work. (Re)start USB...^M USB0: USB EHCI 1.00^M scanning bus 0 for devices... 4 USB Device(s) found^M scanning usb for storage devices... 2 Storage Device(s) found^M ** File not found /boot/uImage **^M ** File notby edinger - uBoot
Re: 2014.07 U-Boot Kirkwood - GoFlexNet, GoFlexHome, PogoE02, Dockstar, iConnect, NetgearStora, PogoV4/Mobile, Sheevaplug, NSA325, NSA320 - 9 years ago
Hi bodhi, I have a nsa325v2. I had changed the /etc/fw_env.config to get it readable as described here: https://micha.stoecker.me/p/X9M4 I followed your description except the fw_config. You write in section B to /dev/mtd0, but the uboot_env resides in /dev/mtd1! Is that correct? root@debian:/mnt/sdc1/uboot# cat /proc/mtd dev: size erasesize name mtd0: 00100000 00020000 "uboby edinger - uBoot
Re: NSA 325 V2 Debian Is Possible! - 9 years ago
bodhi Wrote: ------------------------------------------------------- > edinger, > > The NSA325 and NSA325-V2 are the same box > (differences are only cosmetics). > > It is OK to update to new u-boot. But if booting > back to stock OS from the new U-Boot is important > to you, then you should wait until I have some > time to try that. > > I canby edinger - Debian
Re: NSA 325 V2 Debian Is Possible! - 9 years ago
bodhi Wrote: ------------------------------------------------------- > Try > > setenv bootcmd 'setenv mainlineLinux yes; setenv > arcNumber 4495; saveenv; run bootcmd_linux; setenv > mainlineLinux no; setenv arcNumber 4495; saveenv; > run bootcmd_stock' > boot > > The saveenv above is what I want to avoid, > but if stock u-boot can't handlby edinger - Debian
Re: NSA 325 V2 Debian Is Possible! - 9 years ago
bodhi Wrote: ------------------------------------------------------- > @edinger, > > In serial console, > > setenv bootcmd 'setenv mainlineLinux yes; run > bootcmd_linux; setenv mainlineLinux no; run > bootcmd_stock' > boot > > See if this works. And post the serial boot log > when you boot without the USB. 1. Boot into stock os without uby edinger - Debian
Page 1 of 2 Pages: 12