Description of problem:
I have recently installed fedora core 4 on an old toshiba laptop, i was using a
live boot disk instead of fedora. I needed something more stable and wanted my
cd drive back, so i downloaded andinstalled fedora. In the first day i was very
happy with the product, until i felt the bottom of the laptop. It is very hot.So
i waited a while and monitored the fan it never came back on. I was using a slax
live cd and the fan was working fine.I honestly have no idea what to categorize
this problem under so i made an educated guess.
Version-Release number of selected component (if applicable):
Fedora Core 4
Steps to Reproduce:
*** Bug 176693 has been marked as a duplicate of this bug. ***
Hmm, probably a kernel problem? I've removed the bug alias -- you can easily get
back to this bug via "My Front Page".
To debug this problem, there is a lot of information missing:
- What exact laptop model do you have?
- Output of "lspci" and "lspci -v" (as root)
- What exact live CD distro and version did you use before?
- What kernel version do you run now that exhibits the problem?
the lap top model is an old toshiba sattelite 4300 series
the live cd is th new slax
2.6.11-1.1369_FC4 is what grub tells me
im not sure what you mean when you ask Output of "lspci" and "lspci -v" (as root)
I mean: Run (as user "root") the commands "lspci" and "lspci -v", attach the
output of both commands to this bugzilla ticket.
The kernel you run is awfully old. PLease try to reproduce the problem with the
an up to date system (this would e.g. have kernel-2.6.14-1.1653_FC4), don't
update only the kernel, but the rest as well. What kernel version does "the new
This is a mass-update to all currently open kernel bugs.
A new kernel update has been released (Version: 2.6.15-1.1830_FC4)
based upon a new upstream kernel release.
Please retest against this new kernel, as a large number of patches
go into each upstream release, possibly including changes that
may address this problem.
This bug has been placed in NEEDINFO_REPORTER state.
Due to the large volume of inactive bugs in bugzilla, if this bug is
still in this state in two weeks time, it will be closed.
Should this bug still be relevant after this period, the reporter
can reopen the bug at any time. Any other users on the Cc: list
of this bug can request that the bug be reopened by adding a
comment to the bug.
If this bug is a problem preventing you from installing the
release this version is filed against, please see bug 169613.
Closing per previous comment.