Hello! huh, this doesn't look too good. The most common reason for prob1:
> problem 1 : I’m using E320 with uhd 3.15 and static boost lib. I can do > uhd_find_device and it work for a min then its stop when I use args=”addr=192…..” does anyone has this problem? I appreciate the help would be that your computer reconfigures your network interface "cleverly"; seen that disrupt connections to USRPs more than once... However, > problem 2: I ssh to E320 and I receive kernel error attached. > Uff. We've got a failing sd-resolv, and it seems to fail in kernel land on socket creation... uh. This *might* be a result of the ext4 filesystem driver dying a second earlier, when it tries to allocate memory where it shouldn't. Never saw that. I believe the kernel on that machine has no Ettus-specific modification related to storage, so a process causing kernel errors when trying to list a directory is ... surprising. Can you SSH on the device first, and then simply do something like dmesg cd / find -type f > /dev/null dmesg and observe whether you get new dmesg errors through exercising the file system? If that is the case: Do you have the board-only version of the E320, where it'd be easy to access the SD card? Best regards, Marcus _______________________________________________ USRP-users mailing list -- usrp-users@lists.ettus.com To unsubscribe send an email to usrp-users-le...@lists.ettus.com
