Richard Dice wrote: > > Can't you try with 2.2.17 again? > [and] > > Did you by chance enable the New Input Layer in the 2.2.18 kernel? > > This is somewhat moot -- before receiving your email, I had created > yet-another 2.2.18 kernel and installed it, and now the mouse is working > fine. > > Still, I was/am curious, so I checked my new .config file, and I > couldn't see an option in there that seemed to correspond to the > New Input Layer. I tried poking around by a few other means to > (checking out the help docs on the various config options, rgrep > "New Input Layer") and still didn't see it.
grep INPUT .config should show you the options related to the new input layer. > It's very important for me to be able to have simultaneous display. > I do a lot of teaching, training and speaking at conferences, and I'd > _much_ rather be able to project Linux onto the big screen than > Windoze. :-) [My hardware is fine -- I can get simultaneous display > working without a hitch on my Win98 boot.] > > I just tried it with the ati driver as well, and it doesn't seem to be > able to handle simultaneous displays, either. Is there a driver that > does? No. The former r128 driver has been merged into the ati driver. There's no other driver which has knowledge about your graphics chip. > If I have to buy a new video card for my laptop in able to get > this feature, then I will. If you could exchange it... > (If I have to switch to a non-free X server, then I will do this, too, > though I'd prefer to just get a new video card, even if the price is higher > this way.) A commercial X server might be a solution, don't know. > One minor problem: When I leave X and go back to text tty & console, > my laptop screen is a _lot_ dimmer than it was before. Might this > be a function of using the new ati driver? (I didn't notice this when > I was using the r128 driver.) Not likely, as it's basically the same driver. BTW setterm or some other tool might help making the console lighter. > Regarding the original problem with the r128 driver provided in the 4.0.2 > debs and its unresolved symbols, might this be fixed if I just "apt-get > source xfree86-xserver" and compile this on my own machine? (Just a > thought.) Very unlikely. BTW I wonder what the pattern behind this problem is, as it works on my PPC machine? Is it architecture or Debian specific? Michel -- Earthling Michel Daenzer (MrCooper) \ CS student and free software enthusiast Debian GNU/Linux (powerpc,i386) user \ member of XFree86 and The DRI Project
