danleff

I tool a look at the specs. for your system. I bet the issue is that this card is attached to a PCI Express interface. It looks like some have found information on this and a script that works for the card, but, this assumes some knowledge with Linux and making this work. Support for PCI-E is just emerging and I wonder if the next version of Fedora will fair better. Let me look around some more. I did find this statement by Shuttle on Linux support. Did your system come with a driver CD that includes Linux drivers?

I assume you mean to install tha source package? I did find a thread located here that gives some hints. Also, armagetron is included in the Dapper repository, as noted here.

I looked up this router. It has 4 ethernet ports. If you hooked the network up via a LAN card-->CAT5 (Ethernet) cable, rather than via usb, this should work. Do you have a LAN card or built-in Ethernet in your system? There are no USB drivers that I could find for this router, as well. I assume this is a DSL provider that you have? Do you have to login with a user ID and password to access the DSL connection?

Was this an upgrade installation, or a fresh installation? Folks tend to use "upgrade" to mean different things. Did you cut and paste your Grub.conf file, or hand transcribe it? I see a couple of problems with it. There should be a space between rootnoverify and (hd0,1) Do you get any errors when trying to boot Windows, a "grub" cursor hang, or just a hang with no output?

I would not recommend going back to RH 9, for the same reasons. But I noticed that your drive has been formatted several times with various filesystems. I would zerofill the drive, which will erase everyting on the drive, including the MBR. See the utility from Samsung located here. that will do the job. What you want to do is low-level format the drive (erase HDD). This will allow you to start over, as if the drive was new and has no data on it at all. Note the directions provided.

ambardeep, your thread, as well as several other ones on this subject, has finally prompted me to write an article on the subject of installing Fedora or Linux. it will contain several considerations related to the same issues that you have experienced. I will post a location for it on this thread when it is finished. Do not worry, it will not contain any reference to one specific thread or person! Nor will it contain any material from any specific posts, except mine. Questions like your have come up many, many times. So it is time to document such considerations, so I do not repeat my posts over and over. This way, I can reference my thoughts and explanations more easily.

Now that we have more information about your system, some more things become clear. this is why it is beneficial to have the information. It would seem that Fedora Core 4 does not have native support for your sis chipset. See the threead located here. So the kernel panic is related to this problem. I know this is titled Fedora Core 3, but read down the replies and you see that the problem exists with FC 4 as well. I suggest that if you want to run linux, specifically Fedora, then you need FC 5 to install it without a lot of headaches. Esspecially if you want to dual boot with the sata drive with XP on the system. You are also missing one point that I was trying to make. If you want to keep the sata drive on the system to dual boot XP; 1. You must keep the sata drive with XP in the system, otherwise Fedora or otherwise does not know about it. 2. In order to dual boot successfully, the order of the boot drive in the bios must be the same as when you installed Windows XP. So, I assume that when XP was installed, the sata drive was the only drive in the system, or it was set f\irst in the bios boot order. If you change this to pata, when you will not be able to boot Windows XP in a dual boot environment, as you changed the boot order to other than when XP was installed. The Windows boot.ini file is expecting to find what it needs in the same logical order when XP was first installed. Remember, if you change the boot order in the bios back to sata, XP will boot. This is because the XP bootloader is on the MBR of the sata drive, AND the drive is in the logical order that it should be (when XP is installed). So you must have ther drives in the correct order when either OS is installed. So if you want a dual boot environment; 1. Keep the bios boot order the same as when you installed Windows XP, I assume sata first. 2. Install Fedora Core 5 (or a patched version of Fedora Core 4, as per the article). 3. Make sure that the Grub bootloader is located on the MBR of the sata drive, or the first drive in the boot order of the bios, where XP is located. If you have problems downloading FC 5, because of bandwidth issues, consider buying a set from a vendor. There are several around that are inexpensive, such as Linux Central . The complete set for $10.95 USD. One more consideration. This motherboard is an AMD 64 bit system? You can either get the i386 version of Fedora, or the x64 version, if it is available. Either will work fine. There are also other distros that should work on your system, so you are not limited to Fedora, as your only choice.

This is not the wierdest dual boot problem ever. It is actually a common problem that folks make. When you install Linux, you want to have both hard drives in the system, with the bios boot order the way you want to dual boot. If you take the Windows XP disk out, then put it back in after the installation, you can't expect Linux to know about it, can you? You also can't expect XP to dual boot, without making some changes. You are correct, RedHat 9 does not do sata. It is an old release, before sata support was added in. So, let's take a look at your hardware. What make and model computer is this? If you built the system yourself, what motherboard is in the system? This will tell us what exact sata interface that you have and support for it with Fedora whatever version. What make is the pata drive in the system? Why? This tells us the options for formatting your hard drive correctly and getting rid of any MBR which may be invalid. What you have is a pata drive that either still has the MBR written to it (if you have the bios boot order with the pata drive set first), or you wrote over the MBR on the sata drive (if it is the first in the boot order in the bios) and have a pata drive with mixed partitions on it. DOS boot disks and using fdisk in DOS will not delete all the information on the pata drive, especially if Linux was installed and a bootloader to the MNR. Not unless you really know what your doing. Quote: VFS:cannot open root "<NULL>" or unknown boot (8,3). please append a correct"root=" boot option kernel panic not syncing :VFS unable to mount root fs and loads to rubbish... Fedora's grub can't find the root filesystem on the pata drive, as the partition setup is most likely incorrect with the multiple attempts to install. Also, if you took out the sata drive during the installation, then put it back in, most likely the designation of the drives has changed, so Grub can't find Fedora where it expects it. From all the posts that have been on the forum for Fedora Core 4, I suggest trying Fedora Core 5. But either way, you need to install Fedora with some changes during the installation with how the bootloader is configured (the order of the drives at boot), as Fedora assumes that you are installing on the only hard drive in the system, unless you tell it otherwise. You must be careful where Grub and the bootloader is installed and have BOTH hard drives in the system. Of course, unless you know what you are doing. Please bear with me. It is difficult to know what you have done with all these installation attempts and manipulations of your partitions. essentually what you want to do is; 1. Get rid of any current partitions on the pata drive. 2. Have both drives in the system, with the bios boot order the way that you will keep it. No changes after the installation. 3. Install Fedora with the bootloader to the MBR of the drive that is the boot drive, not any other.

First, the ndiswrapper wiki card list that you referenced (#10 under Belkin) is for a different chipset, namely the version 3 Realtek card. If you have the version 2 (Atmel), support is already built in. However, as per my link in the first line of my post # 173849 above, there seems to be a bug with the upgrade to Dapper. See the last post on that bug report, which describes your situation exactly. Not you exact card, but the same chipset. I would post a thread on the Ubuntu forums, where folks are most likely encountered this problem and have found a solution.

I just looked around the Ubuntu wiki and a few other places. You don't need ndiswrapper. However, thee seems to be an issue with these cards in the new version. See the thread located here. Are you trying to hotplug the card, or have you also had the card in before booting?

When you open a new message foler and compose the message, go to the insert dropdown tab and look toward the bottom of the options. There is a request return receipt feature, as well as priority options.

If the correct card is also configured under the Video card section (not vesa), as well, and you still don't have support for the correct resolution, then you can try the Fedora FAQ how-to for the nvidia drivers, which has support for your video card. Alternately, if this is an LCD monitor, then you can also try the generic LCD support for the resolution that you need. Same process as with my last post.

Yep, the version 2 card has the Atmel chipset and version 3, the Realtek. This would explain the native support previously. Reference

The link that you provided is the version 3 driver, not the version 2, which is located here on the Belkin site. I wonder if this is the problem. They could have different chipsets. Do you know if this is the case? If it worked in the previous version of Ubuntu (without ndiswrapper), I am wondering what chipset that it actually has. It would be strange if it worked previously and not now, unless this is a bug in the upgrade process. What I was wondering, is where did you see references to the Bel6020.inf on the web? I can't get the cab files to extract after unzipping the exe package, so I can't see if it is there. How did you get the cab files to decompress? Maybe it just a fluke with Fedora Core 5. Reference

Are you using Gnome? If so, navigate to System-->Administration-->Display. Under the hardware tab, click on the "configure" button next to Monitor Type. Scroll down to Dell and you model will be there. Make sure that you pick the exact monitor model and type (digital or analog) that you have. Your monitor is listed as a selection. Then naviagte back to the "settings" tab and see if your resolution comes up as supported and that you can choose the one that you want. See if it works.

Thanks for the response. I was sufing for an answer and found what I think may do it, but lost the link! Looks like someone wrote a script to do the job, so it's not user friendly for the average user. Yes, that install link for FC is a good one! I have a bookmark for it, but have no referenced it in a while. Thanks for the reminder.

Have you asked this on one of the mailing lists for NoCatAuth? If you don't get an adequate response here, I would do so. I have no idea about this, but I did find this reference about the issue.

I have got as far as making the new initrd file with the LVM volumes. However, on boot, /proc and /sys fail to load. The directories are empty. Any thoughts, james419?

Can you supply a link or two on the driver you are speaking of regarding what you found on google? This ia a PCMCIA/carbus card, correct? ...and you had it working before with ndiswrapper? Which version card is this? It can make a difference.

OK, I going to make some assumptions. There are three models of this USB adapter. Straight F5D7050, as well as a version 2 and 3. I think the original version has a prism chipset, fromwhat I am reading. Versions 2 and 3 should be Ralink. Letś assume that it is version 2 or 3. What is the exact name of the inf and sys files that you used from the drivers disk? Did you use the Windows XP versions of the driver sys and inf files? many driver disks have the drivers for multiple versions of the USB device, so make sure that you used the correct ones for your version. You apparently did the ndiswrapper -m command, which does not load the driver, but places it in the modules.conf file so it loads at boot. lsmod | grep ndiswrapper shows that it it running. What is the output of the command, as root user; iwconfig Does it show rausb0 or something like that with the output of some parameters? Like; rausb IEEE 802.11b ESSID:"" Mode: Managed Channel: 0 Access Point: Not-Associated Bit Rate: 0 kb/s Tx-Power: 0 dBm Sensitivity=0/3 Retry: off RTS thr: off Fragment thr: off Encryption key: off Power Management: off Link Quality=0/94 Signal level=-95 dBm Noise level=-95 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 sit0 no wireless extensions. ppp0 no wireless extensions.

Hmmm... I don like this. Want to throw caution to the wind? Get into a terminal window, as root user. Type in; grub-install --recheck /dev/hde NOT hde1 Hit the enter key. See if XP and Fedora will now boot. It looks like the drive mapping was off, where hde (the IDE drive) was mapped first. If Fedora boots, but XP does not, report back what error or result that you got. You can also try changing the boot.ini back to the original value for rdisk and try again.

Yea, it looks that way. I could not find the updated version for SuSE 10. You could compile from source, but that gets a bit complicated. Why not keep 10.1 and install the Madwifi for 10.1, located here?

Quote: I have had linux running (FC4) successfully on this PC before on the PATA drive on the IT8212, but not dual boot. Installs and runs fine. I have it there cos it's an ATA133 interface. That's exactly the difference. Linux did not need to interact with essentually three different interfaces, ITE8212, IDE {traditional pata) and sata. I assume that when FC4 was et up on the system, this drive was the first in the boot order and/or perhaps there was no sata drive in the system? What Fedora and grub try to do is "guess" the correct designation of your drives, based on the bios settings on boot. Your system has some complex series of settings that can be made to detect drives on the system. If you in fact did tell FC5 to install to the MBR of the sata drive, and it did not, then this interactin is what I am referring to. If you boot straight into XP with the sata drive set first, then the MBR was not written over. The article that I referenced, the author ran into problems with this. He gave up and ditched the ITE8212 interface. I bet a bios setting needs to be adjusted to get it to work properly. Quote: Should I: 1. Boot to FC5 rescue, chroot /mnt/sysimage and grub-install /dev/sda to try and force a grub reinstall on the SATA? You can try this, but you may end up with booting errors, much like the author of the article did, due to the ITE8212. Quote: or 2. Change the BIOS order to boot from the PATA first (where Grub is from the last FC5 install). This will then basically how I had it when I had FC4 - PATA as boot disk, Grub in the MBA. If I do this I assume I will have to change boot.ini drive numbering as the SATA where XP is will no longer be the same reference (I have an XP boot floppy disk on which I can change boot.ini and get into XP), and I assume also I will need to reconfigure Grub to find XP again as it will have 'changed' locations? Yep, you are correct. Or, you can try "reverse mapping" in grub, which will fake out the bios order and change the logical order back to having sata first. Usually the commands are something like; title Windows XP (or "other" in the original config.) map (hd0) (hd1) map (hd1) (hd0) rootnoverify (hd0,0) chainloader +1 But, of course, this depends on how the drives are seen in your /boot/grub/device.map file. Any reason why you don't want Fedora on the sata drive with dual boot?

Could you post the model number of the adapter? There are several. Did you read the ndiswrapper instructions for SuSE, located here? Are you using the ndiswrapper package that came with SuSE, or did you use a newer version from the ndiswrapper website? Depending on the model number of your adapter, you may need a newer version of nsidwrapper. The article mentions that you may have an issue with having the wired connection set to be detected on boot. Where did you find directions that both needed to be loaded? You also mention that you have the wired card set as static and the USB as DHCP? Which is your connection to your ISP, dynamic or static? Finally, did you follow the basic instructions for actually loading the module and setting your essid and passphrase (WEP or WPA), if you have one?

Quote: Am I barking at the wrong tree anyway? Has no one been able to get it to work with LVM on USB drives? Should I just try partitioning it without LVM, and then the instructions work (basically - running the mkinitrd with the needed modules, and running it once from the grub console)? It seems that the system's bios has a lot to do with the problem. I just tried again and the boot failed, although I was able to configure the graphical grub screen, which was missing before. Most of the directions that I have seen speak to IDE drives, not sata. The situation is complicated more by using LVM for the filesystem choice. theng got it going with the traditiional Linux setup for partitions (no LVM) and FC5 seems to have changed some things. Most directions seem specific for FC4. He also noted; Quote: I thought it was just ticking the box that specified 'Hide RAID device/ LVM Vol Group members'; however the same 'magic number' still appeared at FC initialisation then I realised that LVM was still created. Hence, I chose Anaconda's custom layout option for disk partitioning. Which makes sense, as "hidden" just means that, that the partition is hidden from view, not that it is not created. In his case, he changed over to the traditional partitioning scheme. I found some other snags in the process and will report back and let everyone know my progress.