RE: Updated to f20, but can only boot f19. [SOLVED]
> This is a Fedora - windows dual-boot system, 64-bit. > > This afternoon, I updated to Fedora-20 using fedup. But Fedora-20 is not offered in the boot window. > I see three options for Fedora-19, and a windows option. I can sign on to Fedora-19, but the left and > right screens are reversed! (This is a dual monitor system.) This is a home system. > > I'm not a sys. admin. How do I get this system to boot up Fedora-20? > > thanks, > Bill. After the most recent post on this, I realized a had more steps to do. 1. I needed to "grub2-install /dev/sda" as suggested by Michael J. Chudobiak. I've since done it. Thank-you, Mike. 2. I needed to do the post-update steps given in the F-20 fedup instructions. I've since done them. A couple issues remain, but I believe them to be unrelated to the original post. So I'm closing this. I'll post separate questions on those other issues. I thank all who helped me with this, especially Chris Murphy. Bill. -- 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
Re: Updated to f20, but can only boot f19.
Good evening, I followed Chris's suggestions. Thank-you, Chris. Here are relevant session portions: = bash.6[~]: grub2-install /dev/sda Installation finished. No error reported. bash.7[~]: - [edited /etc/default/grub. here are the new contents] GRUB_TIMEOUT=8 GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)" GRUB_DEFAULT=saved GRUB_CMDLINE_LINUX="rd.md=0 rd.lvm=0 rd.dm=0 $([ -x /usr/sbin/rhcrashkernel-para m ] && /usr/sbin/rhcrashkernel-param || :) rd.luks=0 vconsole.keymap=us rhgb qui et nouveau.modeset=0 rd.driver.blacklist=nouveau video=vesa:off" GRUB_DISABLE_RECOVERY="true" GRUB_THEME="/boot/grub2/themes/system/theme.txt" GRUB_GFXPAYLOAD_LINUX=text - bash.14[~]: grub2-mkconfig -o /boot/grub2/grub.cfg Generating grub.cfg ... Found theme: /boot/grub2/themes/system/theme.txt Found linux image: /boot/vmlinuz-3.12.8-200.fc19.x86_64 Found initrd image: /boot/initramfs-3.12.8-200.fc19.x86_64.img Found linux image: /boot/vmlinuz-3.12.7-200.fc19.x86_64 Found initrd image: /boot/initramfs-3.12.7-200.fc19.x86_64.img Found linux image: /boot/vmlinuz-3.12.6-200.fc19.x86_64 Found initrd image: /boot/initramfs-3.12.6-200.fc19.x86_64.img Found linux image: /boot/vmlinuz-0-rescue-70857e3fb05849139515e66a3fdc6b38 Found initrd image: /boot/initramfs-0-rescue-70857e3fb05849139515e66a3fdc6b38.img Found Windows 7 (loader) on /dev/sda1 done bash.15[~]: - bash.19[~]: fedup --network 20 --debuglog fedupdebug.log = I also ran the upgrade. I saw no signs of trouble. When the boot menu came back, Fedora-20 was at the top; it appeared to boot fine, and I signed in fine. So far, it looks like everything worked ok. The debug log is fpasted: bash.4[~]: fpaste fedupdebug.log Uploading (263.0KiB)... http://ur1.ca/ghn3f -> http://paste.fedoraproject.org/71198/28951139 bash.5[~]: I don't know how to determine whether my system is UEFI or BIOS. How do I do that? thanks, Bill. -- 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
Re: Updated to f20, but can only boot f19.
On Jan 22, 2014, at 6:18 PM, Chris Murphy wrote: >> >> Chris's part 1 raises another question. My system was new in March 2013. >> Fedora-18 was installed. Whatever grub came with that is the grub that was >> installed. > > No, Fedora 18 came with 2.00-13 not 1.99. So either the bootinfoscript has a > bug and is misidentifying the version of GRUB in the MBR (possible) or It's likely a bootinfoscript bug, looks like it slightly predates the release of 2.00. Any 2.00 installation is erroneously reported as 1.99. Does anyone know of a newer boot info script like thing? Chris Murphy -- 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
Re: Updated to f20, but can only boot f19.
On Jan 22, 2014, at 4:55 PM, William Mattison wrote: > Joe asks: > > > > And I did "fedup --network 20". > > > > Have you run the upgrade yet? > > Yes, I did that Monday afternoon. I did not watch it continually, but I saw > no indication of trouble until the boot screen came up with no Fedora-20. > > Important question... Given my answer above, is what Chris advises... > > > 1. > > > > "Grub2 (v1.99) is installed in the MBR…" > > > > Why has this never been updated? I have to go back to Fedora 16 to find a > > GRUB this old. Since what's in the MBR points to > > core.img at sector 1, and the first partition starts at LBA 2048, it's safe > > to have Fedora 19 reinstall grub. I would replace it: > > > > grub2-install /dev/sda > > > > 2. > > I'd also replace the grub.cfg with one created by grub2-mkconfig: > > > > grub2-mkconfig -o /boot/grub2/grub.cfg > > > > It appears you have custom boot parameters "nouveau.modeset=0 > > rd.driver.blacklist=nouveau video=vesa:off" in which case you > > should have edited /etc/default/grub and added those boot parameters to > > GRUB_CMDLINE_LINUX=. If you haven't, do that > > before running grub2-mkconfig so that those boot options get picked up in > > the new grub.cfg. > > > > > > And I did "fedup --network 20". > > > > Try: > > > > fedup --network 20 --debuglog fedupdebug.log > > > > Before rebooting, confirm that fedup says it's ready for you to reboot the > > system, and then fpaste the fedupdebug.log (or pastebin it). > > > > Chris Murphy > > … still the proper things to do? What's the question? > > Chris's part 1 raises another question. My system was new in March 2013. > Fedora-18 was installed. Whatever grub came with that is the grub that was > installed. No, Fedora 18 came with 2.00-13 not 1.99. So either the bootinfoscript has a bug and is misidentifying the version of GRUB in the MBR (possible) or in fact it has the wrong version of GRUB on it. Anyway, I'd blow it away as suggested. > I ran "yum update" every week. In July or August, I updated to Fedora-19. > I continue to run "yum update" every week. So why is my grub so out-of date? > Doesn't the "yum update" take care of that? On UEFI yes. On BIOS no. On BIOS the package is updated, but unless you grub2-install, none of the package contents are used to create all grub modules, bake the necessary ones into a new core.img, and embed that in the MBR gap or BIOS Boot partition. On UEFI, we all get the same prebake grubx64.efi that's in the package, there is no use for grub2-install on EFI (it can be done on non-Secure Boot systems, but it'll behave differently than the prebaked one that comes in the package). > By the way, I don't recall doing anything to customize my grub boot > parameters. Could this have something to do with this being a dual-boot > system? No, the other system is Windows. Are we sure you're using the grub.cfg that bootinfoscript reported? Reboot your computer, at the grub menu type e to edit the first entry, and look for the linux line of parameters and see if it includes "nouveau.modeset=0 rd.driver.blacklist=nouveau video=vesa:off". Something added that either directly to grub.cfg or to /etc/grub/default. While you're at it, just check /etc/grub/default for its GRUB_CMDLINE_LINUX= Chris Murphy -- 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
Re: Updated to f20, but can only boot f19.
Joe asks: > > And I did "fedup --network 20". > > Have you run the upgrade yet? Yes, I did that Monday afternoon. I did not watch it continually, but I saw no indication of trouble until the boot screen came up with no Fedora-20. Important question... Given my answer above, is what Chris advises... > 1. > > "Grub2 (v1.99) is installed in the MBR…" > > Why has this never been updated? I have to go back to Fedora 16 to find a GRUB this old. Since what's in the MBR points to > core.img at sector 1, and the first partition starts at LBA 2048, it's safe to have Fedora 19 reinstall grub. I would replace it: > > grub2-install /dev/sda > > 2. > I'd also replace the grub.cfg with one created by grub2-mkconfig: > > grub2-mkconfig -o /boot/grub2/grub.cfg > > It appears you have custom boot parameters "nouveau.modeset=0 rd.driver.blacklist=nouveau video=vesa:off" in which case you > should have edited /etc/default/grub and added those boot parameters to GRUB_CMDLINE_LINUX=. If you haven't, do that > before running grub2-mkconfig so that those boot options get picked up in the new grub.cfg. > > > And I did "fedup --network 20". > > Try: > > fedup --network 20 --debuglog fedupdebug.log > > Before rebooting, confirm that fedup says it's ready for you to reboot the system, and then fpaste the fedupdebug.log (or pastebin it). > > Chris Murphy ... still the proper things to do? Chris's part 1 raises another question. My system was new in March 2013. Fedora-18 was installed. Whatever grub came with that is the grub that was installed. I ran "yum update" every week. In July or August, I updated to Fedora-19. I continue to run "yum update" every week. So why is my grub so out-of date? Doesn't the "yum update" take care of that? By the way, I don't recall doing anything to customize my grub boot parameters. Could this have something to do with this being a dual-boot system? thanks, Bill. -- 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
Re: Updated to f20, but can only boot f19.
On Jan 21, 2014, at 11:00 PM, Chris Murphy wrote: > > Before rebooting, confirm that fedup says it's ready for you to reboot the > system, and then fpaste the fedupdebug.log (or pastebin it). And for that matter if it says you can reboot, go ahead. You should have something like an "System Update (Fedup)" in the GRUB menu. Chris Murphy -- 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
Re: Updated to f20, but can only boot f19.
On Jan 21, 2014, at 7:44 PM, William wrote: > > > The url is "pastebin.com/tGhLuhJt" > 1. "Grub2 (v1.99) is installed in the MBR…" Why has this never been updated? I have to go back to Fedora 16 to find a GRUB this old. Since what's in the MBR points to core.img at sector 1, and the first partition starts at LBA 2048, it's safe to have Fedora 19 reinstall grub. I would replace it: grub2-install /dev/sda 2. I'd also replace the grub.cfg with one created by grub2-mkconfig: grub2-mkconfig -o /boot/grub2/grub.cfg It appears you have custom boot parameters "nouveau.modeset=0 rd.driver.blacklist=nouveau video=vesa:off" in which case you should have edited /etc/default/grub and added those boot parameters to GRUB_CMDLINE_LINUX=. If you haven't, do that before running grub2-mkconfig so that those boot options get picked up in the new grub.cfg. > And I did "fedup --network 20". Try: fedup --network 20 --debuglog fedupdebug.log Before rebooting, confirm that fedup says it's ready for you to reboot the system, and then fpaste the fedupdebug.log (or pastebin it). Chris Murphy -- 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
Re: Updated to f20, but can only boot f19.
On 01/21/2014 06:44 PM, William wrote: And I did "fedup --network 20". Have you run the upgrade yet? -- 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
Re: Updated to f20, but can only boot f19.
On Jan 20, 2014, at 7:25 PM, William https://admin.fedoraproject.org/mailman/listinfo/users>> wrote: Sorry for the delay in responding; I've been down with a bug. >/ /> >/ Thank-you Chris. I did as suggested. I posted the results in "pastebin.com" under the username "wcmpaste", > and the text is named "bootinfoscript results". /> I can't find it with that information. It should have given you a URL you can post. >/ By the way, that took quite a lot of copy-and-paste operations. Is there a way to just upload the file? /> Yeah fpaste, but it has a pretty small size limit. Chris Murphy The url is "pastebin.com/tGhLuhJt" Found the "fpaste". Thank-you, Ed. I'll try to keep it in mind. What is the size limit? I didn't see one mentioned in the man page, You should be able to drag and drop the monitor icons around into the order that you want, in the displays properties configurator. Thank-you, Tim. That partially solved the problem. At least now I can get the cursor from one monitor to the other the short way. rpm -q kernel, to see if you have an *fc20* kernel Thank-you, Frank. Here's what I get: bash.2[~]: rpm -q kernel kernel-3.12.6-200.fc19.x86_64 kernel-3.12.7-200.fc19.x86_64 kernel-3.12.8-200.fc19.x86_64 bash.3[~]: No f20 kernel! Why? I have the correct fedup: bash.3[~]: rpm -q fedup fedup-0.8.0-3.fc20.noarch bash.4[~]: And I did "fedup --network 20". Bill. -- 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
Re: Updated to f20, but can only boot f19.
Allegedly, on or about 20 January 2014, William sent: > I can sign on to Fedora-19, but the left and right > screens are reversed! (This is a dual monitor system.) You should be able to drag and drop the monitor icons around into the order that you want, in the displays properties configurator. -- [tim@localhost ~]$ uname -rsvp Linux 3.9.10-100.fc17.x86_64 #1 SMP Sun Jul 14 01:31:27 UTC 2013 x86_64 All mail to my mailbox is automatically deleted, there is no point trying to privately email me, I will only read messages posted to the public lists. George Orwell's '1984' was supposed to be a warning against tyranny, not a set of instructions for supposedly democratic governments. -- 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
Re: Updated to f20, but can only boot f19.
On Mon, 20 Jan 2014 16:37:56 -0500 William wrote: > This is a Fedora - windows dual-boot system, 64-bit. > > This afternoon, I updated to Fedora-20 using fedup. But Fedora-20 is > not offered in the boot window. rpm -q kernel, to see if you have an *fc20* kernel ___ Regards, Frank www.frankly3d.com -- 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
Re: Updated to f20, but can only boot f19.
On 01/20/2014 04:37 PM, William wrote: This is a Fedora - windows dual-boot system, 64-bit. This afternoon, I updated to Fedora-20 using fedup. But Fedora-20 is not offered in the boot window. Sometimes I've had to update the grub selections manually, using: grub2-mkconfig -o /boot/grub2/grub.cfg grub2-install /dev/sda Not for the faint of heart, however. Beware. - Mike -- 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
Re: Updated to f20, but can only boot f19.
On Jan 20, 2014, at 7:25 PM, William wrote: > > Thank-you Chris. I did as suggested. I posted the results in "pastebin.com" > under the username "wcmpaste", and the text is named "bootinfoscript > results". I can't find it with that information. It should have given you a URL you can post. > By the way, that took quite a lot of copy-and-paste operations. Is there a > way to just upload the file? Yeah fpaste, but it has a pretty small size limit. Chris Murphy -- 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
Re: Updated to f20, but can only boot f19.
On 01/21/14 10:25, William wrote: > Thank-you Chris. I did as suggested. I posted the results in "pastebin.com" > under the username "wcmpaste", and the text is named "bootinfoscript > results". By the way, that took quite a lot of copy-and-paste operations. > Is there a way to just upload the file? Use fpaste. man fpaste -- Getting tired of non-Fedora discussions and self-serving posts -- 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
Re: Updated to f20, but can only boot f19.
> > This is a Fedora - windows dual-boot system, 64-bit. > > > > This afternoon, I updated to Fedora-20 using fedup. But Fedora-20 is not offered in the boot window. > > I see three options for Fedora-19, and a windows option. I can sign on to Fedora-19, but the left and > > screens are reversed! (This is a dual monitor system.) This is a home system. > > > > I'm not a sys. admin. How do I get this system to boot up Fedora-20? > > No idea. Let's see the partition layout for the drive and the grub.cfg. You can download this script from > F19, run it, and post the resulting file it produces somewhere like pastebin. > > http://sourceforge.net/projects/bootinfoscript/ > > Chris Murphy Thank-you Chris. I did as suggested. I posted the results in "pastebin.com" under the username "wcmpaste", and the text is named "bootinfoscript results". By the way, that took quite a lot of copy-and-paste operations. Is there a way to just upload the file? thanks, Bill. -- 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
Re: Updated to f20, but can only boot f19.
On Jan 20, 2014, at 2:37 PM, William wrote: > This is a Fedora - windows dual-boot system, 64-bit. > > This afternoon, I updated to Fedora-20 using fedup. But Fedora-20 is not > offered in the boot window. I see three options for Fedora-19, and a windows > option. I can sign on to Fedora-19, but the left and right screens are > reversed! (This is a dual monitor system.) This is a home system. > > I'm not a sys. admin. How do I get this system to boot up Fedora-20? No idea. Let's see the partition layout for the drive and the grub.cfg. You can download this script from F19, run it, and post the resulting file it produces somewhere like pastebin. http://sourceforge.net/projects/bootinfoscript/ Chris Murphy -- 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
