[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#618665: linux-image-2.6.32-5-686: mouse pointer not visible and crashes when playing video files



Am Samstag, den 19.03.2011, 17:52 +1030 schrieb maikkeli: 
> Renaming /etc/modprobe.d/i915.modeset.conf
> to /etc/modprobe.d/i915.modeset.conf.disabled does not disable
> modesetting, as confirmed by the output of:
> --------------------
>     # cat /sys/module/i915/parameters/modeset
> --------------------
> 
> Editing /etc/modprobe.d/i915.modeset.conf to contain the following,
> did disable modesetting:
> --------------------
>     options i915 modeset=1
> --------------------
> ..However, this simply causes the xorg intel driver to fail to load,
> falling back to vesa which works perfectly but is slow.

I just took a look what my i915.modeset.conf, and it contains exactly
the line 'options i915 modeset=1', and
'cat /sys/module/i915/parameters/modeset' yields 1 (kernel 2.6.32-31).

I changed this to 'options i915 modeset=0' and rebooted. During boot, I
noticed that the resolution (the font-size of the boot messages) is much
lower, and directly before showing the login screen there is a brief,
slightly distorted flash of the BIOS' spash-screen -- BTW, the same as
if I live-boot Linux Mint 9.

After boot, the mouse pointer was visible (still on kernel version
2.6.32-31) and I could play videos, but the playback was unusably slow.

I also tried live-booting Ubuntu 10.04 once more.
- if I boot with no parameters, the boot hangs instantly
- if I boot with 'nolapic', it boots to a black screen
- if I boot with 'nolapic' and 'i915.modeset=1', it boots to the desktop
and even has composition enabled (and thus 3D acceleration), but crashes
after a few seconds, falling back to reduced graphic settings

As a reminder, I can boot Debian with 'nolapic' and
with /sys/module/i915/parameters/modeset yielding '1', and everything
runs fine (with kernel 2.6.32-30), but no 3D acceleration.

I do not expect to get my 3D acceleration fixed here, but maybe this
information is of some relevance for fixing the bug.

Regards,
Tobias 




Reply to: