From my own tests with current unstable today, adding "video=i915" to the kernel command line suffices; the ":modeset=1" bit is not necessary. In both cases, the resolution changes before /sbin/init is started, i.e. at initrd time. So it looks like the policy specified in /etc/modprobe.d/ does propagate to the initrd.
Therefore at the moment, as far as I can tell, there are two ways to have a KMS-enabled console right from the start of the boot process, in unstable: 1. By adding "video=i915" to the kernel command line, with or without the ":modeset=1" suffix. 2. By adding "i915" and "intel_agp" to /etc/initramfs-tools/modules. IMHO, adding the kernel command line option is no worse than what we had to do before anyway to enable suitable framebuffer consoles. But of course, if a way is found to load i915 automatically at initrd/udev/whatever time, that'd be great too. Thanks, Vasilis -- Vasilis Vasaitis "A man is well or woe as he thinks himself so." -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
