From: Matt E. <me...@in...> - 2004-03-24 13:15:01
|
> > The AMD K6-500 had a Matrox 400 (well I think it's actually a > > 450) in iot which is not supported > > If it was a G400, it should be supported. If it is a G450, it > isn't supported, but it shouldn't crash and it should just drop > back to the Vesa 2.0 driver. Did you try to boot Syllable on > that machine with the Matrox card still in it? Yes (sorry, email seems to be crossing over), the Matrox card seems to get farther, but it flips to a display frequency not supported by my LCD monitor here at work, more or less at about the time the AppServer would kick in. > > ..the onboard sis 530 chipset... this failed in the way I > > described. Is the Sis driver conflicting witht hte 530 chipset? > > No idea. Arno is the SiS guy. Well I know he mentioned SiS620 at one point, but not 530. The 530 is quite compatible with the 620, in so far as the 620 driver will work with it under BeOS (but fairly badly except in 32bit color depth.) IIRC the boot sequence found the matrox card fine (after trying a bunch of others first, as it should have) and decided it was a G400. There was less to-ing and fro-ing with the 530, it got past the detection quite quickly, but then locked at the point I mentioned (still blue debug output, no appserver/GUI except the one time it locked.) I'm guessing the problem with the G400 (it's a dual head, is that a usual config - dunno, never really owned one till about a month or two ago) is it's flipping into a mode the monitor doesn't support. Is there a way to fix the resolution at boot time? Matt |