Ok, now I'm on a mission. Again I compiled in matroxfb support and checked off the G200 driver. My system boots properly if I boot into text mode but no matter what I put in lilo I get a blank screen if I want to boot into the frame buffer. I don't have my lilo.conf handy but from memory I have: vga=0x315 append="matrox:vesa:noblink,mtrr"
From the matroxfb.txt I am confused on how you separate the options and values with colons and commas so I have tried several combinations of the append line and I have used vga=ask. Is somebody out there using matroxfb support with a G200? What is in your lilo.conf? Phillip???
The vesafb works fine with the stock kernel but ever since I saw the matroxfb support I'm on a mission to get it to work. Thanks, Greg Because e-mail can be altered electronically, the integrity of this communication cannot be guaranteed. -- 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/
On Fri, 25 Feb 2000, Thomas, Gregory (NBC, KNBC) 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 ;). -- -=|JP|=- Jon Pennington | Atipa Linux Solutions -o) jpennington@atipa.com | Kansas City, MO /\\ 816-241-2641 x107 | http://www.atipa.com _\_V -- 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/
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'd go with the vesafb, as that is able to boot in gm. and gets the cute little Tux overlooking the boot process... vga=0x315 is the same as vga=789 and should work fine. Older lilo's had a problem with hex but from 5.3 and on this hasn't been a problem.(Maybe earlier but I know it works in 5.3 as it was with that one I first tried vesafb) /Mattias -- 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/
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/
On Fri, Feb 25, 2000 at 12:15:33PM -0500, Thomas, Gregory (NBC, KNBC) wrote:
Ok, now I'm on a mission. Again I compiled in matroxfb support and checked off the G200 driver. My system boots properly if I boot into text mode but no matter what I put in lilo I get a blank screen if I want to boot into the frame buffer.
I don't have my lilo.conf handy but from memory I have:
vga=0x315 append="matrox:vesa:noblink,mtrr"
Here's what works for me: ---8<--- append="video=matrox:vesa:283" # 1280x1024x32 boot=/dev/sda #compact # faster, but won't work on all systems. vga=normal read-only prompt ---8<--- -- Brad Shelton On Line Exchange http://online-isp.com -- 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/
On Sat, 26 Feb 2000, Brad Shelton wrote:
On Fri, Feb 25, 2000 at 12:15:33PM -0500, Thomas, Gregory (NBC, KNBC) wrote:
Ok, now I'm on a mission. Again I compiled in matroxfb support and checked off the G200 driver. My system boots properly if I boot into text mode but no matter what I put in lilo I get a blank screen if I want to boot into the frame buffer.
I don't have my lilo.conf handy but from memory I have:
vga=0x315 append="matrox:vesa:noblink,mtrr"
Here's what works for me:
---8<---
append="video=matrox:vesa:283" # 1280x1024x32 boot=/dev/sda
Ok, I do believe that is where my problem was. I was missing the video= part. Anyway, I currently have matroxfb loading as a module and everything is working great (except no Tux on boot, bummer!). My /etc/lilo.conf: vga=normal My /etc/modules.conf: options matroxfb vesa=0x317 mtrr Don't know if it takes the mtrr or not but I don't get any errors. Two questions now: 1) Philipp Thomas had mentioned that fbset -depth 0 would set it back to text mode. It's not doing that for me, is it because I am using matroxfb as a module??? 2) When I try to modprobe -r matroxfb I get "Device or resource busy". Is there anyway to remove the module at this point??? Thanks all, 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/
participants (5)
-
bshelton＠online-isp.com -
ethant＠earthlink.net -
gregory.thomas＠nbc.com -
jpennington＠atipa.com -
mattias＠hemmet.chalmers.se