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
tilator, > RTC works fine after rebooting this 4.1.16 kernel, > but powerdown does not power it properly down and > after unplugging there must be some bits remaining > somewhere preventing RTC to work. I suppose it > would need some kind of RTC or I2C driver reset > while booting. How difficult this might be to do? I think you would need to run stock to find out theby bodhi - Debian
tilator, I'm convinced that the new Ext4 module in kernel 4.4 has a serious problem with the old Oxnas rootfs. And it might be because of something in the kernel 4.4 Oxnas configuration that it does not like now (but was OK with before). Booting back to the old kernel 4.1 on the same rootfs is fine without any problem (I tried both Ext3 and Ext4 rootfs). It's taking too much of mby bodhi - Debian
Hi Reto, I'm not using Raid so I'm not the best person to answer it. You can create a new Debian topic and I'm sure people will respond. However, if you are using Raid, you might want to keep your rootfs on USB (things are going to be much simpler).by bodhi - uBoot
tilator, > B.T.W Original kernel source has different SATA > settings. SATA0 and SATA1 has different addresses > in original sorce, but this kernel FDT seems to > have only one address and two ports assigned to > it. Might this be a problem? You are using a different DTS (not Pogo Pro) so I'm not sure. However, if that was a change to go with your current sata_oxnasby bodhi - Debian
Reto Wrote: ------------------------------------------------------- > Yes I have. So I have to live with an USB memory > key sticking out of the box for now? No. You can migrate (copy) the rootfs to your HDD and then adjust u-boot envs to boot from the HDD.by bodhi - uBoot
tilator, I suspect that the Ext4 driver might be faulty. [ 16.968752] EXT4-fs (sda1): mounting ext3 file system using the ext4 subsystem [ 17.022627] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) done. Begin: Running /scripts/local-bottom ... done. Begin: Running /scripts/init-bottom ... done. INIT: version 2.88 booting [ 17.579955] oxnas-gmac 4040000by bodhi - Debian
Hi tilator, I need this file and the associated patch: https://dev.openwrt.org/browser/trunk/target/linux/oxnas/files/drivers/net/ethernet/stmicro/stmmac/dwmac-oxnas.c?order=name https://dev.openwrt.org/browser/trunk/target/linux/oxnas/patches-4.4/700-oxnas-dwmac.patch -- NVM, I got them downloaded.by bodhi - Debian
Reto Wrote: ------------------------------------------------------- > Ok, so which guide should I follow to flash the > kernel? You already have the kernel running on USB rootfs: http://forum.doozan.com/read.php?3,25120,25698#msg-25698by bodhi - uBoot
512MB on ext3 rootfs.by bodhi - Debian
tilator, > How about root device with that kernel? RW or RO? It is RW. The USB rootfs was mounted successfully. You should check errors on your SATA rootfs. As I mentioned, I think too many kernel panics probably corrupted your FS (especially your SATA disk was already up during kernel panic). My rootfs was corrupted a few times. But I use a small USB rootfs for testing so I just restby bodhi - Debian
Hi pbg4, > have you downloaded the NSA325 kernel sources?, > it might be worth to look if > zyxel has implemented something like a /proc/hwmon > device, this was the case > with NSA320 which has the least capable simple > holtek mcu, but that was sufficient > to implement nsa3xx-hwmon new, > > but because zyxel used i2cget commands to read out > the vaby bodhi - Debian