bodhi, just got some time to play with my dockstar again. I have installed the Linux-4.15.2-kirkwood-tld-1 kernel image and what should I say it is working! :) U-Boot 2017.07-tld-1 (Oct 24 2017 - 22:32:36 -0700) Seagate FreeAgent DockStar gcc (Debian 6.3.0-18) 6.3.0 20170516 GNU ld (GNU Binutils for Debian) 2.28 Hit any key to stop autoboot: 0 starting USB... USB0: USB EHCIby Tom74 - Debian
Eureka! Success! :) :) :=) Thank you for your help bodhi. U-Boot 2017.07-tld-1 (Oct 24 2017 - 22:32:36 -0700) Seagate FreeAgent DockStar gcc (Debian 6.3.0-18) 6.3.0 20170516 GNU ld (GNU Binutils for Debian) 2.28 Hit any key to stop autoboot: 0 starting USB... USB0: USB EHCI 1.00 scanning bus 0 for devices... 4 USB Device(s) found scanning usb for storage devices... Useby Tom74 - Debian
root@debian9:/tmp# fw_printenv bootcmd_exec=run load_uimage; if run load_initrd; then if run load_dtb; then bootm $load_uimage_addr $load_initrd_addr $load_dtb_addr; else bootm $load_uimage_addr $load_initrd_addr; fi; else if run load_dtb; then bootm $load_uimage_addr - $load_dtb_addr; else bootm $load_uimage_addr; fi; fi bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_by Tom74 - Debian
I flashed uboot.2017.07 finally once again, so we are sure that this is the actual version. root@debian9:/tmp# tar -xf uboot.2017.07-tld-1.dockstar.bodhi.tar root@debian9:/tmp# flash_erase /dev/mtd0 0 4 Erasing 128 Kibyte @ 7f5eef5c00000064 -- 4 % complete root@debian9:/tmp# nandwrite /dev/mtd0 uboot.2017.07-tld-1.dockstar.mtd0.kwb Writing data to block 0 at offset 0x0 Writing databy Tom74 - Debian
Hello bodhi, Here is my session/log for flashing u-boot: Can you please have a look if I can do a reboot or maybe I need to adjust something more? root@debian9:~# cat /etc/fw_env.config # MTD device name Device offset Env. size Flash sector size Number of sectors /dev/mtd0 0xc0000 0x20000 0x20000 root@debian9:~# root@debian9:~# cat /proc/mtd dev: sizby Tom74 - Debian
Ok. I will try it during the weekend. And thanks that you will have a look at the procedure and will double check it for me. But I think I will use the 4.10.9-kirkwood-tld-1 kernel because I know it is working with my dockstar at the moment. Right now I don't have a serial console for further debugging. I will install it later when I have more free time. QuoteNo. You should restby Tom74 - Debian
Hello bodhi, I have now a working system with Debian 9 and the 4.10.9-kirkwood-tld-1 kernel. What about flashing the new u-boot? Do I have to look for something special? These are my bad blocks in mtd0: root@debian9:~# dmesg | grep -i 'bad' [ 5.831470] Scanning device for bad blocks [ 5.845415] Bad eraseblock 127 at 0x000000fe0000 [ 5.887606] Bad eraseblock 61by Tom74 - Debian
At the moment I don't have the time to look for the root cause of failure. So I did an "apt-get dist-upgrade" on my installation. And now what should I say samba is working. I think some important libraries didn't got installed with a simple "apt-get update".by Tom74 - Debian
[ 0.160945] : /ocp@f1000000/ethernet-controller@72000/ethernet0-port@0: local-mac-address is not set Is this info critical?by Tom74 - Debian
Could this be an issue? With start of using kernel Linux-4.11.3-kirkwood-tld-1 u-boot>> boot boot (Re)start USB... USB: Register 10011 NbrPorts 1 USB EHCI 1.00 scanning bus for devices... 4 USB Device(s) found scanning bus for storage devices... 1 Storage Device(s) found Loading file "/rescueme" from usb device 0:1 (usbda1) ** File not found /rescueme reaby Tom74 - Debian
Bodhi, is it possible that you built me a new rootfs (4.12.1 or maybe later) with the DTB embedded for my dockstar and netconsole enabled (for debugging)? /etc/initramfs-tools/modules setup to: netconsole netconsole=6666@192.168.0.016/eth0,6666@192.168.0.1/ This would help me a lot to do further investigations. Too bad that I can't built it on my own because my system is notby Tom74 - Debian
Ok. The usb thumb drive I used for the testing above is an older Corsair Voyager GT 16GB in exchange of the sandisk cruzer fit below. My old Debian Squeeze on DockStar is installed on an 4GB Philips thumb drive and it worked well all the years without any major issues. For the main test/upgrade attempt of my old system I am using 2 new sandisk cruzer fit thumb drives with 16GB of RAM.by Tom74 - Debian
Yes bodhi , I have exact the same segfault issue with samba as you mentioned above. I used my other test thumb drive with your older 4.4.0 rootfs and 4.4.x kernel updated to debian stretch on my dockstar. I have also an additional issue in this setup compiling some program sources 'cmake' also quits with an segfault. -Tomby Tom74 - Debian
That's weird... Now I used another USB thumb drive. usb_set_bootargs=setenv bootargs console=$console root=LABEL=rootfs rootdelay=$usb_rootdelay $mtdparts $usb_custom_params Environment size: 2815/131068 bytes u-boot>> boot boot (Re)start USB... USB: Register 10011 NbrPorts 1 USB EHCI 1.00 scanning bus for devices... 4 USB Device(s) found scanning bus for stoby Tom74 - Debian
I have modified my working Debian-4.4.0-kirkwood-tld-1 installation with the netconsole options to see the kernel messages. U-Boot 2011.12 (Feb 12 2012 - 21:33:07) Seagate FreeAgent DockStar arm-none-linux-gnueabi-gcc (Sourcery G++ Lite 2009q3-67) 4.4.1 GNU ld (Sourcery G++ Lite 2009q3-67) 2.19.51.20090709 Hit any key to stop autoboot: 10 u-boot>> setenv usb_set_bootargs &by Tom74 - Debian
1. fstab is correct 2. bootargs are set but still kernel will not boot. Additional question: I am trying to setup netconsole to troubleshoot Debian kernel booting like mentioned in this thread Use netconsole to troubleshoot Debian kernel booting My problem now is I can't generate new initramfs image for the dockstar written to the usb stick. The command wants to update the initramfsby Tom74 - Debian
Hello, I am trying to boot Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi on my Dockstar without success. I did extract Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi.tar.bz2 to a blank usb drive formatted as ext3 with 1 partition. I have generated the uImage with DTB for the Dockstar embedded inside. The kernel starts booting and then the dockstar stucks. The LED lights solid amber. Environment vby Tom74 - Debian
Strange.... The Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi is also not working. Same behavior as before with the other kernel. Maybe still an incorrect environment var? arcNumber=2097 baudrate=115200 bootcmd=usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run rescue_bootcmd; run pogo_bootcmd; reset bootcmd_pogo=run bootcmd_rescue bootcmd_rescue=runby Tom74 - Debian
Now I have set the label as told to rootfs correctly. root@debian:~# e2label /dev/sdb1 rootfs root@debian:~# But still I have no luck. :( The kernel failed to run. The LED color is still amber. Yes, I don't have a serial console with a physical cable attached. At the moment I can only use the netconsole as mentioned in the other thread. Any chance to get it work? :) Tomby Tom74 - Debian
Hello bodhi, just found the time to post the requested information. Please note: At the moment I only can use a Debian 9.0 (Stretch) Linux system in virtual machine (VMWare). The e2label command only works as superuser/root and shows no entry. The used usb pen drive is mounted as /media/tom/7b3f7f98-dc8e-47a4-8857-3ac9976121a8 here in Debian and not as /media/sdb1 tom@debian:/$ sudoby Tom74 - Debian
bodhi, sorry for the typo before... I have seen it right now... Files look good in /boot -rw-r--r-- 1 root root 107471 Apr 25 2012 config-3.3.3-dockstar-shyd -rw-r--r-- 1 root root 1672696 Apr 25 2012 vmlinuz-3.3.3-dockstar-shyd -rw-r--r-- 1 root root 1225355 Apr 25 2012 System.map-3.3.3-dockstar-shyd -rw-r--r-- 1 root root 6637098 Mai 19 2012 initrd.img-3.3.3-dockstar-by Tom74 - Debian