REAL problems with X crashing for fc5 and radeon cards - Help ?

[Kam Leo]

On 4/22/06, Mike Cohler <mike.cohler at gmail.com> wrote:
> On 4/21/06, Mike Cohler <mike.cohler at gmail.com> wrote:
> > I have a freshly installed FC5 system on a machine that was running
> > FC4 until today.
> > It has an Athlon processor and an onboard Trident Cyberblade graphics
> > card, as well as a Radeon 7000 PCI card, and the monitor is plugged
> > into the Radeon card.
> >
> > It would not do a graphical install at all, so I did a text install -
> > and this appeared successful.
> >
> > However, once complete it refused to enter firstboot - and crashed as
> > soon as X tried to start.
> > I have been unable to get past that point !  I had severe problems
> > last year - see
> > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=169637
> > for the problems relating to fc4.
>
> Having had some thoughts overnight I think that the basic problem may
> be that during install the installer recognised the Trident on-board
> graphics card and selected this as the card to use instead   of the
> PCI radeon card to which the monitor was plugged in.  The monitor was
> nevertheless detected correctly by the probe.
>
> I therefore wonder if it is possible to select which graphics card the
> system uses by a kernel parameter when the installer starts (assuming
> I re-installed from scratch) ?  For example is it possible to select
> pci=reverse or somesuch or does anyone know the details of the kernel
> parameters to be able to say what other options might work ?  Cetainly
> noacpi, noapic and selecting resolution all make no difference.
>
> If the monitor is connected to the onboard Trident socket then the
> screen is not displaying anything once the system boots so I presume
> the BIOS detects the monitor -  this is all very puzzling and I am not
> sure if it is something simple to cure or if I should unplug the PCI
> graphics card and stick with the old on-board one.
>
> Mike
>
>
> --
>
> mike cohler
>

If you are not using the Trident adapter go into the BIOS and disable it.