Hey bodhi, installed your new 4.6 kernel (big thanks btw!), and dmesg gives me the following warning: [ 2.776931] : /ocp@f1000000/mdio-bus@72004/ethernet-phy@1: Whitelisted compatible string. Please remove At the moment everything works fine, nothing to complain. Wanted to know if i can ignore this warning. Thanks in advance! LE: Unit is NSA310sby JohnnyUSA - Debian
Thanks for this topic @bodhi I think you'd better PIN this one on top if you're willing to keep us updated each time something major comes up ;)by JohnnyUSA - Debian
bodhi Wrote: ------------------------------------------------------- > OK. I finally figured out this problem with the > NSA310S Ethernet. It was the Marvell PHY code > change. > > So kernel 4.5 is working OK. I will release it > when I can. Beautiful! /bow to youby JohnnyUSA - Debian
Damn guys, i was waiting for a 4.5 release on 310s, i guess i'll have to wait until you wizards will manage to fix it :)by JohnnyUSA - Debian
Thanks bodhi!by JohnnyUSA - Debian
bodhi Wrote: ------------------------------------------------------- > JohnnyUSA Wrote: > -------------------------------------------------- > ----- > > Strange thing is, for me it's working fine now. > > And you guys know i've had the same problems as > > @giggls. > > Johnny, > > Are you running stock u-boot? @bodhi, No more, iby JohnnyUSA - Debian
Strange thing is, for me it's working fine now. And you guys know i've had the same problems as @giggls.by JohnnyUSA - Debian
Yes, you're missing the fact that @bodhi posted instructions on how you can regenerate those keys. Also he firmly suggests that you should do that on your first run on his rootfs. Read carefully his guide. Quote from his topic: Quote Note1: After logging in this rootf the first time, remember to generate new SSH key to make it your own unique rootfs. And also update your rootfs tby JohnnyUSA - Debian
bodhi, Tell me when ready and i will be your tester on this matter ;)by JohnnyUSA - Debian
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 toby JohnnyUSA - Debian
@bodhi, thanks! it worked!by JohnnyUSA - uBoot
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: [ 4.217679] sd 2:0:0:0: Attacby JohnnyUSA - Debian
@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, canby JohnnyUSA - Debian
osa Wrote: ------------------------------------------------------- > 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, righby JohnnyUSA - Debian
I have more than 4 servers available: 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.by JohnnyUSA - Debian
@bodhi, 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 toby JohnnyUSA - Debian
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 # 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 serverby JohnnyUSA - Debian
@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: NET: Registered protocol family 10 IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 100 Mb/s, full duplex, flow control disabled IPv6: ADDRCONF(NETDEV_CHANGE): eth0:by JohnnyUSA - Debian
@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 instruby JohnnyUSA - Debian
@bodhi, i'm trying to flash the new u-boot for nsa310s but i'm a bit scared of those bad blocks you're mentioning in the tutorial. My dmesg is this: [ 1.982828] Bad eraseblock 100 at 0x000000c80000 [ 1.992505] Bad eraseblock 200 at 0x000001900000 Is it safe to flash? Or i need some workaround? I'm a bit confused about this considering your warning: Be surby JohnnyUSA - uBoot
@chrishelms, don't worry, it's easy, just be careful to connect the pins in the correct order.by JohnnyUSA - Debian
osa Wrote: ------------------------------------------------------- > 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 > dhby JohnnyUSA - Debian
@bodhi, did a restart after i've removed the lines you said i don't need so now, my /etc/network/interfaces looks like this: auto lo eth0 iface lo inet loopback iface eth0 inet static address 192.168.1.173 netmask 255.255.255.0 gateway 192.168.1.1 Also, here is the DMESG after reboot: [ 2.068207] libphy: orion_mdio_bus: probed [ 2.078641]by JohnnyUSA - Debian
@bodhi, with stock OS it does. Can you check please since you have the box also? I'm unable to test atm, but i remember it did with stock. I've removed the power cable and plugged back in and the box auto started. Also, this is something to worry about? Or i better ignore it?: [ 63.374474] mv643xx_eth: Set the PHY back to auto-negotiation mode [ 63.408626] mv643xx_eth_poby JohnnyUSA - Debian
@bodhi, nicely done! Gonna test it soon.by JohnnyUSA - uBoot
Just came back home after aprox. 2 weeks of absence, installed the new kernel and phy working fine without old workarounds. Fantastic job guys! I'll keep investigating and see if any more problems surface. Cheers!! LE: Everything is working as expected except the fact that box doesnt resume after power loss, i need to power it manually. Any hints on how to debug/fix this?by JohnnyUSA - Debian
osa, care to share the exact steps you did to apply the patch pls? i'm kinda noob at this.by JohnnyUSA - Debian
@bodhi, where is the LIKE button on these forums? We badly need one :Pby JohnnyUSA - Debian