Description of problem: Live DVD boots properly to menus, but yields a Black Screen of Death when any menu option is chosen if the DVD-ROM is attached to Silicon Image 3114 SATA PCI controller. Case 0: SATA DVD-ROM drive attached to motherboard SATA ports: Live DVD works as expected. Case 1: SATA DVD-ROM drive attached to Silicon Image 3114 SATA PCI Controller Card: Computer boots into F25-A2 Live DVD menu. User is presented with menu options to load Live DVD, check media, etc. When user selects a menu option the Live DVD responds with a Black Screen of Death. The screen clears, and a white flashing dash is rendered in the upper left hand corner of a blank screen. No further DVD-ROM action is identifiable (ie: lights do not flash). Normally no error messages occur. Once I did notice an error message about not being able to find a CD-ROM drive. If the DVD-ROM's SATA cable is moved to one of the motherboard SATA ports and the PC is rebooted (Case O above) the live DVD boots normally. When connected back to the SI controller the Live DVD will boot but will not execute menu selections. Any menu selection results in BSOD. Case 2: When DVD-ROM is connected to the SI device driver, an old Linux Mint Live DVD works fine. This clearly seems to be a problem with recognition of the SI controller by the F25 Live DVD environment. Is the driver missing? This bug effectively blocks the F25-A2 live DVD from running when the system is booted off of the SI controller card. In my case, I am reserving all of the motherboard SATA6 ports for hard disk drives, I have no SATA ports available for optical media, and I am using the slower PCI card's SATA interface for the slow DVD-ROM drive. Works with other DVD media, just not F25. Software Version: F25 Workstation Alpha-2 DVD How reproducible: Always Steps to Reproduce: 1. Verify Installation Media on another PC 2. Attempt to run Live DVD from motherboard SATA Controller -- works 3. Attempt to run Live DVD from SI PCI controller card -- boots to DVD menu but menu options lock-up when chosen and Live DVD will not load. Actual results: Expected results: Additional info: Output of lspci when the system is booted into F20: 05:06.0 RAID bus controller: Silicon Image, Inc. SiI 3114 [SATALink/SATARaid] Serial ATA Controller (rev 02) Subsystem: Silicon Image, Inc. Device 7114 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 32, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 21 Region 0: I/O ports at b040 [size=8] Region 1: I/O ports at b030 [size=4] Region 2: I/O ports at b020 [size=8] Region 3: I/O ports at b010 [size=4] Region 4: I/O ports at b000 [size=16] Region 5: Memory at fe180000 (32-bit, non-prefetchable) [size=1K] Expansion ROM at fe100000 [disabled] [size=512K] Capabilities: [60] Power Management version 2 Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=2 PME- Kernel driver in use: sata_sil Kernel modules: sata_sil
I am using the x64_64 media. output of lspci in Case 0, when the system is booted into F25-A2 Live DVD using one of the motherboard SATA ports: 05:06.0 RAID bus controller: Silicon Image, Inc. SiI 3114 [SATALink/SATARaid] Serial ATA Controller (rev 02) Subsystem: Silicon Image, Inc. Device 7114 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 32, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 21 NUMA node: 0 Region 0: I/O ports at b040 [size=8] Region 1: I/O ports at b030 [size=4] Region 2: I/O ports at b020 [size=8] Region 3: I/O ports at b010 [size=4] Region 4: I/O ports at b000 [size=16] Region 5: Memory at fe180000 (32-bit, non-prefetchable) [size=1K] Expansion ROM at fe100000 [disabled] [size=512K] Capabilities: [60] Power Management version 2 Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=2 PME- Kernel driver in use: sata_sil Kernel modules: sata_sil
Submitting this bug as a blocker for F25 Beta. In this case, the Live DVD itself boots properly, but fails to execute any menu item such as booting into the Live DVD environment. This is being submitted as a beta blocker according to the following two criteria (not sure which one is most applicable): * Criterion: Initialization Requirements > Release-blocking images must boot * Criterion: Installer Requirements > Hardware and firmware RAID; machine BIOS boots properly to the DVD-ROM drive hosted on the controller card, and provides the menu selections on the Live DVD, but the Live DVD environment fails to boot when it's menu item is selected.
Moving this to a place thats more useful
If you modify the boot entry to remove the 'quiet rhgb' options, do you see anything different on the screen? We kinda need to narrow down if this is failure in the bootloader, kernel, or initramfs.
Discussed during the 2016-09-12 blocker review meeting: [1] The decision to delay the classification of this as a bug was made as we're not yet sure exactly how this is failing or how much hardware may be affected; we have asked the reporter for more info and will also put out a call for optical media testing. [1] https://meetbot.fedoraproject.org/fedora-blocker-review/2016-09-12/f25-blocker-review.2016-09-12-16.01.txt
I have three new observations to report: (1) the Live DVD will boot from the troubleshooting menu entry when selecting boot with a basic video system. (2) (In reply to Chris Murphy from comment #4) > If you modify the boot entry to remove the 'quiet rhgb' options, do you see > anything different on the screen? We kinda need to narrow down if this is > failure in the bootloader, kernel, or initramfs. there is no 'quiet rhgb' option in the boot entry. usually i see this as 'rhgb quiet' (reversed order), but that isn't in the boot entry either. the boot entry does not contain 'rhgb' though it does contain 'quiet'. I don't know if the appearance of 'quiet' not preceded by 'rhgb' is a syntax error or not. removing 'quiet' allows the system to boot from the live CD. (3) this bug does not effect the KDE spin of the Live DVD. even though the KDE live DVD contains the same kernel command as referenced in (2) above, the KDE spin DVD will boot while the regular Gnome version will not. hth
Peculiar that booting with this SATA control affects video. Anyway, I suggest booting without 'quiet', get to a console and package up some things about the system. dmesg > dmesg.log lspci -vvnn > lspci.txt scp or usb stick those files off the system and add them as attachments to the bug report.
Created attachment 1200722 [details] verbose output of lspci
Created attachment 1200723 [details] dmesg log
FWIW I was unable to use the USB stick transfer method, as even though dmesg shows that my Lexar USB stick was recognized, the Gnome environment failed to recognize/mount the USB stick.
I tested on 2 desktops with sata dvd drive and and laptop and desktop with usb dvd drive. It worked on all of them.
(In reply to bob from comment #10) > FWIW I was unable to use the USB stick transfer method, as even though dmesg > shows that my Lexar USB stick was recognized, the Gnome environment failed > to recognize/mount the USB stick. Please ignore comment 10. The USB recognition problem is a specific to Bug 1376455 in which USB ports are rendered non-functional if AMD IOMMU is enabled.
Discussed at 2016-09-19 blocker review meeting: [1]. This bug was rejected as Beta blocker: this does not seem to affect much hardware, and there is a workaround available [1] https://meetbot-raw.fedoraproject.org/fedora-blocker-review/2016-09-19/
What's the "workaround"? Not using the controller?
(In reply to bob from comment #14) > What's the "workaround"? Not using the controller? In lieu of comments 7, 8, 9, I take it to mean that removing "quiet" allowed you to boot with this controller to supply the dmesg. But looking at them, the word "silicon" doesn't appear at all so, how did you boot? The bottom line is that we need more information, there's essentially no information in the bug to understand where the failure is happening. So you'd need to have the configuration setup to boot using this controller first, and then remove "quiet" boot parameter. There's no way to know if this is failing in the bootloader, or kernel, or initramfs.
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. 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 EOL if it remains open with a Fedora 'version' of '25'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.