Comments on: Shiny new hardware! http://www.kallisti.net.nz/blog/2006/09/shiny-new-hardware/ I am not an IP address! I am a free 'blog! Thu, 22 Jul 2010 10:45:07 +1200 http://wordpress.org/?v=2.8.4 hourly 1 By: Robin http://www.kallisti.net.nz/blog/2006/09/shiny-new-hardware/comment-page-1/#comment-1449 Robin Wed, 07 Feb 2007 06:23:32 +0000 http://www.kallisti.net.nz/blog/2006/09/shiny-new-hardware/#comment-1449 The ethernet just worked, I didn't have to do anything. I haven't tested it at gigabit, my LAN is just 100Mbit. I think the module that it uses is 'forcedeth'. HTH. The ethernet just worked, I didn’t have to do anything. I haven’t tested it at gigabit, my LAN is just 100Mbit. I think the module that it uses is ‘forcedeth’.

HTH.

]]> By: LokiSnake http://www.kallisti.net.nz/blog/2006/09/shiny-new-hardware/comment-page-1/#comment-1448 LokiSnake Wed, 07 Feb 2007 06:04:22 +0000 http://www.kallisti.net.nz/blog/2006/09/shiny-new-hardware/#comment-1448 Hi, I built a new computer with a very similar configuration (same board, processor, and BFG 7600GT card). Instead, I am running Slackware. I am wondering if you got the gigabit Ethernet to work? If so, was a custom kernel needed? Do you know what module I need to add to support the on-board gigabit? A reply email would be greatly appreciated. Thanks in advance. Hi, I built a new computer with a very similar configuration (same board, processor, and BFG 7600GT card). Instead, I am running Slackware. I am wondering if you got the gigabit Ethernet to work? If so, was a custom kernel needed? Do you know what module I need to add to support the on-board gigabit?

A reply email would be greatly appreciated.

Thanks in advance.

]]> By: Blog Without An Important Name » Ubuntu 6.10 (Edgy) upgrade http://www.kallisti.net.nz/blog/2006/09/shiny-new-hardware/comment-page-1/#comment-243 Blog Without An Important Name » Ubuntu 6.10 (Edgy) upgrade Mon, 30 Oct 2006 02:52:09 +0000 http://www.kallisti.net.nz/blog/2006/09/shiny-new-hardware/#comment-243 [...] A few days back I upgraded my machine to the newest Ubuntu release. As is often the case with upgrades like this, there were a few issues. The main one is a conflict between my M2N4-SLI motherboard and the 2.6.17 kernel. I get the impression that Asus has left quite a few bugs in the firmware, and if you boot straight up, it gets so far and then just locks up. My first solution was booting the kernel with the noapic parameter, and that works. However, I was also reminded of this comment that suggest using the enable_8254_timer parameter. I’ll try that next time I reboot. [...] [...] A few days back I upgraded my machine to the newest Ubuntu release. As is often the case with upgrades like this, there were a few issues. The main one is a conflict between my M2N4-SLI motherboard and the 2.6.17 kernel. I get the impression that Asus has left quite a few bugs in the firmware, and if you boot straight up, it gets so far and then just locks up. My first solution was booting the kernel with the noapic parameter, and that works. However, I was also reminded of this comment that suggest using the enable_8254_timer parameter. I’ll try that next time I reboot. [...]

]]> By: Patrick Hohmeyer http://www.kallisti.net.nz/blog/2006/09/shiny-new-hardware/comment-page-1/#comment-136 Patrick Hohmeyer Thu, 05 Oct 2006 22:37:01 +0000 http://www.kallisti.net.nz/blog/2006/09/shiny-new-hardware/#comment-136 A little WARNING though : I have almost the same build and the 2.6.15 kernel (which is what Ubuntu 6.06 uses) works fine. (as does 2.6.16). But after I updated to a 2.6.17 (or 2.6.18) kernel, it refused to boot. After a lot of debugging (including bisecting the kernel) I found out (two days ago), that I need to provide the kernel-parameter "enable_8254_timer" (without the quotes) in order to make it boot. Running with it since then and everything's fine again :) A little WARNING though :

I have almost the same build and the 2.6.15 kernel (which is what Ubuntu 6.06 uses) works fine. (as does 2.6.16).
But after I updated to a 2.6.17 (or 2.6.18) kernel, it refused to boot. After a lot of debugging (including bisecting the kernel) I found out (two days ago), that I need to provide the kernel-parameter “enable_8254_timer” (without the quotes) in order to make it boot.

Running with it since then and everything’s fine again :)

]]> By: Nathan http://www.kallisti.net.nz/blog/2006/09/shiny-new-hardware/comment-page-1/#comment-127 Nathan Fri, 29 Sep 2006 00:27:07 +0000 http://www.kallisti.net.nz/blog/2006/09/shiny-new-hardware/#comment-127 Hey, I really appreciate it, thanks Hey, I really appreciate it, thanks

]]> By: robin http://www.kallisti.net.nz/blog/2006/09/shiny-new-hardware/comment-page-1/#comment-126 robin Thu, 28 Sep 2006 23:11:48 +0000 http://www.kallisti.net.nz/blog/2006/09/shiny-new-hardware/#comment-126 It really sounds like a heatsink problem, or a faulty processor that is generating too much heat. For comparison, when idle (like right now) the heatsink temp is about 35C, with a room temp of about 15C. On a hot day, it'll idle a little higher, but never reaches 40C. When I'm doing something CPU intensive, it'll get up to about 42C and the fan kicks in, and then it'll sit around the 45C mark. I don't think I've ever seen it higher than about 47C, and that was when I was encoding two videos at once. The fan speeds up to compensate for the temperature change anyway, so it makes sense that it'll sit around a certain point. Note that these temperature readings are provided by a sensor in the heatsink, so probably add about 5 degrees to get the real CPU temperature. I haven't had to flash the BIOS at all. I don't know what BIOS revision I'm running though, but I expect if you bought it within the past month, it'll be similar to what you have. It really sounds like a heatsink problem, or a faulty processor that is generating too much heat. For comparison, when idle (like right now) the heatsink temp is about 35C, with a room temp of about 15C. On a hot day, it’ll idle a little higher, but never reaches 40C. When I’m doing something CPU intensive, it’ll get up to about 42C and the fan kicks in, and then it’ll sit around the 45C mark. I don’t think I’ve ever seen it higher than about 47C, and that was when I was encoding two videos at once. The fan speeds up to compensate for the temperature change anyway, so it makes sense that it’ll sit around a certain point. Note that these temperature readings are provided by a sensor in the heatsink, so probably add about 5 degrees to get the real CPU temperature.

I haven’t had to flash the BIOS at all. I don’t know what BIOS revision I’m running though, but I expect if you bought it within the past month, it’ll be similar to what you have.

]]> By: Nathan http://www.kallisti.net.nz/blog/2006/09/shiny-new-hardware/comment-page-1/#comment-125 Nathan Thu, 28 Sep 2006 22:59:02 +0000 http://www.kallisti.net.nz/blog/2006/09/shiny-new-hardware/#comment-125 Hey... maybe you can help me... I am building an extremely similar machine but am running into a problem and I am having a really difficult time isolating it. Athlon X2 4600+ AM2 M2N4-SLI 2 * 1g DDR2-800 BFG NVIDIA 7800GT 2 * Western Digital 350gb SATA II During idle the CPU is at around 60 degrees C and hard locks up when trying to install any OS (no KB, mouse, animation, CD movement, HD movement, nothing) usually the first moment there is a CPU intensive task. I've tried everything I can think of... replaced the MB, reseated the heatsink/CPU, new CPU cooler, isolating every device I can think of in the BIOS, and a new powersupply (520W). Suffice it to say I'm fairly sure it is the CPU itself which is currently on its way to California to get tested by AMD. AMD said like 95% of the CPUs they get test positive so that makes me worry that they are going to send me an email and tell me that I'm a moron. If that happens, all I could guess would be another bad motherboard (seems unlikely), bad memory (seems unlikely because the MB detects it and does the full memory test without error), or something that came to me recently which is the BIOS revision. I can't check at the moment to the current BIOS revision because my processer is in a UPS package in the middle of colorado by now probably but it is either 0201 or 0301. The 0301 series, AMD says, is the first ones they decided to support X2 with. My (long winded) question to you is, did you have to flash your BIOS or update it in any way for your 4600 AM2 to work? Thanks, Nathan nathanmarcos@cox.net Hey… maybe you can help me… I am building an extremely similar machine but am running into a problem and I am having a really difficult time isolating it.

Athlon X2 4600+ AM2
M2N4-SLI
2 * 1g DDR2-800
BFG NVIDIA 7800GT
2 * Western Digital 350gb SATA II

During idle the CPU is at around 60 degrees C and hard locks up when trying to install any OS (no KB, mouse, animation, CD movement, HD movement, nothing) usually the first moment there is a CPU intensive task. I’ve tried everything I can think of… replaced the MB, reseated the heatsink/CPU, new CPU cooler, isolating every device I can think of in the BIOS, and a new powersupply (520W). Suffice it to say I’m fairly sure it is the CPU itself which is currently on its way to California to get tested by AMD.

AMD said like 95% of the CPUs they get test positive so that makes me worry that they are going to send me an email and tell me that I’m a moron. If that happens, all I could guess would be another bad motherboard (seems unlikely), bad memory (seems unlikely because the MB detects it and does the full memory test without error), or something that came to me recently which is the BIOS revision.

I can’t check at the moment to the current BIOS revision because my processer is in a UPS package in the middle of colorado by now probably but it is either 0201 or 0301. The 0301 series, AMD says, is the first ones they decided to support X2 with.

My (long winded) question to you is, did you have to flash your BIOS or update it in any way for your 4600 AM2 to work?

Thanks,

Nathan
nathanmarcos@cox.net

]]> By: Laurent http://www.kallisti.net.nz/blog/2006/09/shiny-new-hardware/comment-page-1/#comment-83 Laurent Sat, 09 Sep 2006 18:16:17 +0000 http://www.kallisti.net.nz/blog/2006/09/shiny-new-hardware/#comment-83 Robin, thanks a lot for these informations. It isn't easy to find compatibility information about Linux and ubuntu with so specific uptodate hardware. So I will try this MB ! Robin,

thanks a lot for these informations. It isn’t easy to find compatibility information about Linux and ubuntu with so specific uptodate hardware.

So I will try this MB !

]]> By: robin http://www.kallisti.net.nz/blog/2006/09/shiny-new-hardware/comment-page-1/#comment-79 robin Sat, 09 Sep 2006 00:15:04 +0000 http://www.kallisti.net.nz/blog/2006/09/shiny-new-hardware/#comment-79 Laurent, sure. I'm running Ubuntu 6.06 (Dapper) 64-bit. All the hardware support has been working fine (except an actual hardware-based issue with the video card, but I'm hopefully getting a replacement in a few days). Everything except the video card works with open source drivers, too, although I believe nVidia supplies binary drivers for the nForce 4 chipset too. Laurent, sure. I’m running Ubuntu 6.06 (Dapper) 64-bit. All the hardware support has been working fine (except an actual hardware-based issue with the video card, but I’m hopefully getting a replacement in a few days). Everything except the video card works with open source drivers, too, although I believe nVidia supplies binary drivers for the nForce 4 chipset too.

]]> By: Laurent http://www.kallisti.net.nz/blog/2006/09/shiny-new-hardware/comment-page-1/#comment-77 Laurent Fri, 08 Sep 2006 13:32:50 +0000 http://www.kallisti.net.nz/blog/2006/09/shiny-new-hardware/#comment-77 Hi, Thanks for theses great informations. I'm actually studying to build a new computer arround the M2N4 and an AMD Dual Core + Dapper Drake. Could you confirm me which Ubuntu version you installed ? Thanks a lot Laurent Hi,

Thanks for theses great informations.
I’m actually studying to build a new computer arround the M2N4 and an AMD Dual Core + Dapper Drake.

Could you confirm me which Ubuntu version you installed ?

Thanks a lot
Laurent

]]>