e_lion_1

I happen to use LinuxFromScratch - and have since 2.3 of the LFS book.

...the street lives on in a new form... Just tried finding it and discovered to moved around. Glad to see the collected wisdom won't be lost. Hello to everyone!

brando56894, have a look at the sensors.conf that I posted a while back...you might find it useful http://www.diy-street.com/forum/showpost.p...8&postcount=378

I might be able to help some...as I have had similar problems. When the kernel loops, what are the messages on the screen? Also, check DIY Street Linux Thread above for some good ideas. It is probably a RAM related setting. I have found that this is the trickiest thing to figure out. Keep posting back...I'll try to share ideas which worked for me - Rig #2 (see my sig.) is currently overclocked 25% (also, add a sig of your own too)

I wonder if a power spike came through the grid and fried something. Might I suggest that you check the battery first (button batteries are cheap), then the bios chip and then try changing the more expensive parts. It feels to me like the bios is scrambled.

It shouldn't be a problem - just switch it up like any cpu. I'm pretty sure that your bios is recent enough. Right now I'm using an opty in my SLI board with no problems. Now to make your software use both cores...you might need to research that a bit. Good luck!

So, after some searching, I discovered that most of the Winchesters in the overclocking database were running the ram on dividers...gave it a try and presto! everything works. My guess is that the memory controller on this cpu just doesn't like to be pushed too hard (esp. with the RDX200 board). Should anybody else have some thoughts, I'd like to hear them. Thanks!

yes, ponderingpete, the setup runs just fine at stock speeds. Rig #2 was a new build from scratch using some parts I had around (CPU, RAM, Powersupply) and new parts (RDX200, hard drive, video card). To be more exact, the OS starts booting up but then dies a few seconds into it, rebooting the computer in the process.

I've been off having an adventure with this RDX200 board I picked up. However, I can't seem to boot into WinXP or LFS when overclocked - I honestly don't understand why or what to change. Memtest passes with flying colors. Also, the CPU and RAM had been in my NF4 board OC'd with minimal problems. Any ideas? Bios Settings 250 MHz Disable x3 x10 1.425 Disable Software Reset Disable x16 Enable 1.250 126.4 % 2.8 1.8 1.3 1.3 1.3 DRAM settings 200 Enable 2.5 4 8 3 7 16 2 2 1 2 3071 Enable Auto 0 Level 11 Level 2 8 5 256 Disable 16 7 Disable :confused::confused::confused:

That feels like a driver limitation to me. It might be that the depth is too much (32). In the Xorg.conf find the line Section "Screen" and see if there is this line: DefaultDepth 32 If so, change the number 24 or 16. A depth of 16 still looks pretty good and does go faster, especially on older hardware! If the line does not exist, you can safely add it in the Screen section. Here's what my config file looks like: ... Section "Screen" ... Identifier "Screen0" Device "Card0" Monitor "Monitor0" DefaultDepth 24 SubSection "Display" Viewport 0 0 Depth 1 EndSubSection SubSection "Display" Viewport 0 0 Depth 4 EndSubSection SubSection "Display" Viewport 0 0 Depth 8 EndSubSection SubSection "Display" Viewport 0 0 Depth 15 EndSubSection SubSection "Display" Viewport 0 0 Depth 16 EndSubSection SubSection "Display" Viewport 0 0 Modes "1280x1024" Depth 24 EndSubSection EndSection Good luck!

It depends on the quality of your headphones/speakers. I found there to be a difference when using my Sennheiser HD570 headphones, but not so much for the cheaper ones I have lying around

I've found the 2GB Mushkin redlines to be working well for me so far, which are an infineon based RAM (from what i've read.)

After quite a while of tinkering and wishing that someone else had come up with something - I've now got a sensors.conf which works better than the default one: #### lm_sensors setup for the DFI NF4-SLI-DR #### #### by e_lion_1 #### chip "it87-*" "it8712-*" #### label area: putting the right name on things #### label in0 "CPU CoreV" label in1 "LDT Bus V" label in2 "ATX +3.3V" label in3 "ATX +5V " label in4 "ATX +12V " label in5 "Chipset V" label in6 "DRAM V " label in7 "5VStandby" label in8 "Battery V" label temp1 "CPU Temp " label temp2 "PWM Temp " label temp3 "Chipset " label vid "CPU VID " label fan1 "CPU Fan " label fan2 "PWM Fan " label fan3 "C/S Fan " #### compute area: making the numbers right - taken from the #### #### example sensors.conf file in the tarball #### compute in3 ((6.8/10)+1)*@ , @/((6.8/10)+1) compute in4 ((30/10) +1)*@ , @/((30/10) +1) compute in7 ((6.8/10)+1)*@ , @/((6.8/10)+1) #### setup area: acceptable levels o' stuff #### #### Voltages #### #### CPU Core #### set in0_min vid * 0.95 set in0_max vid * 1.05 #### LDT #### set in1_min in1 * 0.95 set in1_max in1 * 1.05 #### 3.3 V #### set in2_min 3.3 * 0.95 set in2_max 3.3 * 1.05 #### 5 V #### set in3_min 5.0 * 0.95 set in3_max 5.0 * 1.05 #### 12 V #### set in4_min 12 * 0.95 set in4_max 12 * 1.05 #### Chipset #### set in5_min in5 * 0.95 set in5_max in5 * 1.05 #### DRAM #### set in6_min in6 * 0.95 set in6_max in6 * 1.05 #### 5 V Standby #### set in7_min 5 * 0.95 set in7_max 5 * 1.05 #### Temps #### #### CPU #### set temp1_over 45 set temp1_low 15 #### PWM #### set temp2_over 60 set temp2_low 15 #### Chipset #### set temp3_over 60 set temp3_low 15 #### Fan settings #### #### Min accptable RPMs #### set fan1_min 600 set fan2_min 0 set fan3_min 0 #### Ignore area - for all those things you don't use ### ignore fan2 #### k8temp #### chip "k8temp-*" label temp1 "Core0Temp" label temp3 "Core1Temp" might not be exactly what the rest of you need, but enough to point in the right direction ... and save all the frustration i had

I don't think so....I'm currently using the 2GB redlines in my SLI-DR with no problems...be sure to check the mushkin forums too.... http://forums.mushkin.com/phpbb2/index.php also, notice the product number 991493 is the Infineon CE6 (which is what I have) whereas 991492 is the Samsung UCCC (I think...)

It might be a mixing issue. I haven't tried Ubuntu recently and have also taken the karajan module out of my motherboard, but I do remember that the kernel module needed is snd-intel8x0. And probably an asoundrc file would need to be done up as well. Check this link http://www.alsa-project.org the info there should point you in the right direction True...and most OC'ers aren't using Linux It is nice to see this thread stickied.