Results 1 to 10 of 10

Thread: Yes, my wireless isn't working yet.

  1. #1
    Stormadvisor NNTP User

    Unhappy Yes, my wireless isn't working yet.

    All,
    After reading and following directions on both sticky's (with some results), and following directions here specific to my card, and looking at the info here finding that my card should work in low power mode, I am still not working.

    I found out my card is a PCI device:

    Code:
    103: udi = '/org/freedesktop/Hal/devices/pci_14e4_4315' 
      pci.subsys_product_id = 11 (0xb) 
      info.subsystem = 'pci' 
      pci.subsys_vendor_id = 4136 (0x1028) 
      info.product = 'BCM4310 USB Controller' 
      pci.device_class = 2 (0x2) 
      info.udi = '/org/freedesktop/Hal/devices/pci_14e4_4315' 
      pci.device_subclass = 128 (0x80) 
      pci.device_protocol = 0 (0x0) 
      linux.sysfs_path = '/sys/devices/pci0000:00/0000:00:1c.1/0000:0c:00.0' 
      pci.vendor = 'Broadcom Corporation' 
      info.parent = '/org/freedesktop/Hal/devices/pci_8086_2841' 
      info.vendor = 'Broadcom Corporation' 
      pci.linux.sysfs_path = '/sys/devices/pci0000:00/0000:00:1c.1/0000:0c:00.0' 
      pci.product = 'BCM4310 USB Controller' 
      pci.subsys_vendor = 'Dell' 
      pci.product_id = 17173 (0x4315) 
      linux.hotplug_type = 2 (0x2) 
      pci.vendor_id = 5348 (0x14e4) 
      linux.subsystem = 'pci'
    I then used "/sbin/lspci" to get:
    Code:
    0c:00.0 Network controller: Broadcom Corporation BCM4310 USB Controller (rev 01)
    and then ran "/sbin/lspci -n" to get:
    Code:
    0c:00.0 0280: 14e4:4315 (rev 01)
    I then ran "dmesg | less" and went through all 621 lines and did not find anything regarding the above information. (since i'm a noob here, is there a way to export the info from "dmesg" to a text file?)

    I went out searching around and found the above pages that I did the firmware update and I still have nothing.

    Where do I go from here?

    Thanks.

    BTW: I do have the switch in the ON position for my wireless card.

  2. #2
    Join Date
    Jun 2008
    Location
    Kansas City Area, Missouri, USA
    Posts
    7,236

    Default Re: Yes, my wireless isn't working yet.

    Stormadvisor wrote:
    > All,
    > After reading and following directions on both sticky's (with some
    > results), and following directions 'here' (http://tinyurl.com/mcf5p6)
    > specific to my card, and looking at the info 'here'
    > (http://tinyurl.com/6hj4bf) finding that my card should work in low
    > power mode, I am still not working.
    >
    > I found out my card is a PCI device:
    >
    >
    > Code:
    > --------------------
    > 103: udi = '/org/freedesktop/Hal/devices/pci_14e4_4315'
    > pci.subsys_product_id = 11 (0xb)
    > info.subsystem = 'pci'
    > pci.subsys_vendor_id = 4136 (0x1028)
    > info.product = 'BCM4310 USB Controller'
    > pci.device_class = 2 (0x2)
    > info.udi = '/org/freedesktop/Hal/devices/pci_14e4_4315'
    > pci.device_subclass = 128 (0x80)
    > pci.device_protocol = 0 (0x0)
    > linux.sysfs_path = '/sys/devices/pci0000:00/0000:00:1c.1/0000:0c:00.0'
    > pci.vendor = 'Broadcom Corporation'
    > info.parent = '/org/freedesktop/Hal/devices/pci_8086_2841'
    > info.vendor = 'Broadcom Corporation'
    > pci.linux.sysfs_path = '/sys/devices/pci0000:00/0000:00:1c.1/0000:0c:00.0'
    > pci.product = 'BCM4310 USB Controller'
    > pci.subsys_vendor = 'Dell'
    > pci.product_id = 17173 (0x4315)
    > linux.hotplug_type = 2 (0x2)
    > pci.vendor_id = 5348 (0x14e4)
    > linux.subsystem = 'pci'
    >
    > --------------------
    >
    > I then used "/sbin/lspci" to get:
    >
    > Code:
    > --------------------
    > 0c:00.0 Network controller: Broadcom Corporation BCM4310 USB Controller (rev 01)
    > --------------------
    >
    > and then ran "/sbin/lspci -n" to get:
    >
    > Code:
    > --------------------
    > 0c:00.0 0280: 14e4:4315 (rev 01)
    > --------------------
    >
    >
    > I then ran "dmesg | less" and went through all 621 lines and did not
    > find anything regarding the above information. (since i'm a noob here,
    > is there a way to export the info from "dmesg" to a text file?)
    >
    > I went out searching around and found the above pages that I did the
    > firmware update and I still have nothing.
    >
    > Where do I go from here?


    If you had run the 'lspci' commands specified in the stickies, you
    would have seen that your wireless device reports a PCI ID of
    14e4:4315. As has been stated many times on this forum, that device
    needs to use the Broadcom wl driver. It will not work with b43!

  3. #3

    Default Re: Yes, my wireless isn't working yet.

    Hi stormadvisor;

    welcome to the OpenSuse forums; we are delighted that you have installed OpenSuse, and we would like to welcome you to the OpenSuse community, here to help and support community members.

    One of the real strengths of the wireless forum on OpenSuse is we have a couple of real experts on wireless; one of whom is Larry Finger; Larry does a fantastic amount of work developing wireless drivers for linux (amongst other things); and I am not sure how he keeps up the pace of work that he does; he must get really tired sometimes;

    I think he is pointing you towards the broadcom wl driver

    You need to know whether you are running 32bit or 64bit Suse

    if you can't remember which you installed, if you type

    uname -r
    in a terminal, it should tell you

    One way to get this broadcom wl driver is to go to the Packman repository

    PackMan :: Package details for broadcom-wl

    .......... select the 32bit or 64 bit package that you need ..

    ......... that matches what you got in the uname -r above

    __________

    and why did you have to do all this? Well, as I understand it, OpenSuse means open source, so only software that is purely Open Source comes with the core OpenSuse; linux means freedom, so you are FREE to download other things

    __

    Broadcom have developed linux drivers for their products: thanks very much Broadcom from the linux community; but they are closed-source I understand;

    ______

    frustrating for beginners? You could well say that; but that is the way it is set up

    _____

    linux becomes a bit like being able to do minor jobs on your car; or fix your lawnmower; so you sort of learn how some things work;

    have a read at this link

    Fix BCM4311/4312/4321/4322 Wireless in openSUSE 11.1 and earlier | SUSE & openSUSE

    it uses YaST to install programmes; click on each picture; takes you through how YaST helps you to install;

    You need Packman repository enabled to use this; and that's another story:

    tell us if you need help enabling Packman

    _________

    welcome to the OpenSuse community; we want it to grow and succeed

  4. #4
    Stormadvisor NNTP User

    Default Re: Yes, my wireless isn't working yet.

    If you had run the 'lspci' commands specified in the stickies, you
    would have seen that your wireless device reports a PCI ID of
    14e4:4315. As has been stated many times on this forum, that device
    needs to use the Broadcom wl driver. It will not work with b43!
    I did find out my card was the 4315. I must have gotten confused trying to check and search what I had, using very new procedures that I am not familiar with, and reading over many many lines of information.

    I am sorry to have offended you. I will do better in the future.

    Thanks

  5. #5
    Stormadvisor NNTP User

    Default Re: Yes, my wireless isn't working yet.

    I was able to get the wl driver working after a couple tries. I was able to get the following output when I ran "iwconfig":
    Code:
    eth1      IEEE 802.11  Nickname:""
              Access Point: Not-Associated   
              Link Quality:5  Signal level:0  Noise level:0
              Rx invalid nwid:0  invalid crypt:0  invalid misc:0
    I would assume it is working now. I do not have a wireless router so i cannot actually connect to anything and try it out fully. Doing a "iwlist scan" offered no results. I must not be close enough to receive anything from my neighbors

    Thanks to you and lwfinger for your help. I'm now off to get my audio to work.

    Thanks

  6. #6

    Default Re: Yes indeed, my wireless isn't working yet.

    hi stormadvisor; good luck with tweaking the sound: oldcpu usually provides very good support for sound on the hardware forum;

    .. your title above may be truer than you think .....

    we will await the expert prognostications of lwfinger or deltaflyer; but I suspect they will say that unless you download and install the broadcom wl driver from a site such as packman; your broadcom 4310 ain't go to work as broadcom intended it to ..

    from a post I read, I see the packman version of the broadcom driver is better than the "raw" one from broadcom, as it has been "tweaked" to optimise it;

    if anyone demands to see the reference for that, I will have to go away and re-google it; as I did not bookmark it;

  7. #7
    Join Date
    Jun 2008
    Location
    Kansas City Area, Missouri, USA
    Posts
    7,236

    Default Re: Yes, my wireless isn't working yet.

    pdc 2 wrote:
    > hi stormadvisor; good luck with tweaking the sound: oldcpu usually
    > provides very good support for sound on the hardware forum;
    >
    > . your title above may be truer than you think .....
    >
    > we will await the expert prognostications of lwfinger or deltaflyer;
    > but I suspect they will say that unless you download and install the
    > broadcom wl driver from a site such as packman; your broadcom 4310 ain't
    > go to work as broadcom intended it to ..
    >
    > from a post I read, I see the packman version of the broadcom driver is
    > better than the "raw" one from broadcom, as it has been "tweaked" to
    > optimise it;
    >
    > if anyone demands to see the reference for that, I will have to go away
    > and re-google it; as I did not bookmark it;


    I would like to see that reference. As the critical part of that
    driver is only available as a binary blob, there is no way to tweak
    it. AFAIK, the only difference is that Packman has the driver prebuilt
    for the standard kernels; whereas it must be built by the user for the
    code that comes from Broadcom.

  8. #8
    Join Date
    Mar 2008
    Location
    Phuket, Thailand
    Posts
    27,108
    Blog Entries
    40

    Default Re: Yes indeed, my wireless isn't working yet.

    Quote Originally Posted by pdc_2 View Post
    hi stormadvisor; good luck with tweaking the sound: oldcpu usually provides very good support for sound on the hardware forum;
    Hey stormadvisor, I've been looking for your post/thread re: sound tweaking, but I have not seen anything, so I am hoping it all went well. I try to help with basic single card graphic sound problems, but anything more than that is often too advanced for me to provide reliable assistance.

    In case it will help, here is a troubleshooting guide for audio that I wrote: SDB:AudioTroubleshooting - openSUSE

  9. #9

    Default Re: Yes, my wireless isn't working yet.

    it was this post I meant:

    Random Thoughts: It works! Broadcom Official Wireless driver (wl) with hidden networks!

    the initial person said

    The problem seems to lie in Broadcom's driver. It does not support 'scan_capa'.
    and he said

    So to add this support, you can recompile the driver from the source RPM from Packman along with this additional patch.
    and later in the post; "Chris" from Fedora says

    Thanks for this. I'm going to include it in the Fedora RPM and am trying to get Broadcom to include it upstream too.
    and later in the post it is also quoted

    SUSE users who use the packman repository for getting the official broadcom-wl driver package already have this patch included (thanks to the packager Andrea Florio).
    it then says

    For others, you just have to add the line:

    range->scan_capa = IW_SCAN_CAPA_ESSID;

    to the file "wl_iw.c" in the driver source after these three lines:

    range->enc_capa|=IW_ENC_CAPA_CIPHER_TKIP;
    range->enc_capa|=IW_ENC_CAPA_CIPHER_CCMP;
    range->enc_capa|=IW_ENC_CAPA_WPA2;

    and compile the driver. Hope this clears everything...

  10. #10
    Stormadvisor NNTP User

    Default Re: Yes indeed, my wireless isn't working yet.

    I was able to get it worked out without much needed help. I forget which post it was. My sound was very low. I went to Yast, hardware, sound and selected my sound card (pretty easy. It was the only one listed) which is a "82801H (ICH8 Family) HD AudioController" . I then selected the "Other" and "sound". At this point I cranked everything up and VIOLA, I could hear!

Posting Permissions

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