Connecting to Wireless?? Must be missing something.
SUSE / openSUSEThis Forum is for the discussion of Suse Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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.
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.
Originally posted by barrythai 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.
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.
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 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.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.