[Solved]Re: Fedora 17 not booting after installing akmod nvidia driver
On 06/05/2012 02:52 PM, Richard Shaw wrote: On Tue, Jun 5, 2012 at 1:40 AM, Swapnil Bhartiya swapnil.bhart...@gmail.com wrote: On 06/05/2012 07:46 AM, Gilboa Davara wrote: $ /sbin/lsmod | grep nouveau nouveau 785681 1 nxm_wmi 12823 1 nouveau wmi 18697 2 mxm_wmi, nouveau video18980 1 nouveau drm_kms_helper 40409 1 nouveau ttm 79709 1 nouveau drm 241920 3 ttm, drm_kms_helper, nouveau i2c_core 38028 4 drm_kms_helper, nouveau, i2c_i801 Yup, nouveau is still being loaded, probably from your initrd. As long as this happens the nvidia driver will not be able to load, period. This may be because you're dual booting that for some reason the initrd isn't being updated properly? Thanks it worked when I tried with Fedora Grub in MBR. Thanks everyone. Swapnil Richard -- users mailing list users@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
Re: Fedora 17 not booting after installing akmod nvidia driver
On Tue, Jun 5, 2012 at 9:40 AM, Swapnil Bhartiya swapnil.bhart...@gmail.com wrote: This is how mine now looks GRUB_CMDLINE_LINUX=quiet rhgb rdblacklist=nouveau nouveau.modset=0 vga=0x317 3 You grub command line looks *very* short (and fishy!). Lack of LVM maybe? E.g. Mine, on multiple machines looks something like this: GRUB_CMDLINE_LINUX=rd.md=0 rd.dm=0 rd.lvm.lv=xxx KEYTABLE=us quiet SYSFONT=latarcyrheb-sun16 rhgb rd.lvm.lv=xxx rd.luks=0 LANG=en_US.UTF-8 vga=0x317 $ /sbin/lsmod | grep nouveau nouveau 785681 1 nxm_wmi 12823 1 nouveau wmi 18697 2 mxm_wmi, nouveau video 18980 1 nouveau drm_kms_helper 40409 1 nouveau ttm 79709 1 nouveau drm 241920 3 ttm, drm_kms_helper, nouveau i2c_core 38028 4 drm_kms_helper, nouveau, i2c_i801 It looks like you didn't rebuild the grub configuration before rebooting. ($ grub2-mkconfig -o /boot/grub2/grub.cfg) NOTE: As I mentioned before, you grub configuration looks *very* broken, once you rebuild the grub configuration you may find yourself with a broken Fedora configuration. 7. Please post the output of: $ cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-3.3.4-5.fc17.x86_64 root=/dev/sda6 Gaah. Oh man (see above). On a working machine, you cmdline should be: BOOT_IMAGE=/vmlinuz-3.3.7-1.fc17.x86_64 root=XXX ro rd.md=0 rd.dm=0 rd.lvm.lv=XXX KEYTABLE=us quiet SYSFONT=latarcyrheb-sun16 rhgb rd.lvm.lv=XXX rd.luks=0 LANG=en_US.UTF-8 vga=0x317 - Gilboa -- users mailing list users@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
Re: Fedora 17 not booting after installing akmod nvidia driver
On 06/05/2012 07:46 AM, Gilboa Davara wrote: On Tue, Jun 5, 2012 at 8:29 AM, Swapnil Bhartiya swapnil.bhart...@gmail.com wrote: Done exactly that. I did not add vga=0x317 as my monitor is 1900x1080 I rebuilt the grub configuration as you suggested. Note: I am multi-booting with Ubuntu so that I do have a system working unless I fix Fedora issue. I did not install Fedora grub instead using Ubuntu grub. So, I also updated Ubuntu's grub. When I did everything as you stated and rebooted. But once again when I booted into Fedora the boot started and then screen was stuck here: [ 13.172058] ADDRCONF (NETDEV_CHANGE): em1: link becomes ready Swapnil OK. Lets try the following: 0. When Fedora boot, bring up the grub menu. Couldn't find a way to bring grub during Fedora boot. However, upon booting again the screen was stuck at the above command and I went to TTY2 to edit grub. 1. 'E' to edit the Fedora entry. 2. After rhgb quiet, add rdblacklist=nouveau nouveau.modeset=0 vga=0x317 3. (Notice the '3' in the end) This is how mine now looks GRUB_CMDLINE_LINUX=quiet rhgb rdblacklist=nouveau nouveau.modset=0 vga=0x317 3 3. Ctrl-X to reboot. 4. Fedora will be boot, but will not try to bring up X. 5. Login as root. 6. Please post the output of: $ /sbin/lsmod | grep nouveau nouveau 785681 1 nxm_wmi 12823 1 nouveau wmi 18697 2 mxm_wmi, nouveau video18980 1 nouveau drm_kms_helper 40409 1 nouveau ttm 79709 1 nouveau drm 241920 3 ttm, drm_kms_helper, nouveau i2c_core 38028 4 drm_kms_helper, nouveau, i2c_i801 7. Please post the output of: $ cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-3.3.4-5.fc17.x86_64 root=/dev/sda6 8. If nouveau is loaded (will be shown in the output of line 6), try removing it: $ /sbin/rmmod nouveau tried says: Error:Module mouveau is in use 9. Repeat line 6, does nouveau still appear? 10. If nouveau is not present, type: $ xinit 11. If nothing happens, press Ctrl-C, and attach the contents of the /var/log/Xorg.0.log 12. If everything worked just fine, edit /etc/default/grub, locate the rhgb quiet and add rdblacklist=nouveau nouveau.modeset=0 vga=0x317. 13. Rebuild the grub configuration: $ grub2-mkconfig -o /boot/grub2/grub.cfg - Gilboa -- users mailing list users@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
Re: Fedora 17 not booting after installing akmod nvidia driver
On Tue, Jun 5, 2012 at 1:40 AM, Swapnil Bhartiya swapnil.bhart...@gmail.com wrote: On 06/05/2012 07:46 AM, Gilboa Davara wrote: $ /sbin/lsmod | grep nouveau nouveau 785681 1 nxm_wmi 12823 1 nouveau wmi 18697 2 mxm_wmi, nouveau video 18980 1 nouveau drm_kms_helper 40409 1 nouveau ttm 79709 1 nouveau drm 241920 3 ttm, drm_kms_helper, nouveau i2c_core 38028 4 drm_kms_helper, nouveau, i2c_i801 Yup, nouveau is still being loaded, probably from your initrd. As long as this happens the nvidia driver will not be able to load, period. This may be because you're dual booting that for some reason the initrd isn't being updated properly? Richard -- users mailing list users@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
Re: Fedora 17 not booting after installing akmod nvidia driver
On 06/05/2012 02:52 PM, Richard Shaw wrote: On Tue, Jun 5, 2012 at 1:40 AM, Swapnil Bhartiya swapnil.bhart...@gmail.com wrote: On 06/05/2012 07:46 AM, Gilboa Davara wrote: $ /sbin/lsmod | grep nouveau nouveau 785681 1 nxm_wmi 12823 1 nouveau wmi 18697 2 mxm_wmi, nouveau video18980 1 nouveau drm_kms_helper 40409 1 nouveau ttm 79709 1 nouveau drm 241920 3 ttm, drm_kms_helper, nouveau i2c_core 38028 4 drm_kms_helper, nouveau, i2c_i801 Yup, nouveau is still being loaded, probably from your initrd. As long as this happens the nvidia driver will not be able to load, period. This may be because you're dual booting that for some reason the initrd isn't being updated properly? Is there any way I can tweak the Ubuntu Grub? This is my main machine so that solution will be better as I keep couple of distros on the system and fedora can't detect them so I keep Ubuntu Grub. If not I can take a risk, just for the sake of testing and getting it resolved, and reinstall Fedora and install Grub. Swapnil Richard -- users mailing list users@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
Re: Fedora 17 not booting after installing akmod nvidia driver
Am 04.06.2012 13:36, schrieb Swapnil Bhartiya: I am revisiting the same problem that I faced with Fedora 16, and the reason I could not use it. I installed 'akmod' and 'nvidia settings' from Yumex and when rebooted the screen was stuck at / em1: link becomes ready/ I logged into tty3 and then removed akmod nvidia [root@localhost ~]# yum remove akmod-nvidia.x86_64 [root@localhost ~]# yum remove akmods.noarch and now system is booting well. What is the problem? How can I use nvidia drivers without this issue. I am liking Fedora 17 very much and would like to continue to use it as my primary OS along with Ubuntu. you should simply NOT upgrade to the latest fedora version soon after release if you rely on third-party drivers this is always the same discussion after each new release F16 has the same kernel, firefox, thunderbird. in this moment there is not much new in F17 for most workloads but you get usually a newer xorg which causes your problems and will do with each release in the future as long you are not willing to buy supported hardware signature.asc Description: OpenPGP digital signature -- users mailing list users@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
Re: Fedora 17 not booting after installing akmod nvidia driver
On 06/04/2012 01:39 PM, Reindl Harald wrote: Am 04.06.2012 13:36, schrieb Swapnil Bhartiya: I am revisiting the same problem that I faced with Fedora 16, and the reason I could not use it. I installed 'akmod' and 'nvidia settings' from Yumex and when rebooted the screen was stuck at / em1: link becomes ready/ I logged into tty3 and then removed akmod nvidia [root@localhost ~]# yum remove akmod-nvidia.x86_64 [root@localhost ~]# yum remove akmods.noarch and now system is booting well. What is the problem? How can I use nvidia drivers without this issue. I am liking Fedora 17 very much and would like to continue to use it as my primary OS along with Ubuntu. you should simply NOT upgrade to the latest fedora version soon after release if you rely on third-party drivers I am running Ubuntu at the moment. The reason I could not use Fedora 16 was this issue. I have been playing with Fedora 17 and liking it, so do want to use it as my primary OS. If installing nvidia drivers is an issue I can keep then disabled and try later. However, if there are instructions how to install nvidia drivers that will help. Best Swapnil this is always the same discussion after each new release F16 has the same kernel, firefox, thunderbird. in this moment there is not much new in F17 for most workloads but you get usually a newer xorg which causes your problems and will do with each release in the future as long you are not willing to buy supported hardware -- users mailing list users@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
Re: Fedora 17 not booting after installing akmod nvidia driver
On Mon, Jun 4, 2012 at 2:36 PM, Swapnil Bhartiya swapnil.bhart...@gmail.com wrote: Hi, I am revisiting the same problem that I faced with Fedora 16, and the reason I could not use it. I installed 'akmod' and 'nvidia settings' from Yumex and when rebooted the screen was stuck at [snip] and now system is booting well. What is the problem? How can I use nvidia drivers without this issue. I am liking Fedora 17 very much and would like to continue to use it as my primary OS along with Ubuntu. I'll start by saying that I'm running F17 on large number of (vastly different) machines, of that, 2 are using nouveau and 4 are using the nVidia binary drivers. (I usually use the binary drivers only if I require high-performance OpenGL) The reason I mention it, is that it's unlikely that I missed a major (Fedora specific) issue w/ nVidia binary drivers under F17. With that said, a couple of questions: 0. Please post your hardware configuration. 1. Are you using RPMFusion or are you using different nVidia RPMs repository? 2. Have you followed the nVidia HOW FAQ? (http://rpmfusion.org/Howto/nVidia) 3. Have you made sure nouveau is *disabled* in grub? 4. Why are you using akmods-nvidia instead of kmod-nvidia? Any particular reason for build the RPMs locally? 5. akmod-nvidia requires time to finish building the RPMs, have you tried giving it some time to finish? 6. Try rebooting. When you see the Loading grub message, press space (it'll bring the grub menu), select the top Fedora entry and press 'e'. Locate the line that has rhgb quiet and remove the rhgb quiet string. Once done Ctrl-X to reboot. Does it work? If it doesn't, what do you see? - Gilboa -- users mailing list users@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
Re: Fedora 17 not booting after installing akmod nvidia driver
Swapnil Bhartiya wrote: Hi, I am revisiting the same problem that I faced with Fedora 16, and the reason I could not use it. I installed 'akmod' and 'nvidia settings' from Yumex and when rebooted the screen was stuck at / em1: link becomes ready/ I logged into tty3 and then removed akmod nvidia [root@localhost ~]# yum remove akmod-nvidia.x86_64 [root@localhost ~]# yum remove akmods.noarch and now system is booting well. What is the problem? How can I use nvidia drivers without this issue. I am liking Fedora 17 very much and would like to continue to use it as my primary OS along with Ubuntu. Swapnil Please see: https://bugzilla.rpmfusion.org/show_bug.cgi?id=2353 -- users mailing list users@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
Re: Fedora 17 not booting after installing akmod nvidia driver
On Mon, Jun 4, 2012 at 6:36 AM, Swapnil Bhartiya swapnil.bhart...@gmail.com wrote: Hi, I am revisiting the same problem that I faced with Fedora 16, and the reason I could not use it. I installed 'akmod' and 'nvidia settings' from Yumex and when rebooted the screen was stuck at em1: link becomes ready I logged into tty3 and then removed akmod nvidia [root@localhost ~]# yum remove akmod-nvidia.x86_64 [root@localhost ~]# yum remove akmods.noarch and now system is booting well. What is the problem? How can I use nvidia drivers without this issue. I am liking Fedora 17 very much and would like to continue to use it as my primary OS along with Ubuntu. Unfortuantely it's difficult to make the akmods process robust so akmods should really only be used by those running rawhide OR those who are good at troubleshooting problems when things go wrong. One thing you could do after installing akmods and akmod-nvidia is to try running akmods as root and see if the build process completes so we would know if it's a systemd service related problem or something else. Richard -- users mailing list users@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
Re: Fedora 17 not booting after installing akmod nvidia driver
I'll start by saying that I'm running F17 on large number of (vastly different) machines, of that, 2 are using nouveau and 4 are using the nVidia binary drivers. (I usually use the binary drivers only if I require high-performance OpenGL) The reason I mention it, is that it's unlikely that I missed a major (Fedora specific) issue w/ nVidia binary drivers under F17. With that said, a couple of questions: 0. Please post your hardware configuration. GPU: GeForce GTX 275 Intel i5 8GB RAM 1. Are you using RPMFusion or are you using different nVidia RPMs repository? RPMFusion 2. Have you followed the nVidia HOW FAQ? (http://rpmfusion.org/Howto/nVidia) On that page it says PAE. I am using 64bit of Fedora 17, should I use PAE? I am not sure which drivers should I install. I tried both kmod and akmod from Yumex (one by one and at both times boots into Fedora and the screen get stuck with above mentioned em1: link becomes ready) 3. Have you made sure nouveau is *disabled* in grub? No. 4. Why are you using akmods-nvidia instead of kmod-nvidia? Any particular reason for build the RPMs locally? http://ask.fedoraproject.org/question/315/what-is-the-difference-between-an-akmod-and-kmod 5. akmod-nvidia requires time to finish building the RPMs, have you tried giving it some time to finish? Yes, Yumex showed it completed. 6. Try rebooting. When you see the Loading grub message, press space (it'll bring the grub menu), select the top Fedora entry and press 'e'. Locate the line that has rhgb quiet and remove the rhgb quiet string. Once done Ctrl-X to reboot. Does it work? If it doesn't, what do you see? System boots and then get stuck at em1: link becomes ready - Gilboa -- users mailing list users@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
Re: Fedora 17 not booting after installing akmod nvidia driver
On Mon, Jun 4, 2012 at 6:35 PM, Swapnil Bhartiya swapnil.bhart...@gmail.com wrote: With that said, a couple of questions: 0. Please post your hardware configuration. GPU: GeForce GTX 275 Intel i5 8GB RAM I've got a two machines using GTX 2xx cards. HW should be safe, I reckon. 2. Have you followed the nVidia HOW FAQ? (http://rpmfusion.org/Howto/nVidia) On that page it says PAE. I am using 64bit of Fedora 17, should I use PAE? x86_64 is 64bit. No need for PAE. (yum install kmod-nvidia etc) I am not sure which drivers should I install. I tried both kmod and akmod from Yumex (one by one and at both times boots into Fedora and the screen get stuck with above mentioned em1: link becomes ready) 3. Have you made sure nouveau is *disabled* in grub? No. Big no-no. nouveau collides with the nVidia binary driver. This alone might explain the issues you are facing. 1. Install the nVidia binary drivers. $ yum install -y kmod-nvidia.x86_64 xorg-x11-drv-nvidia-libs.i686 xorg-x11-drv-nvidia-libs.x86_64 (You can remove the xorg-x11-drv-nvidia-libs.i686 part if you don't need 32bit support) 2. Edit /etc/default/grub 2a. Locate a line that contains rhdb quiet 2b, Right after the quiet, add: rdblacklist=nouveau nouveau.modeset=0 (I usually also add vga= to get a nicer login screen. E.g. If your display is capable of displaying 1024x768 you can add vga=0x317) 3. Once done, rebuild the grub2 configuration. $ grub2-mkconfig -o /boot/grub2/grub.cfg 4. Reboot. 4. Why are you using akmods-nvidia instead of kmod-nvidia? Any particular reason for build the RPMs locally? http://ask.fedoraproject.org/question/315/what-is-the-difference-between-an-akmod-and-kmod In general akmods are only needed if you plan to deploy self-built / testing kernels. 5. akmod-nvidia requires time to finish building the RPMs, have you tried giving it some time to finish? Yes, Yumex showed it completed. akmods run *every* boot as a service. - Gilboa -- users mailing list users@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
Re: Fedora 17 not booting after installing akmod nvidia driver
On Mon, 2012-06-04 at 13:15 -0400, Gilboa Davara wrote: On Mon, Jun 4, 2012 at 6:35 PM, Swapnil Bhartiya swapnil.bhart...@gmail.com wrote: 4. Why are you using akmods-nvidia instead of kmod-nvidia? Any particular reason for build the RPMs locally? http://ask.fedoraproject.org/question/315/what-is-the-difference-between-an-akmod-and-kmod In general akmods are only needed if you plan to deploy self-built / testing kernels. Also useful for when Fedora pushes a new kernel and rpmfusion doesn't get an updated kmod for a couple of days. Booting is usually seamless with akmod building the replacement module when it detects it isn't there. When the kmod eventually appears, yum will grab it. By contrast, whatever ATRPMs does with the nVidia modules for RHEL is annoying as hell--I can't boot a new kernel until ATRPMS releases the corresponding module, and modules don't get deleted when their corresponding kernels do--I have to do it by hand. (Unless I've got something royally misconfigured...) 5. akmod-nvidia requires time to finish building the RPMs, have you tried giving it some time to finish? Yes, Yumex showed it completed. akmods run *every* boot as a service. AFAIK, all it does if the module is already there is detect it. I didn't think it rebuilt on every boot--only if the module is missing. -- users mailing list users@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
Re: Fedora 17 not booting after installing akmod nvidia driver
On 06/04/2012 07:15 PM, Gilboa Davara wrote: On Mon, Jun 4, 2012 at 6:35 PM, Swapnil Bhartiya swapnil.bhart...@gmail.com wrote: With that said, a couple of questions: 0. Please post your hardware configuration. GPU: GeForce GTX 275 Intel i5 8GB RAM I've got a two machines using GTX 2xx cards. HW should be safe, I reckon. 2. Have you followed the nVidia HOW FAQ? (http://rpmfusion.org/Howto/nVidia) On that page it says PAE. I am using 64bit of Fedora 17, should I use PAE? x86_64 is 64bit. No need for PAE. (yum install kmod-nvidia etc) I am not sure which drivers should I install. I tried both kmod and akmod from Yumex (one by one and at both times boots into Fedora and the screen get stuck with above mentioned em1: link becomes ready) 3. Have you made sure nouveau is *disabled* in grub? No. Big no-no. nouveau collides with the nVidia binary driver. This alone might explain the issues you are facing. 1. Install the nVidia binary drivers. $ yum install -y kmod-nvidia.x86_64 xorg-x11-drv-nvidia-libs.i686 xorg-x11-drv-nvidia-libs.x86_64 (You can remove the xorg-x11-drv-nvidia-libs.i686 part if you don't need 32bit support) 2. Edit /etc/default/grub 2a. Locate a line that contains rhdb quiet 2b, Right after the quiet, add: rdblacklist=nouveau nouveau.modeset=0 (I usually also add vga= to get a nicer login screen. E.g. If your display is capable of displaying 1024x768 you can add vga=0x317) 3. Once done, rebuild the grub2 configuration. $ grub2-mkconfig -o /boot/grub2/grub.cfg 4. Reboot. Done exactly that. I did not add vga=0x317 as my monitor is 1900x1080 I rebuilt the grub configuration as you suggested. Note: I am multi-booting with Ubuntu so that I do have a system working unless I fix Fedora issue. I did not install Fedora grub instead using Ubuntu grub. So, I also updated Ubuntu's grub. When I did everything as you stated and rebooted. But once again when I booted into Fedora the boot started and then screen was stuck here: [ 13.172058] ADDRCONF (NETDEV_CHANGE): em1: link becomes ready Swapnil -- users mailing list users@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
Re: Fedora 17 not booting after installing akmod nvidia driver
On Mon, Jun 4, 2012 at 10:49 PM, Matthew Saltzman m...@clemson.edu wrote: akmods run *every* boot as a service. AFAIK, all it does if the module is already there is detect it. I didn't think it rebuilt on every boot--only if the module is missing. Bad word selection on my part. It runs on every boot, it doesn't build the RPMs on every boot. (As you stated, if the RPM already built / pre-installed, it'll simply move on) - Gilboa -- users mailing list users@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
Re: Fedora 17 not booting after installing akmod nvidia driver
On Tue, Jun 5, 2012 at 8:29 AM, Swapnil Bhartiya swapnil.bhart...@gmail.com wrote: Done exactly that. I did not add vga=0x317 as my monitor is 1900x1080 I rebuilt the grub configuration as you suggested. Note: I am multi-booting with Ubuntu so that I do have a system working unless I fix Fedora issue. I did not install Fedora grub instead using Ubuntu grub. So, I also updated Ubuntu's grub. When I did everything as you stated and rebooted. But once again when I booted into Fedora the boot started and then screen was stuck here: [ 13.172058] ADDRCONF (NETDEV_CHANGE): em1: link becomes ready Swapnil OK. Lets try the following: 0. When Fedora boot, bring up the grub menu. 1. 'E' to edit the Fedora entry. 2. After rhgb quiet, add rdblacklist=nouveau nouveau.modeset=0 vga=0x317 3. (Notice the '3' in the end) 3. Ctrl-X to reboot. 4. Fedora will be boot, but will not try to bring up X. 5. Login as root. 6. Please post the output of: $ /sbin/lsmod | grep nouveau 7. Please post the output of: $ cat /proc/cmdline 8. If nouveau is loaded (will be shown in the output of line 6), try removing it: $ /sbin/rmmod nouveau 9. Repeat line 6, does nouveau still appear? 10. If nouveau is not present, type: $ xinit 11. If nothing happens, press Ctrl-C, and attach the contents of the /var/log/Xorg.0.log 12. If everything worked just fine, edit /etc/default/grub, locate the rhgb quiet and add rdblacklist=nouveau nouveau.modeset=0 vga=0x317. 13. Rebuild the grub configuration: $ grub2-mkconfig -o /boot/grub2/grub.cfg - Gilboa -- users mailing list users@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
