Hi,
I would be glad if someone could comment if you managed to run Fedora 23 live image on a Lenovo C540.
I find that when booting from the Fedora 23 live image the Lenovo C540 freezes.
I submitted a bug report in bugzilla too [1].
Thanks,
RM
[1] Live media/net install media cannot be booted for lenovo c540 regardless of uefi enabled or disabled https://bugzilla.redhat.com/show_bug.cgi?id=1303446
On Sun, 2016-01-31 at 17:55 -0200, Bernardo Sulzbach wrote:
In what stage does it freeze?
Hi Bernardo, thanks for writing. The system freezes after selecting "Start Fedora Live". The display is black with a blinking cursor on the top left of the screen. The CapsLock and NumLock no longer toggle the LEDs on the keyboard. I have to try again to remember if Ctrl-Alt-Del works.
I am just asking because installing Fedora on notebooks (at least for me) **never** was an easy task. It mostly has to do with BIOS settings.
I can't recall if I ran into the problem you describe, but it may be a local issue and not a bug per se, if you understand me.
Be warned that I am not a "Linux IT guy" (if I was I would have a better name for it) so dealing with BIOS and making bootable media is always a weird step for me, after the OS is running I know what I am doing a lot better.
Did you use this media on another machine? Did it boot correctly into the live session?
On Sun, 2016-01-31 at 19:11 -0200, Bernardo Sulzbach wrote:
Did you use this media on another machine? Did it boot correctly into the live session?
I had not used the media elsewhere and when I attempted it on other older machine a few minutes ago the boot failed too! I am now creating a USB device with the live image to try booting from a USB memory instead.
On Sun, 2016-01-31 at 22:30 +0000, R Mercado wrote:
On Sun, 2016-01-31 at 19:11 -0200, Bernardo Sulzbach wrote:
Did you use this media on another machine? Did it boot correctly into the live session?
I had not used the media elsewhere and when I attempted it on other older machine a few minutes ago the boot failed too! I am now creating a USB device with the live image to try booting from a USB memory instead
Hi, I am writing to report that booting from the USB disk I created failed to boot on the Lenovo C540. When selecting "Legacy only" boot in the BIOS, the result was a black screen with a blinking cursor at the top left. The keyboard LEDs did respond to CapsLock and NumLock though. When selecting "UEFI only" in the BIOS screens the PC attempted to start PXE boot over IPV4 and IPV6 but after skipping those, could not find a bootable disk. It did not find the bootable USB key....
My method of making a bootable USB disk was to use the script livecd-iso-to-disk from the Fedora 23 Live Image this way:
sudo ./livecd-iso-to-disk --format '/home/rmercado/Downloads/hj/Fedora -Live-Workstation-x86_64-23-10.iso' /dev/sdb1
Is this the correct method of generating a bootable USB disk?
Thanks,
RM
I've been used dd command to create my pendrives... Maybe it can be worthy...
# dd if=/home/rmercado/Downloads/hj/Fedora-Live-Workstation-x86_64-23-10.iso' of=/dev/sdb (not /dev/sdb*1*)
Wagner França Marques 954731643 970768470
2016-01-31 21:17 GMT-02:00 R Mercado r_mercado@o2.co.uk:
On Sun, 2016-01-31 at 22:30 +0000, R Mercado wrote:
On Sun, 2016-01-31 at 19:11 -0200, Bernardo Sulzbach wrote:
Did you use this media on another machine? Did it boot correctly into the live session?
I had not used the media elsewhere and when I attempted it on other older machine a few minutes ago the boot failed too! I am now creating a USB device with the live image to try booting from a USB memory instead
Hi, I am writing to report that booting from the USB disk I created failed to boot on the Lenovo C540. When selecting "Legacy only" boot in the BIOS, the result was a black screen with a blinking cursor at the top left. The keyboard LEDs did respond to CapsLock and NumLock though. When selecting "UEFI only" in the BIOS screens the PC attempted to start PXE boot over IPV4 and IPV6 but after skipping those, could not find a bootable disk. It did not find the bootable USB key....
My method of making a bootable USB disk was to use the script livecd-iso-to-disk from the Fedora 23 Live Image this way:
sudo ./livecd-iso-to-disk --format '/home/rmercado/Downloads/hj/Fedora -Live-Workstation-x86_64-23-10.iso' /dev/sdb1
Is this the correct method of generating a bootable USB disk?
Thanks,
RM
users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
On Sun, Jan 31, 2016, 4:18 PM R Mercado r_mercado@o2.co.uk wrote:
My method of making a bootable USB disk was to use the script livecd-iso-to-disk from the Fedora 23 Live Image this way:
sudo ./livecd-iso-to-disk --format '/home/rmercado/Downloads/hj/Fedora -Live-Workstation-x86_64-23-10.iso' /dev/sdb1
No, for UEFI it also needs --efi
Is more reliable to use:
--efi --reset-mbr --format
And point it at the whole device rather than an existing partition. This of course obliterates everything on the stick.
Chris Murphy
On Mon, 2016-02-01 at 13:06 -0200, Wagner Marques wrote:
I've been used dd command to create my pendrives... Maybe it can be worthy...
Thanks, I tried it and it's the documented method in the installation guide. I did not get the Lenovo C540 or the older Medion system to boot with the stick generated though. I will try Chris Murphy's suggestion next.
RM
I have now been able to validate the Live Fedora CD by booting it on an older machine. The Lenovo C540 does not boot with it though. Thanks to Chris Murphy's suggestions I also got a bootable USB stick.
The Lenovo picks up some of the boot code and comes to a menu where i can choose "Start Live CD", "Verify media and start live CD" and "Troubleshoot".
Selecting "start live CD" the machine shows a black screen with a blinking cursor at the top left and freezes. The keyboard NumLock/CapsLock LEDs stop responding to toggle. Ctrl-Alt-Del work when frozen.
I could not find Lenovo firmware updates to flash the BIOS.
I initially installed Fedora 20 on the Lenovo C540 and I remember the installation media used to work okay on it.
Thanks, RM
On 02/01/16 18:21, R Mercado wrote:
I have now been able to validate the Live Fedora CD by booting it on an older machine. The Lenovo C540 does not boot with it though. Thanks to Chris Murphy's suggestions I also got a bootable USB stick.
The Lenovo picks up some of the boot code and comes to a menu where i can choose "Start Live CD", "Verify media and start live CD" and "Troubleshoot".
This is the GRUB menu. You can choose which entry to boot, and also edit the boot command lines before you select one. So, if you need to add or remove kernel options, select the line with your cursor, and hit the "e" key.... If you read the screens, they should be mostly self explanatory.
Selecting "start live CD" the machine shows a black screen with a blinking cursor at the top left and freezes. The keyboard NumLock/CapsLock LEDs stop responding to toggle. Ctrl-Alt-Del work when frozen.
One of the things to remove would be the "rhgb" options, and possibly the "quiet" option as well (is that two options?) Then you can see what the startup is doing and you can then report back the last few messages on the console or some errors that happen during the boot up
I could not find Lenovo firmware updates to flash the BIOS.
I initially installed Fedora 20 on the Lenovo C540 and I remember the installation media used to work okay on it.
Another thing to try is to boot each Fedora Live image between FC20 and FC23 to try and see where the failure starts. Especially, if FC23 doesn't work, does FC22?
Thanks, RM
Hi. Thanks for writing.
One of the things to remove would be the "rhgb" options, and possibly the "quiet" option as well (is that two options?) Then you can see what the startup is doing and you can then report back the last few messages on the console or some errors that happen during the boot up
I tried removing rhgb and quite and there are no messages, only the blinking cursor as before.
Another thing to try is to boot each Fedora Live image between FC20 and FC23 to try and see where the failure starts. Especially, if FC23 doesn't work, does FC22?
I downloaded the netinst image for FC22 because it's not as large. Booting using this FC22 image freezes the Lenovo C540 as before.
I may download FC21 later. It takes a while to get 1.4 Gb on my link. Too bad I can't find the Fedora 20 image I had.
RM
On 02/02/16 17:51, R Mercado wrote:
I may download FC21 later. It takes a while to get 1.4 Gb on my link. Too bad I can't find the Fedora 20 image I had.
I have copies of both the Fedora-Live-Desktop for F20 if you need it, they're each just shy of 1GB. I can make them available at the drop of a hat. Yes, the F21 Desktop-Live-Workstation images are substantially larger (~1.4GB). And you have lots of choice as to which F23 Live image you want.
RM
I have copies of both the Fedora-Live-Desktop for F20 if you need it, they're each just shy of 1GB. I can make them available at the drop of a hat.
Hi Kevin, I now intend to use the link at work (tomorrow) to grab FC21 faster. If not too difficult, please do make available the FC20 installation media. Thanks for offering! Regards, RM
Just reading this now (sorry).
I'm adding the following:
http://kjchome.homeip.net/Fedora-Live-Desktop-i686-20 http://kjchome.homeip.net/Fedora-Live-Desktop-x86_64-20
should be links to the images. I got my images via BitTorrent so each directory should contain both an ISO file and a CHECKSUM file
Let me know if you have any problems.
On 02/02/16 19:09, R Mercado wrote:
I have copies of both the Fedora-Live-Desktop for F20 if you need it, they're each just shy of 1GB. I can make them available at the drop of a hat.
Hi Kevin, I now intend to use the link at work (tomorrow) to grab FC21 faster. If not too difficult, please do make available the FC20 installation media. Thanks for offering! Regards, RM
On Wed, 2016-02-03 at 19:11 -0500, Kevin Cummings wrote:
Just reading this now (sorry).
I'm adding the following:
http://kjchome.homeip.net/Fedora-Live-Desktop-i686-20 http://kjchome.homeip.net/Fedora-Live-Desktop-x86_64-20
Thanks for taking the trouble. I found the images at https://torrents.fedoraproject.org/ too. I can't get any image to boot of the USB disk and ran out of blank DVDs to try burning and booting from a DVD. I still have blank 700 MB CDs and very few images are small enough.
My intention was to do a clean install, but I am considering an upgrade now. RM
On Sat, 2016-02-06 at 07:33 +0000, R Mercado wrote:
On Wed, 2016-02-03 at 19:11 -0500, Kevin Cummings wrote:
Just reading this now (sorry).
I'm adding the following:
http://kjchome.homeip.net/Fedora-Live-Desktop-i686-20 http://kjchome.homeip.net/Fedora-Live-Desktop-x86_64-20
Thanks for taking the trouble. I found the images at https://torrents.fedoraproject.org/ too. I can't get any image to boot of the USB disk and ran out of blank DVDs to try burning and booting from a DVD. I still have blank 700 MB CDs and very few images are small enough.
My intention was to do a clean install, but I am considering an upgrade now. RM
What are the reasons you are not able to boot from USB; is this a new laptop, what are the errors you are getting? I had similar issues with booting but managed to find a work around.
On 02/06/2016 02:33 AM, R Mercado wrote:
Thanks for taking the trouble.
No trouble, just had to add 2 symlinks to my main page.
I found the images at https://torrents.fedoraproject.org/ too.
I stopped seeding those files shortly after they were obsoleted, but I keep all of my images.
I can't get any image to boot of the USB disk and ran out of blank DVDs to try burning and booting from a DVD. I still have blank 700 MB CDs and very few images are small enough.
My intention was to do a clean install, but I am considering an upgrade now.
FedoraProject has a nice page on doing yum/dnf upgrades. IIRC, its the 21->21 upgrade where you have to choose a "product name" if you use fedup. There was also a fedora-upgrade that you could use. Read the docs very carefully. If you choose the yum/dnf route, and your source system is old enough, there is always stuff you will need to do by hand (detailed in the pages).
Good Luck with that! I've spent many an hour fixing my home server by hand because "something" happened during the upgrade that caused me to have to run the transactions by hand, which can be a pain with 2-3 thousand packages installed. Luckily, I learn more about packages and dependencies every time I do it. Right now, my home server is stuck at FC20+, waiting for me to bring it up to 21, and then 22. I just have to find the right time when I can afford to be offline for a couple of days (just in case!), and that time is not now.
RM
On Sat, 06 Feb 2016 07:33:42 +0000 R Mercado r_mercado@o2.co.uk wrote:
On Wed, 2016-02-03 at 19:11 -0500, Kevin Cummings wrote:
Just reading this now (sorry).
I'm adding the following:
http://kjchome.homeip.net/Fedora-Live-Desktop-i686-20 http://kjchome.homeip.net/Fedora-Live-Desktop-x86_64-20
Thanks for taking the trouble. I found the images at https://torrents.fedoraproject.org/ too. I can't get any image to boot of the USB disk and ran out of blank DVDs to try burning and booting from a DVD. I still have blank 700 MB CDs and very few images are small enough.
My intention was to do a clean install, but I am considering an upgrade now. RM
You could try doing a pxe install. Here are a couple of links that describe the process. http://webworxshop.com/2011/08/21/installing-fedora-15-via-boot-fedoraprojec... https://boot.fedoraproject.org/faq
And the download page for the images. https://boot.fedoraproject.org/download
I used the lkrn image to try to install Rawhide (f24). It worked fine for getting the anaconda installer up and running twice, but rawhide is so inconsistent that there were failed dependencies in the installs I tried to download. The installs are probably kickstarter files. When they failed, the wholed process aborted. But, for a release version, this should not be an issue, since everything is stable and dependencies are met.
I did edit /boot/grub2/grub.cfg to put the BFO Boot entry after my regular boot, instead of making it the default.
What I liked is it didn't require any media, just booting the lkrn file.
Hi all,
Thanks for your replies.
I have just emerged from a Fedora 23 upgrade and my previous reports were not correct!
The CDs do boot when one chooses the non-UEFI option.
I have now created two partitions, one intended for rawhide and one for 23 (stable).
I can't yet explain why booting off a USB stick fails. I don't seem to be able to choose non-UEFI boot for the USB media.
Best wishes, RM
On Mon, Feb 8, 2016 at 2:10 PM, R Mercado r_mercado@o2.co.uk wrote:
Hi all,
Thanks for your replies.
I have just emerged from a Fedora 23 upgrade and my previous reports were not correct!
The CDs do boot when one chooses the non-UEFI option.
OK, this is not your fault, but be aware of two things: 1. "non-UEFI option" is a big fat lie, what it does is add another layer (a compatibility support module), so there can be more bugs than without it, but in any case your system now how even more differences in behavior than pretty much everyone else's; 2. not all computers have such an option. So to a lot of people, what you're describing above, makes no sense.
I have now created two partitions, one intended for rawhide and one for 23 (stable).
I can't yet explain why booting off a USB stick fails.
How are you creating the USB stick? How does it fail? The description "it fails" isn't helpful because it doesn't tell us what does happen. There's no way to know from this description whether it fails to find the bootloader (or which one, there's more than one possible).
I don't seem to be able to choose non-UEFI boot for the USB media.
Unsurprising (to me) that the CSM doesn't support USB booting. Any legacy OS, which is what the CSM is meant for, will boot from a CD.
On Mon, 2016-02-08 at 16:14 -0700, Chris Murphy wrote:
How are you creating the USB stick? How does it fail? The description "it fails" isn't helpful because it doesn't tell us what does happen. There's no way to know from this description whether it fails to find the bootloader (or which one, there's more than one possible).
Hi,
Thanks for writing.
The failure is described in https://bugzilla.redhat.com/show_bug.cgi?id =1303446
I generate the USB stick using
sudo ./livecd-iso-to-disk --efi --reset-mbr --format '/home/rmercado/Downloads/hj/Fedora-Live-Workstation-x86_64-23- 10.iso' /dev/sdb
The system freezes after showing a boot menu. It does indeed look like the UEFI boot menu is different to the non-UEFI menu, at least because the boot screen font looks like in a type of graphics mode (UEFI boot menu) instead of text mode (non-UEFI boot menu).
Josh Boyer offers to pursue this in rawhide/Fedora 24 images. I wonder if it is worthwhile.
Regards, RM
Fixing bugs is always worthwhile.
If neither Fedora 22 or 23 install media can be booted, but Ubuntu can, then i suspect it's not kernel related.
Do you get different results when you use dd to create installer media? That really is the most reliable way to create media. But also dd and livecd-iso-to-disk create very different install media. Both should work. But the three finger salute with litd appears to not work on your system for as yet unknown reasons.
My suggestion: - Create the installer media with dd - Find a reset to defaults option in the firmware setup, and reset the firmware. - Make sure you have the latest firmware version from the manufacturer. - When you get to the boot menu, the UEFI bootloader will be white text on a black background, and e is used to edit boot entries. A gray background or color text is the BIOS borrower, tab key edits boot entries. You really want the former, fewer layers.
- Select the first boot option, e to edit, navigate to the linuxefi line, find the parameters 'quiet rhgb' and delete them both. Then use with F10 or Ctrl-x to boot this edited entry. Removing those will show more text on screen, and maybe the failure cause becomes more obvious.
Also, report what does happen, rather than what doesn't.
Chris Murphy