| 2008-01-19 16:48:46 |
sammydlm |
bug |
|
|
added bug |
| 2008-08-02 21:06:09 |
Jean-Baptiste Lallement |
None: bugtargetdisplayname |
Ubuntu |
linux (Ubuntu) |
|
| 2008-08-02 21:06:09 |
Jean-Baptiste Lallement |
None: bugtargetname |
ubuntu |
linux (Ubuntu) |
|
| 2008-08-02 21:06:09 |
Jean-Baptiste Lallement |
None: statusexplanation |
|
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description does not yet have enough information.
Please include the following additional information, if you have not already done so (pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" after a fresh boot and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.
For your reference, the full description of procedures for kernel-related bug reports is available at [WWW] https://wiki.ubuntu.com/KernelTeamBugPolicies Thanks in advance! |
|
| 2008-08-02 21:06:09 |
Jean-Baptiste Lallement |
None: title |
Bug #184367 in Ubuntu: "Fan runs constantly on Everex NC1502" |
Bug #184367 in linux (Ubuntu): "Fan runs constantly on Everex NC1502" |
|
| 2008-08-02 21:09:23 |
Jean-Baptiste Lallement |
linux: status |
New |
Incomplete |
|
| 2008-08-02 21:09:23 |
Jean-Baptiste Lallement |
linux: statusexplanation |
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description does not yet have enough information.
Please include the following additional information, if you have not already done so (pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" after a fresh boot and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.
For your reference, the full description of procedures for kernel-related bug reports is available at [WWW] https://wiki.ubuntu.com/KernelTeamBugPolicies Thanks in advance! |
|
|
| 2008-08-17 10:47:02 |
Jean-Baptiste Lallement |
linux: status |
Incomplete |
Invalid |
|
| 2008-08-17 10:47:02 |
Jean-Baptiste Lallement |
linux: statusexplanation |
|
We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again! |
|
| 2011-05-13 02:08:54 |
Grant Schumacher |
bug |
|
|
added subscriber Grant Schumacher |
