**** BEGIN LOGGING AT Sat Jul 22 03:00:04 2017 Jul 22 12:31:08 Hi, I'm having some issues with setting up NFS with my BBB. I'm not sure where the issue lies, but for a starter my ethernet link goes down and up again when the boot sequence arrives at the NFS part Jul 22 12:31:20 But the problem is, the ip is lost in the process Jul 22 12:31:57 I tried to edit /etc/network/interfaces to add a static address, which work prefectly when I ifup/ifdown the interface Jul 22 12:32:38 But for some reason, when I reset my BBB, the IP disappears Jul 22 12:35:46 From what I saw, it could be linked to the Network Manager, which I disabled Jul 22 12:35:55 But maybe I didn't disable it enough? Jul 22 12:40:54 Here's the boot log I'm getting https://paste.debian.net/977625 Jul 22 13:10:24 teroshan: the fact that this probably should not be, but why exactly is the ip address necessary? did you filter by IP at the NFS server? Jul 22 13:17:12 knttl: Not really. What's the alternative, setting up a dhcp server ? Jul 22 13:18:53 if you don't filter on nfs server side you client ip souldn't even matter. as far as i know. Jul 22 13:19:11 maybe kernel parameter "nfsrootdebug" will help you a little? Jul 22 13:19:43 Great, I'll activate that then Jul 22 13:19:49 Thanks! Jul 22 13:37:29 link down/up is because linux resets the phy when bringing it up... very annoying Jul 22 13:39:54 rootpath is blank Jul 22 13:40:08 I can't imagine that is right :P Jul 22 13:57:09 I saw multiple logs online with the rootpath blank that successfully booted Jul 22 13:57:19 hmm Jul 22 13:57:58 And I put "bootargs=console=ttyO0,115200 root=/dev/nfs rw nfsroot=192.168.0.1:/nfs ip=192.168.0.100:192.168.0.1::255.255.255..0:beagle::off:: nfsrootdebug" as my bootarg Jul 22 13:58:08 ok, it's been too long ago since I've done anything with nfs Jul 22 13:58:13 what makes you say it lost its ip ? Jul 22 13:58:18 So the path is there, if I trust the kernel documentation Jul 22 13:58:58 When I reset the board, once comes the part where the NFS magic should happen, my eth link comes down, and up without the IP Jul 22 13:59:04 ON the host (server) Jul 22 13:59:24 When I look at desmg Jul 22 13:59:34 [56062.935672] r8169 0000:01:00.0 enp1s0: link down Jul 22 13:59:37 [56065.448676] r8169 0000:01:00.0 enp1s0: link up Jul 22 13:59:42 That's what I see Jul 22 14:00:03 And since network is like black magic to me, I was wondering if maybe I was missing something on the host Jul 22 14:00:19 ohh Jul 22 14:00:53 And when it comes up, there isn't an ip if I look at the ifconfig Jul 22 14:01:07 just like if I did ifconfig eth0 0.0.0.0 Jul 22 14:01:10 the bbb is connected directly to the host, not via a switch? Jul 22 14:01:13 Yep Jul 22 14:01:50 you shouldn't use ifconfig (or its newer replacement "ip addr") to configure it then but setup whatever network manager you use to configure it automatically when the link comes up Jul 22 14:02:04 alternatively, insert a switch between them so the host doesn't see link down/up Jul 22 14:02:33 or most cumbersome of all options, manually configure the ip after the link comes up again Jul 22 14:04:00 I tried spamming "ifconfig eth0 192.168.0.1" while the card was booting, no success there Jul 22 14:04:06 I also have a kernel patch for the BBB side which aims to prevent the phy from being reset when linux brings up the link: https://github.com/dutchanddutch/bb-kernel/blob/am33x-v4.9/patches/local/0003-WiP-trying-to-achieve-fast-link-up-at-boot.patch Jul 22 14:04:10 I'll try looking into what manages the connection maybe Jul 22 14:05:49 oh wow I didn't realize I still left that WARN_ON(1) in that I used to trace how/why the phy was being reset Jul 22 18:27:40 Hello Jul 22 18:52:44 Hello all! I want to use LogiBone cape and PRU together. I tried preconpiled image for LOGiBone and i follow tutorials to work with PRU but i get the error that PRU failed to open. Kernel version 3.8.13 Jul 22 19:25:41 logibone? *googles* Jul 22 19:26:07 kernel 3.8 is really old btw Jul 22 19:27:25 having said that, stuff has changed quite a few times, so if you want to follow a guide you need to find one that's roughly the same age as the image you're using Jul 22 19:40:54 logibone is a fpga cape. now i am trying the latest debian image but i cannot work properly with logibone wishbone communication Jul 22 19:49:02 a lot of pru code uses uio-pruss, which isn't enabled by default in current images Jul 22 19:49:36 in the latest images however it's very easy to enable in /boot/uEnv.txt Jul 22 20:00:48 @zmatt nice to hear this. maybe do you have any link of working tutorial? thank you Jul 22 20:01:46 no idea, sorry... I know there's a lot of outdated info out there unfortunately :/ Jul 22 20:34:52 Hi all, i'm building a custom board based on BBB , what changes i need to do in DT in order to replace the RTC with external RTC chip(likst MCP794x) Jul 22 20:35:46 @zmatt ok! thank you! :) Jul 22 20:36:27 cyberguy: declare the rtc (as child node of the i2c bus)... and maybe something is needed to tell the kernel that it should be used as the default rtc or something Jul 22 20:36:56 I'd say first just declare it and see if that suffices Jul 22 20:49:15 okay, where do i get the exact entry i need to add to the i2c? i've noticed the same chip exacly is with beaglebone x15, here is what i did (after some googling) https://paste.debian.net/977699/ do you think its currect Jul 22 20:50:51 looks okay to me, although I don't see any reason to label it and the 'status = "okay";' is unnecessary Jul 22 20:51:16 (status = "okay" is only needed when it overrides an earlier status = "disabled") Jul 22 20:53:18 zmatt: great thanks! **** ENDING LOGGING AT Sun Jul 23 03:00:01 2017