Re: questions re updating to -CURRENT

2017-09-12 Thread Jakub Lach
> Maybe ... but this is one of those things that (in my > experience) either Just Work or Go Horribly Wrong. That's why I would go at least (latest) -RELEASE to -STABLE before going -STABLE to -CURRENT, if you must. Why trying your luck with big jumps? -- Sent from:

Re: questions re updating to -CURRENT

2017-09-10 Thread owner-freebsd-current
Jakub Lach writes: > Are you sure you are not using drm2 already? I would check > with kldstat. Ckecked; it's there. > The message in UPDATING is about removing > old code from the tree. Maybe ... but this is one of those things that (in my experience) either Just Work or

Re: questions re updating to -CURRENT

2017-09-08 Thread Jakub Lach
I use 11-STABLE with Intel. Some time ago, there was a switch to drm2 here. Iirc I had to add kld_list="i915kms.ko to rc.conf and ensure that drm2/drm2 and drm2/i915kms are built (which should be default). Are you sure you are not using drm2 already? I would check with kldstat. The message in

questions re updating to -CURRENT

2017-08-29 Thread owner-freebsd-current
Hello: I finally get to update a system from: FreeBSD 11.0-RC2 #0 r304729: Wed Aug 24 06:59:03 UTC 2016 amd64 to -CURRENT. After reading src/UPDATING, I understand everything (I think) _except_: 20170311: The old drm (sys/dev/drm/) drivers for i915 and radeon