Opensuse 13.1 wireless is not active

English Network/Internet
1

xxxxx@linux-3f3p:~> su
Password:
linux-3f3p:/home/xxxxx # /sbin/route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
linux-3f3p:/home/xxxxx # hwinfo --wlan
17: PCI 400.0: 0282 WLAN controller
[Created at pci.319]
Unique ID: YVtp.laWSEP5Dyl5
Parent ID: 6NW+.DxIsuPn1vDC
SysFS ID: /devices/pci0000:00/0000:00:1e.0/0000:04:00.0
SysFS BusID: 0000:04:00.0
Hardware Class: network
Model: “D-Link AirPremier DWL-G550 Wireless PCI Adapter”
Vendor: pci 0x168c “Atheros Communications Inc.”
Device: pci 0x0013 “Atheros AR5001X+ Wireless Network Adapter”
SubVendor: pci 0x1186 “D-Link System Inc”
SubDevice: pci 0x3a18 “D-Link AirPremier DWL-G550 Wireless PCI Adapter”
Revision: 0x01
Driver: “ath5k”
Driver Modules: “ath5k”
Device File: wlp4s0
Features: WLAN
Memory Range: 0x90000000-0x9000ffff (rw,non-prefetchable)
IRQ: 21 (no events)
HW Address: 00:17:9a:08:c3:8d
Link detected: no
WLAN channels: 1 2 3 4 5 6 7 8 9 10 11
WLAN frequencies: 2.412 2.417 2.422 2.427 2.432 2.437 2.442 2.447 2.452 2.457 2.462
WLAN encryption modes: WEP40 WEP104 TKIP CCMP
WLAN authentication modes: open sharedkey wpa-psk wpa-eap
Module Alias: “pci:v0000168Cd00000013sv00001186sd00003A18bc02sc00i00”
Driver Info #0:
Driver Status: ath5k is active
Driver Activation Cmd: “modprobe ath5k”
Config Status: cfg=no, avail=yes, need=no, active=unknown
Attached to: #12 (PCI bridge)
linux-3f3p:/home/xxxxx #

what to do ? to activate it?

2

On 2015-08-27 07:16, error4linux wrote:
>
> xxxxx@linux-3f3p:~> su
> Password:
> linux-3f3p:/home/xxxxx # /sbin/route -n

First, two comments:

One, better use “su -” (with a dash), and then you don’t need to type
the sbin path.

Two, that in order to post commands and computer messages on forums like
these you must use code tags. Use the ‘#’ button in the forum editor.

About your question: did you read the sticky posts at the top of this
wireless forum?

–
Cheers / Saludos,

Carlos E. R.

(from 13.1 x86_64 “Bottle” (Minas Tirith))

3

http://s13.postimg.org/lfqscca6b/Capture1.jpg](http://postimg.org/image/lfqscca6b/)

http://s15.postimg.org/j3coaddbb/Capture2.jpg](http://postimg.org/image/j3coaddbb/)http://s9.postimg.org/x5z3q153f/Capture3.jpg](http://postimg.org/image/x5z3q153f/)

4

From what you posted so far, it seems to work.
But the interface is not up, “ifup wlp4s0” should “fix” that, or set the interface to be started at Boot.
Next, you’d need to configure the connection in YaST, by selecting the interface and clicking on “Edit”.

But I’d rather recommend to switch to “User-managed with NetworkManager” in YaST->Network Devices->Network Settings->Global Options, and use your desktop’s networking applet to configure it instead of YaST.
Actually this applet should immediately show available networks after you switch to NetworkManager.

If you already use NetworkManager, switch to “Traditional Method using ifup” and press OK, then switch back. Under some circumstances it can happen that both are active which leads to problems. Explicitly switching should fix that.