Bug 583956 - High temperature using nouveau driver
Summary: High temperature using nouveau driver
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-nouveau
Version: 20
Hardware: x86_64
OS: Linux
high
urgent
Target Milestone: ---
Assignee: Ben Skeggs
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-20 11:09 UTC by Fabien Archambault
Modified: 2015-06-30 00:33 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-06-30 00:33:03 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Xorg.log (33.91 KB, text/plain)
2010-04-23 09:47 UTC, Mathieu F
no flags Details
dmesg (52.37 KB, text/plain)
2010-04-25 20:01 UTC, Fabien Archambault
no flags Details
Xorg.*.log (86.39 KB, text/plain)
2010-04-25 20:02 UTC, Fabien Archambault
no flags Details
andrei's Xorg.*.log (116.34 KB, text/plain)
2010-06-17 15:27 UTC, Andrei Nistor
no flags Details

Description Fabien Archambault 2010-04-20 11:09:57 UTC
Description of problem:
I upgraded to Fedora 13 on my laptop and as nvidia is still not "easily" available I am using nouveau but the laptop after some time is very hot and fans are not running at max speed level compared to cases when the same temperature is attained on Seven or Fedora 12 with nvidia drivers.

Version-Release number of selected component (if applicable): 0.0.16-3.20100305git6b8b157.fc13.x86_64


How reproducible: after about one hour of only internet and listen to music


Steps to Reproduce:
1. Only use a little the computer
  
Actual results:
Difficult to hold the hand where the graphic card is...


Expected results:
A cooler temperature !

Additional info:
This is the xps M1330 from Dell with the GeForce 8400M GS graphic card. Configuration of computer : http://www.smolts.org/client/show/pub_97a51b9b-9c31-4027-b192-acdfa7376036

If you need more informations... I cannot access the temperature from the probe of the graphic card: sensors-detect cannot use it... But the motherboard is at 43°C which is a bit high as in "normal" conditions I am at 31°C.
The cpu is scaled to 800MHz as usual.
There is nearly no processus in current use except gnomemusicbrowser.
I would like at least to be able to change the fan speed to 100% in order to cool things!

Comment 1 Jeff Raber 2010-04-22 21:01:20 UTC
    Thanks for the bug report. We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue. 

    Please attach your X server config file (/etc/X11/xorg.conf), X server log file (/var/log/Xorg.*.log) and the output of "dmesg" to the bug report as individual uncompressed text/plain file attachments using the bugzilla file attachment link above called "Add an attachment". 

    We will review this issue again once you've had a chance to attach this information. 

    Thank you in advance.

Comment 2 Mathieu F 2010-04-23 09:47:12 UTC
Created attachment 408558 [details]
Xorg.log

I think I have the same bug : I own a similar laptop (Dell XPS M1530) with a similar graphic card (8600M GT).

I join you the last Xorg.log I have before switching to nvidia binary blob, who doesn't have this problem. My xorg.conf was the default one (I think it's no xorg.conf by default). I can't join dmesg, since I use nvidia instead of nouveau.

I can add that F12 have *no* problem like this with *nouveau*, so it's a severe regression.

My problem seems similar. My computer's fan never calms down : I think it's the medium level of fanning, when F12 with nouveau or F13 and Win7 with nvidia use the lowest level. However my CPU is quite cool (less than 60°C). Like Fabien Archambault, the only way to know the temperature of my GPU is to install nvidia or use Windows. If I restart on Windows, the fan calms down in a minute.

Comment 3 Mathieu F 2010-04-23 12:38:23 UTC
I created my own bug report (#585203), so feel free to remove my comments and attachment of this bug (#583956).

Comment 4 Fabien Archambault 2010-04-25 20:01:31 UTC
Created attachment 409005 [details]
dmesg

dmesg of the laptop as asked in first reply.

Comment 5 Fabien Archambault 2010-04-25 20:02:34 UTC
Created attachment 409007 [details]
Xorg.*.log

cat /var/log/Xorg.*.log > Xorg.log
Files of the laptop as asked in first reply.

Comment 6 Fabien Archambault 2010-04-25 20:03:36 UTC
Hello,
I added the asked files except the /etc/X11/xorg.conf which is the default one as I do not have the file (except old backup from F12 and nvidia driver).

Comment 7 Jeff Raber 2010-04-26 02:52:26 UTC
This bug has been triaged.

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 8 Fabien Archambault 2010-05-19 15:28:35 UTC
I am not sure this is solved by the latest update. But since about a week the temperature of my laptop is becoming reasonable (when touching it) after a long time of use (more than 5 hours).
The update of today : xorg-x11-drv-nouveau-0.0.16-6.20100423git13c1043.fc13.x86_64
Seems to have even cooldown better the laptop.

Comment 9 Andrei Nistor 2010-06-17 15:26:37 UTC
I have an 8600GT card with passive cooling. The card is very hot with nouveau. With the binary blob the card was still a little hot, but I could hold my hand on it, with nouveau it burns.

I'm also using 
xorg-x11-drv-nouveau-0.0.16-6.20100423git13c1043.fc13.x86_64

I'm quite worried with the high temperature...

Comment 10 Andrei Nistor 2010-06-17 15:27:59 UTC
Created attachment 424858 [details]
andrei's Xorg.*.log

I'm not using an xorg.conf

Comment 11 Fabien Archambault 2010-11-05 09:58:32 UTC
Still present with this version:
xorg-x11-drv-nouveau.x86_64         1:0.0.16-8.20100423git13c1043.fc13

I was using the nvidia driver for some times then I tried again the nouveau driver and the difference in temperature is very important. Where I put my left hand it is very warm in comparison with the time when using the nvidia driver.

I am not sure if it was really solved by the time I said it seemed...

Comment 12 Fabien Archambault 2010-11-05 09:58:55 UTC
I forgot the dmesg:
$ dmesg | grep nouveau
nouveau 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
nouveau 0000:01:00.0: setting latency timer to 64
[drm] nouveau 0000:01:00.0: Detected an NV50 generation card (0x086700a2)
[drm] nouveau 0000:01:00.0: Attempting to load BIOS image from PRAMIN
[drm] nouveau 0000:01:00.0: ... appears to be valid
[drm] nouveau 0000:01:00.0: BIT BIOS found
[drm] nouveau 0000:01:00.0: Bios version 60.86.45.00
[drm] nouveau 0000:01:00.0: TMDS table revision 2.0 not currently supported
[drm] nouveau 0000:01:00.0: BIT table 'd' not found
[drm] nouveau 0000:01:00.0: Found Display Configuration Block version 4.0
[drm] nouveau 0000:01:00.0: Raw DCB entry 0: 01000323 00010034
[drm] nouveau 0000:01:00.0: Raw DCB entry 1: 02011300 00000028
[drm] nouveau 0000:01:00.0: Raw DCB entry 2: 02022312 00020010
[drm] nouveau 0000:01:00.0: Raw DCB entry 3: 0000000e 00000000
[drm] nouveau 0000:01:00.0: DCB connector table: VHER 0x40 5 14 2
[drm] nouveau 0000:01:00.0:   0: 0x00000041: type 0x41 idx 0 tag 0xff
[drm] nouveau 0000:01:00.0: unknown type, using 0x40
[drm] nouveau 0000:01:00.0:   1: 0x00000100: type 0x00 idx 1 tag 0xff
[drm] nouveau 0000:01:00.0:   2: 0x00002261: type 0x61 idx 2 tag 0x08
[drm] nouveau 0000:01:00.0:   3: 0x00000310: type 0x10 idx 3 tag 0xff
[drm] nouveau 0000:01:00.0:   4: 0x00000311: type 0x11 idx 4 tag 0xff
[drm] nouveau 0000:01:00.0:   5: 0x00000313: type 0x13 idx 5 tag 0xff
[drm] nouveau 0000:01:00.0: Parsing VBIOS init table 0 at offset 0xC42B
[drm] nouveau 0000:01:00.0: Parsing VBIOS init table 1 at offset 0xC76B
[drm] nouveau 0000:01:00.0: Parsing VBIOS init table 2 at offset 0xD1C0
[drm] nouveau 0000:01:00.0: Parsing VBIOS init table 3 at offset 0xD2B2
[drm] nouveau 0000:01:00.0: Parsing VBIOS init table 4 at offset 0xD4AC
[drm] nouveau 0000:01:00.0: Parsing VBIOS init table at offset 0xD511
[drm] nouveau 0000:01:00.0: 0xD511: Condition still not met after 20ms, skipping following opcodes
[drm] nouveau 0000:01:00.0: 0xB534: parsing output script 0
[drm] nouveau 0000:01:00.0: 0xB6AA: parsing output script 0
[drm] nouveau 0000:01:00.0: Detected 128MiB VRAM
[drm] nouveau 0000:01:00.0: 512 MiB GART (aperture)
[drm] nouveau 0000:01:00.0: gpio tag 0xff not found
[drm] nouveau 0000:01:00.0: gpio tag 0xff not found
[drm] nouveau 0000:01:00.0: Allocating FIFO number 1
[drm] nouveau 0000:01:00.0: nouveau_channel_alloc: initialised FIFO 1
[drm] nouveau 0000:01:00.0: allocated 1280x800 fb: 0x40230000, bo ffff880116d8b400
fbcon: nouveaufb (fb0) is primary device
[drm] nouveau 0000:01:00.0: 0xB399: parsing clock script 0
fb0: nouveaufb frame buffer device
[drm] Initialized nouveau 0.0.16 20090420 for 0000:01:00.0 on minor 0
[drm] nouveau 0000:01:00.0: 0xB4F7: parsing clock script 1
[drm] nouveau 0000:01:00.0: Allocating FIFO number 2
[drm] nouveau 0000:01:00.0: nouveau_channel_alloc: initialised FIFO 2
[drm] nouveau 0000:01:00.0: Allocating FIFO number 3
[drm] nouveau 0000:01:00.0: nouveau_channel_alloc: initialised FIFO 3
[drm] nouveau 0000:01:00.0: Allocating FIFO number 4
[drm] nouveau 0000:01:00.0: nouveau_channel_alloc: initialised FIFO 4
[drm] nouveau 0000:01:00.0: nouveau_channel_free: freeing fifo 4

Comment 13 Fabien Archambault 2011-02-18 10:02:56 UTC
Hi,

after a long period being with nvidia I have come back to nouveau and I still have the same issue about temperature...
I have only Firefox started and my CPUs (the only thing I can monitor with nouveau) are at 61°C whereas with nvidia drivers I was at 45-50°C for the same activity!

Here is the $ dmesg | grep nouveau
[   11.190988] nouveau 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[   11.190997] nouveau 0000:01:00.0: setting latency timer to 64
[   11.195023] [drm] nouveau 0000:01:00.0: Detected an NV50 generation card (0x086700a2)
[   11.199488] [drm] nouveau 0000:01:00.0: Attempting to load BIOS image from PRAMIN
[   11.288381] [drm] nouveau 0000:01:00.0: ... appears to be valid
[   11.288387] [drm] nouveau 0000:01:00.0: BIT BIOS found
[   11.288390] [drm] nouveau 0000:01:00.0: Bios version 60.86.45.00
[   11.288393] [drm] nouveau 0000:01:00.0: TMDS table version 2.0
[   11.288396] [drm] nouveau 0000:01:00.0: BIT table 'd' not found
[   11.288399] [drm] nouveau 0000:01:00.0: Found Display Configuration Block version 4.0
[   11.288402] [drm] nouveau 0000:01:00.0: Raw DCB entry 0: 01000323 00010034
[   11.288405] [drm] nouveau 0000:01:00.0: Raw DCB entry 1: 02011300 00000028
[   11.288407] [drm] nouveau 0000:01:00.0: Raw DCB entry 2: 02022312 00020010
[   11.288410] [drm] nouveau 0000:01:00.0: Raw DCB entry 3: 0000000e 00000000
[   11.288413] [drm] nouveau 0000:01:00.0: DCB connector table: VHER 0x40 5 14 2
[   11.288417] [drm] nouveau 0000:01:00.0:   0: 0x00000041: type 0x41 idx 0 tag 0xff
[   11.288419] [drm] nouveau 0000:01:00.0: unknown type, using 0x40
[   11.288422] [drm] nouveau 0000:01:00.0:   1: 0x00000100: type 0x00 idx 1 tag 0xff
[   11.288425] [drm] nouveau 0000:01:00.0:   2: 0x00002261: type 0x61 idx 2 tag 0x08
[   11.288428] [drm] nouveau 0000:01:00.0:   3: 0x00000310: type 0x10 idx 3 tag 0xff
[   11.288431] [drm] nouveau 0000:01:00.0:   4: 0x00000311: type 0x11 idx 4 tag 0xff
[   11.288434] [drm] nouveau 0000:01:00.0:   5: 0x00000313: type 0x13 idx 5 tag 0xff
[   11.288439] [drm] nouveau 0000:01:00.0: Parsing VBIOS init table 0 at offset 0xC42B
[   11.314202] [drm] nouveau 0000:01:00.0: Parsing VBIOS init table 1 at offset 0xC76B
[   11.333042] [drm] nouveau 0000:01:00.0: Parsing VBIOS init table 2 at offset 0xD1C0
[   11.333058] [drm] nouveau 0000:01:00.0: Parsing VBIOS init table 3 at offset 0xD2B2
[   11.335147] [drm] nouveau 0000:01:00.0: Parsing VBIOS init table 4 at offset 0xD4AC
[   11.335155] [drm] nouveau 0000:01:00.0: Parsing VBIOS init table at offset 0xD511
[   11.356055] [drm] nouveau 0000:01:00.0: 0xD511: Condition still not met after 20ms, skipping following opcodes
[   11.356085] [drm] nouveau 0000:01:00.0: Detected 128MiB VRAM
[   11.395426] [drm] nouveau 0000:01:00.0: 512 MiB GART (aperture)
[   12.398287] [drm] nouveau 0000:01:00.0: Allocating FIFO number 1
[   12.405676] [drm] nouveau 0000:01:00.0: nouveau_channel_alloc: initialised FIFO 1
[   12.565853] [drm] nouveau 0000:01:00.0: allocated 1280x800 fb: 0x40260000, bo ffff88011735c400
[   12.565918] fbcon: nouveaufb (fb0) is primary device
[   12.577145] fb0: nouveaufb frame buffer device
[   12.577211] [drm] Initialized nouveau 0.0.16 20090420 for 0000:01:00.0 on minor 0
[   45.373732] [drm] nouveau 0000:01:00.0: Allocating FIFO number 2
[   45.381825] [drm] nouveau 0000:01:00.0: nouveau_channel_alloc: initialised FIFO 2
[   45.623323] [drm] nouveau 0000:01:00.0: Allocating FIFO number 3
[   45.630788] [drm] nouveau 0000:01:00.0: nouveau_channel_alloc: initialised FIFO 3
[ 1072.160397] [drm] nouveau 0000:01:00.0: Allocating FIFO number 4
[ 1072.173988] [drm] nouveau 0000:01:00.0: nouveau_channel_alloc: initialised FIFO 4
[ 1121.147705] [drm] nouveau 0000:01:00.0: Allocating FIFO number 5
[ 1121.155625] [drm] nouveau 0000:01:00.0: nouveau_channel_alloc: initialised FIFO 5
[ 1121.160350] [drm] nouveau 0000:01:00.0: nouveau_channel_free: freeing fifo 4
[ 1121.201328] [drm] nouveau 0000:01:00.0: nouveau_channel_free: freeing fifo 5

I have no xorg.conf file.
Here is the rpm -qa | grep nouveau
xorg-x11-drv-nouveau-0.0.16-11.20100826git065576d.fc14.x86_64
xorg-x11-drv-nouveau-debuginfo-0.0.16-11.20100826git065576d.fc14.x86_64

I am going back to nvidia after this but if you have anything to change please ask I will do it.

Comment 14 Fabien Archambault 2011-03-11 08:58:21 UTC
I am using F15 alpha and for the moment it seems that the temperature is also very high.
I cannot compare with nvidia yet and also it is an alpha version...

Comment 15 Fabien Archambault 2011-05-13 21:07:22 UTC
I am still using nouveau in F15 and after 30 minutes being on the internet on Firefox 4 the fans are running and the computer is very warm!
In comparison I have done the same one hour ago with F14 and the nvidia drivers the computer was not that warm!

rpm -q xorg-x11-drv-nouveau 
xorg-x11-drv-nouveau-0.0.16-24.20110324git8378443.fc15.x86_64

Comment 16 Fabien Archambault 2011-05-13 21:08:04 UTC
I forgot:
$ dmesg | grep nouveau
[    1.276503] nouveau 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[    1.276512] nouveau 0000:01:00.0: setting latency timer to 64
[    1.280694] [drm] nouveau 0000:01:00.0: Detected an NV50 generation card (0x086700a2)
[    1.285415] [drm] nouveau 0000:01:00.0: Attempting to load BIOS image from PRAMIN
[    1.377768] [drm] nouveau 0000:01:00.0: ... appears to be valid
[    1.377773] [drm] nouveau 0000:01:00.0: BIT BIOS found
[    1.377776] [drm] nouveau 0000:01:00.0: Bios version 60.86.45.00
[    1.377780] [drm] nouveau 0000:01:00.0: TMDS table version 2.0
[    1.377782] [drm] nouveau 0000:01:00.0: BIT table 'd' not found
[    1.377785] [drm] nouveau 0000:01:00.0: Found Display Configuration Block version 4.0
[    1.377788] [drm] nouveau 0000:01:00.0: Raw DCB entry 0: 01000323 00010034
[    1.377791] [drm] nouveau 0000:01:00.0: Raw DCB entry 1: 02011300 00000028
[    1.377794] [drm] nouveau 0000:01:00.0: Raw DCB entry 2: 02022312 00020010
[    1.377796] [drm] nouveau 0000:01:00.0: Raw DCB entry 3: 0000000e 00000000
[    1.377800] [drm] nouveau 0000:01:00.0: DCB connector table: VHER 0x40 5 14 2
[    1.377803] [drm] nouveau 0000:01:00.0:   0: 0x00000041: type 0x41 idx 0 tag 0xff
[    1.377805] [drm] nouveau 0000:01:00.0: unknown type, using 0x40
[    1.377808] [drm] nouveau 0000:01:00.0:   1: 0x00000100: type 0x00 idx 1 tag 0xff
[    1.377811] [drm] nouveau 0000:01:00.0:   2: 0x00002261: type 0x61 idx 2 tag 0x08
[    1.377814] [drm] nouveau 0000:01:00.0:   3: 0x00000310: type 0x10 idx 3 tag 0xff
[    1.377817] [drm] nouveau 0000:01:00.0:   4: 0x00000311: type 0x11 idx 4 tag 0xff
[    1.377819] [drm] nouveau 0000:01:00.0:   5: 0x00000313: type 0x13 idx 5 tag 0xff
[    1.377824] [drm] nouveau 0000:01:00.0: Parsing VBIOS init table 0 at offset 0xC42B
[    1.401123] [drm] nouveau 0000:01:00.0: Parsing VBIOS init table 1 at offset 0xC76B
[    1.417983] [drm] nouveau 0000:01:00.0: Parsing VBIOS init table 2 at offset 0xD1C0
[    1.417994] [drm] nouveau 0000:01:00.0: Parsing VBIOS init table 3 at offset 0xD2B2
[    1.419094] [drm] nouveau 0000:01:00.0: Parsing VBIOS init table 4 at offset 0xD4AC
[    1.419103] [drm] nouveau 0000:01:00.0: Parsing VBIOS init table at offset 0xD511
[    1.439110] [drm] nouveau 0000:01:00.0: 0xD511: Condition still not met after 20ms, skipping following opcodes
[    1.458372] [drm] nouveau 0000:01:00.0: 3 available performance level(s)
[    1.458377] [drm] nouveau 0000:01:00.0: 0: memory 100MHz core 169MHz shader 338MHz voltage 1150mV fanspeed 100%
[    1.458382] [drm] nouveau 0000:01:00.0: 1: memory 301MHz core 275MHz shader 550MHz voltage 1150mV fanspeed 100%
[    1.458386] [drm] nouveau 0000:01:00.0: 2: memory 600MHz core 400MHz shader 800MHz voltage 1150mV fanspeed 100%
[    1.458412] [drm] nouveau 0000:01:00.0: c: memory 351MHz core 200MHz shader 400MHz voltage 1150mV
[    1.458525] [drm] nouveau 0000:01:00.0: Detected 128MiB VRAM
[    1.461325] [drm] nouveau 0000:01:00.0: 512 MiB GART (aperture)
[    1.505620] [drm] nouveau 0000:01:00.0: ACPI backlight interface available, not registering our own
[    1.666690] [drm] nouveau 0000:01:00.0: allocated 1280x800 fb: 0x40000000, bo ffff880112f39000
[    1.666749] fbcon: nouveaufb (fb0) is primary device
[    2.709227] fb0: nouveaufb frame buffer device
[    2.709242] [drm] Initialized nouveau 0.0.16 20090420 for 0000:01:00.0 on minor 0

Comment 17 Rudd-O DragonFear 2012-07-06 16:07:49 UTC
I have the same problem.


01:00.0 VGA compatible controller: nVidia Corporation GF106 [GeForce GTX 460M] (rev a1)


Fedora 17

Just uninstalled kmod-nvidia in favor of nouveau (ironically I did that because I needed to develop clutter apps and those don't work in fedora with the nvidia driver).

And the laptop is going noisy with the fan, and can barely be touched.  That's how hot it is.

Comment 18 Rudd-O DragonFear 2012-07-06 16:11:03 UTC
Seriously:


ouveau-pci-0100
Adapter: PCI adapter
temp1:        +83.0°C  (high = +100.0°C, crit = +110.0°C)


WTH.

Comment 19 Fedora End Of Life 2012-08-16 21:37:10 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 20 Fabien Archambault 2012-08-17 06:58:24 UTC
I reopen it as it is still available for F17 and I am not alone...

PS: I hope the status assigned is fine.

Comment 21 Fedora End Of Life 2013-07-04 06:38:24 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is end of life. If you 
would still like  to see this bug fixed and are able to reproduce it 
against a later version  of Fedora, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 22 Fabien Archambault 2013-07-19 08:48:22 UTC
I have updated to F19 and I still have the fans being at 100% after a short time and an increasing temperature which is difficult to support.

Comment 23 Fedora End Of Life 2015-01-09 21:43:20 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 24 Fabien Archambault 2015-01-29 17:12:12 UTC
Bumped to F20!
I was using nvidia in Fedora 20 and I tried once again nouveau and after a few minutes the laptop is too warm!
$ uname -r
3.17.8-200.fc20.i686+PAE
$ rpm -qa | grep nouveau
xorg-x11-drv-nouveau-1.0.9-2.fc20.i686


This is not the case woth nvidia.

Comment 25 Fedora End Of Life 2015-05-29 08:37:01 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 26 Fedora End Of Life 2015-06-30 00:33:03 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.