danleff

Quote: At this point, I need the linux welcome screen to go away. That will enable autoboot from cd. right? No, this is not correct. The Linux bootloader is still on the Master Boot Record (MBR) of your hard drive. This has nothing to do with the cd being able to boot. If the bios is set to boot from cd first, then if this is a bootable copy of Windows, then it should boot before the bios even looks at the MBR. Either this is not a bootable Windows CD, or you do not have the bios set to boot first from the cd. What make and model system is this? There could be some other quirks that could be preventing the cd from booting.

I'm having the same issue with pppoe and Debian wireless. I would check over the Ubuntu wiki and see if you can find some good how-to articles. By default, in Debian, eth0 (the wired connection) is picked for pppoe by default. It ignores wifi (ie; wlan0) and I had to do some editing by hand. I did get my base internet connection up, but need to retrace my steps to see how I actually did it. I would also try posting at the ubuntu forums, as they have great support by their users. They should be able to get you going. I am away until May 5, but do report back and let us know if you find a solution!

This is the catch 22. RedHat 9 is no longer supported. I could not find a pre-compiled kernel update for 9 for the required kernel. If you have more than one kernel version on the system (ie: you updated the kernel at some time), then make sure that you have the required symlink and either the kernel header files or kernel source installed for your currently run kernel, as per the quote above... ls /lib/modules/`uname -r`/build. Also see the ndiswrapper wiki page for more information. Reverting back to an older version that may work, I would not recommend. There are too many improvements in ndiswrapper to roll back to an older version effectively, especially if you have a newer wireless card. What make and exact model + revision card do you have? I'll be gone until May 5, so hopefully others can respond.

A preity good guide on installing ndiswrapper in SuSE 10 can be found here. Also, take note of the specifics for your card here. I will be away until May 5th, so hopefully others can comment if you have questions.

This is a large hard drive. Did you install this hard drive yourself, or did it come with the system? Some system bios' can't handle these large drives effectively without some modifications. Is it a PATA hard drive (IDE), or sata? If it is an ide drive, try getting into the bios and changing the drive detection from "auto" to "LBA" and see if you can boot either OS. Please post the make and model of your system, or if it is a self built system, the make and model of the motherboard. Also, if you can, get into a Fedora root console as root user and type in; /sbin/fdisk -l (the small letter L for the -l, not the number 1). if possible post the output. ...and yes, if you write over the MBR with fixboot and fixmbr, you will not be able to boot Linux, except with the recovery mode, by using the 1st Fedora install cd to get in.

Do you have different kernel versions on this installation? Also, according to the install readme file for version 1.14; Quote: Prerequisites ============= You need a recent kernel, at least 2.6.6 or 2.4.26, with header files for the kernel. Make sure there is a link to the kernel source from the modules directory. The command ls /lib/modules/`uname -r`/build should have at least 'include' directory and '.config' file.

I just found this issue myself. It seems that there is a bug in Grub in Fedora in some system configurations. If you feel adventurous and can afford to possibly muck up your system, you can try the fix. Let me know if this is a mission critical system or not and if you would like to give this a try.

I did some looking around. It appears that in your case, the WPN111 comes in one version, an Atheros chipset. There are two basic packages that can be installed to get Atheros chipsets to work in Linux. The first, madwifi does not support USB devices, from what i can gather. The second, ndiswrapper, should work. The issue is accessing the drivers from your cd, or off the Netgear website. They comes, as you noted, in an exe format. Fedora does not allow you to easily extract them - don't know about SuSE. The idea would be to extract the drivers, so that you can use them with ndiswrapper. Ndiswrapper can use the raw native drivers to get the device working. Let me look more at this. The process for your device is a little more complicated than usual, of course! You can look at the cd and see if the drivers come in a folder...they should be in a directory marked Drivers-->Windows, or XP. If the cd just has the exe file, then this will not work easily. I do know that there is a way to extract these files (inf and sys files are what you are looking for), but I can't remember what the process is right now. You may also find them, if you did an installation of Windows on this system, or any other box, in a directory marked wpn111_setup.zip_FILES depending on the version of the drivers that you used. Of course, there are two versions of the drivers, with differnt names of directories that either create when they are extracted.

Good, your making progress. i was going to have you install the system-config-display utility, which would have worked also. I have read some previous documents on the Modem, but from what i remember, this will not be easy for a new user. You should have an ethernet card built into the system, which would be the way to go (the easiest). In this configuration, you would connect the box to the modem w/o usb, via a cat5 cable. linux will pick this up automatically. thios way you bypass the usb hassles. You can read NTFS filesystems from within Fedora, after you install a package which allows reading of NTFS volumes. If you want to give this a try, I will provide some links. Otherwise, the easiest way to do this is to share Windows files via a FAT32 partition (rather than NTFS), which Fedora can read and write to. If you add a FAT32 partition to one of your drives, than this would be the easiest way to go. Of course, this means that you would need to resize your Linux partition, or add such a partition, if you have free space on any of your drives. Is there any free space on your system now, or room that you can safey make for such a partition?

Two comments. Well, maybe more. Linux and USB wireless adapters are a little difficult to set up. realize that these adapters are made for Windows users, as are their drivers. It is possible to get it to work with some persistence on your part. Linux does not use exe files. These are Widows executable files. What exe file are you trying to use, the driver package from the Netgear website? Do you have the cd that came with the adapter with the Windows XP drivers on it? Just a suggestion for the future. When you buy any OS, make sure that the hardware that you are planning to use is compatible with the OS. SuSE has a good hardware compatability database for this purpose.

headlesstinman; Please start a new thread topic with your question and give as much information as you can, so someone can fully understand what your issue is. Please include what distro (flavor of Linux) and version that you are using and what packages (software)that you are trying. This question has nothing to do with what is being discussed on this thread. You will get better responses by starting a new thread and posing your question with as much information as possible.

QUESTION 1 How is the ADSL modem connected to the computer, via USB, or are you using a NIC card and cable? QUESTION 2 Well, we have gotten this far without knowing anything about your computer. What make and model computer are you using? Do you have any idea what video card is in the system? What monitor is being used (make and model, if this is not a Dell, Gateway or Compaq system and you posted the make and model already). Where are you looking at the video resolution settings? There are two places to look and you can install the system-config-display package through the software manager tool, if it is not already installed. This will help, but resolution depends on your video card and monitor. Some are well supported and others are not. QUESTION 3 You don't. Windows can't read Linux partitions.

Glad that you got it going. The answer to your final question is yes. Change the value from 0 to 1.

I believe that this function, in Fedora, just writes the file to a cd disk, but does not burn the iso image to cd. You need burning software to do this correctly. If you look at the contents of one of the offending cd disks, do you see just one iso file written to the disk, or a group of files and directories, which indicate that the iso image was extracted and burned to the cd disk correctly. The other issue is the speed that the iso image is burned to the cd. It should be at 4X or 8X, no faster. Look to see if you have K3b burning software on your Fedora Core 3 installation. If not, and you are using KDE as your desktop GUI, install K3b either via yum, or the software manager in Fedora. Then you can try to burn the iso images to disk correctly by choosing in the K3b dropdown menu..--->Tools--> burn cd image or burn iso image. See if in K3b, that you can set the burn speed slow, as mentioned above and in my article.

Take a look at this how-to. Section 5.1.

Two questions. What burning program are you using and in what OS? What speed are you burning the disks at? See my article on the subject located here.

Yes, defrag the Windows partition first, before trying any resizing of the Windows partition. I agree. I think that the best utility to resize partitions is PartitionMagic. I use it all the time. But I'm sure elnystrom will not invest in this utility.

Quote: I decided to try out Fedora. I used the Fedora DVD to reformat my existing linux partions and use the default Fedora partitions. I set up Grub to install in the MBR on HDA, but now, when I try to boot I get a Error 17 after Grub starts and I can not boot Fedora or XP. Here is my current HD FS setup: HDA is NTFS. HDB1 is NTFS. HDB2 is Linux and HDB3 is Linux LVM. I tried grub-install /dev/hda, but I get an error saying "/dev/hdb2 does not have any corresponding BIOS drive." Some thoughts. 17 : Cannot mount selected partition This error is returned if the partition requested exists, but the filesystem type cannot be recognized by GRUB. Looks like you did not delete the Ubuntu partition(s) or mucked them up somehow. i don't use LVM and have limited experience with it. But, I wonder if this is ther problem, mixing partitons made with differnt distro installations. Also, describe how you are trying to run grub-install /dev/hda. Are you trying to run this from rescue mode off the Fedora DVD? If so, did you do the chroot /mnt/sysimage command once you got to a command line, before running te grub-install command, to get to the root filesystem of Fedora? The easiest solution may be to re-install Fdora and make sure that you delete the old Ubuntu partition, then allow Fedora to install it's default partition scheme. Also, are you sure that you wrote grub during the Fedora Installation to hda, or hdb? This could explain why the Grub 17 error, as the Ubuntu grub boot record could still be there with no reference files to refer to, if indeed you deleted the ubuntu partition.

Looks like you already went ahead with your installation from your other post. Please refer to that thresd.

Quote: So chose to install Fedora on drive 2, in the unpartitioned half of the 2nd drive. All went fine, I chose all default options in the boot loader, but now it boots straight into windows. When you installed fedora to the second drive, you accepted the default options. Most likely what you did was install Grub to the second hard drive, so it is not resident on your boot drive, the primary master that the system is set to boot from, the Windows drive. Windows boots up because there is no reference to Fedora on the boot drive, the primary master, which is set to boot in the bios. This question keeps coming up and folks do not seem to understand the concept of booting. Fedora assumes that you installed on the boot drive and defaults loading the grub bootloader to the drive that it is installed on, unless you tell it otherwise. To get Fedora to boot, you need to have grub installed on the boot drive set in the bios to boot first. Quote: Ive tried booting off the fedora disk , and changing the boot loader options, but it keeps reporting that "No Kernel packages were installed on your system". By just booting from the disk and choosing linux rescue, you are just in rescue mode, not the root of Fedora. It can't find the kernel files properly, so the error that you are getting. Try getting to the root Fedora filesystem, after using the rescue disk, by typing in the console chroot /mnt/sysimage This gets you to the root of the Fedora filesystem. Then try typing in the console grub-install /dev/hda Note: space between grub-install and /dev/hda DO NOT type hda1, you want the MBR of the hda drive, not the hda1 partition. Reboot the system and see if you get grub, with the option to boot both Fedora and Windows. The other issue is that grub defaults to only a few seconds before booting the first listed OS. Depending on what you chose to boot first (hopefully not Windows) during the installation of Grub, that OS will boot quickly. Let us know what happens, then we can change the timeout of the booting via Grub. Essentually what you want to do is get into the /boot/grub/menu.lst file and change the line that starts with timeout from 10 to 50.

This is a confusing part of learning Linux for most folks. Did you attempt to set up the card during the installation of Fedora? If so, did you just look at the regular section on NIC cards, or try the wireless setup? This is often missed by may installations folks do. Anyway, your card may be able to be used. The important thing to know about Linux, is that it works different from Windows. Most card makers have firmware for Windows only. Fortunately, you may be able to use the Winows XP drivers in Linux, with a little work. I'm not finding anything specific with Fedora and your card yet, but I believe it is a Broadcom chipset. There are some possible options, but, again, it will take some work on your part. If you opt for a new card, choose one with a Orinoco or Prism chipset. These often work "out of the box" with linux, once you set them up in the network utility in Fedora. To give examples, see this list. look for the green areas, where the cards are known to work. Look at the Orinoco and Prism chipsets first. Atheros chipsets slao work, once the appropriate package is installed to use your Windows drivers. One word of advice. if you buy a new card, make sure that it is the exact model revision, as noted in the link that I gave. Different revisions of the same model may have different chipsets.

If you are taking the course and they provided you with a copy of RHEL, then tell them that you need RHEL 4 U2, due to the exact hardware issue that we are speaking of.

Can you be a little more specific? You were able to do a full installation of XP? What happens when you try to boot to XP? Did you make one large fat32 partition when deleting the other partitions? Windows wants one partition on the drive that it can see to initiate the installation. This is why I recommended the other suggestions, rather than the Fedora method. BTW, what make and model of computer do you have? If you were able to do a full installation of XP and it will not boot, then pop in the XP disk and allow it to boot to the options menu. Pick "R" for rescue mode. At the resulting command line, issue the fixboot command. When this is finished, issue the fixmbr command and see if this allows a normal XP boot. Realize,that you must know the administrator password for XP for this to work.

From the Ubuntu wiki page Windows Dual Boot How-to. Make sure that you read the entire article, including the section on Issues with Windows XP and NTFS. Make absolutely sure that you defrag the Windows partition first. You should always back-up your important files, even if you don't install Ubuntu, to cd disks or DVD. You risk losing your data anyway, say if the hard drive goes south, or a virsu takes the system down.

The easiest way to do this, in your case, is to get the utility disk for the make of your drive. For example, if you have a Maxtor hard drive, download the Maxbast iso and burn it to a cd. Boot from this cd and choose to maker one large NTFS filesystem, by telling the utility to format the drive for XP use. Seagate has a good utility for this purpose, if you have a Seagate hard drive. See the respective hard drive maker's sites for their utility. You can also either burn a cd of Mepis or SystemRescue cd and use the utility qtparted, which comes with both cd disks to format the disk as fat32. Or, get cd #1 of Fedora and run the installer to the partitioning utility, format the drive as fat32, allow the partitioning to proceed, then exit the prcess before actually installing Fedora, just after the formatting is complete. But, the Fedora partitining utility might be the most confusing, so I recommend the previous suggestions.