danleff

I think jarves has XP already installed and is booting Debian via a boot floppy disk now? If this is the case, is grub or lilo installed as the bootloader?

Why not start with Debian's own Installation manual. ...as well as their own guide on booting using lilo or grub. Another good article on dual booting is located here.

As long as you have enough hard drive space, there is no need to reinstall any OS. How large is your hard drive and is it an ide hard drive? You need to have some free space on the hard drive, or make room for the Mandrake installation. Are you using any partitioning or have any partitioning software currently that you can use? I have six distros on one machine that can boot fine. I use PartitionMagic, as it resizes my partitions withe ease and make it much easier to allocate what space that I need for a new installation. Mandrake's partitioning tool will work fine under most circumstances. What is the layout and space allocation of your current partitions as they now stand?

cbouch35, what did you try already to get it going? There are two possible solutions, the linuxant drivers or ndiswrapper. Remember, you found this post, but it is quite old. Your situation is complicated by this being a pcmcia adapter. But, it still should work. The Linuxant driver installation is somewhat complicated and hindered by the need to have the correct Windows drivers available to load via the http config screen. The other issue is the kernel that comes stock with Mandrake, which does not handle the windows drivers well, unless you use one of the modified Mandrake kernel packages provided by Linuxant to deal with the stack overflow issue. I thnk the original solution posted was using ndiswrapper. So, with the linuxant driver package, at what point did it fail? Did it allow you to install the windows drivers from your installation cd OK?

Looks like fuelinux already has a thread on Linuxquestions.org about this. Try this in Slax. Maybe it is just a permissions issue. As root user in a console, see where the partition is mounted. Type in; df (hit the enter key) See if this outputs where the partition is mounted on. Then cd to that partition; cd /wherethepartitionismountedon Then do; ls Which should list the contents. What does it say? Are your files/directories there?

If either of you have the room on your hard drive, you may want to test SuSE 10 beta 2. Very nice! There are some minor bugs with some hardware detection, but easily solved. A beautiful graphical grub splash screen is included that does away with the previously ugly stock grub screen.

Originally posted by mel: Quote: Use ubuntu version 4.10 to find your OS's. I tried upgrading to version 5.04. That shows you that the latest is not always the best! Quote: Well, everything looked fine,until I booted windows. I don't know if it's just my machine,but with version 5.04,after booting windows, version 5.04 says all the OS's are not valid operating systems and refuses to boot anything. That's what you get for booting Windows! 8) I use Puppy Linux off the cd to recover my distro problems. Isn't it nice to find a good distro that does this recovery stuff for you? I found that the older versions of Mepis are good for this too. The older versions place a nice icon for each partition on the desktop. Fix them all at once! Yep, I mess up all the time. Also, SuSE 10 beta 2's grub has a wonderful graphic splash screen that is not butt ugly. It's now on my main system.

I know nothing about SIMS, but $200.00??? Try giving the gaming folks some more information. What are your system specifications? Do they meet the requirements to run the program? Sounds like a video memory problem to me.

Sorry about the confusion. I should have been more clear. I wanted to know what the cable assignment was (location), which you also answered. Some may not agree, but this is a Dell system with the recovery partition on hda1, so your Windows system is on hda2. The issue as I see it is the designation of the jumpers on the hard drives. These need to be set correctly first, since you have two different makes of hard drives in the system. Consult the Western Digital users manual for the drive in your system. You need to have the Maxtor as the primary drive, as It has the Dell recovery partition there and Windows XP, which I assume was pre-installed on the system. The cable position is ok (upper most pin connection). Your cable assignments look ok, as they should be. But, was the Maxtor set to cable select before you started all this? This is where the documentaion comes in. Two different makes of hard drives sometimes have to be set a certain way for the system bios to see both drives correctly, per the jumpers. Many drives have no jumper set to use the drive as slave. So, there is no jumper used at all. Make sure the Western Digital is set correctly as slave, per the manual. The issue is how were the drives set originally when you installed Fedora? This should be your starting point. Failing this is the issue, try setting both drives as cable select and see what happens. This is often not correct, but in your case may need to be what happens. You have tried too many solutions to tell what grub conf file (menu.lst) is being referenced, but fdisk -l seems to see the drives as Maxtor as primary master and WD as primary slave. I assume Fedora is on hdb1, but what distro of Linux is on hdb3? Unfortunately, I am going on vacation this am and will not be back for a few days, but others, like darkonc should help sort it out.

If your card says DWL-520 only, then it should be the USA model with the atheros chipset. If it says DWL-520+ (note the "+") then it is the overseas model. If the card is not seen with the drivers included in Fedora, then you need a utility like madwifi or ndiswrapper. By all means, try the madwifi drivers, as suggested by talljimbo.

Originally posted by romanticnick4eva: Quote: no it aint i dont know how to edit it so it will work OK, no it aint what? You need to be more specifc. The card is not listed, or you don't have ndiswrapper installed on the system? I will assume that you did not (or were not able to) configure the card during the installation. Many people miss this. Go back to the network tool and click on the "add" button. Choose wireless. Do you get just "other" or does it show your card with some options to install it? If you card model shows, what options do you get? If it offers to install the card without the ndiswrapper option, go ahead and try it. You may only get one option of installing using ndiswrapper. If this is the case, than things will be a little more complcated. You will need your native Windows XP drivers from the wireless card installation cd to install and configure ndiswrapper. It would also be helpful if you give some more information. Is your network set up with WEP or WPA? But let's go one step at a time.

Where is the Western Digital drive located and jumpered for? Master slave Secondary master Secondary slave?

Did you just update the kernel or alsa? If not and this is a fresh installation, you need to add yourself to the audio group. Try this; Go to a console, as root user. Type in; adduser USER_NAME audio So, to add myself to the group audio, I would do; adduser danleff audio Log off and back on again and see if this worked.

Originally posted by iamroot: Quote: Linspire has a bad rep among the general GNU/Linux community cos of it's fervent efforts to emulate Windows, right down to the interface and the security permissions. Linspire doesn't have the root, user standard config. Wow, iamroot, where did you get that idea? Without getting into a debate, Linspire is based on Debian. Did you ever try Linspire? I refer you to this NewsForge article.

If this is the DWL-520 revision b card, then Fedora may already see it as a prism chipset. Did you try using the Network Administration Tool? Go to the Main Menu Button (on the Panel) => System Settings => Network. ...and see if it is listed. If not, do you have the ndiswrapper package installed on your system?

The bad eip value is a hardware issue. It may be a NIC problem, or, as mentioned above, a pci add-on controller issue. The kernel panics, as it is unable to detect or use the piece of hardware correctly using the base kernel modules. Most likely it is an issue with the kernel being able to set the pci address, or PNP is set in the bios. Sometimes there is a conflict with another slot, especially in systems that share resources between slots. You used to see this a lot with pci slots next to isa slots, where the resources were shared. Or, a pci slot next to the agp slot. Moving the pci card to another slot might solve the issue, resolving the apparent conflict.

Probably because Linspire has it's own fine forum. The folks over there are very helpful and there is a broad base of very dedicated users who essentially run the forum. I have been a Linspire insider since the beginning, but have really set my base here with various distros. Some Linux users shun Linspire, because it is a distro that one pays for. But my experience has been that it is worth the price for new Linux users who have little inclination to fuss with there hardware issues. It's not a perfect distro, but has a broad base of supporters and is a fine distro for most regular users.

Ndiswrapper is designed for wireless cards. Is this a nForce chipset motherboard? What make and model? Mandrake 2005 (Limited Edition), Fedora Core 4 or SuSE 9.3 will work fine. It does on my system. The Marvell chipsets are new and require a newer distro to work.

Given the problems that you are having, i am going to assume that you have a corrupted cd disk. What speed did you burn the cd disk at? More than 4X or 8X speed? Did you also check the validity of the download? What media did you burn in, cdrw or cdr? See my article here. These are common problems burning iso images.

Ahhh...Windows 2000 came out way before your video card. Bet that you have to install a Win 2000 driver from within Windows 2000 before putting the new card in.

You don't get disk 4 unless you are a Mandrake Club member. To get an idea of how to burn Linux iso images correctly, see my article here.

Try Mel's solution first. If it does not work, you will need to do a low level format of the hard disk. Then, reformat the hard disk. Do you know what make hard drive that this is?

My goodness! I finally gave a good tip? One of those "hidden" secrets!!!

Look at your other post on this subject of the hard drive issue. So, is the hard drive formatted with a Windows compatible partition? When you wiped the hard drive (if that is what you did), did you format the drive again as fat32? Windows needs a valid fat32 or NTFS partition on the drive, the first partition on the hard drive, for it to do an installation.

Look at the users manual for the laptop and let us know what type (name and if possible the model) of ethernet and modem are on the system. In the case of the modem, it is most likely a "winmodem" designed to work in Windows only. It may or may not work in Linux, depending on the modem.