Re: Woody & XFree86: no screens found

["Eric G. Miller" <egm2@jps.net>]

On Tue, 27 Nov 2001 01:56:33 -0500
Brian Clark <brianj@fusionwerks.com> wrote:

[snip]

Shot in the dark...

> Section "Device"
>         Identifier      "Viper v770 TNT2"
>         Driver          "nv"
>         Option          "UseFBDev"              "true"
> EndSection

  Do you really want to use the framebuffer device?  And, if so does
your current kernel have framebuffer support compiled in?  I'd think
there'd be a warning, but I couldn't see anything obviously wrong
and the log isn't very telling -- the only thing I note, is it
starts unloading modules after it loads up the framebuffer
driver and just before it poops out.  The problem may also be
related to modelines, as I didn't see any in the logs, is
X 4 not able to query your monitor for timings?  But I guess
that's a result of specifying the framebuffer device?  

[snip]

> (**) NV(0): Option "UseFBDev" "true"
> (==) NV(0): Using HW cursor
> (**) NV(0): Using framebuffer device
> (II) Loading sub module "fbdevhw"
> (II) LoadModule: "fbdevhw"
> (II) Loading /usr/X11R6/lib/modules/linux/libfbdevhw.a
> (II) Module fbdevhw: vendor="The XFree86 Project"
>         compiled for 4.1.0.1, module version = 0.0.2
>         ABI class: XFree86 Video Driver, version 0.4
> (II) UnloadModule: "nv"
> (II) UnloadModule: "fbdevhw"
> (II) Unloading /usr/X11R6/lib/modules/linux/libfbdevhw.a
> (II) UnloadModule: "vgahw"
> (II) Unloading /usr/X11R6/lib/modules/libvgahw.a
> (II) UnloadModule: "int10"
> (EE) Screen(s) found, but none have a usable configuration.


-- 
Eric G. Miller <egm2@jps.net>