Mike Chambers wrote: > Maybe you need to boot up into rescue mode and reinstall grub? I've had > to do that a few times during fresh installs lately. That had already occurred to me. How do I select rescue mode, when I cannot even get the grub menu? I the tried, from grub rescue, typing set root=(hd0,1) and on another line trying linux16 /boot/vmlinuz... but there is no way for me to determine the exact name of the kernel. Just as an experiment, I tried cat (hd0,1)/boot/grub2/grub.cfg but cat is not recognized, etc. I think access to all of the files on the drive are blocked, so even were I to deduce their names correctly, I would not be able to access them.

Chris Murphy wrote: > On Sat, May 7, 2016 at 7:48 PM, P. Gueckel <pgueckel(a)gmail.com&gt; wrote: >> Mike Chambers wrote: >> >>> Maybe you need to boot up into rescue mode and >> reinstall grub? I've had >>> to do that a few times during fresh installs lately. >> >> That had already occurred to me. How do I select >> rescue mode, when I cannot even get the grub menu? I >> the tried, from grub rescue, typing set root=(hd0,1) >> and on another line trying linux16 /boot/vmlinuz... >> but there is no way for me to determine the exact name >> of the kernel. Just as an experiment, I tried cat >> (hd0,1)/boot/grub2/grub.cfg but cat is not recognized, >> etc. I think access to all of the files on the drive >> are blocked, so even were I to deduce their names >> correctly, I would not be able to access them. > > It may be one of the TPM related patches for GRUB. I suggest filing a > bug, as during the entire pre-release testing of beta no one ran into > this and the more information that's collected about the problem the > better off Fedora is for final release. Include in the bug cc: > mjg59(a)srcf.ucam.org > > More info on TPMs and measured boot. > http://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.or... > > After that, you can probably fix this by booting any media you have > and putting the new system in a chroot: > mount <devrootfs> /mnt > mount <devboot> /mnt/boot > mount -B /sys /mnt/sys > mount -B /dev /mnt/dev > mount -B /proc /mnt/proc > chroot /mnt > curl -Os > https://kojipkgs.fedoraproject.org//packages/grub2/2.02/0.25.fc23/x86_64/... > & curl -Os > https://kojipkgs.fedoraproject.org//packages/grub2/2.02/0.25.fc23/x86_64/... > & curl -Os > https://kojipkgs.fedoraproject.org//packages/grub2/2.02/0.25.fc23/x86_64/... > & dnf downgrade *rpm > grub2-install /dev/sdX > exit > reboot > > Seems like it ought to be easier but that's what I'm thinking off off > hand. > > Hey, thanks! If its that long and complicated, it has to work ;-) I've been at this literally since breakfast, so I think I'll call it a day for tonight, but I will give that a try and file the bug report, too. I'll include your email address in the CCs. Merci a lot. I sure hope it works! That old laptop is still as good as new, practically. I'd hate it to be bricked. I suppose I could go back to F23, if TPM hasn't gotten hardware switched somehow.

The firmware is ancient. I haven't had windows (XP) since about 2000.

I haven't ever managed to figure out how to do BIOS updates in Linux. Is it possible?

Felix Miata wrote: > There probably isn't a motherboard in existence

a BIOS that old that > does not require a genuine DOS boot to update its BIOS. That should be no > impediment to any Linux user, as DOS boot media to facilitate flashing are > readily available. e.g. from http://www.bootdisk.com/ I've checked out that site before, but it's been a while. I just wasn't sure whether I wanted to risk

open source BIOS, or do they have loaders for the original BIOS updates from the manufacturers? I'd

to give it a try some time... but first I have to

this TPM solved ;-) > Mike Chambers wrote: > It's increasingly possible with fwupdate but it requires manufacturer > support for it, pretty sure. Anyway, most manufacturers have a FreeDOS > based image that can be used to flash the BIOS. If you have to have > Windows to do this, probably forget it because that means starting > over - that installer will obliterate the drive contents. > But before worrying about the firmware, find out whether you have the > latest version or not and include that information in the bug report. > And check the changelogs. If none of the versions since what you have > fix anything related to TPM then it may not even be relevant. I'd noticed fwupdate in the repo, but I think there were some warnings, so I thought I better leave well enough alone. One day, I would like to give it a

since I don't want to be forced into the Windows environment to perform basic system maintenance. Thanks for the ideas.

Chris Murphy wrote: > You might check if > the firmware is current. The firmware is ancient. I haven't had windows (XP) since about 2000. I haven't ever managed to figure out how to do BIOS updates in Linux. Is it possible?

Have you had a chance to file a bug about this yet?