On Thu, 16 Jan 2003, Greg Julius wrote: > >Where did you get it? Compile from source or a binary package from > >somewhere? Did you get the DRI module, too? > > The 2.4.20 kernel I got from Linux.org - compiled from source with gcc 3.2
kernel.org? what .config? (did you select anything AGP related?) > The 4.2.99.3 XFree I got from XFree86.org as a binary. I have also brought > the cvs tree for 4.2.99.3 down yesterday so I have the source. I haven't as > yet figured out how to build XFree86 and all of its parts from the source. > > Did I get the DRI module? How would I know? What should it have been > in. I didn't download anything specific. >From http://www.xfree86.org/~dawes/845driver.html : In addition to building/installing XFree86 CVS code, a recent 2.4.x kernel is needed. 2.4.19 or later is recommended. If you want to use the DRI support, an updated i830 DRM module is also required, and it is best to build one from either the XFree86 or DRI source tree. To do this you will also need your kernel source installed. Here is an example of how to build and load the new i830 DRM module: # cd xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel # make -f Makefile.linux i830.o # modprobe agpgart # rmmod i830 # insmod i830.o Here is an example of how to install the new i830 DRM module so that it will be loaded automatically when needed: # mv /lib/module/`uname -r`/kernel/drivers/char/drm/i830.o \ /lib/module/`uname -r`/kernel/drivers/char/drm/i830.o.save # cp i830.o /lib/module/`uname -r`/kernel/drivers/char/drm [end] > > > >What does lsmod tell you before you run startx? > > I have put some stuff up on my website: > lsmod: http://www.outtacyte.com/outtacyte/ref/lsmodlist > XFree86.0.log: http://www.outtacyte.com/outtacyte/ref/XFree86-log > XF86Config: http://www.outtacyte.com/outtacyte/ref/XF86Config > > The config file comes from XFree86 -configure and I've only changed the > driver from i810 to vesa. Thanks. See if you can change it back after recompiling the kernel with vesafb. > > >About the weird blanking when switching between virtual consoles > >(Ctrl-Alt-Fn), have you tried the vesafb ? (easier to do if you compile > >the kernel from source, I think) > > what is vesafb? Is this a driver? What would I do to try it out? in the kernel source tree: make menuconfig and find the right option. Then make dep bzImage modules followed by make install modules_install as root -- just your standard kernel compile. The vesafb is another way of handling the "text-mode" console. It actually doesn't have to run in text mode, even for text output. vesafb keeps the video card in graphics mode all the time. It was suggested in Dawes' document: "Lots of people have reported problems related to VT switching with the 830M. Feedback from the "9 December" update indicates that most of these problems are now fixed, but that a few less-frequent problems still remain. If you are seeing this type of problem, please send me details, including a log file (/var/log/XFree86.0.log) and your laptop brand and model, and BIOS revision. If you saw this problem with the previous version, and don't see it after the "9 December" update, please also drop me a note. I've had a report that (on Linux) if you use the vesafb console instead of the default text-mode console, the VT switching problem can be avoided. As Calum Mackay suggested, this is a good workaround if you're being bitten by this problem (and if the "9 December" update doesn't fix it)." > I have the following AGP/DRM > CONFIG_AGP=m Load the module before you start X or change to y and recompile. It might work. > 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 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. -Peter _______________________________________________ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
