danleff

First of all nice system! Dapper Dan is probably right. The best thing to do is to try and boot the live cd in another box. Preferably with older hardware. If it works, this tells you that it is likely a hardware issue, which I suspect. A common mistake is to burn an iso image at the top rated speed of the cdrw or dvd drive. ISO images do not like this. They like to take it nice and slow. On a cdrw drive, burn at 8X or below. Many Linux distros are just catching up with sata, hyperthreading and the like. So it would not surprise me if hardware is the cause. Additionallly, my DVD/CDRW drive is funky about burning and booting iso images. The other thing to try, if the image was burned at a slower speed, is to make sure that the cd is booted from the same drive that created the burned image. Of course, using good quality cdr disks help, as does using cdr media rather than cdrw media. I had this happen to me a few times. Booting failed with cdrw media but not cdr disks.

I'm afraid that you have fallen prey to the FC2 partition issue, which has been reported for some time. Did you choose a bootloader during the install, such as Grub to the MBR, or make a floppy boot disk. The answer to recovery depends on if you made a boot floppy or installed grub. Let us know what you have. If you have a method to get into Fedora, then it can be fixed from the Fedora command line. Whenever you receive such a message during an install, you should abort and seek what the issue is. FC2 sees the partitions on the drive differently than windows. So, the grub bootloader attempts to set variables different than what windows recognizes in the MBR. Do you have your Windows install CD? Hopefully your system does not have XP pre-installed and you don't have the cd. What you need to do is fix the MBR. First, in the bios, try setting the drive in question to LBA mode, rather than auto or CHS. Then try to boot the system. Hopefully you get the grub bootloader and can get into XP or Fedora. Note. Please, check what access mode you realy normal use to access disk. Changing access mode from Large to LBA for example can lead to lose data from your disk! If this does not fix the boot issue, then you will need the XP cd to get into the recovery console. How to do this is described in a Microsoft article here. When in the recovery console, you need to run fixmbr and fixboot. This should restore the MBR and you should be able to get into Windows. We can then go from there. References: http://www.fedoraforum.org/forum/showthread.php?s=&postid=14703 http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=115980

I hope you have a good reason to re-install Windows! Anyway, I borrowed the following from another forum; You have to boot from the first cd of fedora, in rescue mode. If you are in the prompt, do the following: # chroot /mnt/sysimage # grub-install <device> (where device is /dev/hda, if that is where you MBR is at) Of course, if you have a boot floppy, go to a root console and just type in; # grub-install <device>

Dapper Dan, let me know what you think. I have Suse 9.0 Pro loaded on my system. Generally pretty good. It will be interesting to see what changes have been made. Especially related to hardware detection.

A good howto is located here.

You mayw ant to see the most recent thread posted by Raist999 located here. This is a good find that you may want to take advantage of. The package includes Suse Pro 9.1!

In your case, it looks like the iso images may have been burned at too fast of a burning speed. What software package did you use to burn the images? Try burning the images at 8X speed or less. This is often an issue with burning iso images - don´t burn them at the highest rating for the burner itself. Choose the ¨burn image¨ function of the software to burn the iso images. try booting from the same cdrw that you used to burn the images. Sometimes, older cdromś have problems recognizing cd´s burned with a cdrw. And...you did not extract the images first with a utility like Iso Buster and then copy the files to each CD, did you? Mandrake has been having issues with the first CD booting properly. If the above was done and the 1st cd does not boot correctly, try the second cd, then when prompted, replace it with cd #1 and see if the install proceeds. Finally, the sata drives were already set up in Windows? If so, you may have trouble with Mandrake recognizing the drives correctly. Others have reported problems when sata raid is set up via Windows first.

Did you look at the amsn faq's located here?

OK, let's back up a bit. You are speaking of both source and RPM. Just unpacking the source kernel gz or bz files from, say, Kernel.org will not work, if this is what you did. The kernel will need to be compiled from either of these packages for the necessary kernel headers, links and modules to be installed properly. When you install the kernel source RPM from the distro that you are using, then the files are extracted and built automatically, usually to/from /usr/src/linux. This should be where you are pointing the NVIDIA installer to. If the installer can't find viable kernel source/headers, it will attempt to download and use one from it's own database, assuming that you have an internet connection. Again, what distro and version are you using? It appears that it is Mandrake? What does the command uname -r show as the kernel version? As mentioned above, if this is Fedora Core 2, I have no idea if this will work with the new x.org x-windows interface, which is new to Fedora Core 2. Fedora Core 1 still uses the XFree86 x-window interface, which the installer will work with.

From what I have gathered ( I do not personally have one of these boards or SATA), if you have set up SATA in Windows already, there are issues. If this will be a straight Linux system, then some have reported some luck. If you do a search on google and on this forum, you will get some answers. For example, here. Do a search on linux AN7, or Mandrake 10 sata and look at what others have done and their experiences.

Well, that all depends on what Distro you are using. What distro is it and where did you get the source? Are you referring to the kernel-source RPM's for Fedora...Mandrake...? Make sure that you have the right package for your current kernel.

First of all, what distro are you using? It looks like perhaps RedHat? My Samba is real rusty but... During the install of the distro, you intend to choose server or client? Generally, you need to set up the system with the same username and password on all the OS' that you use (at least in the older distro versions). So, when it prompts you for a password, what happens when you type the password in for the system? Windows 2000 machines also need encripted passwords enabled in Samba. See this article for a howto for RedHat. I need to ask, any reason why you chose this distro and version, rather than a more recent one (which would be much easier to configure)?

Yep, I'm not surprised. This is a fairly specific Windows program and probably requires specific native DDL files to work. Unless you know how to set these up, it is likely even if you got it to work, it would not be totally functional.

I have to agree with DapperDan. The chipset on this card is a C-Media, which translates to CMI8738 in Linux. Whether it is compiled into the kernel is another question. There is a link to another card by the same company, which has the same chipset, which is located here. In the articles that I found, the performance in Linux ws somewhat questionable anyway. I have the Sound Fortissimo, which has some of the same issues, although it has the Yamaha chipset. Just beware of what you buy. Go and get a Soundblaster in a local computer store or computer outlet. There are dozans of variations of the Soundblaster. Don't be tempted to buy one cheap at an online outlet. A lot of these "cheap" cards are legacy for Gateway and other companies and have issues when used on machines other than what they were designed for.

If you look at the fax at the web site for this product,they are firm about not having a Linux version of the product. Wine, in my opinon, will be a bear to get it working, since it has not been tried/tested by experienced Linux/Wine users and the Wine sites that I visit don't mention it as working under Wine. There must be a Linux alternative, but I have no experience with these programs, so I am of little help with this. Perhaps someone can suggest an alternative.

If you are an somewhat experienced Linux user and can install the nForce chipset drivers, then you can give it a try. The reports that I have read, are that the onboard NIC does not work out of the box. The reports also state that the onboard sound works fine in Alsa, usng the snd_810 sound module from Alsa. If this is your main system, I would not expect the NIC and sound to work, without some tweaking. If you have another NIC that you can use, like a RealTek PCI card, you will have better results. So, these are the considerations. The nForce chipsets seem to work better "out of the box" with Mandrake 10 and Fedora, which have the 2.6.X kernels as default and have the support built into them for these chipsets. They are newer versions of these distros, so you would expect such support. I wish that I could give you more specifics, but my nForce box does not have any more room on it's hard drive to install Suse 9 Pro, or I would give it a try for you. Suse 9 does have an install option for the 2.6 kernel (test version) but I have not tried that either. Since it is a test version, I would not rely on full support.

It's nice to see someone asking for directions on how to install before trying it! I could not find a mandrake 10 page but this is a good general guide. There are some considerations that may be dependent on your system. The article covers most of the important considerations, such as partitioning your drive and XP issues. You may want to post some specs. on your system so that everyone can comment on any potential hardware or other issues that they have already faced with their installs, as well as what worked for them. Some other considerations are; 1. Are you planning to dual boot (have Windows and Linux available on a boot screen) at startup? 2. I always recommend partitioning the drive ahead of time. This prevents any issues with Mandrake's installation partitioning tool that may can cause problems with systems with multiple OS' installed. Do you have any partitioning software available to you? 3. If you have Windows XP and plan to add Mandrake on the same drive, MAKE SURE that you follow the advice about defraging the XP drive before resizing it for Mandrake. If you are using the entire system for Mandrake, you do not have to worry about these issues. Let everyone know and good luck!

Ditto what Raist999 said. Is this a hard drive install of Knoppix, or off the cd? I'll have to look at Knoppix and see what it has. Does the card work in any other OS?

Take a look at this link and see if it helps. I believe that this is an Atheros chipset? If so, my D-Link DWL-G650 works with the Linuxant driver very well. Well worth the small outlay of cash to get it to work. You can try the trial version first, to see if it works. Take a look at the Linuxant driver page to get an idea if the card is supported.

What result did modprobe b44 show? This would determine if the driver is compiled in the kernel or not. Are you using a dynamic or static ISP? Start at the basics before worrying about IRQ's and such. If you have dual boot with Windows, does the card get detected by windows and is it usable in Windows?

Lot's of different opinions on configuring nForce chipset motherboards, but the A7N8X continues to generate posts. First, we would need to know what distro of Linux that you are running and the version. Secondly, what kernel you are running on the system. One thing that I remember is that the audio driver works with alsa under the i810_audio driver. There are two NICS on the system, the onboard nForce one and a 3com. What I have found from readers is that they could get one or the other working, depending on the distro they are using. In terms of compiling the nForce drivers, this would depend on the distro that you are using and if you have development packages installed that are needed to compile the package from source. Depending on how much linux knowledge that you have, would determine which route that you might want to take, compiling drivers, or having a distro work with most of the hardware "out of the box." Let us know what you think and what you are comfortable doing and trying.

This is what I found about the driver, which should be in the kernel source. "BCM 4400 ethernet OK: This is not supported in early 2.4 kernels, but the driver is on the CDROM provided Drivers/Lan/4401/Linux/bcm4400-1.0.1.tar.gz and on ASUS' website. To install from the network, a supported PCMCIA, PCI (or USB?) network card can be used. The driver is included in Linux 2.4.22 and above (module name b44). Most reports are that the driver is stable; although some have experienced problems with 2.4.22's version (2.4.23 changelog include fixes to this driver)." Found on this page So hopefully it is already there. Try typing in a console, as root user; modprobe b44 and see if you just get a prompt return with no errors. My knowledge in restarting the network server in Knoppix or Mandrake is rusty, but you should be able to add it in Knoppix in modules.conf to start on boot, if you get the command prompt after the modprobe command with no errors. I'll let the real networking gurus explain this to you more fully.

This is good news! I had heard that core 2 did not have a supermount option built in. I'll have to try it and see. DapperDan, did you use the upgrade route to core 2 or fresh install? Any problem with the issue with reading or changing your windows partition?

Are these drives set up as IDE drives and not scsi? What filesystems are on the drives formatted with, NTFS, vfat...? Also, how are the drive(s) jumpered...master primary, primary slave... If you are trying the drives one by one, make sure that you are using the proper cables for the drive(s)and that they are properly oriented for pin 1, etc and that each drive is jumpered correctly, based on the manufacturer's recommendations. Mixing drive brands (if you are using more than one of the drives in the system at a time) can be a problem.

Fedora Core 2? Could you post what commands/method that you are using to access the drive and if it is listed in your /etc/fstab file.