danleff

You are probably correct. Let's look at what may have happened. Quote: At the partitioning stage I followed the default to "delete all Linux partitions and install Fedora". If you did this the first time, as well, understand that you had NO Linux partitions on the system, if Xp was the only OS installed, and the hard drive is occupied by one large partition. If you take a look at the Fedora installation instructions for partitioning, located here, you will see that you have three basic auto-partitioning options. 1. Delete all Linux partitions and install Fedora. If you have Linux partitions on the drive and want to overwrite them to use with Fedora, you choose this option. 2. Remove all partitions on selected drives and create default layout. This option erases and reformats the entire drive to use with Fedora. 3. Use free space on selected drives and create default layout. Use this if you have free, non-formatted space on the drive that Fedora can use. Quote: I would be happy to get rid of the Windows program and only run FC5 so I assume if I select "remove all partitions" This is fine, if this is really what you want to do. If not, and you want to keep Windows, I would make enough free space on the drive to install Fedora to and choose option #3. You can do this a number of ways, from within Windows XP, by using a partition manager like PartitionMagic, or a Live CD, such as a SystemRescue CD. Finally, you can also modify the partition by using Segate's Utility, available on their website. Quote: There is still over 100gig of disc space on the only hard drive installed on the machine. If you say that you have 100 gigs of space on the drive, is this free, non-formatted space, or is it occupiued by one or more Windows partitions? BTW, is the hard drive sata, or an IDE drive (pata)?

Well, first of all, your problem is the same as many others. I assume what you are saying, is that you have Windows XP on your primary hard drive and Fedora installed on a second physical hard drive in the system? Drive "C" and "D" are windows terms and don't mean much, unless you clarify this. In Windows, you can have a "C" and "D" partition (not drive) on the same physical hard drive. C and D don't necessarily mean different physical hard drives, unless you set a C and D partition on the same drive. See this thread. Or see thsi thread. Or see this thread. All these threads speak to installing Fedora on a second hard drive on the system. When you install Fedora on a second hard drive, and choose the default settings while doing so, Grub (the bootloader) is often installed on the second hard drive. Fedora assumes you will be booting from the same hard drive that you installed it on, unless you tell it so otherwise. If this is not the case in your situation (you have one physical hard drive only on the system in question), let us know. if you did install Fedora on a second physical hard drive, then you need to make sure that you choose Grub to be installed on the Master Boot record (MBR) of the primary drive, which is usually hda (the primary master drive in Linux lingo).

I just installed Gentoo 2006, so if you are still looking for an answer, I am going to try and configure my wireless tonight. Unfortunately, mine is an Atheros chipset, not a prism. So my task is a bit more complicated. This distro is not for the faint of heart to set up. So, please don't take any offense to my question on your experience with Linux, or Gentoo in particular. It took me a good part of the weekend to configure the basics. Are you using Gnome or KDE? Did you emerge the wireless-tools package?

Remember, I did mention to you in your other post, that RedHat 9 was not a good version to install on your system. It is too old for the hardware in your system. you are bound to have problems with it. Did you install the correct version of the driver package? You should have tried the Xfree 4.3 version for gcc 3.x, which is what RedHat was built on. On first thought, it should be the XFree86 4.3.0 (gcc 3.x) file. But realize, I have no idea if this supports your PCI-E video interface. So, you have Xfree86 version 4.3, not Xorg, which would be in Fedora Core 5. Additionally, the author of the package makes note of problems with the sis 760 chipset,which is what you have on your system. It sounds like you did the right things, but the question is, did you pick the correct package for your system? How are you trying to change the resolution and video settings? Are you using redhat-config-display via a command line, or otherwise? Also, from my perspective, if you set up the system without sis support initially, then the Xfree86 config file is probably set to vesa and your monitor not set up correctly, as it is most likely newer than what was supported by RedHat in it's time. I would assume that you would need to change the config settings in the /etc/X11/XFree86.conf file to use the sis driver, or set up the video card via a utility (say redhat-config-display) to take advantage of the new sis driver. Did you ask this question on the forum referenced on the author's website? This would make sense, since he developed the driver and that forum could best answer the questions that you pose? If you do chose to use his forum, make sure that you post what motherboard model you are using, that you are using RedHat 9 and what package you attempted to install. This will help them troubleshoot what the issue may be.

Quote: I run a Athalon 64 x 3200 desktop stand alone unit. Can you be more specific about what you mean by a stand alone unit.? This means different things to differnt folks. Make and model of the system please. Interface eth0 refers to the NIC connection on your system. Are you connected to the Internet? If by a stand alone unit, you mean that you are not connected to the Internet, this message means nothing, just that Fedora found no active NIC connection. Without knowing exactly what you mean by "following the prompts" it's hard to know what default settings that you chose for the installation. However; 1. If the bootloader was installed (as it seems that it was, because you get to booting Fedora), then apparently you got through the installation. How long did the installation process take? 2. When you chose the option to partition the hard drive, what exact option did you choose? There are three. One (the default) is to delete all linux partitions and install Fedora. If you had all your space taken up by the Windows XP installation with NTFS filesystem, this could explain one possible problem. I assume that there is only one hard drive in the system that you installed Fedora to? Do you know what video card is in the system, if you installed one other then what came with the system? But knowing about your system and the hardware in it, will help. Post any information that you think might be helpful. Understand, that answering your question is difficult, unless we know more information, such as if the system is compatible with Fedora to begin with. it's knda like asking "my car has an 8 cyl. engine in it and I just installed a new carburetor. It won't start, what could be wrong?"

What you want to do is modify the Windows boot.ini file. This needs to be done from within the Windows environment. See the Microsoft article; How to edit the Boot.ini file in Windows XP. However, take care to remove the correct entry, not the active one. I would just leave it alone.

Take a look at the Fedora 5 Installation Guide here. This article may also help, as well as this one.

Follow this link; How to Remove Linux and Install Windows XP

First of all, what version of Gentoo are you using? How much experience do you have with Gentoo? What exactly have you tried? What online guides? Please be specific, as it is hard to know what you have done, unless you tell us. It looks like lspci -v shows the card, so what have you tried to get the card up? Network Manager in Gnome? Command line setup of the card? Looks like you have a Prism based chipset card, so we know that. Gentoo is one distro that I don't use, but I looked at the Gentoo wiki page here, which gives a step by step how-to on wireless. I do have to admit that the documnentation is somewhat technical, so I can understand if you get confused.

Looks as if this is curently being worked on. See this article.

Quote: I'm installing FC4 now, when will I get prompted for the boot floppy or how do I create the boot floppy? By the time you read this. your nstallation wouldm be done and you found that there is no prompt for a boot floppy during the installation process. Fedora installs a bootloader, by default, to the Master Boot Record of your hard drive. So, there is no need for a boot floppy. Did you get Fedora installed and booting?

In order to understand what chipset is in your USB device, we need to know the exact model number and revision of the device. There are several revisions of this card, A, A2, B and D. Look on the ID plate to get the revision number. This will determine whether you have native support for the device, or if you will need to load a specific driver for it. if you don't know where to look, click on the reference link below and select the device that you have. This will bring up a screen to tell you where to look for the revision number. Reference Have you tried any solutions so far? Is your internet connection broadband or DSL? Do you have WEP or WPA set up on the router?

Let's start with the Netgear card. What have you tried already? Telling us this would help. 1. Are you using the ndiswrapper version that came with SuSE? 2. What version of SuSE are you currently using? 3. Did you follow the directions on the ndiswrapper wiki website? 4. Did you use the recommended Windows XP drivers? 5. Did you set up the essid and password for your router? Telling us what you already tried would help a great deal.

Great! unpocoloco, if you are still there, we now know how to get it going in Fedora. If you stuck with us, let us know and we will try to guide you through it.

I did some looking around. It appears that the sky2 module was not included in the base Debian kernel. However, you are compiling from scratch and that seems to present some new challenges w/o mkinitrd support. Take a look at this post on the subject. In terms of sky2 support, also look at this thread on sky2. It's for a notebook, but look under the lan section.

Quote: I find that very interesting danleff, becuase I am using the same hardware adn I have just successfully installed using a debian etch network install cd (EG. base system on teh cd but gets most packages off the internet) and this just worked! 100%! By the same hardware, do you mean that you also have a Shuttle SB86i, or just what you think is the same NIC card? If the former, you may have hit on the answer. The sk98lin driver is for the Marvell Yukon chipset. The 88E8053 seems to be the Marvell Yukon 2 chipset. Two different cards. Quote: So once past the network detection part I moved to another tty and had a look at the syslog. the module it loads is "sky2", have a look at my system afterwards no "sky2" on the system. I assume that you tried to load the sky2 driver by; modprobe sky2? Does it show up in ifconfig? If yes, did you restart the Network or configure it for auto DHCP during boot? I assume that you have broadband, not DSL, the latter which may need a username and password and be configured for DSL? The other question is, do you have the kernel source installed on the Debian Etch system?

If you have an 939Dual-SATA2 board, then you have Realtek RTL8201CL 10/100 Ethernet LAN PHY. Nice board! You should be using Fedora Core 5! Reference In any case, connect the LAN (ethernet connection) to one of the connections on the back of the modem, via a CAT5 cable. Then follow the directions listed here. Remember, the connection was set up by the ISP Provider's CD disk for Windows, not the case in Linux. So, you need to do it somewhat manually. If your connection is dynamic, not static, you should be able to forgo the need to input the Primary and secondary DNS numbers from you dsl provider.

Great! This shows why I refer folks to other distro specific forums at times. These forums are a good place to start, but sometimes the user specific forums have users who have already solved the problem specific to that distro. It can save time. This was the case here, where a specific package, not installed by default in Ubuntu, was needed to get the installer to run. loserboy02 was also using a run package installer type, so this is different from source. Important to know in this case, hence the question that I had about what exact package was being installed.

There seems to be a bug in Grub. I believe it has something to do with a users system and how it handles a default installation of Fedora. The grub booloader does not get installed correctly wheninstalling on a second hard drive. Since this is not a mission critical system, let's try the following; If you changed the bios boot order back to booting Windows 2000 first. If you did a default installation of Fedora and did not specify how the second hard drive should be partitioned. This would have given you a /boot partition on the target drive and set up a LVM (Logical Volume management) partiton. You know this is the caee, if you, as root user, type in; /sbin/fdisk -l (the small letter L} You see a small boot partition (hdb1) and hdb2 as LVM Type. Get to a command line (terminal) as root user. Get into grub manually and type in; grub (hit the emter key & after each command below) grub> root (hd1,0) (since fedora /boot is on /hdb) grub> setup (hd0) (the mbr of the first hd) grub> quit Again, this assumes the bios is back to booting from the Windows drive again, before you started the Fedora installation. Then reboot and see if you get both Fedora and Windows to boot.

Wrong location? Look in the /etc directory for the file modules. This is the file that should be appended. Not the /etc/modutils folder, I would guess.

...and if you read the last post by Vincent, he was unable to get the card to connect unless he followed the procedure that he outlined for hotplugging the card. The bug report is somewhat confusing, as the original bug file speaks to the F5D6020 orinoco-based wireless card, the last comment, to your card chipset. My point was to explain that there seems to be a problem with the card and PCMCIA. The Amtel driver is already in Dapper, but apparently has a problem. Given the issue at hand, this is why I suggested posting on the Ubuntu forum. Your more likely to get a good response, given others have had the same problem with these cards and someone is likely to have found a solution, which might include dumping the installed version and upgrading to a newer one. But, better let them tell you what exactly to do, then trying solutions that may or may not work. I would rather have you go there, then get frustrated with not getting a direct answer from this forum.

I saw your post on the forums. It looks like you should be in business soon. Let us know.

Which exact version are you trying to install? Can you give a link to the exact source? This is the next step in installing packages in Linux, from source. If you want the latest, then you have to consider this option. The Ubuntu wiki is a good place to start, as well. See the article on the wiki here on installing tarballs. I don't use this game (or many at all), but the key is the format that the latest package is in. It seems that there are a few installer types out there, so giving a link to what you are trying exactly will help.

try this link to see if you can get it going on boot. Skim down to the lines; # modprobe usbserial vendor=0xf3d product=0x0112 and appending this line to /etc/modules will cause it to be automatically (re)loaded the next time you reboot: You may need to follow the rest of the article, but make sure that you replace your vendor values for the examples given in red.

First, let me clarify. In all my posts, I do not advocate changing the bios order to boot Windows and Linux. In fact I have taken greeat pains to recommend against this, for the same reasons that you give with your dual boot issues. Let me also clarify, once again, what happens when you change the boot order in the bios. 1. Each OS that you install and it's ability to boot is dependent on where the drive is seen in the bios and how the drive is jumpered (IDE or pata drives) when you first installed the OS. 2. If you install Windows on a primary master drive and it is the first drive tagged by ther bios in the system, then the Windows boot.ini file points to the system startup files on that drive. 3. If you change the boot order in the bios to a second drive, that drive is seen as the first drive in the system. 4. You now have the second drive set first in the bios. Grub uses it's script to start the boot process (tag the boot.ini file to run Windows) on the correct drive, hd1,0, which means the master slave drive. This is correct now for Grub, but then the boot.ini file is invoked and says, "I am looking for the system files on the first drive in the system", or hd0,0. However, now this drive is really the Fedora drive, not the Windows drive, so Grub seems to hang. In this case, there are two solutions, either install Grub to the MBR of hda and keep the boot order as you always had it, or "fake" grub to change the boot order of the drives when you choose the Windows boot option, so Windows boots normally (reverse mapping). I am working on an article about this, for users that know how to modify the grub.conf or menu.lst file. But, this assumes that you feel comfortable with how to do this. I don't use Nortons, but found this article on Norton AV. If in fact, auto protection does not allow writing to the MBR, as a virus protection tool, then you need to turn off this feature, as per the instructions given, before installing any software or OS that may change any of the protected areas.