fido95, > My pogoplug indicator doesn't blink green or red, > with nor without sd card. > Is connecting via serial converter to load uboot > the only solution to connect with my pogoplug ? Yes, connect serial is the only way. Yes those should work. But also read this thread before buying: http://forum.doozan.com/read.php?8,13263by bodhi - uBoot
sLOID, > i tried your workaround but without success. i'll > give your actual u-boot a try Don't flash :) they are not built for the LaCie! do only UART booting see if it works.by bodhi - Debian
sLOID, It is a classical problem with ntpd and ntpdate resource fighting. Sep 4 10:14:56 LaCie daemon.err ntpd[1502]: unable to bind to wildcard address 0.0.0.0 - another process may be running - EXITING Our member restamp did a really good job with his explanation: http://forum.doozan.com/read.php?2,20817,20828#msg-20828 If you were running one of my new u-boot images, then SNTP prby bodhi - Debian
tilator Wrote: ------------------------------------------------------- > I have it all. Do you want it? It is a little old, > though ;) I could have used this long ago :) I don't see the need for this now. Except if we need to find out what it does with the RTC driver m41t00. I think you should try to resolve the shutdown problem first (perhaps it is related to the RTC problemby bodhi - Debian
sLOID, Which rootfs are you running? if you are running my 3.18.5 rootfs then your ntpd should be running. Could you post the whole dmesg output and logread output here or pastebin them. I don't think I can guess the problem without seeing the whole picture. > is > there a way to set the rtc over the > serial-connection after interrupting the boot > sequence ?? Not liby bodhi - Debian
Woow. I did not know we have GPL for this?! is that from Oxnas? do you have the whole GPL package or just a few files?by bodhi - Debian
tilator, > There must be some reset routine somewhere in the > old kernel Apparently so. I agreed, seems like it needs to be more than what being done in the 4.1 driver. Wonder what's in 4.4 or 4.5-rc?by bodhi - Debian
sLOID, Yes dmesg for kernel messages and also use logread to print out Debian messages (this log file is normally in var/log/messages, but we are logging to RAM so logread will print it)..by bodhi - Debian
sLOID Wrote: ------------------------------------------------------- > hi bodhi, > > it's the "LaCie Networkspace 2 lite". I include > the specified name of the dtb-file in the DTS > folder while building the image. > (kirkwood-ns2lite.dtb). Everything went without > errors, so it should be the right one. > > sLOID Now this is a puzzle, it&by bodhi - Debian
steve1987, > 2. I used the latest roots I found, is there any > newer I can use? Unfortunately, no. The latest rootfs is 3.18.5. > fw_setenv reboot 'run preboot_nc' (overwritten > previous value) There is a typo here. fw_setenv preboot 'run preboot_nc' For netconsole, because there are many versions of netcat in different OS, you'll hby bodhi - uBoot
Waynosan, Cool :) > Do I still need to go through part D. Add uEnv.txt > to /boot directory? No need to. Only if you want to play with the envs for some purpose and don't want to mess up the boot envs. BTW, I have a backup blog: bodhi's corner.by bodhi - uBoot
Oh I forgot this about Arch: bootargs also needs modification because there is no uInitrd file. I've updated the above instruction.by bodhi - uBoot
Waynosan, At this point, to boot Debian USB rootfs: Power up, interrupt serial console and: setenv dtb_file /'boot/dts/kirkwood-pogo_e02.dtb' boot And to boot Arch rootfs, setenv set_bootargs 'setenv bootargs console=ttyS0,115200 root=/dev/sda1 rootdelay=10 $mtdparts $custom_params' setenv dtb_file /'boot/dtbs/kirkwood-pogo_e02.dtb' boot See iby bodhi - uBoot
sLOID, This mtd0 will not work with the current /etc/fw_env.config. So definitely fw_printenv/setenv will not work. The above link pointed to u-boot images, so I really can't tell what the correct settings should be. However, we've strayed far from original topic! Getting back to the RTC, what is the exact name of this Lacie DTB?by bodhi - Debian
steve1987, 1. The LED behavior might indicate that the kernel file was not the right one to boot with the current setings of u-boot envs. Which u-boot you have installed? version ? 2. The rootfs 3.18.5 did not yet support the NSA320S kernel. QuoteUpdated 16 April 2015: Kernel 4.0.0-kirkwood-tld-1 package has been uploaded. The following features were added: 1. This FDT kernel nowby bodhi - uBoot
sLOID, > yeah, i did. while playing around i found other > frightened stuff: commands like: > > fw_setenv bootdelay=5 > This should be fw_setenv bootdelay 5 But it is not related to the error below. > end up with: > > Warning: Bad CRC, using default environment > MTD erase error on /dev/mtd0: Invalid argument No worry. This only means that the aby bodhi - Debian
Waynosan, > Sounds like I should make a backup of the > archlinux install that I've done to-date in case > things blow up on me again (figuratively > speaking). Yes, definitely make a backup of: - Listing of u-boot envs - Arch rootfs. > > I'd like to that so I can fall back on Arch if > things go sour. > It is a trivial change in u-bootby bodhi - uBoot
This is the working thread for effort to compiling OPenWrt for Kirkwood boxes.by bodhi - Off-Topic
Hi Waynosan, > I did not flash the default uboot.envs or do any > of the other steps. Is there a reason why didn't you flash the default u-boot envs and stop there? you should flash it so the new u-boot will boot Debian correctly. But warning: after you flashed default u-boot envs image, booting back to Arch will not be possible without changing some envs. > I createdby bodhi - uBoot
sLOID Wrote: ------------------------------------------------------- > hi bodhi, > > yes, it does: > > rtc-mv f1010300.rtc: setting system clock to > 2018-08-30 21:39:56 UTC (1535665196) > > what does it mean ?? The RTC is running, so it meant your hwclock command did not transfer the datetime to clock. It seems the Lacie uses Marvell SoC RTC so rtc-mv worksby bodhi - Debian
tilator , Try it. I think it will work. rtc@68 { compatible = "st,m41t00"; reg = <0x68>;by bodhi - Debian
sLOID Wrote: ------------------------------------------------------- > hi there, > > i'm a big fan of this forum and got a few devices > allready running successfully bodhi's great debian > stuff - thank you for all your work :-) > > my latest project is a broken (hdd - crashed) > lacie networkspace 2 lite devices. i flashed the > mainline u-boot (by bodhi - Debian
bobafetthotmail, > Why the standard env image uses ext2load instead > of ext4load? > I'm a bit curious. (mostly because I want to > modify it to have full boot for both ext2 and ext4 > in my boxes) You can use ext4 load and it will work. I simply missed this when I redefined the envs. In fact, I planned to update the envs to use just "load" and the new u-boby bodhi - uBoot
habibie Wrote: ------------------------------------------------------- > I told some friends about this device and got > interested. So, they asked me several questions > and one of them is if there is any FREE Chinese, > Korean, and/or Japanese channels with TV series > shows available to stream by this device. I have > never used any InternetTV device, so I could not &by bodhi - Off-Topic
craigcoffman Wrote: ------------------------------------------------------- > Bohdi: > > the 3.18 worked like a charm Thanks. Would've > started with the newer tar-fs if I could found it > earlier. > > Thanks for your help. Cool! Glad you found it in the first post. It's down in previous updated section since we are many releases after that.by bodhi - Debian
tilator, The device property needs to be more specific to the hardware. The mt41t00 variation has extra processing in the ds1307 driver (in addition to the general case of a ds1307). i2c-gpio { compatible = "i2c-gpio"; gpios = <0x5 0x9 0x0 0x5 0xa 0x0>; i2c-gpio,delay-us = <0xa>; #address-cells = <0x1>; #size-cells = <0x0>; rtc@68 {by bodhi - Debian
craigcoffman, OK so you want to install from scratch, then it is quite simple. Change the step below to: Wiped the disk flash drive I'm using, created new ext3 filesystem (on my Debian desktop box) on it with the rootfs label extracted 3.18.5 rootfs from Debian-3.18.5-kirkwood-tld-1-rootfs-bodhi.tar.bz2 copied the uEnv_arch_uboot_boot_debian.txt uEnv.txt to the /boot on the nby bodhi - Debian
craigcoffman, Problem: rootfs 3.14 is non-FDT, so the variable fdt_file must be clear so that Arch u-boot will act correctly. IOW, this file should not be in the rootfs. So you need to take out the 2 bold lines below. console=ttyS0,115200 uimage=/boot/uImage initrd=/boot/uInitrd fdt_file=/boot/dts/kirkwood-dockstar.dtb fdt_addr=0x1c00000 uimage_addr=0x800000 initrd_addr=0xby bodhi - Debian
craigcoffman Wrote: ------------------------------------------------------- > Ahh.. just stumbled across the pointer on > migrating from Arch to Debian which points me to > this thread: > http://forum.doozan.com/read.php?3,23727 > > So I need to update uboot basically, correct. No. You don't need to if you don't want to. The linked thread above showed how yby bodhi - Debian
craigcoffman, > "Waiting for root device /dev/sda1" & it hangs. > > I'm guessing that it's either a uboot enviroment > parameter, OR that I simply need to update/change > the uboot install (it does say "Arch Linux" when > uboot starts. Sounds like you have serial console? If so, boot up, interrupt serial console and get the envs lisby bodhi - Debian