I had Fedora 15 installed on my laptop and I have a problem which had bothered me for a long time. Every time I turn on my laptop, I would get a messages which says "Thermal Shutdown Occurred". I tried other Linux distributions but the same problem. It operates normally with Windows 7.
View 7 RepliesWhen I shut down fedora 14, no messages are displayed. I commented out "rhgb quiet" to display the startup messages. How do I configure Fedora 14 to display the shutdown messages when shutting down?
View 4 Replies View RelatedDuring boot-up and shutdown of Fedora-14-x86_64-Live-Desktop.iso live USB, I just see some graphical stuff. What needs to be done so that the screen shows text messages about what's happening during boot-up and shutdown?
View 2 Replies View RelatedMy problem is as follows:Hp Envy 17 3D (2nd gen i7/6gig ram/720hdd/ Win 7 Home Prem 64bit) when attemting to install Ubuntu 11.04 I get a "thermal shutdown" error message. this error has been duplicated two times while attempting to install via Wubi
View 2 Replies View RelatedWhen my computer shuts down, I always get a long error message from the kernel. It's the very last thing the computer does and I can't even use the keyboard, since the system is halted. I wanted to read it more carefully (it's very long and doesn't fit the screen) and file a bug report against the kernel with it. But for that, I needed to save all that text in a file.
View 1 Replies View RelatedI just installed Debian testing on my new ThinkPad T400s. Everything went like a charm, but, I have three questions to fix some minors: (A) When I reboot or shutdown, just before everything turns off message appear:
[37.439999] thinkpad_acpi: THERMAL ALLERT: unknown thermal allert received
During the boot-sequence of jessie there is more text flying by on the screen (including some errors or warnings) than I can read thorugh fast enough. I don't think this is very serious stuff, and if it were I could always look at dmesg and or syslog i /var/log but I would find it really convenient to log these messages in a file instead of sifting through or grep-ing dmesg.
When duckduckgoing this matter I found [URL] ....
I installed tried bootlogd but when configuring it to "yes" and rebooting nothing comes up in /var/log/boot.
Then I saw this line in above link
If you use systemd as your init system, you may need to use systemctl to debug boot problems.
I have Lucid installed on two PCs. The PCs are identical except one uses the on-board Intel G33 video controller while the other has an nvidia 210 video card attached. The nvidia PC restarts/shuts down without showing any console text messages, however the Intel based PC has the following problem. The software on both machines is identical (except for the nvidia packages).
On restart or shutdown on the intel based PC plymouth gives way to a console for 2 or 3 seconds showing the following (none of which are errors as far as i know)...
Code:
Broadcast Message from root@xyz-desktop
(unknown) at 11:44 ...
The System is going down for restart NOW!
* Deactivating Swap ...
* Unmounting weak filesystems ...
[Code]....
how to record/save logout/shutdown messages for OpenSuse 11.2.
View 9 Replies View Relatedeverytime I try to shutdown/reboot, it gets to the screen where it has the green/bold status messages on the side, but then it simply stops. The cursor doesn't blink, nothing happens...you could wait 10 minutes, and it would still be at that same screen. I don't know if I've described this well enough for anyone to understand, but I hope so! I don't have a camera, but if I did...I'd post a picture of where I mean...
But like I said, after getting to a certain, without actually shutting down, it simply stops and does absolutely nothing. This is rather inconvenient, and I'd like to find a solution to this if possible. EDIT: I'm sorry I didn't provide any hardware info, but I'm using Gnome...This didn't happen 100% of the time KDE like it does now though. (But it DID happen in KDE as well) I'm using OpenSUSE 11.2... I'll be back in a moment with hardware info, assuming it may aid in a solution.
[Code]...
I am looking for the best place to report this issue. FC14 appears to falsely detect some hardware as a Thermal diode and causes random shut down due to thermal over temperature condition. I am in the process of building a new MythTV back end and choose the EliteGroup motherboard A790GXM-AD3. I did a fresh FC14 install usewd the update depositary during the install. On the first boot the system shut down before I could get the password entered. Eventually I noticed the following in the /var/log/dmesg file. May 6 09:20:52 pvr1 kernel: [ 71.081080] Critical temperature reached (127 C), shutting down. I installed the lm_sensors RPM and I see the following:
[root@pvr1 ~]# uptime
08:29:07 up 0 min, 1 user, load average: 1.45, 0.45, 0.16
[root@pvr1 ~]# service lm_sensors status
acpitz-virtual-0
Adapter: Virtual device
temp1: +30.0�C (crit = +110.0�C)
k10temp-pci-00c3
[Code]........
I did log a call with the ECS mother board support to get their view on this issue. But based on the BIOS PC Health display temp3 should not exist. So perhaps the kernel is detecting some other hardware as a thermal diode? Random shut downs due to ghost hardware is not good. The kernel version is 2.6.35.12-90.fc14.x86_64
I tried to boot a FC15 beta live CD but it shut down due to the over temp condition before it completed booting. A google search of the error message got two hits one in FC12 and the other in Ubunuto linux both with ECS motherboards.
My F-14 x64 bootup stalls with this message: "K10 temp ... unreliable CPU thermal sensor: monitoring disabled". I'm unable to find an explanation/basis for this message. I can boot from CD#1 and chroot onto the disk - near as I can tell, all the data is there. Might this be the result of a corrupt boot up sequence file and, if so, which one(s)?
View 3 Replies View RelatedThis link, acpi: thermal/sysfs-api, explains how the new thermal management sysfs class is built, but doesn't give much information about using it. Using watch, I can see that the cur_state of cooling_device2 changes from 0 to 5 when I check "Dim display when idle" in Power Management Preferences. But I haven't found an applet that changes cooling_device0 or cooling_device1.
Echoing different integers to the cur_state files limits the maximum cpu frequency for cpu0 and cpu1, respectively. This behaviour is expected from what I've read, and mimics the options in Windows power manager for extending battery life by throttling the CPUs. I've had no luck with google and local man pages, so has anybody has seen an applet for controlling /sys/class/thermal/cooling_device[0|1]/cur_state?
On a side note, a value of 1 does slow the CPU down, but it will still hit 100C (normal for an Intel mobile duo core). However, values of 2 and larger throttle enough to lower the maximum CPU temp. Since the CPU temp is a good indicator of power consumption, it's pretty obvious that these two cur_state files are intended to extend battery life. dd_wizard
Recently I installed vncserver (tigervnc) on my desktop. Ever since my computer refuses to shutdown normally. At shutdown the following message pops up: Quote: System policy prevents stopping the system when other users are logged in Then I have to enter the root password to shutdown. If I stop vncserver before, the computer shuts down normally.
[Code]....
My fedora12 send me this error message:
Code:
An internal system error has occurred ..... Please use your distribution bugtracker to report this error ... What is the bugtracker? How i can use it?
Errors occurred when booting F12 on my laptop.
Code:
Mounting local filesystems: WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/.
...
Starting system message bus: [FAILED]
[Code].....
You have to define PLUGINS in /etc/sysconfig/sipwitch before running sipwitch
Then the system froze there. Press Ctrl+Alt+F2 can enter command line mode.
I have two graphic cards on my laptop, one is Intel and the other is Nvidia. There seems to be something wrong with the Intel card and I changed into the Nvidia card to boot. Then the errors occurred. The driver of the Nvidia card has not been installed. How can I start my network in command line mode? I cannot enter graphic mode now.
Code:
Error Type: <class 'yum.Errors.RepoError'>
Error Value: Error getting repository data for installed, repository not found
File : /usr/share/PackageKit/helpers/yum/yumBackend.py, line 3125, in <module> main()
File : /usr/share/PackageKit/helpers/yum/yumBackend.py, line 3122, in main
backend.dispatcher(sys.argv[1:])
File : /usr/lib/python2.6/site-packages/packagekit/backend.py, line 710, in dispatcher
self.dispatch_command(args[0], args[1:])
File : /usr/lib/python2.6/site-packages/packagekit/backend.py, line 657, in dispatch_command
self.update_packages(only_trusted, package_ids)
File : /usr/share/PackageKit/helpers/yum/yumBackend.py, line 1948, in update_packages
signed = self._is_package_repo_signed(pkg)
File : /usr/share/PackageKit/helpers/yum/yumBackend.py, line 1437, in _is_package_repo_signed
repo = self.yumbase.repos.getRepo(pkg.repoid)
File : /usr/lib/python2.6/site-packages/yum/repos.py, line 121, in getRepo
'Error getting repository data for $s, repository not found' $ (repoid)
I cant update my system what can I do?
While booting my fedora15, it gets stuck for about 5-6 minutes. Previously there was no problem. I don't know what made this problem. After going through the boot process, error occurred during network process. Using following command I got the result.
Code: # systemctl status network.service
network.service - LSB: Bring up/down networking
Loaded: loaded (/etc/rc.d/init.d/network)
Active: failed since Sun, 05 Jun 2011 21:13:55 +0545; 11h ago
Process: 845 ExecStart=/etc/rc.d/init.d/network start (code=exited, status=1/FAILURE)
CGroup: name=systemd:/system/network.service
Also right after the long pause following messages are printed
Code: 261.742053 usb4-1: device not accepting address 4 error -7
261.794087 hub4-0.1.0: unable to enumerate usb device on ports
I noted it down as soon as I saw the message after that long pause.
I am trying to set my root password for my mysql database. After I enter /etc/init.d/mysqld start
[code]...
Timeout error occurred trying to start MySQL Daemon. Then when I try to set the password for my root account I get
[code]...
I want to dual boot Fedora 11 with Ubuntu 9.04 Jaunty Jackalope.
I already have Ubuntu installed, but when I try to install Fedora 11 from Live CD, it comes up with this error:
An unhandled exception has occurred. This is most likely a bug... blah blah etc. Bug report is attached.
I would really appreciate it if anyone helps me!
I have had Ubuntu for about a month now (Windows blue screen), I want to use Fedora for a new experience and to do certain things I can't do with Ubuntu
I am booting from a USB stick.
I just installed Fedora 12 and while I was trying to install Skype, there was a system crash and since then I cannot install any other software or cannot even access 'add/remove software'. Whenever I try to install a software or try to open the 'add/remove software' or, 'Software Updates' I get the message
'An internal system error has occured'.
and inside it contains this-
Code:
Traceback (most recent call last):
File "/usr/share/PackageKit/helpers/yum/yumBackend.py", line 2956, in __init__
self.repos.confirm_func = self._repo_gpg_confirm
File "/usr/lib/python2.6/site-packages/yum/__init__.py", line 717, in <lambda>
repos = property(fget=lambda self: self._getRepos(),
File "/usr/lib/python2.6/site-packages/yum/__init__.py", line 496, in _getRepos
self.conf # touch the config class first .....
I tried these using the terminal-
yum clean all
yum metadata
sudo yum clean all
yum clean metadata
and all of these gave me the same result-
Code:
Loaded plugins: presto, refresh-packagekit
Config Error: File contains no section headers.
file: file://///etc/yum.repos.d/skype.repo, line: 1
"su -c 'yum -y install skype' "
Everything else is working fine, but I just can not install or update any more software.
when I open synaptics I get this message:
E: Error occured while processing abrt (CollectFileProvides)
E: Problem with MergeFileProvides /var/lib/apt/lists/download.fedoraproject.org_pub_fedora_linux_update s_12_x86%5f64_repodata_repomd.xml
E: The package lists or status file could not be parsed or opened.
I have a syslog-ng running and kernel build of 2.6.34.8 I use a syslog API in my program with facility LOG_LOCAL5 and and levels debug err and crit and info. when I ran on the older syslog facility I had everything logged fine as I intended. now I have written these rules into the syslog-ng.conf:
options {
flush_lines (0);
time_reopen (10);
log_fifo_size (1000);
[code]....
the last two rules show my program gnssapp. the result is all debug levels or crit or err levels I don't see any of them !
I just upgraded to maverick meerkat two days ago and each time I boot I get a problem about the thermal sensor on my cpu. Apparently from this link below it has happened to others and supposedly a bug fix was going to be released, but I haven't seen one. Is there anything I can do about this? I have a amd phenom x4. [URL]
View 1 Replies View RelatedI need to install a bematech MP-4000 TH USB thermal printer, but the system does not recogize the printer.
I tried to install various cups versions and other related packages; without results....
Am am trying to install on my mini pc (operating on Debian ) a thermal printer. As I read on the internet you must first instal cups, but unfortunately I am unable to accomplish this. The error that I get is this:
apt-get install cups
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed.
[Code] ...
I originally installed Kubuntu 7.10 on an ACER laptop (exact model escapes me at the moment) and subsequently upgraded to 9.10 and then to 10.04. Starting with 9.10, I had problems with the computer suddenly turning off in the middle of doing work. Eventually, I figured out that when this happened, the bottom panel had gotten quite warm so it probably a thermal control measure. Further, I discovered that I could prevent this by setting the power regulator to powersave, which effectively kept frequency scaling at 50% and under which I never had the computer suddenly turn, the only exceptions being when unplugged the computer and replugged it in and it would switch to dynamic power policy thus running at full power.
However, after "upgrading" to 10.04, I can't do anything to restrict frequency scaling. Whether I set the regulator to powersave, ondemand or anything, CPU frequency can go to full capacity until it heats the CPU to the critical trip point, invoking poweroff. Sometimes, this would happen just a few minutes after "acpi -t" reported 40C (is there some way to test the output from acpi, I've seen it report obviously wrong figures such as 0C when the room was considerably above freezing?). While trying to figure out what to do, I discovered the /proc/acpi/thermal directory and subsequently the /sys/dev/... directory.
I would like to know which directory I should focus on and what files in order to establish trip points and direct actions that will force the system to reduce heating so it won't reach critical. It's not like it's particularly compute intensive tasks triggering this. I have had it happen while running nothing more than the windowing system, system monitor, terminal and paging through a file with less. I have looked for documentation online but have not found anything that clearly explains what I need to do. The only parts I understand from what I've found are "[critical]: S5", "[active]", and "[passive]". The "[passive]" line included items like "tc=..." and "device=0x...", but I have no idea whatsoever what any of those settings do and the documents do absolutely nothing to explain them.
1) what file I need to edit, 2) what options I can set in the file, 3) what values those options can take and 4) what effects those values have on ACPI's behavior. Lastly, the default setting HAVE GOT TO BE CHANGED. Having poweroff as the first line of defense against overheating is simply UNACCEPTABLE. What would happen if this occurs during the middle of a system upgrade? I know at least enough to figure what needs to be done, even if I can't figure out how to do it. Many users can't even do that and I don't think they should have to. The installation process should automatically detect what methods of reducing thermal output available (reducing frequency scaling, throttling, fans) and set trip points that invoke them before reaching critical.
I have installed a cluster computer with 10 nodes . The manufacturer is HP . All nodes and the master node have redhat enterprise linux installed in them . When I shutdown the nodes from the master terminal using "shutdown -h now" they get shutdown . But they dont get completely turned off . This issue bothers me when the power supply is given , all nodes boot up simultaneously generating a huge heat .
Thing to note : When we shutdown our PC they get completely turned off . When the power supply is given , a press on the Power On button is required to boot the system. But , why does it not happpen in the case of cluster? Is there any other way of completely turning off the nodes from the master terminal ?
i was in Staples and saw this stuff for the first time. i have a 4 year old laptop and especially when i run Ubuntu, the fan runs almost nonstop. i've looked at the fan, it's pretty clean, but it still runs a lot. the exhaust right now is pretty hot.
is this something worth buying? if i do buy it, where do i apply it? to the fan somewhere? i've already taken this thing apart a couple of times, i don't mind doing it again, but i'd like to have an idea of what exactly i need to aim for.
As the subject state, I am running linux on a Sun Fire X4100 M2 BladeServer. The distro is ubuntu 8.10, kernel version 2.6.24 patchlevel 24. I need to monitor the thermal and fan statistics on this server, but there are no stat files in /proc/acpi/thermal_zone or /proc/acpi/fan. I have tried loading all of the lm modules (and all other available ones in the drivers/hwmon section of the kernel modules) provided with no avail.
View 1 Replies View Related