* Patric <[EMAIL PROTECTED]> wrote: > andrea wrote: > >... > >The X session loads smooth with no errors and no warnings but after X is > >loaded there is no way to come back to the framebuffer console (pressing > >CTRL+ALT+F* or closing the session). > > > >I get an almost white screen with some distorsion. If I come back > >pressing CTRL+ALT+F7 I see my X session up n running. > >The same happens if I close my session and then write "startx" on the > >white screen. I have a brand new session running with no problems and no > >errors. > > I'm afraid I can't provide any help on this, but wanted to mention that I > experience exactly the same behaviour with my GeForce Go 6800 (TurboCache). > And this is not only for the current driver, but has been the case ever > since i > own this notebook (it's an Acer Travelmate 4150LMi). The nvidia driver > version > at the time I got it was 1.0-7184, and was already broken back then. > I would really love to see a solution for this, since not being able to > leave X > is pretty annoying. > I should mention that on this system I have Debian installed, and used > kernel.orgs vanilla kernel + nvidia driver from their homepage ever since.
You're talking about the NV's secret-code driver ? It makes heavy trouble with fbdev. Both together monst likely won't work. That's because they refuse to use the well approved DRI interface and do something completely own and obfuscated. Nobody outside of NV can really help you :( cu -- --------------------------------------------------------------------- Enrico Weigelt == metux IT service - http://www.metux.de/ --------------------------------------------------------------------- Please visit the OpenSource QM Taskforce: http://wiki.metux.de/public/OpenSource_QM_Taskforce Patches / Fixes for a lot dozens of packages in dozens of versions: http://patches.metux.de/ --------------------------------------------------------------------- -- gentoo-user@lists.gentoo.org mailing list
