kc9udx so any IP address assigned to the machine in question would work.
Yeah, any address in the 127/8 range should work (it does on Linux); even 127.0.0.1 is OK. After all, no packets sent by the system to any of its own addresses (even external) will ever go out on the wire.
anarchosax That looks pretty straight forward, but I am wondering what happens when the laptop goes traveling… Doesn’t/etc/hosts file up quickly?
Don't get this--how does it fill up? We're just saying that the hostname is also 127.0.0.1.
anarchosax I added a -t4value in the xbattbar line of my ~/.xinitrc and again, I am getting xauth errors.
Correlation--not causation, mate. xauth is a red-herring (really! I can give you chapter and verse if you want...).
I think the root cause here is, either:
- an issue with your HW (less likely).
Run memtest+ for a day or so to rule out the major cause of this, ie. memory.
- KabyLake CPU issue (even less likely).
Update the BIOS and install the latest intel-microcode-netbsd package for this one.
- this is an DRMKMS driver problem.
There were some fixes just a few days ago for KabyLake Gen6 HW.
For the latter, either try the latest -HEAD image (with the recommended modesetting(4) Xorg display-driver), or if that too is unstable use the safe wsfb(4) driver. You could also run a 10.1 userland on the latest -HEAD kernel/modules/graphics-blobs to keep using the quarterly binary packages.
