Ixthusdan

At the top of our board is a link called "Easy-Urpmi." Go there. First, select the appropriate version in the drop downs. Next, find mirrors that are close to you geographically. Despite this note, I used to always use ftp.nluug.nl because their bandwidth was better than some mirrors in the US. You will configure 5 sources: Main, contrib, updates, plf-free, and plf-nonfree. At the last, you will get a rather lengthy text to enter into a console. Open a console, su to root. type urpmi.removemedia -a Then copy all the text from the Easy-Urpmi sight and paste it into the console. It will automatically contact each mirror and get the list of rpms on that mirror. I ususally have to hit enter before the last line will go in. Now your urpmi is properly configured, eliminating the need to hunt for anything.

Your kernel sources must match the running kernel. Whether they are "stripped" or not is not relevant. Did you upgrade the kernel without upgrading the sources? The stock kernel is 2.6.17-13mdv, therefore your sources should be kernel-source-stripped-2.6.17-13mdv. If you have configured urpmi properly, then you can simply as root enter in a console urpmi kernel-source If it gives you choices, choose. B)

What is the model/brand of the card? ndiswrapper is best initiated from the command line prior to using the gui. Also, here is a Linux driver called bcm43xx that Mandriva gives preference to, although I have never been able to get it to work with any wireless card. I prefer ndiswrapper. The problem is that if bcm43xx is loaded, it will prevent ndiswrapper from working. It needs to be unloaded and blacklisted so that it won't interfere with ndiswrapper.

First remove all ndiswrapper by urpme ndiswrapper Then, Get this file Unpack with the command tar zxvf ndiswrapper.blah.blah.tar.gz Go into the directory and make su to root and make install Follow the steps you already know to put it into the system. The notes indicate that ndiswrapper was crashing with Broadcom 64 bit drivers. I have used 64 bit drivers that would not work in windows, but worked fine in Linux!

For a 64 bit system, I compile from source. But the latest rpm seems to work just fine for me. After removing bcm43xx and being sure it does not load, modprobing ndiswrapper should have brought the lights on. The reason they did not initially was because bcm43xx is given precedent by the system. Personally, I have never gotten it to work with any wireless device, so I use ndiswrapper. Ndiswrapper acknowledged that the device was identified. The reason it did not activate was because of interference from bcm43xx. Without any other edits, if ndiswrapper sees the device, at that time launch Mandriva Control Center and configure it from there. I recommend going back to the point where you had ndiswrapper loaded and you then removed bcm43xx. So, 1) remove your edits in oeder to start over. 2) Assure that bcm43xx is not loading. 3) Modprobe ndiswrapper (to be sure it is loaded.) 4) Associate ndiswrapper with the windows driver. 5) Open Mandriva Control Center and configure your wireless. I have successfully used ndiswrapper following these steps many times on a vast variety of systems.

Please check in your BIOS and see if you can turn "plug and play" off. To get into the BIOS, at boot time you have to hit a key or combination of keys. Generally, the boot up messages are hidden behind a splash screen. F1, Delete, or Ctrl-Alt-F1 are all possible combinations for getting into your computer's BIOS.

Yes, you must unload blacklist bcmxx or ndiswrapper will not load.

You can also open a console, su to root, and type "nvidia-settings" Make your changes and save them to your xorg file. It is all done in gui.

Your problem is not related to the above because 1) it is an Nvidia card, not ATI and 2) you simply need to utilized the Proprietary Nvidia drivers, as we have suggested to you elsewhere. adamw told you that your pci id was not available at the time of the release, but your card will work fine. Despite it looking similar to you, please do not get confused with what you are dealing with and an ATI problem. Unlike Windows, the "auto configure" functions in a Linux system do not determine whether a device works or not. It simply makes things easier, when it does work. Your video card will work if you follow the steps we have given you. If you have any questions, please do not hesitate to ask them..

A little research prior to your installation would have releived some of you anxiety! :lol: But hind-sight is always 20-20. First, a note about drivers: "Linux" is built almost totally by volunteers. This means that without any big commercial bucks, hardware vendors do not have to cooperate with Linux at making drivers or even offering the sources for thier product. It is this way primarily so that folks like you, who do not know, will get upset and stick with windows. Pretty effective, isn't it? B) Nvidia is absolutely the best graphics manufacturer out there. They have written drivers for Linux almost from the beginning. When using an Nvidia based card (All my cards are Nvidia) simply use the "vesa" driver to get started with a gui. Better yet, go to their sight and download their graphics driver for Linux. At the command line, go to the location where you placed the file and as root type sh NVIDIA-Linux-x86_64-100.14.11.pkg2.run Follow the instructions, answer yes to everything, and startx X by typing startx For Ndiswrapper, it is easier to get started in a gui, although I always do the process at the command line because I can see the results. All of the following is command line and should be done as root. urpmi ndiswrapper modprobe -a modprobe ndiswrapper ndiswrapper -i /location/of/windows/sys/driver At this point you will geet a message which confirms that the driver you have selected will find your hardware. You may even get some lights working. From this point, you can go to the gui in the "Configure my Computer" and finish associate with the access point. this is a lot for a beginner, but each of us here has started exactly like you. We will help you get through it. ;) BTW, I have a similar rig, but I use ethernet.

? You have lost me as to 1) what you have done to your drive, 2) what result you are trying to get, and 3) what you are doing now. I think that you should try to stay on one track and get results before spinning your wheels doing whatever it is you are doing. What did you do that Mandriva won't boot? Also, I think you should understand that these tools are Linux tools and not just Mandriva tools. If every tool mentioned in this thread, whether Windows or Linux, has not worked on yuor drive, then the hardware is at fault. Replace the drive. B)

Some windows programs (Partition Magic) report bad partitions when they are not bad. How do you mean "bad?" If everything is working, they can't be too bad. A not: the last time I had a hard drive report partition errors, it was going out. Did you back up your data?

Open SuSE will work by the method described above. I have done it several times. ;)

Umm.. When it comes to proprietary drivers, it is up to the manufacturer to "settle the differences." For example, Nvidia stuff works marvelously because Nvidia has been writing Linux drivers practically from the beginning. It is an ATI thing, not Linux thing. I thought ATI had gotten up to speed but apparently they have not.

The versions that may be purchased have some software on them that is not on the free versions. However, all of the software is readily available on the internet after configuring your urpmi sources.

When you burn a cd with an .iso ending, you must burn it as an "image" file. Simply copying the file will not do at all. Look at your burning software and be sure you have selected an image type of burn. What software are you using? Nero is a little tricky. When selecting "image" you first only gert Nero image files. But the drop down box offers .iso as a type to burn. After selecting this, you will burn the image to the cd.

On both my brother's machine and my own, I cannot get Doom 3 to run while using a 3D desktop. I must turn of 3D and then the game will launch. It complains about lacking virtual memory when attempting to launch. Any solutions? We both use Nvidia video cards with Nvidia drivers. (GeForce 7300 GS) I have 2G of RAM, 667 MHz.

I think you offered the number on the power supply. Could you just give the model number?

Also, what is your motherboard, or computer brand and model number?

Try booting without the usb drive in place. Also, what specifically happens? Please be specific. What is on the screen when it goes black, or what was immediately on the screen prior to going black?

Could you give some more details about your hardware?

First, try booting with some options that turn off acpi. They are available on the first boot screen. This is the most common problem in installation. As far as I know, the ATI driver issue has been solved for several releases, so there should be no issue with video. Also, be sure your bios is set for "no" on plug and play os. Linux needs to utilize the bios for configuring hardware.

Actually, I used to place all kernels in Mandriva's /boot, but not on a separate partition. The syntax of the lilo/grub file changed, while the specific instructions for each / location had to be reconfigured according to Mandriva's perspective in the system. It worked, but simply making changes in the lilo/grub file was easiest and I did not have to copy the kernels.

When you burned the cd/dvd, did you verify the integrity of the download by checking the md5sum? This should be done prior to burning. A bad download in this type of file means problems during the install. Also, an iso file should be burned at a slower speed, rather than a fast speed, again so that there are very few extrapolation errors when burned. At what point does the installation "go black?" Is it immediate or after a few minutes?

It should, but I would make a copy of the current setup and st wit in an area that can be recalled later. That way, if needed, you can manually make any entries. Personally, I always manually edit either lilo or grub when adding other operating systems.