From owner-freebsd-wireless@freebsd.org Mon Nov 16 08:38:49 2015 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E7E5FA302BE for ; Mon, 16 Nov 2015 08:38:49 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D127312C1 for ; Mon, 16 Nov 2015 08:38:49 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id tAG8cnbb087502 for ; Mon, 16 Nov 2015 08:38:49 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 203745] A2DP Support for Bluetooth Headphone Audio Date: Mon, 16 Nov 2015 08:38:49 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: hselasky@FreeBSD.org X-Bugzilla-Status: In Progress X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Nov 2015 08:38:50 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203745 --- Comment #23 from Hans Petter Selasky --- Forwarding message from Nathanial Sloss: > AFAICT the only reason as to why auto config would fail would be if the max > bitpool value that is calculated is smaller than the minimum bit pool value. > > This is possibile on some headphones/speakers bta2dpd has the -B switch so the > user can set the max bitpool value. Is there hci dump on freebsd as seeing > the output of getConfiguration will confirm this. Otherwize increasing > DEFAULT_MAXBITPOOL from 80 to say 160 in sbc_encode.h might work for his > headphones but I am at a loss as to whether this will effect others. The > problem stems from the fact that different manufacturers specify different > encoding ranges and I've made it use the highest possible value as this will > give the best quality but in some cases the headphones will report a bitpool > range of 2-253 but if you encode the audio at 253 you wont get any playback > and most android/linux will just use 36 and this wont work with some > headphones or sound bad. Tony: Could you try to change the definition of DEFAULT_MAXBITPOOL? --HPS -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-wireless@freebsd.org Fri Nov 20 03:56:24 2015 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7F9E0A32EDE for ; Fri, 20 Nov 2015 03:56:24 +0000 (UTC) (envelope-from serge0x76@gmail.com) Received: from mail-qk0-x235.google.com (mail-qk0-x235.google.com [IPv6:2607:f8b0:400d:c09::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3DE681E8B for ; Fri, 20 Nov 2015 03:56:24 +0000 (UTC) (envelope-from serge0x76@gmail.com) Received: by qkas77 with SMTP id s77so33125928qka.0 for ; Thu, 19 Nov 2015 19:56:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=7h7CM+WsfkIBeT4hPIVeWgiAp6Qy8/iDxHt3X9BqDCY=; b=sQngt9jO7ORDxX0d7AXWaw+pSKVLfzl747f7MeBnBIVg9z2i05L5hXkPozG++9M+t1 wBC1F/OwRj1K5H1RqAZDEMdISiwiWx9oC/huTdAMsfOUrYG/MUB3uSubHUViHq3Q6Rvq S1npsxtwzt/f5rhgYdlThRJOKlwRIlz/qbeVuZrLREKfuegHNWHj8bem1ySnzJl8aIIW 7i4xaHDLwpa/i/1BA/wtu/OTiUS0DVWRc+z3pj6rqB/62BI9/a3BmHgYV5nQBcEKWB/W HLzDLcF6acSXGYwRYHSGS4F4EqIEyRtlffnYHQQWCNNYtlwFbyJXNhRHmkcCSS9jP7xV veCA== MIME-Version: 1.0 X-Received: by 10.55.21.65 with SMTP id f62mr10932486qkh.46.1447991783112; Thu, 19 Nov 2015 19:56:23 -0800 (PST) Received: by 10.55.179.2 with HTTP; Thu, 19 Nov 2015 19:56:23 -0800 (PST) Date: Thu, 19 Nov 2015 22:56:23 -0500 Message-ID: Subject: USB WiFi works only after cold reboot From: Serge Voilokov To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Nov 2015 03:56:24 -0000 Hi, I have a problem on Raspberry PI-A with Realtek WiFi adapter. After reboot on watchdog or kernel panic wifi doesn't init properly. Sometimes wlan0 is not created, sometimes ethernet address is ff:ff:ff:ff:ff:ff, firmware loading errors, etc. After cold reboot it works file. How can I avoid the cold reboot? Now on boot I do several attempts of 'usbconfig reset' until wifi starts working. It doesn't seem reliable. Is the other way to make cold reset of usb and/or wifi without rebooting the OS? Thanks, --serge From owner-freebsd-wireless@freebsd.org Fri Nov 20 04:36:33 2015 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 46D1EA3378E for ; Fri, 20 Nov 2015 04:36:33 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-io0-x229.google.com (mail-io0-x229.google.com [IPv6:2607:f8b0:4001:c06::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 095FF1C83 for ; Fri, 20 Nov 2015 04:36:33 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by iouu10 with SMTP id u10so114156502iou.0 for ; Thu, 19 Nov 2015 20:36:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=M5WLtBjGGHNOPbajwVGpa+aRvvJkTtckaD8+hBoyO1U=; b=zEvhSojnv5j9VIqh04Vg+JsM4Dff/fLYCvbYRmve3mRF1nwM3lNqKJreBeqUxS8Kpv U6mx3VGtLI0JNa/FMEeTO9o8K5dk83kQx2zbqPqdILbioVH4Z9nb3Q5kC315S77rwokv VWbb99pXlAU9cG95lOKCkh8k0H9/1AqEzmN638cGtAM7CkVekEJc+zURejWs0Afmj9ms GqJfioJpisQ43Cz2wksY4u2ljhiEdr73KCgymwJn/6XE0ebzBuuNr4ZxfZEchEmUDioC xfnhs7IqOF4pEu3Bn0eQz+Qu6s0/7EvJ8J9Qa3tpKibF6N2G88nZvwOFhB/xS/VNYBjb 0MTw== MIME-Version: 1.0 X-Received: by 10.107.162.21 with SMTP id l21mr11341289ioe.123.1447994192294; Thu, 19 Nov 2015 20:36:32 -0800 (PST) Received: by 10.36.217.196 with HTTP; Thu, 19 Nov 2015 20:36:32 -0800 (PST) In-Reply-To: References: Date: Thu, 19 Nov 2015 20:36:32 -0800 Message-ID: Subject: Re: USB WiFi works only after cold reboot From: Adrian Chadd To: Serge Voilokov Cc: "freebsd-wireless@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Nov 2015 04:36:33 -0000 It looks like it's reading some invalid data via the EEPROM. I've seen it do it yet and I haven't sat down to figure it out. Which device is it? -a On 19 November 2015 at 19:56, Serge Voilokov wrote: > Hi, > > I have a problem on Raspberry PI-A with Realtek WiFi adapter. > After reboot on watchdog or kernel panic wifi doesn't init properly. > Sometimes wlan0 is not created, sometimes ethernet address is > ff:ff:ff:ff:ff:ff, firmware loading errors, etc. > > After cold reboot it works file. > > How can I avoid the cold reboot? > Now on boot I do several attempts of 'usbconfig reset' until wifi > starts working. > It doesn't seem reliable. > Is the other way to make cold reset of usb and/or wifi without rebooting the OS? > > Thanks, > --serge > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" From owner-freebsd-wireless@freebsd.org Fri Nov 20 04:57:37 2015 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8BD1AA33ADB for ; Fri, 20 Nov 2015 04:57:37 +0000 (UTC) (envelope-from serge0x76@gmail.com) Received: from mail-qk0-x230.google.com (mail-qk0-x230.google.com [IPv6:2607:f8b0:400d:c09::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4118E124F for ; Fri, 20 Nov 2015 04:57:37 +0000 (UTC) (envelope-from serge0x76@gmail.com) Received: by qkas77 with SMTP id s77so33426260qka.0 for ; Thu, 19 Nov 2015 20:57:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=aPMeQM+QZvzFhkMCtPtzqKQz5MFY/cBrCuUJ+zO1wCk=; b=mbRFJnogFiDbKMy1+90FufgrZGIDQO9g6Q/TB0oxSdPFGBmZLlyCou7megI7rVG72w rb/JdCwPSITfrbbZNf1rTxOFnVzEuldLstS+LvMVT2yYJuE93nbYap09tRPQR+7yZPbw bWNBCP9Z4ue7cYNPx/WvUmlYa5dftMkAaO9T9lz/as/wd9rwIdT06r5T6SfglZ5diIEj 3jEpJwwS/mHAw4n+na6tEjphXpxyBVfqUBKiThkvULqc8Li+RT6fZU/LvUXGxmdd5ZdV fzN+Y9EPt5vncLcTn5Q+ZIcisU1OuwtCrXMrnMbRnX7/Fk1e0OWtMr1DSCntoIUcJNTE xGig== MIME-Version: 1.0 X-Received: by 10.55.40.211 with SMTP id o80mr11005417qko.93.1447995456353; Thu, 19 Nov 2015 20:57:36 -0800 (PST) Received: by 10.55.179.2 with HTTP; Thu, 19 Nov 2015 20:57:36 -0800 (PST) In-Reply-To: References: Date: Thu, 19 Nov 2015 23:57:36 -0500 Message-ID: Subject: Re: USB WiFi works only after cold reboot From: Serge Voilokov To: Adrian Chadd Cc: "freebsd-wireless@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Nov 2015 04:57:37 -0000 Realtek: urtwn0: on usbus0 urtwn0: MAC/BB RTL8188CUS, RF 6052 1T1R From: https://www.adafruit.com/products/814 On Thu, Nov 19, 2015 at 11:36 PM, Adrian Chadd wrote: > It looks like it's reading some invalid data via the EEPROM. I've seen > it do it yet and I haven't sat down to figure it out. > > Which device is it? > > > -a > > > On 19 November 2015 at 19:56, Serge Voilokov wrote: >> Hi, >> >> I have a problem on Raspberry PI-A with Realtek WiFi adapter. >> After reboot on watchdog or kernel panic wifi doesn't init properly. >> Sometimes wlan0 is not created, sometimes ethernet address is >> ff:ff:ff:ff:ff:ff, firmware loading errors, etc. >> >> After cold reboot it works file. >> >> How can I avoid the cold reboot? >> Now on boot I do several attempts of 'usbconfig reset' until wifi >> starts working. >> It doesn't seem reliable. >> Is the other way to make cold reset of usb and/or wifi without rebooting the OS? >> >> Thanks, >> --serge >> _______________________________________________ >> freebsd-wireless@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-wireless >> To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" From owner-freebsd-wireless@freebsd.org Fri Nov 20 23:08:01 2015 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EC987A33297 for ; Fri, 20 Nov 2015 23:08:01 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BF5A213D5 for ; Fri, 20 Nov 2015 23:08:01 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id tAKN81MI059998 for ; Fri, 20 Nov 2015 23:08:01 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 204228] wlan interface cannot connect to AP if_iwm driver - Intel Dual Band Wireless AC 3160 Date: Fri, 20 Nov 2015 23:08:02 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: news@saz.gr X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Nov 2015 23:08:02 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204228 Fotis Zabaras changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |news@saz.gr --- Comment #1 from Fotis Zabaras --- Hello Stefan, I jsut got an intel 7260.hmwwb.r today and I got the same problem. On my AP setup I had my ssid hidden. When I made it public I managed to associate with wpa_supplicant(but it shows 11g, havent tried speedtests yes) I guess it is a probe problem and it cannot verify the hidden SSID even if you add the line scan_ssid=1 on wpa_supplicant.conf Hope than helps Fotis P.S. dmesg and ifconfing wlan0: # dmesg|grep 7260 iwm0: mem 0xf7c00000-0xf7c01fff irq 19 at device 0.0 on pci2 # ifconfig wlan0 wlan0: flags=8843 metric 0 mtu 1500 ether 7c:5c:f8:2f:15:8e inet 192.168.1.62 netmask 0xffffff00 broadcast 192.168.1.255 nd6 options=29 media: IEEE 802.11 Wireless Ethernet OFDM/36Mbps mode 11g status: associated ssid TEST channel 6 (2437 MHz 11g) bssid country US authmode WPA2/802.11i privacy ON deftxkey UNDEF AES-CCM 2:128-bit txpower 0 bmiss 10 scanvalid 60 protmode CTS wme roaming MANUAL groups: wlan -- You are receiving this mail because: You are the assignee for the bug.