Hi, On Sun, Jul 29, 2012 at 12:12:01PM +0700, Erich Dollansky wrote: > On Sat, 28 Jul 2012 21:49:18 -0700 > Kevin Oberman <kob6558_at_gmail.com> wrote: > > > You are working too hard from old information. Do not attempt to load > > i915kms.ko. Do not attempt to load drm2.ko. For the past months the > > drivers have been fixed to automatically load all needed drivers and > > kernel modules when Xorg is started. My Sandybridge behaves just like > > How do the wrong modules get loaded? Thanks for all the help guys. The problem was the result of my own stupidity. I went through some code trying to find out why the wrong modules were loaded, and I discovered that I previously commented out this line in x11-drivers/xf86-video-intel/Makefile: EXTRA_PATCHES+= ${PATCHDIR}/extra-i915kms This patch is for -CURRENT since the name of the module changed when kib_at_ imported the code to -CURRENT: - intel->drmSubFD = drmOpen("i915", busid); + intel->drmSubFD = drmOpen("i915kms", busid); Since I built -CURRENT from around 3 months ago and an up-to-date ports tree, I had to remove this patch to make it work. So it fell apart when I tried to upgrade to the lastest -CURRENT... Apparently portsnap doesn't overwrite local modifications to the ports tree unless there are updates (unlike csup), so the patch wasn't included until I discovered my mistake. Next time I'll keep a list of local changes for my ports tree, so I don't shoot myself in the foot again. Sorry for the noise. -- Denny LinReceived on Sun Jul 29 2012 - 05:21:39 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:29 UTC