On Tue, Jun 12, 2018 at 08:07:20AM -0500, Jonathan A. Kollasch wrote: > On Tue, Jun 12, 2018 at 12:13:27PM +0100, Patrick Welche wrote: > > I haven't seen "autoconfiguration error" before - something to worry about? > > (native X works fine) > > > > No, just an extra couple of words that were added to those messages > > to make them easier to spot (easier to grep for.) > > > > kre > > As kre says. It was nearly impossible to spot what caused the > aprint(9) error count to be incremented. That made the "WARNING: > %d error%s while detecting hardware; check system log.\n" message from > config_finalize() very difficult diagnose in the cases where the error > message isn't worded ominously enough???a not-uncommon occurrence.
Ah - I have often thought "what hardware errors?" I hadn't connected the two. Maybe s/detecting/autoconfiguring/ - it sounds worse but the pattern matching works better? Or just leave it, as you (and kre) have applied clue instead... Cheers, Patrick
