On 2012-10-21 04:48, Jonathan Nieder wrote:
Per Foreby wrote:Next thing to try is to blacklist the i915 module, but it doesn't seem to work. This is what I did: # echo "blacklist i915" > /etc/modprobe.d/i915-blacklist.conf # depmod -ae -F /boot/System.map-3.2.0-3-amd64 # update-initramfs -u -k all Module still loads.Does the i915 module still load if you boot in recovery mode (kernel 'single' or 'text')? If so, please attach lsmod output and output from "grep . /etc/modprobe.d/*".
The module was not loaded in recovery, and when booting multiuser, lsmod shows no dependencies.
I did however find a working solution in the Arch wiki (https://wiki.archlinux.org/index.php/Kernel_modules#Using_files_in_.2Fetc.2Fmodprobe.d.2F_2). So using "install i915 /bin/false" in blacklist.conf, the i915 module is finally gone.
The output from lspci/dmsg/Xorg.0.log is still identical and indicates 256 MB, but the Vesa driver also added this to Xorg.0.log:
[ 22.177] (II) VESA(0): Total Memory: 1023 64KB banks (65472kB) [ 22.200] (II) VESA(0): VESA VBE Total Mem: 65472 kBNote that this is 1023 memory banks, not 1024, so it's not exactly 64 MB (65536 kB). Maybe the reason why it almost works with 256 MB is that the kernel always thinks that we have exactly 256 MB but the Mobo supplies one memory bank less. Just a theory..
/Per