Segfault on Install with Radeon + Intel iGPU both enabled

Bug #1407375 reported by Wendell
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xorg (Ubuntu)
Expired
Low
Unassigned

Bug Description

My system is an Intel i7 4770k on an asus Z87 WS motherboard with an AMD R9 290X graphics card. With Intel iGPU enabled in the UEFI, the installer crashes.

I have 4 displays, 3 attached to the R9 290X and one attached to the onboard graphics.

I hit ctrl+alt+f1 and looked at /var/log/X.org.0 log and it indicated a Segmentation fault. I was able to continue with the install by unplugging all monitors but the primary monitor AND disabling the iGPU in the UEFI. I was somewhat surprised that it was necessary to completely disable the onboard graphics because in many OEM configurations onboard and PCIe will be enabled for possible multi-monitor configurations.

After installing, apt-get update && apt-get upgrading the distro, I installed the proprietary fglrx driver using software center, and that worked fine.

I re-enabled the iGPU however the system appears to hang hard. On two of the displays (attached to the R9 290X) I can see the animated boot screen, but ctrl+alt+f1 does not work, and the caps lock light does not toggle if I hit capslock. No mouse cursor. I did not try ssh, but the system did not respond to a 'tap' of the power button to shut it down.

I would be willing to experiment a bit here if someone can point me the right way. I realize I might have to do some things at the command line, but I wanted to bring this to your attention because I am not sure enabling the iGPU should causes the system to become unusable.

I am using the official gnome variant of the 14.10 install USB stick.

I tried both "Try Ubuntu" and "Install Ubuntu" from the UEFI boot menu and both options behave approximately the same way in terms of the Segfault.

Tags: utopic
Revision history for this message
Wendell (wendell-u) wrote :

I answered "yes" to the submit a bug prompt within ubuntu. my machines hostname was failbox1 if that helps you look it up.

affects: usb-creator (Ubuntu) → ubiquity (Ubuntu)
Phillip Susi (psusi)
affects: ubiquity (Ubuntu) → xorg (Ubuntu)
Revision history for this message
penalvch (penalvch) wrote :

Wendell, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal as it will automatically gather and attach updated debug information to this report:

apport-collect -p xorg 1407375

Please ensure you have xdiagnose installed, and that you click the Yes button for attaching additional debugging information.

As well, given the information from the prior release is already available, testing a release prior to the development one would not be helpful.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

Changed in xorg (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Wendell (wendell-u) wrote :

The installer will run and completes now, even with the integrated graphics enabled. However, and this is really weird, after first reboot it seems as though the graphical login screen crashes and restarts over and over again. I can hear the ubuntu welcome drum beat thing over and over. On screen I can watch most of the displays enter graphical mode, then they exit back to the console before starting again.

Should I do the apport-collect command or do a new bug report?

Revision history for this message
penalvch (penalvch) wrote :

Wendell, could you please test the amd64 variant of http://cdimage.ubuntu.com/daily-live/current/ and advise to the results?

tags: added: utopic
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for xorg (Ubuntu) because there has been no activity for 60 days.]

Changed in xorg (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.