Ohh I see. I’m running Ubuntu 20.04.2
In that case, install dnsmasq on your Desktop PC running ubuntu 20.04.2 desktop pc, and leave the beagle in default/auto/dhcp mode…
Here is one guide:
Or stick a router between your PC and your network connection.
Got it, I’ll set that up. Thanks a ton!
Thanks for all your hard work RCN!
Could you explain the differences between using the rootfs and your “blessed” flasher image? I’m moving up from 16.04 and given that 20.04 still has nearly 4 years of life left vs 2 years for 18.04 or ~2 years for any debian release that might come out this summer, 20.04 LTS seems like the foundation to build on for immediate projects.
Hi @CNN, for Ubuntu there is very little difference between my versions and normal Ubuntu.
We just add an apt repo, with our beagleboard.org kernel builds on top of Ubuntu… To make it easy to install and update our kernel builds.
I’ve been ussing Ubuntu 20.04 on a beaglebone black by following the setup in this guide. I have it running off of a 32 GB SD card. I’ve been running into issues where the beaglebone will suddenly freeze (my ssh connection drops, the lights that previously always flickered on the board now just stay on and sometimes the ethernet port light turns off). I suspect that it’s RAM related but I’ve added 2GB of swap space through the SD card. Any thoughts on how I could proceed to debug this? It happens more often when I’m running ROS
Hi @mrunaljsarvaiya what kernel? uname -r?
Output of uname -r is 4.19.191-bone67
Humm, i’ve a boards running that right now in my test farm:
[bbg-pwr07-ser15: 4.19.191-bone67 (up 14 hours, 48 minutes)] reboot system boot 4.19.191-bone67 Thu Aug 19 03:12 still running reboot system boot 4.19.191-bone67 Wed Aug 18 21:32 - 03:11 (05:39) reboot system boot 4.19.191-bone67 Thu Aug 12 21:39 - 21:31 (5+23:52) reboot system boot 4.19.191-bone67 Thu Aug 12 21:30 - 21:38 (00:08) reboot system boot 4.19.191-bone67 Thu Aug 12 16:55 - 21:29 (04:34) reboot system boot 4.19.191-bone67 Thu Aug 5 23:14 - 16:54 (6+17:40) reboot system boot 4.19.191-bone67 Thu Aug 5 15:37 - 23:13 (07:35) reboot system boot 4.19.191-bone67 Tue Jul 27 20:50 - 15:37 (8+18:47) reboot system boot 4.19.191-bone67 Tue Jul 13 16:12 - 20:49 (14+04:37) reboot system boot 4.19.191-bone67 Tue Jul 13 15:47 - 16:11 (00:23) reboot system boot 4.19.191-bone67 Tue Jul 13 15:24 - 15:47 (00:23) reboot system boot 4.19.191-bone67 Fri Jul 9 00:36 - 15:23 (4+14:46) reboot system boot 4.19.191-bone67 Tue Jul 6 21:23 - 00:36 (2+03:13) reboot system boot 4.19.191-bone67 Thu Jun 24 13:36 - 21:22 (12+07:45) reboot system boot 4.19.191-bone67 Tue Jun 22 19:56 - 13:35 (1+17:39) reboot system boot 4.19.191-bone67 Fri Jun 18 23:46 - 19:55 (3+20:09) reboot system boot 4.19.191-bone67 Fri Jun 18 23:39 - 23:45 (00:06) reboot system boot 4.19.191-bone67 Wed Jun 16 22:13 - 23:39 (2+01:25) reboot system boot 4.19.191-bone67 Tue Jun 8 15:21 - 22:12 (8+06:50) reboot system boot 4.19.191-bone67 Mon Jun 7 21:41 - 15:21 (17:40) reboot system boot 4.19.191-bone67 Wed Jun 2 16:11 - 21:40 (5+05:28)
These devices remain mostly idle, but run an uptime status report over nfs every 15 minutes…
anything in the serial log?
Could you please clarify what you mean by serial log? I’m ssh’ed in, I don’t see any errors on that terminal window
So I simultaneously ran dmesg and as the beaglebone froze I got this message
[Aug19 19:07] PM: suspend entry (deep)
[ +0.000018] PM: Syncing filesystems … done.
Oh, are you putting it in standby???
It’s been a very long time since I tested Sleep functionality…
No I’m not! I was in the middle of some code development and it randomly froze
What could cause it to enter the standby state?
Should I try this?
sudo systemctl mask sleep.target suspend.target hibernate.target hybrid-sleep.target
That’s this section:
Let’s look your linux log:
journalctl | grep suspend journalctl | grep PM
Got it thanks for the link to the code!
journalctl | grep suspend returned empty.
journalctl | grep PM returned the following:
May 27 15:16:20 arm kernel: hw perfevents: enabled with armv7_cortex_a8 PMU driver, 5 counters available
Aug 20 17:32:21 arm /usr/lib/gdm3/gdm-x-session: (==) modeset(0): DPMS enabled
Aug 20 17:32:21 arm /usr/lib/gdm3/gdm-x-session: (II) Initializing extension DPMS
journalctl -f and got these relevant logs when the beaglebone went to sleep
Aug 20 18:05:55 arm NetworkManager: [1629482755.8353] manager: sleep: sleep requested (sleeping: no enabled: yes)
Aug 20 18:05:55 arm systemd: Reached target Sleep.
Aug 20 18:05:55 arm systemd: Starting Suspend…
Aug 20 18:05:56 arm gnome-shell: Screen lock is locked down, not locking
Aug 20 18:05:56 arm systemd-sleep: Suspending system…
Aug 20 18:05:56 arm kernel: PM: suspend entry (deep)
So it’s gnome, that’s forcing suspend… Sorry I use Cinnamon, take a look at this article:
Got it, thanks a ton!!
So I ran into the same issue (beaglebone froze, 2 of the user LEDS and ethernet lights constantly stayed on). But I didn’t see any unusual messages through
journalctl -f. Any other logs you’d recommend taking a look at? CPU usage wasn’t too bad (~25%), 50% of the RAM was in use and the rest was in cache.
The code that is running, executes a loop at 100Hz, where during every cycle it queries a GPIO input and sets the duty cycle on a pwm pin
I really hope the PRU is doing that.