On Mon, Oct 19, 2009 at 3:02 PM, Brice Goglin <[email protected]>wrote:
> Thomas Hahn wrote: > > > > > > On Mon, Oct 19, 2009 at 12:32 PM, Brice Goglin > > <[email protected] <mailto:[email protected]>> wrote: > > > > Thomas Hahn wrote: > > > Sigh, after upgrading I am having the same problem. > > > On the build in screen of the laptop the mouse cursor is > > visible, but > > > on the bigger TFT it has disappeared. > > > > > > # CONFIG_DRM_I915_KMS is not set > > > > > > So, I need to build my own kernel? > > > > > > Anything else necessary to get KMS working? > > > > You can enable KMS with your current kernel by passing modeset=1 > > to the > > i915 module at startup, either through the initramfs config or on the > > kernel command line. > > > > Brice > > > > > > Tnx for the info. > > I have changed the command line via /boot/grub/menu.lst to > > Kernel command line: root=/dev/sda5 ro vga=0x0361 resume=/dev/sda8 > > modeset=1 > > If using a plain Debian kernel, see > http://wiki.debian.org/KernelModesetting > > Brice > Been there tried that, got: (**) intel(0): Kernel mode setting active, disabling FBC. BUT: (II) intel(0): EDID for output LVDS1 (II) intel(0): Manufacturer: LPL Model: 0 Serial#: 0 (II) intel(0): Year: 2004 Week: 0 (II) intel(0): EDID Version: 1.2 (II) intel(0): Digital Display Input (II) intel(0): Max Image Size [cm]: horiz.: 33 vert.: 21 (II) intel(0): Gamma: 2.20 (II) intel(0): No DPMS capabilities specified (II) intel(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4 (II) intel(0): First detailed timing is preferred mode (II) intel(0): redX: 0.590 redY: 0.344 greenX: 0.323 greenY: 0.534 (II) intel(0): blueX: 0.156 blueY: 0.138 whiteX: 0.312 whiteY: 0.328 (II) intel(0): Manufacturer's mask: 0 (II) intel(0): Supported detailed timing: (II) intel(0): clock: 71.2 MHz Image Size: 289 x 21 mm See those 21 mm, should have been 210mm! So letters are absolutely HUGE and render this useless. There is some Section "Monitor" Identifier "LVDS" DisplaySize 330 206 HorizSync 30-90 VertRefresh 50-60 EndSection in the xorg.conf as this must have been a problem sometime before, but it doesnt help now ... Thomas
