So it turns out, Suse on an (old even) laptop is even more fun that it is on a desktop.
BUT, I still cant get my wireless to work!
I have the Encore ENUWI-N3 USB adaptor.
Suse sucessfully detects my USB device, recognize its a Wireless lan network adapter, installs it as such (gives it its driver) and adds my wireless menu under network manager.
(it gives it the rt2x00)
I can enable / disable the USB device from there (its light corroborates that) .
So all in all, suse installs my wireless.
But I CANNOT find any AP when I scan.
Under the “scan” tool (under connec to wireless > A wireless network ect ect) I find no APs.
Adding the SSID of the AP manually is of no help either.
And the command sudo /usr/sbin/iwlist scan
merely gives - “wlan1 Scan completed” and nothing else.
Check ifconfig - not a frame sent/received…
Whats going on here?
What does lsusb -v say about the device and driver?
> Whats going on here?
if you boot from a live cd (or dual boot OS) does the wireless work then?
maybe the laptop’s wireless antenna has become disconnected?
–
DenverD (Linux Counter 282315)
CAVEAT: http://is.gd/bpoMD
posted via NNTP w/TBird 2.0.0.23 | KDE 3.5.7 | openSUSE 10.3
2.6.22.19-0.4-default SMP i686
AMD Athlon 1 GB RAM | GeForce FX 5500 | ASRock K8Upgrade-760GX |
CMedia 9761 AC’97 Audio
Ah yes, I forgot to include that.
I’ll give you the entire output (relevant to the USB card).
______________________-
Bus 001 Device 004: ID 203d:1480
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x203d
idProduct 0x1480
bcdDevice 1.01
iManufacturer 1 Ralink
iProduct 2 802.11 n WLAN
iSerial 3 1.0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 67
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 450mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 7
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 5 1.0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x04 EP 4 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x05 EP 5 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x06 EP 6 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0000
(Bus Powered)
_________________-
Its a USB adapter Denver (eliminates the possibility of it being a DC antenna)
Also, I tried the adapter on my desktop (which dual boots w/ XP) and XP detected the AP fine.
Thanks for pointing me to the first link Caf.
It would seem that suse deceived me - as according to that page (though it seems it has been setup) its not a matter as simple as that.
I find it strange though, that suse would go as far as to identify my device, give it a driver, show me it in ifuf, but then not be able to connect.
I should also add that whereas that page says its not recognized by yast - MINE IS. So this stuff probably really only applies to 11.1
Anywho - I’ll try and get my hands on that RSA_readme file they speak of, then configure the card.
If anything comes up - I shall be certain to make mention.
Gratzi.
It usually pays to get a device that just works. I asked about this some weeks ago:
USB Wireless Device that works OOTB? - openSUSE Forums
I went with this
USB Wireless Device that works OOTB? - openSUSE Forums
Yes it just works
I suppose. I had limited $$ @ the time though.
Well - I’ve already bought it - so I’ll see what I can do with it.
If I’m sucessful, I’ll catalog how I did it.
Thanks caf (and keep up the thread houndage ; p )