Red Hat Bugzilla – Bug 467158
Anaconda on Fedora 10 Beta Net install crashes (RuntimeError: could not open display)
Last modified: 2008-10-24 11:55:19 EDT
Description of problem:
The Fedora 10 Beta installer crashes when trying to start an X server.
Version-Release number of selected component (if applicable):
"Running anaconda 126.96.36.199" i386 net install iso
Steps to Reproduce:
1. Select Install or Upgrade... at boot
2. Skip the media check (not skipping doesn't help but does add more steps)
3. Wait for it.
4. You're greeted with "you may safely reboot your system" (and other stuff)
Install gives up very early
Installer should let me install the OS and at least fall back to textmode.
Dell Inspiron 700m
Traceback (most recent call last):
File "/usr/bin/anaconda", line 832, in <module>
File "/usr/bin/anaconda", line 72, in doStartupX11Actions
File "/usr/lib/python2.5/site-packages/gtk-2.0/gtk/__init__.py", line 79, in <
File "/usr/lib/python2.5/site-packages/gtk-2.0/gtk/__init__.py", line 67, in _
RuntimeError could not open display
install exited abnormally [1/1]
then stuff about NetworkManager deactivating the network interface
On terminal F2 there's just he unusable shell prompt at this point
On term F4 at the end
<6>[drm] Initialized i915 1.6.0 20080730 on minor 1
<3>[drm:i915_gem_object_bind_to_gtt] *ERROR* GTT full, but LRU list empty
<3>[drm:i915_gem_object_pin] *ERROR* Failure to bind: -12<3>[drm:i915_gem_idle]
*ERROR* hardware wedged
On terminal F5
Build ID: xorg-x11-server 1.5.0-6.fc10
New driver is "intel"
Using defualt built in config
(EE) open /dev/fb0: No such device
(EE) intel(0): Failed to pin front buffer: Cannot allocate memory
Fatal server error:
Couldn't bind memory for BO front buffer
My video is the Intel 855GM Chipset (according to dmesg)
Looks like this might be related: https://bugzilla.redhat.com/show_bug.cgi?id=461205
But still, anaconda shouldn't crash when text mode can still run.
talked this over with wwoods and he believes real bug is that anaconda should fail back to text mode. changing component to 'anaconda'
This should be fixed in the next build of anaconda, though the critical bug here is that X isn't starting up. I believe that's already been filed though.