On 06/08/13 03:14, Jonathan Gray wrote:
On Sat, Jun 08, 2013 at 03:06:26AM -0400, Scott McEachern wrote:
On 06/08/13 02:38, Ville Valkonen wrote:
Hi, did you compile the recent Xenocara too?
No, I didn't get that far. Just the kernel. That's how I know it
wasn't the recent xenocara updates that caused the problem and
believe this specific commit is the culprit.
However, you did get me thinking...
I'll skip using X and go console-only, build the new xenocara and
see if the problem goes away. I'll bet that kernel commit requires
the new X. I'll post the results in a bit.
You'll need to build at least libdrm as mentioned here:
http://www.openbsd.org/faq/current.html#20130607b
The X builds in the snapshots aren't updated as often
as the rest of the sets so it may take some time for
snapshots to catch up.
Yep, just read "following current" and did a facepalm. I'm building a
new system now. I'm sure everything will be fine.
Sorry for the noise...
--
Scott McEachern
https://www.blackstaff.ca
"Those who would give up essential liberty to purchase a little temporary safety
deserve neither liberty nor safety." -- Benjamin Franklin
