[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Xfree86 problems, sarge/woody



On Mar 02 2007, Sven Arvidsson wrote:
> 
> On Fri, 2007-03-02 at 07:56 -0800, Arlie Stephens wrote:
> > The complaint is that it fails to find a framebuffer, regardless of
> > which answer I give to the question of whether or not to use the
> > kernel's framebuffer. I (stupidly) failed to save the XF86Config file
> > before starting, but the current one is identical to an older one that
> > was lying around in /etc/X11. What I don't know is whether that's one
> > from before I got X working on this system the last time, or one that
> > actually worked. 
> 
> (EE) Unable to find a valid framebuffer device
> (EE) NV(0): Failed to open framebuffer device, consult warnings and/or errors above for possible reasons
>         (you may have to look at the server log to see warnings)
> 
> These errors (and the warnings above) indicate that you need to load the
> framebuffer driver for nvidia cards, "modprobe nvidiafb". 

Hmm, looks like it's time to really display my ignorance. Is this a
driver in the sense of kernel driver - and in particular, a kernel
driver that's loaded dynamically and not built into the main kernel? 
Or is this a "driver" in some sense specific to X? 

I'm inclined to presume the former - but if so, well, the system is
running on a kernel that was current when 'woody' was still the stable
release of debian. Did kernels of that generation even have this
driver - or am I looking at a need to upgrade my kernel in order to
use this version of xfree86 on this system? (Or perhaps more correctly
- in order to use it without much hand tweaking of files that
dpkg-reconfigure can't seem to get right - since commenting out
various things in XF86Config-4 did get X basically working.) 

-- 
Arlie

(Arlie Stephens	                              arlie@worldash.org)



Reply to: