danleff

gef4000 posted under Slack Space. This forum is shared between both NTCompatible and LinuxCompatible. Nothing is wrong with this.

I just installed the "ng" version of the madwifi drivers in Mandriva 2006. Yes, the wlanconfig command seems specific to the new ng drivers and works once you set up the system to recognize the new interface. Make sure that you use the directions for the type of madwifi drivers that you are using, either the old series or the new "ng" series. heffo_j's directions are on the money for the ATrpm versions available.

The first question that I have, is it possible for you to upgrade to Fedora Core 4? USB modem support is much better. The second question is could you give a little more information, such as the make and model of the modem? The easiest solution would be to connect via a network (NIC) card to the modem. You can get an inexpensive Linksys or Realtek NIC card, if your system does not already have one, for about $10-15 USD. Fedora should pick one of these up right off and you save yourself a lot of headaches.

This just goes to show you that the newest is not always the best! It apparently was a known issue in earlier kernels and fixed in the kernel-2.6.13-1.1532_FC4 version. Apparently it is not fixed in the newest? Try installing that kernel and see what happens. Reference

The first thing to do, if you know nothing about Linux, is to get comfortable with it. First, I suggest that you peruse the Ubuntu documentation and the support forums. Getting wireless, namely usb wireless going is a task that should be attempted by one who is comfortable with their distro. Expecting someone to write a detailed guide for you is not reasonable, but someone has already done that for the masses at the Ubuntu wiki. Take a look at that how-to article to see what you need to do and why I mention that being comfortable with your distro is important. What I would do, is set up a wired connection first via a NIC card, then go about the task of trying ndiswrapper with the Windows drivers for the card. Also, see a previous thread on the subject located here.

Take a look at this article. Try; make xconfig make all make modules_install make install

-For 128-bit ASCII WEP keys, use 13 ASCII characters –For 128-bit hexadecimal WEP keys, use 26 hexadecimal characters –For 40-bit ASCII WEP keys, use 5 ASCII characters –For 40-bit hexadecimal WEP keys, use 10 hexadecimal characters

Is this the firewire model? I have no experience with this, but you can look up any drive that you are considering to buy and see if it is certified with mandriva as working. The database is located here

Also, try my how-to located here.

You did follow the instructions?; Quote: My repository only holds the x86 platform based -tools packages, so for any other platform you should choose the package builder. This should have built the packages including the tools. I will try this out, as I don't have madwifi built for my Debian install. I'll report back.

Did you try adding the above entry for Windows to the menu.lst file?

Realize that the article post is over one year old. Roob85, what distro and version are you using? Did you download the driver and follow the directions on the ATI site located here?

First, make sure that your wireless cared has an atheros chipset. The DWL-G510 was made using two different chipsets, depending on the revision number on the card. If it is a rev 01 or B card, it should have an atheros chipset. If it is any other, it probably has a Marvell chipset. Wlanconfig should be part of the madwifi packages. Did either of you download 2 packages, one the main package and the other the kmdl (modules) package? Giving a link to where the packages were downloaded would help determine if all the packages and dependency packages are installed on your systems. Take a look at the madwifi wiki, located here. Also, take a look at the installation section, located here

Sorry for ther delayed response, I've been on the road. I think I see the problem. Try the following for the Windows grub entry; title Window XP map (hd2)(hd0) map (hd0)(hd2) makeactive chainloader (hd0)+1 Remember, you reversed the mapping, so all references for the Windows drive should be hd0. Do not use a rootnoverify line. You can test this without editing the grub.conf file, via the grub menu on boot, to see if it works first. Depending on your version of grub, when you get the grub splash screen, try hitting the esc key. If this does not get you into the grub edit mode, hit the "e" key. Once you are in edit mode, you can edit the lines of code by highlighting the entry to change, hit the "e" key. Then edit the line and hit the "enter" key to temp. save the change on that line. Do the same for each line that need editing. Once you are finished, then hit the "b" key to see if the changes result in a good boot. If this works, you can make the changes in the grub.conf file for good.

Originally posted by michiganmark: Quote: Hi, I'm first time Linux user, possible convert, but I can't get 10.0 SUSE Prof. to recognize the DSL or the home network (at least not as near as I can tell). Did you attempt to set up DSL during the installation? If not, did you use yast to try after the install? You need to know if your provider uses dynamic or static IP addressing. I assume that you are connected to the network via a network card (NIC} or is this USB to the DSL modem? Quote: I DID have a problem with disk#4 being unreadable, and so I downloaded a disk 4 .iso and made a new one, which seemed to help it complete the install. ISO images need to be burned at a slow speed. Say 4X, not the full speed of the burner. This is a common issue. Also, did you verify the iso image was downloaded intact by checking the md5sum of the file? Quote: I have 512mb RAM, and it is as slow as it was with windows XP home. I was expecting it to really cruise. I found SuSE to be somewhat slow in general. It has a lot built into it which requires not only enough ram, but also a good processor. what processor is in your system? SuSE is optimised for Pentium or newer AMD processors. If you have an older processor, this can be an issue, as well.

Originally posted by mjolnir: Quote: well, the chainloader idea was a good idea, and, although it didn't work, it did do something different. This time it said "error 21, no existing disc" Which I know isn't true, because if I go into bios and tell it to ignore all the other drives, it will load windows up just fine. as far as "was windows set installed as secondary slave originally", no, it was primary master when I installed it, as, for some reason, windows didn't want to play nice with installing it with my nix drives installed at the same time. So I had just it and the dvd rom installed, changing it to the sec. slave afterwards. ...and there is the problem. When you install Windows, it attempts to always install on the primary master drive. Therefore, the Windows boot.ini file references the Windows startup files on the primary master, where they were when you installed Windows originally. When grub calls the boot.ini file, boot.ini is looking for the startup files for Windows on the primary master. There is a lot of hot debate about this, but you should always install windows on the primary master, then Linux on the other drives, if using multiple drives on a system. You can't switch drive designations without making adjustments. When you tell the bios to ignore the other drives, it forces the Windows drive as primary master, or the only drive in the system. Solution? make the Windows drive primary master and then install linux on the other. Grub will then reference Windows and Linux correctly. If you know how to rescue the Linux system, then you can adjust the grub menu.lst or grub.conf file to designate where youir Linux root filesystem is, without doing a Linux re-install. Or currently as the system is, if you know how to edit grub and/or the boot.ini correctly, you can make some changes to get both to work. Make sure that the jumpers and cables are correct when you make any changes.

Was the secondary slave where XP is installed originally always the secondary slave, or did you move the drive jumper designation? Do you know how to edit the grub file at the login screen? If so, try; title Windows XP rootnoverify (hd3,0) chainloader +1 or; chainloader (hd3,0) +1

What is the bios set to boot from first, the sata drive; or hdd0, which would be the primary master drive? Your sata drive is not the MBR, if there are pata drives in the system and the bios is set to boot the pata (primary master) first. You also seem to have a /boot partition, which leads me to believe that somewhere in the install you told Fedora to make a boot drive, which would hold the grub data. Given the complex nature of the drives in your system, did you let Fedora partition your paata drive for the installation, or use the expert partitioning utility to set the partitions on the drive. This may answer a few things. I don't use logical volumes on my system, but try this. If the bios is set to boot from the primary master (pata drive), change it to the sata drive, save the changes, reboot, and see what happens. However, stop trying to reinstall grub. There was an answer to this question in an earlier post, I will try to find it.

Linspire is a great distro for normal users who want a system (like you seemed to have purchased) that is pre-installed on a retail system. The issue is that you have to see this as a Linux box, not a Windows box. Frank's corner may be of some help, but from what I remember, the development packages are not in the retail version of these boxes that are sold. You need some of these tools to get Wine to work. I suggest that you visit the Linspire forums and do a search on your games, or post a thread. The folks over there are very helpful and can guide you more easily, relative to Linspire. Linspire dabbled with Wine early on, but dumped the project. However, many users have used Wine on these systems effectively. tap into their wisdom. I also don't suggest that you dump Linspire totally for another distro. These boxes are built pre-compiled to use Linspire to detect and run the hardware on your system. Try the Linspire forums first. You purchased a box with Linspire. Try to sort out the issues on the forums before making any drastic changes to the system first. Let us know what you find out.

Assuming that you are using the same source for the files, run the following as root user in a console; rpm --import http://atrpms.net/RPM-GPG-KEY.atrpms This assumes that you have a working internet connection without the wireless. Then try installing the packages.

Quote: I get a sweries of beeps but the icon just stays as the red X. A series of beeps? So this is not the same internal wireless card? Is this a PCMCIA card? If so, post the make, model and revision of the card.

One way to check this is to run the older kernel. If the apps work you know what the issue is. If they do not, then I bet KDE was updated and caused some issues.

Are you using WEP or WPA encription? Also, did you set the essid to what the router is? What wireless card are you using, make and model, as well as revision number? Some cards with different revision numbers have different chipsets. This determines what drivers to use and if ndiswrapper will work with your card.

Look at the thread that you posted on at the via arena site here. Via notes that support is coming in December/January for the A8V-MX in Fedora. Can you wait?

Running modprobe ndiswrapperloads the module manually. Unless you do this manually at each boot, the module does not get loaded. You can insert the module in /etc/modprobe.conf or /etc/modules.conf (depending on what distro that you are using) through the ndiswrapper -m command. However, depending on what distro you are using and how it is set up to load modules, this may or may not work. I bet that is what he is referring to. If you use that command, it is not inserted properly, or into the right conf file to load at boot. I ran into this issue with Fedora and SuSE. I had to write a short script to load the module and the network card settings. I would invoke this when I wanted to bring up the wireless card. I'm just testing out SuSE 10.1 alpha and have run into a couple of issues like this with madwifi for my atheros chip. If you look at the ndiswrapper wiki page for SuSE, located here, you see that there are no instructions for SuSE 10. They must have changed the structure for auto loading modules somewhat. I'll have a look at mine and let you know what I find.