no login after update to kernel -3.7.6-102 - Page 2
FedoraForum.org - Fedora Support Forums and Community
Page 2 of 2 FirstFirst 1 2
Results 16 to 27 of 27
  1. #16
    Join Date
    Oct 2011
    Posts
    141
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: no login after update to kernel -3.7.6-102

    Quote Originally Posted by JValeck
    You also mentioned 'Open the terminal. [Super]+terminal in Gnome 3' What is this ?
    Hi,

    It was just that you had mentioned running commands using the run dialogue [alt]+F2

    So I was suggesting using a terminal - the "command prompt" in Windows - so you could get the output of the commands.

    Since you've just copied and pasted the output into the thread I would say that is not a problem.

    OK in a step by step breakdown of the only course of action I can think of (just saying explicitly what I've already said which is really just what is said in the NVidia thread).

    Code:
    su -l
    yum remove akmod-nvidia kmod-nvidia xorg-drv-x11-nvidia xorg-x11-drv-nvidia-libs xorg-x11-drv-nvidia-libs.i686
    yum update
    systemctl reboot
    
    # restart computer and load latest kernel then open the terminal (command prompt)
    
    su -l
    yum install akmod-nvidia xorg-x11-drv-nvidia-libs.i686
    mv /boot/initramfs-$(uname -r).img /boot/initramfs-$(uname -r)-nouveau.img
    dracut /boot/initramfs-$(uname -r).img $(uname -r)
    systemctl reboot
    
    # reboot into hopefully working latest kernel with NVidia drivers installed
    Hopefully there wont be any problems starting without the NVidia drivers installed. If there is you may need to enable recovery mode then boot into that to continue. I said how to do that in an earlier post in this thread so wont repeat it here.

    I'm afraid that if that doesn't work I'm out of ideas.

  2. #17
    Join Date
    Jan 2010
    Location
    Vernonia, Oregun
    Posts
    122
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: no login after update to kernel -3.7.6-102

    I did the code you suggested but was never able to run kernel 102 had to keep selecting 101 to boot.
    When allowed to run the latest kernel 3.7.3-102.fc17.x86_64 the system hung before getting to the login prompt.

    Hung at Starting Sendmail Mail Transport Client...



    Do you think it is possible that kernel 3.7.3-102.fc17.x86_64 is somehow corrupted ?
    If so, can I use yum to uninstall it ?

    I have attached a txt file with the responses to the commands, perhaps you can take a look?

    Thanks,
    Val
    Attached Files Attached Files
    Fedora 19 64bit (Installed Dec. 2013)
    Memory 3Gb
    Video nVidia GeForce 9800GT 512Mb DDR3, CPU AMD Phenom 9550
    Disk Samsung HD103SJ 1Tb 3Gb/s (Installed April 2010)

  3. #18
    Join Date
    Oct 2011
    Posts
    141
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: no login after update to kernel -3.7.6-102

    Quote Originally Posted by JValeck
    I did the code you suggested but was never able to run kernel 102 had to keep selecting 101 to boot.
    When allowed to run the latest kernel 3.7.3-102.fc17.x86_64 the system hung before getting to the login prompt.

    Hung at Starting Sendmail Mail Transport Client...



    Do you think it is possible that kernel 3.7.3-102.fc17.x86_64 is somehow corrupted ?
    If so, can I use yum to uninstall it ?

    I have attached a txt file with the responses to the commands, perhaps you can take a look?

    Thanks,
    Val
    What I'm not getting is how you are on version 3.7.3-102 after a "yum update". F17 (I'm assuming you are using 17 from the package you have quoted) is now at kernel-3.7.6-102.fc17*. OK, I think that you must just have made a typo, right? And the latest kernel you were trying to boot was 3.7.6-102.

    Did you look at my earlier post on enabling recovery mode to boot into the problem kernel? There's no point running the second set of commands without being in the latest kernel.

    Quote Originally Posted by mikeym
    You may need to go into fallback mode, which I had to enable in /etc/default/grub

    Code:
    GRUB_DISABLE_RECOVERY="false"
    Then update grub with:

    Code:
    su -l
    grub2-mkconfig -o /boot/grub2/grub.cfg
    Reboot and select Fedora Advanced then your kernel version and fallback.


    ---------- Post added at 11:54 AM ---------- Previous post was at 10:48 AM ----------

    Also there is something very weird going on with your dependency discovery; yum is only pulling in:

    Installing : 1:akmod-nvidia-304.64-3.fc17.x86_64 1/2
    Installing : 1:xorg-x11-drv-nvidia-libs-304.64-3.fc17.i686
    It should be pulling in xorg-x11-drv-nvidia and xorg-x11-drv-nvidia-libs.x86_64 at least (possibly others, I've not had a chance to check).

    ---------- Post added at 03:26 PM ---------- Previous post was at 11:54 AM ----------

    Code:
    $ yum deplist akmod-nvidia
    Loaded plugins: fastestmirror, langpacks, presto, refresh-packagekit, remove-
                  : with-leaves
    Loading mirror speeds from cached hostfile
     * fedora: mirror01.th.ifl.net
     * livna: rpm.livna.org
     * rpmfusion-free: mirror01.th.ifl.net
     * rpmfusion-free-updates: mirror01.th.ifl.net
     * rpmfusion-nonfree: mirror01.th.ifl.net
     * rpmfusion-nonfree-updates: mirror01.th.ifl.net
     * updates: mirror01.th.ifl.net
    package: akmod-nvidia.x86_64 1:304.64-6.fc18
      dependency: /bin/sh
       provider: bash.x86_64 4.2.42-3.fc18
      dependency: akmods
       provider: akmods.noarch 0.5.1-3.fc18
      dependency: kmodtool
       provider: kmodtool.noarch 1-21.fc18
      dependency: nvidia-kmod-common >= 1:304.64
       provider: xorg-x11-drv-nvidia.x86_64 1:304.64-5.fc18
    $yum deplist xorg-x11-drv-nvidia
    Loaded plugins: fastestmirror, langpacks, presto, refresh-packagekit, remove-
                  : with-leaves
    Loading mirror speeds from cached hostfile
     * fedora: mirror01.th.ifl.net
     * livna: rpm.livna.org
     * rpmfusion-free: mirror01.th.ifl.net
     * rpmfusion-free-updates: mirror01.th.ifl.net
     * rpmfusion-nonfree: mirror01.th.ifl.net
     * rpmfusion-nonfree-updates: mirror01.th.ifl.net
     * updates: mirror01.th.ifl.net
    package: xorg-x11-drv-nvidia.x86_64 1:304.64-5.fc18
      dependency: /bin/sh
       provider: bash.x86_64 4.2.42-3.fc18
      dependency: ldconfig
       provider: glibc.x86_64 2.16-28.fc18
       provider: glibc.i686 2.16-28.fc18
      dependency: libc.so.6()(64bit)
       provider: glibc.x86_64 2.16-28.fc18
      dependency: libc.so.6(GLIBC_2.2.5)(64bit)
       provider: glibc.x86_64 2.16-28.fc18
      dependency: libdl.so.2()(64bit)
       provider: glibc.x86_64 2.16-28.fc18
      dependency: libdl.so.2(GLIBC_2.2.5)(64bit)
       provider: glibc.x86_64 2.16-28.fc18
      dependency: libm.so.6()(64bit)
       provider: glibc.x86_64 2.16-28.fc18
      dependency: libm.so.6(GLIBC_2.2.5)(64bit)
       provider: glibc.x86_64 2.16-28.fc18
      dependency: libpthread.so.0()(64bit)
       provider: glibc.x86_64 2.16-28.fc18
      dependency: libpthread.so.0(GLIBC_2.2.5)(64bit)
       provider: glibc.x86_64 2.16-28.fc18
      dependency: librt.so.1()(64bit)
       provider: glibc.x86_64 2.16-28.fc18
      dependency: librt.so.1(GLIBC_2.2.5)(64bit)
       provider: glibc.x86_64 2.16-28.fc18
      dependency: nvidia-kmod >= 304.64
       provider: kmod-nvidia-3.7.8-202.fc18.x86_64.x86_64 1:304.64-6.fc18.2
       provider: kmod-nvidia-3.7.7-201.fc18.x86_64.x86_64 1:304.64-6.fc18
       provider: kmod-nvidia-3.7.6-201.fc18.x86_64.x86_64 1:304.64-4.fc18
       provider: kmod-nvidia-3.7.5-201.fc18.x86_64.x86_64 1:304.64-2.fc18.5
       provider: kmod-nvidia-3.7.4-204.fc18.x86_64.x86_64 1:304.64-2.fc18.4
       provider: kmod-nvidia-3.7.2-204.fc18.x86_64.x86_64 1:304.64-2.fc18.3
       provider: kmod-nvidia-3.7.2-201.fc18.x86_64.x86_64 1:304.64-2.fc18.2
       provider: kmod-nvidia-3.6.11-3.fc18.x86_64.x86_64 1:304.64-2.fc18.1
       provider: kmod-nvidia-3.6.10-4.fc18.x86_64.x86_64 1:304.64-2.fc18
       provider: kmod-nvidia.x86_64 1:304.64-6.fc18.2
       provider: akmod-nvidia.x86_64 1:304.64-6.fc18
      dependency: nvidia-settings
       provider: nvidia-settings.x86_64 1.0-26.fc18
      dependency: nvidia-xconfig
       provider: nvidia-xconfig.x86_64 1.0-25.fc18
      dependency: which
       provider: which.x86_64 2.20-4.fc18
      dependency: xorg-x11-drv-nvidia-libs(x86-64) = 1:304.64-5.fc18
       provider: xorg-x11-drv-nvidia-libs.x86_64 1:304.64-5.fc18
    So akmod-nvidia depends on:

    Code:
    bash akmods kmodtool xorg-x11-drv-nvidia
    And xorg-x11-drv-nvidia depends on:

    Code:
    glibc bash (a)kmod-nvidia nvidia-settings nvidia-xconfig which xorg-x11-drv-nvidia-libs
    Which are not getting installed on your system. I don't know why this would be the case.
    Last edited by mikeym; 20th February 2013 at 04:37 PM. Reason: double post

  4. #19
    Join Date
    May 2008
    Age
    52
    Posts
    97
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Angry Re: no login after update to kernel -3.7.6-102

    this is the kind of stuff that keeps people in the microsoft camp. Although I am a beginner/intermediate at linux (mostly Fedora, some ubuntu and debian for servers) and have used/loved it for 5 years, I wince every time a kernel upgrade and/or drivers & browsers get released. It is just a royal PITA to lose 1-3 days trying to chase down issues while browsers are crashing every 5 minutes. Some of us just don't have time to tinker and want to get real work done! This relationship is truly bittersweet.

    Kernel 3.7.6-102 currently hanging for me (with the kmods, akmods packages since nvidia native drivers would not work) and hitting the escape button does not bring up the booting script, only the fedora logo. Argh...

  5. #20
    Join Date
    Jan 2010
    Location
    Vernonia, Oregun
    Posts
    122
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: no login after update to kernel -3.7.6-102

    OK I have modified the grub file.
    Reboot and select Fedora Advanced then your kernel version and fallback. ??

    Grub now offers the following:

    Fedora, with Linux 3.7.6-102.fc17.x86_64
    Fedora, with Linux 3.7.6-102.fc17.x86_64 (recovery mode)
    Fedora, with Linux 3.7.3-101.fc17.x86_64
    Fedora, with Linux 3.7.3-101.fc17.x86_64 (recovery mode)
    ...

    Which one should I be selecting ? and yes you were correct I did a typo on the kernel version before.

    Thanks,
    -Val
    Fedora 19 64bit (Installed Dec. 2013)
    Memory 3Gb
    Video nVidia GeForce 9800GT 512Mb DDR3, CPU AMD Phenom 9550
    Disk Samsung HD103SJ 1Tb 3Gb/s (Installed April 2010)

  6. #21
    Join Date
    Oct 2011
    Posts
    141
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: no login after update to kernel -3.7.6-102

    Hi JValeck,

    Yes it would be the Kenel version you are wanting to boot (in this case the latest one 3.7.6-102) with the words "recovery mode" after it. This will let you boot into Fedora if you're having problems getting it to boot normally. It will dump you to a terminal with root privilege (so is a security issue if this is a public computer). You can try the commands I gave you for after booting into the latest kernel.

    However because I'm an idiot they are unlikely to help in this case. I hadn't checked the kernel version and nvidia packages version against the original problem package. It looks like (as of yesterday - the last time I checked) Fedora 18 had updated the problem package combination but Fedora 17 is still using them. In that case you may need to use the previous kernel and NVidia version for the meantime, and file a bug or make it known elsewhere that there is a critical outstanding issue with these 2 packages.

    I know that NVidia isn't supported by the official repositories (but rpmfusion) but this really shouldn't be happening, let alone not fixed for a number of days. I agree with vfulco, seems like a major own goal to me.

    Sorry JValeck for leading you on a bit of a merry chase, but hopefully you learnt some things while you were at it.
    Last edited by mikeym; 21st February 2013 at 01:54 PM. Reason: can't spell

  7. #22
    Join Date
    Jan 2010
    Posts
    7,747
    Mentioned
    3 Post(s)
    Tagged
    0 Thread(s)

    Re: no login after update to kernel -3.7.6-102

    One thing I'm finding is that after some (but not all) kernel updates, I have to do a reinstall of akmod-nvidia. I remember having to do that, then, the next time I didn't, and thought all was well. Then, today, once again, I had to reinstall it. As it's a really simple thing, and not a big deal (one of the advantages of booting into text mode) I haven't been paying much attention, though I think one kernel upgrade removed the nvidia module. Still, I haven't had to do anything dracut or manual blacklisting.

  8. #23
    Join Date
    Jan 2010
    Location
    Vernonia, Oregun
    Posts
    122
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: no login after update to kernel -3.7.6-102

    Thank you all for your patience with me and this issue, I have learnt alot.

    I have no problem continuing to use 3.7.3-101.fc17.x86_64 and wait for a solution.

    If this has been fixed in fc18, do you think this new release would be an expectable solution ? I normally wait a good 6 months before I use a new release and let the pros get the bugs out. I am willing to give it a try if you believe it is stable.

    Half the fun I have using Linux is working with you folks when I have an issue. It seems the best way to learn.

    You mentioned submitting a bug report. I do not know how to do this.

    Best regards,
    -Val
    Fedora 19 64bit (Installed Dec. 2013)
    Memory 3Gb
    Video nVidia GeForce 9800GT 512Mb DDR3, CPU AMD Phenom 9550
    Disk Samsung HD103SJ 1Tb 3Gb/s (Installed April 2010)

  9. #24
    Join Date
    Jan 2010
    Location
    Vernonia, Oregun
    Posts
    122
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: no login after update to kernel -3.7.6-102

    I was notified today with a s/w update that akmod-nvidia-1:304.64-6.fc17 is now available.

    Should I try this or should I just move on to fc18 ?

    Thanks,
    -Val
    Fedora 19 64bit (Installed Dec. 2013)
    Memory 3Gb
    Video nVidia GeForce 9800GT 512Mb DDR3, CPU AMD Phenom 9550
    Disk Samsung HD103SJ 1Tb 3Gb/s (Installed April 2010)

  10. #25
    Join Date
    Feb 2013
    Location
    On the Moon
    Posts
    86
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: no login after update to kernel -3.7.6-102

    This will only help if you UPGRADE...
    I am running kernel = 3.7.9-201
    NVIDIA driver is available = 313.18-2 as akmod from rpmfusion-nonfree

    So far, no problems.

  11. #26
    Join Date
    Oct 2011
    Posts
    141
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: no login after update to kernel -3.7.6-102

    I would try updating everything. The latest kernel looks to be kernel-3.7.9-104.fc17

  12. #27
    Join Date
    Jan 2010
    Location
    Vernonia, Oregun
    Posts
    122
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: no login after update to kernel -3.7.6-102

    My finial solution was to upgrade to fc18 the Nvidia drivers installed without problem using this guide.

    http://www.if-not-true-then-false.co...-nvidia-guide/

    Thanks to all,
    -Val
    Fedora 19 64bit (Installed Dec. 2013)
    Memory 3Gb
    Video nVidia GeForce 9800GT 512Mb DDR3, CPU AMD Phenom 9550
    Disk Samsung HD103SJ 1Tb 3Gb/s (Installed April 2010)

Page 2 of 2 FirstFirst 1 2

Similar Threads

  1. Can't login with kernel update and NVIDIA
    By billquinn in forum Using Fedora
    Replies: 28
    Last Post: 21st May 2012, 07:41 AM
  2. no login possible after aborted kernel update
    By libelle in forum Using Fedora
    Replies: 0
    Last Post: 10th September 2011, 09:37 PM
  3. Stopped on the previous page of Login after update a new kernel
    By guouoo in forum Installation, Upgrades and Live Media
    Replies: 3
    Last Post: 7th April 2010, 02:45 AM
  4. Login problem after kernel update
    By paulvitic in forum Using Fedora
    Replies: 4
    Last Post: 2nd July 2008, 08:51 AM
  5. Replies: 14
    Last Post: 2nd February 2008, 05:33 AM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •