Description of problem: I booted the fedora 36 install usb it went to a balck screen after a while i hit power and it shutdown instantly i turned my computer off and on several times went out and erased my drive (on purpose) then rebooted to the installer same black screen instant off i turned my computer off and on several times it finally booted i checked media and installed fedora 36 using manual standard ext4 partitions (boot/efi, / , swap) it rebooted withourt issue and then this popped up on the screen i did this as a test ive been having the same issue booting to silverblue 36 which ive been using for a month (when i can get it to boot) Additional info: reporter: libreport-2.17.1 WARNING: CPU: 0 PID: 8 at drivers/gpu/drm/i915/display/intel_ddi.c:1378 intel_ddi_level+0x198/0x1b0 [i915] Modules linked in: i915 rtsx_pci_sdmmc mmc_core crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel serio_raw rtsx_pci ttm wmi video ip6_tables ip_tables ipmi_devintf ipmi_msghandler fuse CPU: 0 PID: 8 Comm: kworker/0:1 Not tainted 5.17.5-300.fc36.x86_64 #1 Hardware name: Hewlett-Packard HP Spectre x360 Convertible 13 /802D, BIOS F.54 12/27/2019 Workqueue: events output_poll_execute RIP: 0010:intel_ddi_level+0x198/0x1b0 [i915] Code: 48 8b 5f 50 48 85 db 75 03 48 8b 1f e8 91 0f 22 f4 48 c7 c1 80 a1 74 c0 48 89 da 48 c7 c7 11 6d 76 c0 48 89 c6 e8 81 8b 61 f4 <0f> 0b 8b 54 24 04 e9 7a ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 RSP: 0018:ffffa8458007fa80 EFLAGS: 00010282 RAX: 0000000000000037 RBX: ffff918ec11a4cf0 RCX: 0000000000000000 RDX: 0000000000000001 RSI: ffffffffb5665ad5 RDI: 00000000ffffffff RBP: ffff918eca4a0000 R08: 0000000000000000 R09: ffffa8458007f8c0 R10: ffffa8458007f8b8 R11: 0000000000000003 R12: ffff918ec7e3a000 R13: 0000000000000000 R14: ffffffffc07155f0 R15: ffff918ec9ba2000 FS: 0000000000000000(0000) GS:ffff919006c00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f0abef6f860 CR3: 000000010de10002 CR4: 00000000003706f0 Call Trace: <TASK> intel_enable_ddi+0x107/0x740 [i915] intel_encoders_enable+0x80/0xa0 [i915] hsw_crtc_enable+0x1a0/0x5f0 [i915] intel_enable_crtc+0x60/0x80 [i915] intel_commit_modeset_enables+0x53/0x80 [i915] intel_atomic_commit_tail+0x6e1/0x1930 [i915] ? flush_workqueue+0x15d/0x3f0 intel_atomic_commit+0x339/0x390 [i915] drm_client_modeset_commit_atomic+0x1c4/0x200 drm_client_modeset_commit_locked+0x56/0x150 drm_client_modeset_commit+0x21/0x40 drm_fb_helper_set_par+0x98/0xd0 drm_fb_helper_hotplug_event+0xb9/0xd0 output_poll_execute+0x8e/0x1e0 ? kfree+0x1c7/0x220 process_one_work+0x1c7/0x380 worker_thread+0x4d/0x380 ? _raw_spin_lock_irqsave+0x25/0x50 ? process_one_work+0x380/0x380 kthread+0xe9/0x110 ? kthread_complete_and_exit+0x20/0x20 ret_from_fork+0x22/0x30 </TASK> Potential duplicate: bug 2057591
Created attachment 1912350 [details] File: dmesg
This may or may not be related to my initial problem. The initial problem is that half the time fedora wont boot. After i got it to boot (after a fresh install) this popped up on the sceen. Heres some info on the initial problem: If fastboot is on in bios my computer wont boot. If fastboot is off in the bios and i have a usb flash drive plugged in My computer will boot (after the keyboard lights flash twice) This will work with any flash drive empty or not (ive tried 4) If fastboot is off and i dont have a flash drive in it wont boot But if i press f9 (boot options) and hit enter on fedora (What it was going to boot anyway) it boots Possibly activatng the hdmi display by pressing f9 helps it?? When my computer does not boot and press power off, it goes off instantly. So it has not booted and is just not talking to the display. I have this problem w fedora and silverblue Ive tried going back to version 32 which i think is before wayland And that works. Ive tried switching 36 to xorg but it doesnt seem to matter. My username on the silverblue bug report page is windows_guy if you want to read the entire thread on this problem which led me to test it on fedora And post it here as well. The info is more complete on silverblues github
Ive also tried rebasing my fedora silverblue to 37 (which must be beta) and that does not fix the issue. Ill try rawhide when i get some time. Ill try things for you if you want. Im pretty sure its related to my specific hardware.
rebasing to rawhide today does not fix the fact that i struggle to get silverblue and fedora to boot whatever it is, its in both only solution i have now is to choose bios boot options and pick fedora (which is the only bootable option i have) then it boots (which is what its trying to do when it doesnt boot) may be a timing issue with trying to talk to my hdmi monitor before it switches on ... idk Heres a transcript of how this issue started in silverblues github Windows-Guy commented 5 days ago I have a core i7 laptop with a broken screen that ive taken off and ive plugged it into an hdmi monitor. When i first installed sb36, it rebooted to a black screen after the install. I finally got it to boot to hdmi and updated it and then it would reboot/start to hdmi every time until today when i got an update. I started to think its booting to my non existent laptop screen except that when i hit the power button it turns off instantly instead of waiting 60 seconds. If i tap f9 at boot and pick what it was going to boot to anyway, it boots w hdmi working. I thought maybe it was wayland but im logging in under xorg. No idea whats going on but i love silverblue and ive spent a lot of time setting this up for what i need. If i cant just turn it on or reboot im going to have to go back to mint, it just works. I dont have this issue with windows 10, mint20,21, rescuezilla, backbox, rhel8, sb32, tails, uefi bios… so its not my machine @Windows-Guy Author Windows-Guy commented 5 days ago Ps ive had the same issue intermittently w rhel9, fedora36, silverblue34,35,36 so im thinking its wayland, or a timing issue like its looking for something before it had time to initialize, idk but whatever it is its core to fedora and redhat and didnt exist in silverblue32 @Windows-Guy Author Windows-Guy commented 5 days ago Intel hd5500 @travier Member travier commented 4 days ago If you can reproduce this issue with Fedora Workstation 36 then I would suggest opening a bug in Bugzilla with as much details as possible. Thanks @Windows-Guy Author Windows-Guy commented 4 days ago I did a bit more digging on sb36 today. I have a sept 13 backup that i restored to and it turns out that the problem was not in the update after that. The problem seems to be if i do not have my usb flash drive plugged in sb boots to a blank screen and the power button turns the machine off instantly no matter how long i wait. If i have the usb unplugged and i press f9 for the boot menu and hit enter for item 1(sb) it boots. There is no way grub is on my flash drive. Its been wiped w ventoy and some iso’s. So its kind of a security feature:) noone can boot my machine without my flash drive. Its a goofy issue. Ill try an earlier backup and report back @Windows-Guy Author Windows-Guy commented 4 days ago By backup above, i mean whole drive, part table, grub, partitions, everything @Windows-Guy Author Windows-Guy commented 4 days ago My best guess so far is that by having 2 bootable uefi sources or pressing the key to pick what to boot, slows down the boot process enough for the hdmi to go live before its picked up @Windows-Guy Author Windows-Guy commented 4 days ago Ok i went all the way back to my base install plus virt-manager etc no vm dated 9-5 and it boots fine with any of 4 usb flash drives plugged in and it doesnt boot if theyre not plugged in. All of are uefi bootable. Ill format one brb. Humm the plot thickens… i nuked one and put a big blank ntfs partition on it and sb boots with it in and doesnt with it out. Booting is fundemental :) you got any guesses? @Windows-Guy Author Windows-Guy commented 4 days ago That base image is just a fresh install of sb 36 with all the stuff from stephens tech talks youtube video added (i skipped the fonts, extensions and ssl, i just wanted to run kvm) and i updated that rebooted and burnt it. It pretty close to stock @Windows-Guy Windows-Guy changed the title SB randomly boots to a blank screen depending on the update SB randomly boots to a blank screen unless any usb drive is plugged in 4 days ago @Windows-Guy Windows-Guy changed the title SB randomly boots to a blank screen unless any usb drive is plugged in SB36 boots to a blank screen unless any usb drive is plugged in 4 days ago @Windows-Guy Author Windows-Guy commented 4 days ago It does seem to hang a bit when it does boot with a usb flash plugged in, then the lighted keyboard blinks off on twice and it boots. Also i have used standard ext4 partitions with one for boot/efi, boot, /, swap (wasnt sure why i needed both boots but it seemed to work that way) i think i did an auto and tried to copy that @Windows-Guy Author Windows-Guy commented 4 days ago • I restored a mint 21 image i had from august and i cant get it to not boot. I noticed its logo is on its own screen after the hp logo whereas fedoras is animated and on the hp screen. Not sure that matters but who knows. It may be my manual partitioning. Maybe var needs its own partition off root. I really like that youve got selinux, immutable core, and basically rolling modern automatic updates forever. I thought i was done:) now ive gotta update mint and sb until i decide… but one things for sure, im not a windows guy anymore :) travier reacted with thumbs up emoji @travier Member travier commented 3 days ago This seems like a firmware, bootloader or kernel issue. If you can reproduce it with a classic Fedora Workstation installation and report it in Bugzilla that would be great. @Windows-Guy Author Windows-Guy commented 3 days ago Oh… alright :) this will take a while @Windows-Guy Author Windows-Guy commented 3 days ago The flash drive i wiped out was fedora 36 lol. when i get this up ill be installing it w manual ext4 partitions boot/efi, /, and swap to keep w what ive done on sb36 the computer is an Hp spectre c360 13-4005dx With intel hd graphics 5500 And a removed built in touch screen @Windows-Guy Author Windows-Guy commented 3 days ago Ok first off the installer does the same thing at launch Black screen, power off is instant i have pressed f9 to choose this flash drive to boot to so that trick isnt working i think im dead in the water here I cant install it @Windows-Guy Author Windows-Guy commented 3 days ago I wiped out the partitions for my previous install thinking that might change things it did not I cant boot to the install iso i know nothing about bugzilla Feel free to send all this over there if you want i gotta get a working computer going so i can send out some invoices @Windows-Guy Author Windows-Guy commented 3 days ago Ive got it installing I just turned it off on several times And it came up once Media tested out fine @Windows-Guy Author Windows-Guy commented 3 days ago Finished install Shutdown Pulled out flash drive And it booted @Windows-Guy Author Windows-Guy commented 3 days ago • This just popped up Xorg-x11-drv-intel Sytem failure Crash function Intel_enable_ddi @Windows-Guy Author Windows-Guy commented 3 days ago • Bugzilla report: https://bugzilla.redhat.com/show_bug.cgi?id=2127485 @Windows-Guy Author Windows-Guy commented 3 days ago • Oh btw fastboot was disabled in my bios When it would only boot w a usb plugged in Or by selecting it in boot devices w fastboot on, it doesnt boot no matter what Thanks for working with me to nail this down. Even though ive moved back to mint21 for now, Im really impressed with this process and ill be Back when booting isnt an issue. On mint id submit this to the forum and me And some other guy would have the same Problem, then the thread would slowly change Into a contest of unrelated cool things other guys have done with sudo :)
Ive also got what appears to be 2 duplicate entries in grub for a total of 4. Ive never touched it. Ive also not let dbx update because it makes my ventoy usb un bootable. That may be a sign that ventoy is up to no good, but at this point its too late. Ive used it for everything. Is there any chance this will all be fixed in 37?
This problem, seems to have gone away on a fully updated system as of today. Im logining into wayland and my fast has fastboot enabled
This message is a reminder that Fedora Linux 36 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16. 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 'version' of '36'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 36 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 Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16. Fedora Linux 36 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 Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.