well, i guess im forced to use redhat 9. i tried installing XIG on suse 9, slackware 9.1, mandrake 9.0/9.1/9.2, and redhat 9 is the only one to work.

i got 1024x768 now, but i dont know how to enter a serial number. how do i enter in a serial number? the area in XSetup where is asks for it wont allow me to edit the extsting one there (the demo one).

also, its crashing a lot and freezing my whole system, forcing me to reboot. i dont knw if this is the demo, of if its because i havent entered the serial.

ive got it working now with xig, Xsummit LX edition. my current setup is on suse 9.1.

so far, the XiG commercial xserver doesnt work on ANY debain distro ive tried, only redhat distros, but slackware seems to work fine using the RPM command, not rpm2tgz.

im still continuing to check out the linux community to see if this chipset is supported, and im finding that there are in fact people in the debian community to fix this problem. ill post back later with more results.

So, I've been following up this problem, still. Google searching every now and then for hope that something will come along and replace the commercial drivers.

I have gotten this to work on other distros besides RedHat based. But there's a few tricks.

On gentoo: It's easiest just to emerge the RPM program, and simple rpm -uvh --nodeps" the xig package. Simple as that, build in the xsvc kernel module, and continute to the very last step in this thread.

On debian: It's as simple as using alien to convert the RPM to deb. After that, just do the last step in this thread.

Slackware: rpmtgz to convert it as well.

Ubuntu: Im going to be more detailed here, as ubuntu is gaining popularity. Some distros will make you rebuild your kernel because they dont include the kernel headers anywhere, leaving you dead to build your own kernel. In ubuntu, all you have to do is apt-get the following: build-essential, linux-headers-[kernel version here], gcc and that's it. Build xsvc and you're good to go.

For the *LAST STEP*
Assuming you've sucessfully installed the xsvc module, and the Summit Desktop package, this last step should be a breeze. When you install the desktop package, it doesnt fully install, for some reason. It doesnt replace the X binary with the Xaccel binary. So you have to manually, as root, go into /usr/X11R6/bin and "mv X X.bak" to make a backup of the X binary file. Then "cp Xaccel X" to make a copy of Xaccel as X. All this while still under /usr/X11R6/bin

Run Xsetup as the xig instructions say to, and setup the Xig xserver. Now upon bootup, ive run into some problems. your xig server may not start. this is due to xsvc not being modprobed. you can always manually (as root) do "modprobe xsvc" every time, or you can have linux autorun "modprobe xsvc" at every bootup.

On gentoo, just use the drivers that are you can get with emerge.
No need to use RPM.
If you have a new chipset (965GM/G/... maybe others too) do
echo "xf86-video-intel ~x86" >> /etc/portage/package.keywords
and then emerge it
emerge -av xf86-video-intel

For older drivers just emerge xf86-video-i810


Anyone an idea how to get the 965 working on OpenSuse?

I hesitate to bring up this old thread, but in case anyone is installing Linux on this laptop (Gateway M305CRV), Xorg now is able to provide the 1024x768 resolution. I don't know when or how it happened, but I'm glad. I tried 3 distros (Kubuntu 7.10, Fedora Core 8, and Gentoo) on this laptop, and all 3 were able to go into 1024x768 with no special setup. I ended up with Gentoo, just because it was the last one I tried. I don't know if I'd recommend it though, as the CPU gets crazy hot during those marathon compile sessions. I got a big Lasko fan and pointed it at the exhaust fan just to keep the temp in the 50's C. Of the other two, I liked Fedora Core 8 better... it had some flaky errors during the install and took forever to install to the hard drive, but it booted about 30 seconds faster than Kubuntu, which took over 2 minutes for some reason. It also provides a KDE setup closer to the default, while Kubuntu installs some other stuff. Of course, Gentoo is better in both these respects.

Don't hesitate to bring up old threads There's actually solutions now that are free. I'm sure many people will be glad.

yeah, the driver actually became officially supported around the time ubuntu Gutsy came out. At the time, x.org started using the bulletproof x I think that may have something to do with it) Currently, all new linux distros work with this laptop now. I've tried a number if distros (vector, zenwalk, gentoo, sabayon) and they all work with no problem.

So I guess this could be officially closed. Problem has been solved.

ACPI is probably a BIOS issue.

Use the i810 driver in X.org. You already have it. I've done 1280x1024 with it. The i810 is strange in that the video memory is just a region of main memory. No separate video RAM. The region's size is set by BIOS. If it is set too small, then that's your problem. Your 1024x768 is on the order of one million pixels. That takes 24 MB at 24 bits/pixel. Look in your BIOS for the setting for video memory size. Try setting it to at least 64 MB. Or try 16-bit or 8-bit color depth.

X.org's "vesa" driver just uses the CPU to twiddle bits instead of telling the graphics hardware to do it. It won't have any effect on how much memory is available for display.

If you don't know how to edit /etc/X11/xorg.conf to alter the display modes available, you probably shouldn't go looking for video drivers outside your distribution. Installing from source or even tarballs from outside your distro often involves interpolating poorly written instructions. They'll skip steps or overlook dependencies, or you'll get such bad grammar that a sentence just doesn't make any sense. Document interpolation's a vital skill that software professionals develop over time, but newbies don't have it yet. The i810 driver in your distro will do what you want. Looking for another driver is a rat hole.

I have had one problem with several different i810 motherboards. We get a rendering error in the title bar of a window in KDE. I've never seen it happen anywhere else. The title bar background pattern is interrupted with rectangles of a different pattern, as if it's blitting from the wrong place. I've never seen it affect the application inside the window. Must be some drawing operation that only KDE does.