On Thu, Jan 22, 2015 at 1:56 PM, Fred Smith <fredex@xxxxxxxxxxxxxxxxxxxxxx> wrote: > On Wed, Jan 21, 2015 at 10:40:56PM -0700, Chris Murphy wrote: >> On Wed, Jan 21, 2015 at 10:28 PM, Fred Smith >> <fredex@xxxxxxxxxxxxxxxxxxxxxx> wrote: >> > On Wed, Jan 21, 2015 at 09:36:48PM -0700, Chris Murphy wrote: >> >> On Wed, Jan 21, 2015 at 6:12 PM, Fred Smith >> >> <fredex@xxxxxxxxxxxxxxxxxxxxxx> wrote: >> >> > I tried "yum reinstall" for all the kernel bits of the latest (non- >> >> > working) kernel, and it said "not available" for all but (I think >> >> > it was) headers. What does "not available" mean here? I mean, it had >> >> > just downloaded for installation a little while before, they've >> >> > disappeared in the meantime? >> >> >> >> It might be helpful to include the exact actual error message. Pretty >> > >> > It's a little hard to get without writing down by hand, unless there's >> > a way I don't know of to get panic dumps written out to a network >> > drive. >> > >> > there isn't really any distinct error message, just a panic dump >> > full of hexadecimal numbers. >> >> OK I quoted you above where you said "not available" in reference to >> doing yum reinstall. That should not produce a kernel panic and you >> didn't previously report that yum reinstall caused a kernel panic; you >> said booting caused a kernel panic. I'm not asking about the kernel >> panic, I'm asking about the yum reinstall error. You can tell I'm >> asking about the yum reinstall error because of what I quoted. So >> don't change contexts to the kernel panic when I didn't ask about the >> kernel panic. > > > OK, bypassing the yum reinstall errors,I simply booted from a f21 live > image and fsck-ed the whole drive, then booted up the last working > kernel and removed all the kernel*3.14.27*.rpm packages, rebooted, > did yum update and it installed the newer kernel, did a reboot and > find we're in business. sopmething mjust have failed in the original > install (whenit hung, for whatever unknown reason) and it took the > remove/update pair to be run to clean it up. > > thanks for helping clarify things in my (weak,apparently) mind! I'm glad it worked out. Perseverance is the primary repair tool. -- Chris Murphy -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx 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
