You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all, I would like to thank everyone for the project, it is of real importance and I am really thankful for it. Keep up with the good job..
I am having some trouble with the whole disable-card and power management in Fedora 16.
My laptop is
The temperature is still high ( 65 º C with the card OFF and 78 º C and more with the card ON ) and sometimes the card is not really disabled on boot time, so I have to disable it manually. I compiled things from source following a tutorial found here http://fedoraforum.org/forum/showthread.php?t=272692
Do you have logs for a session in which the card is not automagically disabled? You do not need the load_state option if bumblebeed is installed since the driver is loaded before. If you want to use load_state, blacklist the nouveau/nvidia driver.
Well, it turns out that re-doing the whole bbswitch modprobe thing did the trick. I turned the pc on twice and checked the status of the card and it was disabled on boot. The temperature is now 54º C, I just hope it doesn't heat too much. I think this has something to do with the Intel Sandybridge thing..
Hello, all!
First of all, I would like to thank everyone for the project, it is of real importance and I am really thankful for it. Keep up with the good job..
I am having some trouble with the whole disable-card and power management in Fedora 16.
My laptop is
The temperature is still high ( 65 º C with the card OFF and 78 º C and more with the card ON ) and sometimes the card is not really disabled on boot time, so I have to disable it manually. I compiled things from source following a tutorial found here http://fedoraforum.org/forum/showthread.php?t=272692
Did I miss something?
Anyway, here is some output that may be helpful..
http://pastebin.com/wVtvr8YW
http://pastebin.com/7btLE4a1
The text was updated successfully, but these errors were encountered: