[SOLVED] 3.11 kernel, akmod and Plymouth
FedoraForum.org - Fedora Support Forums and Community
Page 1 of 2 1 2 LastLast
Results 1 to 15 of 18
  1. #1
    Join Date
    Nov 2010
    Posts
    37
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    3.11 kernel, akmod and Plymouth

    I'm getting the "Failed to start Wait for Plymouth Boot Screen to Quit" on boot which I believe was caused by the issue described in this thread:

    http://forums.fedoraforum.org/showthread.php?t=294091

    I tried the fix mentioned in the thread above, but it just wouldn't go for me. I've also tried removing the nvidia driver using:

    Code:
    yum remove xorg-x11-drv-nvidia\* nvidia-settings nvidia-xconfig
    And then reinstalling but no luck. I'm still getting "Failed to start Wait for Plymouth Boot Screen to Quit".

    Or maybe it has nothing to do with Plymouth as described in the second post of this thread:
    http://forums.fedoraforum.org/showthread.php?t=294133

    The only way I can (and know how) to use the system at all is to use Ctrl-Alt-F2 and get into the terminal. And I can't revert to an older kernel cause I've been running yum update and all my kernels are now 3.11 in the selection before boot.

    If it matters, or just out of curiosity, the system in question is an old Pentium III, socket 370 rig with a PCI 520 nvidia card. And Fedora and the drivers have always worked fine till lately.

    I NEED A HAND HOLDING I AM LOST

    Thanks guys.
    Last edited by Veeshush; 13th October 2013 at 04:55 AM.

  2. #2
    Join Date
    Nov 2009
    Posts
    14
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: 3.11 kernel, akmod and Plymouth

    I am getting pretty much the same thing. I too have tried the suggestions at that post with no luck. I am, however not running a system quite as old as yours. My system is a mid 2008 mac book pro with a 8600M GT chipset.

    wish I could figure out whats up with this jazz. have'n trouble with my desktop nvidia situation as well.

  3. #3
    b4time Guest

    Re: 3.11 kernel, akmod and Plymouth

    sorry guys I see you all ready found it I have no idea what wrong.I have to go lay down
    Last edited by b4time; 15th October 2013 at 11:49 PM. Reason: to sick to pay attention

  4. #4
    Join Date
    Oct 2013
    Location
    Bucharest
    Posts
    1
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: 3.11 kernel, akmod and Plymouth

    Same here,

    After upgrading to 3.11 had the akmod issue then followed the instructions described in the thread you mentioned AND now after this new kernel update can't boot into the desktop. However i am still able to use the previous 3.11 which i've selected right before boot with no issues at all.

    After i got it working with 3.11.3 by using the patched akmod package i still havent updated it as it shows into the notifications bar. Should i? and give it a go with the new recently installed 3.11?

    My system is running very nice with the first 3.11 and have no problem using it until further notice on the matter.

  5. #5
    Join Date
    Nov 2010
    Posts
    37
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: 3.11 kernel, akmod and Plymouth

    Whelp, no solution still but at least I'm not alone.

    I might try booting from a LIVE cd, copying all my stuff to a thumb drive, and just try reinstalling Fedora.

    edit

    Booted a live cd, tried to dig around the logs some.
    Xorg.0.log
    Code:
    [    43.954] (EE) NVIDIA: Failed to load the NVIDIA kernel module. Please check your
    [    43.956] (EE) NVIDIA:     system's kernel log for additional error messages.
    [    43.956] (EE) No devices detected.
    [    43.956] (EE)
    But I kind of already know this, seeing as I can't boot to the GUI.

    edit2

    Reinstalling Fedora tonight. I want to see if this will happen with a fresh install. I'll let you guys know if it fixed it for me tomorrow.
    Last edited by Veeshush; 19th October 2013 at 03:18 AM.

  6. #6
    Join Date
    Nov 2010
    Posts
    37
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: 3.11 kernel, akmod and Plymouth

    Ok, this isn't looking good. I finished reinstalling, ran yum update and then installed akmod-nvidia drivers.

    Good news: No more "Failed to start Wait for Plymouth Boot Screen to Quit"

    Bad News: Can not boot to GUI still!

    This post actually is pretty much what I'm getting on boot:
    http://forums.fedoraforum.org/showthread.php?t=294735

    edit

    This is an i686 Fedora build btw. I noticed my 64bit Fedora machine doesn't suffer from any of these issues, but I have no idea if that's in any way related. Something is up with these 3.11 kernels.

    edit2

    I'm pretty confident this is another 3.11 kernel + akmod issue. If someone with more Fedora know-how can tell me what logs I should be checking, I'd be more than happy to copy and paste them.
    Last edited by Veeshush; 19th October 2013 at 06:28 PM.

  7. #7
    Join Date
    Nov 2010
    Posts
    37
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: 3.11 kernel, akmod and Plymouth

    Nothing I can do but run yum update and wait for a new kernel + akmod that hopefully doesn't suffer from these issues.

    I'd like to see if it's even been reported yet, and if not, then I'd report something. I'll search and edit this post if I find anything that sounds like this problem.

    edit

    Yeah, I can't find anything.
    Last edited by Veeshush; 21st October 2013 at 09:04 PM.

  8. #8
    b4time Guest

    Re: 3.11 kernel, akmod and Plymouth

    have you tried here http://rpmfusion.org/Howto/nVidia not sure it will help but worth a look.

  9. #9
    Join Date
    Nov 2010
    Posts
    37
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: 3.11 kernel, akmod and Plymouth

    Quote Originally Posted by b4time
    The last two might actually help- Disable and Bug Report.

    Going to see what log I get with this:
    4a) Please always include a copy of an nvidia-bug-report.log file, which can be generated with the `nvidia-bug-report.sh` script shipped with the NVIDIA Linux/FreeBSD graphics drivers and installed in your PATH; the log file will be placed in the current working directory. Newer versions of the script will automatically compress the log file renaming it to nvidia-bug-report.log.gz.
    edit

    I managed to get a nvidia-bug-report.log, I'm going to post it over at https://devtalk.nvidia.com/default/board/98/linux/
    Last edited by Veeshush; 21st October 2013 at 11:50 PM.

  10. #10
    Join Date
    Nov 2010
    Posts
    37
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: 3.11 kernel, akmod and Plymouth

    Alright, I made a thread over there:
    https://devtalk.nvidia.com/default/t...-login-screen/

    The log is attached ^

    But it's basically just
    46.194] (EE) NVIDIA: Failed to load the NVIDIA kernel module. Please check your
    [ 46.195] (EE) NVIDIA: system's kernel log for additional error messages.
    [ 46.195] (EE) No devices detected.
    [ 46.195] (EE)
    Fatal server error:
    [ 46.195] (EE) no screens found(EE)
    [ 46.195] (EE)
    So for whatever reason, something changed with the newer nvidia drivers (or with akmod) and it just can not detect my card I take it.

    edit

    For reference this is with 325.15 nvidia drivers and 3.11.4-201.fc19.i686 kernel.
    Last edited by Veeshush; 22nd October 2013 at 02:02 AM.

  11. #11
    b4time Guest

    Re: 3.11 kernel, akmod and Plymouth

    Really I'm not the person for this but I'm wondering what card you have?

    Code:
    /sbin/lspci | grep VGA
    run this code also might help some one to diagnose your trouble

    Code:
    rpm -qa *\nvidia\*  *\kernel\*|sort;uname -r;lsmod |grep -e nvidia -e nouveau;cat /etc/X11/xorg.conf
    Last edited by b4time; 22nd October 2013 at 03:09 AM. Reason: code added

  12. #12
    Join Date
    Nov 2010
    Posts
    37
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: 3.11 kernel, akmod and Plymouth

    Quote Originally Posted by b4time
    Really I'm not the person for this but I'm wondering what card you have?
    It's a pci 520:
    http://www.newegg.com/Product/Produc...82E16814500228

    Even my old review for it is still there, I even mentioned it working well with Fedora 16. (and it had been working great up till these past weeks with Fedora 19)

    Sauerbraten Cube 2 can easily run up into +40fps even with this rig being so old.

    Code:
    /sbin/lspci | grep VGA
    run this code also might help some one to diagnose your trouble

    Code:
    rpm -qa *\nvidia\*  *\kernel\*|sort;uname -r;lsmod |grep -e nvidia -e nouveau;cat /etc/X11/xorg.conf
    I'll run both of those in a minute and I'll edit this post with the results. Thanks for the help by the way!

    edit

    Here's /sbin/lspci | grep VGA:
    Code:
    01:00.0 VGA compatible controller: Trident Microsystems CyberBlade/i1 (rev 6a)
    02:00.0 VGA compatible controller: NVIDIA Corporation GF119 [GeForce GT 520] (rev a1)
    The first one is the onboard, which is the whole reason I started dabbling in seeing if modern nvidia pci cards would go in such an old system (legacy hardware is fun but I still can't stand the old tiny screen resolutions, 1024 × 768 being the highest). I can't disable the ancient onboard in the BIOS or with a jumper, but that's typical of old systems and never hurt anything before.

    I'll get the second output later. It's going to take me a while to get that one. I'll probably have to use something like rpm -qa | sort | pr –column=2 > abc.txt to save the output to text, get it from the hard drive using a live cd and then pasting it here. If anyone has any easier methods, let me know.
    Last edited by Veeshush; 22nd October 2013 at 08:07 AM.

  13. #13
    leigh123linux Guest

    Re: 3.11 kernel, akmod and Plymouth

    Quote Originally Posted by Veeshush
    Alright, I made a thread over there:
    https://devtalk.nvidia.com/default/t...-login-screen/

    The log is attached ^


    But it's basically just


    So for whatever reason, something changed with the newer nvidia drivers (or with akmod) and it just can not detect my card I take it.

    edit

    For reference this is with 325.15 nvidia drivers and 3.11.4-201.fc19.i686 kernel.
    How the hell to you expect any help if you don't post any logs or requested info.

  14. #14
    Join Date
    Nov 2010
    Posts
    37
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: 3.11 kernel, akmod and Plymouth

    Quote Originally Posted by leigh123linux
    How the hell to you expect any help if you don't post any logs or requested info.
    ...

    " If someone with more Fedora know-how can tell me what logs I should be checking, I'd be more than happy to copy and paste them. "

    I posted the bug report log, but it's showing up "[SCANNING... PLEASE WAIT] nvidia-bug-report.log " on the nvidia forums if thats what you mean. And I already mentioned, I can't exactly easily copy and past stuff from ctrl alt f2 terminal if you're referencing why I haven't posted "rpm -qa *\nvidia\* *\kernel\*|sort;uname -r;lsmod |grep -e nvidia -e nouveau;cat /etc/X11/xorg.conf".

    edit

    Here I'll attach the bug report log here...
    Attached Files Attached Files
    Last edited by Veeshush; 22nd October 2013 at 06:59 PM.

  15. #15
    leigh123linux Guest

    Re: 3.11 kernel, akmod and Plymouth

    Quote Originally Posted by Veeshush
    ...

    " If someone with more Fedora know-how can tell me what logs I should be checking, I'd be more than happy to copy and paste them. "

    I posted the bug report log, but it's showing up "[SCANNING... PLEASE WAIT] nvidia-bug-report.log " on the nvidia forums if thats what you mean. And I already mentioned, I can't exactly easily copy and past stuff from ctrl alt f2 terminal if you're referencing why I haven't posted "rpm -qa *\nvidia\* *\kernel\*|sort;uname -r;lsmod |grep -e nvidia -e nouveau;cat /etc/X11/xorg.conf".

    edit

    Here I'll attach the bug report log here...
    I see you have two cards, nvidia vbios is loaded (good)

    Code:
    [  1288.889] (--) PCI: (0:1:0:0) 1023:8500:1023:8500 rev 106, Mem @ 0xe1800000/8388608, 0xe2000000/131072, 0xe1000000/8388608, BIOS @ 0x????????/65536
    [  1288.889] (--) PCI:*(0:2:0:0) 10de:1040:19da:1228 rev 161, Mem @ 0xda000000/16777216, 0xd0000000/134217728, 0xd8000000/33554432, I/O @ 0x0000c000/128, BIOS @ 0x????????/524288

    Xorg.0.log is incomplete (not much use for debug)


    Your using 3.11.4-201.fc19.i686 and nouveau is blacklisted (nouveau might still be alive in initramfs)

    Code:
    [  1288.882] Kernel command line: BOOT_IMAGE=/vmlinuz-3.11.4-201.fc19.i686 root=/dev/mapper/fedora-root ro rd.lvm.lv=fedora/swap nomodeset rd.md=0 rd.dm=0 vconsole.keymap=us rd.luks=0 vconsole.font=latarcyrheb-sun16 rd.lvm.lv=fedora/root rhgb quiet nouveau.modeset=0 rd.driver.blacklist=nouveau video=vesa:off

    Xorg.conf is a mess (still functional), why do people insist on running nvidia-xconfig (it's a crap tool for the job)

    Code:
    # nvidia-xconfig: X configuration file generated by nvidia-xconfig
    # nvidia-xconfig:  version 325.15  (buildmeister@swio-display-x64-rhel04-07)  Wed Jul 31 19:32:06 PDT 2013
    
    # RPM Fusion - nvidia-xorg.conf
    # 
    
    Section "ServerLayout"
        Identifier     "Default Layout"
        Screen         "Default Screen" 0 0
        InputDevice    "Keyboard0" "CoreKeyboard"
        InputDevice    "Mouse0" "CorePointer"
    EndSection
    
    Section "InputDevice"
    
        # generated from default
        Identifier     "Keyboard0"
        Driver         "keyboard"
    EndSection
    
    Section "InputDevice"
    
        # generated from default
        Identifier     "Mouse0"
        Driver         "mouse"
        Option         "Protocol" "auto"
        Option         "Device" "/dev/input/mice"
        Option         "Emulate3Buttons" "no"
        Option         "ZAxisMapping" "4 5"
    EndSection
    
    Section "Monitor"
        Identifier     "Monitor0"
        VendorName     "Unknown"
        ModelName      "Unknown"
        HorizSync       28.0 - 33.0
        VertRefresh     43.0 - 72.0
        Option         "DPMS"
    EndSection
    
    Section "Device"
        Identifier     "Videocard0"
        Driver         "nvidia"
    EndSection
    
    Section "Screen"
        Identifier     "Default Screen"
        Device         "Videocard0"
        Monitor        "Monitor0"
        SubSection     "Display"
            Modes      "nvidia-auto-select"
        EndSubSection
    EndSection

    Xorg.1.log -Xorg.5.log shows a missing nvidia.ko for kernel 3.9.5-301.fc19.i686

    Code:
    [    42.433] (EE) NVIDIA: Failed to load the NVIDIA kernel module. Please check your
    [    42.435] (EE) NVIDIA:     system's kernel log for additional error messages.
    [    42.435] (EE) No devices detected.
    [    42.435] (EE)

    This shows you have a matching nvidia.ko for the running kernel (


    Code:
    /sbin/modinfo nvidia | grep vermagic
    
    vermagic:       3.11.4-201.fc19.i686 SMP mod_unload 686

    This shows nouveau isn't loaded, so no conflict of modules

    Code:
    *** /proc/modules
    *** ls: -r--r--r--. 1 root root 0 2013-10-21 20:07:05.701042888 -0400 /proc/modules
    ebtable_nat 12695 0 - Live 0xf818b000
    nf_conntrack_netbios_ns 12585 0 - Live 0xf7fb1000
    nf_conntrack_broadcast 12487 1 nf_conntrack_netbios_ns, Live 0xf81c5000
    ipt_MASQUERADE 12760 1 - Live 0xf8b75000
    ip6table_nat 12871 1 - Live 0xf7e6a000
    nf_nat_ipv6 13053 1 ip6table_nat, Live 0xf8077000
    ip6table_mangle 12620 1 - Live 0xf7fd8000
    ip6table_security 12630 1 - Live 0xf7fac000
    ip6table_raw 12603 1 - Live 0xf811b000
    ip6t_REJECT 12826 2 - Live 0xf7fd0000
    nf_conntrack_ipv6 18318 24 - Live 0xf7fc2000
    nf_defrag_ipv6 26016 1 nf_conntrack_ipv6, Live 0xf7fba000
    iptable_nat 12867 1 - Live 0xf7f46000
    nf_nat_ipv4 13039 1 iptable_nat, Live 0xf7f53000
    nf_nat 24756 5 ipt_MASQUERADE,ip6table_nat,nf_nat_ipv6,iptable_nat,nf_nat_ipv4, Live 0xf7f7e000
    iptable_mangle 12615 1 - Live 0xf7f89000
    iptable_security 12625 1 - Live 0xf7f58000
    iptable_raw 12598 1 - Live 0xf8059000
    bnep 18959 2 - Live 0xf7f4d000
    nf_conntrack_ipv4 14320 20 - Live 0xf7e6f000
    nf_defrag_ipv4 12601 1 nf_conntrack_ipv4, Live 0xf7e09000
    bluetooth 317833 7 bnep, Live 0xf7fe3000
    xt_conntrack 12664 42 - Live 0xf7de5000
    nf_conntrack 74019 11 nf_conntrack_netbios_ns,nf_conntrack_broadcast,ipt_MASQUERADE,ip6table_nat,nf_nat_ipv6,nf_conntrack_ipv6,iptable_nat,nf_nat_ipv4,nf_nat,nf_conntrack_ipv4,xt_conntrack, Live 0xf7f6a000
    rfkill 20721 2 bluetooth, Live 0xf7f5f000
    ebtable_filter 12715 0 - Live 0xf7ddd000
    ebtables 21315 2 ebtable_nat,ebtable_filter, Live 0xf7e00000
    ip6table_filter 12711 1 - Live 0xf7cf3000
    ip6_tables 17634 5 ip6table_nat,ip6table_mangle,ip6table_security,ip6table_raw,ip6table_filter, Live 0xf7e1c000
    snd_hda_codec_hdmi 40508 1 - Live 0xf7e3d000
    snd_hda_intel 42658 1 - Live 0xf7e10000
    snd_via82xx 24326 1 - Live 0xf7cfa000
    snd_mpu401_uart 13712 1 snd_via82xx, Live 0xf7c9b000
    gameport 14522 1 snd_via82xx, Live 0xf7cee000
    snd_rawmidi 24472 1 snd_mpu401_uart, Live 0xf7dd0000
    snd_hda_codec 155748 2 snd_hda_codec_hdmi,snd_hda_intel, Live 0xf7f1e000
    snd_ac97_codec 104827 1 snd_via82xx, Live 0xf7e22000
    snd_hwdep 13232 1 snd_hda_codec, Live 0xf7c47000
    ac97_bus 12602 1 snd_ac97_codec, Live 0xf7cd5000
    snd_seq 54679 0 - Live 0xf7d03000
    nvidia 8439589 4 - Live 0xf8b95000 (POF)
    snd_seq_device 13824 2 snd_rawmidi,snd_seq, Live 0xf7c7c000
    snd_pcm 81999 5 snd_hda_codec_hdmi,snd_hda_intel,snd_via82xx,snd_hda_codec,snd_ac97_codec, Live 0xf7dea000
    snd_page_alloc 13852 3 snd_hda_intel,snd_via82xx,snd_pcm, Live 0xf7cab000
    snd_timer 23750 2 snd_seq,snd_pcm, Live 0xf7cce000
    via686a 19413 0 - Live 0xf7cb7000
    ppdev 17363 0 - Live 0xf7cb1000
    i2c_viapro 13096 0 - Live 0xf7c81000
    parport_pc 27416 0 - Live 0xf7c74000
    8139too 32530 0 - Live 0xf7ca2000
    drm 230162 1 nvidia, Live 0xf7d13000
    8139cp 27130 0 - Live 0xf7c4c000
    mii 13311 2 8139too,8139cp, Live 0xf7c31000
    snd 59132 16 snd_hda_codec_hdmi,snd_hda_intel,snd_via82xx,snd_mpu401_uart,snd_rawmidi,snd_hda_codec,snd_ac97_codec,snd_hwdep,snd_seq,snd_seq_device,snd_pcm,snd_timer, Live 0xf7cbe000
    i2c_core 28619 3 nvidia,i2c_viapro,drm, Live 0xf7c89000
    soundcore 14123 1 snd, Live 0xf7c6f000
    microcode 18789 0 - Live 0xf7c59000
    parport 39185 2 ppdev,parport_pc, Live 0xf7c64000
    serio_raw 13189 0 - Live 0xf7c3e000
    mperf 12551 0 - Live 0xf7c2c000
    uinput 17265 0 - Live 0xf8250000
    ata_generic 12790 0 - Live 0xf7c25000
    pata_acpi 12886 0 - Live 0xf7c1d000
    pata_via 13407 2 - Live 0xf7c39000

    It looks like there a bug in 325.15

    Code:
    Oct 21 20:06:53 localhost kernel: [ 1283.678158] NVRM: rm_init_adapter(0) failed
    Oct 21 20:06:58 localhost kernel: [ 1288.721677] NVRM: RmInitAdapter failed! (0x12:0x2b:1830)
    Oct 21 20:06:58 localhost kernel: [ 1288.721711] NVRM: rm_init_adapter(0) failed

    I would downgrade to 304xx and see if it helps


    Code:
    su
    yum erase *\nvidia\*
    yum install akmod-304xx

    wait a couple of minutes for the kmod to build then reboot

Page 1 of 2 1 2 LastLast

Similar Threads

  1. [SOLVED]
    New kernel 3.11 doesn't akmod Virtualbox at all!
    By marklf in forum Using Fedora
    Replies: 7
    Last Post: 25th September 2013, 03:39 PM
  2. PlanetCCRMA RT kernel breaks dkms akmod
    By witchbutter in forum Using Fedora
    Replies: 0
    Last Post: 9th June 2013, 05:20 AM
  3. Custom kernel and akmod-wl
    By roelj in forum Using Fedora
    Replies: 5
    Last Post: 30th March 2011, 06:09 PM
  4. Custom kernel and akmod
    By slabber in forum Using Fedora
    Replies: 3
    Last Post: 14th February 2009, 05:37 PM
  5. akmod and kernel update
    By BadMofo666 in forum Hardware & Laptops
    Replies: 3
    Last Post: 15th November 2008, 03:39 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
  •