https://bugzilla.redhat.com/show_bug.cgi?id=648732 Based on this bug report, is there a fix for this problem. I am unable to install my nvidia drivers because of this bug. I don't understand it at all. Every time I installed the drivers and reboot this is the results. I don't know why these two programs are in conflict but it seems they are. Will somebody take a look at this problem. I am running Fedora 16/64-bit on Dell 9400 Inspiron with a Quadro FX2500m video card.
On 28 November 2011 20:14, Lawrence Graves lgraves95@gmail.com wrote:
https://bugzilla.redhat.com/show_bug.cgi?id=648732 Based on this bug report, is there a fix for this problem. I am unable to install my nvidia drivers because of this bug. I don't understand it at all. Every time I installed the drivers and reboot this is the results. I don't know why these two programs are in conflict but it seems they are. Will somebody take a look at this problem. I am running Fedora 16/64-bit on Dell 9400 Inspiron with a Quadro FX2500m video card.
Hi,
So far as I can see (and I may have missed an email, because you seem to have started several different threads on this) you've never said why you think the Intel wireless problem is connected to your nvidia problem. There's no mention of nvidia in that bug report and for all I know the two may be completely unrelated. If you can set out: what you've tried to install the drivers, in what way the install process fails or they don't work and any other information you think is relevant such as why you think the iwl problem is related then someone may be able to help. Currently you're the only person with enough information to investigate the problem.
Finally, does disabling 802.11n as described in comment 68 of that bug https://bugzilla.redhat.com/show_bug.cgi?id=648732#c68 fix the wifi problem for you?
On 12/01/2011 12:53 AM, Ian Malone wrote:
On 28 November 2011 20:14, Lawrence Graveslgraves95@gmail.com wrote:
https://bugzilla.redhat.com/show_bug.cgi?id=648732 Based on this bug report, is there a fix for this problem. I am unable to install my nvidia drivers because of this bug. I don't understand it at all. Every time I installed the drivers and reboot this is the results. I don't know why these two programs are in conflict but it seems they are. Will somebody take a look at this problem. I am running Fedora 16/64-bit on Dell 9400 Inspiron with a Quadro FX2500m video card.
Hi,
So far as I can see (and I may have missed an email, because you seem to have started several different threads on this) you've never said why you think the Intel wireless problem is connected to your nvidia problem. There's no mention of nvidia in that bug report and for all I know the two may be completely unrelated. If you can set out: what you've tried to install the drivers, in what way the install process fails or they don't work and any other information you think is relevant such as why you think the iwl problem is related then someone may be able to help. Currently you're the only person with enough information to investigate the problem.
Finally, does disabling 802.11n as described in comment 68 of that bug https://bugzilla.redhat.com/show_bug.cgi?id=648732#c68 fix the wifi problem for you?
-- The problem is what is preventing me from installing nvidia drivers. I disabled the wifi firmware and used my wlan line to install and still get the same results. Aggregation error. Lawrence Graves All things are workable but don't all things work.
On 1 December 2011 13:25, Lawrence Graves lgraves95@gmail.com wrote:
On 12/01/2011 12:53 AM, Ian Malone wrote: On 28 November 2011 20:14, Lawrence Graves lgraves95@gmail.com wrote:
(I've fixed the quoting)
https://bugzilla.redhat.com/show_bug.cgi?id=648732 Based on this bug report, is there a fix for this problem. I am unable to install my nvidia drivers because of this bug. I don't understand it at all. Every time I installed the drivers and reboot this is the results. I don't know why these two programs are in conflict but it seems they are. Will somebody take a look at this problem. I am running Fedora 16/64-bit on Dell 9400 Inspiron with a Quadro FX2500m video card.
So far as I can see (and I may have missed an email, because you seem to have started several different threads on this) you've never said why you think the Intel wireless problem is connected to your nvidia problem. There's no mention of nvidia in that bug report and for all I know the two may be completely unrelated. If you can set out: what you've tried to install the drivers, in what way the install process fails or they don't work and any other information you think is relevant such as why you think the iwl problem is related then someone may be able to help. Currently you're the only person with enough information to investigate the problem.
-- The problem is what is preventing me from installing nvidia drivers. I disabled the wifi firmware and used my wlan line to install and still get the same results. Aggregation error.
Again: If you can set out: what you've tried to install the drivers, in what way the install process fails or they don't work and any other information you think is relevant such as why you think the iwl problem is related then someone may be able to help. Currently you're the only person with enough information to investigate the problem. - with more words. And steps.
I'm going to take a guess based on what you've just said and suggest that: 1. Your problem is actually that the yum install is not working due to some kind of rpm database or connectivity issue. 2. It has nothing specifically to do with either nvidia or intel wifi.
But, honestly, I've no idea what you've done, what you're experiencing or what problem you're trying to solve. So without more detail I'm just going to have to stop here.
On 12/01/2011 11:30 AM, Ian Malone wrote:
On 1 December 2011 13:25, Lawrence Graveslgraves95@gmail.com wrote:
On 12/01/2011 12:53 AM, Ian Malone wrote: On 28 November 2011 20:14, Lawrence Graveslgraves95@gmail.com wrote:
(I've fixed the quoting)
https://bugzilla.redhat.com/show_bug.cgi?id=648732 Based on this bug report, is there a fix for this problem. I am unable to install my nvidia drivers because of this bug. I don't understand it at all. Every time I installed the drivers and reboot this is the results. I don't know why these two programs are in conflict but it seems they are. Will somebody take a look at this problem. I am running Fedora 16/64-bit on Dell 9400 Inspiron with a Quadro FX2500m video card.
So far as I can see (and I may have missed an email, because you seem to have started several different threads on this) you've never said why you think the Intel wireless problem is connected to your nvidia problem. There's no mention of nvidia in that bug report and for all I know the two may be completely unrelated. If you can set out: what you've tried to install the drivers, in what way the install process fails or they don't work and any other information you think is relevant such as why you think the iwl problem is related then someone may be able to help. Currently you're the only person with enough information to investigate the problem.
-- The problem is what is preventing me from installing nvidia drivers. I disabled the wifi firmware and used my wlan line to install and still get the same results. Aggregation error.
Again: If you can set out: what you've tried to install the drivers, in what way the install process fails or they don't work and any other information you think is relevant such as why you think the iwl problem is related then someone may be able to help. Currently you're the only person with enough information to investigate the problem.
- with more words. And steps.
I'm going to take a guess based on what you've just said and suggest that:
- Your problem is actually that the yum install is not working due to
some kind of rpm database or connectivity issue. 2. It has nothing specifically to do with either nvidia or intel wifi.
But, honestly, I've no idea what you've done, what you're experiencing or what problem you're trying to solve. So without more detail I'm just going to have to stop here.
I have done a yum install akmod-nvidia kmod-nvidia, reboot and the screen flashes about three times and comes back with a list of the programs it started and waiting for about 1 to 2 minutes and it gives me the message of :Aggregation not enabled for tid 0 because load = 1, waiting a few more minutes and it says the same thing again only it changes load =0 or 6 or 4 etc. This is all I can explain because I am not as technical as you are. Sorry I can't do any more.http://comments.gmane.org/gmane.linux.redhat.fedora.general/404038
Lawrence Graves lgraves95@gmail.com wrote:
https://bugzilla.redhat.com/show_bug.cgi?id=648732 Based on this bug report, is there a fix for this problem. I am unable to install my nvidia drivers because of this bug. I don't understand it at all. Every time I installed the drivers and reboot this is the results. I don't know why these two programs are in conflict but it seems they are. Will somebody take a look at this problem. I am running Fedora 16/64-bit on Dell 9400 Inspiron with a Quadro FX2500m video card.
The problem is what is preventing me from installing nvidia drivers. I disabled the wifi firmware and used my wlan line to install and still get the same results. Aggregation error.
Ian Malone wrote:
If you can set out: what you've tried to install the drivers, in what way the install process fails or they don't work and any other information you think is relevant such as why you think the iwl problem is related then someone may be able to help. Currently you're the only person with enough information to investigate the problem.
- with more words. And steps.
I'm going to take a guess based on what you've just said and suggest that:
- Your problem is actually that the yum install is not working due to
some kind of rpm database or connectivity issue. 2. It has nothing specifically to do with either nvidia or intel wifi.
But, honestly, I've no idea what you've done, what you're experiencing or what problem you're trying to solve. So without more detail I'm just going to have to stop here.
On 1 December 2011 20:57, Lawrence Graves lgraves95@gmail.com wrote:
I have done a yum install akmod-nvidia kmod-nvidia, reboot and the screen flashes about three times and comes back with a list of the programs it started and waiting for about 1 to 2 minutes and it gives me the message of :Aggregation not enabled for tid 0 because load = 1, waiting a few more minutes and it says the same thing again only it changes load =0 or 6 or 4 etc. This is all I can explain because I am not as technical as you are. Sorry I can't do any more.http://comments.gmane.org/gmane.linux.redhat.fedora.general/404038
Thank you, it's not in-depth technical analysis I wanted, just a literal description of what was happening.
What you're describing (screen flashes three times and then changes to text mode) is X trying to start and failing. This does probably indicate the nvidia drivers aren't loading, by being in text mode you're also seeing any other startup errors, including a different and probably unrelated error from the iwl startup. You should be able to login in text mode by pressing Ctl-Alt-F2 to get a login prompt (or try F1 through to F8 if that doesn't work).
At this point there are a few things that would be useful: 1. output of the command lsmod 2. Contents of /var/log/X.0.log 3. output of rpm -qa|grep nvidia
If you're not able to copy things off the system then just these instead: lsmod |grep nv lsmod |grep nouveau grep EE /var/log/X.0.log rpm -qa|grep nvidia
On 12/01/2011 03:52 PM, Ian Malone wrote:
Lawrence Graveslgraves95@gmail.com wrote:
https://bugzilla.redhat.com/show_bug.cgi?id=648732 Based on this bug report, is there a fix for this problem. I am unable to install my nvidia drivers because of this bug. I don't understand it at all. Every time I installed the drivers and reboot this is the results. I don't know why these two programs are in conflict but it seems they are. Will somebody take a look at this problem. I am running Fedora 16/64-bit on Dell 9400 Inspiron with a Quadro FX2500m video card.
The problem is what is preventing me from installing nvidia drivers. I disabled the wifi firmware and used my wlan line to install and still get the same results. Aggregation error.
Ian Malone wrote:
If you can set out: what you've tried to install the drivers, in what way the install process fails or they don't work and any other information you think is relevant such as why you think the iwl problem is related then someone may be able to help. Currently you're the only person with enough information to investigate the problem.
- with more words. And steps.
I'm going to take a guess based on what you've just said and suggest that:
- Your problem is actually that the yum install is not working due to
some kind of rpm database or connectivity issue. 2. It has nothing specifically to do with either nvidia or intel wifi.
But, honestly, I've no idea what you've done, what you're experiencing or what problem you're trying to solve. So without more detail I'm just going to have to stop here.
On 1 December 2011 20:57, Lawrence Graveslgraves95@gmail.com wrote:
I have done a yum install akmod-nvidia kmod-nvidia, reboot and the screen flashes about three times and comes back with a list of the programs it started and waiting for about 1 to 2 minutes and it gives me the message of :Aggregation not enabled for tid 0 because load = 1, waiting a few more minutes and it says the same thing again only it changes load =0 or 6 or 4 etc. This is all I can explain because I am not as technical as you are. Sorry I can't do any more.http://comments.gmane.org/gmane.linux.redhat.fedora.general/404038
Thank you, it's not in-depth technical analysis I wanted, just a literal description of what was happening.
What you're describing (screen flashes three times and then changes to text mode) is X trying to start and failing. This does probably indicate the nvidia drivers aren't loading, by being in text mode you're also seeing any other startup errors, including a different and probably unrelated error from the iwl startup. You should be able to login in text mode by pressing Ctl-Alt-F2 to get a login prompt (or try F1 through to F8 if that doesn't work).
At this point there are a few things that would be useful:
- output of the command
lsmod 2. Contents of /var/log/X.0.log 3. output of rpm -qa|grep nvidia
If you're not able to copy things off the system then just these instead: lsmod |grep nv lsmod |grep nouveau grep EE /var/log/X.0.log rpm -qa|grep nvidia
This is all I could get. Hope this helps and thanks for your patience.
On 12/01/2011 03:52 PM, Ian Malone wrote:
Lawrence Graveslgraves95@gmail.com wrote:
https://bugzilla.redhat.com/show_bug.cgi?id=648732 Based on this bug report, is there a fix for this problem. I am unable to install my nvidia drivers because of this bug. I don't understand it at all. Every time I installed the drivers and reboot this is the results. I don't know why these two programs are in conflict but it seems they are. Will somebody take a look at this problem. I am running Fedora 16/64-bit on Dell 9400 Inspiron with a Quadro FX2500m video card.
The problem is what is preventing me from installing nvidia drivers. I disabled the wifi firmware and used my wlan line to install and still get the same results. Aggregation error.
Ian Malone wrote:
If you can set out: what you've tried to install the drivers, in what way the install process fails or they don't work and any other information you think is relevant such as why you think the iwl problem is related then someone may be able to help. Currently you're the only person with enough information to investigate the problem.
- with more words. And steps.
I'm going to take a guess based on what you've just said and suggest that:
- Your problem is actually that the yum install is not working due to
some kind of rpm database or connectivity issue. 2. It has nothing specifically to do with either nvidia or intel wifi.
But, honestly, I've no idea what you've done, what you're experiencing or what problem you're trying to solve. So without more detail I'm just going to have to stop here.
On 1 December 2011 20:57, Lawrence Graveslgraves95@gmail.com wrote:
I have done a yum install akmod-nvidia kmod-nvidia, reboot and the screen flashes about three times and comes back with a list of the programs it started and waiting for about 1 to 2 minutes and it gives me the message of :Aggregation not enabled for tid 0 because load = 1, waiting a few more minutes and it says the same thing again only it changes load =0 or 6 or 4 etc. This is all I can explain because I am not as technical as you are. Sorry I can't do any more.http://comments.gmane.org/gmane.linux.redhat.fedora.general/404038
Thank you, it's not in-depth technical analysis I wanted, just a literal description of what was happening.
What you're describing (screen flashes three times and then changes to text mode) is X trying to start and failing. This does probably indicate the nvidia drivers aren't loading, by being in text mode you're also seeing any other startup errors, including a different and probably unrelated error from the iwl startup. You should be able to login in text mode by pressing Ctl-Alt-F2 to get a login prompt (or try F1 through to F8 if that doesn't work).
At this point there are a few things that would be useful:
- output of the command
lsmod 2. Contents of /var/log/X.0.log 3. output of rpm -qa|grep nvidia
If you're not able to copy things off the system then just these instead: lsmod |grep nv lsmod |grep nouveau grep EE /var/log/X.0.log rpm -qa|grep nvidia
This is all I could get. Hope this helps and thanks for your patience.
This looks as if it could be another instance of the problems with nvidia 290.10 Try reverting or going to the new 'long-lived' 275.36
Several examples on the atrpms-users list.
HTH
John P
On 2 December 2011 08:46, John Pilkington J.Pilk@tesco.net wrote:
This looks as if it could be another instance of the problems with nvidia 290.10 Try reverting or going to the new 'long-lived' 275.36
Several examples on the atrpms-users list.
Are you sure? From the lsmod and Xorg it looks like nouveau is being loaded, and nvidia is not.
If Lawrence has network access in text only mode I would suggest as root: yum reinstall xorg-x11-drv-nvidia nvidia-settings akmod-nvidia kmod-nvidia xorg-x11-drv-nvidia-libs nvidia-xconfig
(All one line)
If that doesn't help or there's no net access then (again as root), first line is moving the file to a backup with today's date: mv /etc/X11/xorg.conf /etc/X11/xorg.conf.backup-20111202 nvidia-config-display echo blacklist nouveau >> /etc/modprobe.d/blacklist-nouveau.conf dracut /boot/initramfs-$(uname -r).img $(uname -r)
This (in order), moves your current Xorg configuration to a backup file, uses nvidia-config-display to create a new one, tells the system not to use the nouveau driver (you'll need to undo this if you ever want to use nouveau) and creates a new initrd with nouveau excluded. Let us know how you get on.
On 02/12/11 12:04, Ian Malone wrote:
On 2 December 2011 08:46, John PilkingtonJ.Pilk@tesco.net wrote:
This looks as if it could be another instance of the problems with nvidia 290.10 Try reverting or going to the new 'long-lived' 275.36
Several examples on the atrpms-users list.
No, I'm not sure at all: I just saw the 290.10 packages and knew that several people, including me, had reported segfaults etc that have gone away after one of the options I suggested.
Are you sure? From the lsmod and Xorg it looks like nouveau is being loaded, and nvidia is not.
If Lawrence has network access in text only mode I would suggest as root: yum reinstall xorg-x11-drv-nvidia nvidia-settings akmod-nvidia kmod-nvidia xorg-x11-drv-nvidia-libs nvidia-xconfig
(All one line)
If that doesn't help or there's no net access then (again as root), first line is moving the file to a backup with today's date: mv /etc/X11/xorg.conf /etc/X11/xorg.conf.backup-20111202 nvidia-config-display echo blacklist nouveau>> /etc/modprobe.d/blacklist-nouveau.conf dracut /boot/initramfs-$(uname -r).img $(uname -r)
This (in order), moves your current Xorg configuration to a backup file, uses nvidia-config-display to create a new one, tells the system not to use the nouveau driver (you'll need to undo this if you ever want to use nouveau) and creates a new initrd with nouveau excluded. Let us know how you get on.
On 12/02/2011 05:04 AM, Ian Malone wrote:
On 2 December 2011 08:46, John PilkingtonJ.Pilk@tesco.net wrote:
This looks as if it could be another instance of the problems with nvidia 290.10 Try reverting or going to the new 'long-lived' 275.36
Several examples on the atrpms-users list.
Are you sure? From the lsmod and Xorg it looks like nouveau is being loaded, and nvidia is not.
If Lawrence has network access in text only mode I would suggest as root: yum reinstall xorg-x11-drv-nvidia nvidia-settings akmod-nvidia kmod-nvidia xorg-x11-drv-nvidia-libs nvidia-xconfig
(All one line)
If that doesn't help or there's no net access then (again as root), first line is moving the file to a backup with today's date: mv /etc/X11/xorg.conf /etc/X11/xorg.conf.backup-20111202 nvidia-config-display echo blacklist nouveau>> /etc/modprobe.d/blacklist-nouveau.conf dracut /boot/initramfs-$(uname -r).img $(uname -r)
This (in order), moves your current Xorg configuration to a backup file, uses nvidia-config-display to create a new one, tells the system not to use the nouveau driver (you'll need to undo this if you ever want to use nouveau) and creates a new initrd with nouveau excluded. Let us know how you get on.
I tried all that you instructed to no avail. When I tried reinstalling the nvidia drivers, I received the message that there were no mirrors. When I tried the mv, it came back and said nvidia-config-display is not a directory. I agree with the first statement made, the nouveau drivers are being loaded and not the nvidia drivers for some strange reason. I have never had this problem before. I bought the lastest nvidia card with the express purpose of not facing these problems. Oh well:-) I still express my thanks for your hard work. I guess it is back to the drawing board. I wish I could send my laptop to you. I believe if you could see what it is doing with your own eyes and not the eyes of a novice, it would be an easy fix.
On 12/02/2011 05:54 AM, John Pilkington wrote:
On 02/12/11 12:04, Ian Malone wrote:
On 2 December 2011 08:46, John PilkingtonJ.Pilk@tesco.net wrote:
This looks as if it could be another instance of the problems with nvidia 290.10 Try reverting or going to the new 'long-lived' 275.36
Several examples on the atrpms-users list.
No, I'm not sure at all: I just saw the 290.10 packages and knew that several people, including me, had reported segfaults etc that have gone away after one of the options I suggested.
Are you sure? From the lsmod and Xorg it looks like nouveau is being loaded, and nvidia is not.
If Lawrence has network access in text only mode I would suggest as root: yum reinstall xorg-x11-drv-nvidia nvidia-settings akmod-nvidia kmod-nvidia xorg-x11-drv-nvidia-libs nvidia-xconfig
(All one line)
If that doesn't help or there's no net access then (again as root), first line is moving the file to a backup with today's date: mv /etc/X11/xorg.conf /etc/X11/xorg.conf.backup-20111202 nvidia-config-display echo blacklist nouveau>> /etc/modprobe.d/blacklist-nouveau.conf dracut /boot/initramfs-$(uname -r).img $(uname -r)
This (in order), moves your current Xorg configuration to a backup file, uses nvidia-config-display to create a new one, tells the system not to use the nouveau driver (you'll need to undo this if you ever want to use nouveau) and creates a new initrd with nouveau excluded. Let us know how you get on.
I am not sure as to how to do that.
On 2 December 2011 13:48, Lawrence Graves lgraves95@gmail.com wrote:
On 12/02/2011 05:04 AM, Ian Malone wrote:
If Lawrence has network access in text only mode I would suggest as root: yum reinstall xorg-x11-drv-nvidia nvidia-settings akmod-nvidia kmod-nvidia xorg-x11-drv-nvidia-libs nvidia-xconfig
If that doesn't help or there's no net access then (again as root), first line is moving the file to a backup with today's date:
This (in order), moves your current Xorg configuration to a backup file, uses nvidia-config-display to create a new one, tells the system not to use the nouveau driver (you'll need to undo this if you ever want to use nouveau) and creates a new initrd with nouveau excluded. Let us know how you get on.
I tried all that you instructed to no avail. When I tried reinstalling the nvidia drivers, I received the message that there were no mirrors.
Sounds like you don't have a net connection up. If you had it configured previously you /might/ be able to get it up by doing: systemctl start NetworkManager.service
When I tried the mv, it came back and said nvidia-config-display is not a directory.
Sorry, those should all be separate lines, I've put a $ to indicate each one below (also it should have been nvidia-xconfig, not nvidia-display-config, again fixed this below):
$ mv /etc/X11/xorg.conf /etc/X11/xorg.conf.backup-20111202 $ nvidia-xconfig $ echo blacklist nouveau >> /etc/modprobe.d/blacklist-nouveau.conf $ dracut /boot/initramfs-$(uname -r).img $(uname -r)
On 02/12/11 12:04, Ian Malone wrote:
This (in order), moves your current Xorg configuration to a backup file, uses nvidia-config-display to create a new one, tells the system not to use the nouveau driver (you'll need to undo this if you ever want to use nouveau) and creates a new initrd with nouveau excluded. Let us know how you get on.
On 2 December 2011 14:06, Lawrence Graves lgraves95@gmail.com wrote:
I am not sure as to how to do that.
It's just this series of 4 commands, run as root. (Don't enter the # signs, they're just to mark the start of each line):
# mv /etc/X11/xorg.conf /etc/X11/xorg.conf.backup-20111202 # nvidia-xconfig # echo blacklist nouveau >> /etc/modprobe.d/blacklist-nouveau.conf # dracut /boot/initramfs-$(uname -r).img $(uname -r)
On 12/02/2011 11:18 AM, Ian Malone wrote:
On 02/12/11 12:04, Ian Malone wrote:
This (in order), moves your current Xorg configuration to a backup file, uses nvidia-config-display to create a new one, tells the system not to use the nouveau driver (you'll need to undo this if you ever want to use nouveau) and creates a new initrd with nouveau excluded. Let us know how you get on.
On 2 December 2011 14:06, Lawrence Graveslgraves95@gmail.com wrote:
I am not sure as to how to do that.
It's just this series of 4 commands, run as root. (Don't enter the # signs, they're just to mark the start of each line):
# mv /etc/X11/xorg.conf /etc/X11/xorg.conf.backup-20111202 # nvidia-xconfig # echo blacklist nouveau>> /etc/modprobe.d/blacklist-nouveau.conf # dracut /boot/initramfs-$(uname -r).img $(uname -r)
I am very sorry but it didn't work. I got the same read out results. I uninstall the nvidia drivers and reinstalled them and tried it a second time with no results.
On 2 December 2011 21:08, Lawrence Graves lgraves95@gmail.com wrote:
On 12/02/2011 11:18 AM, Ian Malone wrote:
On 02/12/11 12:04, Ian Malone wrote:
This (in order), moves your current Xorg configuration to a backup file, uses nvidia-config-display to create a new one, tells the system not to use the nouveau driver (you'll need to undo this if you ever want to use nouveau) and creates a new initrd with nouveau excluded. Let us know how you get on.
On 2 December 2011 14:06, Lawrence Graves lgraves95@gmail.com wrote:
I am not sure as to how to do that.
It's just this series of 4 commands, run as root. (Don't enter the # signs, they're just to mark the start of each line):
# mv /etc/X11/xorg.conf /etc/X11/xorg.conf.backup-20111202 # nvidia-xconfig # echo blacklist nouveau >> /etc/modprobe.d/blacklist-nouveau.conf # dracut /boot/initramfs-$(uname -r).img $(uname -r)
I am very sorry but it didn't work. I got the same read out results. I uninstall the nvidia drivers and reinstalled them and tried it a second time with no results.
Were there any errors reported while running those commands? Has the machine been rebooted? If you do lsmod |grep nouveau Do you still see the nouveau module? Does lsmod |grep nv Show the old nv module or nvidia?
I'm wondering if it's necessary to reboot between after adding the blacklist line and before doing dracut. If you reboot and nouveau is not showing up with the 'lsmod|grep nouveau' above, then it may be worth trying the dracut line again. Also the new /etc/X11/xorg.conf would be good to see.
On 12/03/2011 03:37 AM, Ian Malone wrote:
On 2 December 2011 21:08, Lawrence Graveslgraves95@gmail.com wrote:
On 12/02/2011 11:18 AM, Ian Malone wrote:
On 02/12/11 12:04, Ian Malone wrote:
This (in order), moves your current Xorg configuration to a backup file, uses nvidia-config-display to create a new one, tells the system not to use the nouveau driver (you'll need to undo this if you ever want to use nouveau) and creates a new initrd with nouveau excluded. Let us know how you get on.
On 2 December 2011 14:06, Lawrence Graveslgraves95@gmail.com wrote:
I am not sure as to how to do that.
It's just this series of 4 commands, run as root. (Don't enter the # signs, they're just to mark the start of each line):
# mv /etc/X11/xorg.conf /etc/X11/xorg.conf.backup-20111202 # nvidia-xconfig # echo blacklist nouveau>> /etc/modprobe.d/blacklist-nouveau.conf # dracut /boot/initramfs-$(uname -r).img $(uname -r)
I am very sorry but it didn't work. I got the same read out results. I uninstall the nvidia drivers and reinstalled them and tried it a second time with no results.
Were there any errors reported while running those commands? Has the machine been rebooted? If you do lsmod |grep nouveau Do you still see the nouveau module? Does lsmod |grep nv Show the old nv module or nvidia?
I'm wondering if it's necessary to reboot between after adding the blacklist line and before doing dracut. If you reboot and nouveau is not showing up with the 'lsmod|grep nouveau' above, then it may be worth trying the dracut line again. Also the new /etc/X11/xorg.conf would be good to see.
Here is the results of your questions? I am very grateful to you for all your help. See attached.
On 3 December 2011 14:18, Lawrence Graves lgraves95@gmail.com wrote:
On 2 December 2011 21:08, Lawrence Graves lgraves95@gmail.com wrote:
On 12/02/2011 11:18 AM, Ian Malone wrote:
On 02/12/11 12:04, Ian Malone wrote:
Ian Malone wrote:
It's just this series of 4 commands, run as root. (Don't enter the # signs, they're just to mark the start of each line):
# mv /etc/X11/xorg.conf /etc/X11/xorg.conf.backup-20111202 # nvidia-xconfig # echo blacklist nouveau >> /etc/modprobe.d/blacklist-nouveau.conf # dracut /boot/initramfs-$(uname -r).img $(uname -r)
Lawrence Graves lgraves95@gmail.com wrote:
I am very sorry but it didn't work. I got the same read out results. I uninstall the nvidia drivers and reinstalled them and tried it a second time with no results.
Ian Malone wrote:
Were there any errors reported while running those commands? Has the machine been rebooted? If you do lsmod |grep nouveau Do you still see the nouveau module? Does lsmod |grep nv Show the old nv module or nvidia?
I'm wondering if it's necessary to reboot between after adding the blacklist line and before doing dracut. If you reboot and nouveau is not showing up with the 'lsmod|grep nouveau' above, then it may be worth trying the dracut line again. Also the new /etc/X11/xorg.conf would be good to see.
Lawrence Graves lgraves95@gmail.com wrote:
Here is the results of your questions? I am very grateful to you for all your help. See attached.
It looks like nouveau is still being loaded. If you can post the /etc/X11/xorg.org file and /var/log/Xorg.0.log that might help pin down the cause.
However, I think I missed out a necessary option for the dracut command, try (again don't type the # they just indicate separate lines run as root): # mv /boot/initramfs-$(uname -r).img /boot/initramfs-$(uname -r).img.bak # dracut /boot/initramfs-$(uname -r).img $(uname -r)
(For the record: I meant to suggest dracut -f which would force overwrite of the existing initramfs file, however it's probably safer to move it to a backup as in the two lines above.)
Sorry this is taking so much back-and-forth, I've been on your end of this kind of thing and I know it's frustrating.
On 12/03/2011 01:46 PM, Ian Malone wrote:
On 3 December 2011 14:18, Lawrence Graveslgraves95@gmail.com wrote:
On 2 December 2011 21:08, Lawrence Graveslgraves95@gmail.com wrote:
On 12/02/2011 11:18 AM, Ian Malone wrote:
On 02/12/11 12:04, Ian Malone wrote:
Ian Malone wrote:
It's just this series of 4 commands, run as root. (Don't enter the # signs, they're just to mark the start of each line):
# mv /etc/X11/xorg.conf /etc/X11/xorg.conf.backup-20111202 # nvidia-xconfig # echo blacklist nouveau>> /etc/modprobe.d/blacklist-nouveau.conf # dracut /boot/initramfs-$(uname -r).img $(uname -r)
Lawrence Graveslgraves95@gmail.com wrote:
I am very sorry but it didn't work. I got the same read out results. I uninstall the nvidia drivers and reinstalled them and tried it a second time with no results.
Ian Malone wrote:
Were there any errors reported while running those commands? Has the machine been rebooted? If you do lsmod |grep nouveau Do you still see the nouveau module? Does lsmod |grep nv Show the old nv module or nvidia?
I'm wondering if it's necessary to reboot between after adding the blacklist line and before doing dracut. If you reboot and nouveau is not showing up with the 'lsmod|grep nouveau' above, then it may be worth trying the dracut line again. Also the new /etc/X11/xorg.conf would be good to see.
Lawrence Graveslgraves95@gmail.com wrote:
Here is the results of your questions? I am very grateful to you for all your help. See attached.
It looks like nouveau is still being loaded. If you can post the /etc/X11/xorg.org file and /var/log/Xorg.0.log that might help pin down the cause.
However, I think I missed out a necessary option for the dracut command, try (again don't type the # they just indicate separate lines run as root): # mv /boot/initramfs-$(uname -r).img /boot/initramfs-$(uname -r).img.bak # dracut /boot/initramfs-$(uname -r).img $(uname -r)
(For the record: I meant to suggest dracut -f which would force overwrite of the existing initramfs file, however it's probably safer to move it to a backup as in the two lines above.)
Sorry this is taking so much back-and-forth, I've been on your end of this kind of thing and I know it's frustrating.
Sorry, I forgot to give you this log.
Ian Malone wrote:
If you do lsmod |grep nouveau Do you still see the nouveau module? Does lsmod |grep nv Show the old nv module or nvidia?
Ian Malone wrote:
It looks like nouveau is still being loaded. If you can post the /etc/X11/xorg.org file and /var/log/Xorg.0.log that might help pin down the cause.
However, I think I missed out a necessary option for the dracut command, try (again don't type the # they just indicate separate lines run as root): # mv /boot/initramfs-$(uname -r).img /boot/initramfs-$(uname -r).img.bak # dracut /boot/initramfs-$(uname -r).img $(uname -r)
Lawrence Graves lgraves95@gmail.com wrote:
Sorry, I forgot to give you this log.
/etc/X11/xorg.org is actually a configuration file rather than a log, this one is attempting to set up nvidia which is correct. If nouveau is still being loaded then I think it must be coming from the initramfs, things to try:
1. Run the 'mv' and 'dracut' commands given above (I know you've done the dracut one already, but it probably refused to overwrite the existing initramfs file).
2. If after rebooting you're still finding nouveau is being loaded (by running the lsmod|grep nouveau command) then do: # cat /etc/modprobe.d/blacklist-nouveau.conf
and check it has the line 'blacklist nouveau'. If it does then try this: # dracut -f /boot/initramfs-$(uname -r).img $(uname -r)
(again, don't type those '#' signs)
3. If at this point after rebooting nouveau is still starting then I'm really stumped. The log file /var/log/Xorg.0.log would be useful. You could also capture the dmesg information (the kernel messages) by doing: dmesg > dmesg-out.txt If you do send the dmesg-out.txt file created then it's probably best to send that direct to my email rather than the users list as it will be quite big.
On 4 December 2011 11:22, Ian Malone ibmalone@gmail.com wrote:
- If at this point after rebooting nouveau is still starting then I'm
really stumped. The log file /var/log/Xorg.0.log would be useful. You could also capture the dmesg information (the kernel messages) by doing: dmesg > dmesg-out.txt If you do send the dmesg-out.txt file created then it's probably best to send that direct to my email rather than the users list as it will be quite big.
I've got Lawrence's dmesg output and nouveau is being loaded very early on:
[7.591930] [drm] Initialized drm 1.1.0 20060810 [7.613319] nouveau 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 [7.613325] nouveau 0000:01:00.0: setting latency timer to 64 [7.616906] microcode: CPU0 updated to revision 0xd1, date = 2010-10-01 [7.616918] microcode: CPU1 sig=0x6f6, pf=0x20, revision=0xc7 [7.625064] [drm] nouveau 0000:01:00.0: Detected an NV40 generation card (0x049a00a2) [7.626500] [drm] nouveau 0000:01:00.0: Attempting to load BIOS image from PRAMIN [7.650724] cfg80211: Calling CRDA to update world regulatory domain [7.653761] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.06
I don't have confirmation from him that he's been able to check: cat /etc/modprobe.d/blacklist-nouveau.conf
has the 'blacklist nouveau' line and successfully run: dracut -f /boot/initramfs-$(uname -r).img $(uname -r)
If he has done these then does anyone know how nouveau could still get loaded? The next step would be to add nouveau as a rdblacklist line in the kernel arguments, it looks like this is now done via GRUB_CMDLINE_LINUX in /etc/default/grub.
On 12/04/2011 07:44 AM, Ian Malone wrote:
On 4 December 2011 11:22, Ian Maloneibmalone@gmail.com wrote:
- If at this point after rebooting nouveau is still starting then I'm
really stumped. The log file /var/log/Xorg.0.log would be useful. You could also capture the dmesg information (the kernel messages) by doing: dmesg> dmesg-out.txt If you do send the dmesg-out.txt file created then it's probably best to send that direct to my email rather than the users list as it will be quite big.
I've got Lawrence's dmesg output and nouveau is being loaded very early on:
[7.591930] [drm] Initialized drm 1.1.0 20060810 [7.613319] nouveau 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 [7.613325] nouveau 0000:01:00.0: setting latency timer to 64 [7.616906] microcode: CPU0 updated to revision 0xd1, date = 2010-10-01 [7.616918] microcode: CPU1 sig=0x6f6, pf=0x20, revision=0xc7 [7.625064] [drm] nouveau 0000:01:00.0: Detected an NV40 generation card (0x049a00a2) [7.626500] [drm] nouveau 0000:01:00.0: Attempting to load BIOS image from PRAMIN [7.650724] cfg80211: Calling CRDA to update world regulatory domain [7.653761] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.06
I don't have confirmation from him that he's been able to check: cat /etc/modprobe.d/blacklist-nouveau.conf
has the 'blacklist nouveau' line and successfully run: dracut -f /boot/initramfs-$(uname -r).img $(uname -r)
If he has done these then does anyone know how nouveau could still get loaded? The next step would be to add nouveau as a rdblacklist line in the kernel arguments, it looks like this is now done via GRUB_CMDLINE_LINUX in /etc/default/grub.
I just placed rdblacklist=nouveau in the grub command line and also added it to the blacklist.conf file and then rebooted and nothing. It blinked about 3 times and then the readout it showed in the beginning and then 1 minute later the error message: iwl4965 0000:0c:00.0: Aggregation not enabled for tid 0 because load=1.
Ian Malone wrote:
If he has done these then does anyone know how nouveau could still get loaded? The next step would be to add nouveau as a rdblacklist line in the kernel arguments, it looks like this is now done via GRUB_CMDLINE_LINUX in /etc/default/grub.
Lawrence Graves lgraves95@gmail.com wrote:
I just placed rdblacklist=nouveau in the grub command line and also added it to the blacklist.conf file and then rebooted and nothing. It blinked about 3 times and then the readout it showed in the beginning and then 1 minute later the error message: iwl4965 0000:0c:00.0: Aggregation not enabled for tid 0 because load=1.
Okay, I think we're getting somewhere. This is different to what it was doing before? If you can get to a text login screen (Ctl-Alt-F2, or try Ctl-Alt- F1 through to F8) then check nouveau isn't being loaded and see if you can get hold of the Xorg startup log /etc/X11/X.0.org
If you want to be able to rule out the iwl4965 module as a cause at this point then you can use an rdblacklist=iwl4965 kernel argument TOGETHER WITH the rdblacklist=nouveau. If X starts up then some conflict with iwl4965 is the cause if not then hopefully the X.0.org file will indicate what the problem is.
-
Ian Malone -
John Pilkington -
Lawrence E Graves