Talk:Mandrake:IPW2200
From Linux 101, The beginner's guide to all things Linux.
I hope I am placing this in the right place. Firstly thank you for this article. After stuffing around for nearly 6 months, this simple article has my Cenbtrino working in an LG LS50a laptop. I had tried ndiswrapper and any other method with no luck.
Partly becuase of all the work I have done I now find that I have a lot of old profiles in the network configuration. I am running Mandrake 10.1 official version.
If I use the control panel method everytime I remove the old eth0, eth1 and so on profiles, they just return. The WIFI is happily running as eth3 which it detirmined itself and I have let it go.
Is there anyway I can clean up all this old stuff and get back to eth0 as the LAN and eth1 and the WIFI ????
Many thanks
Mike
Contents |
[edit] ifup, mandrake 10.1 and net profiles
To fix this you can remove the excess network config files in /etc/sysconfig/network-scripts/. The easiest way to do this is become root (su) and edit each of the files, renaming if necessary. You can use the ifup utility to test the configuration.
I found that while working on a laptop with Mandrake I could not use the ifup tool on the command line to bring up interfaces. It seems that ifup looks for scripts in one place, but the scripts are in another place.
Perhaps the GUI is set to store them (I think) in /etc/sysconfig/network-scripts/ and ifup looks for them in /etc/sysconfig/network/profiles/default/.
So to fix this I had to make a symlink from latter path to the former, and ifup works. The files in question are called something like ifup-eth#.cfg (where # is the 0, 1, 2, 3...) and you can examine them if you like.
One other thing I found was that this file had the incorrect hardware (MAC) address for the machine and I had to fix it manually by seeing what ifconfig listed it as.
Mandrake 10.1 seems to like making lots of network devices, I think it even makes one for a firewire controller.
[edit] Cleaning up
Thanks for that help, but If I clean out the extra network profiles from /etc/sysconfig/network scripts, they just come back!! I noticed in modprobe.conf that it keeps creating aliases for the Centrino of eth3. If I clear them out of modprobe.conf and network-scripts, again they come back sorting themselves out however they want to.
Something else seems to be influencing it???
Mike
[edit] mandrake net profiles
I'm not really sure what to tell you at this point, because that's all I remember and I don't personally use Mandrake 10.1. It may be that it has some legitimate reason for creating those, I'm not sure. What is eth0, eth1 and eth2? Have you tried the Mandrake Users Forums yet? I've found that to be a pretty good resource for all things Mandrake. Does anyone else reading this run Mandrake and know the solution?
[edit] mandrake wireless active
Ok this is a great page well done for all the work. Just want to find out HOW did people get their wireless turned on so that the modprobe will work correctly? I can't seem to find out how to turn on the wireless adaptor so that I can load the module.
Not sure what you mean here. When you have a hardware device plugged into the computer, but no module (or if it is not compiled into the kernel) then the device is not present to the system at all. If it is a USB device, the best that you would see is that the USB system found the device, but it has no driver to attach to it. Effectively, this device is not active, or present to the system.
Therefore, it is important to modprobe the device driver, then you can to begin to use the device. Maybe you mean active as in connected to the network, since you are discussing a network card.
Because it is wireless, there is an important tool to know:
- iwconfig (from wireless-tools package, you can search this if you need it)
And because it's a network device, some other important tools are:
- ifconfig (InterFace config, this should be on your system for sure.)
- a DHCP client (dhcpcd, for example)
For a wireless card, you would want to configure the WEP and ESSID for the network with iwconfig. There is a man page for it, so take advantage of it if you are going to run this at the console.
Then after you have it configured for wireless settings, the dhcp client would be the next thing to run. Then after it completes, if you run ifconfig, hopefully you'll see a configured network.
I don't use mandrake, but I do know it has GUI tools for these settings. So hopefully you can try there before reverting to the console commands I have discussed above. The concepts carry over. Hope this helps, please report back on what your thoughts are.
