On Tue, Apr 08, 2003 at 06:45:52PM -0500, Thomas Dodd wrote: > Ed Wilts wrote: > > On Tue, Apr 08, 2003 at 05:24:36PM -0500, Thomas Dodd wrote: > >>Sound like something for bugzilla maybe. Not sure why X wouldn't startup > >>though. I tried it on an old laptop, specifying the wrong chip/sync, and > >> when that didn't work It switched to the vesa driver. But if I give > >>the correct chip/sync it's fine. I don't see X, but it appears to be > >>running somewhere. > > > > I've already bugzilla'd it. With my ProSavageDDR chipset, the savage > > driver dies a quick and horrible death (X hang) whereas vesa works just > > fine. > > Perhaps if you told it an obvious wrong chip, it would fallback > correrctly? What about using --set-driver=vesa ? Does it hang or does it > use the vesa drive like you said to? If I explicitely tell it to use the vesa driver, it works properly. If I give it an obviously wrong one, startx fails with a Fatal server error: no screens found. This was with i810, s3 and trident. So, at least the savage driver thinks it should be able to work. > Still, if if the savage driver hangs the system, it shouldn't use it. > I remember before a few chips that got vesa or some other generic driver > because probing was unstable/locked up. Check with Mike Harris about the > driver locking up. Mike is the owner of the bugzilla report right now. It's 87778. > rh-cfg-xf need a way to not use that driver on that chip. Perhaps the > recent change in maintainer caused it to be missed? Did you test in the > last beta cycle? I didn't have this system available during the beta. I successfully installed AS2.1, 7.3, and 8.0 and wouldn't even thought of having issues with something like the graphical install of phoebe or 9. I do have to wonder why anaconda tries to use the native savage driver when the vesa driver is more likely to be successful. Sure, use the savage driver later (which in my case still fails), but at least let the user do the install properly. Which leads to another question - how do I tell anaconda to use the vesa driver instead of the savage driver? -- Ed Wilts, Mounds View, MN, USA mailto:ewilts@xxxxxxxxxx Member #1, Red Hat Community Ambassador Program
