Debian on NSA310S?
Posted by pengu
|
Re: Debian on NSA310S? September 12, 2015 03:49AM |
Registered: 9 years ago Posts: 118 |
@bodhi,
cleared the u-boot env settings you gave me on PM and used pengu's ones posted above (since, as i've said, i failed to save my original u-boot envs when i've upgraded to the new u-boot and i don't have them anymore thus, i rely on envs you guys post on this forum).
Also, i made only one partition on the usb stick (rootfs), no more swap or whatever - as you instructed me on PM.
Tried again to boot with fresh ROOTFS (and default kernel-3.18.5) and everything is working fine. I have lan on restart/shutdown.. no problems whatsoever.
Now, i've tried to upgrade the kernel to the last one (kernel-4.2.0) and on restart/shutdown i have no working lan even if the nsa310s dtb is loading on u-boot start.
Also, i get some strange fsck error, error that wasn't present when booting with default rootfs kernel-3.18.5:
My "new" u-boot envs are these: http://pastebin.com/T0e0gsty
Bootlog with new 4.20 -kernel (with no eth link): http://pastebin.com/4YzvGw9a
To install kernel and create uImage/uInitrd i've used the following commands:
Link errors from boot:
The kirkwood-nsa310s.dtb file is loaded at start-up:
LE: Further testing done was with static ip on /etc/network/interfaces. This time i've had eth link and internet access! So, only DHCP doesn't work.
U-boot log:
Ping:
Date is wrong on 4.2.0 kernel boot:
NOTE: I've tried to upgrade directly from 3.18.5 to 4.2.0
NOTE2: I have a backup of 3.18.5 uInitrd, uImage; if i put these two back on /boot and overwrite the 4.2.0 ones, my system works fine (i have ethernet link, no fsck errors.. etc)
NOTE3: Ping didn't work with DHCP on /etc/network/interfaces on 4.2.0 kernel. But DHCP worked fine on 3.18.5 kernel.
Edited 9 time(s). Last edit at 09/12/2015 04:21AM by JohnnyUSA.
cleared the u-boot env settings you gave me on PM and used pengu's ones posted above (since, as i've said, i failed to save my original u-boot envs when i've upgraded to the new u-boot and i don't have them anymore thus, i rely on envs you guys post on this forum).
Also, i made only one partition on the usb stick (rootfs), no more swap or whatever - as you instructed me on PM.
Tried again to boot with fresh ROOTFS (and default kernel-3.18.5) and everything is working fine. I have lan on restart/shutdown.. no problems whatsoever.
Now, i've tried to upgrade the kernel to the last one (kernel-4.2.0) and on restart/shutdown i have no working lan even if the nsa310s dtb is loading on u-boot start.
Also, i get some strange fsck error, error that wasn't present when booting with default rootfs kernel-3.18.5:
Begin: Checking root file system ... fsck from util-linux 2.25.2 fsck: error 2 (No such file or directory) while executing fsck.ext3 for /dev/sda1 fsck exited with status code 8 done. Warning: File system check failed but did not detect errors [ 9.607328] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) done.
My "new" u-boot envs are these: http://pastebin.com/T0e0gsty
Bootlog with new 4.20 -kernel (with no eth link): http://pastebin.com/4YzvGw9a
To install kernel and create uImage/uInitrd i've used the following commands:
tar -xjf linux-4.2.0-kirkwood-tld-1-bodhi.tar.bz2 dpkg -i linux-image-4.2.0-kirkwood-tld-1_1.0_armel.deb mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-4.2.0-kirkwood-tld-1 -d vmlinuz-4.2.0-kirkwood-tld-1 uImage mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs-4.2.0-kirkwood-tld-1 -d initrd.img-4.2.0-kirkwood-tld-1 uInitrd
Link errors from boot:
[ 16.029776] NET: Registered protocol family 10 [ 16.145141] mv643xx_eth: Set the PHY back to auto-negotiation mode [ 16.151461] 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.org/software/dhcp/ Listening on LPF/eth0/5c:f4:ab:df:07:2b Sending on LPF/eth0/5c:f4:ab:df:07:2b Sending on Socket/fallback DHCPREQUEST on eth0 to 255.255.255.255 port 67 Unable to set up timer: unexpected error If you think you have received this message due to a bug rather than a configuration issue please read the section on submitting bugs on either our web page at www.isc.org or in the README file before submitting a bug. These pages explain the proper process and the information we find helpful for debugging.. exiting. Failed to bring up eth0. done. [ ok ] Starting rpcbind daemon.... [FAIL] Starting NFS common utilities: statd idmapd failed! [ ok ] Cleaning up temporary files.... [FAIL] startpar: service(s) returned failure: nfs-common ... failed! INIT: Entering runlevel: 2 [ 17.824301] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 100 Mb/s, full duplex, flow control disabled [ 17.834162] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [info] Using makefile-style concurrent boot in runlevel 2. [....] Starting busybox' syslogd implementation : syslogdStarting /sbin/syslogd... 1205 (syslogd) . ok [ ok ] Starting system message bus: dbus. [FAIL] Starting NFS common utilities: statd idmapd failed! [ ok ] Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon. [warn] Not starting NFS kernel daemon: no exports. ... (warning). [ ok ] Starting NTP server: ntpd. [ ok ] Starting OpenBSD Secure Shell server: sshd. [....] Starting busybox' klogd implementation : klogdStarting /sbin/klogd... 1206 (klogd) . ok [FAIL] startpar: service(s) returned failure: nfs-common ... failed!
The kirkwood-nsa310s.dtb file is loaded at start-up:
USB0: USB EHCI 1.00
scanning bus 0 for devices... 3 USB Device(s) found
scanning usb for storage devices... 1 Storage Device(s) found
13455 bytes read in 215 ms (60.5 KiB/s)
3147200 bytes read in 330 ms (9.1 MiB/s)
7148518 bytes read in 412 ms (16.5 MiB/s)
LE: Further testing done was with static ip on /etc/network/interfaces. This time i've had eth link and internet access! So, only DHCP doesn't work.
U-boot log:
[ 15.670849] mv643xx_eth: Set the PHY back to auto-negotiation mode [ 16.107655] NET: Registered protocol family 10 [ 16.113318] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [....] Configuring network interfaces...Aborted done. [ ok ] Starting rpcbind daemon.... [ 17.447037] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 100 Mb/s, full duplex, flow control disabled [ 17.456826] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [FAIL] Starting NFS common utilities: statd idmapd failed! [ ok ] Cleaning up temporary files.... [FAIL] startpar: service(s) returned failure: nfs-common ... failed! INIT: Entering runlevel: 2 [info] Using makefile-style concurrent boot in runlevel 2. [....] Starting busybox' syslogd implementation : syslogdStarting /sbin/syslogd... 1254 (syslogd) . ok [ ok ] Starting system message bus: dbus. [FAIL] Starting NFS common utilities: statd idmapd failed! [ ok ] Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon. [warn] Not starting NFS kernel daemon: no exports. ... (warning). [ ok ] Starting NTP server: ntpd. [ ok ] Starting OpenBSD Secure Shell server: sshd. [....] Starting busybox' klogd implementation : klogdStarting /sbin/klogd... 1251 (klogd) . ok [FAIL] startpar: service(s) returned failure: nfs-common ... failed!
Ping:
root@debian:~# ping www.google.com PING www.google.com (62.231.75.216) 56(84) bytes of data. 64 bytes from cache.google.com (62.231.75.216): icmp_seq=1 ttl=60 time=4.34 ms 64 bytes from cache.google.com (62.231.75.216): icmp_seq=2 ttl=60 time=4.38 ms ^C --- www.google.com ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1000ms rtt min/avg/max/mdev = 4.347/4.367/4.387/0.020 ms
Date is wrong on 4.2.0 kernel boot:
root@debian:~# date Mon Nov 27 12:15:32 EET 1933but it's fine when i boot with 3.18.5 kernel. Maybe the culprit is this? (from 4.2.0 bootlog with static ip):
[ 11.684817] rtc rtc0: __rtc_set_alarm: err=-22
NOTE: I've tried to upgrade directly from 3.18.5 to 4.2.0
NOTE2: I have a backup of 3.18.5 uInitrd, uImage; if i put these two back on /boot and overwrite the 4.2.0 ones, my system works fine (i have ethernet link, no fsck errors.. etc)
NOTE3: Ping didn't work with DHCP on /etc/network/interfaces on 4.2.0 kernel. But DHCP worked fine on 3.18.5 kernel.
Edited 9 time(s). Last edit at 09/12/2015 04:21AM by JohnnyUSA.
|
Re: Debian on NSA310S? September 12, 2015 04:26AM |
Admin Registered: 13 years ago Posts: 18,997 |
Johnny,
>
> Also, i get some strange fsck error, error that
> wasn't present when booting with default
> rootfs kernel-3.18.5:
>
Don't worry about this warning. This is a change in the way rootfs specified in fstab in later kernel.
/dev/root is no longer valid. But it does not matter, because we have rootfs set in bootargs. So it is only a warning for us to change it in fstab eventually. I plan to do that in future rootfs release. For now it is not a real problem. I'm seeing it too previously. If you do apt-get update, and apt-get upgrade you probably will see the error message changes a little bit (I did). But the warning is still going to be there.
>
> Now, i've tried to upgrade the kernel to the last
> one (kernel-4.2.0) and on restart/shutdown i have
> no working lan even if the nsa310s dtb is loading
> on u-boot start.
It is indeed strange, because I am running the same u-boot and kernel version as you are, too.
The only difference is my rootfs uses static IP, not dynamic IP. What is the timestamp of your kirkwood-nsa310s.dtb ? when you installed kernel 4.2 did you untar the DTB tarball to get the latest DTB?
- Make sure you use latest DTB
- Try changing it to static IP to see if it somehow caused this.
I've scanned your bootlog briefly, and everything looks normal, except the network link behavior. But I will take a closer look.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
>
> Also, i get some strange fsck error, error that
> wasn't present when booting with default
> rootfs kernel-3.18.5:
>
> Begin: Checking root file system ... fsck from > util-linux 2.25.2 fsck: error 2 (No such file or > directory) while executing fsck.ext3 for /dev/sda1 > fsck exited with status code 8 > done. > Warning: File system check failed but did not > detect errors > [ 9.607328] EXT4-fs (sda1): mounted filesystem > with ordered data mode. Opts: (null) > done. >
Don't worry about this warning. This is a change in the way rootfs specified in fstab in later kernel.
/dev/root is no longer valid. But it does not matter, because we have rootfs set in bootargs. So it is only a warning for us to change it in fstab eventually. I plan to do that in future rootfs release. For now it is not a real problem. I'm seeing it too previously. If you do apt-get update, and apt-get upgrade you probably will see the error message changes a little bit (I did). But the warning is still going to be there.
>
> Now, i've tried to upgrade the kernel to the last
> one (kernel-4.2.0) and on restart/shutdown i have
> no working lan even if the nsa310s dtb is loading
> on u-boot start.
It is indeed strange, because I am running the same u-boot and kernel version as you are, too.
root@Nsa310s:~# myinfo Nsa310s 192.168.0.248 Machine model: Zyxel NSA310S Linux version 4.2.0-kirkwood-tld-1 (root@tldDebian) (gcc version 4.9.2 (Debian 4.9.2-10) ) #1 PREEMPT Mon Aug 31 23:12:00 PDT 2015 console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=orion_nand:0x100000(uboot),0x80000(stock_uboot_env),0x80000(key_store),0x80000(info),0xA00000(etc),0xA00000(kernel_1),0x2FC0000(rootfs1),0xA00000(kernel_2),0x2FC0000(rootfs2) uboot_version=U-Boot 2014.07-tld-4 (Aug 17 2015 - 16:10:11)
The only difference is my rootfs uses static IP, not dynamic IP. What is the timestamp of your kirkwood-nsa310s.dtb ? when you installed kernel 4.2 did you untar the DTB tarball to get the latest DTB?
- Make sure you use latest DTB
- Try changing it to static IP to see if it somehow caused this.
I've scanned your bootlog briefly, and everything looks normal, except the network link behavior. But I will take a closer look.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on NSA310S? September 12, 2015 04:29AM |
Admin Registered: 13 years ago Posts: 18,997 |
Johnny,
I see :) so DHCP indeed caused this problem. Let me think about this a bit.
UPDATE 1:
Your rtc is not running. That could cause the DHCP lease problem.
UPDATE 2:
Try a warm reboot
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 09/12/2015 04:33AM by bodhi.
I see :) so DHCP indeed caused this problem. Let me think about this a bit.
UPDATE 1:
[ 11.684817] rtc rtc0: __rtc_set_alarm: err=-22
Your rtc is not running. That could cause the DHCP lease problem.
UPDATE 2:
Try a warm reboot
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 09/12/2015 04:33AM by bodhi.
|
Re: Debian on NSA310S? September 12, 2015 04:36AM |
Admin Registered: 13 years ago Posts: 18,997 |
Johnny,
Boot with static IP, and check the timestamp in the log:
And then reboot, see if the rtc is running.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Boot with static IP, and check the timestamp in the log:
dmesg -T
And then reboot, see if the rtc is running.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on NSA310S? September 12, 2015 04:39AM |
Registered: 9 years ago Posts: 118 |
@bodhi, will do in a sec and i'll edit this post.
EDIT:
I made sure i'm using your latest dtb file from 4.2.0 kernel tar.
On coldboot, dmesg -T output:
dmesg -T output after restart:
So, it's the same timestamp (using static IP). That rtc error went away tho (on coldboot/restart). But still the date is wrong (1933).
NOTE: If i activate DHCP, i don't have link and the year is still wrong (1933).
NOTE2: New bootlog: http://pastebin.com/yyYYf67g
Edited 7 time(s). Last edit at 09/12/2015 05:20AM by JohnnyUSA.
EDIT:
I made sure i'm using your latest dtb file from 4.2.0 kernel tar.
On coldboot, dmesg -T output:
[Mon Nov 27 12:55:59 1933] NET: Registered protocol family 10 [Mon Nov 27 12:55:59 1933] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [Mon Nov 27 12:56:00 1933] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 100 Mb/s, full duplex, flow control disabled [Mon Nov 27 12:56:00 1933] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
dmesg -T output after restart:
[Mon Nov 27 12:59:59 1933] NET: Registered protocol family 10 [Mon Nov 27 12:59:59 1933] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [Mon Nov 27 13:00:00 1933] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 100 Mb/s, full duplex, flow control disabled [Mon Nov 27 13:00:00 1933] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
So, it's the same timestamp (using static IP). That rtc error went away tho (on coldboot/restart). But still the date is wrong (1933).
[ 2.111905] ht1382 0-0068: rtc core: registered ht1382 as rtc0
NOTE: If i activate DHCP, i don't have link and the year is still wrong (1933).
NOTE2: New bootlog: http://pastebin.com/yyYYf67g
Edited 7 time(s). Last edit at 09/12/2015 05:20AM by JohnnyUSA.
|
Re: Debian on NSA310S? September 12, 2015 05:32AM |
Admin Registered: 13 years ago Posts: 18,997 |
JohnnyUSA Wrote:
-------------------------------------------------------
> @bodhi, will do in a sec and i'll edit this post.
>
> EDIT:
>
> I made sure i'm using your latest dtb file from
> 4.2.0 kernel tar.
>
> On coldboot, dmesg -T output:
>
> dmesg -T output after restart:
>
> So, it's the same timestamp (using static IP).
> That rtc error went away tho (on
> coldboot/restart). But still the date is wrong
> (1933).
>
> NOTE: If i activate DHCP, i don't have link and
> the year is still wrong (1933).
> NOTE2: New bootlog: http://pastebin.com/yyYYf67g
You definitely has rtc problem, it does not set to the right date. Do you have ntp running?
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-------------------------------------------------------
> @bodhi, will do in a sec and i'll edit this post.
>
> EDIT:
>
> I made sure i'm using your latest dtb file from
> 4.2.0 kernel tar.
>
> On coldboot, dmesg -T output:
>
> [Mon Nov 27 12:55:59 1933] NET: Registered > protocol family 10 > [Mon Nov 27 12:55:59 1933] IPv6: > ADDRCONF(NETDEV_UP): eth0: link is not ready > [Mon Nov 27 12:56:00 1933] mv643xx_eth_port > mv643xx_eth_port.0 eth0: link up, 100 Mb/s, full > duplex, flow control disabled > [Mon Nov 27 12:56:00 1933] IPv6: > ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready >>
> dmesg -T output after restart:
>
> [Mon Nov 27 12:59:59 1933] NET: Registered > protocol family 10 > [Mon Nov 27 12:59:59 1933] IPv6: > ADDRCONF(NETDEV_UP): eth0: link is not ready > [Mon Nov 27 13:00:00 1933] mv643xx_eth_port > mv643xx_eth_port.0 eth0: link up, 100 Mb/s, full > duplex, flow control disabled > [Mon Nov 27 13:00:00 1933] IPv6: > ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready >>
> So, it's the same timestamp (using static IP).
> That rtc error went away tho (on
> coldboot/restart). But still the date is wrong
> (1933).
>
> [ 2.111905] ht1382 0-0068: rtc core: registered > ht1382 as rtc0 >>
> NOTE: If i activate DHCP, i don't have link and
> the year is still wrong (1933).
> NOTE2: New bootlog: http://pastebin.com/yyYYf67g
You definitely has rtc problem, it does not set to the right date. Do you have ntp running?
ps -deaf | grep -i ntp logread | grep -i ntp
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on NSA310S? September 12, 2015 05:32AM |
Registered: 9 years ago Posts: 118 |
And (again) i feel i'm losing my mind...
tried again what you've said and now, on coldboot i have 1933 year (so wrong date) and on reboot i have the correct date.
only thing i did is uncomment a line in ntp.conf
tried again what you've said and now, on coldboot i have 1933 year (so wrong date) and on reboot i have the correct date.
only thing i did is uncomment a line in ntp.conf
# You do need to talk to an NTP server or two (or three). #server ntp.your-provider.example # pool.ntp.org maps to about 1000 low-stratum NTP servers. Your server will # pick a different set every time it starts up. Please consider joining the # pool: http://www.pool.ntp.org/join.html server 0.debian.pool.ntp.org iburst #server 1.debian.pool.ntp.org iburst #server 2.debian.pool.ntp.org iburst #server 3.debian.pool.ntp.org iburst
|
Re: Debian on NSA310S? September 12, 2015 05:37AM |
Registered: 9 years ago Posts: 118 |
@bodhi,
That's the output on coldboot.
Now it's wrong date even on restart or (warmboot)... it seems so random that it drives me crazy.
Edited 1 time(s). Last edit at 09/12/2015 05:40AM by JohnnyUSA.
root@debian:~# ps -deaf | grep -i ntp root 1518 1512 0 13:36 ttyS0 00:00:00 grep -i ntp root@debian:~# logread | grep -i ntp Nov 27 13:35:47 debian daemon.notice ntpd[1411]: ntpd 4.2.6p5@1.2349-o Fri Apr 10 19:35:06 UTC 2015 (1) Nov 27 13:35:48 debian daemon.notice ntpd[1412]: proto: precision = 1.722 usec Nov 27 13:35:48 debian daemon.err ntpd[1412]: unable to bind to wildcard address 0.0.0.0 - another process may be running - EXITING Nov 27 13:35:55 debian daemon.err ntpdate[1041]: no server suitable for synchronization found Nov 27 13:35:55 debian daemon.err ntpdate[1073]: Can't adjust the time of day: Invalid argument
That's the output on coldboot.
Now it's wrong date even on restart or (warmboot)... it seems so random that it drives me crazy.
Edited 1 time(s). Last edit at 09/12/2015 05:40AM by JohnnyUSA.
|
Re: Debian on NSA310S? September 12, 2015 05:48AM |
Admin Registered: 13 years ago Posts: 18,997 |
Johnny,
My theory is your time at one point your RTC was set to a bad value. So it should be adjusted to a sane one and then it will be normal again.
You do need at least one server to sync time during boot. So
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
My theory is your time at one point your RTC was set to a bad value. So it should be adjusted to a sane one and then it will be normal again.
You do need at least one server to sync time during boot. So
cat /etc/ntp.conf | grep serverIf no server specified in your ntp.conf, then you should uncomment all four. You can sync with other time servers, instead of using Debian pool servers. But normally, uncomment these pools is all you need to do.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on NSA310S? September 12, 2015 06:10AM |
Registered: 9 years ago Posts: 118 |
I have more than 4 servers available:
Tried even with all 4 from debian.pool. It refuses to sync on boot.
Looking through the bootlog i've noticed something strange:
This shows at every boot no matter if cold/warm.
NOTE: I wonder why this happens only with kern 4.2.0 and not with 3.18.5. If i switch to 3.18.5 i have no "date" problems or "dhcp".
Edited 1 time(s). Last edit at 09/12/2015 06:12AM by JohnnyUSA.
root@ionut-nas:~# cat /etc/ntp.conf | grep server # You do need to talk to an NTP server or two (or three). #server ntp.your-provider.example # pool.ntp.org maps to about 1000 low-stratum NTP servers. Your server will server 0.debian.pool.ntp.org iburst #server 1.debian.pool.ntp.org iburst #server 2.debian.pool.ntp.org iburst #server 3.debian.pool.ntp.org iburst server 192.12.19.20 server 164.67.62.194 server 140.142.16.34 server 206.246.122.250 # Note that "restrict" applies to both servers and clients, so a configuration # up blocking replies from your own upstream servers. # Local users may interrogate the ntp server more closely.
Tried even with all 4 from debian.pool. It refuses to sync on boot.
Looking through the bootlog i've noticed something strange:
221.[ 2.177562] ht1382 0-0068: setting system clock to 2070-01-02 17:38:55 UTC (3155909935)
This shows at every boot no matter if cold/warm.
NOTE: I wonder why this happens only with kern 4.2.0 and not with 3.18.5. If i switch to 3.18.5 i have no "date" problems or "dhcp".
Edited 1 time(s). Last edit at 09/12/2015 06:12AM by JohnnyUSA.
|
Re: Debian on NSA310S? September 12, 2015 10:46AM |
Registered: 9 years ago Posts: 47 |
|
Re: Debian on NSA310S? September 12, 2015 03:04PM |
Admin Registered: 13 years ago Posts: 18,997 |
osa Wrote:
-------------------------------------------------------
> 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.
osa,
We should not use hwclock, IMO. ntpd is sync to the rtc, so that might mess up the clock. As long as ntpd is running, it should adjust to the correct date time.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-------------------------------------------------------
> 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.
osa,
We should not use hwclock, IMO. ntpd is sync to the rtc, so that might mess up the clock. As long as ntpd is running, it should adjust to the correct date time.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on NSA310S? September 12, 2015 05:08PM |
Registered: 9 years ago Posts: 47 |
So.. we do not need rtc driver?Quote
ntpd is sync to the rtc,
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 reason
|
Re: Debian on NSA310S? September 12, 2015 05:11PM |
Registered: 9 years ago Posts: 118 |
osa Wrote:
-------------------------------------------------------
>
> 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 reason
@osa,
How do i fix this exactly?
-------------------------------------------------------
>
> So.. we do not need rtc driver?Quote
ntpd is sync to the rtc,
> 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 reason
@osa,
How do i fix this exactly?
|
Re: Debian on NSA310S? September 12, 2015 05:47PM |
Admin Registered: 13 years ago Posts: 18,997 |
@osa,
> So.. we do not need rtc driver?
They are complimentary (2 slightly different purposes). On boxes without rtc, ntpd is all you need. On boxes that has rtc, then the clock is accurate to the granularity of the rtc capability while rtc is running.
> Proper or just not stupid date/time is needed to
> get dhcp working (in my case)
True.Once it is set to sane value then DHCP will be OK.
@Johnny,
Use the command date to set it manually lin Linux.
However, you should get ntp running correctly anyway. That way your clock will never be messed up again. The new kernel 4.2 has osa's patch incorporated, so rtc should work properly, however it has to start with a good value.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> So.. we do not need rtc driver?
They are complimentary (2 slightly different purposes). On boxes without rtc, ntpd is all you need. On boxes that has rtc, then the clock is accurate to the granularity of the rtc capability while rtc is running.
> Proper or just not stupid date/time is needed to
> get dhcp working (in my case)
True.Once it is set to sane value then DHCP will be OK.
@Johnny,
Use the command date to set it manually lin Linux.
However, you should get ntp running correctly anyway. That way your clock will never be messed up again. The new kernel 4.2 has osa's patch incorporated, so rtc should work properly, however it has to start with a good value.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on NSA310S? September 12, 2015 06:00PM |
Registered: 9 years ago Posts: 118 |
@bodhi,
the thing that troubles me so much is i don't understand why i have these problems and you guys don't, i'm using the same rootfs with no modifications besides locales and tzdata. Those two can affect so much?
Tomorrow morning i'll try to set the date manually. Atm i'm running with default 3.18.5 kernel (only one that works without problems).
PS: bodhi, can you share the correct address for zyxelos nand boot? lost mine. Cheers!
Edited 1 time(s). Last edit at 09/12/2015 06:02PM by JohnnyUSA.
the thing that troubles me so much is i don't understand why i have these problems and you guys don't, i'm using the same rootfs with no modifications besides locales and tzdata. Those two can affect so much?
Tomorrow morning i'll try to set the date manually. Atm i'm running with default 3.18.5 kernel (only one that works without problems).
PS: bodhi, can you share the correct address for zyxelos nand boot? lost mine. Cheers!
Edited 1 time(s). Last edit at 09/12/2015 06:02PM by JohnnyUSA.
|
Re: Debian on NSA310S? September 12, 2015 06:20PM |
Admin Registered: 13 years ago Posts: 18,997 |
JohnnyUSA Wrote:
-------------------------------------------------------
> @bodhi,
> the thing that troubles me so much is i don't
> understand why i have these problems and you guys
> don't, i'm using the same rootfs with no
> modifications besides locales and tzdata. Those
> two can affect so much?
Just make sure ntp is working. You can try different time servers that are close to your locale:
http://support.ntp.org/bin/view/Servers/WebHome
And then watch your serial log to see if the clock is set to a good value during booting (the time value when you shutdown), and then check the current clock is saved when you shut down.
> PS: bodhi, can you share the correct address for
> zyxelos nand boot? lost mine. Cheers!
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-------------------------------------------------------
> @bodhi,
> the thing that troubles me so much is i don't
> understand why i have these problems and you guys
> don't, i'm using the same rootfs with no
> modifications besides locales and tzdata. Those
> two can affect so much?
Just make sure ntp is working. You can try different time servers that are close to your locale:
http://support.ntp.org/bin/view/Servers/WebHome
And then watch your serial log to see if the clock is set to a good value during booting (the time value when you shutdown), and then check the current clock is saved when you shut down.
> PS: bodhi, can you share the correct address for
> zyxelos nand boot? lost mine. Cheers!
nand read.e 0x2000000 0xc80000 0xA00000; bootm 0x2000000
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on NSA310S? September 13, 2015 06:35AM |
Registered: 9 years ago Posts: 118 |
Thanks to @bodhi and @osa, i finally managed to make it work using data and hwclock commands. Now it's working ok with or without dhcp. I suppose my hwclock was messed up badly...
But.. as always, something else happened ...:))
@bodhi, i'm using atm your custom uboot envs you've sent me to PM and looking at dmesg, i get some strange things:
Something to worry about?
On a side note, found a fix(by Braiam) for ntp not working fine on Debian Jessie:
Now my ntp is working fine on every warmboot/coldboot:
NOTE: If i unplug the power cord while NAS is running and i plug it back in, the box starts again so, i suppose NSA310s has PowerON Resume?
Edited 11 time(s). Last edit at 09/13/2015 08:36AM by JohnnyUSA.
But.. as always, something else happened ...:))
@bodhi, i'm using atm your custom uboot envs you've sent me to PM and looking at dmesg, i get some strange things:
[ 4.217679] sd 2:0:0:0: Attached scsi generic sg1 type 0 [ 4.229066] sd 2:0:0:0: [sdb] Write Protect is off [ 4.237185] sd 2:0:0:0: [sdb] Mode Sense: 43 00 00 00 [ 4.237928] sd 2:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [ 4.253974] sdb: sdb1 [ 4.268303] sd 2:0:0:0: [sdb] Attached SCSI removable disk [ 14.495495] __nand_correct_data: uncorrectable ECC error [ 14.500828] __nand_correct_data: uncorrectable ECC error [ 14.506180] blk_update_request: I/O error, dev mtdblock5, sector 8 [ 19.678818] EXT3-fs (sdb1): mounted filesystem with ordered data mode [ 19.685334] kjournald starting. Commit interval 5 seconds [ 21.009295] random: nonblocking pool is initialized [ 21.092969] systemd-udevd[310]: starting version 215 [ 21.401518] input: gpio_keys as /devices/platform/gpio_keys/input/input0 [ 21.649244] orion_wdt: Initial timeout 25 sec [ 22.805560] __nand_correct_data: uncorrectable ECC error [ 22.810897] __nand_correct_data: uncorrectable ECC error [ 22.831596] blk_update_request: I/O error, dev mtdblock5, sector 8 [ 23.766717] EXT3-fs (sdb1): using internal journal
Something to worry about?
On a side note, found a fix(by Braiam) for ntp not working fine on Debian Jessie:
Ntpdate is running when you try to start the server. I haven't found reasons why to leave it installed so you could remove it if you are using ntp daemon:apt-get remove ntpdate
Now my ntp is working fine on every warmboot/coldboot:
root@ionut-nas:~# logread | grep -i ntp Sep 13 14:51:23 ionut-nas daemon.notice ntpd[1533]: ntpd 4.2.6p5@1.2349-o Fri Ap r 10 19:35:06 UTC 2015 (1) Sep 13 14:51:23 ionut-nas daemon.notice ntpd[1534]: proto: precision = 1.728 use c Sep 13 14:51:23 ionut-nas daemon.info ntpd[1534]: Listen and drop on 0 v4wildcar d 0.0.0.0 UDP 123 Sep 13 14:51:23 ionut-nas daemon.info ntpd[1534]: Listen and drop on 1 v6wildcar d :: UDP 123 Sep 13 14:51:23 ionut-nas daemon.info ntpd[1534]: Listen normally on 2 lo 127.0. 0.1 UDP 123 Sep 13 14:51:23 ionut-nas daemon.info ntpd[1534]: Listen normally on 3 eth0 192. 168.1.173 UDP 123 Sep 13 14:51:23 ionut-nas daemon.info ntpd[1534]: Listen normally on 4 eth0 2a02 :2f0d:xxxx:ed00:xxxx:abff:fedf:xxx UDP 123 Sep 13 14:51:23 ionut-nas daemon.info ntpd[1534]: Listen normally on 5 lo ::1 UD P 123 Sep 13 14:51:23 ionut-nas daemon.info ntpd[1534]: Listen normally on 6 eth0 fde9 :xxxx:493e:0:xxxx:abff:fedf:xxx UDP 123 Sep 13 14:51:23 ionut-nas daemon.info ntpd[1534]: Listen normally on 7 eth0 fe80 ::xxx:xxxx:fedf:72b UDP 123 Sep 13 14:51:23 ionut-nas daemon.info ntpd[1534]: peers refreshed Sep 13 14:51:23 ionut-nas daemon.info ntpd[1534]: Listening on routing socket on fd #24 for interface updates
NOTE: If i unplug the power cord while NAS is running and i plug it back in, the box starts again so, i suppose NSA310s has PowerON Resume?
Edited 11 time(s). Last edit at 09/13/2015 08:36AM by JohnnyUSA.
|
Re: Debian on NSA310S? September 13, 2015 09:00AM |
Registered: 9 years ago Posts: 295 |
JohnnyUSA Wrote:
-------------------------------------------------------
>
> Something to worry about?
I see this more or less on many kirkwood devices.
-------------------------------------------------------
>
> [ 14.495495] __nand_correct_data: > uncorrectable ECC error > [ 14.500828] __nand_correct_data: uncorrectable > ECC error > [ 22.805560] __nand_correct_data: > uncorrectable ECC error > [ 22.810897] __nand_correct_data: uncorrectable > ECC error > [ 22.831596] blk_update_request: I/O error, dev > mtdblock5, sector 8 >>
> Something to worry about?
I see this more or less on many kirkwood devices.
|
Re: Debian on NSA310S? September 13, 2015 01:31PM |
Admin Registered: 13 years ago Posts: 18,997 |
Johnny,
> [ 14.495495] __nand_correct_data:
> uncorrectable ECC error
> [ 14.500828] __nand_correct_data: uncorrectable
> ECC error
> [ 14.506180] blk_update_request: I/O error, dev
> mtdblock5, sector 8
This is mtd5 so no need to worry about. But it means that the stock FW probably has problem. Eventually you want to get rid of this error, could be done by reformatting the rest of NAND (i.e. for rescue system). We only need mtd0 where u-boot is.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> [ 14.495495] __nand_correct_data:
> uncorrectable ECC error
> [ 14.500828] __nand_correct_data: uncorrectable
> ECC error
> [ 14.506180] blk_update_request: I/O error, dev
> mtdblock5, sector 8
This is mtd5 so no need to worry about. But it means that the stock FW probably has problem. Eventually you want to get rid of this error, could be done by reformatting the rest of NAND (i.e. for rescue system). We only need mtd0 where u-boot is.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on NSA310S? September 13, 2015 01:37PM |
Registered: 9 years ago Posts: 118 |
bodhi Wrote:
-------------------------------------------------------
> Johnny,
>
> > [ 14.495495] __nand_correct_data:
> > uncorrectable ECC error
> > [ 14.500828] __nand_correct_data:
> uncorrectable
> > ECC error
> > [ 14.506180] blk_update_request: I/O error,
> dev
> > mtdblock5, sector 8
>
> This is mtd5 so no need to worry about. But it
> means that the stock FW probably has problem.
> Eventually you want to get rid of this error,
> could be done by reformatting the rest of NAND
> (i.e. for rescue system). We only need mtd0 where
> u-boot is.
bodhi,
good to know, but for future reference, how can i investigate the stock FW? Tried today to access it with my default envs(that i "magically" found
on 1st page of this topic) and failed, some $kernel error on boot.
Why i care about this? Because i want to try and restore the dual boot (usb/zyxel os) after the u-boot upgrade i did.
Edited 1 time(s). Last edit at 09/13/2015 01:38PM by JohnnyUSA.
-------------------------------------------------------
> Johnny,
>
> > [ 14.495495] __nand_correct_data:
> > uncorrectable ECC error
> > [ 14.500828] __nand_correct_data:
> uncorrectable
> > ECC error
> > [ 14.506180] blk_update_request: I/O error,
> dev
> > mtdblock5, sector 8
>
> This is mtd5 so no need to worry about. But it
> means that the stock FW probably has problem.
> Eventually you want to get rid of this error,
> could be done by reformatting the rest of NAND
> (i.e. for rescue system). We only need mtd0 where
> u-boot is.
bodhi,
good to know, but for future reference, how can i investigate the stock FW? Tried today to access it with my default envs(that i "magically" found
on 1st page of this topic) and failed, some $kernel error on boot.
Why i care about this? Because i want to try and restore the dual boot (usb/zyxel os) after the u-boot upgrade i did.
Edited 1 time(s). Last edit at 09/13/2015 01:38PM by JohnnyUSA.
|
Re: Debian on NSA310S? September 13, 2015 01:42PM |
Admin Registered: 13 years ago Posts: 18,997 |
JohnnyUSA Wrote:
-------------------------------------------------------
> bodhi Wrote:
> --------------------------------------------------
> -----
> > Johnny,
> >
> > > [ 14.495495] __nand_correct_data:
> > > uncorrectable ECC error
> > > [ 14.500828] __nand_correct_data:
> > uncorrectable
> > > ECC error
> > > [ 14.506180] blk_update_request: I/O error,
> > dev
> > > mtdblock5, sector 8
> >
> > This is mtd5 so no need to worry about. But it
> > means that the stock FW probably has problem.
> > Eventually you want to get rid of this error,
> > could be done by reformatting the rest of NAND
> > (i.e. for rescue system). We only need mtd0
> where
> > u-boot is.
>
> bodhi,
>
> good to know, but for future reference, how can i
> investigate the stock FW? Tried today to access it
> with my default envs(that i "magically" found
> on 1st page of this topic) and failed, some
> $kernel error on boot.
>
> Why i care about this? Because i want to try and
> restore the dual boot (usb/zyxel os) after the
> u-boot upgrade i did.
We need to boot back to stock OS to see whether this would cause problem. However, I did not think about stock when I wrote the instruction to flash new u-boot, so now I'll need to think about how best to do that. But this has lowest priority on my todo things :)
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-------------------------------------------------------
> bodhi Wrote:
> --------------------------------------------------
> -----
> > Johnny,
> >
> > > [ 14.495495] __nand_correct_data:
> > > uncorrectable ECC error
> > > [ 14.500828] __nand_correct_data:
> > uncorrectable
> > > ECC error
> > > [ 14.506180] blk_update_request: I/O error,
> > dev
> > > mtdblock5, sector 8
> >
> > This is mtd5 so no need to worry about. But it
> > means that the stock FW probably has problem.
> > Eventually you want to get rid of this error,
> > could be done by reformatting the rest of NAND
> > (i.e. for rescue system). We only need mtd0
> where
> > u-boot is.
>
> bodhi,
>
> good to know, but for future reference, how can i
> investigate the stock FW? Tried today to access it
> with my default envs(that i "magically" found
> on 1st page of this topic) and failed, some
> $kernel error on boot.
>
> Why i care about this? Because i want to try and
> restore the dual boot (usb/zyxel os) after the
> u-boot upgrade i did.
We need to boot back to stock OS to see whether this would cause problem. However, I did not think about stock when I wrote the instruction to flash new u-boot, so now I'll need to think about how best to do that. But this has lowest priority on my todo things :)
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on NSA310S? September 13, 2015 01:48PM |
Registered: 9 years ago Posts: 118 |
|
Re: Debian on NSA310S? July 15, 2016 06:39PM |
Registered: 11 years ago Posts: 16 |
Zyxel nsa310s with stock uboot:
Booting Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi from Sandisk Cruze USB stick: SUCCESS!
Thank you very much Bodhi and Pengu for detailed and clear instructions. The system is recognized as nsa310s (had to edit rc.local)
Now I need to figure out how to mount the array member that Zyxel created on the internal drive.
It's really awesome to be able to boot Debian from USB without flashing anything, the fw_env settings work great.
Booting Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi from Sandisk Cruze USB stick: SUCCESS!
Thank you very much Bodhi and Pengu for detailed and clear instructions. The system is recognized as nsa310s (had to edit rc.local)
Now I need to figure out how to mount the array member that Zyxel created on the internal drive.
It's really awesome to be able to boot Debian from USB without flashing anything, the fw_env settings work great.
