Announcement
Collapse
No announcement yet.
Intel Core i7 and X58 experience?
Collapse
X
-
I installed a system based on a Gigabyte EX58 deluxe but for some reason, I am not getting eth0 or eth1 to show up in ifconfig. What's odd is that I had it working randomly once but after restarting I no longer have access to LAN. Any ideas?
Leave a comment:
-
Originally posted by jwilliams View PostThanks! It looks like MCE is enabled:
config-2.6.27-9-generic:CONFIG_LIRC_MCEUSB=m
config-2.6.27-9-generic:CONFIG_LIRC_MCEUSB2=m
config-2.6.27-9-generic:CONFIG_X86_MCE=y
config-2.6.27-9-generic:CONFIG_X86_MCE_AMD=y
config-2.6.27-9-generic:CONFIG_X86_MCE_INTEL=y
Leave a comment:
-
Originally posted by MisterIO View PostTo see if you have MCE enabled, you can go to the boot dir and do "grep MCE config*"(in that dir you should have a file called config-"something") and look for the things I posted on the previous message.
config-2.6.27-9-generic:CONFIG_LIRC_MCEUSB=m
config-2.6.27-9-generic:CONFIG_LIRC_MCEUSB2=m
config-2.6.27-9-generic:CONFIG_X86_MCE=y
config-2.6.27-9-generic:CONFIG_X86_MCE_AMD=y
config-2.6.27-9-generic:CONFIG_X86_MCE_INTEL=y
Leave a comment:
-
Originally posted by jwilliams View PostI am running a stock Ubuntu kernel, 2.6.27-9. I'm not sure if MCE is enabled, but dmesg | grep -i machine does not find anything (also nothing in /var/log/messages), so I guess not.
I have been running the computer quite a bit (I am using it now) so if an MCE is very bad, probably I'm not getting any?
Also, I replied in another message that I got my F4K BIOS update from a tweaktown board, but I think my post got sent for moderation because of the URL. Hopefully it shows up soon.
Leave a comment:
-
Originally posted by MisterIO View PostMCE = Machine Check Exception(very very bad, it usually means an hardware problem)
In this particular case though, it happens only at boot, so it may be related to a bug in the bios, which causes the MCE at boot POST time.
To search for it, first you need to have a kernel with MCE enabled. If you use a debian kernel, that's good. If you don't know, just do a "grep MCE config-file", where config-file is the config file used to build your kernel. You should see this :
CONFIG_X86_MCE=y
CONFIG_X86_MCE_INTEL=y
Then just boot your system with that kernel, wait ~10 minutes(even a lot less should suffice, but just to be sure), then on root terminal type "dmesg | grep Machine". If you get something like "Machine check events logged", then an MCE got logged. depending on the distro(and the log daemon), you may also try "cat /var/log/messages | grep Machine", but just using dmesg should suffice.
Another thing, have you ever heard the cpu fan in Linux? I haven't, not even when I touched more than 70?C. I guess that's because this motherboard and cpu is still not supported. I can get the readings of the cpu sensors, but the system doesn't seem to react to to the temperature readings.
I have been running the computer quite a bit (I am using it now) so if an MCE is very bad, probably I'm not getting any?
Also, I replied in another message that I got my F4K BIOS update from a tweaktown board, but I think my post got sent for moderation because of the URL. Hopefully it shows up soon.
Leave a comment:
-
Originally posted by jwilliams View PostI have a UD5, but my CPU is a 965. My kernel is 2.6.27-9 x86_64. If you tell me what an MCE is and what your log message looks like, I will check my logs to see if I have it.
In this particular case though, it happens only at boot, so it may be related to a bug in the bios, which causes the MCE at boot POST time.
To search for it, first you need to have a kernel with MCE enabled. If you use a debian kernel, that's good. If you don't know, just do a "grep MCE config-file", where config-file is the config file used to build your kernel. You should see this :
CONFIG_X86_MCE=y
CONFIG_X86_MCE_INTEL=y
Then just boot your system with that kernel, wait ~10 minutes(even a lot less should suffice, but just to be sure), then on root terminal type "dmesg | grep Machine". If you get something like "Machine check events logged", then an MCE got logged. depending on the distro(and the log daemon), you may also try "cat /var/log/messages | grep Machine", but just using dmesg should suffice.
Another thing, have you ever heard the cpu fan in Linux? I haven't, not even when I touched more than 70?C. I guess that's because this motherboard and cpu is still not supported. I can get the readings of the cpu sensors, but the system doesn't seem to react to to the temperature readings.Last edited by MisterIO; 15 December 2008, 12:37 AM.
Leave a comment:
-
Originally posted by Jupiter View PostThe 'W83667HG' is the sensor chip the Asus board has. Your mb probably
has a different sensor chip. I am basically using a 'W83627EHF' module
for now because it is very similar. 'modprobe w83627ehf force_id=0x8860'.
A patch has been added to kernel-2.6.28-rc8 to add support for the
w83667hg module. The lm_sensors repo now has a beta version that
allows coretemp to be recognized as the Core i7 temp module.
Sensors-detect has also been patched to detect w83667hg.
http://dl.lm-sensors.org/lm-sensors-3/snapshots/
I'd like to check any motherboard temperature sensors I can, since I am using a CPU cooler that blows air parallel to the motherboard, and I am wondering whether the motherboard chipsets are receiving adequate cooling.
Leave a comment:
-
Originally posted by MisterIO View PostDoes anyone else have an I7 920/940 with a Gibagyte GA-EX58-UD5? I have one and I've been using Linux 64bit in it for some days now. There seems to be some problems with this hardware configuration, because I get an MCE logged every time I boot, but never more after the boot(at least for what I've seen so far). I've posted about this on the lkml and I received emails from other 2 people who have the same problem. The MCE gets logged only on kernels >= 2.6.27(64 bit).
Leave a comment:
Leave a comment: