(In reply to Guillaume Millet from comment #23)
> Well, I'm lost. After adding some printk without any change, I deleted the
> module video.ko just to check if it is used... no change, the system works
> the same. On the other end, the kernel package installed video.ko and
> CONFIG_ACPI_VIDEO=m is present in /boot/config-3.13.0-031300-generic,
> doesn't it mean that video is a loadable module?
>
> Moreover, lsmod displays an entry video:
> video 19859 1 i915
> whereas $ modprobe video
> FATAL: Module video not found.
>
> Where does that video module listed by lsmod comes from?
Maybe from initrd.
>
> Could the problem be related to the bug in drm module which logs a trace in
> dmesg, starting with [drm:intel_pipe_config_compare] *ERROR* mismatch in
> gmch_pfit.lvds_border_bits (expected 32768, found 0)?
Not sure about the drm driver.
Could you just build the entire kernel tree instead of only the video module?
(In reply to Guillaume Millet from comment #23) 3.13.0- 031300- generic,
> Well, I'm lost. After adding some printk without any change, I deleted the
> module video.ko just to check if it is used... no change, the system works
> the same. On the other end, the kernel package installed video.ko and
> CONFIG_ACPI_VIDEO=m is present in /boot/config-
> doesn't it mean that video is a loadable module?
>
> Moreover, lsmod displays an entry video:
> video 19859 1 i915
> whereas $ modprobe video
> FATAL: Module video not found.
>
> Where does that video module listed by lsmod comes from?
Maybe from initrd.
> pipe_config_ compare] *ERROR* mismatch in lvds_border_ bits (expected 32768, found 0)?
> Could the problem be related to the bug in drm module which logs a trace in
> dmesg, starting with [drm:intel_
> gmch_pfit.
Not sure about the drm driver.
Could you just build the entire kernel tree instead of only the video module?