Find the answer to your Linux question:
Page 2 of 5 FirstFirst 1 2 3 4 5 LastLast
Results 11 to 20 of 49
I have /lib/firmware/b43. Where else do u suggest to make dir b43? I didnt see a search for the firmware, nor any trouble installing it. lspci Code: 00:00.0 Host bridge: ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #11
    Linux Newbie TrashOverride's Avatar
    Join Date
    May 2004
    Location
    @home...soon in your homes ;) /usr/src/bulgaria
    Posts
    162

    I have /lib/firmware/b43. Where else do u suggest to make dir b43? I didnt see a search for the firmware, nor any trouble installing it.
    lspci
    Code:
    00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07)
    00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
    00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
    00:1a.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03)
    00:1a.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03)
    00:1a.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 03)
    00:1a.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03)
    00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03)
    00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03)
    00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 (rev 03)
    00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 (rev 03)
    00:1c.4 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 5 (rev 03)
    00:1c.5 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 6 (rev 03)
    00:1d.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03)
    00:1d.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03)
    00:1d.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03)
    00:1d.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03)
    00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93)
    00:1f.0 ISA bridge: Intel Corporation ICH9M LPC Interface Controller (rev 03)
    00:1f.2 IDE interface: Intel Corporation ICH9M/M-E 2 port SATA IDE Controller (rev 03)
    00:1f.5 IDE interface: Intel Corporation ICH9M/M-E 2 port SATA IDE Controller (rev 03)
    02:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g (rev 01)
    85:00.0 Ethernet controller: Marvell Technology Group Ltd. Unknown device 4357
    lsusb
    Code:
    Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 008 Device 002: ID 0458:003a KYE Systems Corp. (Mouse Systems)
    Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 001 Device 003: ID 04f2:b083 Chicony Electronics Co., Ltd
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 003 Device 002: ID 03f0:171d Hewlett-Packard Wireless (Bluetooth + WLAN) Interface [Integrated Module]
    Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

  2. #12
    Linux Guru
    Join Date
    Jul 2004
    Posts
    4,593
    Well, the device shows up in lspci, so that isn't the problem.

    You can try copying the firmware directly into the /lib/firmware folder, if you haven't already done that. Other than that, I can't come up with any other solutions to try. This may be a configure thing with Slackware, and I don't use Slackware so I can't help with that.

    I see that there is a netconfig command that may help.
    The Slackware Linux Project: Configuration Help

    Otherwise, here's an old thread that may provide some help:
    http://www.linuxforums.org/forum/sla...slcakware.html
    Please do not send Private Messages to me with requests for help. I will not reply.

  3. #13
    Linux Newbie TrashOverride's Avatar
    Join Date
    May 2004
    Location
    @home...soon in your homes ;) /usr/src/bulgaria
    Posts
    162
    netconfig is only for ethernet devices, not for wifi.
    The strange thing is that with ndiswrapper and the wl driver it works, but a cannot conect, now with the original driver i cannot see the device. I'm wondering if there is a different command to bring up the device...

    10x again

  4. #14
    Linux Guru
    Join Date
    Jul 2004
    Posts
    4,593
    I would think that whether it is a wireless or a wired device, it still is a network device.

    I guess that I lead you down the wrong road. You may want to go back to the wl driver. At least you had a wireless device listed then!
    Please do not send Private Messages to me with requests for help. I will not reply.

  5. #15
    Linux Guru
    Join Date
    Jul 2004
    Posts
    4,593
    I did locate some info that says that you should modify this file:
    /etc/rc.d/rc.inet1.conf

    Find the line that has #IFNAME[4]="wlan0" and uncomment it (remove the "#")

    There also are two wireless configuration files, although I don't know where they are located or what to do with them:
    rc.wireless
    rc.wireless.conf

    EDIT: There may also be this file:
    rc.wlan

    I got that info here:
    The Slackware Linux Project: Configuration Help
    Here's maybe more useful info?:
    Wireless

    I think that you use Wicd instead of the wpa_supplicant file. But I think that Wicd needs wpa_supplicant to be installed.
    Last edited by waterhead; 04-11-2009 at 03:38 PM.
    Please do not send Private Messages to me with requests for help. I will not reply.

  6. #16
    Linux Newbie TrashOverride's Avatar
    Join Date
    May 2004
    Location
    @home...soon in your homes ;) /usr/src/bulgaria
    Posts
    162

    Red face edit

    Quote Originally Posted by waterhead View Post
    I did locate some info that says that you should modify this file:
    /etc/rc.d/rc.inet1.conf

    Find the line that has #IFNAME[4]="wlan0" and uncomment it (remove the "#")

    There also are two wireless configuration files, although I don't know where they are located or what to do with them:
    rc.wireless
    rc.wireless.conf

    EDIT: There may also be this file:
    rc.wlan

    I got that info here:
    The Slackware Linux Project: Configuration Help
    Here's maybe more useful info?:
    Wireless

    I think that you use Wicd instead of the wpa_supplicant file. But I think that Wicd needs wpa_supplicant to be installed.
    I have alredy edited those files when i was with the wl driver, but it didnt help. Also i thik i read somewhere that wicd takes kare of wpa_supplicant for itself. I'm concerned about
    Code:
    Association request to the driver failed
    i had this with ndiswrapper and wl, that's why i want to try the firmware, but there is no interface... i'm reading some ubuntu forums that has similar threds.
    I'll post if i find something usefull
    Quote Originally Posted by waterhead View Post
    I would think that whether it is a wireless or a wired device, it still is a network device.
    netconfig has options only for ethernet -loopback, staticIP, DHCP

    EDIT:
    lspci -vnn | grep 14e4
    Code:
    02:00.0 Network Controller [0280]: Broadcom Corporation BCM4312 802.11b/g [14e4:4315] (rev 01)
    and according to b43 - Linux Wireless :
    Code:
    PCI-ID               State                Chip                    Driver  
    14e4:4315   not supported   BCM4312 - low power   b43
    I gues my only chance is with the wl driver, but then again, why i cannot connect?
    I'm sure that the card can do WPA2 /on xp and vista does/ so...
    EDIT2
    whe i start mpdprobe wl the syslog says:
    Code:
    localhost kernel: [ 1753.867456]wl: module license " taints the kernel
    i'll keep looking

  7. #17
    Linux Guru
    Join Date
    Jul 2004
    Posts
    4,593
    Nice catch!

    Well, you reported that the wireless was 4212, and that is supported. I used to ask for the -nn output of lspci, but some distros don't support it. I see you used the -vnn option, I'll have to start using that.

    Yes, the wl driver is the one you want to use. Sorry for the sidetrack. If you added it to the blacklist file, make sure you remove it and add b43 to the file.

    I think that Wicd will only support drivers that wpa_supplicant supports. This may not include the wl driver, so you may have to us NDISwrapper. Here is the driver section of the wpa_supplicant man pages.
    AVAILABLE DRIVERS
    A summary of available driver backends is below. Support for each of the driver backends is chosen at
    wpa_supplicant compile time. For a list of supported driver backends that may be used with the -D option
    on your system, refer to the help output of wpa_supplicant (wpa_supplicant -h).

    hostap (default) - Host AP driver (Intersil Prism2/2.5/3). (this can also be used with Linuxant Driver-
    Loader).

    hermes - Agere Systems Inc. driver (Hermes-I/Hermes-II).

    madwifi - MADWIFI 802.11 support (Atheros, etc.).

    atmel - ATMEL AT76C5XXx (USB, PCMCIA).

    wext - Linux wireless extensions (generic).

    ndiswrapper - Linux ndiswrapper.

    broadcom - Broadcom wl.o driver.

    ipw - Intel ipw2100/2200 driver.

    wired - wpa_supplicant wired Ethernet driver

    bsd - BSD 802.11 support (Atheros, etc.).

    ndis - Windows NDIS driver.
    Hey, I see the wl driver as listed. Tell wpa_supplicant to use that one! The command would look something like this:
    Code:
    wpa_supplicant -Dbroadcom -iwlan0 -c/etc/wpa_supplicant.conf
    Please do not send Private Messages to me with requests for help. I will not reply.

  8. #18
    Linux Guru
    Join Date
    Jul 2004
    Posts
    4,593
    You may need to compile the wl support into wpa_supplicant. To see the drivers it supports, use the -h option. Here is mine (no Broadcom support):
    Code:
    wpa_supplicant -h
    <snip>
    drivers:
      wext = Linux wireless extensions (generic)
      atmel = ATMEL AT76C5XXx (USB, PCMCIA)
      ndiswrapper = Linux ndiswrapper
      wired = wpa_supplicant wired Ethernet driver
    </snip>
    It looks like the souce is available from here:

    http://hostap.epitest.fi/releases/wp...t-0.6.9.tar.gz
    Please do not send Private Messages to me with requests for help. I will not reply.

  9. #19
    Linux Newbie TrashOverride's Avatar
    Join Date
    May 2004
    Location
    @home...soon in your homes ;) /usr/src/bulgaria
    Posts
    162

    edit

    Code:
    wpa_supplicant -Dwext -ieth1 -c/etc/wpa_supplicant.conf
    and the output is (i'm on other computer, so i'm retyping it)
    Code:
    Trying to associate with ...MAC of router... (SSID='router' freq=2437 MHz)
    ioctl[SIOCSIWAP]: Device or resource busy
    Association request to the driver failed
    Authentication with ...MAC of router... timed out
    and then it repeats until i stop it

    EDIT
    didnt see your post i'll try updating wpa_supplicant

    EDIT2
    one more thing i noticed in syslog (i have eventwatcher in realtime for /var/log/syslog, /var/log/secure, /var/log/messages)
    Code:
    localhost dhclient: Bind socket to interface: No such device

  10. #20
    Linux Guru
    Join Date
    Jul 2004
    Posts
    4,593
    I downloaded the wpa_supplicant sources, and found this in the /wpa_supplicant-0.6.9/wpa_supplicant/README file.
    Broadcom wl.o driver (old version only)
    This is a generic Linux driver for Broadcom IEEE 802.11a/g cards.
    However, it is proprietary driver that is not publicly available
    except for couple of exceptions, mainly Broadcom-based APs/wireless
    routers that use Linux. The driver binary can be downloaded, e.g.,
    from Linksys support site (Welcome to Linksys.com)
    for Linksys WRT54G. The GPL tarball includes cross-compiler and
    the needed header file, wlioctl.h, for compiling wpa_supplicant.
    This driver support in wpa_supplicant is expected to work also with
    other devices based on Broadcom driver (assuming the driver includes
    client mode support). Please note that the newer Broadcom driver
    ("hybrid Linux driver") supports Linux wireless extensions and does
    not need (or even work) with the specific driver wrapper. Use -Dwext
    with that driver.
    So it seems if you are using the latest "hybrid" driver from HERE, then you just tell wpa_supplicant to use the wext driver. No need to re-compile wpa_supplicant.
    Please do not send Private Messages to me with requests for help. I will not reply.

Page 2 of 5 FirstFirst 1 2 3 4 5 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •