You are not logged in.
Hey everyone
First time user of Arch here, and I really love it.
However, I got a weird issue. Every once in a while my desktop pc just shuts down without notification. Like a power out. First i thought it was only when i played videofiles, but now it happens randomly when a browser is open. Doesnt matter if it is Chromium or Firefox. My previous install on this pc was Fedora, and I had no issues of this kind.
I tried installing both 32bit and 64bit Arch, disabling/enabling compiz, but nothing seems to solve the problem. My pc is a quadcore, 8gb ram, and a nvidia gt130 graphics card.
And excuse my noobness. I dont know which logfiles would be relevant to the issue.
Regards
Last edited by enderleit (2011-01-20 15:57:11)
Offline
Does it actually turn off? Could be the temperature of the cpu is getting too high. You should setup lmsensors to get information on computer temperature.
If the screen is just going blank then it's probably a graphics driver issue.
Personally, I'd rather be back in Hobbiton.
Offline
yes it actually turns off, so no, it isnt just the screen going blank
output from sensors:
[jesper@enderleit ~]$ sudo /etc/rc.d/sensors start
:: Starting Up Sensors [DONE]
[jesper@enderleit ~]$ sensors
coretemp-isa-0000
Adapter: ISA adapter
Core 0: +33.0°C (high = +74.0°C, crit = +100.0°C)
coretemp-isa-0001
Adapter: ISA adapter
Core 1: +42.0°C (high = +74.0°C, crit = +100.0°C)
coretemp-isa-0002
Adapter: ISA adapter
Core 2: +39.0°C (high = +74.0°C, crit = +100.0°C)
coretemp-isa-0003
Adapter: ISA adapter
Core 3: +42.0°C (high = +74.0°C, crit = +100.0°C)
it8718-isa-0a10
Adapter: ISA adapter
in0: +1.09 V (min = +0.00 V, max = +4.08 V) ALARM
in1: +3.01 V (min = +0.00 V, max = +4.08 V) ALARM
in2: +3.26 V (min = +0.00 V, max = +4.08 V) ALARM
in3: +4.08 V (min = +0.00 V, max = +4.08 V) ALARM
in4: +3.09 V (min = +0.00 V, max = +4.08 V) ALARM
in5: +2.14 V (min = +0.00 V, max = +4.08 V) ALARM
in6: +1.12 V (min = +0.00 V, max = +4.08 V) ALARM
in7: +3.02 V (min = +0.00 V, max = +4.08 V) ALARM
Vbat: +3.18 V
fan1: 2213 RPM (min = 0 RPM)
fan3: 0 RPM (min = 0 RPM)
temp1: +34.0°C (low = -1.0°C, high = +127.0°C) ALARM sensor = thermal diode
temp2: +37.0°C (low = -1.0°C, high = +127.0°C) ALARM sensor = thermistor
temp3: +29.0°C (low = -1.0°C, high = +127.0°C) ALARM sensor = thermal diode
Offline
Can only say check log files kernel all etc... for any clues, possibly a hardware issue but again could be anything
Sorry not much to go on
MrG
Last edited by Mr Green (2011-01-17 10:48:27)
Mr Green
Offline
Yeah i know. And it probably is a hardware issue, but then Im wondering how come it works flawlessly with fedora 14 ?
I can force the error for certain by playing youtube videos for 5 mins or so. But as I wrote, it has also happened once or twice with just a browser open.
Fedora 14 64bit has a 2.6.35 kernel and Arch has 2.6.36, could it be the Arch kernel is less resistant to hardware issues ?
Was hoping it was just some easy fixable rookie mistake . I really want to keep Arch as it absolutely rocks otherwise.
And I really dont know if the logs shows anything, as the computer shuts down like pulling the plug. And I dont know what to look for in which logs. Have been looking through the various logs in /var/log, but its rather hard, when you have no clue what to look for
Last edited by enderleit (2011-01-17 11:02:07)
Offline
enderleit,
your output from sensors is probably the temperature at one point in time.
To have a more or less real-time feedback of the temperature you can install "gkrellm" and configure the
sensors part.
Some applications can make the temperature jump to higher values.
But as Mr Green says, check log files.
Mektub
Follow me on twitter: https://twitter.com/johnbina
Offline
When I was 'debugging' my overheating laptop a while back I would run a bunch of intensive stuff, web browsers, videos, etc, and continually check sensors. The temperature would slowly rise up until it shut off. A BIOS update fixed it.
Personally, I'd rather be back in Hobbiton.
Offline
I had the same problem with one Acer laptop.
Adding 'nolapic' to the kernel line fixed the problem.
It some times gets fixed with 'noapic' or 'noacpi' in the kernel line too.
Hope this helps.
R.
Offline
I will try editing the kernelline when I get back home thursday. And if that doesnt work I guess i have to read up on how to flash my bios from linux ;-).
Thanks all for the quick replies, I will be posting the results of our efforts thursday :-)
Offline
You can do it via grub, first install syslinux and then copy the memdisk file as root
cp /usr/lib/syslinux/memdisk /boot/grub/
then edit /boot/grub/menu.lst
# (2) BIOS Upgrade
title BIOS Upgrade v1.45
kernel /memdisk # /boot/memdisk if no separate boot partition
initrd /biosupdate.img # /boot/biosupdate.img
The biosupdate.img file can be obtained on the internet, it will have a different name but will always be a floppy image. Memdisk allows you to boot the floppy image without a floppy drive. If you have a floppy drive you can just format it and boot from floppy via the BIOS (hit F12 or something).
Last edited by Anikom15 (2011-01-17 18:31:43)
Personally, I'd rather be back in Hobbiton.
Offline
Yay, apparently the kernel line fix did the trick. Ive been running 1080p flash videos nonstop for half an hour now, without any crashes.
Thanks a bunch guys, I am now one happy archer
Offline