On Fri, 25 Feb 2000, Mattias Hermansson wrote:
I don't have my lilo.conf handy but from memory I have:
vga=0x315
This might be your headache. Try `vga = 791', which is 1024x768@16. If this works, you should explore /usr/src/linux/doc a little further ;).
Actually, I think this has to do with a bug in matroxfb that prevents the computer from booting in graphics mode. Compile it as a module and try again. This is true for Alpha/Linux, but I read somewhere that it's a cross platform bug.
I give up. I'll stick with the vesafb for now. I compiled matroxfb as a module and when I loaded it, blank screen. I telneted in and the modules loaded fine, I ran fbset -i and everything looked fine except that I think the mode was 0x0, maybe that's the cause of the blank screen? (I'm not sure exactly what it was as I switched back to my old kernel and am no longer on that mission). When I loaded the module was I supposed to pass the mode??? Or should I put the mode in the append line in lilo.conf instead of after vga=??? Hmmmm, maybe I'll look into this a little more. Oh yeah, I assume that I could have used fbset to change things around but this brings up another question: on some apps when I run --help and pipe it to more or less sometimes it doesn't seem to pipe and I only see the end of the help info. Is there another way to be able to see all of the --help in this case? Thanks for all the --help! Later, Greg -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/