iwconfig syas no power so your driver is not configured.

go to yast network wireless
see if your card is listed if it is carry on and step through the configuration.

Reboot if you cannot get the dhcp - knowing a ip address rather than a domain name quickly sorts this problem.

If not go to yast hardware and find your hardware wireless card and chipset.

Then you will need to install with the ndiswrapper program.

install from yast software then read the help file on ndiswrapper how to install the driver.

Come back and tell us how you have got on.

I'm trying to install on 10rc1 several units but yet to get 10 to work but that maybe because I am using low cost
wireless cards that are the latest. Older cards are much easier.

command "make" not found?!?

You'll have to install 'make' and probably also 'gcc'. There should be packages on your installation CDs.

I found a problem with 10rc1 where the router could only be found on the local lan.

If ping 64.179.4.149 is working then :

with a browser check you can see the router over the wireless with a browser using it's ip address eg http://192.168.1.1 see router handbook for it's setup page.

If this works try to got to Linux questions with http://64.179.4.149
if this works and the domain name is not found then it is the problem I found.

Unlike other distro's the configuration of the resident ethernet chip and the wireless card do not allow the dhcp to correctly setup.

I fixed this in yast network by deleting the ethernet adapter and then without rebooting, the dhcp worked properly and the browsers resolved the domain name to the
correct ip.

All these wireless bugs make SuSE not very beginner friendly. A good distro could be made a great distro if more attention was made to wireless automatic configuration.

That would be a bit difficult, considering he's currently trying to install the drivers for his wireless card.

The point is reading from others as well, maybe his drivers are installed.

The point that the ndisdrivers are not shown up in the network -cannot confirm this as
I have yet to get any ndisdriver to work- may mean that the driver is installed.

This leads me to the check with a ping rather than using the browser to see if you are connected to the web. I spent a day on this yesterday installing a driver that was working and finally finding it was the dhcp problem of conflicting hardware and that applies to the Suse distro and not to other distros to my knowledge.

There's no way the card will work _at all_ without the firmware installed (which we know he didn't have installed), and he's using native drivers, so ndiswrapper doesn't come into it.

In post #8, ifconfig doesn't list the interface, and iwconfig has 'channel:0' and 'access point: 00:00:00:00:00:00' for the interface, so the card isn't associating with any access point. It's either a layer 1 or layer 2 problem, and 'ping' will never work.

Dave

I think your firmware is installed as in post 8 as the wireless is connected to eth0.

True you are not connecting to any access point but that does not mean an ap is not there.
In the case you have the wrong driver installed.

The trouble suse has so few drivers installed for wireless compared with Mandrake that has loads.

Perhaps, if you knowthe chipset is which will be listed in YAST hardware and the the Suse version and then I can be of more help.

Is the network adapter listed in YAST network?

http://www.linuxquestions.org/questi...81#post1836281

/me draws circle, bangs head.

The card appears in YAST, fully recognized, but is effectively crippled ATM. I'll install make and gcc tomorrow when I get the chance...

Yes what does it say as a chipset or manufacturer exactly?

The reason is that in the madwifi hunt I found reference to an Intel card having an Atheros chipset and is mis-discribed in the hardware. Have you read the numbers on the chip itself.

Have you checked the list of drivers that are installed in yast - network - configure - advanced options - hardware - select from the list?

You will see only a few drivers I presume non of them matching your card?

If it happens to my latest headache Atheros It will not work. It appears just as you say in hardware. ( A large number of cards have this chipset) as the driver needs to use the madwifi driver.

Anyone got the TP Link Atheros TL WN550G working on SuSE or Mandrake?

I know I'm the biggest moron on earth.

How do I install make and gcc? I couldn't find them in the YaST install/remove program thing...

thanks

Check out both this article as well as this one, one of which I think should be helpful.

As you have discovered, SuSE Personal does not come with make, however it can be added later. -- J.W.

Thanks, I'm trying that now.

Biggest problem is booting between windows and linux to download files/try them/discover I missed one/rinse and repeat.

BTW, I appreciate all the help you guys have given me.

Pulsar

I was following the directions from the second article posted. I downloaded the RPMs onto a windows-linux shared partition I have, then booted into linux. I copied all three RPMs to my desktop in linux (working as root). Opened Konquerer, navigated to the desktop, opened the first RPM as per the directions, and clicked "install with yast".

Yast pops up -- the right pane is blank. So I search for "devel" to try and find the one it just supposedly loaded. OK, it comes up, so I check it and hit accept.

It goes to the installation, but immediately crashes with an error to the effect of "Cannot find file on media" with the options of Abort, Retry, and Ignore. Retry fails, Ignore and Abort stop the installation.

Anybody have any similiar problems?

I'm planning on writing a step-by-step howto for ipw2100 setup when I get this figured out.

Thanks,
Pulsar

p.s. - JW: this isn't you is it?