Ralink 2860 Wireless Card

Hello, with my Ralink 2860 my wireless device has always been identified as ra0 instead of wlan0 and it worked fine. Well with a recent kernel update, my device got switched to being identified as wlan0, and now I have problems connecting to networks via essid, problems with creating a stable connection, now it seems like my card only wants to connect half the time... What went on? What was wrong with the old driver? I know I can always downgrade to the old kernel, or install the driver from the manufacturer's website. But I'm just wondering why the kernel "upgraded" to a driver that no longer makes my card work.

Ok, I just found a related thread: http://bbs.archlinux.org/viewtopic.php?pid=669653
Last edited by DeeCodeUh (2010-01-11 17:02:09)

Similar Messages

  • HP Pavilion dv6t-7000 - Ralink RT5390 Wireless Upgrade

    Hi,
    I'm looking forward to replace my Wireless card, I have noticed a stamp on my wireless card informing me that I have to replace it with HP SPARE, I have scaned the barcode "670691-001" and I found it's Ralink RT5390 wireless card.. can I replace it with intel 7260HMW wireless card ? if not, what other wireless cards does my device support? Bluetooth 4.0 supported if possible.
    Thank you in advance for your reply
    Best Regards,
    mabusair
    HP Pavilion dv6t-7000 CTO Entertainment Notebook PC - Windows 8.1
    i7-3610QM, 8 GB RAM
    This question was solved.
    View Solution.

    Hi mabusair,
    Welcome to the HP Support Forums, I hope you enjoy your experience! To help you get the most out of the HP Forums I would like to direct your attention to the HP Forums Guide First Time Here? Learn How to Post and More.
    I see that you are looking to replace your Ralink wireless card. Page 52 of the Maintenance and Service Guide will show you the compatible wireless cards the Intel 7260HMW but there are two others with Bluetooth 4.0 support.
    Thank you,
    Please click “Accept as Solution ” if you feel my post solved your issue.
    Click the “Kudos Thumbs Up" on the right to say “Thanks” for helping!
    Thank you,
    BHK6
    I work on behalf of HP

  • Combining bandwidth of two wireless cards

    Hi, I have a mac mini c2d which comes with a built in b/g network. recently ive upgraded to a new N router for which i bought a new llinksys usb key (N Netowrk operating on 5 ghz). the problem is that this connection seems to be cutting in and out, mainly i beleive due to no linksys/apple drivers directly from manufacturer due to whcih i had to use the ralink drivers widely mentioned in forums, but they seem unstable whereafter a while of high bandwidth usage the connection stalls and i have to unplug/replug the usb key. there seems to be no fix for this, and i was wondering if its possible for me to somehow configure the mac to combine the bandwidth of the usb key wireless n and built in wireless adapter (which i currently keep off). this way if my wireless n stalls, while certain high bandwidth processes will stop such as streaming hd content off network, atleast browsing and music will continue making this less of a problem. is this somehow possible?

    another note, i have my original router (linksys wrt 54g with dd wrt) running the G network, which si what my built in wireless card ould connect to, while my new router (a linksys wrt610n) is configured to only run 5 ghz N network (as my research and reviews suggested using one mode results in faster wireless network than using it in multi mode). the new N network is connected to via my linksys wusb600n usb key on mini.

  • Linux compatible chipset wireless card

    Okay,
    I'm sick to death of my Broadcom Corporation Dell Wireless 1390 WLAN Mini-PCI Card (rev 01)
    I'm just curious if there is any company that is looking to cater to the linux market. I'd like my wallet to show my thanks:)
    It's not that ndiswrapper is hard to use but even when done I simply can't get it to work and yes I've searched the forum and gone through 4 or 5 different setups........I'm not asking for help on this because plenty has been offered on this board.
    My question is: Is there a company that is making pci and pcmcia cards that are linux compatible without having to install some compatibility layer (correct term?) like ndiswrapper? A company that is giving the source code to us so we can have true drivers for our product?
    Don't misunderstand this post - I'm not complaining about linux - I just want to support the companies that would like our business.
    Thanks,
    McRae

    arew264 wrote:One thing I have heard is that we shouldn't blame Broadcom for poor driver support because the actual frequencies their cards run on are controlled by the drivers, which means that if they released linux drivers, they could be hacked into letting you access government and police radio frequencies. That would lead to legal problems which is why their are no drivers from Broadcom for linux.
    Unfortunately, that's bulldust, we have every reason to blame Broadcom for their lack of support.
    The current drivers utilise the firmware files from the windows driver. And it's in those firmware files that the frequencies live. So no, Broadcom COULD have released a driver, just like the one being developed. This is also how intel, Ralink, TI and other vendors work. All of which have licenses that forbid modification, thus if someone does hack them, they're doing so illegally, and the respective manufacturers can't be held at fault. Heck, the firmware in the broadcom windows drivers, already falls under an equivalent license, so they wouldn't need to even change that.
    They could even build one like Madwifi, which has a closed source file which is included at compile time that contains the frequencies. Or just not build shit software based wireless cards, and develop proper ones that work more at a hardware level like the rt2500.
    That's not a valid excuse from Broadcom part, not even remotely valid.
    James

  • HP DV7T 6000 USE AN intel 622ANHMW 6200 6200 agn wireless card sps:572509-001?

    Hello,
    My Wi-Fi card only works on 2.4 Ghz. 
    I want to upgrade it to a dual band 2.4Ghz/5 Ghz.
    I have two HP DV7T's 6000 (With PART# LM726AV & PART#LM726AAR).  Will an intel 622ANHMW 6200 6200 agn wireless card sps:572509-001? work in them?
    I have tried other cards on past HP Laptops and sometimes they are locked out and will not work and receive a BIOS error.
    Thanks!  

    Huffer,
    check this out:
    =============================================================================
    http://forum.notebookreview.com/hp-pavilion-notebooks/651517-found-hp-approved-dual-band-wireless-n-...
    In the threads discussing upgrading the Intel Wireless-N 1030 to dual band, I haven't seen this card mentioned, but if I missed it and I'm repeating old news, I apologize. 
    I have a dv7T-6000 I received in February 2012 and I wasn't happy with the built-in wireless card, but the BIOS mods didn't seem very stable either (i.e. you can't save changes to BIOS settings after installing the modded version). I decided to take a look through the BIOS code on my own and was able to locate the FCC ID whitelist, which is where I found this card listed.
    From what I can find, this card is actually sold by HP for some of its business laptops but for whatever reason it's listed in our whitelist. The cards are available from Hong Kong on eBay for 25 bucks by searching for "630813-001". I just received mine today (took about 2 weeks or so) and it installed perfectly, the bluetooth and Wifi is working fine. I don't have a Wireless-N router to test it with yet, but the important part is the BIOS accepted it and the drivers are working. HP Connection Manager also recognizes it, and the wifi button on the keyboard is operable as well. There are drivers for this card actually listed under the dv7-6c00 on the HP support site, although the link only says Ralink b/g/n, but then if you click through, it lists several more Ralink adapters including this one, the a/b/g/n.
    http://www.amazon.com/gp/product/B00AARQ5F2/ref=ox_sc_act_title_1?ie=UTF8&smid=A2KPDAFXIXUTZL
    ===========================================================================
    I am going to try it.

  • Wireless card not "on" ?

    Hello,
    So far this forum has been good to me, so I'm hoping that someone might be able to help me out with another problem I've recently encountered.
    I am currently trying to set up my Wireless card which is a Belkin F5D7000 card that uses the rt2500 chipset (which there are drivers for through Ralink) and though I have been able to install the drivers alright, I didn't notice until recently that the lights on the back of the card are out and the card doesn't seem to be "active" at all.
    Does anyone have any suggestions as to what may be causing this to happen?  The card does show up on lspci, but only as "Network controller: unknown device" (although I know that it is the card because of the identification codes).
    Thanks!
    -Locri

    What a co-incidence, I installed Belkin wlan on my Arch/XP dual-boot system a few days ago!....
    I'm running the Windows drivers on Arch using ndiswrapper... have you got this bit working yet? You need the rt2500 drivers which you can download or you can find them on your windows installation in program files/belkin.... (you need the .inf and .sys files)
    Another issue I've had is I can't get the wlan working on linux with WEP encryption enabled but it works ok on XP. I'm using mac-address locking for security at moment.
    If you can be more specific about what your having a problem with I'll try to help (but a bit later when I get back to my home PC!)
    - Cheers, Renners

  • Wireless Card PC54G

    I have to wirelless card's pc54g in my two computers, and in windows's one i want to give a try on Windows XP 64 Bits, cause now msi provide almost all drivers for my board (MSI Neo 2 Platinum), but i'm still missing the driver for my wireless card. So the question is: when msi will provide us the driver and the software (WlanUtility) for Windows 64 bits.. thanks in advance

    Thank you all. I've got the driver from
    http://files.aoaforums.com/index.php?dir=224 - The Topic (You have to login/register first)
    http://files.aoaforums.com/code.php?file=2130  - The Driver (You have to login/regiter first)
    is a nice forum for the 64 bits world.
    Dr Stu, the chipset is  Ralink RT2500, i know it cause i use ndiswrapper in Linux to use the card, and with the rt2500.sys  driver.
    Dream_True thanks, but the site didn't work for me.
    Assaf thanks for the faster response.
    One more question, if you don't care, there is a WlanUtility version for Windows 64 Bits?
    thanks in advance

  • 3rd party PCI Wireless cards

    OK, so I've decided to finally install broadband at home.
    I've had an Airport Express (AE) for several months to use when traveling, etc.
    I have a PowerBook with an Airport Extreme card in it and I use its wireless capability all the time.
    My older G4 tower (Digital Audio) does NOT have a wireless card.
    I want to install a wireless card in the G4 tower, since I suspect that will be the easiest way to get both of my computers online. I know I could buy a wired router instead, but...
    Anyways, my G4 tower would need the old original Airport card, which costs way more than the new Airport Extreme cards. So then, like my title says...
    Are there any known issues with using a 3rd party PCI Wireless card?
    For instance, Belkin's F5D7001.
    I thought I saw somewhere that Belkin supports OS X, but some people had problems in Tiger. Others may have had problems with various wireless encryption methods.
    Am I better off just biting the bullet and finding an old Airport card for $100?
    Sorry if this topic has been covered, I tried a search but didn't get much info on this particular topic.
    I am running Panther on both my machines.
    Thanks, folks!

    I am using a Belkin F5D7000 in a AGP G4 Tower. The chipset is by Ralink. Free OS X version drivers are available here:
    http://www.ralinktech.com/supp-1.htm
    While not as elegant as Airport software, of course, the driver and card work excellent.
    If you can find a wireless PCI card using the original Broadcom chip sets, just like the Airport card, then it will be recognized as an Airport card and use the Apple software. These are hard to find now however.
    Here is an excellent article on what you are trying to do:
    http://homepage.mac.com/techedgeezine/2005_0217-54g-inyourmac1.htm

  • G62 Notebook wireless card replacement?

    Hi all,
    I've got a HP G62-18sa notebook with the standard RT3090 wifi+bluetooth combo card in and I was wondering if I can replace it at all? I've been looking at this card http://is.gd/nNjsK8
    Reason I'm asking is the RT3090 card has very, VERY bad support for Linux and I'm looking to replace it. If the above card won't fit can anyone suggest ones that might fit and work under Linux?
    Many thanks.
    This question was solved.
    View Solution.

    Hi, 
    There are 2 compatible wifi/bth cards for your laptop, the Ralink and a Broadcom 4313. I would suggest to disable the whitelist (list of the compatible components) in the BIOS and after that you may use the Intel 6230 combo card (any wireless card you want) without problems..
    http://forums.mydigitallife.info/threads/20223-Remove-whitelist-check-add-ID-s-to-break-hardware-res...
    I have disabled the whitelist myself and upgraded the wireless card to an Intel Ultimate-N 6300 450Mbps. It's not the best solution but works. I also use linux and Intel wireless cards have the best support, like HP printers..
    Dv6-7000 /Full HD/Core i5-3360M/GF 650M/Corsair 8GB/Intel 7260AC/Samsung Pro 256GB
    Testing - HP 15-p000
    HP Touchpad provided by HP
    Currently on Debian Wheeze
    *Please, help other users with the same issue by marking your solved topics as "Accept as Solution"*

  • T23 wireless card

    Hi all,
    I will be receiving my new (old) T23 from ebay next week, but the laptop did not have built in antennas or a pci wireless card originally. Since I don't want to retrofit new antennas (which won't work nearly as well as the ones with built in ones), I will be using a wireless card instead. Any thoughts on which are the best? The card must support WPA2 (with 802.11x authentication) and preferably work with Linux out of the box. Thanks!
    My Thinkpads: T42 (GPU failure), T60, W530
    W530: Windows 7 Pro | i7-3720qm | FHD screen | 256gb Samsung 840 Pro SSD | 500GB Ultrabay HDD | 16gb Crucial RAM | Nvidia K1000m
    Solved!
    Go to Solution.

    If I understand your question correctly, you're looking for a PCMCIA wireless card.
    Anything Ralink will work well in Linux, been there and done that.
    Cheers,
    George
    In daily use: R60F, R500F, T61, T410
    Collecting dust: T60
    Enjoying retirement: A31p, T42p,
    Non-ThinkPads: Panasonic CF-31 & CF-52, HP 8760W
    Starting Thursday, 08/14/2014 I'll be away from the forums until further notice. Please do NOT send private messages since I won't be able to read them. Thank you.

  • Wireless card hardware failure or something else?

    I've been using Arch quite merrily on my desktop for 1.5 years, but just recently my wireless card failed to work correctly after a reboot.
    Here is the output lspci shows for the card:
    04:00.0 Network controller: Ralink corp. RT3090 Wireless 802.11n 1T/1R PCIe
    Subsystem: Ralink corp. RT3090 Wireless 802.11n 1T/1R PCIe
    Flags: bus master, fast devsel, latency 0, IRQ 19
    Memory at f7d00000 (32-bit, non-prefetchable) [size=64K]
    Capabilities: [40] Power Management version 3
    Capabilities: [50] MSI: Enable- Count=1/32 Maskable- 64bit+
    Capabilities: [70] Express Endpoint, MSI 00
    Capabilities: [100] Advanced Error Reporting
    Capabilities: [140] Device Serial Number 00-00-4d-1e-fb-2a-02-48
    Kernel driver in use: rt2800pci
    Kernel modules: rt2800pci
    Here is the output of netcfg when the card fails to work:
    :: home2 up Successfully initialized wpa_supplicant
    Could not set interface wlan0 flags (UP): Input/output error
    nl80211: Could not set interface 'wlan0' UP
    Could not set interface wlan0 flags (UP): Input/output error
    WEXT: Could not set interface 'wlan0' UP
    wlan0: Failed to initialize driver interface
    wpa_supplicant did not start, possible configuration error
    [fail]
    (ip and ifconfig similarly fail to set the card up)
    And here is a relevant section of dmesg output:
    [ 26.981666] ieee80211 phy0: rt2x00lib_request_firmware: Info - Loading firmware file 'rt2860.bin'
    [ 26.989624] ieee80211 phy0: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.34
    [ 28.336325] ieee80211 phy0: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x00000068]
    [ 29.670269] ieee80211 phy0: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x00000068]
    [ 29.670322] ieee80211 phy0: rt2800pci_set_device_state: Error - Device failed to enter state 4 (-5)
    [ 31.017556] ieee80211 phy0: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x00000068]
    [ 32.351500] ieee80211 phy0: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x00000068]
    [ 32.351553] ieee80211 phy0: rt2800pci_set_device_state: Error - Device failed to enter state 4 (-5)
    [ 127.605994] ieee80211 phy1: rt2x00_set_rt: Info - RT chipset 3090, rev 3213 detected
    [ 127.609564] ieee80211 phy1: rt2x00_set_rf: Info - RF chipset 0005 detected
    [ 127.609646] ieee80211 phy1: Selected rate control algorithm 'minstrel_ht'
    [ 133.882799] ieee80211 phy1: rt2x00lib_request_firmware: Info - Loading firmware file 'rt2860.bin'
    [ 133.882829] ieee80211 phy1: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.34
    [ 135.228923] ieee80211 phy1: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x00000068]
    [ 136.562879] ieee80211 phy1: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x00000068]
    [ 136.564000] ieee80211 phy1: rt2800pci_set_device_state: Error - Device failed to enter state 4 (-5)
    [ 137.913502] ieee80211 phy1: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x00000068]
    [ 139.247449] ieee80211 phy1: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x00000068]
    [ 139.248509] ieee80211 phy1: rt2800pci_set_device_state: Error - Device failed to enter state 4 (-5)
    [ 145.739959] fglrx_pci 0000:01:00.0: irq 47 for MSI/MSI-X
    [ 145.740550] <6>[fglrx] Firegl kernel thread PID: 480
    [ 145.740690] <6>[fglrx] Firegl kernel thread PID: 481
    [ 145.740889] <6>[fglrx] Firegl kernel thread PID: 482
    [ 145.740970] <6>[fglrx] IRQ 47 Enabled
    [ 145.750661] <6>[fglrx] Reserved FB block: Shared offset:0, size:1000000
    [ 145.750663] <6>[fglrx] Reserved FB block: Unshared offset:f878000, size:4000
    [ 145.750664] <6>[fglrx] Reserved FB block: Unshared offset:f87c000, size:484000
    [ 145.750665] <6>[fglrx] Reserved FB block: Unshared offset:7ffef000, size:11000
    [ 173.163088] ieee80211 phy1: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x00000068]
    [ 174.497033] ieee80211 phy1: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x00000068]
    [ 174.497038] ieee80211 phy1: rt2800pci_set_device_state: Error - Device failed to enter state 4 (-5)
    [ 327.003969] ieee80211 phy2: rt2x00_set_rt: Info - RT chipset 3090, rev 3213 detected
    [ 327.007543] ieee80211 phy2: rt2x00_set_rf: Info - RF chipset 0005 detected
    [ 327.007618] ieee80211 phy2: Selected rate control algorithm 'minstrel_ht'
    [ 335.902246] ieee80211 phy2: rt2x00lib_request_firmware: Info - Loading firmware file 'rt2860.bin'
    [ 335.902269] ieee80211 phy2: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.34
    [ 337.248728] ieee80211 phy2: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x00000068]
    [ 338.582670] ieee80211 phy2: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x00000068]
    [ 338.582676] ieee80211 phy2: rt2800pci_set_device_state: Error - Device failed to enter state 4 (-5)
    [ 339.929962] ieee80211 phy2: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x00000068]
    [ 341.263914] ieee80211 phy2: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x00000068]
    [ 341.263920] ieee80211 phy2: rt2800pci_set_device_state: Error - Device failed to enter state 4 (-5)
    [ 621.399725] ieee80211 phy2: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x00000068]
    [ 622.733664] ieee80211 phy2: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x00000068]
    [ 622.733670] ieee80211 phy2: rt2800pci_set_device_state: Error - Device failed to enter state 4 (-5)
    [ 624.080967] ieee80211 phy2: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x00000068]
    [ 625.414895] ieee80211 phy2: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x00000068]
    [ 625.414901] ieee80211 phy2: rt2800pci_set_device_state: Error - Device failed to enter state 4 (-5)
    [ 703.834386] ieee80211 phy2: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x00000068]
    [ 705.168333] ieee80211 phy2: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x00000068]
    [ 705.168339] ieee80211 phy2: rt2800pci_set_device_state: Error - Device failed to enter state 4 (-5)
    [ 712.758502] ieee80211 phy2: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x00000068]
    [ 714.092443] ieee80211 phy2: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x00000068]
    [ 714.092449] ieee80211 phy2: rt2800pci_set_device_state: Error - Device failed to enter state 4 (-5)
    [ 739.097308] ieee80211 phy2: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x00000068]
    [ 740.431256] ieee80211 phy2: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x00000068]
    [ 740.431263] ieee80211 phy2: rt2800pci_set_device_state: Error - Device failed to enter state 4 (-5)
    [ 835.981975] ieee80211 phy2: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x00000068]
    [ 837.315927] ieee80211 phy2: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x00000068]
    [ 837.315933] ieee80211 phy2: rt2800pci_set_device_state: Error - Device failed to enter state 4 (-5)
    (The "rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy" messages appear when I try to use the card with netcfg or ip or whatever.)
    If you want to see the earlier bits of my dmesg output, here is a complete log: http://sprunge.us/gWOJ. It's from a different boot, but the error messages at the end are the same.
    Anyway, when this first happened, I googled around after the errors in hope of finding someone else with the same problem (not much luck there), and also looked up my wireless card in the wiki. I ended up trying out the rt3090-dkms driver from the AUR as suggested here (and yes, I followed all the directions). The rt3090 driver actually allowed me to set the card up manually, and I could send and receive pings, but if I tried to use the connection for something more interesting like loading a webpage, it caused the whole system to crash.
    After a while of messing around with this stuff, I found out that occasionally the card works perfectly fine after a reboot (using the standard rt2800 drivers -- I uninstalled the rt3090 one). I can't find anything that's particularly different from one reboot to the next, but the card seems to work after about 35% of reboots. The irregularity of it all has me wondering if it's a hardware problem. Is there an easy way to know if it's a hardware problem or not? I'm pretty much stuck, so any insights on this issue are greatly appreciated

    Here is some module info.
    >$ modinfo rt2800pci
    filename: /lib/modules/3.16.1-1-ARCH/kernel/drivers/net/wireless/rt2x00/rt2800pci.ko.gz
    license: GPL
    firmware: rt2860.bin
    description: Ralink RT2800 PCI & PCMCIA Wireless LAN driver.
    version: 2.3.0
    author: http://rt2x00.serialmonkey.com
    srcversion: F8D3E83728CFFB1CC77557E
    alias: pci:v00001814d0000539Fsv*sd*bc*sc*i*
    alias: pci:v00001814d0000539Bsv*sd*bc*sc*i*
    alias: pci:v00001814d0000539Asv*sd*bc*sc*i*
    alias: pci:v00001814d00005392sv*sd*bc*sc*i*
    alias: pci:v00001814d00005390sv*sd*bc*sc*i*
    alias: pci:v00001814d00005362sv*sd*bc*sc*i*
    alias: pci:v00001814d00005360sv*sd*bc*sc*i*
    alias: pci:v00001814d0000359Fsv*sd*bc*sc*i*
    alias: pci:v00001814d00003593sv*sd*bc*sc*i*
    alias: pci:v00001814d00003592sv*sd*bc*sc*i*
    alias: pci:v00001814d00003562sv*sd*bc*sc*i*
    alias: pci:v00001814d00003062sv*sd*bc*sc*i*
    alias: pci:v00001814d00003060sv*sd*bc*sc*i*
    alias: pci:v00001432d00007722sv*sd*bc*sc*i*
    alias: pci:v00001432d00007711sv*sd*bc*sc*i*
    alias: pci:v00001814d00003390sv*sd*bc*sc*i*
    alias: pci:v00001814d00003290sv*sd*bc*sc*i*
    alias: pci:v00001A3Bd00001059sv*sd*bc*sc*i*
    alias: pci:v00001462d0000891Asv*sd*bc*sc*i*
    alias: pci:v00001432d00007768sv*sd*bc*sc*i*
    alias: pci:v00001432d00007758sv*sd*bc*sc*i*
    alias: pci:v00001432d00007748sv*sd*bc*sc*i*
    alias: pci:v00001432d00007738sv*sd*bc*sc*i*
    alias: pci:v00001432d00007728sv*sd*bc*sc*i*
    alias: pci:v00001432d00007727sv*sd*bc*sc*i*
    alias: pci:v00001432d00007708sv*sd*bc*sc*i*
    alias: pci:v00001814d00003092sv*sd*bc*sc*i*
    alias: pci:v00001814d00003091sv*sd*bc*sc*i*
    alias: pci:v00001814d00003090sv*sd*bc*sc*i*
    alias: pci:v00001814d00000781sv*sd*bc*sc*i*
    alias: pci:v00001814d00000701sv*sd*bc*sc*i*
    alias: pci:v00001814d00000681sv*sd*bc*sc*i*
    alias: pci:v00001814d00000601sv*sd*bc*sc*i*
    depends: rt2x00lib,rt2800lib,rt2800mmio,rt2x00mmio,rt2x00pci,eeprom_93cx6
    intree: Y
    vermagic: 3.16.1-1-ARCH SMP preempt mod_unload modversions
    parm: nohwcrypt:Disable hardware encryption. (bool)
    Also possibly relevant: at the same time my wireless card starting giving me issues, my SD card reader module stopped loading. It seems the driver was renamed from rt5139 to rtsx_usb_sdmmc in Linux 3.16. I now have to load it manually on boot. I doubt the problem is directly related, but maybe it is indicative of a general module issue?
    >$ lsusb -v
    Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
    Device Descriptor:
    bLength 18
    bDescriptorType 1
    bcdUSB 2.00
    bDeviceClass 255 Vendor Specific Class
    bDeviceSubClass 255 Vendor Specific Subclass
    bDeviceProtocol 255 Vendor Specific Protocol
    bMaxPacketSize0 64
    idVendor 0x0bda Realtek Semiconductor Corp.
    idProduct 0x0129 RTS5129 Card Reader Controller
    bcdDevice 39.60
    iManufacturer 1 Generic
    iProduct 2 USB2.0-CRW
    iSerial 3 20100201396000000
    bNumConfigurations 1
    Configuration Descriptor:
    bLength 9
    bDescriptorType 2
    wTotalLength 39
    bNumInterfaces 1
    bConfigurationValue 1
    iConfiguration 4 CARD READER
    bmAttributes 0xa0
    (Bus Powered)
    Remote Wakeup
    MaxPower 500mA
    Interface Descriptor:
    bLength 9
    bDescriptorType 4
    bInterfaceNumber 0
    bAlternateSetting 0
    bNumEndpoints 3
    bInterfaceClass 255 Vendor Specific Class
    bInterfaceSubClass 6
    bInterfaceProtocol 80
    iInterface 5 Bulk-In, Bulk-Out, Interface
    Endpoint Descriptor:
    bLength 7
    bDescriptorType 5
    bEndpointAddress 0x01 EP 1 OUT
    bmAttributes 2
    Transfer Type Bulk
    Synch Type None
    Usage Type Data
    wMaxPacketSize 0x0200 1x 512 bytes
    bInterval 0
    Endpoint Descriptor:
    bLength 7
    bDescriptorType 5
    bEndpointAddress 0x82 EP 2 IN
    bmAttributes 2
    Transfer Type Bulk
    Synch Type None
    Usage Type Data
    wMaxPacketSize 0x0200 1x 512 bytes
    bInterval 0
    Endpoint Descriptor:
    bLength 7
    bDescriptorType 5
    bEndpointAddress 0x83 EP 3 IN
    bmAttributes 3
    Transfer Type Interrupt
    Synch Type None
    Usage Type Data
    wMaxPacketSize 0x0003 1x 3 bytes
    bInterval 10
    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)

  • Wireless-Card doesn't not work with WPA/WPA2 but with WEP [Solved]

    Hello I have a MacBook (late 2007) with a wireless-card from Broadcam, the card works with WEP and the classic configuration over rc.conf very well. But I can't get the card running with WPA and the net network-profiles.
    Here is the link to the driver - http://www.broadcom.com/support/802.11/linux_sta.php
    eth2 = wireless-card
    eth1 = firewireanything
    eth0 = wired-card
    rc.conf
    # /etc/rc.conf - Main Configuration for Arch Linux
    # LOCALIZATION
    # LOCALE: available languages can be listed with the 'locale -a' command
    # HARDWARECLOCK: set to "UTC" or "localtime"
    # USEDIRECTISA: use direct I/O requests instead of /dev/rtc for hwclock
    # TIMEZONE: timezones are found in /usr/share/zoneinfo
    # KEYMAP: keymaps are found in /usr/share/kbd/keymaps
    # CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
    # CONSOLEMAP: found in /usr/share/kbd/consoletrans
    # USECOLOR: use ANSI color sequences in startup messages
    LOCALE="en_US.utf8"
    HARDWARECLOCK="UTC"
    USEDIRECTISA="no"
    TIMEZONE="Europe/Berlin"
    KEYMAP="us"
    CONSOLEFONT=
    CONSOLEMAP=
    USECOLOR="yes"
    # HARDWARE
    # MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
    # MOD_BLACKLIST: Prevent udev from loading these modules
    # MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
    # NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
    MOD_AUTOLOAD="yes"
    #MOD_BLACKLIST=() #deprecated
    #MODULES=(sky2 snd-mixer-oss snd-pcm-oss snd-hwdep snd-page-alloc snd-pcm snd-timer snd snd-hda-intel soundcore)
    # Scan for LVM volume groups at startup, required if you use LVM
    USELVM="no"
    # NETWORKING
    # HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
    HOSTNAME="macbook"
    # Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
    # Interfaces to start at boot-up (in this order)
    # Declare each interface then list in INTERFACES
    # - prefix an entry in INTERFACES with a ! to disable it
    # - no hyphens in your interface names - Bash doesn't like it
    # DHCP: Set your interface to "dhcp" (eth0="dhcp")
    # Wireless: See network profiles below
    eth0="eth0 192.168.1.220 netmask 255.255.255.0 broadcast 192.168.1.255"
    INTERFACES=(!eth0 !eth1 eth2)
    # Routes to start at boot-up (in this order)
    # Declare each route then list in ROUTES
    # - prefix an entry in ROUTES with a ! to disable it
    gateway="default gw 192.168.1.1"
    ROUTES=(!gateway)
    # Enable these network profiles at boot-up. These are only useful
    # if you happen to need multiple network configurations (ie, laptop users)
    # - set to 'menu' to present a menu during boot-up (dialog package required)
    # - prefix an entry with a ! to disable it
    # Network profiles are found in /etc/network.d
    # This now requires the netcfg package
    NETWORKS=(wireless)
    # DAEMONS
    # Daemons to start at boot-up (in this order)
    # - prefix a daemon with a ! to disable it
    # - prefix a daemon with a @ to start it up in the background
    DAEMONS=(syslog-ng network net-profiles netfs alsa crond portmap fam hal)
    /etc/network.d/wireless
    CONNECTION="wireless"
    INTERFACE=eth2
    HOSTNAME=macbook
    IP="static"
    IFOPTS="192.168.1.225 netmask 255.255.255.0 broadcast 192.168.1.255"
    GATEWAY=192.168.1.1
    DNS1=192.168.1.1
    # Wireless Settings (optional)
    ESSID=3Com
    #KEY=
    IWOPTS="mode managed essid $ESSID channel 11"
    #WIFI_INTERFACE=wlan0 # use this if you have a special wireless interface
    # that is linked to the real $INTERFACE
    #WIFI_WAIT=5 # seconds to wait for the wireless card to
    # associate before bringing the interface up
    USEWPA="yes" # start wpa_supplicant with the profile
    WPAOPTS="" # use "" for normal operation or specify additional
    # options (eg, "-D ipw")
    # see /etc/wpa_supplicant.conf for configuration
    Can I set here the WPA/WPA2-Key also? Why here ESSID? Do I need still a configuration in wpa_supplicant.conf?
    Thats very confusing and not explained.
    WPAOPTS? Do I need to add something like "-D wext"?
    /etc/wpa_supplicant.conf
    # This is a network block that connects to any unsecured access point.
    # We give it a low priority so any defined blocks are preferred.
    ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=wheel
    network={
    key_mgmt=NONE
    priority=-9999999
    network={
    ssid="3Com"
    proto=WPA
    key_mgmt=WPA-PSK
    pairwise=CCMP TKIP
    group=CCMP TKIP
    psk="topsecret"
    priority=5
    # WPA2
    # proto=WPA RSN
    I need help. Please
    Last edited by hoschi (2009-01-04 20:21:58)

    fwojciec wrote:If this info is not in the wiki it might be worth it to add it -- it's all detailed in /etc/network.d/examples/complete.example though.
    Thats the reason why I was so confused.
    My new and well working configuration:
    # /etc/rc.conf - Main Configuration for Arch Linux
    # LOCALIZATION
    # LOCALE: available languages can be listed with the 'locale -a' command
    # HARDWARECLOCK: set to "UTC" or "localtime"
    # USEDIRECTISA: use direct I/O requests instead of /dev/rtc for hwclock
    # TIMEZONE: timezones are found in /usr/share/zoneinfo
    # KEYMAP: keymaps are found in /usr/share/kbd/keymaps
    # CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
    # CONSOLEMAP: found in /usr/share/kbd/consoletrans
    # USECOLOR: use ANSI color sequences in startup messages
    LOCALE="en_US.utf8"
    HARDWARECLOCK="UTC"
    USEDIRECTISA="no"
    TIMEZONE="Europe/Berlin"
    KEYMAP="us"
    CONSOLEFONT=
    CONSOLEMAP=
    USECOLOR="yes"
    # HARDWARE
    # MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
    # MOD_BLACKLIST: Prevent udev from loading these modules
    # MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
    # NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
    MOD_AUTOLOAD="yes"
    #MOD_BLACKLIST=() #deprecated
    #MODULES=(sky2 snd-mixer-oss snd-pcm-oss snd-hwdep snd-page-alloc snd-pcm snd-timer snd snd-hda-intel soundcore)
    # Scan for LVM volume groups at startup, required if you use LVM
    USELVM="no"
    # NETWORKING
    # HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
    HOSTNAME="macbook"
    # Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
    # Interfaces to start at boot-up (in this order)
    # Declare each interface then list in INTERFACES
    # - prefix an entry in INTERFACES with a ! to disable it
    # - no hyphens in your interface names - Bash doesn't like it
    # DHCP: Set your interface to "dhcp" (eth0="dhcp")
    # Wireless: See network profiles below
    eth0="eth0 192.168.1.220 netmask 255.255.255.0 broadcast 192.168.1.255"
    INTERFACES=(!eth0 !eth1 !eth2)
    # Routes to start at boot-up (in this order)
    # Declare each route then list in ROUTES
    # - prefix an entry in ROUTES with a ! to disable it
    gateway="default gw 192.168.1.1"
    ROUTES=(!gateway)
    # Enable these network profiles at boot-up. These are only useful
    # if you happen to need multiple network configurations (ie, laptop users)
    # - set to 'menu' to present a menu during boot-up (dialog package required)
    # - prefix an entry with a ! to disable it
    # Network profiles are found in /etc/network.d
    # This now requires the netcfg package
    NETWORKS=(3com)
    # DAEMONS
    # Daemons to start at boot-up (in this order)
    # - prefix a daemon with a ! to disable it
    # - prefix a daemon with a @ to start it up in the background
    DAEMONS=(syslog-ng network net-profiles netfs alsa crond portmap fam hal)
    CONNECTION="wireless"
    DESCRIPTION="Very verbose complete wireless example"
    INTERFACE=eth2
    HOSTNAME=macbook
    # Interface Settings (use IP="dhcp" for DHCP)
    IP="static"
    IFOPTS="192.168.1.225 netmask 255.255.255.0 broadcast 192.168.1.255"
    GATEWAY=192.168.1.1
    # DNS Settings (optional)
    DOMAIN=localdomain
    DNS1=192.168.1.1
    DNS2=
    SEARCH=
    # Standard Wireless Settings
    ESSID=3Com
    SECURITY=wpa-config # One of wep, wpa, wpa-config, none
    KEY=""
    # Scans to see if network is available before connecting (reccomended)
    SCAN="YES"
    # Time to wait to connect to a network. Default 15.
    TIMEOUT=10
    # Pass *custom* options to iwconfig. Usually not needed (optional)
    IWOPTS="mode managed essid $ESSID channel 6 key restricted $KEY"
    # Any extra arguments for wpa_supplicant
    WPA_OPTS=
    # For SECURITY='wpa-config' only - filename of a wpa-supplicant config
    WPA_CONF=/etc/wpa_supplicant.conf
    # This is a network block that connects to any unsecured access point.
    # We give it a low priority so any defined blocks are preferred.
    ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=wheel
    network={
    key_mgmt=NONE
    priority=-9999999
    network={
    ssid="Linksys"
    proto=WPA RSN
    key_mgmt=WPA-PSK
    pairwise=CCMP TKIP
    group=CCMP TKIP
    psk="areulookingatmybreasts"
    priority=5
    network={
    ssid="3Com"
    proto=WPA
    key_mgmt=WPA-PSK
    pairwise=CCMP TKIP
    group=CCMP TKIP
    psk="nomam"
    priority=5
    # WPA2
    # proto=WPA RSN
    There are also profiles for the Linksys-Router and for wired cable.
    Thanks for the help!
    Last edited by hoschi (2009-01-04 20:21:23)

  • PCI-e wireless card causes lock ups Z87 MPower MAX

    I've already asked this question once, but was part of an epic essay that I've decided to break down into smaller more manageable chunks (as unsurprisingly that one got no replies).
    I've got an ASUS PCE-A66 wireless ac pci-e card. Had absolutely no issues with it in my old Z77 board, but I seem to be having a lot of issues with it in my new Z87 MPower MAX. System was locking up like mad when I was trying to install the drivers at first. Had to rip out the WiFi/Bluetooth/WiDi module to get the drivers installed but the system randomly hangs on boot up? Don't get the issues with the card unplugged and don't always get it with it plugged in, but there seems to be some form of conflict with it that I can't resolve. Has anyone else had any such issues with any PCI-e add in cards on this motherboard?
    Specs are:
    i7 4770k
    MSI MPower MAX using .128 bios (will try the .131 later)
    2x4GB Corsair Dominator Platinum 2400
    Coolermaster Silent Pro Hybrid 1050w
    EVGA NVidia GTX 780 SC ACX
    Windows 8 Pro 64bit

    Yes, old system was Win8 Pro 64 bit too and the drivers are Windows 8 certified. As I say though, I had no issues with it on the old build? Even got a replacement sent out by Amazon in case the card itself was damaged  Did initially try to do a warm update of the hardware into the same OS installation but didn't play well so did a full re-install in the end. Tried standard and UEFI installs (just in case) and after a problem with my OCZ Vector 2 not being recognised I bought a new Samsung 840 Pro so was a virgin SSD installed on to as well.
    I'll raise it directly with MSI but just wanted to know if anyone else had experienced anything similar with any wireless cards in this mobo.
    Cheers for the reply though 

  • Wireless card BCM4313 no connection at boot

    Hi,
    I have an HP Pavilion dv6 with a Broadcom BCM4313 wireless card. I use NETCFG and before the last kernel upgrade I was able to connect to my home wireless connection at boot without troubles. Now I have to do it manually and I need to try 2 or 3 times to see my connection active.
    lspci -vnn
    02:00.0 Network controller [0280]: Broadcom Corporation BCM4313 802.11b/g/n Wireless LAN Controller [14e4:4727] (rev 01)
    Subsystem: Hewlett-Packard Company Device [103c:1483]
    Flags: bus master, fast devsel, latency 0, IRQ 16
    Memory at c3400000 (64-bit, non-prefetchable) [size=16K]
    Capabilities: <access denied>
    Kernel driver in use: brcmsmac
    Kernel modules: bcma, wl, brcmsmac
    lsmod
    Module Size Used by
    cpufreq_stats 3890 0
    radeon 992718 0
    ttm 54360 1 radeon
    ipv6 290407 22
    cpufreq_ondemand 6132 4
    uvcvideo 64931 0
    videodev 78006 1 uvcvideo
    media 10437 2 uvcvideo,videodev
    usbhid 35256 0
    hid 81635 1 usbhid
    v4l2_compat_ioctl32 8292 1 videodev
    snd_hda_codec_hdmi 22092 1
    joydev 9895 0
    snd_hda_codec_idt 55175 1
    i915 707307 7
    snd_hda_intel 22122 0
    snd_hda_codec 77927 3 snd_hda_codec_hdmi,snd_hda_codec_idt,snd_hda_intel
    drm_kms_helper 25409 2 radeon,i915
    lib80211_crypt_tkip 8506 0
    drm 183380 5 radeon,ttm,i915,drm_kms_helper
    snd_hwdep 6325 1 snd_hda_codec
    snd_pcm 73856 3 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec
    snd_timer 19416 1 snd_pcm
    r8169 42643 0
    lib80211 4158 1 lib80211_crypt_tkip
    snd 57786 7 snd_hda_codec_hdmi,snd_hda_codec_idt,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer
    sg 25557 0
    hp_accel 13864 0
    lis3lv02d 10508 1 hp_accel
    i2c_i801 8187 0
    serio_raw 4294 0
    iTCO_wdt 12717 0
    hp_wmi 7738 0
    intel_agp 10904 1 i915
    arc4 1410 2
    btusb 11577 0
    evdev 9530 9
    bluetooth 138465 1 btusb
    soundcore 6146 1 snd
    bcma 13762 0
    i2c_algo_bit 5199 2 radeon,i915
    sparse_keymap 3088 1 hp_wmi
    mei 31249 0
    i2c_core 20133 7 radeon,videodev,i915,drm_kms_helper,drm,i2c_i801,i2c_algo_bit
    iTCO_vendor_support 1929 1 iTCO_wdt
    pcspkr 1819 0
    snd_page_alloc 7121 2 snd_hda_intel,snd_pcm
    intel_ips 11213 0
    psmouse 55224 0
    intel_gtt 14423 3 i915,intel_agp
    mii 3995 1 r8169
    input_polldev 2882 1 lis3lv02d
    battery 10905 0
    wmi 8411 1 hp_wmi
    ac 3265 0
    button 4470 1 i915
    brcmsmac 594624 0
    thermal 7863 0
    video 11228 1 i915
    brcmutil 6563 1 brcmsmac
    mac80211 215605 1 brcmsmac
    cfg80211 160516 2 brcmsmac,mac80211
    rfkill 15402 3 hp_wmi,bluetooth,cfg80211
    crc_ccitt 1331 1 brcmsmac
    acpi_cpufreq 5877 1
    freq_table 2451 3 cpufreq_stats,cpufreq_ondemand,acpi_cpufreq
    processor 24256 1 acpi_cpufreq
    mperf 1275 1 acpi_cpufreq
    ext4 369556 2
    mbcache 5817 1 ext4
    jbd2 71074 1 ext4
    crc16 1297 2 bluetooth,ext4
    sr_mod 14951 0
    sd_mod 28307 4
    cdrom 36329 1 sr_mod
    ahci 20865 3
    libahci 18885 1 ahci
    libata 173297 2 ahci,libahci
    ehci_hcd 39511 0
    scsi_mod 131482 4 sg,sr_mod,sd_mod,libata
    usbcore 142544 5 uvcvideo,usbhid,btusb,ehci_hcd
    dmesg | grep wlan0
    [ 11.715805] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 13.791409] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 16.885059] wlan0: authenticate with 50:67:f0:ab:4f:d4 (try 1)
    [ 16.886567] wlan0: authenticated
    [ 16.890100] wlan0: associate with 50:67:f0:ab:4f:d4 (try 1)
    [ 16.892793] wlan0: RX AssocResp from 50:67:f0:ab:4f:d4 (capab=0x471 status=0 aid=1)
    [ 16.892798] wlan0: associated
    [ 16.894146] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
    [ 26.697130] wlan0: deauthenticating from 50:67:f0:ab:4f:d4 by local choice (reason=3)
    [ 87.612906] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 89.754106] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 92.849882] wlan0: authenticate with 50:67:f0:ab:4f:d4 (try 1)
    [ 92.851661] wlan0: authenticated
    [ 92.851823] wlan0: associate with 50:67:f0:ab:4f:d4 (try 1)
    [ 92.854142] wlan0: RX AssocResp from 50:67:f0:ab:4f:d4 (capab=0x471 status=0 aid=1)
    [ 92.854150] wlan0: associated
    [ 92.855920] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
    [ 103.719958] wlan0: no IPv6 routers present
    [ 105.980215] wlan0: deauthenticating from 50:67:f0:ab:4f:d4 by local choice (reason=3)
    [ 120.237260] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 122.316759] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 125.422195] wlan0: authenticate with 50:67:f0:ab:4f:d4 (try 1)
    [ 125.423760] wlan0: authenticated
    [ 125.423960] wlan0: associate with 50:67:f0:ab:4f:d4 (try 1)
    [ 125.426083] wlan0: RX AssocResp from 50:67:f0:ab:4f:d4 (capab=0x471 status=0 aid=1)
    [ 125.426090] wlan0: associated
    [ 125.428085] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
    [ 136.398877] wlan0: no IPv6 routers present
    You could see that first I get the connection and then I lost it... for 2 or 3 times, then I could connect without problems.
    ifconfig
    lo Link encap:Local Loopback
    inet addr:127.0.0.1 Mask:255.0.0.0
    inet6 addr: ::1/128 Scope:Host
    UP LOOPBACK RUNNING MTU:16436 Metric:1
    RX packets:338 errors:0 dropped:0 overruns:0 frame:0
    TX packets:338 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:27772 (27.1 Kb) TX bytes:27772 (27.1 Kb)
    wlan0 Link encap:Ethernet HWaddr E0:2A:82:A2:B5:88
    inet addr:192.168.1.33 Bcast:192.168.1.255 Mask:255.255.255.0
    inet6 addr: fe80::e22a:82ff:fea2:b588/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:12484 errors:0 dropped:0 overruns:0 frame:0
    TX packets:9606 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:13841736 (13.2 Mb) TX bytes:1241490 (1.1 Mb)
    iwconfig
    wlan0 IEEE 802.11bgn ESSID:"WLAN_A9"
    Mode:Managed Frequency:2.452 GHz Access Point: 50:67:F0:AB:4F:D4
    Bit Rate=54 Mb/s Tx-Power=19 dBm
    Retry long limit:7 RTS thr:off Fragment thr:off
    Power Management:off
    Link Quality=40/70 Signal level=-70 dBm
    Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
    Tx excessive retries:0 Invalid misc:82 Missed beacon:0
    my wirelessCasa netcfg profile
    CONNECTION='wireless'
    DESCRIPTION='A simple WEP encrypted wireless connection'
    INTERFACE='wlan0'
    SECURITY='wep'
    ESSID='WLAN_A9'
    KEY='s:mykey'
    IP='dhcp'
    POST_UP="notify-send -u critical -i /usr/share/icons/Faenza/status/48/connect_established.png -t 15000 'Connected to WLAN_A9'"
    POST_DOWN="notify-send -u critical -i /usr/share/icons/Faenza/status/48/gnome-netstatus-disconn.png -t 15000 'Connection lost'"
    # Uncomment this if your ssid is hidden
    #HIDDEN=yes
    rc.conf
    NETWORKS=(wirelessCasa)
    DAEMONS=(syslog-ng dbus net-profiles net-auto-wired !network !netfs crond laptop-mode alsa slim @acpid @cups)
    When I execute netcfg for the first time (after boot) I see:
    #NETCFG_DEBUG=yes netcfg wirelessCasa
    DEBUG: Loading profile wirelessCasa
    DEBUG: Configuring interface wlan0
    :: wirelessCasa up [BUSY] DEBUG: status reported to profile_up as:
    DEBUG: Loading profile wirelessCasa
    DEBUG: Configuring interface wlan0
    DEBUG: wireless_up stop_wpa wlan0
    DEBUG: wireless_up start_wpa wlan0 /run/network//wpa.wlan0/wpa.conf nl80211,wext
    DEBUG: wireless_up stop_wpa wlan0
    DEBUG: wireless_up Configuration generated at /run/network//wpa.wlan0/wpa.conf
    DEBUG: wireless_up ifup
    DEBUG: wireless_up start_wpa wlan0 /run/network//wpa.wlan0/wpa.conf nl80211,wext
    DEBUG: wireless_up wpa_check
    DEBUG: wpa_cli -p /run/wpa_supplicant -i wlan0 status
    DEBUG: Loading profile wirelessCasa
    DEBUG: Configuring interface wlan0
    DEBUG: ethernet_iproute_up ifup
    DEBUG: ethernet_up dhcpcd -qL -t 10 wlan0
    DEBUG:
    > DHCP IP lease attempt failed.
    DEBUG: Loading profile wirelessCasa
    DEBUG: Configuring interface wlan0
    DEBUG: Loading profile wirelessCasa
    DEBUG: Configuring interface wlan0
    DEBUG: ethernet_down if_down
    DEBUG: wireless_down stop_wpa wlan0
    DEBUG: profile_up connect failed
    [FAIL]
    And the second one:
    #NETCFG_DEBUG=yes netcfg wirelessCasa
    DEBUG: Loading profile wirelessCasa
    DEBUG: Configuring interface wlan0
    :: wirelessCasa up [BUSY] DEBUG: status reported to profile_up as:
    DEBUG: Loading profile wirelessCasa
    DEBUG: Configuring interface wlan0
    DEBUG: wireless_up stop_wpa wlan0
    DEBUG: wireless_up start_wpa wlan0 /run/network//wpa.wlan0/wpa.conf nl80211,wext
    DEBUG: wireless_up stop_wpa wlan0
    DEBUG: wireless_up Configuration generated at /run/network//wpa.wlan0/wpa.conf
    DEBUG: wireless_up ifup
    DEBUG: wireless_up start_wpa wlan0 /run/network//wpa.wlan0/wpa.conf nl80211,wext
    DEBUG: wireless_up wpa_check
    DEBUG: wpa_cli -p /run/wpa_supplicant -i wlan0 status
    DEBUG: Loading profile wirelessCasa
    DEBUG: Configuring interface wlan0
    DEBUG: ethernet_iproute_up ifup
    DEBUG: ethernet_up dhcpcd -qL -t 10 wlan0
    DEBUG:
    DEBUG: ethernet_iproute_up hostname archlap
    [DONE]
    I've tried to use the wl driver but it doesn't seems to work properly.
    Could anyone help me please?
    Thank you,
    enrico

    litemotiv wrote:
    Hmm it seems your card now takes longer to connect, the 'deauthenticating by local choice' often means that the default timeout is reached and netcfg disconnects. You can try adding a specific timeout parameter to your netcfg profile:
    TIMEOUT=60
    That doesn't explain why it takes longer to connect than before, but at least you should be able to connect in 1 try again.
    Hi,
    thank you for your time!
    I'v tried adding the timeout line to my profile but it doesn't change nothing
    I could connect at 3rd try.
    Any other idea?

  • Startup gets 'Network cable unplugged' on mini-PCI wireless card

    I recently installed a Netgear DG834GT wireless router and now have an intermittent problem connecting my Tecra 9100 to it. If the 9100 has been shutdown for a while (like overnight), when I restart I always get 'Network cable unplugged' for the wireless connection. Rebooting a number of times (anything from 3 upwards) I eventually get connected to the router and all then works fine for hours. Even a quick restart at this point (i.e. once the wireless card has connected) does not cause a problem but as soon as I leave the machine shutdown for a length of time it fails again at reboot.
    There are no errors in the Event log.
    I am using the built in mini-PCI wireless card and have already upgraded to the latest driver.
    Any ideas gratefully recieved, at the moment each morning is a 20-30 minute frustration of rebooting trying to get my connection working.
    (Running Win2K Professional)

    Checking other boards for help (Netgear etc.) it seems that the 'Network cable unplugged' is a common message when wireless connectivity is failing. However, to prove the point, I have disabled the other LAN card (for which I was also getting 'network cable unplugged' but as expected since it was). I still get the same issue with the wireless card, although now the reboots are slightly more predictable - it normally seems to succeed on the third reboot. I guess disabling the other card has changed the startup timing slightly and in that way made things slightly better.
    Again, any other suggestions gratefully received. As this seems to be a timing issue at startup, I am suspicious that one of the other things that runs at that time is causing the problem.

Maybe you are looking for