danleff

Take a look at the SuSE how-to located here. See if that helps. What exact drivers did you download from the net and from where?

The most common mistake during installation, is to install Fedora's bootloader options to the MBR of the wrong drive that boots into the bios first. Quote: I'm having a SATA hard drive on which Windows XP resides(made as Primary slave in bios) and a IDE hard drive(made as Secondary Master) where i installed Fedora Core 5 recently and after installed successfully and rebooted it did not ask for dual boot and went directly to Windows XP. There is no primary/secondary master or slave designation with sata drives, just what drive is set to boot in the bios first. If oct326's directions do not work, or are confusing to you (because you do not know how to edit the grub file), also take a look at my guide located here. Also, look here.

Take a look at the Ubuntu Documentation Wiki regarding networking here. The wiki is a great place to learn about the distro. What version of Ubuntu did you install?

The link to the driver is here. Did you try this driver yet?

You have 6 USB ports, 2 in the front and 4 on the back of the case. Are you plugging in your USB hardware on the back ports, or front ports? If on the front ports, try the back ports.

Also, take a look at this post on your laptop with Ubuntu.

Never tried Backtrak or Backtrack 2, but took a look at their wiki page. It looks like there are a lot of changes in the new version, including the installation process. That aside, did you follow the directions on the wiki for installation? It looks like you do not have Lilo (are they still using Lilo?) or the bootloader properly configured. Is there an entry for XP on the boot menu? In other words, did you set it up as a dual boot configuration and\or follow the directions on the wiki? There is a good video on this from the wiki, although it may be for the older version. Did you view this video? But to answer your question, as long as you still see the Windows partition there, did you try to boot into Windows recovery and use the fixboot and fixmbr commands to recover the master boot record?

What are you trying to run it under, Wine or Cedega? See this post Also see this cedega wiki entry

There can be a number of reasons why the drive is not detected. 1. The drive formatted as one large partition is not compatible with the system. 2. The drive is not jumpered correctly to be compatible with the system. 3. The hard drive is too large for the system's bios to recognize it. What is the make and model of the system, as well as the hard drive? You may have to partition the drive using the hard drive manufacturer's utility (on the system that you expect to use it on) for the utility to format it properly, then for the system detect it properly.

There is not much written about Linux in particular and this motherboard. But let me ask a couple of questions. When you say ¨multimedia system," do you mean that all hardware will work, or you want to use the box for video and audio editing? Any idea what flavor of Linux that you want to try? In Linux, hopefully the drivers (modules in Linux) are included in the Linux kernel, the core of the operating system, to run your hardware. The newer the version of the Linux distro that you use, the better the chance that the modules are included in the Linux distro. Of course, the newer that your hardware is, there is a chance that the modules are not yet included. This is also true for Windows, where manufacturers make drivers to make the newer hardware run. Some manufacturers will support Linux, some not. In a majority of the cases, there are modules (drivers) available from a number of sources, since there are a number of Linux developers working on drivers to make newer hardware run. So, if a piece of hardware does not work in Linux, then this is the time to ask the question about where to find the drivers. As you may suspect, there can be hundreds of different ways that folks can have there systems set up with as many different hardware configurations. For example, do you plan on using just sata drives in a normal cofiguration, or if you were planning to use a RAID array? Live CD versions are great to try first, as you get an idea if your hardware is supported "out of the box." Most Linux distros also have a wiki page that keep a database of hardware and if that flavor of Linux runs on their systems (what does and does not). Hopefully this is somewhat helpful, so feel free to ask any specific questions that you have as you start your journey with Linux.

Try this Microsoft article. Pay special attention to the FixMbr abd FixBoot commands.

What specific "drivers" are you speaking of? In Linux, hopefully the drivers (modules in Linux) are included in the Linux kernel, the core of the operating system. The newer the version of the Linux distro that you use, the better the chance that the modules are included in the Linux distro. Of course, the newer that your hardware is, there is a chance that the modules are not yet uncluded. This is also true for Windows, where manufacturers make drivers to make the newer hardware run. Some manufacturers will support Linux, some not. In a majority of the cases, there are modules (drivers) available from a number of sources, since there are a number of Linux developers working on drivers to make newer hardware run. So, if a piece of hardware does not work in Linux, then this is the time to ask the question about where to find the drivers. As you may suspect, there can be hundreds of different ways that folks can have there systems set up with as many different hardware configurations. This is why I asked the questions that I did, such as if your system will be a straight sata system, or if you were planning to use a RAID array, since you noted two different model drives for your new system. Live CD versions are great to try first, as you get an idea if your hardware is supported "out of the box." Most Linux distros also have a wiki page that keep a database of hardware and if that flavor of Linux runs on their systems (what does and does not). The compatability database on this site attempts to do the same. Hopefully this is somewhat helpful, so feel free to ask any specific questions that you have as you start your journey with Linux.

Head on over to the Ubuntu forums and also do a search on the card. This should give you the information that you need.

I assume that the EVO is a desktop system, not a notebook? Is the drive that you put into the new system the only one in the system, or did you add it to an existing drive already in the system? If the latter, how is it jumpered (IDE drive)? Also, you realize that is the hardware in the new system is significantly different than on the machine that you originally installed XP on, then you could run into some problems with XP?

Don't know if it will be compatible with Linux, it depends on what Linux distro that you use. Your motherboard is not listed yet in the Compatability database Are you plannng to use this box with just Linux, or a dual boot with Windows? Are you going to use a RAID array or the drives as distinct "regular" drives? If you are looking to use Linux for video editing, then you could try Ubuntu Studio. A lot of distros (flavors of Linux) have Live CD versions that allow you to test the distro without installing it to the hard drive. This allows you to see if there are any issues with your hardware.

Gigabyte GA-7ix, right? Was this computer used regularly or dusted off for use recently, or recenly put in a case (installed)? Check the motherboard manual. Is jumper JP-10 (keyboard power on) set to on or off? How did you reset the bios jumper exactly?

Take a look at this post

How about the CPUID website?

I remember reading about a problem like this with sound after resume from standby, or reboot, with Realtek HD audio. This issue happens all the time? Did you look at the audio faq page on the AsRock web page?

The reason that I mentioned the correct ps/2 ports, is that I have myself made this mistake. You are sure that the mouse is in the green ps/2 port and the keyboard in the purple ps/2 port. I was also referring to the onboard LED on the motherboard. You noted that the "lights" (plural) come on and then go off, is what you were referring to the onboard LED on the motherboard itself, not the computer case? Have you tried another ps/2 keyboard? Rare that they go bad, but it can happen. It is also rare that the keyboard controller goes bad on the motherboard itself, but actually my wife's did a while back. The bad checksum error usually means that the information stored in the cmos has been corrupted, or is incorrect. This can be due to a bad cmos battery, or bad/inadequate power supply, among other issues, such as a virus that corrupted it. Your system seems to have developed the problem since putting in a new power supply. This is why I mentioned this as a possible issue. Just to make sure, what is the make and model of the new power supply? I guess my question is now, what led you to put in a new power supply? Just to have a new one, or were you having some issues that led you to replace the power supply? The problem is, you were working inside the case. So, I assume that you used methods to prevent electrostatic discharge to the motherboard while you replaced the power supply? If you tried all of the above to no avail, then possibly you can reset your cmos and the system will work again. Take a look at the motherboard user's manual, which has a lot of information on how to set the bios values. Yes, I realize that you do not have a working keyboard. But if you try to use a USB one, then you want to make sure that the option that I mentioned is set, or that will potentially not work as well. Let us know where you are at.

Since the problem occured when you replaced the power supply, is the new power supply rated for P4 systems? It is a 24 pin motherboard connectpr with a secondary 4 pin connector also attached (atx power and atx 12v)? The onboard LED is lit to green when the system is powered up? If you try a USB keyboard, make sure that Legacy USB is set to auto in the bios, so that the keyboard gets recognized during boot. Also, since the checksum error occured, make sure that the default values are loaded in the bios and saved.

Are you sure that the keyboard and mouse are connected to their correct respective ps/2 ports? I assume that you disconnected them before replacing the power supply? A bios checksum error is usually a failing cmos battery, or corrupted cmos, but first; Check and make sure that the pins on the keyboard ps/2 connector are not bent. Try another keyboard on the system (ps/2) if possible. Can you also post the make and model of the system, or if self built, the make and model of the motherboard?

Try a search on low profile video cards which should give some possible results. One example would be Directron, who carries such cards. Of course you would have to determine if they will actually fit, based on the specs. of the thin client box. The other possibility would be mini-itx suppliers.

Kain; I am not probably be of much help, but figure that I can throw some free floating ideas into the mix. You have a complex array of bios options with your motherboard. Since you upgraded the bios, did you check the bios settings for USB fully? Sometimes the default settings, if that is what you chose when you upgraded the bios, miss a few things. In the users manual for the Asus motherboard, section 4.4.6, note the options in the Advanced-->USB Configuration. Are all eight ports activated? Is legacy USB support set to auto? What do the other settings say?

I have never used this distro, but some basics first. The correct syntax for fdisk is the command with the option of the small letter "L", not the number 1. So, fdisk -l Try that first. The mount command must have the option of what you are mounting. Just typing in the mount command just displays what processes are already mounted. So, if you type in a device to be mounted, it must contain the correct designation of the drives mounted, as well as where the device should be mounted to. Say mount /dev/sda1 /mnt/sda1 The device is the physical designation for the drive and the /mnt/.. is where it should be mounted to, so you can see the drive. Don't know if BackTrack is able to mount NTFS partitions, which you may have in your system which has Vista? In your case, I assume that you have a sata drive on the system, so it should show up with sd... designation. I assume that in qtparted (which I never use, as I found it somewhat unreilable in some cases) you are seeing the drive and it's partitions, as sata drives, not the hd designation that you expect to find, which wuld be for an IDE drive in the system. The BackTrack wiki should also help, which is located here.