<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    This might be a good bug report to consider<br>
    <br>
    <a class="moz-txt-link-freetext" href="https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1419341">https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1419341</a><br>
    <br>
    Various respondents have suggested either a bios upgrade or possible
    hardware issues. The person who posted the bug report used a USB
    extension cord with his usb wifi modem, without success.  I doubt
    that the problem is hardware related, since your lsusb confirms the
    wifi's existence.<br>
    <br>
    Drivers and commands for your peripheral might be found in newer
    kernels. The command 'uname -r' will give your computer's kernel
    version.  A newer kernel (I'm on 4.6.x, which is stable) can be
    compiled independently or downloaded through repository.  Google
    'canonical-kernel-team' for instructions on how to use a ppa to
    obtain newer kernels by repository.  <br>
    <br>
    Thanks,<br>
    Jordan <br>
    <br>
    <div class="moz-cite-prefix">On 07/10/2016 05:59 PM, Teresa Binstock
      wrote:<br>
    </div>
    <blockquote cite="mid:5782C532.8070403@q.com" type="cite">
      <meta http-equiv="content-type" content="text/html;
        charset=windows-1252">
      <div class="moz-forward-container">see below.<br>
        <div class="moz-forward-container"><br>
          <br>
          <br>
          <div dir="ltr">
            <div class="gmail_quote">
              <div dir="ltr">Teresa Binstock <<a
                  moz-do-not-send="true" href="mailto:tcbinstock@q.com"><a class="moz-txt-link-abbreviated" href="mailto:tcbinstock@q.com">tcbinstock@q.com</a></a>>

                schrieb am So., 10. Juli 2016 um 16:16 Uhr:<br>
              </div>
              <blockquote class="gmail_quote" style="margin:0 0 0
                .8ex;border-left:1px #ccc solid;padding-left:1ex">
                <div bgcolor="#FFFFFF" text="#000000">
                  <p>A verified PAU05 purchaser (Amazon) said he had
                    success installing Xubu with the PAU05, and a
                    Panda-help tech (after my lament) installed Xubu
                    14,04.4 on an in-house computer using the PAU05 and
                    was successful. Installing 14.04.4 on my dv7t seems
                    to reset "<span>1: brcmwl-0: Wireless LAN" to "Hard
                      blocked: yes", and that setting was resistant to
                      change on my computer. {<a moz-do-not-send="true"
href="http://www.samundra.com.np/unblock-disabled-wireless-card-in-ubuntu/1125"
                        target="_blank">http://www.samundra.com.np/unblock-disabled-wireless-card-in-ubuntu/1125</a>}<br>
                    </span></p>
                  <p><span>Mt dv7t has no finger accessible Wifi switch,
                      and the dv7t continued to use the PAU05 while
                      running W7. From dv7t:</span></p>
                  <p><span>tcb@dv7C:~$ rfkill list all<br>
                      0: phy0: Wireless LAN<br>
                          Soft blocked: no<br>
                          Hard blocked: no<br>
                      1: brcmwl-0: Wireless LAN<br>
                          Soft blocked: no<br>
                          <font color="#990000">Hard blocked: yes
                        <-------</font><br>
                      2: phy1: Wireless LAN<br>
                          Soft blocked: no<br>
                          Hard blocked: no</span></p>
                </div>
              </blockquote>
              <div><br>
              </div>
              <div>Post the output of:</div>
              <div>  lsusb # in a Terminal </div>
              <div><br>
              </div>
              <div>"brcmwl" looks like a Broadcom chipset. AFAIK they
                always need firmware BLOBs.</div>
              <div><br>
              </div>
              <div>Also might give you an idea what went wrong:</div>
              <div>  dmesg | grep -i wifi<br>
                <br>
                ----<br>
                <br>
                My dv7t now boots into W7 and Mint 17.3.<br>
                <br>
                tcb@dv ~ $ lsusb #<br>
                Bus 002 Device 002: ID 064e:c107 Suyin Corp. HP webcam
                [dv6-1190en]<br>
                Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0
                root hub<br>
                Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1
                root hub<br>
                Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1
                root hub<br>
                Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1
                root hub<br>
                Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1
                root hub<br>
                Bus 001 Device 003: ID 148f:5372 Ralink Technology,
                Corp. RT5372 Wireless Adapter<br>
                Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0
                root hub<br>
                Bus 004 Device 002: ID 046d:c52b Logitech, Inc. Unifying
                Receiver<br>
                Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1
                root hub<br>
                Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1
                root hub<br>
                tcb@dv ~ $ <br>
                <br>
                tcb@dv ~ $ dmesg | grep -i wifi<br>
                tcb@dv ~ $ sudo dmesg | grep -i wifi<br>
                [sudo] password for tcb: <br>
                tcb@dv ~ $ <br>
                <br>
                <br>
              </div>
              <div><br>
              </div>
            </div>
          </div>
        </div>
        <br>
      </div>
      <br>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
    </blockquote>
    <br>
  </body>
</html>