gracevasup.blogg.se

5 Juni 2022 - 06:42
Current driver d link dwa 160
Allmänt
Current driver d link dwa 160












  1. CURRENT DRIVER D LINK DWA 160 INSTALL
  2. CURRENT DRIVER D LINK DWA 160 DRIVERS
  3. CURRENT DRIVER D LINK DWA 160 SOFTWARE
  4. CURRENT DRIVER D LINK DWA 160 PC
  5. CURRENT DRIVER D LINK DWA 160 DOWNLOAD

The signal strength, however, is not any better than Super G card that the 160 replaced even when normalizing on windows wireless as the source of truth. This is odd because the actual strength is consisitent with what windows shows and the throughput is exceptional, typically 240+mpbs.

It comes with a nice usb base and extenstion cord so you can position it for a clear signal, not worry if its stuffed in back of your pc in a cabinet.Ĭons: The dlink connection wizard shows a lower graph bar signal strength then the windows built in wireless. Like the dlink super g bus card it replaced, it stays connected, I never hear about connectivity problems from my family using the computer connected to it.ĭlink has always seemed to struggle a little with designing PCI cards. I am using it on 5ghz (with a DIR 825 Router). I have great file transfer rates and have not lost a connection with the 3rd party software. Overall Review: The DWA-160 is a solid performer once you get it stable. I found it gave rock solid connection and I was able to make several different different profiles connections which ranged from work, home, family and friends.

I spent some time searching out the software and settled on the Oddyssey Access Client. I found that some 3rd party software do not use the Windows Zero. Many of the Wireless adapter software rely on the Windows Zero software to make the connections. I came to realize it the the Windows Zero software that was causing the instability. I decided to do my own research and found a common factor to the instalibily. They contributed nothing to resolve this issue. Spent several days with level 1 &2 Tech support which had me try several rev. Never knew when the cycle would start but once it did it was difficult to get the connection back.

This driver needs binary firmware images, which are available through the package "ar9170-firmware" but can be used with the "standard" wpa_supplicant (wext-extension).įeedback is highly appreciated as the drivers might be merged to the semi-official "driver:wireless"-repo later.Pros: Works well with DIR-825 once you get the DWA-160 working.Ĭons: Experienced dropped connection after a few minutes to maybe hours. If you want to use WPA with this device, you will need a special wpa_supplicant, I also offer packages version 0.6.8, however the implementation of "otus"-extension is a bit hackish, so I don't know if that will work, feedback would be highly appreciated.Ģ) The new mac80211-based driver "ar9170", kmp-packages available for openSUSE 11.1 and openSUSE Factory, the driver for 11.1 is in the "compat-wireless-kmp-*Kernelflavor*", for openSUSE Factory there is an extra package ar9170-kmp-*Kernelflavor*. In my OBS-Repository you will find two different types of drivers for these otus devices.ġ) The old otus driver "arusb_lnx", kmp-packages for openSUSE 10.3 - 11.1 are available (for openSUSE Factory the driver is included in the kernel). In this case it's also a pitty the OP gave up so early (or I am so late in responding), but for further readers of this post a little hint.

To assist anyone trying to help, HERE is my NIC and HERE is the download page for the drivers. I've been working at this for three days from morning till night trying to resolve the issue, and getting nowhere.Īny and all help would be immensely appreciated. I get the same issue with both 32-bit and 64-bit Suse. These include make, autoconf, and gcc (awk and the other thing that goes with it). I've verified that all of the packages necessary (and some) are installed. The error is very similar in Yast, except it uses a few more words. Installation of the driver failed in the compile phaseĮrror: %post (otusdriver-3.2.)scriptlet failed, exit status 255 Instead of installing, making my NIC work, and everyone lives happily ever after, I get this in the terminal: Where "x" is the driver version (17 in my case). rpm file and let Yast do its thing, or bring up the terminal and type The provided instructions stated to either click the.

I'm trying to install the Atheros Otus driver which I acquired from D-Link's website for my DWA-160 rev.A1 Xtreme N USB wireless NIC. Ok, so I decide to slap OpenSuse on my system, and what should have been an easy switch, turned into a pain in the rawhide.














Current driver d link dwa 160
0 kommentar(er)
Om Mig: