Description of problem: Booting fails when attempting to boot a livecd or boot.iso (for Fedora 21 or rawhide) via usb on my Acer C720P. I have been able to succeed in booting and installing Fedora 20 on this machine (using the 'mem=' trick). The console displays: Loading vmlinuz0... ok Loading initrd0.img... then the system immediately reboots. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Boot livecd or boot.iso from usb Actual results: Boot fails Expected results: Boot succeeds Additional info: I have tried various daily builds of the livecd for F21 and rawhide over the past week. I tried both workstation and LXDE. I even attepmted TC4 and TC5 without success.
Same here with SATA DVD drive on MSI P35 Platinum MoBo (See https://lists.fedoraproject.org/pipermail/test/2014-September/122716.html, 2.)
(In reply to Joachim Backes from comment #1) Addendum: -------------------------------------------------------------------------- 0. The DVD drive is OK ---------------------------------------------------------------------------- 1. a. Other bootable CDs/DVDs without F21 Alpha TC6 are booting properly. b. Bootable USB sticks containing F21 TC6 ALPHA images are booting properly. ----------------------------------------------------------------------- 2. Other machines (another MoBo/BIOS) are booting properly with that CDs/DVDs. ----------------------------------------------------------------------- 3. biosdecode # biosdecode 2.12 BIOS32 Service Directory present. Revision: 0 Calling Interface Address: 0x000F0010 PCI Interrupt Routing 1.0 present. Router ID: 00:1f.0 Exclusive IRQs: None Compatible Router: 8086:2910 Slot Entry 1: ID 00:01, on-board Slot Entry 2: ID 00:02, on-board Slot Entry 3: ID 00:1f, on-board Slot Entry 4: ID 00:1d, on-board Slot Entry 5: ID 00:1a, on-board Slot Entry 6: ID 00:1b, on-board Slot Entry 7: ID 00:1c, on-board Slot Entry 8: ID 02:00, slot number 32 Slot Entry 9: ID 05:00, slot number 1 Slot Entry 10: ID 05:01, slot number 2 Slot Entry 11: ID 05:02, on-board Slot Entry 12: ID 03:00, slot number 36 Slot Entry 13: ID 04:00, slot number 37 PNP BIOS 1.0 present. Event Notification: Not Supported Real Mode 16-bit Code Address: F000:6D32 Real Mode 16-bit Data Address: F000:0000 16-bit Protected Mode Code Address: 0x000F6D5A 16-bit Protected Mode Data Address: 0x000F0000 ACPI 1.0 present. OEM Identifier: ACPIAM RSD Table 32-bit Address: 0xBFFB0000 SMBIOS 2.5 present. Structure Table Length: 1377 bytes Structure Table Address: 0x000FC0D0 Number Of Structures: 27 Maximum Structure Size: 187 bytes ---------------------------------------------------------------------- 4. lspci 00:00.0 Host bridge: Intel Corporation 82G33/G31/P35/P31 Express DRAM Controller (rev 02) 00:01.0 PCI bridge: Intel Corporation 82G33/G31/P35/P31 Express PCI Express Root Port (rev 02) 00:1a.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 02) 00:1a.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 02) 00:1a.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 02) 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 02) 00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 02) 00:1c.4 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 5 (rev 02) 00:1c.5 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 6 (rev 02) 00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 02) 00:1d.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 02) 00:1d.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 02) 00:1d.3 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 02) 00:1d.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 02) 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 92) 00:1f.0 ISA bridge: Intel Corporation 82801IR (ICH9R) LPC Interface Controller (rev 02) 00:1f.2 IDE interface: Intel Corporation 82801IR/IO/IH (ICH9R/DO/DH) 4 port SATA Controller [IDE mode] (rev 02) 00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 02) 00:1f.5 IDE interface: Intel Corporation 82801I (ICH9 Family) 2 port SATA Controller [IDE mode] (rev 02) 01:00.0 VGA compatible controller: NVIDIA Corporation GT218 [GeForce 210] (rev a2) 01:00.1 Audio device: NVIDIA Corporation High Definition Audio Controller (rev a1) 03:00.0 IDE interface: Marvell Technology Group Ltd. 88SE6121 SATA II / PATA Controller (rev b2) 04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 01)
(In reply to Joachim Backes from comment #1) 2nd addendum: If I try to boot, then the message "Isolinux..." is presented very short (that's what I mean by flickering) , then the screen becomes black with a blinkung underscore char, and the machine begins to reboot. I have no chance to join somehow in the CD boot procedure (because it's soooo short). My impression: the CD is not fully complient to the guidelines for bootable CDs.
TC6 Workstation and LXDE do not work for me. Fedora-Live-LXDE-x86_64-21-20140912.iso does not work for me. Fedora-Live-Workstation-x86_64-21-20140912.iso does not work. boot.iso from today does not work. Any suggestions? I'm not sure how to try to debug this or give any more info.
(In reply to Joachim Backes from comment #1) 3rd Addendum: After investigating a long time, I suspect that is has to do with **syslinux**. Why? I have in F20 a shellscript generating a bootable cd (it uses mkbootdisk, and it runs well since generations of Fedora (mkbootdisk uses syslinux)). But running this script in F21, the generated CD is no more bootable. If I use the F20 syslinux for making the CD image (syslinux-4.05-7.fc20.x86_64) under F21, the generated CD **is** bootable, but not if using the F21-syslinux syslinux-6.02-7.fc21.x86_64.
Joachim: I think you may have hijacked a bug report here. Dale was booting from a USB stick, and his bug occurs after the bootloader has run. Your case does not look to be the same. Could you please separate your report?
(In reply to Adam Williamson (Red Hat) from comment #6) > Joachim: I think you may have hijacked a bug report here. Dale was booting > from a USB stick, and his bug occurs after the bootloader has run. Your case > does not look to be the same. Could you please separate your report? I opened already a new BZ for, concerning my remarks, on 2014-09-14: https://bugzilla.redhat.com/show_bug.cgi?id=1141496. Sorry for trouble.
Just an update. The following still do not boot: Fedora-Live-Workstation-x86_64-21-20141102.iso Fedora-Live-Workstation-x86_64-rawhide-20141102.iso boot.iso from November 2
Hi, I have the same problem with my acer c720 and fedora 21. I am currently using fedora 20 without any issue.
I have an Acer C720 (not the C720P) and also was unable to boot Fedora 21 Workstation from a USB exactly as described in the original bug report - booting from the live USB just reboots the system. However, I was able to (previously) boot Fedora 20 and install it (I then upgraded with fedup to Fedora 21).
I have the same issue with my Acer C720. However, if I try the 32bit Workstation iso there is no problem and I can install F21.
Sounds like the same thing a guy on G+ is reporting on a Chromebook Pixel, so I'm guessing it's to do with the firmwares on these things. Assigning to grub2 as a proxy for Weird Firmware Crap, and CCing mjg59. Any ideas, peter, matt?
Dirk Hohndel is the G+ guy, and he reported similar experience with F21 images - "Insert, boot, Ctrl-L, ESC, 1 (to boot from stick); see Fedora boot menu; wait, don't touch any key; count down to 0 screen turns black; two seconds later back at the white screen telling me that secure mode is off and waiting for me to press Ctrl-L" He reported though that installing from F20 and upgrading to F21 works fine. Linus says the same (I don't think Linus has tried booting from an F21 USB stick yet).
The same issue appears on HP chromebook 14. Indeed first installing F20 and then upgrading to F21 works, however booting a live F21 USB stick not.
I just tried installing F21 on my Chromebox-M004U, and I'm seeing the same problem. "Loading vmlinuz .................... Loading initrd.img ...................... ready." (Then this next part flashes by so quickly, even with boot_delay=1000. I had to get a video of it and replay it slowly). "Probing EDD (edd=off to disable) ... ok." And then the system reboots. Since it says "ok", I'm assuming EDD is fine. I am curious what it might be doing before/after that point though. I've been unable to collect any more information, even when using many of the recommended options here (in the crash/hangs section): https://fedoraproject.org/wiki/Common_kernel_problems?rd=KernelCommonProblems I was able to install F20 on this same hardware, using this same USB cdrom drive (with the mem=1024M boot option). I wonder if there's some kind of driver in the F21 initrd that wasn't present in F20. Something is making it crash pretty early in the boot process.
On my HP chromebook 14 I also had the "Probing EDD (edd=off to disable) ... ok.", but like you said I also don't think it is the problem. I already disabled edd and it still reboots. The only way I have it now running is by installing F20 first and then upgrade to 21 with "fedup"
The "Probing EDD" message is a perfectly normal boot message that I think appears on all systems, you just happen to be seeing it when the bug occurs, I think.
I can confirm the same behaviour on the Asus Chromebox M004. I can also confirm that the workaround suggested by Linus (Installing F20 and then upgrading via Fedup) works fine, which leads me to believe this is specifically an Installation/Live Media issue.
Note that on the same Acer C720P, I was able to boot F21 live usb after changing the firmware to the one provided here: http://johnlewis.ie/
I am able to boot the F21 ISO with my C720P as long as I make my own bootable USB with an earlier version of GRUB from my ubuntu box (grub-install, version 2.02-beta2-9ubuntu1). My grub.cfg menu entry is: menuentry "Fedora 21 Workstation_GNOME" { loopback loop /Fedora-Live-Workstation-x86_64-21-5.iso linux (loop)/isolinux/vmlinuz0 root=live:LABEL=Fedora-Live-WS-x86_64-21-5 iso-scan/filename=/Fedora-Live-Workstation-x86_64-21-5.iso rootfstype=auto ro rd.live.image quiet rhgb rd.live.check initrd (loop)/isolinux/initrd0.img } With the workstation ISO set in my main directory of my USB drive (FAT32).
I posted a possible patch at http://www.syslinux.org/archives/2015-February/023209.html
Fedora 22 (Live Workstation x86_64) Alpha 3 hard resets after the kernel is loaded into memory, and before it executes, on a Chromebook. The syslinux patch listed above addresses the same symptom.
This also affects me on an Acer C720 (no touch). I've been told that custom firmware will fix the issue. I have tried to build an iso with the patch, but I'm making some mistakes somewhere. Other distros (Arch, Ubuntu deriv, Gentoo, DragonFly BSD and OpenBSD boot on the stock firmware. Shouldnt Fedora also work? If we are using a different version of syslinux, then do we need to create a spin that works with the stock firmware on Chromebooks? I will work on this if it's desired, but will need some help/guidance.
Testing Fedora-Server-netinst-x86_64-23_Alpha.iso and Fedora-Live-Xfce-x86_64-23_Alpha-2.iso on Acer C720 also has the same results, grub starts, after grub selection, vmlinuz is loaded, EDD probe starts and machine reboots. I tried passing nomodeset, boot: linux0, mem=1980M and all combinations of those boot parameters and all had the same results on the Live-Xfce image.
I have also tested F22-x86_64-MATE-20150806.iso and gotten the same results as noted above.
Per Zach Villers this affects 23 and Rawhide too, so bumping.
(In reply to S from comment #21) > I posted a possible patch at > http://www.syslinux.org/archives/2015-February/023209.html This patch got merged upstream[1], can we get it into f23? [1] http://repo.or.cz/syslinux.git/commit/0a2dbb3392ee710838bea6bda80d4daad6b54780
I did have success booting F23 beta using the dd method, no issue with mem parameter whatsoever. If I used the Gnome Disk Utility Restore Image procedure, the USB flash drive would hang on boot.
Just updating - installer crashes after EDD probe for today's downloads of rawhide and F23.
I just installed Fedora 23 workstation from an usb stick on my Chromebook Acer C720P without any problem. For information, I have flashed my bios several months ago using johnlewis.ie release !
I tried the 64bit F23 Live image on a C720, written to the USB stick with Gnome Disk Utility. It boots to the bootloader, I select to start Fedora and one or two seconds later it reboots and I'm back to the screen that tells me secure mode is off.
I have this problem too on my HP Chromebook 14.
Can we have an update on this problem please. It will be great if it can be fixed for Fedora 24. Thanks
I flashed my HP Chromebook 14 (Falco) with the Full ROM (instead of LEGACY_RW) from John Lewis and now I can boot and install Fedora.
Fedora works perfectly with the Full ROM but for those that can't, or don't want to install it, it will great if the bug can be fixed. Thanks.
I tried Fedora 24 Alpha and the problem is still here with Legacy RW. I don't know if the syslinux fix is merged into Fedora 24 Alpha.
The fix from comment 21 is included in Syslinux 6.04. I can confirm that it work. Can it be integrated on Fedora 24 ? Thanks, Jérémy
syslinux-6.03-8.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-34a172b2cf
Thank you Peter for backporting the needed fix ! We should be able to test it with the Fedora 24 beta if I'm right. And Peter, I don't know why you didn't answer any of my messages (here, email, mailing list) but again thanks !
syslinux-6.03-8.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-34a172b2cf
syslinux-6.03-8.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.
Still have problems with Fedora 24 Beta.
(In reply to Everaldo Canuto from comment #42) > Still have problems with Fedora 24 Beta. Not sure if syslinux-6.03-8.fc24 made it in Fedora 24 beta. If anyone know it ?
I have also tried rawhide 20160510 and same problem. We probably need to wait a couple of days before test again.
I just tried the latest ISO of Fedora 24 and Rawhide from here ( http://koji.fedoraproject.org/koji/tasks?state=all&view=tree&method=livemedia&order=-id ) and I can confirm that they work on my HP Chromebook 14 (Falco) with the stock firmware + Legacy RW from MattDevo ( https://github.com/MattDevo/scripts ) ! Thanks !
Using Fedora-Workstation-Live-x86_64-24-20160512.n.0.iso also works for me.