Comment 7 for bug 312924

> 01:05.0 VGA compatible controller [0300]: ATI Technologies Inc RS690 [Radeon
X1200 Series] [1002:791e]
> 02:00.0 VGA compatible controller [0300]: ATI Technologies Inc Mobility
Radeon HD 3450 [1002:95c5]
> Seems you have two graphic cards, maybe that confuses the driver?

Testing I did with the RS690 only produced similar results. I do not think
xserver is confused by the two video cards.

>What kind of computer do you have?

SapphireTech R690 motherboard, AMD 3800+, 2GB, AHCI sata disk and IDE DVD.
I was using 4GB but couldn't get anything to work. IOMMU problem.

I have updated the bios since I reported the bug. There were updates in IDE-
AHCI handling.

> Do the graphics work with Intrepid?

Yes, but I could only use second monitor to mirror the primary using Ubuntu
supplied ATI proprietary. Both monitors and both devices were identified by
AMDCCCLE. Both analog monitors were run from the HD3450.

What happens if you try to use the driver "radeonhd"
I have not tried the Novell driver. Jaunty was my first choice.

I did spend a fair amount of time to manually configure xorg.conf. All my
changes would be removed by the recommended command they advice you to run.
Obviously, I stopped using it. As soon as I added monitor specs such a hsync
or vsync it would fail. Driver changes also failed. The fglrx driver would
not load due to incompatible libraries.

I am currently wiping the disk to get a consistent starting point (alpha2 +
updates). Should I try radeonhd? The online docs at xorg state it only works
for R5xx, R6xx and below.

Murray

> Thanks!
>
> --
> HD3450 configuration fails on reboot in jaunty
> https://bugs.launchpad.net/bugs/312924
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in ?xorg? source package in Ubuntu: Incomplete
>
> Bug description:
> Binary package hint: xserver-xorg
>
> Installed onto fresh formatted disk using jaunty alpha 2.
> Updated install with sudo apt-get update.
> The only successful boot I can get is by manually adding driver "vesa" to
device section in /etc/X11/xorg.conf
>