Description of problem: Boot F13 RC2 DVD iso for x86_64 on HP BL460c G1 blade server. I get text-mode install even if I select the default. After asking for language and keyboard I get asked for install source. If I press F2 to add sources the installer crashes. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: when the installer asks me for language I have only one line in tty3: 11:36:36,699 ERROR : got to setupCdrom without a CD device In tty4 I see the following relating to the cdrom: NOTICE kernel:scsi 0:0:0:0: CD-ROM HP Virtual DVD-ROM PQ: 0 ANSI: 0 CCS ... WARN kernel:sr0 scsi3-mmc drive: 0x/0x caddy INFO kernel:Uniform CD-ROM driver Revision: 3.20 DEBUG kernel:sr 0:0:0:0: Attached scsi CD-ROM sr0 NOTICE kernel:sr 0:0:0:0: Attached scsi generic sg0 type 5 In tty4 I also see this line regarding framebuffer: INFO kernel:fb0: radeondrmfb frame buffer device I'll see if I can get screenshots of tty4 and the traceback after the crash
Created attachment 396048 [details] tty4 screenshot
Created attachment 396049 [details] SIGSEGV message screenshot
We've got a couple other bugs about X not starting, so let's use this one to track the segfault in comment #2. Here's where it's happening: 0x40fa7e - /usr/src/debug/anaconda-13.29/loader/driverdisk.c:364 0x4104fd - /usr/src/debug/anaconda-13.29/loader/driverdisk.c:398 0x417dcb - /usr/src/debug/anaconda-13.29/loader/hdinstall.c:298 0x40a8c1 - /usr/src/debug/anaconda-13.29/loader/loader.c:1563
Couldn't the SIGSEGV be a consequence of not finding the install media? Even if it loads drivers for the (virtual) DVD-ROM drive that contains the full DVD image it asks me where to find the install image. I think I would be more worried about that then the actual SIGSEGV at the end? I would expect not finding the install media to perhaps also explain the lack of working X. The other issues I have seen about lacking X have been related to nvidia. I do have a list of suggested devices on the screen where I am supposed to select install media. Which device should have worked given the driver messages above? I could try selecting that device and see if there are any meaningful error messages.
Btw. This server will be available for fedora testing only until it gets a memory upgrade (vendor claims about one week). After that it will go into production as a ESX server. I hope we can get all necessary input to find this bug by then.
Just tried RC3. I no longer get the text mode install. In fact I get no way to interact with anaconda at all. Instead I get straight to the SIGSEGV. I can still switch between consoles. There is nothing in tty2. I'll attach the screen dumps from ttys 1, 3 and 4.
Created attachment 396249 [details] F13 alpha RC3 SIGSEGV message
Created attachment 396250 [details] F13 alpha RC3 tty3 output
Created attachment 396251 [details] F13 alpha RC3 tty4 output
Tried again today with RC4. Same as RC2.
This is already included in rawhide anaconda-14.0-1.
anaconda-13.36-1.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/anaconda-13.36-1.fc13
anaconda-13.36-1.fc13 has been pushed to the Fedora 13 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update anaconda'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/anaconda-13.36-1.fc13
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '13'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.