>>>>> Camaleón <noela...@gmail.com> writes:
>>>>> On Mon, 25 Jul 2011 01:23:47 +0700, Ivan Shmakov wrote:
>>>>> Camaleón <noela...@gmail.com> writes:
>>>>> On Sun, 24 Jul 2011 18:23:54 +0700, Ivan Shmakov wrote:
[…]
>>>> Otherwise, fbcon works pretty much correctly for the case in
>>>> question. As per lsmod, the driver is i915.
>>> Intel KMS requires fbcon, unless this has changed recently... and
>>> for Intel cards KMS is also mandatory, so I dunno what to suggest
>>> :-)
>> What do you mean by “mandatory”? I've ran the system without both
>> the i915 module and fbcon, and had no problems with that setup so
>> far. In particular, X works correctly.
> I remember a problem with intel driver
The kernel's, or the X.org's one?
> and fbcon not being loaded that caused X to crash, but maybe this has
> already been corrected.
To state it explicitly: I haven't tested X with kernel's i915
and without fbcon — only X without /either/ of i915 and fbcon.
I hope to check whether the respective kernel modules can be
“blacklisted” via modprobe.conf(5) shortly.
--cut: /etc/modprobe.d/blacklist --
# This file lists modules which will not be loaded as the result of
# alias expansion, with the purpose of preventing the hotplug subsystem
# to load them. It does not affect autoloading of modules by the kernel.
# This file is provided by the udev package.
--cut: /etc/modprobe.d/blacklist --
(But I still wonder, is this the hotplug subsystem that loads
the modules in question, or is it the kernel?)
--
FSF associate member #7257
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/86pqkwpbcc....@gray.siamics.net
