On Thu, 16 Jan 2003, Greg Julius wrote: > I first tried to install the XFree86 via the cvs. Got things all tied in a > knot and re-installed.
Did you get the 4.2.99 snapshot or the newest code? (all versions of files in the snapshot are tagged -- if you don't specify that tag when you check out the source you will get the newest version of all the files which is NOT what you want. Yes, I think there should have been a tarball, too :/ ) The build system for XFree86 is also not too nice. > Later found binaries. I am worried about them > because they are for gcc 2.something and I've got gcc 3.2 and figure they > may be a portion of my problem. Mebe not, but with the way things have Don't think it is. > I look into my .config file and I find CONFIG_FB_VESA=y so I guess that > means I already have it. It looks that way, yes :) > Will change to y. Can I change any of the below to n? Clearly I can't > make the 830=y because I have to replace it with the XFree86 version. I > think I need the 810 stuff, but what about the other stuff? I think you need CONFIG_AGP_I810 but not the other CONFIG_AGP_xxx's. > > > CONFIG_AGP_INTEL=y > > > CONFIG_AGP_I810=y > > > CONFIG_AGP_VIA=y > > > CONFIG_AGP_AMD=y > > > # CONFIG_AGP_AMD_8151 is not set > > > CONFIG_AGP_SIS=y > > > CONFIG_AGP_ALI=y > > > CONFIG_AGPSWORKS=y > > > CONFIG_DRM=y > > > # CONFIG_DRM_OLD is not set > > > > > > # > > > # DRM 4.1 drivers > > > # > > > CONFIG_DRM_NEW=y > > > CONFIG_DRM_TDFX=m > > > CONFIG_DRM_R128=m > > > CONFIG_DRM_RADEON=m > > > CONFIG_DRM_I810=m > > > # CONFIG_DRM_I810_XFREE_41 is not set > > > CONFIG_DRM_I830=m and you can turn this off and build the module with the XFree86. When you build modules outside of a kernel source tree, you must make sure the include files the compiler finds will be the right ones. Sometimes the makefile has a define you can set to where your kernel headers are, sometimes you have to make sure that /usr/include/linux points to the right place. > >Looks as if you build the right type of module with the kernel, but Dawes > >writes that you need the module from the DRI or XFree86 source instead of > >from the kernel source. > > Is this stuff likely to make it into a kernel.org kernel sometime in the > not to distant future? (Not that I'm going to wait). Yes. > From another note: > >or rather: doesn't /quite/ answer it. The support.html has a link to > >Dawes' page that explains how to make the 4.2.99 snapshot work but it's > >not easy to do (witness the problems Greg Julius are having). > > The the first of the big problems was that RH 8 comes with gcc 3.2 and the I think it also comes with an older version under the name of kgcc (for kernel gcc). > To find David's page I googled around, came through the intel site and > found it. There are a lot of us newbies out there with newish sort of > hardware For now the best advice is to NOT buy the newest hardware if it is weird AND to pester the people you bought the hardware from (Intel, in this case). It is most likely their fault if there aren't Linux drivers yet. > and the XFree86 site is hard to use. You might say that again! > The search feature needs to > be more visible. I only discovered it late last night (it didn't use to be there, I think -- how many months has it been there? I have been almost completely away from my computer for four months...) There was a guy who had redesigned the DRI site with great success back in the summer -- he thought a bit about how to fix the XFree86 site but I think the internal opposition/inertia was too much for him. I think Georgina Economou is/was in charge of the website and if so I can certainly understand why he didn't want to continue the struggle :( > It might help if they made the i830.o DRM module in a few flavors that > people could download. Yeah, but they shouldn't. You either buy hardware that is supported or you compile some stuff yourself -- or pay others to fix it for you. You don't want the general progress hampered too much by having to cater to every and all newbie. > This may not be possible as a .o, but surely there > is something less formidable than extracting the whole cvs branch (took all > day on my DSL link) just to get a useable i830.o module. A tarball for a prerelease, though, that is different. You can't expect everybody to both be able to read installation instructions AND handle a compiler AND handle cvs ;) > Thanks for the help so far. You are welcome :) -Peter PS: I think that even after all the above has been sorted out that you might need to talk to Dawes to get a small fix in regarding the BIOS version that your video "card" has. _______________________________________________ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
