11-06-2017, 11:11 PM
Thanks TC
That link was interesting reading -- great insight into Linux. I spent the next couple hours in follow-up reading. Yeah, it's fun to learn.
Perhaps I was unclear. My last post was meant to show that there is NO difference between a live boot from USB vs a boot from the installed system -- at least in regards to the problem behaviour.
The triggering event is enabling a wifi connection -- the enabling event is a power-up boot. The problem does not occur after a subsequent soft boot (i.e. sudo reboot).
I've got to believe this problem is isolated to the hardware on my bench. If it were more common, there would be lots of complaints, and there would be far fewer installs. When it pops up, the problem is severe enough to make the system unusable. That is why I call it a bug -- marked high severity but low frequency, use work-around.
Jim
That link was interesting reading -- great insight into Linux. I spent the next couple hours in follow-up reading. Yeah, it's fun to learn.
Perhaps I was unclear. My last post was meant to show that there is NO difference between a live boot from USB vs a boot from the installed system -- at least in regards to the problem behaviour.
The triggering event is enabling a wifi connection -- the enabling event is a power-up boot. The problem does not occur after a subsequent soft boot (i.e. sudo reboot).
I've got to believe this problem is isolated to the hardware on my bench. If it were more common, there would be lots of complaints, and there would be far fewer installs. When it pops up, the problem is severe enough to make the system unusable. That is why I call it a bug -- marked high severity but low frequency, use work-around.
Jim
If not looking for things, I'm waiting for things.