I'm not sure anymore. My log file has twice as many out of range warnings as yours and it works beautifully. So don't worry about those. You might read some documentation on framebuffer kernel parameters to try to get the fb driver working. I don't quite remember where that 791 came from. It either came from some weird support page or mandrake set it up automatically. I believe 791 means special SVGA. Its somewhat of a generic driver, and I've seen it used on certain laptops if I recall. There are other numbers you can try. Try reading through /usr/src/linux/Documentation/fb/* especially vesafb. You can try 318 for instance. I never got the framebuffer drivers working in redhat, so I finally just installed mandrake and it worked. So this fb solution might be a serious undertaking.
If your card doesn't support mode 791, this makes me kind of wonder what nvidia is doing. People get really upset about their closed source drivers in the first place, but having cards that don't respond to industry standards seems worse. No matter what you send at a graphics card, it shouldn't lock up the entire system. I've gotten hardlocks from this nforce chip too, but just from the generic X driver, not the nvidia one or the framebuffer. Does your card work in windows? You might read through nvidia's site and their driver readme files and whatever to see if your particular card is even supported by the package. -Eric Hattemer On Sun, 2002-10-27 at 22:36, Rodney Kanno wrote: > > Try this... Make sure your /etc/lilo.conf contains vga=791 ie: > That made the computer lock up right after I selected "linux-enterprise" > from lilo...I have attached the XFree86.0.log. There are a bunch of errors > in there "horizontal sync out of range," any other ideas? > > Rodney >
