Lennart Sorensen (lsorense@csclub.uwaterloo.ca) wrote: > On Fri, Nov 04, 2005 at 05:19:03PM +0100, Gilles wrote: > > Could these be the cause of the strange behaviour: > > > > CONFIG_FB=y > > CONFIG_FB_CFB_FILLRECT=y > > CONFIG_FB_CFB_COPYAREA=y > > CONFIG_FB_CFB_IMAGEBLIT=y > > CONFIG_FB_SOFT_CURSOR=y > > CONFIG_FB_MODE_HELPERS=y > > CONFIG_FB_VESA=y > > Certainly possible. The nvidia driver is not compatible with the FB > drivers, while the nv driver is compatible with some of them. > > Of course if you don't enable the vesa fb at boot it shouldn't cause a > problem but maybe it still messes things up. > > > The problem shows up when the driver "nvidia" is enbled instead of > > the "nv" driver. > > Well as I said, the nv driver does not have problems with some fb > drivers, while nvidia driver always does. Uhm? Does the =Y not referr to built in module in the kernel? Don't you have to disable a builtin module at boot time to get rid of it? You don't have to enable it, right? > > > [I posted 2 log files about 3 hours ago.] > > Yes, C-Alt-Bspace returns me to the console. > > Len Sorensen > > > -- > To UNSUBSCRIBE, email to debian-amd64-REQUEST@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org -- .O. Scream, Scream like the silence of the bits. ..O Dead lies the flag by the feet of the cold one. OOO Freedom WILL break the walls of mammon.
Attachment:
pgpmjXiz02u1_.pgp
Description: PGP signature