danleff

Well, OK, you did not mention this before. In this case, it sounds like a hardware issue. The best way to test the video card, would be to test it on another computer to see if the video card has gone bad. But, make sure that the video card is peoperly seated in the AGP slot. On some systems, you need to apply a little pressure when seating the card in the AGP slot. Also make sure that when you secured the card with the retention screw, that the card does not partially pop out of the slot on the far end. Some cards fit somewhat tightly on some motherboards and this can happen. On inspection, you should only be able to see a little of the gold connectors on the card in the AGP slot. What is exposed should be even. How long was the card working before this happened? It actually may be that the video card went south, if the card was working properly for a time. But, make sure that the card is peoperly seated in the AGP slot.

I l;ooked at the Intel web site. This is what they say about the 865GBF; Quote: What is the Intel® Extreme Graphics 2 controller? Intel® Extreme Graphics 2 controller is the integrated graphics controller within the Intel® 82865G Graphics and Memory Controller Hub (GMCH). The Intel® 865G chipset contains two separate, mutually exclusive graphics options. Either the Intel® Extreme Graphics 2 controller (contained within the 82865G GMCH) is used, or an AGP add-in video card can be used. When an AGP add-in video card is installed, the integrated Intel Extreme Graphics 2 controller is disabled. So apparently a bios change is not needed. They also say; Quote: What add-in AGP cards can be used? The D865GBF AGP socket is keyed for Universal 0.8 V AGP cards that comply with the AGP 3.0 specification or 1.5 V AGP cards that comply with the AGP 2.0 specification. The AGP connector supports 8x, 4x AGP 3.0 add-in cards operating at 0.8V, or 4x, 1x AGP 2.0 add-in cards operating at 1.5V. Note: There is no support for AGP 2x operation or legacy 3.3V AGP cards. I don't know if the 9200 SE meets these standatds. I can't seem to find this exact information. Some troubleshooting guides can be found here on the Asus site (I hope the link will work).

The problem with this thread is that there is not enough information to determine what the issue really is. If the system consistently boots to the incomplete Windows screen, then Windows may be damaged, or there is a propblem with the hard drive, or a corrupt NTFS partition. If trying to boot the Windows XP disk results in the system shutting down, then it may actually be a hardware problem, such as a bad hard drive, corrupt Windows partition, or even that the system is designed to shut down when it does not sense the proper fan speed. In this case, he may have a bad CPU fan. It could also be a power supply failure, or even memory failure. What would be good to know is what exactly, or as closely as possible, what the error message is that he is getting. Did he try to boot off the Windows XP disk? If so, was the bios set to boot off the cdrom first, or did he actually just boot partially into Windows again and the boot disk was not set to boot first in the bios order? Just because he is not connected to the internet, does not mean that he could have inherited a virus by sharing files that were infected with a virus.

Did you disable the onboard graphics in the bios, as suggested earlier? You didn't mention what motherboard this is, or what make and model system that you have. If not, then the onboard driver will continue to be re-installed when Windows starts and cause the issue. Also, this is an AGP video card and not a PCI card, correct?

In terms of the Realtek high definition audio, these drivers are probably going to be in the next alsa release. But, could you share what Linux distro and version that you are using? If Ubuntu, ther complex solution is located here. So, if you want to wait.... If you know enough about compiling patches and such...

Wait a minute, I just read your post more carefully, Is this a wireless card or PCI NIC card connected via an ethernet cable? Ndiswrapper is for wireless cards only. If this is a wired PCI card, what is the make and model of your computer? Sorry if I assumed that it was wireless, but when you said ndiswrapper, I assumed it was wireless and a ratlink based card (RT2500).

Is this the same system that you are having trouble with from your post here, or a different machine? If they are different systems, you may have a problem with your power at home. Take Cormac's good suggestion, but have the folks at the store test the computer with the thumb drive. If it works there, I would make sure that you have your computers connected to a seperate curcuit in the house from the TV. Make sure that you watch them test the laptop.

Let's take a look at what the ndiswrapper driver assistance package is supposed to do. It is not a driver, but a package that uses the Win XP native drivers to configure the card. Let me ask a couple of questions. Did you use the latest ndiswrapper package compiled from source, or the Fedora rpm package? What is the exact make, model number and revision of the NIC card that you have? Did you install the kernel source package to match the kernel version that you have for Fedora? Did you follow the distribution specific instructions from the ndiswrapper wiki page, located here? Quote: The same card is detected and used in windowsxp which i am using without any options for internet connectivity. Well not really. Either the drivers were configured already on the system, or you used the manufaturer disk to install the Windows drivers. This assists in setting up the card. If you get no hardware present message, then the drivers were not installed correctly, you used the wrong drivers, or the card is not supported in ndiswrapper. Did you look at the ndiswrapper card list to see if your card is known to work with ndiswrapper, or what the suggested drivers are to use with ndiswrapper? Did you use the Windows XP drivers (inf and sys) files to install with ndsiwrapper. If so, from where? There are other Ratlink drivers to get the card to work in Linux, but let's see what you have done and found out so far.

You can get the drivers at the Intel site, depending on your exact OS here.

You already have alsa installed in a default Fedora installation. It should be newer version 1.0.11rc2 in Core 5. The issue is how to get it to work properly with this driver. What happens when you go to a terminal window, as root user and enter alsamixer (hit the enter key). When the config. screen comes up, adjust the volumes on the active channels almost all the way up. Then hit the esc. key when you are finished. I also found that with some cards, you also have to adjust the balance, even if it seems slightly off center, to get both speakers to work. Try doing this all from within alsamixer.

It looks like you found how to use the livna repositiries. One good article on this subjext is the Fedora Core 5 Installation notes. Another is the Unofficial Fedora FAQ Page. By default, Fedora requires a login. However, look at this article which explains how to set Gnome and KDE with auto-login.

Actually, I have been commenting on FC5 in your case. Quote: Also, these motherboards and process ors are fairly new and support may not be resident on FC5 for your chipset or processor type. I mentioned FC6 test, just to explain what happened with the test version to me. I did find this thread which most likely explains your issue. Maybe not a solution, but a confirmation that it is an issue. I suspect the bios and it's processor settings are at issue, and possibly proper support for the processor and it's chipset.

Great! My next guess was that the onboard ethernet was interferring with pppconfig and was configured for pon, or set to start at boot-up. Nice work!

I had all kinds of problems with Fedora Core 6 test 2, which would not install on my system. I would not recommend it for everyday use, as it is what it says, a test version. Something has changed with the installer from test 1 and 2, as test 1 had no problem with my Athlon 64. Test 2 also failed on my second system with a straight Athlon (32 bit) system. I looked around on Google and saw two scenarios. one, where folks had no problem installing Linux on these boards, the other were it just would not install. My installs seemed to fail as Fedora tried to probe the sata hard drives onmy system. You can try to install it in text mode, which might give you more clues on what the issue is. At the installation splash screen, type in linux text. It should give you some indication where the process fails. If it does install in text mode, then the issue is most likely related to the PCI-E chip on the motherboard and proper support for it. Also, these motherboards and process ors are fairly new and support may not be resident on FC5 for your chipset or processor type. What's important here is to get some idea what errors are appearing. Did you actually get to a command prompt, or did the process just stop? If the latter, then you should be able to see some sort of error message that occured, as the installation failed.

How do you know that the files on the partition are intact? The reason that I ask, is if you changed the partition to swap, then the partition should have been written (formatted) over as a swap partition. Also, which fdisk are you speaking of, the Linux fdisk, or DOS fdisk command? If you really were able to see your partition files with some utility, I would be interested what utility you saw them with.

Let's take a step back and see what you should be doing. To establish a connection, if the modem is supported, all you should need to connect via pon and poff, is the username for your ISP, your password and the name of the device that the modem is connected to. Did you read the Ubuntu wiki page on this, located here? Look at the section under pppconfig & pon/poff. Read that section. You should be choosing the options listed. There should not be any other options listed for the modem connection, except those mentioned. Also, look under the section Configuring the dialup connection to your provider.

Can you explain what you mean exactly by a disk imaging method? This means different things to different folks.

Take a look at this previous post. Looks like you are not alone. I will have to see what chipset is in this modem. The chipset is not listed on the Actiontec webpage, but note, it has no support for Linux, according to Actiontec. However, the Puppy Linux Wiki shows it as working, but gives no details. Wait a minute...I looked farther down. Is this modem connected via serial or USB?

What version of Fedora are you trying to install?

Can you post the exact model number of the Actiontec modem, located on the back/underneath ID panel of the modem?

The best way to have a wired internet connection in Linux, is by not using the USB port of the router/modem to connect to Linux. You would use the ethernet card in your system, if you have one, to connect to the router. Then the internet connection should work fine. But, you did not answer any of my questions about your setup, so it's impossible to know what you have in order to answer your questions. Wireless is a little more tricky, depending what card that you have, if this is a wireless setup. In windows, your ISP usually gives you a setup disk to do the job for you. In Linux, you usually have to do it manually, so knowing what you have determines how easy it will be to set up the connection. However, your last post says it all. If this system is used by the entire family and say you deleted Windows in favor of Linux (without having an idea how to set up the connection), then I can see your father's point. It would be best to have a second system that you could play with and learn Linux. Then you can convert the family by showing them how it works! You can have both Windows and Linux on the system, but I would not recommend this, as it seems that you don't know enough about the process to mess with the family system.

Off the top of my head, it looks like one of several issues. From my rote memory (trying to remember Yast settings), when you went to set up the wireless PCMCIA in Yast, did you check off the option to use PCMCIA? Also, are you using a WEP or WPA key? Hexadecimal or asci key? If you are unsure, check the router/modem settings. When you do iwconfig, look and see if you have a valid AP (not AP:ffffff) and if the WEP key shows accurately, or if it is garbled or displays exactly as it should.

Try this Microsoft article.

You need to download the i386 images from ftp://ftp.wustl.edu/pub/linux/distributions/fedora/5/i386/iso/ Note the location of the images. Do not use the sprms, if that is what you really did. The other possible issue is the quality and rating of the CD disks. Try burning the first disk, test it, then report back.

Your wireless card should have the Ralink chipset in it. there are basically two ways to do this. Either using the Ralink drivers to get the card up, or ndiswrapper, which uses your Windows XP drivers to recognize the card, usually the ones found on your driver CD that came with the card. For an idea on the subject, see my article on FC 4 test 3 (somewhat dated, but you get the idea) located here. The general article for Linux is located here.