This problem might be one for the Xfree86 developer's list. Turning off the
framebuffers worked for me, since it didn't for you then I am at a loss.
Glen
On Saturday 05 May 2001 18:46, you wrote:
> Well, I recompiled the kernel, and did not enable framebuffer device
> support... Still having the same problem. Could anyone help out with
> switching to XFree86 3.3.6? Will I just have to install it from scratch, or
> is there some setting to switch it, as I think it is installed. Thanks,
>
> Doug
>
> On Tuesday 01 May 2001 21:52, you wrote:
> > FBDev is your framebuffer device. You don't need it for X, and that's
> > what is hurting the console. You are likely using a stock kernel that
> > came with your distro, so I strongly urge you to try compiling it
> > yourself -- it's not hard at all. Basically you just issue these
> > commands:
> >
> > make config (menuconfig or xconfig -- I like menuconfig but most of SLUG
> > seems to like xconfig; I find it a little confusing with all of the
> > options in front of me all at once and config by itself is tedious). This
> > is where you disallow the framebuffer driver. If you select 'prompt for
> > incomplete or experimental option' (or however it's worded), it'll give
> > you the option to use the framebuffers or not to.
> >
> > pick all of the options you need. There's help on almost all of them,
> > type a '?' to get info on any you have questions with.
> >
> > make dep clean bzImage modules modules_install
> >
> > 'Nuff said here, you can even put this all on one line and wait for it
> > to finish.
> >
> > Next, copy the System.map file and arch/i386/boot/bzImage to /boot, and
> > don't forget to modify /etc/lilo.conf. When editing lilo.conf, just copy
> > one of the image sections you already have and make the image= line say
> >
> > image=/boot/<insert kernel file name here>
> >
> > then give it a name under label= and re-run lilo at the prompt. It
> > should list your new label, and you're ready to boot to it. Never delete
> > the other images, tho, until you are *positive* this one works. Read the
> > linux-kernel-HOWTO on this for more details, or ask someone on this list
> > to email theirs or ask for more info. Also, go to www.linuxdoc.org for
> > current HOWTOs on everything.
> >
> > This is, of course, in case the framebuffer is the problem. If anyone
> > else has more info or corrections, please be mean to me.
> >
> > Glen
> >
> > On Tuesday 01 May 2001 21:21, you wrote:
> > > Glen,
> > >
> > > Thanks for the info. I tried your XF86Config file (much cleaner than
> > > mine!!!), and same problem. I looked through mine, and couldn't find
> > > any reference to FBDev, which is what I suppose is the suspect. Should
> > > I try to use the FBDev, or would it just create more havoc?
> > > Also, can anyone explain why there are two related directories for X?
> > > One in /etc/X11, and one in usr/X11R6/lib/X11 (with many links pointing
> > > to the /etc/X11 directory).
> > >
> > > Thanks,
> > >
> > > Doug
> > >
> > > On Monday 30 April 2001 19:32, you wrote:
> > > > Sounds like you are using the framebuffer driver in the kernel. This
> > > > is bad, as those things tend to get flakey with X and vice versa.
> > > > When X is running, it'll screw up the console display and sometimes
> > > > they won't fix after X is killed. I follow Paul Foster's credo
> > > > concerning framebuffer drivers: don't use them. I have a voodoo3 3000
> > > > (same chipset as the banshee), and it works great. (I've ogl
> > > > framerates OVER 240fps in tests).
> > > >
> > > > I put my XF86Config file at http://members.acer-access.com/gurensan.
> > > > I've changed monitors since then, but this file should drop right in.
> > > >
> > > > Glen
> > > >
> > > > On Sunday 29 April 2001 22:45, you wrote:
> > > > > Hello,
> > > > >
> > > > > I have a Diamond Monster Fusion Video card (VooDoo Banshee
> > > > > chip) and a Phillips 107S monitor. I have tried getting
> > > > > XFree86 4.0.3 to work in both Redhat 7.1 and Mandrake 8.0
> > > > > clean installs with the same results in both. Both the card
> > > > > and the monitor are found correctly by the install. However,
> > > > > when I try to startx, things get weird (using KDE). Hard to
> > > > > explain exactly, but here goes: X starts, but everything is
> > > > > extremely grainy, the background, icons, everything. The
> > > > > cursor looks like a fuzzy rectangle. The K menu is about
> > > > > 1/8" wide, and all icons in it (and on the desktop) are
> > > > > unreadable. I use the cntrl-alt-backspace to get back to a
> > > > > command prompt, and I think it does... but the screen is now
> > > > > a jumble of many colors. Pressing alt+F2 through alt+F6
> > > > > reveals that all terminals look the same way. But commands
> > > > > are accepted... So, I use cntrl-alt-del to reboot.
> > > > > I have tried Xconfigurator, and I have manually edited the
> > > > > XF86Config file, and even tried the xfree86config (sp?)
> > > > > tool, all to no avail. Thanks for any help!
> > > > >
> > > > >
> > > > > Douglas W Koobs MCSE
> > > > > Network Engineer
> > > > > Dimension Networks, Inc
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 20:16:07 EDT