[olug] upgrading to Fedora 21 - smoothest one in a while

[Jon Larsen]

I used fedup to upgrade my laptop and desktop (as I have with the previous
two versions).

My laptop is working okay.  I had a graphics issue with 3.17.4 on the
laptop when using the built in intel and external USB displaylink adapter.
That appears resolved in 3.17.6.

On my desktop, with 3.17.4, I didn't have any sound.  The sound card is
listed in lspci, but no kernel modules get loaded to support the card.
This was resolved by running the 3.17.6 kernel (lsmod|grep snd shows the
modules).  Oddly enough, I did get 3.17.6 installed but it wasn't the
default kernel in grub at boot, 3.17.4 was, so I had to edit the
/etc/default/grub file and set GRUB_DEFAULT=0 (it was =saved).  That may
have been a product of the upgrade, or when I removed the older fedora 20
kernels.

Jon L.

On Sun, Dec 14, 2014 at 9:11 AM, Samuel W. Flint <swflint at flintfam.org>
wrote:
>
> It turns out it was as simple as 3.17.4 not liking it, I switched to
> 3.17.6 and it worked fine.
>
> Samuel W. Flint
> Please forgive any typos as this was composed on a screen keyboard.
>
> > On Dec 14, 2014, at 7:57 AM, Samuel W. Flint <swflint at flintfam.org>
> wrote:
> >
> > I should mention that they work in kernel 3.16, bit don't in 3.17.
> >
> > Samuel W. Flint
> > Please forgive any typos as this was composed on a screen keyboard.
> >
> >> On Dec 14, 2014, at 7:47 AM, Samuel W. Flint <swflint at flintfam.org>
> wrote:
> >>
> >> Management scripts for the two interfaces.  all it has is a bridge
> adapter. Also, it looks like it doesn't have the various drivers installed
> fir some reason.
> >>
> >> Samuel W. Flint
> >> Please forgive any typos as this was composed on a screen keyboard.
> >>
> >>> On Dec 14, 2014, at 3:21 AM, Lou Duchez <lou at paprikash.com> wrote:
> >>>
> >>> I found this article:
> >>>
> >>>
> http://fedoraproject.org/wiki/Features/SystemdPredictableNetworkInterfaceNames
> >>>
> >>> Apparently, the issue is, when Linux boots it auto-detects network
> devices and assigns them values of "eth0", "eth1", etc in whatever order it
> detects them.  Or at least that's what it used to do; Fedora is moving away
> from that because you can't guarantee which order it's going to detect them
> in.  So devices these days tend to have names like "eno1" or "enp5s2", all
> BIOS-related so they theoretically can't change.
> >>>
> >>> What do you get when you run "ls -l
> /etc/sysconfig/network-scripts/ifcfg-*"?
> >>>
> >>>
> >>>
> >>>> Ok, so I did this on my laptop, and it now will not connect to any
> network, much less recognize the network chipsets.  They show up in lspci,
> but don't have entries in /dev.
> >>>>
> >>>> Any ideas?
> >>>>
> >>>> Samuel W. Flint
> >>>> Please forgive any typos as this was composed on a screen keyboard.
> >>>>
> >>>>> On Dec 12, 2014, at 9:14 PM, Lou Duchez <lou at paprikash.com> wrote:
> >>>>>
> >>>>> So it's Fedora upgrade time again; I've upgraded a half dozen
> servers without any hitches.  The process I've been following:
> >>>>>
> >>>>> 1) "yum update" to make sure you're up to date on your Fedora 20.
> >>>>>
> >>>>> 2) "package-cleanup --leaves" and "package-cleanup --orphans" to
> find any packages that yum doesn't quite know what to do with.  Then run
> "yum remove ________" to get rid of all those packages.
> >>>>>
> >>>>> 3) "yum clean all"
> >>>>>
> >>>>> 4) "yum --releasever=21 distro-sync"*
> >>>>>
> >>>>> 5) This is a new wrinkle: Fedora 21 now comes in three basic
> products, "workstation", "cloud", and "server".  So you are now to run one
> of the four following commands to pick which of the three products you want:
> >>>>>
> >>>>>  yum install system-release-workstation
> >>>>>  yum install system-release-cloud
> >>>>>  yum install system-release-server
> >>>>>  yum install system-release-nonproduct
> >>>>>
> >>>>>  I went with "nonproduct".
> >>>>>
> >>>>> 6) Figure out which device you boot from, by running this command:
> >>>>>
> >>>>>  df | grep "/boot$" | cut -f 1 -d " "
> >>>>>
> >>>>>  It will probably return something like "/dev/sda1", which is
> actually a partition and not a device.  But in this case, the device is
> "/dev/sda".
> >>>>>
> >>>>> 7) Run "grub2-install BOOTDEVICE" (which would be the device from
> the previous step)
> >>>>>
> >>>>> 8) Reboot!  If your experience is anything like mine, your server
> will come right up without any problems.
> >>>>>
> >>>>>
> >>>>> *: One thing I like to do is, after yum has downloaded all the
> version 21 files it needs and has started installing them, I hit Ctrl-Z and
> then run "bg" to make yum run in the background.  That way, even if my SSH
> session gets disconnected, there's still a pretty good chance that yum can
> and will run to completion, rather than screeching to a halt halfway
> through.
> >>>>>
> >>>>>
> >>>>> _______________________________________________
> >>>>> OLUG mailing list
> >>>>> OLUG at olug.org
> >>>>> https://lists.olug.org/mailman/listinfo/olug
> >>>> _______________________________________________
> >>>> OLUG mailing list
> >>>> OLUG at olug.org
> >>>> https://lists.olug.org/mailman/listinfo/olug
> >>>
> >>> _______________________________________________
> >>> OLUG mailing list
> >>> OLUG at olug.org
> >>> https://lists.olug.org/mailman/listinfo/olug
> >> _______________________________________________
> >> OLUG mailing list
> >> OLUG at olug.org
> >> https://lists.olug.org/mailman/listinfo/olug
> > _______________________________________________
> > OLUG mailing list
> > OLUG at olug.org
> > https://lists.olug.org/mailman/listinfo/olug
> _______________________________________________
> OLUG mailing list
> OLUG at olug.org
> https://lists.olug.org/mailman/listinfo/olug
>