Page 2 of 4 FirstFirst 1234 LastLast
Results 11 to 20 of 38

Thread: Proprietary wireless driver problems

  1. #11
    Join Date
    Aug 2005
    Location
    South Carolina, USA
    Beans
    23,506
    Distro
    Ubuntu 17.10 Artful Aardvark

    Re: Proprietary wireless driver problems

    $ apt-get autoremove
    E: Could not open lock file /var/lib/dpkg/lock - open (13: Permission denied)
    E: Unable to lock the administration directory (/var/lib/dpkg/), are you root?
    Please try:
    Code:
    sudo apt-get autoremove
    Then go on to the firmware part.
    "Oh, Ubuntu, you are my favorite Linux-based operating system" --Dr. Sheldon Cooper, Ph.D.

  2. #12
    Join Date
    Jul 2012
    Beans
    14

    Re: Proprietary wireless driver problems

    Code:
    sudo apt-get remove --purge bcmwl-kernel-source
    Gave me this
    Code:
    Reading package lists... Done
    Building dependency tree
    Reading state information... Done
    Package bcmwl-kernel-source is not installed,so not removed
    0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
    After typing this
    Code:
    dmesg | grep wlan
    rfkill list all
    I got
    Code:
    [31.563886] ADDRCONF(NETDEV_UP):wlan0: link is not ready
    [31.565928] ADDRCONF(NETDEV_UP):wlan0: link is not ready
    and
    Code:
    0: hci0:Bluetooth
    Soft blocked: no
    Hard blocked: no
    1: hp-wifi:Wireless LAN
    Soft blocked: no
    Hard blocked: no
    2: hp-bluetooth: Bluetooth
    Soft blocked: no
    Hard blocked: no
    3: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no

  3. #13
    Join Date
    Aug 2005
    Location
    South Carolina, USA
    Beans
    23,506
    Distro
    Ubuntu 17.10 Artful Aardvark

    Re: Proprietary wireless driver problems

    Are those readings after you did:
    Reboot and let us have your report.
    ??
    "Oh, Ubuntu, you are my favorite Linux-based operating system" --Dr. Sheldon Cooper, Ph.D.

  4. #14
    Join Date
    Jul 2012
    Beans
    8

    Re: Proprietary wireless driver problems

    Hi,
    Done that and this is where we're at:
    dirkzobb@dirkzobb-HP-Compaq-nx6325-RU594ES-ABU:~$ sudo apt-get autoremove
    Reading package lists... Done
    Building dependency tree
    Reading state information... Done
    The following packages will be REMOVED:
    dkms fakeroot patch
    0 upgraded, 0 newly installed, 3 to remove and 2 not upgraded.
    After this operation, 890 kB disk space will be freed.
    Do you want to continue [Y/n]? y
    (Reading database ... 167868 files and directories currently installed.)
    Removing dkms ...
    Removing fakeroot ...
    update-alternatives: using /usr/bin/fakeroot-tcp to provide /usr/bin/fakeroot (fakeroot) in auto mode.
    Removing patch ...
    Processing triggers for man-db ...

    What next?

  5. #15
    Join Date
    Aug 2005
    Location
    South Carolina, USA
    Beans
    23,506
    Distro
    Ubuntu 17.10 Artful Aardvark

    Re: Proprietary wireless driver problems

    Quote Originally Posted by Dirkzobb View Post
    Hi,
    Done that and this is where we're at:

    What next?
    Please confirm you did do the firmware part.
    Code:
    dmesg | grep -e wlan -e b43
    ls /lib/firmware/b43
    Thanks.
    "Oh, Ubuntu, you are my favorite Linux-based operating system" --Dr. Sheldon Cooper, Ph.D.

  6. #16
    Join Date
    Jul 2012
    Beans
    14

    Re: Proprietary wireless driver problems

    Quote Originally Posted by chili555 View Post
    Are those readings after you did:
    Reboot and let us have your report.
    ??
    Was this meant for me?
    The same thing comes up after rebooting

  7. #17
    Join Date
    Aug 2005
    Location
    South Carolina, USA
    Beans
    23,506
    Distro
    Ubuntu 17.10 Artful Aardvark

    Re: Proprietary wireless driver problems

    Quote Originally Posted by Peripetilja View Post
    Was this meant for me?
    The same thing comes up after rebooting
    That's the price I pay for trying to juggle two different cases in one thread. Sorry.

    Peri, your case is brcmsmac. Please let me see:
    Code:
    sudo iwlist wlan0 scan
    "Oh, Ubuntu, you are my favorite Linux-based operating system" --Dr. Sheldon Cooper, Ph.D.

  8. #18
    Join Date
    Jul 2012
    Beans
    14

    Re: Proprietary wireless driver problems

    Nah, it's not your fault, Dirkzobb invaded my thread
    What does "brcmsmac" stand for?

    Code:
    sudo iwlist wlan0 scan
    Gave me this
    Code:
    wlan0        Scan completed:
                 Cell 01-Adress:00:1D:68:FB:FE:18
                 Channel:1
                 Frequency:2.412 GHz (Channel:1)
                 Quality=36/70 Signal level=-74 dBm
                 Encryption key:on
                 ESSID:"/*censured(name of my network)*/"
                 Bit Rates:1Mb/s; 2Mb/s;5.5Mb/s; 11 Mb/s; 18Mb/s
                           24Mb/s; 36Mb/s; 54 Mb/s
                 Bit Rates:6Mb/s; 9Mb/s;12Mb/s; 48Mb/s
                 Mode:Master
                 Extra:tsf=000000ef2b4ae376
                 Extra: Last beacon: 784ms ago
                 IE:Unknown:0007666C656B696361
                 IE:Unknown:010882848B962430486C
                 IE:Unknown:030101
                 IE:Unknown:2A0100
                 IE:Unknown:2F0100
                 IE:Unknown:32040C121860
                 IE:Unknown:DD060010180200F0
                  IE:Unknown:DD180050F2020101880003A400042435E0062322F00

  9. #19
    Join Date
    Aug 2005
    Location
    South Carolina, USA
    Beans
    23,506
    Distro
    Ubuntu 17.10 Artful Aardvark

    Re: Proprietary wireless driver problems

    What does "brcmsmac" stand for?
    It's just the next name in the long line of Broadcom drivers. I'm not aware that it stands for anything in particular aside from the brcm part that seems to refer to Broadcom.

    Your signal strength is a bit low:
    Quality=36/70
    However, if the driver and hardware can scan it, Network Manager ought to list it as an available network. Does it? Does it try to connect?
    "Oh, Ubuntu, you are my favorite Linux-based operating system" --Dr. Sheldon Cooper, Ph.D.

  10. #20
    Join Date
    Jul 2012
    Beans
    14

    Re: Proprietary wireless driver problems

    It is quite silly that the signal is so low because the modem is right next to my laptop..
    The manager can see my network, tries to connect and succeeds 1 out of 100 tries and lasts about 1/2 minutes

Page 2 of 4 FirstFirst 1234 LastLast

Tags for this Thread

Bookmarks

Posting Permissions

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