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
sebr, I think the new hwmon module that was patched for NSA320 might work for NSA310. I'll let pbg4 explain further whether it is possible.by bodhi - Debian
sebr, I've splitted your topic into its own thread: http://forum.doozan.com/read.php?2,25783,25797#msg-25797by bodhi - Debian
Reto, Let's not waste time pursuing this. Since you already have serial console, you can set/save envs as you need. And you can boot the latest kernel with stock u-boot! When I have time to revisit this for building new u-boot, we'll do more experiment.by bodhi - uBoot
Reto, Download the attach file. Extract it and execute: ./blparam Please post the output here. Note that this binary can be used to set env too, but the resulting output will be a little bit scary! let's see if works listing the envs first (don't try to test it).by bodhi - uBoot
sebr Wrote: ------------------------------------------------------- > I just set up a NSA310 (not "s") with the latest > jessie rootfs, kernel 4.4 and latest uboot. So far > I got everything working like LEDs, buttons etc. > But how can I control the fan speed? It is always > running at max. rpm. See this thread: http://forum.doozan.com/read.php?2,24655,25760#msby bodhi - Debian
Argrr! I got a different kernel panic now. I guess it's time to dig into the OpenWrt patch.by bodhi - Debian
Thanks damacc, That's ok. I'll dig out my old blparam binary to see if still work the same way. I was just being careful and wanted to use the one from this box. But I think it's very likely the same.by bodhi - Debian
tilator Wrote: ------------------------------------------------------- > I suppose the problem might be this: > > OX820 processor can only boot from sata if there > are some special bytes in start of the disk. > > The bytes are set using this script: > > > perl <<EOF | dd of="$disk" bs=512 > print "\x00" x 0x1a4; >by bodhi - Debian
I'm at 2015.10 for u-boot: http://forum.doozan.com/read.php?3,16017 But I don't think u-boot is related at all to your problem with RO rootfs. Most likely the rootfs fs was set to RO due to the kernel booting problem. I'm making a clean build. If it boots successful, I'll let you know.by bodhi - Debian
tilator Wrote: ------------------------------------------------------- > > It does not look like they have 4.4 yet. > Currently > > they are at 4.0. > > > > > https://dev.openwrt.org/browser/trunk/target/linux > > > /oxnas?rev=45711&order=name > > How about this: > > https://dev.openwrt.org/browser/trunk/target/linux > /oby bodhi - Debian
tilator, > B.T.W root partition is ext4, but is there some > recognition problem since it says it's ext3? The > trouble has to be there. > > I did try GPT and MSDOS partition tables. Both > freeze here with readonly root file system. No, I think it is not related. Usually if your rootfs fs has error, then it will become read-only. Try taking it to another box ifby bodhi - Debian
sambul14, > I don't believe that you were root while > extracting the rootfs. I could download Arch > rootfs and see for myself :). But why don't you > try again? It would be helpful to your sanity to > go through the exercise exactly as the instruction > stated (dont' do something that you think is > equivalent, this is where mistakes are made mostby bodhi - uBoot
bodhi Wrote: ------------------------------------------------------- > tilator, > > Ah, I did not know openWRT has realeased kernel > 4.4. That's a really good source, I should go look > at their patch. > > I've only published up to the 4.1 patch in this > thread. I'm still working on patch 4.4. It does not look like they have 4.4 yet. Currentby bodhi - Debian
Thanks pbg4, Perhaps the latest patch will be better. I've tried the NSA325 with the previous patch and it did not work, I think it's due to a different Holtek MCU (i.e. different magic number).by bodhi - Debian
bodhi Wrote: ------------------------------------------------------- > Sorry I'm not sure I understood. > > I'm interested in what make the boot that has no > kernel panic successful running until 3.218618 > seconds: > > > ## Booting kernel from Legacy Image at 60500000 > ... > Image Name: Linux-4.4.0 > Image Type: ARM Linux Kernby bodhi - Debian
The 2nd case is the boot when kernel panic occured at 4.15 seconds: [ 4.158003] Internal error: Oops: 17 [#1] SMP ARM [ 4.162677] Modules linked in: [ 4.165711] CPU: 0 PID: 1 Comm: init Not tainted 4.4.0 #5 [ 4.171077] Hardware name: PLXTECH NAS782X SoC (Flattened Device Tree) [ 4.177566] task: cf844000 ti: cf848000 task.ti: cf848000 [ 4.182940] PC is at v6wbi_flush_usby bodhi - Debian
Sorry I'm not sure I understood. I'm interested in what make the boot that has no kernel panic successful running until 3.218618 seconds: ## Booting kernel from Legacy Image at 60500000 ... Image Name: Linux-4.4.0 Image Type: ARM Linux Kernel Image (uncompressed) <snip> [ 3.218618] Freeing unused kernel memory: 196K (c06db000 - c070c000) Was it a colby bodhi - Debian