On Mon, Jul 29, 2019 at 07:56:25AM -0400, Gene Heskett wrote: > On Monday 29 July 2019 05:08:49 Reco wrote: > > > On Sun, Jul 28, 2019 at 08:15:20PM -0400, Gene Heskett wrote: > > > On Sunday 28 July 2019 00:27:36 Reco wrote: > > > > On Sun, Jul 28, 2019 at 12:13:21AM -0400, Gene Heskett wrote: > > > > > > > That, and a whole restaraunt sized menu of dpkg stuff for > > > > > > > building packages is on the missing list. Grrrrr. > > > > > > > > > > > > apt install build-essential > > > > > > > > > > I *think* I did that. With synaptic. I gave it quite a list, it > > > > > took about an hour to install it all on a 100Mb circuit. > > > > > > > > If you're unsure if it's installed or not - you have bigger > > > > problems. > > > > > > > > > If it will boot normally I'll make sure. > > > > > > > > Why won't it? > > > > > > It gets to udev, and everything after that seem to take twice as > > > long as the last start, by the time it gets to MTD, whatever that > > > is, the blanker kicks in and nothing will wake it up. I don't > > > thinks its started ssh yet at that point, but its been 6 or so > > > hours. Nope. No ssh answering the phone. > > > > Two options. > > > > 1) You want to solve the problem. > > Then it's "show, do not tell". > > Boot the kernel with the "debug" option, send journalctl output here. > > Where do I find that journalctl log?
journalctl(1). Try it some day. > There not being a handy reset button on the pi makes me use the power > switch, I find it shocking that a man of your skill did not think about a low-voltage circuit-breaker between a power source and a Raspberry Pi. Reco
