Quotentpd is sync to the rtc, So.. we do not need rtc driver? Proper or just not stupid date/time is needed to get dhcp working (in my case) I think ht1382 driver is working fine now and we could trust it a little more. If there's no net connection - there's no ntpd working, right? @JohnnyUSA: please fix your rtc clock on 4.2 and we'll se if it was the reasonby osa - Debian
ht1382 was patched recently. Please set new date, set persistent with hwclock and. AFAIR i had some troubles with old rtc driver becouse it was setting year 1930 and dhcp was not able to renew.by osa - Debian
JohnnyUSA Wrote: ------------------------------------------------------- [ 12.478384] rtc rtc0: __rtc_set_alarm: > err=-22 What does hwclock write about stored time? RTC driver was patched and set to 24h mode by defauld Previously i could get year 1931 set and it caused dhcp problems for me Maybe it issue is related? Have you ever set alarm with zyxel software? Our driver do not supportby osa - Debian
I have a 320 box with 2 4tb drives spinning slowly and fixed it by reseting ide from uboot (my kernel/initrd is in nand)by osa - Debian
bobafetthotmail Wrote: ------------------------------------------------------- > Does that erase stock firmware? We have 2 copies of kernel/rootfs so it detects which was used to boot and overwrite second copy This is limitation of OMV. Did somebody filled such bug or feature request?by osa - Debian
Sorry It should be regs.hour = bin2bcd(tm->tm_hour) | HT1382_HOUR_1224; I copied it from my patch. I called it HT1328_24H_BIT because this bit sets 24h mode but HT1382_HOUR_1224 is commented clearly. Also, please test on your box ( it will always use 24h mode for simplicity and compatibility with zyxel's driver)by osa - Debian
I skipped GPT limit by putting kernel and initram into NAND if disk is > 2TB I remember i was able to create lvm by hand and was able to use it in OMVby osa - Debian
Hi bobafetthotmail Please review my scripts (based on arch's) It supports GPT, raids and nand installer https://www.dropbox.com/sh/w5zpp0utb88a1jt/AACkxs_PqH2IZdzvW4MSxt83a?dl=0&s=soby osa - Debian
@Bohdi: do you have source code for 310s/320/320s/325/325v2 ? I think they all have fancy phy_init like this #if defined(CONFIG_ZYXEL_NSA325) /* Set LED[2] pin is tristate; for communicating with MCU */ mvEthPhyRegWrite(mvBoardPhyAddrGet(ethPortNum),22,0x3); mvEthPhyRegRead(mvBoardPhyAddrGet(ethPortNum),17,®); reg &= ~(1 << 4); regby osa - Debian
I think Bohdi should write tutorial or something There's my way: - set up dev enviroment or cross compilation - download kernel from kernel.org (ie 4.1.3) - extract kernel - apply bohdi's patch - apply my patch - compile using make-kpkg and fakeroot so i finally get linux-image-4.1.3-tld-1_1.0_armel.deb You can try my build https://www.dropbox.com/s/n6n6b0tgwfei4yv/linux-imaby osa - Debian
Guys, i think i have working patch for 4.1. I'll post it here for testing [ 22.152970] NET: Registered protocol family 10 [ 22.414745] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [....] Configuring network interfaces...Internet Systems Consortium DHCP Client 4.3.1 Copyright 2004-2014 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.oby osa - Debian
> Quoteosa > I have alse "link not ready" fixed with this patch > > > Can I somehow try this with phypeek and phypoke? > Tried with > > phypoke 1 22 3 > > Gives error "illegal address"... Hi! 22 = 0x16 so try phypoke 1 16 3 I have tried on my box phypoke 1 16 3 phypoke 1 16 0 My network works after restart ( patch hacks regby osa - Debian