Jump to content

RaZoR1394

Members
  • Content Count

    14
  • Joined

  • Last visited

About RaZoR1394

  • Rank
    New Member
  • Birthday 11/03/1986

Profile Information

  • Gender
    Male
  • Location
    Scandinavia
  1. Hello. The current bios for my motherboards seems to have severe incompatibility problems with the newer Microsoft OS:s like Vista SP1 and 7 beta. Linux and XP SP3 works but newer editions of Ubuntu have started to complain about bad ACPI implementation in the BIOS. It still works though. In Vista and 7 however the computer keeps messing with my USB ports. USB ports dies, replugging the gadget/keyboard/mice does not work. I found out that it was a feature in the newer editions of Windows that turns of USB ports when not used. I put the power saver mode to performance just as described and it got better but the computer still had sever problems when shutting down. What happens is that the wheel keeps spinning, the harddrive keeps reading/writing but it takes at least 15 minutes to shut down. Often I just hold down the power switch for 4 seconds after trying a various things (fast touch on the power button several times) to cut the power. Before I turned up to performance I got bluescreens frequently (something about USB_DEVICE_BUG). I'm also having problems with the keyboard and mice not working while at the login screen. When it does work I have to wait at least 1 minute for the keyboard to power up. I usually run Linux primarily since 2003 but my new memory card reader is incompatible (I was so sure all memory card readers were UMS complaint, well I was wrong), so are a lot of software and lot of other devices. I just wanted to try Windows 7 to see if it was better. Well it certainly was but I have never been so frustrated with a computer since I used Windows XP as primary OS. Never have I had to throw my fist on the keyboard and scream. I'm running the latest bios that I'm aware of and I have tried working with Coreboot but that led nowhere as I had to update the acpi table and that is well out of my knowledge. I presume that the acpi table or whatever It's called has to be reworked in the bios. Here's some info from Everest:
  2. Ok from what I've gathered from a thread on Viaarena (VIA support) this card has severe problems with eSATA. There are other threads regarding this issue as well. http://www.tkarena.com/forums/ide-sata-rai...t6421-card.html Either It's incompatible with all my eSATA cases or the signaling strength is too low making it impossible to use eSATA cables over 1m. Still my eSATA cable is exactly 1m but it may be just too close to the limit.
  3. Running the VIA card as the only pci card in either slot 1 or 2 makes no difference on my first client. Any ideas? I also checked if there were any IRQ conflicts with the VIA card in Windows but XP says there are none.
  4. Ok, so now I have tried swapping places of the two pci cards (VIA and Audigy) without any results. I will try removing the Audigy 4 card and if it doesn't work then the VIA card is probably DOA.
  5. Sorry if my english is bad but It's not my native language. My first client is watercooled so it uses a special switch that switches on devices like speakerset, external eSATA harddrives, pump automatically when the computer powers on. I have to do this because the pump is not taking power from the PSU. But I will try your advice first. Then I will try swapping places of the Audigy card with the VIA SATA card. edit: I can also add that I have tried these switches on client 1: pci=routeirq, irqpoll, pci=noacpi without any results. This is a snippet from my dmesg (client 1): I'm not sure of how to check IRQ:s. I think you can do that under Windows in the device manager but I'm not sure of how to do it under Ubuntu.
  6. Ok so I bought two burners and two VIA PCI sata cards for both my computers to cope with the increased number of SATA devices and to get rid of the IDE units. Burners seem to work fine luckily. Unfortunately my first client is locking up at boot when eSATA drives are connected to the new Via VT6421 card. Currently I have an eSATA bracket connected to the only SATA slot on the VIA card and there is also an eSATA port by default on the back. Connecting to these does not work without the computer locking up. The other client has one internal harddrive connected to the new VIA card but it doesn't lock up with it however I can't see it in GNU/Linux. It only locks up when connecting a eSATA drive to either of the back eSATA connectors on the two VIA cards. Both Windows XP and Ubuntu are having this problem on the first client. I have only tried Ubuntu on the second one. I have disabled all unnecessary things like IRDA, COM, IDE and AC97. I'm wondering if this could be an IRQ conflict problem but I don't know what more to to other than just remove the cards. I find this weird. On my first client the Audigy card connected to the upper pci slot is working fine while the second client locks up when an eSATA device is connected to either VIA cards. However if this would be an eSATA problem (maybe the long eSATA cables don't work so well with the VIA card), why is one of my internal drives not working? Please help me bring this out of the dark.
  7. Hello. Both my DVD burner's have problems (seems the laser is dying) so I'm considering buying two Pioneer DVR-215D and putting one in each client. Problem is that I've heard (at least when they were introduced) that SATA burners have compability problems with some motherboards. So will this work? My clients are in my SIG.
  8. Thanks for the help. However I have decided to return these Corsair sticks and buy two high quality 1gb sticks, maybe a dual channel kit from maybe Ocz or G-skill. That way I can use those sticks in my other dfi rig and lower to latency and timing and transfer my 4 Ocz sticks to my 24/7 rig. Which dual channel kit would you recommend? Are these good? Platinum Series Kit - 2x1024 MB, PC3200 DDR400, CAS 2-3-2-5 - OCZ4002048ELDCPE-K
  9. Hello. I've been running two 512mb sticks in the orange slots for more than a year now on my 24/7/365 machine without any problem. However I noticed that It's very close to start swapping and I would like to run more apps on it so I had to buy more ram. I bought another identical kit. I installed them while esd protected. It won't boot with these configurations: * all slots filled * one in yellow, one in orange in the same channel Even if I put the old memory in single channel it doesn't work whereas it works in dual channel. I have upgraded the bios to the latest 2bta, done the long cmos clear version, switched of CPC (=>2T) and increased voltage to 2.8v. It just gives me three red diag lights and continuos long beeps which indicates that the problem relies with the ram. What should I try next? new bios? other settings? I couldn't find any good settings in the database...
  10. Thanks, I will remember that. Maybe a flash update may fix it. What's the recommended bios nowadays?
  11. I would also check the SMART info. You can do this with a GNU/Linux livecd/dvd. I also had a Raptor that died after about a year. Mine was watercooled so It doesn't seem like a cooling problem for me.
  12. Ok, I changed the cables like I didn't want do to and it works now . However weird that 3 and 4 comes before 1 and 2.
  13. Hello. I have two internal SATA drives and one external SATA drive. The internal ones are two 74G Raptors connected to SATA 1 and 2. The external one is connected to SATA 3. On the first Raptor I have Windows XP32 and XP64. On the second one I have Ubuntu and on the external one I have storage stuff. I find that logical as the external needs to be placed last but according to the bios it detects the SATA 3 drive as the second one and the internal ones as 3 and 4. This creates some problems. After some failures I put the boot loader on the first 74G Raptor drive with the external one removed. This boot loader can load all OS's properly except Windows XP64 which gives a ntoskrnl.exe error. Unfortunately as soon as I connect the external drive Grub can't find the kernel probably because of the external drive becoming hd0 (later /dev/sda). Is there somekind of solution to this? I would really like an option where I could just make SATA 3 as "3" and not "2"! The only thing I can think of is putting the Windows drive on SATA 3 and 4 and the external one on 1 or 2. Unfortunately I would like to avoid that. Thanks.
  14. Hello. I'm having lockups once in a while both while surfing, gaming and watching movies. First I had problems unpacking tarballs and that was fixed by increasing voltage to 2.9v. I have tried memtest86 for some hours without any errors and I've compiled tons of stuff for hours which according to my sources is even more demanding than prime on Windows. There is a possibility that the ati-drivers may be bad or Xorg has It's issues... However, I would like to check if my settings are ok so I can rule it out. As you see I have 2gb memory (4x512mb) and a Clawhammer 4000+ so I've set it to 333mhz and 2t. I haven't touched anything else except pciex freq which is at 105 (ati) and some general bios stuff like usb keyboard, etc. I've checked the thread over at Bleedingedge but the only reference to 4000+ clawhammer settings I could find was related to Ocz VX memory. I can't find any info on 4000+ Clawhammer + Ocz 3200+ plat rev2. BTW, I tried following the Rgone "startup" post and the computer was unable to start after reboot. Even safeboot wouldn't work so I had to reset CMOS. And yes, I've plugged in all power connectors. Maybe it could be of interest.... I have another system with the same motherboard and with the same distro (gentoo 2005.0, ~amd64) and it has been running forever (server). I've surfed a lot on it and It has never locked up. I'm aware of the bug with the current bios I'm running (704) so If I need to change some more settings what bios would you recommend? Overclocking is not of my interest right now. I just want to run it stable as a rock.
×
×
  • Create New...