Re: Unable to load i915kms
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 kob6...@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@ 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 Lin
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Unable to load i915kms
Hi,
On Sun, 29 Jul 2012 15:21:36 +0800
Denny Lin dennyli...@hs.ntnu.edu.tw wrote:
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
so, wrong name -- wrong modules. This simple.
Erich
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Unable to load i915kms
Hi, I updated to r238858 yesterday, but I was unable to load i915kms (I tried loading it manually and putting it in /boot/loader.conf). The computer becomes unresponsive and the screen turns black in either case. I'm using the GENERIC kernel with WITNESS and INVARIANTS disabled. Output of pciconf -lvb: vgapci1@pci0:0:2:0: class=0x03 card=0x15f21043 chip=0x01168086 rev=0x09 hdr=0x00 vendor = 'Intel Corporation' device = '2nd Generation Core Processor Family Integrated Graphics Controller' class = display subclass = VGA bar [10] = type Memory, range 64, base 0xdd40, size 4194304, enabled bar [18] = type Prefetchable Memory, range 64, base 0xb000, size 268435456, enabled bar [20] = type I/O Port, range 32, base 0xe000, size 64, enabled Modules loaded at boot: Id Refs AddressSize Name 1 38 0x8020 12c57f0 kernel 21 0x814c6000 70a8 acpi_video.ko 31 0x814ce000 6568 cuse4bsd.ko 41 0x81612000 cea0 geom_eli.ko 51 0x8161f000 1abc1crypto.ko 61 0x8163a000 a4f9 zlib.ko 71 0x81645000 15e2 fdescfs.ko 81 0x81647000 3daf linprocfs.ko 91 0x8164b000 1eeb2linux.ko 101 0x8166a000 2393 ums.ko 111 0x8166d000 17d3 uhid.ko 121 0x8166f000 a9f3 fuse.ko 131 0x8167a000 7019 i915.ko 141 0x81682000 111c4drm.ko I have WITH_KMS=YES and WITH_NEW_XORG=YES in /etc/make.conf. I also rebuilt xorg-* and xf86-video-intel after updating to r238858. Xorg previously worked on my laptop with all.14.3.patch on top of -CURRENT from around mid-April, so I'm not sure what went wrong. -- Denny Lin ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Unable to load i915kms
Hi, On Sun, 29 Jul 2012 09:53:50 +0800 Denny Lin dennyli...@hs.ntnu.edu.tw wrote: I updated to r238858 yesterday, but I was unable to load i915kms (I tried loading it manually and putting it in /boot/loader.conf). The computer becomes unresponsive and the screen turns black in either case. I'm using the GENERIC kernel with WITNESS and INVARIANTS disabled. Output of pciconf -lvb: vgapci1@pci0:0:2:0: class=0x03 card=0x15f21043 chip=0x01168086 rev=0x09 hdr=0x00 vendor = 'Intel Corporation' device = '2nd Generation Core Processor Family Integrated Graphics Controller' class = display subclass = VGA bar [10] = type Memory, range 64, base 0xdd40, size 4194304, enabled bar [18] = type Prefetchable Memory, range 64, base 0xb000, size 268435456, enabled bar [20] = type I/O Port, range 32, base 0xe000, size 64, enabled Modules loaded at boot: Id Refs AddressSize Name 1 38 0x8020 12c57f0 kernel 21 0x814c6000 70a8 acpi_video.ko 31 0x814ce000 6568 cuse4bsd.ko 41 0x81612000 cea0 geom_eli.ko 51 0x8161f000 1abc1crypto.ko 61 0x8163a000 a4f9 zlib.ko 71 0x81645000 15e2 fdescfs.ko 81 0x81647000 3daf linprocfs.ko 91 0x8164b000 1eeb2linux.ko 101 0x8166a000 2393 ums.ko 111 0x8166d000 17d3 uhid.ko 121 0x8166f000 a9f3 fuse.ko this seems to be wrong: 131 0x8167a000 7019 i915.ko 141 0x81682000 111c4drm.ko From my machine: 21 0x817e4000 aee0 sem.ko 31 0x81a12000 9db3 linprocfs.ko 41 0x81a1c000 587a5linux.ko 51 0x81a75000 3900 ums.ko 61 0x81a79000 2b0d uhid.ko 71 0x81a7c000 1b7a1ng_btsocket.ko 81 0x81a98000 ba58 netgraph.ko 91 0x81aa4000 118b ng_bluetooth.ko 101 0x81aa6000 a9f3 fuse.ko 111 0x81ab1000 69298i915kms.ko 121 0x81b1b000 1ba2 iicbb.ko 134 0x81b1d000 1ddb iicbus.ko 141 0x81b1f000 1cd5 iic.ko 151 0x81b21000 32386drm2.ko 161 0x81b54000 241 acpi_call.ko So, why did drm.ko and i915.ko make it into your kernel? I have WITH_KMS=YES and WITH_NEW_XORG=YES in /etc/make.conf. I also rebuilt xorg-* and xf86-video-intel after updating to r238858. Xorg previously worked on my laptop with all.14.3.patch on top of -CURRENT from around mid-April, so I'm not sure what went wrong. I did not touch this machine since 16.07.12. Maybe your patches affected something. Can you download a fresh source tree? Erich ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Unable to load i915kms
On Sun, Jul 29, 2012 at 10:59:54AM +0700, Erich Dollansky wrote: this seems to be wrong: 131 0x8167a000 7019 i915.ko 141 0x81682000 111c4drm.ko From my machine: 21 0x817e4000 aee0 sem.ko 31 0x81a12000 9db3 linprocfs.ko 41 0x81a1c000 587a5linux.ko 51 0x81a75000 3900 ums.ko 61 0x81a79000 2b0d uhid.ko 71 0x81a7c000 1b7a1ng_btsocket.ko 81 0x81a98000 ba58 netgraph.ko 91 0x81aa4000 118b ng_bluetooth.ko 101 0x81aa6000 a9f3 fuse.ko 111 0x81ab1000 69298i915kms.ko 121 0x81b1b000 1ba2 iicbb.ko 134 0x81b1d000 1ddb iicbus.ko 141 0x81b1f000 1cd5 iic.ko 151 0x81b21000 32386drm2.ko 161 0x81b54000 241 acpi_call.ko So, why did drm.ko and i915.ko make it into your kernel? Both are built by default, but only drm.ko and i915.ko are loaded automatically. i915kms.ko has to loaded manually: http://lists.freebsd.org/pipermail/freebsd-x11/2012-May/011857.html I do have i915kms and drm2.ko, but every time I try to load i915kms.ko, the computer blacks out. I have WITH_KMS=YES and WITH_NEW_XORG=YES in /etc/make.conf. I also rebuilt xorg-* and xf86-video-intel after updating to r238858. Xorg previously worked on my laptop with all.14.3.patch on top of -CURRENT from around mid-April, so I'm not sure what went wrong. I did not touch this machine since 16.07.12. Maybe your patches affected something. Can you download a fresh source tree? I used a new checkout when I updated to r238858, so this shouldn't be a problem. -- Denny Lin ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Unable to load i915kms
On Sat, Jul 28, 2012 at 9:20 PM, Denny Lin dennyli...@hs.ntnu.edu.tw wrote: On Sun, Jul 29, 2012 at 10:59:54AM +0700, Erich Dollansky wrote: this seems to be wrong: 131 0x8167a000 7019 i915.ko 141 0x81682000 111c4drm.ko From my machine: 21 0x817e4000 aee0 sem.ko 31 0x81a12000 9db3 linprocfs.ko 41 0x81a1c000 587a5linux.ko 51 0x81a75000 3900 ums.ko 61 0x81a79000 2b0d uhid.ko 71 0x81a7c000 1b7a1ng_btsocket.ko 81 0x81a98000 ba58 netgraph.ko 91 0x81aa4000 118b ng_bluetooth.ko 101 0x81aa6000 a9f3 fuse.ko 111 0x81ab1000 69298i915kms.ko 121 0x81b1b000 1ba2 iicbb.ko 134 0x81b1d000 1ddb iicbus.ko 141 0x81b1f000 1cd5 iic.ko 151 0x81b21000 32386drm2.ko 161 0x81b54000 241 acpi_call.ko So, why did drm.ko and i915.ko make it into your kernel? Both are built by default, but only drm.ko and i915.ko are loaded automatically. i915kms.ko has to loaded manually: http://lists.freebsd.org/pipermail/freebsd-x11/2012-May/011857.html I do have i915kms and drm2.ko, but every time I try to load i915kms.ko, the computer blacks out. I have WITH_KMS=YES and WITH_NEW_XORG=YES in /etc/make.conf. I also rebuilt xorg-* and xf86-video-intel after updating to r238858. Xorg previously worked on my laptop with all.14.3.patch on top of -CURRENT from around mid-April, so I'm not sure what went wrong. I did not touch this machine since 16.07.12. Maybe your patches affected something. Can you download a fresh source tree? I used a new checkout when I updated to r238858, so this shouldn't be a problem. 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 your system if I try to manually load i915kms.ko. Screen goes black and that is the end. Oh, and you didn't mention libdrm. It should be built with WITH_KMS, too. -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Unable to load i915kms
Hi, On Sun, 29 Jul 2012 12:20:13 +0800 Denny Lin dennyli...@hs.ntnu.edu.tw wrote: On Sun, Jul 29, 2012 at 10:59:54AM +0700, Erich Dollansky wrote: this seems to be wrong: 131 0x8167a000 7019 i915.ko 141 0x81682000 111c4drm.ko From my machine: 21 0x817e4000 aee0 sem.ko 31 0x81a12000 9db3 linprocfs.ko 41 0x81a1c000 587a5linux.ko 51 0x81a75000 3900 ums.ko 61 0x81a79000 2b0d uhid.ko 71 0x81a7c000 1b7a1ng_btsocket.ko 81 0x81a98000 ba58 netgraph.ko 91 0x81aa4000 118b ng_bluetooth.ko 101 0x81aa6000 a9f3 fuse.ko 111 0x81ab1000 69298i915kms.ko 121 0x81b1b000 1ba2 iicbb.ko 134 0x81b1d000 1ddb iicbus.ko 141 0x81b1f000 1cd5 iic.ko 151 0x81b21000 32386drm2.ko 161 0x81b54000 241 acpi_call.ko So, why did drm.ko and i915.ko make it into your kernel? Both are built by default, but only drm.ko and i915.ko are loaded automatically. i915kms.ko has to loaded manually: http://lists.freebsd.org/pipermail/freebsd-x11/2012-May/011857.html ok, try to use my script: http://www.alogreentechnologies.com/freebsd/XonX220 I do not know what this script will do when drm and i915 are already loaded. I do have i915kms and drm2.ko, but every time I try to load i915kms.ko, the computer blacks out. The black screen is normal if you do not start X. I have WITH_KMS=YES and WITH_NEW_XORG=YES in /etc/make.conf. I also rebuilt xorg-* and xf86-video-intel after updating to r238858. Xorg previously worked on my laptop with all.14.3.patch on top of -CURRENT from around mid-April, so I'm not sure what went wrong. I did not touch this machine since 16.07.12. Maybe your patches affected something. Can you download a fresh source tree? I used a new checkout when I updated to r238858, so this shouldn't be a problem. It could be that the two loaded modules cause the problem. Erich ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Unable to load i915kms
Hi, On Sat, 28 Jul 2012 21:49:18 -0700 Kevin Oberman kob6...@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? your system if I try to manually load i915kms.ko. Screen goes black and that is the end. It still works for me. You know, never change a winning team. There seem to be small differences between the CPU/GPUs. Erich ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
