I am a newbie to Linux and have just installed FC4 on a PII 500 machine.

I have a Netgear WG311T card which is not recognized by the OS. I have read many posts and have determined that I need to install the madwifi drivers.

when i perform the ifconfig command I get the typical lo listing and not eth0.


Question 1.: Is there any other method of obtaining these drivers other than cvs since I do not have internet access from this box?

Question 2: Are there any other drivers that will work with this card?

Thanks for your help.

Just ask if you need any other info.

Okay since noone is able to answer my original post, here is something I want to run by you and get opinions if this will work.

Since I am running a dual boot machine with XP and linux I can FTP the wifi file to my server and put the files into directory that is mounted on my LINUX OS.

Once I have the file accessible to my LINUX OS can I then run CVS against the file that I FTP'd.

Not sure if this will work.

Another option I thought of is to obtain CVS for Windows and grab the files using the windows version. And putting the files into a mounted direcotry and go from there.

Does either option sound feasible?

Thanks!!!

Are you sure that MadWiFi is not included in FC4? (I don't know, just asking.)

Surely, there's an rpm out there somewhere.
Ah. Indeed there are many.

http://atrpms.net/dist/fc4/madwifi/
http://madwifi.sourceforge.net/dokuw...#fedora_core_4

Well as I said, I am a newbie and I did actually find this on the web. Just wasn't certain what a RPM actually is. However, I will read up and figure it out.

Thanks for the post I do appreciate it greatly.

A quick (and probably too-condensed) version:

Code author writes in a programming language - C, for example. AKA source code.
Source is run through a compiler to create binaries needed - compiled.
(optional) Package is created to simplify addition and removal of binaries. Examples - RPM, .deb, .tgz,
Binaries are copied to desired or expected locations - installed.

For code to run - be executable - on your machine, it has to be binary - compiled for your architecture. You can download the source code and compile it on your system or get code that's already pre-compiled and packaged for your system type. The RPM list is exactly that.

The bad news is that the person building the RPM might have made certain assumtions about your system that aren't accurate. This can create dependencies or incompatibilities you may not have with compiling from source.

The good news is that using a binary package is usually simpler, faster and less error-prone.

Make sure you pick the RPM that matches the kernel you're using to minimize any conflicts. The command uname -a will list the kernel version if you don't know it.

Good luck.

2Gnu

Thanks for your help and effort in explaining this stuff. This is all starting to make sense.
One day I will be LINUX Genius. HA!


I'll post in the ner future to let ya know how I made out.

Thanks 2Gnu

Well I'm no genius yet, but I did get the drivers installed and the OS now recognizes my card. I can ping my router and my other XP workstation connected to the lan. However, I cannot ping anything outside my lan.

I have security on the router turned off so I don't think it's the wep or wap encryption.


ANY THOUGHTS?

Are you using DHCP to obtain an IP? Did you enter your router IP address as a gateway?

There's a network GUI in FC that makes it pretty simple to enter the network parameters.

If that still doesn't work, post the output of ifconfig and route.

I did use dhcp to get IP and I did not enter the gateway address to the router at least not intentionally.

I did not run the route listing so I will have to post that in another posting. I have to reboot with linux and, well you know the deal.

Here is my ifconfig listing.

ath0 Link encap:Ethernet HWaddr 00:0F:B5:60:2F:90
inet addr:192.168.0.4 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::20f:b5ff:fe60:2f90/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:9948 errors:369 dropped:0 overruns:0 frame:369
TX packets:1278 errors:4 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:199
RX bytes:1320574 (1.2 MiB) TX bytes:182841 (178.5 KiB)
Interrupt:11 Memory:d08c0000-d08d0000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:2591 errors:0 dropped:0 overruns:0 frame:0
TX packets:2591 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1847474 (1.7 MiB) TX bytes:1847474 (1.7 MiB)

Okay 2Gnu here is my route listing

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
169.254.0.0 * 255.255.0.0 U 0 0 0 lo

I have the same card. While I haven't gotten it to connect to the network, my OS does at least recognize it, under the heading of ath0. When I ifconig I don't get an eth0 mode either, I wonder if there's a connection?

Insert the install cd under linux. Do a file search and look for two files. One ends in .inf and in other in .sys. I think it's listed under WINXP drivers or something like that on the CD. In any case, copy these to a folder somewhere on your harddrive. These are the driver files for the card.[/QUOTE]

I'll have a look around the net for a link or two to help you all out then I'll get back with a linux/wg311t walkthru.