I have an odd problem with a wireless PCI card by trendware... I downloaded the driver, compiled it, and load it in modules.conf...

I can get the card up with:
ifconfig eth0 up

and can get a WEP key set with:
iwconfig eth0 key "xxx(whole key)xxx"

and when I review the encryption key with iwconfig eth0--I can see that it has been saved

when I set the essid with:
iwconfig eth0 essid "mingnet"

The ESSID ISN'T listed when I print the settings out with iwconfig eth0 (but the WEP key IS saved, and still prints out)

I have used this card with RH9, so I know that the driver and the card are both Linux compatible. I don't know what is up! If anyone has any ideas, or needs more info from me, please let me know.

Thanks in adv,

Dean

Try, without <>
#iwconfig eth0 essid <something>
#iwconfig eth0 enc <key>
#dhcpcd eth0

Then it shuld be up and running. If not try this to.
#/etc/rc.d/rc.inet1 stop
#/etc/rc.d/rc.inet1 restart

I have done those things--the problem is, some of my settings WON'T save with iwconfig. The WEP key will register as being saved, but I can try inputing the ESSID all day long, and it WILL NOT be in the configuration summary that I print out (but the key that I put in will print out every time)???

Still no progress!?

This is MIND BOGGLING to me--I got the computer to remember the ESSID by toggling the card between Ad-hoc and Managed modes a few times, and then I reset my /etc/rc.d/rc.inet1 script, and got to where I could ping the router (whew!) and then I set the /etc/resolve.conf to my primary DNS server--and bingo, I could get onto the net...

Then I reset the computer to see if I could duplicate the results--an hour and a half later and no luck. I can still get the ESSID to "stick"(by toggling the mode once or twice), but after a while it seems to lapse back into the blank default state. I have manually set the ip to a valid address (192.168.0.74) that is unused by any other computer on my nw, I set the netmask to 255.255.255.0 and the broadcast to 192.168.0.255, and the default route is 192.168.0.1 (which happens to be my router). I have reset these values multiple times, and can't even get the comp to ping the router again!

Am I crazy, or just retarted (ok, don't answer that).

OR is there something that someone knows of that I might have fouled up--or is there some random bug that I might have (like a messed up driver?)

I have recompiled/reinstalled wireless tools, and have recompiled/reinstalled the driver--I don't know what to do next?

thanks

PS I successfully MD5summed my downloaded .iso files--does anyone know how I would go about checking the integrity of the disks that I burned from the .iso files?

So I seem to have found a way around the problem (and have only wasted shipping fees acquiring a different brand of WiFi NIC).

First I found the following thread here and here that detail the fact that the Wireless NIC that I bought has some kinda unpredictable results (btw, the card it a Trendware TEW-223PI). I immediately sent this card back to newegg for a refund.

After re-installing Slack 9.1, I had similar problems w/ my intigrated NIC. Oddly enough, I had no problems with the Trendware or the built in when I ran RH9, but I hate Red Hat--and liked everything about slack other than the fact that I couldn't get my NICs to work. The board is a Soyo sy-k7v dragon plus and it's integrated NIC is a via-rhine chip.

So I put in a D-Link NIC and disabled the onboard--still couldn't get a ping out. However, after reinstalling Slackware with the onboard disabled, and the D-Link installed I finally met sucess.

I ordered a Netgear MA311 Wireless NIC, and put it in this evening. It was as smooth an install as I have ever done--I had the card booting with my essid and WEP key in less than an hour (and I have never successfully configured a wireless card w/ slackware until tonight).

Thanks for everyone's help!