Thanks Jonathon, This morning, I discovered that after writing the file system image with bmaptool,
- if I immediately pull the SD card from the host card reader and insert it into the E310, it boots up ok - If I instead pull the SD card and re-insert it right away in the host card reader (to force auto-remount), do nothing, then click to eject the SD card and insert in the E310. It does not boot up! The host (Ubuntu 20.04) must do something to the SD card by simply mounting and ejecting the SD card. Perhaps it has something to do with the Data partition being an expandable partition? Any ideas on this? The reason for wanting to re-mount the SD card in the host system right away is to configure the /data/network/eth0.network interface to change it from DHCP to Static IP. At first I speculated that re-writing this file on the host was causing the issue, but later I determined that just the mount/eject sequence causes the problem. Also, any ideas on how I can fix the "date/time" so that it doesn't always come up "Aug 6"? Rob On Thu, Nov 11, 2021 at 6:20 PM Jonathon Pendlum <jonathon.pend...@ettus.com> wrote: > Hey Rob, > > Did you use bmaptool to write the image to your SD card? I ran into the > same issue when using bmaptool. I switched to using dd instead and that > fixed the issue. > > Jonathon > > On Thu, Nov 11, 2021, 18:00 Rob Kossler <rkoss...@nd.edu> wrote: > >> Hi, >> I'm having some issues with my E310 related to booting up the file system >> (UHD 4.1 file system loaded using bmaptool). Any help appreciated! >> >> - Issue 1: during boot up, E310 linux fails mounting the /data >> partition and consequently doesn't configure the Ethernet correctly (such >> that I can't login via ssh) (see below startup log from console window). >> - Note that I can look at the micro SD card on my Ubuntu host and >> I see 4 partitions: /uboot, /data, & the 2 OS partitions. Everything >> looks >> OK. >> - I'm starting to suspect a bad micro SD card, but I don't have >> solid reasoning for that. >> - Issue 2: when I'm in this failed startup state, I can use "ip addr >> add" to configure the eth0 device but I can't figure out how to restart >> the >> sshd so that I can ssh into it (note I can ssh out just fine after setting >> the IP addr). Does anyone know how to do so? >> - Issue 3: I can't figure out how to set the real-time clock. If I >> run "date" after bootup, it shows "Aug 6". I can fix this, but upon >> reboot, it is back to "Aug 6". If I run "hwclock", it says it can't find >> the hwclock. Does anyone know how to set the time in a non-volatile way >> such that it won't be "Aug 6" after a power cycle. >> >> Rob >> >> >> *Bootup Console Log* >> [ OK ] Found device /dev/mmcblk0p1. >> [ OK ] Found device /dev/mmcblk0p4. >> Starting File System Check on /dev/mmcblk0p1... >> Starting File System Check on /dev/mmcblk0p4... >> [ OK ] Started File System Check on /dev/mmcblk0p1. >> Mounting /uboot... >> [ OK ] Mounted /uboot. >> [FAILED] Failed to start File System Check on /dev/mmcblk0p4. >> See 'systemctl status systemd-fsck@dev-mmcblk0p4.service' for details. >> [DEPEND] Dependency failed for /data. >> [DEPEND] Dependency failed for Local File Systems. >> [DEPEND] Dependency failed for Grow File System on /data. >> [ OK ] Stopped Dispatch Password …ts to Console Directory Watch. >> [ OK ] Stopped Forward Password R…uests to Wall Directory Watch. >> >> *hwclock output* >> sh-5.0# hwclock --verbose >> hwclock from util-linux 2.34 >> System Time: 1628268135.768399 >> Trying to open: /dev/rtc0 >> Trying to open: /dev/rtc >> Trying to open: /dev/misc/rtc >> No usable clock interface found. >> hwclock: Cannot access the Hardware Clock via any known method. >> _______________________________________________ >> USRP-users mailing list -- usrp-users@lists.ettus.com >> To unsubscribe send an email to usrp-users-le...@lists.ettus.com >> >
_______________________________________________ USRP-users mailing list -- usrp-users@lists.ettus.com To unsubscribe send an email to usrp-users-le...@lists.ettus.com
