- Samsung X10 has several different versions which include either Geforce4 420GO 32M or Geforce4 440GO 64M, but whichever the version I and several others seem to have exactly the same problem: NVidia driver (version 4496-r3) installs with no problem, X starts up but with patterns of horizontal lines rather than a normal display. - When an external monitor is connected and used instead of the internal panel, the NVidia drivers work fine: very nice accelerated 3D. - XFree (nv driver) works fine on the internal panel at 1024x768. Use exactly the same config file (with nv changed to nvidia, dri commented out) with NVidia driver and get horizontal lines. So it seems that the problem is with syncing with the internal panel and the way in which the NVidia driver detects/sets it up. I have tried various different things in XF86Config: different resolutions, IgnoreEDID (it seems that the panel's EDID returns strange values), FlatPanelProperties, etc. Not a real solution: When I load the nvidia driver with "modprobe nvidia NVreg_Mobile=1 NVreg_SoftEDIDs=0" and then startx I got a readable screen with my icons inside but it is covering only the 2/3 of the DFP. By the way glx is ok and FPS are good :-). There is a large black part on the right. Switching resolution does not give anything good and messing with Scale and Dither did not too. If I load the module with NVreg_Mobile=2 I got messy X screen like usual. Reproducible: Always Steps to Reproduce: 1. emerge nvidia-kernel nvidia-glx 2. startx Actual Results: Messy X-Screen. Expected Results: A normal X-Screen. Portage 2.0.49-r13-2 (default-x86-1.4, gcc-3.2.3, glibc-2.3.2-r1, 2.6.0-test7-bk5) ================================================================= System uname: 2.6.0-test7-bk5 i686 Intel(R) Pentium(R) M processor 1300MHz Gentoo Base System version 1.4.3.10 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-march=pentium3 -O3 -pipe -fomit-frame-pointer -mfpmath=sse -mmmx -fforce-addr -funroll-loops -fprefetch-loop-arrays" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /var/qmail/control /usr/share/config /usr/kde/2/share/config /usr/kde/3/share/config /usr/X11R6/lib/X11/xkb" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="-march=pentium3 -O3 -pipe -fomit-frame-pointer -mfpmath=sse -mmmx -fforce-addr -funroll-loops -fprefetch-loop-arrays" DISTDIR="/usr/portage/distfiles" FEATURES="sandbox ccache autoaddcvs" GENTOO_MIRRORS="ftp://ftp.easynet.nl/mirror/gentoo/ http://sunsite.cnlab-switch.ch/ftp/mirror/gentoo/ http://gentoo.inode.at/ http://ftp.easynet.nl/mirror/gentoo/ ftp://gentoo.inode.at/source/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" USE="x86 oss avi crypt cups encode foomaticdb gif jpeg libg++ libwww mad mikmod mpeg ncurses nls pdflib png quicktime spell truetype xml2 xmms xv zlib alsa gdbm berkdb slang readline svga java X sdl tcpd pam ssl perl python esd imlib oggvorbis gnome gtk motif opengl mozilla cdr acpi dvd gstreamer gtk2 joystick nptl pcmcia pda plotutils pnp ppds usb xvid -apm -arts -gpm -kde -qt"
What about previous versions? What about the X11 "nv" driver?
It occures with every version from the nvidia-driver. The xfree-nv-driver works fine.
Not much we can do, as the driver core is closed source. Please report to nVidia, and reopen if a newer driver or possible patch (if one could be made without updating the core) fixes this.
