Broadcom wl with wicd

Hello All,
I have a broadcom card that only works with the wl kernel driver. I was running an older version of wicd (two updates ago) and I could connect to any network such as WPA WEP and wired. Since the newest two updates, I can not connect to secured networks only unsecured ones. ( and wired, but I think that is a different problem) I suspect that I have a problem with my wpa_supplicant with wicd, but I am unsure. is there anything special that I need to do to connect with the wl driver in WICD?
I dont know what files are associated with this problem, but please let me know what you need.
Thanks,
Levi

The card is a BCM4322 802.11a/b/g/n. For the driver I used http://wiki.archlinux.org/index.php/Broadcom_BCM4312 that guide. When the system boots, I have the kernel wl autoloaded, but I can only connect to unsecured wireless networks. I just realized that I had not added ieee80211_crypt_tkip to the modules loaded at boot, would that allow it to connect?

Similar Messages

  • [solved] problem with wicd and broadcom

    I have a compaq 515 with broadcom wireless
    lspci:
    03:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g (rev 01)
    I installed the b43 firmware from AUR
    parts of rc.conf:
    MODULES=(b43 ssb !b43legacy fglrx)
    DAEMONS=(@syslog-ng !network dbus netfs @crond @alsa wicd)
    iwconfig:
    lo no wireless extensions.
    eth0 no wireless extensions.
    wlan0 IEEE 802.11bg Mode:Managed Access Point: Not-Associated
    Tx-Power=20 dBm
    Retry long limit:7 RTS thr:off Fragment thr:off
    Power Management:off
    ifconfig:
    eth0 Link encap:Ethernet HWaddr 18:A9:05:85:D4:D1
    inet addr:192.168.1.7 Bcast:192.168.1.255 Mask:255.255.255.0
    inet6 addr: fe80::1aa9:5ff:fe85:d4d1/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:7173 errors:0 dropped:0 overruns:0 frame:0
    TX packets:5175 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:8792798 (8.3 Mb) TX bytes:631272 (616.4 Kb)
    Interrupt:16
    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:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
    wlan0 Link encap:Ethernet HWaddr 0C:60:76:6C:96:8A
    UP BROADCAST MULTICAST MTU:1500 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
    sudo iwlist wlan0 scan:
    wlan0 No scan results
    wicd tells me it can't find wireless networks, wired works fine and it's managed with wicd
    wireless works right on kubuntu, but not on arch
    can anyone help me?
    Last edited by rolo2005 (2010-07-17 06:45:14)

    sorry but after reboot everything works fine
    mods: delete this thread if you want

  • Broadcom wl with wext driver on Wicd dropping connections

    I have a laptop where I'm using Wicd to connect to my WPA network. My wireless card is a Broadcom Corporation BCM43142 which is, unfortunately, only supported by the "wl" driver. I can connect to my wireless alright, but every 5 to 30 minutes I get disconnected from the internet.
    My journal is littered with these stack traces. I have a feeling these are the culprits.
    Jan 22 17:57:57 myhostname kernel: WARNING: CPU: 1 PID: 1854 at net/wireless/sme.c:920 cfg80211_connect+0x229/0x4d0 [cfg80211]()
    Jan 22 17:57:57 myhostname kernel: Modules linked in: nls_iso8859_1 nls_cp437 vfat fat fuse joydev mousedev ecb uvcvideo btusb videobuf2_vmalloc videobuf2_memops videobuf2
    Jan 22 17:57:57 myhostname kernel: mbcache jbd2 rtsx_usb_sdmmc led_class mmc_core rtsx_usb sd_mod sr_mod crc_t10dif crct10dif_common cdrom atkbd libps2 ahci libahci libat
    Jan 22 17:57:57 myhostname kernel: CPU: 1 PID: 1854 Comm: iwconfig Tainted: P O 3.17.6-1-ARCH #1
    Jan 22 17:57:57 myhostname kernel: Hardware name: Dell Inc. Inspiron 3521/033MX4, BIOS A12 10/25/2013
    Jan 22 17:57:57 myhostname kernel: 0000000000000000 000000007d9185b2 ffff8801ba593bf8 ffffffff81537c3e
    Jan 22 17:57:57 myhostname kernel: 0000000000000000 ffff8801ba593c30 ffffffff8107079d ffff8800a85a6600
    Jan 22 17:57:57 myhostname kernel: 0000000000000000 ffff8800a8ecd400 ffff8800a8ecd5a8 ffff8801c269d000
    Jan 22 17:57:57 myhostname kernel: Call Trace:
    Jan 22 17:57:57 myhostname kernel: [<ffffffff81537c3e>] dump_stack+0x4d/0x6f
    Jan 22 17:57:57 myhostname kernel: [<ffffffff8107079d>] warn_slowpath_common+0x7d/0xa0
    Jan 22 17:57:57 myhostname kernel: [<ffffffff810708ca>] warn_slowpath_null+0x1a/0x20
    Jan 22 17:57:57 myhostname kernel: [<ffffffffa0419359>] cfg80211_connect+0x229/0x4d0 [cfg80211]
    Jan 22 17:57:57 myhostname kernel: [<ffffffffa0432c31>] cfg80211_mgd_wext_connect+0x151/0x1d0 [cfg80211]
    Jan 22 17:57:57 myhostname kernel: [<ffffffffa0432d99>] cfg80211_mgd_wext_siwfreq+0xe9/0x220 [cfg80211]
    Jan 22 17:57:57 myhostname kernel: [<ffffffffa0432ac0>] cfg80211_wext_siwfreq+0x130/0x150 [cfg80211]
    Jan 22 17:57:57 myhostname kernel: [<ffffffff81524e42>] ioctl_standard_call+0x52/0xe0
    Jan 22 17:57:57 myhostname kernel: [<ffffffff81525bc0>] ? iw_handler_get_private+0x70/0x70
    Jan 22 17:57:57 myhostname kernel: [<ffffffff81524df0>] ? call_commit_handler.part.7+0x30/0x30
    Jan 22 17:57:57 myhostname kernel: [<ffffffff81524d76>] wireless_process_ioctl+0x176/0x1c0
    Jan 22 17:57:57 myhostname kernel: [<ffffffff815250e8>] wext_handle_ioctl+0x78/0xe0
    Jan 22 17:57:57 myhostname kernel: [<ffffffff8145b41c>] dev_ioctl+0x2dc/0x5f0
    Jan 22 17:57:57 myhostname kernel: [<ffffffff8105e9bc>] ? __do_page_fault+0x2ec/0x600
    Jan 22 17:57:57 myhostname kernel: [<ffffffff81427352>] sock_ioctl+0x132/0x2c0
    Jan 22 17:57:57 myhostname kernel: [<ffffffff811da5f0>] do_vfs_ioctl+0x2d0/0x4b0
    Jan 22 17:57:57 myhostname kernel: [<ffffffff81426d62>] ? sock_alloc_file+0xb2/0x150
    Jan 22 17:57:57 myhostname kernel: [<ffffffff811da851>] SyS_ioctl+0x81/0xa0
    Jan 22 17:57:57 myhostname kernel: [<ffffffff8153dc69>] system_call_fastpath+0x16/0x1b
    Has anyone seen anything similar to this? Does anyone know if this is a Wicd, wext, or wl problem? Any help in either fixing this problem or mitigating the dropped connections would be great.

    Hi,
    I have the same issue. The stacktrace is printed everytime I connect with Wicd.
    I'm running kernel 3.19 (but it happened on 3.16 as well) and my wifi card is "Broadcom Corporation BCM43228 802.11a/b/g/n".
    DId you find a solution to the problem?

  • [Solved]Problem with Wicd and D-bus

    I get this error at login:
    "could not connect wicd d-bus interface. Check thw wicd log for error messages"
    I restarted both wicd and dbus demons, but didnt work.
    bash-3.2# wicd-client
    Importing pynotify failed, notifications disabled.
    Has notifications support False
    Loading...
    Connecting to daemon...
    Can't connect to the daemon, trying to start it automatically...
    Connected.
    ERROR:dbus.proxies:Introspect error on :1.29:/org/wicd/daemon: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)
    warning: ignoring exception org.freedesktop.DBus.Error.ServiceUnknown: The name :1.29 was not provided by any .service files
    warning: ignoring exception org.freedesktop.DBus.Error.ServiceUnknown: The name :1.29 was not provided by any .service files
    bash-3.2#
    Last edited by Philip J. Fry (2009-06-29 20:05:33)

    If I'm running kdm, I have no issue at all with wicd-client loading, however if I log into a wm/de (usually openbox) without kdm running wicd-client will not load, even after trying the above solutions....
    Importing pynotify failed, notifications disabled.
    Has notifications support False
    Loading...
    Connecting to daemon...
    Can't connect to the daemon, trying to start it automatically...
    (gksudo:19015): Gdk-CRITICAL **: gdk_x11_atom_to_xatom_for_display: assertion `atom != GDK_NONE' failed
    (gksudo:19015): Gdk-CRITICAL **: gdk_x11_atom_to_xatom_for_display: assertion `atom != GDK_NONE' failed
    (gksudo:19015): Gdk-CRITICAL **: gdk_x11_atom_to_xatom_for_display: assertion `atom != GDK_NONE' failed
    (gksudo:19015): Gdk-CRITICAL **: gdk_x11_atom_to_xatom_for_display: assertion `atom != GDK_NONE' failed
    Connected.
    ERROR:dbus.proxies:Introspect error on :1.10:/org/wicd/daemon: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 1 matched rules; type="method_call", sender=":1.9" (uid=1000 pid=19009 comm="python -O /usr/lib/wicd/wicd-client.py ") interface="org.freedesktop.DBus.Introspectable" member="Introspect" error name="(unset)" requested_reply=0 destination=":1.10" (uid=0 pid=19066 comm="python -O /usr/lib/wicd/wicd-daemon.py "))
    warning: ignoring exception org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 1 matched rules; type="method_call", sender=":1.9" (uid=1000 pid=19009 comm="python -O /usr/lib/wicd/wicd-client.py ") interface="org.wicd.daemon" member="GetConnectionStatus" error name="(unset)" requested_reply=0 destination=":1.10" (uid=0 pid=19066 comm="python -O /usr/lib/wicd/wicd-daemon.py "))
    warning: ignoring exception org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 1 matched rules; type="method_call", sender=":1.9" (uid=1000 pid=19009 comm="python -O /usr/lib/wicd/wicd-client.py ") interface="org.wicd.daemon" member="GetNeedWiredProfileChooser" error name="(unset)" requested_reply=0 destination=":1.10" (uid=0 pid=19066 comm="python -O /usr/lib/wicd/wicd-daemon.py "))
    anubis@thor ~/ $

  • [Solved]:How to Manage 2 LAN cards with WICD

    Hi all,
    I have recently added an additional lan card to my system. Its configured and runs fine.
    However the concern is that I use WICD to manage my broadband internet connection through LAN1 and now I want to use LAN2 to connect to Linux/Win client laptop/desktop to share data and internet connection but WICD can manage one interface at a time and with WICD enabled I cant use Arch network daemon(as per wicd archwiki)... how to manage two cards with WICD enabled??
    Thanks in advance.
    Last edited by kapz (2009-10-04 22:00:39)

    Hi and thankls ngoonee, but then I rather use arch network than netcfg coz its not gui, and yep its not possible with wicd to manage two different lan cards simultaneously,tried and tested everything.Anyways i used wicd only coz it showed icon in sys tray(the lan cable keeps movin a lot so icons are really handy to make out if cable is connected or not). Well the only solution I could find is to manage it via arch network daemon, editing rc.conf and stuff...btw wen on my quest I found this archassistant tool, and its quite handy to 'manage' arch system including netcfg.
    But m curious though, what more netcfg has to offer than that to default network daemon?
    Thanks in advance
    Cheers.

  • [SOLVED] DW1510, broadcom-wl and wicd

    Having some problems connecting up wirelessly using a DW1510 wireless card (based off the Broadcom BCM4322 chip). I've got access to an ethernet port, so I set up XFCE and wicd using pacman. However, wicd couldn't find any wireless networks - apparently b43 doesn't play nice with this particular chipset, so I took a look around and found that others use the broadcom-wl. I followed the Arch wiki's guide on setting it up, and got a kernel panic, so I rebooted and uninstalled it.
    I couldn't find any other way to get the wireless card to work, so I tried to reinstall broadcom-wl, but got this:
    broadcom-wl 5.100.82.111-1
    ( Unsupported package: Potentially dangerous ! )
    ==> Edit PKGBUILD ? [Y/n] ("A" to abort)
    ==> ------------------------------------
    ==> n
    ==> broadcom-wl dependencies:
    - linux (already installed)
    - linux-headers (already installed)
    ==> Edit install ? [Y/n] ("A" to abort)
    ==> -----------------------------------
    ==> n
    ==> Continue building broadcom-wl ? [Y/n]
    ==> -------------------------------------
    ==>
    ==> Building and installing package
    ==> Making package: broadcom-wl 5.100.82.111-1 (Sat Oct 22 16:44:38 BST 2011)
    ==> Checking runtime dependencies...
    ==> Checking buildtime dependencies...
    ==> Retrieving Sources...
      -> Downloading hybrid-portsrc_x86_64-v5_100_82_111.tar.gz...
    --2011-10-22 16:44:38--  http://www.broadcom.com/docs/linux_sta/ … 111.tar.gz
    Resolving www.broadcom.com... 63.251.216.155
    Connecting to www.broadcom.com|63.251.216.155|:80... connected.
    HTTP request sent, awaiting response... 200 OK
    Length: 1407430 (1.3M) [application/x-gzip]
    Saving to: `hybrid-portsrc_x86_64-v5_100_82_111.tar.gz.part'
    100%[======================================>] 1,407,430    573K/s   in 2.4s   
    2011-10-22 16:44:41 (573 KB/s) - `hybrid-portsrc_x86_64-v5_100_82_111.tar.gz.part' saved [1407430/1407430]
      -> Found modprobe.d
      -> Found license.patch
      -> Found semaphore.patch
    ==> Validating source files with sha1sums...
        hybrid-portsrc_x86_64-v5_100_82_111.tar.gz ... Passed
        modprobe.d ... Passed
        license.patch ... Passed
        semaphore.patch ... Passed
    ==> Extracting Sources...
      -> Extracting hybrid-portsrc_x86_64-v5_100_82_111.tar.gz with bsdtar
    ==> Starting build()...
    patching file src/wl/sys/wl_linux.c
    Hunk #1 succeeded at 245 (offset 5 lines).
    patching file src/wl/sys/wl_iw.h
    make: Entering directory `/usr/src/linux-3.0-ARCH'
    make: *** No targets.  Stop.
    make: Leaving directory `/usr/src/linux-3.0-ARCH'
    ==> ERROR: A failure occurred in build().
        Aborting...
    ==> ERROR: Makepkg was unable to build broadcom-wl.
    ==> Restart building broadcom-wl ? [y/N]
    ==> ------------------------------------
    ==>
    So, I looked around to see if yaourt had left anything behind:
    [motdef@titan ~]$ rmmod wl
    ERROR: Module wl does not exist in /proc/modules
    [motdef@titan ~]$ modprobe wl
    FATAL: Could not read '/lib/modules/3.0-ARCH/kernel/drivers/net/wireless/wl.ko': No such file or directory
    [motdef@titan ~]$ sudo modprobe -r wl
    Password:
    [motdef@titan ~]$ modprobe wl
    FATAL: Error inserting wl (/lib/modules/3.0-ARCH/kernel/drivers/net/wireless/wl.ko): Operation not permitted
    Apparently modprobe thinks it exists even though the related files don't. I tried rebooting, and now I'm getting errors there, too (sorry about the crude photograph, I couldn't work out how to send the errors to a file):
    As I said earlier, b43 isn't compatible with my chipset anyway, so it's not a huge problem, but irritating nevertheless.
    I'm really stuck for ideas. I'm not sure if the broadcom-wl package files are actually on my system or not, and I've no idea what's missing from the kernel folder, and what it's got to do with the b43 errors at startup. Any suggestions?
    Last edited by mot.def (2011-10-28 11:26:03)

    mot.def wrote:
    I had b43 and ssb blacklisted, as the wiki suggested.
    I just reinstalled Arch from scratch and set up broadcom-wl again. Got another kernel panic after doing "sudo modprobe wl" (and got a picture), and after that I started getting the familiar modprobe and yaourt error messages.
    I'll start again and try using b43, though I did try it on my very first attempt and it definitely didn't want to work with the wireless card.
    I had the same kernel panic after updating the broadcom-wl driver today. I removed the driver and am now using brcmsmac which is part of the kernel. Maybe you can check that out if its compatible with your card. (See the wiki for more details.)

  • Issues with wicd 1.6.0

    I've been using wicd for quite some time now and I use both to manage my wired connection and wireless (using broadcom-wl driver) on my stationary pc. Usually wicd autoconnects to my wired evey time I start my machine but since the upgrade to 1.6.0 yesterday wicd doesn't autoconnect to my wired network anymore. I have to manually connect after each start. Why is that? I haven't changed the slightest in my network setup. My wired connection is named eth1 and my wireless is eth0 by the way.
    Regards
    André

    I get this output:
    $ wicd-client
    Has notifications support True
    Loading...
    Connecting to daemon...
    Can't connect to the daemon, trying to start it automatically...
    Connected.
    /usr/lib/wicd/wicd-client.py:419: GtkWarning: Im Modulpfad »clearlooks« konnte keine Themen-Engine gefunden werden,
    self.menu = (self.manager.get_widget('/Menubar/Menu/About').
    /usr/lib/wicd/wicd-client.py:419: GtkWarning: Im Modulpfad »murrine« konnte keine Themen-Engine gefunden werden,
    self.menu = (self.manager.get_widget('/Menubar/Menu/About').
    ERROR:dbus.proxies:Introspect error on :1.40:/org/wicd/daemon: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)
    warning: ignoring exception org.freedesktop.DBus.Error.ServiceUnknown: The name :1.40 was not provided by any .service files
    warning: ignoring exception org.freedesktop.DBus.Error.ServiceUnknown: The name :1.40 was not provided by any .service files
    I'm using kdemod, too. And I installed python-something, but that didn't worked, too.

  • Howto install broadcom wl with custom kernel

    Hi I am trying to install the broadcom-wl driver from a custom kernel made traditionnal way.
    The makefile they provide give me this :
    KBUILD_NOPEDANTIC=1 make -C /lib/modules/`uname -r`/build M=`pwd`
    make[1]: Entering directory `/home/maxime/kernelbuild/linux-3.10.10'
    Wireless Extension is the only possible API for this kernel version
    Using Wireless Extension API
      CC [M]  /home/maxime/wldriver/src/wl/sys/wl_linux.o
    In file included from /home/maxime/wldriver/src/wl/sys/wl_linux.c:43:0:
    /home/maxime/kernelbuild/linux-3.10.10/arch/arm/include/asm/system.h:3:26: fatal error: asm/compiler.h: No such file or directory
    #include <asm/compiler.h>
                              ^
    compilation terminated.
    make[2]: *** [/home/maxime/wldriver/src/wl/sys/wl_linux.o] Error 1
    make[1]: *** [_module_/home/maxime/wldriver] Error 2
    make[1]: Leaving directory `/home/maxime/kernelbuild/linux-3.10.10'
    make: *** [all] Error 2
    I have change the path in wl_linux.o to include system.h with the full path(as you can see). And it can find it, but I have to change all the path for every <include> wich is very long and i am not sure it s the right way.
    I tried to install the driver with yaourt and it installs the .ko . in my extramodules folder in my /lib/modules/ directory. but modprobe wl report no such file.
    But if i come back to the precompiled kernel it works. I ve tried to change the kernel version to my current version in extramodules in /lib/modules/extramodules-3.10 that the PKGBUILD is looking at and try to install it again with yaourt on my custom kernel but still the same.
    I copied the .ko to my kernel 3.10.10 custom and tried modprob and I got a symlink error.
    As they said i need to modprob the  cfg80211, which i did but I still get the same error.
    Howto build package for my custom kernel and not the default kernel while I am on the custom kernel ??
    Last edited by maxarsys (2013-09-09 21:14:39)

    Sigi wrote:Have you deleted or commented out kernel26 in the file addedpacks?
    oh, thx, i didn't know, that kernel26 is in addedpacks. now, i am building it with  #kernel26
    Sigi wrote:May I ask why you made your own kernel? I'm just wondering... ;-)
    because i wanna change logo in FB, and/or  add splasscreen support.
    or is it possible, add it, to kernel26?
    Sigi wrote:edit: btw, Welcome to the forum!
    oh thx, hello here

  • [SOLVED] Broadcom BCM4313 with NetworkManager - no vissible networks

    Hi. I have a Samsung N150 Plus netbook. Because i have the "plus" version i also got broadcom wifi card, which, as said on the wiki, have issues with default kernel driver. So, installed broadcom-wl from AUR, added "wl !brcm80211 !mac80211 !cfg80211" to modules, and the i installed networkmanager, and added it to the daemons, disabling network by the way. So, after restart it seems ok, ifconfig and iwconfig shows right values, cable network is working but i can't see any networks in network manager applet, it's just saying disconnected. So, how can i make it running?
    Last edited by Zuba (2011-04-14 14:49:59)

    I know NetworkManager from ubuntu, and i like it because i can connect to a network with two clicks, so i would like to stay with it.
    @EDIT
    Fixed it Had to install samsung-tools from AUR, and it's working now. Backlight fn keys are working also
    Last edited by Zuba (2011-04-14 14:49:42)

  • WPA2 Enterpise + AES with wicd

    Hi,
    I'm Matteo and I'm a student.... so to get access to internet i have to connect to a wireless connection that requires AES encryption but i dont know how to do that, i dont see this option when i configure the connection to WPA2 enterprise.
    So, Is there maybe a script that can add this feature to network manager??
    Or some configuration (on wpa_supplicant.conf for example) that can fix this??
    As i already said I use network manager and my card is the Intel Corporation WiFi Link 5100
    Thanks to all in advance for your responses
    Last edited by mate (2011-11-06 16:46:02)

    mate wrote:
    Gusar wrote:Check if you can set CCMP. CCMP connections use AES.
    Hi gusar thanks for your response and sorry for not replying for that long but i had not access to the internet
    I checked and no I cant.... with wpa2-Enterprise i can only use TLS, LEAP, Tunneled TLS and PEAP authentications.
    Any idea?
    Thanks
    Following from Gusar, your Uni guide should be a first start. But from my experience (in Uni when they recently upgraded the network) I have been experiencing connection problems too. Networkmamager does not give a lot of control on how to connect. I switched to netcfg and used the following  to help configure its profile. (I also used the technical specification of my Uni to guide me - the process was iterative until I was successful and sent an email to helpdesk saying YA!)
    http://hostap.epitest.fi/gitweb/gitweb. … icant.conf
    Info about netcfg can be obtained from Arch Wikis (probably your best start)
    https://wiki.archlinux.org/index.php/Netcfg
    Cheers!
    J

  • Broadcom 4312 with 2.6.30-ARCH[Solved]

    well my problem is:
    the entire installation is great, but when installing broadcom drivers follow the steps of compiling the driver AUR adding to rc.conf but I can not operate my wireless, the led is still in red,
    HP dv4-1125nr
    2.6.30-Arch
    Archlinux 2009.08
    appreciate your help
    Last edited by Inzombie (2009-09-02 22:20:59)

    1.go to the HP official site to download the driver for XP
    2.then use winzip to open the exe file and search the inf and sys files for your wireless card
    3.copy the inf and sys files to a usb disk
    4.go to Arch and mount the usb disk
    5.change the dir to your inf and sys files location
    6.ndiswrapper -i filename.inf
      ndiswrapper -m
      ndiswrapper -mi
      ndiswrapper -ma
    7.reboot
    8.done~
    Last edited by Rothsdad (2009-09-02 13:32:33)

  • An anoying problem with wicd logging to terminal

    when ever i start wicd and i haven't strarted my x server yet it logs messages to my terminal while i am trying to use it
    this is very anoying and i would like to know why it does that and if its possible to turn it off

    Not a Sysadmin issue, moving to NC...

  • Issues configuring broadcom wl driver with netctl and wpa_supplicant

    After quite some hurdle, I managed to get the wireless working with a Broadcom 4322 with the wl driver working. But there are two minor issues which I'd like to ask the more experienced audience:
    With netctl, I need to manually interact with wpa_supplicant. This was not needed for the same setup on a different machine with a different driver. I'm fine with that, but when it comes to directing the wpa config to netctl, I had to make the config available as /etc/wpa_supplicant.conf because this is the default for netctl. But according to the man page for netctl, netctl offers the option to specify WPAConfigFile, which should be enabled when Security is set to wpa-config. So, I'd like to have the following config:
    /etc/netctl/myWirelessSetup:
    Interface=eth0
    Connection=wireless
    Security=wpa-config
    IP=dhcp
    ESSID=
    Key=
    WPAConfigFile=/etc/wpa_supplicant/myWPASupplicantSetup
    The reason I did it this way is because I ran into a dependency issue with netcfg when not having a wpa_supplicant config file.
    The other issue I have with the broadcom wl driver is that it forces the naming of the wireless device to be eth0, which I don't like. I tried to set it according to the Network wiki, but on boot udev reported a busy device, so I gave up on that.
    I'd appreciate if anybody can point me on what I'm doing wrong.

    yeah, I know it seems odd, but when you install broadcom-wl, it sets the interface to eth0. You'll find it in the wiki. I also know it's eth0 because that's the interface I use to connect to wifi at home.

  • Arch with broadcom wireless, etc (Dell N5010)

    I have a dell N5010, as seen here http://www.dell.com/us/p/inspiron-15r/pd i have used both ubuntu and fedora on it, so i know linux will run on it, and wireless will work, but is there any written procedures i need to follow to get broadcom working with arch/does anyone know of other issues with this model? Thanks for all help.

    Hello,
    yes, there is: https://wiki.archlinux.org/index.php/Broadcom_wireless
    This first part should get your card running. You'll also need to manage your connections. There's also a written wiki article for that: https://wiki.archlinux.org/index.php/Wl … management
    Have fun!

  • Permissions problem with broadcom-wl?

    Hi,
    I have some sort of a permissions problem:
    When typing 'iwconfig' as a user, I get:
    lo no wireless extensions.
    eth0 no wireless extensions.
    eth1 IEEE 802.11 Nickname:""
    Access Point: Not-Associated
    And only when typing iwconfig as root I get:
    [root@delltux fio]# iwconfig
    lo no wireless extensions.
    eth0 no wireless extensions.
    eth1 IEEE 802.11abgn ESSID:"AAAA" Nickname:""
    Mode:Managed Frequency:2.437 GHz Access Point: 00:1F:1F:16:3B:9E
    Bit Rate=54 Mb/s Tx-Power:32 dBm
    Retry min limit:7 RTS thr:off Fragment thr:off
    Power Managementmode:All packets received
    Link Quality=5/5 Signal level=-39 dBm Noise level=-92 dBm
    Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
    Tx excessive retries:22 Invalid misc:0 Missed beacon:0
    Plus, when trying to change the essid manually as root ('iwconfig eth1 essid BBBB'),
    it often doesn't work, and I have to remove the wl module, and reload it (and even then, it sometimes doesn't work...)
    And - when trying to connect with Wicd, I often get connection problems (it takes forever to connect, only after about 10 tries). If the ssid is set correctly (if I manage to set it...) then commandline dhcp works with no problems.
    Does anybody have a suggestion?
    Thanks
    Fiod

    fiod wrote:
    Hi,
    I have some sort of a permissions problem:
    When typing 'iwconfig' as a user, I get:
    lo no wireless extensions.
    eth0 no wireless extensions.
    eth1 IEEE 802.11 Nickname:""
    Access Point: Not-Associated
    And only when typing iwconfig as root I get:
    [root@delltux fio]# iwconfig
    lo no wireless extensions.
    eth0 no wireless extensions.
    eth1 IEEE 802.11abgn ESSID:"AAAA" Nickname:""
    Mode:Managed Frequency:2.437 GHz Access Point: 00:1F:1F:16:3B:9E
    Bit Rate=54 Mb/s Tx-Power:32 dBm
    Retry min limit:7 RTS thr:off Fragment thr:off
    Power Managementmode:All packets received
    Link Quality=5/5 Signal level=-39 dBm Noise level=-92 dBm
    Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
    Tx excessive retries:22 Invalid misc:0 Missed beacon:0
    I'm seeing the exact same issue.  I'd think this is a bug and that non-root users should be able to query the interface for connection info.  The failure of being able to do this is also causing my network monitoring tools (kwifimanager and knemo) to show missing and/or erroneous data.
    Anyone know how to fix this?

Maybe you are looking for