I did the preupgrade yesterday on three machines without issue. On my laptop, though, I'm having a problem with shutting the laptop down now. It's a Lenovo W510+ and, during the shutdown process, when it switches to text I see an error (don't remember the exact text offhand) about shutdown having a problem. Then the laptop just stops and the CapsLock light starts blinking. At this point I have to power down the old Irish way by holding the power button. Anybody else hitting this?

Darryl L. Pierce wrote: > I did the preupgrade yesterday on three machines without issue. > > On my laptop, though, I'm having a problem with shutting the laptop down > now. It's a Lenovo W510+ and, during the shutdown process, when it > switches to text I see an error (don't remember the exact text offhand) > about shutdown having a problem. Then the laptop just stops and the > CapsLock light starts blinking. At this point I have to power down the > old Irish way by holding the power button. > > Anybody else hitting this?

No, but it sounds like a kernel panic.

You should try hitting the escape key during shut down or boot with "norhgb" (maybe even add "nomodeset") to stop plymouth from hiding any kernel output.

>No, but it sounds like a kernel panic. In my case, it was an obvious kernel panic. AFAIS, the cause was running a Fedora 16 kernel underneath of Fedora 17. Preupgrade (rsp. yum and/or grub underneath) obviously did not upgrade grub2.cfg to boot into the Fedora 17 kernel. For me, rebooting into the F17 installation with the F16 kernel underneath and then explicitly removing and reinstalling the fc17-kernel fixed this issue: # rpm -qa 'kernel-PAE*' kernel-PAE-3.3.7.fc17.i386 kernel-PAE-3.3.7.fc16.i386

On Fri, Jun 01, 2012 at 08:53:59AM -0400, Darryl L. Pierce wrote: > On Fri, Jun 01, 2012 at 04:28:01AM +0200, Ralf Corsepius wrote: >> >No, but it sounds like a kernel panic. >> In my case, it was an obvious kernel panic. >> >> AFAIS, the cause was running a Fedora 16 kernel underneath of Fedora >> 17. Preupgrade (rsp. yum and/or grub underneath) obviously did not >> upgrade grub2.cfg to boot into the Fedora 17 kernel. >> >> For me, rebooting into the F17 installation with the F16 kernel >> underneath and then explicitly removing and reinstalling the >> fc17-kernel fixed this issue: >> >> # rpm -qa 'kernel-PAE*' >> kernel-PAE-3.3.7.fc17.i386 >> kernel-PAE-3.3.7.fc16.i386 > > Hrm, for me I still have an F16 kernel that seems to be eclipsing the > F17 kernel: > > mcpierce@mcpierce-laptop:~ $ rpm -qa kernel > kernel-3.3.7-1.fc16.x86_64 > kernel-3.3.7-1.fc17.x86_64 > kernel-3.3.6-3.fc16.x86_64 > > mcpierce@mcpierce-laptop:~ $ uname -r > 3.3.7-1.fc16.x86_64 > > > -- > Darryl L. Pierce, Sr. Software Engineer @ Red Hat, Inc. > Delivering value year after year. > Red Hat ranks #1 in value among software vendors. > http://www.redhat.com/promo/vendor/ > > -- > users mailing list > users(a)lists.fedoraproject.org > To unsubscribe or change subscription options: > https://admin.fedoraproject.org/mailman/listinfo/users > Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines > Have a question? Ask away: http://ask.fedoraproject.org ### End of Message from Darryl L. Pierce ### I also had problems doing an upgrade from F16 to F17 with old kernels laying around. I though it was because I was using grub2+UEFI so the installer couldn't find the grub.conf file. I hand-edited, and haven't had any problems, since, except, I expect the first Kernel upgrade that comes along will also not find my grub.conf. I've probably completely setup my boot loader wrongly, but I suppose that a matter for a separate thread.

>>Hrm, for me I still have an F16 kernel that seems to be eclipsing the >>F17 kernel: >> >>mcpierce@mcpierce-laptop:~ $ rpm -qa kernel >>kernel-3.3.7-1.fc16.x86_64 >>kernel-3.3.7-1.fc17.x86_64 >>kernel-3.3.6-3.fc16.x86_64 >> >>mcpierce@mcpierce-laptop:~ $ uname -r >>3.3.7-1.fc16.x86_64 >> >>-- >>Darryl L. Pierce, Sr. Software Engineer @ Red Hat, Inc. > >I also had problems doing an upgrade from F16 to F17 with old kernels >laying around. I though it was because I was using grub2+UEFI so the >installer couldn't find the grub.conf file. I hand-edited, and haven't >had any problems, since, except, I expect the first Kernel upgrade that >comes along will also not find my grub.conf. > >I've probably completely setup my boot loader wrongly, but I suppose >that a matter for a separate thread. I have the same thing, F16 kernel with F17. Panics during shutdown. Can you provide specifics on how you "hand-edited?" -- Tim Evans, TKEvans.com, Inc. | 5 Chestnut Court

On Fri, Jun 01, 2012 at 03:30:28PM +0200, Ralf Corsepius wrote: > On 06/01/2012 02:53 PM, Darryl L. Pierce wrote: >> On Fri, Jun 01, 2012 at 04:28:01AM +0200, Ralf Corsepius wrote: >>>> No, but it sounds like a kernel panic. >>> In my case, it was an obvious kernel panic. >>> >>> AFAIS, the cause was running a Fedora 16 kernel underneath of Fedora >>> 17. Preupgrade (rsp. yum and/or grub underneath) obviously did not >>> upgrade grub2.cfg to boot into the Fedora 17 kernel. >>> >>> For me, rebooting into the F17 installation with the F16 kernel >>> underneath and then explicitly removing and reinstalling the >>> fc17-kernel fixed this issue: >>> >>> # rpm -qa 'kernel-PAE*' >>> kernel-PAE-3.3.7.fc17.i386 >>> kernel-PAE-3.3.7.fc16.i386 >> >> Hrm, for me I still have an F16 kernel that seems to be eclipsing the >> F17 kernel: > > Presence of an fc16 kernel should not matter and not disturb. > > Did you try what I wrote? > > What I did was to remove the fc17 kernel and to re-install it.This > fixed the broken grub2.cfg for me. That is what I did. I knocked out the 3.3.7-1 kernel from both 16 and 17, then installed the 3.3.7-1 F17 kernel and booted. I haven't tried shutting down yet but will by end of day. > >> mcpierce@mcpierce-laptop:~ $ rpm -qa kernel >> kernel-3.3.7-1.fc16.x86_64 >> kernel-3.3.7-1.fc17.x86_64 >> kernel-3.3.6-3.fc16.x86_64 >> >> mcpierce@mcpierce-laptop:~ $ uname -r >> 3.3.7-1.fc16.x86_64 > Once you're running an fc17 kernel, you can remove all these.

Tim Evans wrote: > My repo config must not have been reset for fc17 by preupgrade. Having > removed the fc17 kernel, yum cannot find it to (re)install--only sees > fc16 ones. Please do not hijack threads. Start a new thread for your problem.