> 4. The latest kernel uImage and uInitrd are too > big for stock u-boot because of 4GB limitation. Hi, Seems like there is quite much trouble with this old device. Could it be possible to use known good old U-Boot by simply cutting too big kernel image in two parts and loading them one by one? Or is there some other limitations why old U-Boot and new kernel do not match each otheby tilator - uBoot
Hello, Does anyone still have KD20.zip file available here? Google does not find it any more. WBR: Harriby tilator - Debian
Hello, Nice to hear you are still working on these Oxnas devices. RTC was my problem too before and I did not find any good resolution in it. Would it work if I2C was left in kernel and RTC made as module to ensure I2C was initiated first? B.T.W. Original 2.6 kernel dmesg has RTC first and I2C after it: "rtc-ds1307 0-0068: rtc core: registered m41t00 as rtc0 i2c-gpio i2c-gpio.0: uby tilator - Debian
Peacemaker Wrote: ------------------------------------------------------- > Hey tilator, > as I tried today your files: It's not working :-/ > Is the partition needed in a special format > (fat,ext2,3,4)? and may be you can share your > sources as well? Sorry, my SPL works only with device having 256MB RAM. I see you did try it with KD20 and I suppose there is 128MB Rby tilator - uBoot
Hi, Sata-boot needs actually only two things. First is stage 1 loader written directly to a proper space in sata disk (starting from sector 34 if I remember this right). Stage 1 loader (SPL) must be compiled to search U-Boot and environment from disk file system. Second is some bytes written in start of the disk. Rest is setting U-boot environment correctly. If someone still needs thiby tilator - uBoot
bodhi Wrote: ------------------------------------------------------- > The good news: I am able to run w/o seeing any > kernel panic in memory, or seeing segfault in > samba. Apparently the problem was in the old > kernel config that new kernel code does not like. > Just what I've guessed before, but we got > sidetracked into other directions :) ie. samba > segfaby tilator - Debian
> Samba is still running, but when restarting I > still get a segfault. > > Could you install samba, if it is not installed, > and see if you get the same error. I have Samba running, but I don't have that error. Might it have something to do with Linux version? I have still years old Fedora 12 because that's what original software is based on and I have notby tilator - Debian
bodhi Wrote: ------------------------------------------------------- > Yes that was it. So you applied > /generic/patches-4.4/ too? I did not patch it with generic patches, but I did not (yet) run into any kernel panic either. Is the fault so severe, it prevents booting totally or does it apply only once and while randomly? If faulty is severe enough it must have been taken care ofby tilator - Debian
bodhi Wrote: ------------------------------------------------------- > Did you patch smp_tlb.c ? I noticed that patch is > not in OpenWrt Oxnas patch set. I did not put any other patches but those in OpenWRT. Where is this SMP patch and how does it effect? This? https://dev.openwrt.org/browser/trunk/target/linux/generic/patches-4.4/100-ARM-work-around-CONFIG_CPU_SW_DOMAIN_PAN-breakby tilator - Debian
> NVM. I'm cloning their Git. That's right way to go. Patch kernel only with Oxnas spesific files and patches. Don't use OpenWRT patches at all, because they make some weird things like putting rootfs always to UBI if it is available. If you use the config I put here, you must also turn GPIO button related settings on. They are in input devices under keyboard settings.by tilator - Debian
Here is attached latest working kernel config I used, if you want to see it.by tilator - Debian
bodhi Wrote: ------------------------------------------------------- > tilator, > > > BTW - I got kernel 4.4.3 up and going woth it > too. > > Good news! which patch set did you use? is that > from OpenWRT? The ext4 problem was resolved in > this version? > > I'm going to work on this Oxnas kernel in a week > or so. For the GPIO power off,by tilator - Debian
Hi again, Some progress in this, because - thanks to Daniel Golle - RTC works now fine. Next step here would be making the device power down poperly. This DTS bellow produces the working RTC, but it does not allow the device boot up. It triggers power off while it loads. There is some discussion abot the same behavior with Raspberry PI here: https://www.raspberrypi.org/forums/viewtopic.php?by tilator - Debian
This kernel 4.1.6 pincontrol needs (or at least it seems like) some kind on pullup. How can I do it in userspace?by tilator - Debian
bodhi Wrote: ------------------------------------------------------- > tilator, > > I've just remember this. Which u-boot are you > running? the version I've released has SNTP, but > the RTC clock driver was commented out, since the > Pogo V3 does not have it. I have OpenWrt version 2014.10. B.T.W there is one typo in this version Oxnas 300* patch. Thereby tilator - Debian
> > SYS_CTRL_GPIO_PRIMSEL_CTRL_0, > > SYS_CTRL_GPIO_SECSEL_CTRL_0 and > > SYS_CTRL_GPIO_TERTSEL_CTRL_0 are all not > declared > > anywhere in this kernel source and if I > remember > > correcty they are not used anywhere else but > this > > pincontrol. > > It's rare, but sometime the GPL source does not > match what is runninby tilator - Debian
> However, I've concluded that this rootfs is no > longer good to use (we can't say that if those > invalid inodes will not cause problem in the > future). Sounds like rootfs will be corrupted several times more before file system drivers are OK. My investigation about pincontrol has led here. First again a short cut from the original driver: /* Dedicate theby tilator - Debian
bodhi Wrote: ------------------------------------------------------- > tilator Wrote: > -------------------------------------------------- > ----- > > Can you tell me one more thing. > > > > Compiling u-boot 2014.10 does make u-boot > binary, > > but not SPL. What might I do wrong? > > Nothing wrong. You can build u-boot separately, > whiby tilator - Debian
Reto Wrote: ------------------------------------------------------- > Reto Wrote: > -------------------------------------------------- > ----- > > I am trying to get apache2 webserver running on > > the 4.4 kernel. However without success so far. > > Are there any known issues regarding this? > > For some reason the user www-data was corrupt. > Evenby tilator - Debian
Can you tell me one more thing. Compiling u-boot 2014.10 does make u-boot binary, but not SPL. What might I do wrong?by tilator - Debian
> I think you should try to resolve the shutdown > problem first (perhaps it is related to the RTC > problem). If they were related, the device should find RTC with 4.1 kernel if it was shutted down properly with old kernel and then cold booted in the new one. I expect the old kernel does shut it down properly. B.T.W the shutdown process in official kernel source code is here:by tilator - Debian
I have it all. Do you want it? It is a little old, though ;)by tilator - Debian
bodhi Wrote: ------------------------------------------------------- > 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? Here is what's in original 2.6.* source. Does it souby tilator - Debian
bodhi Wrote: ------------------------------------------------------- > tilator , > > Try it. I think it will work. > > > rtc@68 { > compatible = "st,m41t00"; > reg = <0x68>; > Still exactly same situation. After booting first old 2.6.* kernel and then warm boot to 4.1.6 this works fine. I compiled it as a module.by tilator - Debian
bodhi Wrote: ------------------------------------------------------- > 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). > > compatible = "st,m41t00"; > bodhi, I have had this inby tilator - Debian
> If it does not do any extra stuff > during start up, then it might be in the kernel, It's definitely in kernel. It updates system time from RTC before starting rootfs. > which we might see under /sys/class/rtc/rtc0. What > is the definition of rtc in the Atikio DTS in the > kernel 4.1? i2c-gpio { compatible = "i2c-gpio"; gpios = <0x5 0x9 0x0by tilator - Debian
bodhi Wrote: ------------------------------------------------------- > 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 oby tilator - Debian
Here is latest boot log: ## Booting kernel from Legacy Image at 60500000 ... Image Name: Linux-4.4.0 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 3147328 Bytes = 3 MiB Load Address: 60008000 Entry Point: 60008000 Verifying Checksum ... OK ## Flattened Device Tree blob at 61000000 Booting using the fdt blob at 0x61000000 Loading Kernelby tilator - Debian
bodhi Wrote: ------------------------------------------------------- > tilator, > > I suspect that the Ext4 driver might be faulty. > > What is your rootfs FS type? It's Ext4. I'll try ext3 next. 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 oneby tilator - Debian
What's your swap size and type?by tilator - Debian