danleff

That error is common and does not have anything to do with your router. Ignore this for now. When you say that your kernel is updated, do you mean that you updated the kernel before or after installing ndiswrapper? If after, this will not work. you need to reconfigure ndiswrapper for the new kernel. If before, is the kernel source installed? What you look for in dmesg, is if the card is up during boot. You will see an id for the card and some text saying that the card is working. Do you have ndiswrapper running as a module on boot? Do you have your essid and wep key (if you have one) configured, so the card can connect to the router? Taks a look at the ndiswrapper Fedora page for specific instructions. Also, take a look at my page on the subject.

You also need the kernel source package to match your running kernel. See if this link helps. You want to get the kernel-devel package to match your kernel. Do not try to download just the plain kernel package, or a new one. Stick with what you have, in terms of the currently running kernel. If you don't, this will just comlpicate things. You can see what kernel version that you have by typing in a console, as root user; uname -r Also, make sure that your particular card is supported, by looking at the wlan hardware database page.

Go ahead and see if Mandriva sees the card in the network utility. If you see it there, it should be OK to proceed.

Good Job. Glad that it works!

Go to (let me see if I can remember); start-->system-->configure-->configure my computer. Then go to the network settings and try to set up the NIC card again. Choose to activate the NIC card on boot (DHCP). If the card does not connect right off after exiting the utility and accepting the settings, try rebooting and see if Firefox connects. What NIC card make and model are you using?

I was afraid of that. If you know how to edit the xorg file, change the monitor to "vesa" You may also need to change the horiz. and vertical refresh modes to match your monitor settings. Consult the user's manual or manufacturer's web page for your monitor. The old CRT, I am sure, had older refresh rates that will not work. If all else fails, I will try to post more from my xorg file.

Look at the "related threads" link below, which has some links that may be helpful. This is an area that lists threads that may have the same issues as you posted. The actual link to the thread is here.

Is this an LCD monitor or a flat CRT? Look at how to change the run level at the Fedora basic faq page. Follow the directions under "While You Are Booting the Computer." Once you are able to boot to a console, following those directions, look at Red Hat Linux Step-by-Step Installation Run the system-config-display utility. If it is installed, you will get a small GUI (hopefully). If this is an LCD monitor, try setting it to "generic LCD" and the appropriate settings that are found in the monitor's users manual. For most LCD monitors, it should be 1024x768, or 800x600 to get it going. If this works, you can tweak it later on. P.S. I deleted your other post, as it is a duplicate. Keeping the thread on one topic will avoid any confusion and keep the discussion on one thread.

Your title says that you changed the monitor...is this the case? If so, what old monitor did you have and what is the make and model of the new monitor?

Well, this is a shared forum for both the NT and Linux forums, so it shows up on both main forums. You can check the cpu temperature under the "PC Health" status main menu in the bios. Also, check the setting in the bios on the main menu "Load High Performance/Bios setup Defaults" and see if it is set for High Performance rather than the Bios defaults. Setting it back to the Bios default settings can solve stability issues. Have you changed any bios settings recently or added more ram?

...and what was the solution???? I am interested and others may be as well!

Can you explain in a little more detail what you are doing? Quote: I formatted the fedora partition from within windows and restarted my computer. Well that was stupid. The computer displays GRUB: and won't boot to windows or anything. If you erase the Fedora partition, you delete the /boot/grub directory, which Grub references to boot the system properly. Quote: Luckily I have norton systemworks which restores the grub. I don't think that Norton's does this, does it? Can you explain? Also, how did you attempt to recover the MBR exactly, on the old drive? Quote: I need to get some of the files from the old windows partition. It has some irreplaceable pictures of my family and my wife will kill me. I've tried putting the old drive in the new computer as "slave" and it does the same thing. Can you explain what exactly that you are doing? Are you trying to boot Windows from the new computer by changing the bios boot order to the slave drive? If the Windows bootloader is trashed, you can't do this. If the new system is attempting to boot right off from the slave drive, without you doing anything to tell it to do so, it is not jumpered correctly, or it is on the incorrect channel on the hard drive ide ribbon connection. What OS is on the new computer? If nothing and you are trying to boot the system off the old drive, jumpered as slave, this will not work. Windows still thinks that it is on the primary master and the Windows boot.ini file still is trying to point there. If your pictures are on the Windows partition on the old drive, you can just use My Computer to navigate to the old windows partition and get your files. That assumes that you did not trash the Windows partition on this drive by mistake.

No floppy or onboard cdrom drive? First, consider if this laptop would be compatible with Mandriva. Have you checked this out yet? Could you post some specs. on the system? You will need at least 256 mb of ram to do the installation. In your case, without a cdrom or floppy drive, you can do a hard drive installation, but would need the Grub bootloader installed on the hard drive first. There may be another option, but If you are new to Linux, I would not recommend it, as you would get too confused and frustrated.

Sorry, meant to say Compaq, which is also HP! If you want to read more on it here is the link. Often, as is this case here, these modems are "winmodems" made as legacy modems for Compaq and HP. They are designed to work with Windows, which comes pre-installed on these systems. Often, they are designed as AMR modems, which means that they are attached to a "combo card" (2 devices on one internal card). Because of this, they are not true hardware modems, with their own controller, which Linux would have no problem with. More often than not, the drivers for these modems are made by Compaq or HP exclusively for Windows. However, did you check the HP site for your model and see if there were any Linux drives? HP is getting better with this and have designed some drivers for their modems for Linux.

Did you try to set it up during the installation of SuSE? Quote: I have gone to the sites that tell how to get it to work and I guess I'm a bit green. not sure what I'm doing. What sites? Did you try setting it up in Yast?

Your best source of information, is thew ubuntu wiki. The link for the Wine section is here. The main page is here. The user documentation page is here. Some versions of Nero will work, in theory with Wine, but I never had good results with it. The Frank's Corner link that i gave above describes this. Tar files are like zip files, to an extent. Synaptic is designed to take care of dependencies that may be required (other packages that are needed to run specific packages, just like Windows requires some other programs to run, say java). Installing .gz or bz2 source packages (tar packages) are a little more complex. I suggest synaptic, which is much easier for a beginner. In terms of the original source file, I'll take a look.

Thea article that you references is old and for an older version of Ubuntu. You are using version 5.10, the article is for 4.10. The cdrom repository in synaptic is incorrect, as you should have the 5.10 reference there. The other links that show an error are dead, as they no longer exist. I hope that you saved your old sources.list file, or at least your old repository links. If so, you can replace it with the old one, then run apt-get update. Do NOT run apt-get upgrade. You formatted your second hard drive with all Linux partitions. Unfortunately, your old data is gone on this drive. Quote: but notice the file color on the Linux Ext2 partition showing it has files and the used space as well... what is there taking up that space. Would that be the another file system for linux already to go? Yep! Lost & Found is a linux directory where files that are not cleanly saved or shut down before exiting Linux are stored. Your old data and program files will not be there. Quote: I then searched my system and found it in the usr/apps/ area but it was just one file i double clicked it and it did nothing. So right now that is slowing me down. Only reason I want wine is to try to run my StrongDC++ P2P program. I tried using aMule and DC++. aMule doesnt really download, and DC++ is difficult in finding a hub and connecting. so thats why i want WINE. Wine does not run by itself. It is used to install and run Windows applications, basically from the command line. There are a very limited number of applications that run in Wine. To get an idea of what runs using Wine, see here. Another good reference is Frank's Corner.

This is a modem, legacy model, made for Dell to run exclusively in Windows. I did a search on it and found that it is a bear to get going in any distro. Not easy at all, if at all. Do you really need a modem, or do you also have DSL or broadband?

dan7 The modular bay does not make you swap out the cdrom drive, does it? Is the boot order in the bios the same, since you updated the bios, as the old one? If you don't need to swap out the cdrom drive, than hdb is the cdrom drive. Remember, this is seen as an ide drive by the bios and linux. The designation is usually; hd0 = primary master drive hd1 = primary slave drive hd2 - secondary master drive hd3 = secondary slave drive Quote: Few days ago, I upgraded the BIOS and put Windows XP (got rid of Windows 2000) on the primary HD. When the system rebooted, the GRUB menu was gone. Yes, when you install any version of Windows, it overwrites the master boot record where grub resided. When you installed Windows XP, did you reformat the hard drive and install Windows XP on the exact partition that Windows 2000 was on?

Will; Do you know how to edit Grub from the boot splash screen? I really need to write a web page on this to refer to! I have not played with my system with a raid card in it for a while. I think that I need to try this again myself. Linux is seeing the drives, I believe, in reverse order. This is not unusual. The raid card causes this. If you can edit at the splash screen, you can make temp. changes to grub there, without making them final yet (writing to the menu.lst file). At the splash screen, hit the "e" key on your keyboard. Bear with me, I have a Suse grub splash screen and Fedora may be different! When you hit the "e" key, you should get a text based screen. Loook at the bottom command options. Add two lines after the; title Windows XP So that it looks like the following; title Windows XP map (hd0) (hd2) map (hd2) (hd0) rootnoverify (hd0,0) chainloader +1 note: As you edit each line, just hit the enter key to make the changes take. If that does not work, try; title Windows XP map (hd0) (hd2) map (hd2) (hd0) makeactive chainloader (hd0,0)+1 When you are finished, and are back to the text screen that outlines the total Windows XP lines, hit the "b" key on the keyboard. This will attempt a boot. Let us know what happens. If this works, you can modify you actual menu.lst file later on in Fedora. If you maker a mistake, don't worry. Hitting the esc key gets you out.

Look at your other post for a response. Please don't double post. This confuses things and fragments any responses that you may get.

This is why you need to be careful when following directions given on a website. Is this article relevent to the version of Ubuntu that you installed? Which version did you install? Also, the link that you gave to the article is dead. Did you post the total link address? If so, maybe it is down this am. Two of the sites that were given to repositories have moved, so they are dead links. The others look like incorrect links to subdirectories. Linux is designed to run Linux programs, not windows programs. While there are packages (programs) that you can use to emulate running Windows programs, they are still coming along and do not run every Windows program well. Quote: whats the point of using linux when you still need windows? Well, that's true and not true. You can find programs that are designed for linux that will do everything that your Windows programs do. While you learn Linux, you can still use your Windows programs via dual booting. Windows and Linux are two different operating systems. Look at it this way, would you try to run your gas powered car on Diesel fuel? Two different engines, correct? Once you get comfortable with Linux, I think you may see things differently. Remember, you are learning something new and need to think in this regard.

dan7 I assume that you have the drives jumpered correctly, are using ide drives (not sata or raid) and that the installation was set up to boot your hda drive (HDD0 in the bios) first when you did the installation of Fedora? Can you post the /boot/grub/menu.lst and /boot/grub/device.map file contents by any chance? What motherboard is this, or the make and model of the system?

Oopps! I meant to say; You have a pci raid controller card, not an onboard raid controller, correct? Notice that your hard drive designations are different than expecetd, due to the raid card. (fd0) /dev/fd0 (hd0) /dev/hdb (hd1) /dev/hde (hd2) /dev/hdf Where, in a totally ide system w/o a raid card, it would be something like; (fd0) /dev/fd0 (hd0) /dev/hda (hd1) /dev/hdb (hd2) /dev/hdc The drive orders are also interesting in Grub. The difference is based on how the raid card affects the drive order. Can you post the output of; fdisk -l Do this as root user in a console screen. In Fedora, you may need to do; /sbin/fdisk -l Remember, this is the letter L (small case), not the number 1 after fdisk. This will tell us where the Windows installation is, as seen by Fedora.

Quote: i hv read wlanconfig requires wlan-ng drivers.....so how do i install them keeping in mind the above config that i have already done.....do i need to undo all that???? You don't need wlan-ng. This is a totally different driver package. Where did you get these instructions? It looks like you read a previous thread here that had two different methods of getting wireless up?