, Paolo Bettini wrote:
Hi , i am Paolo and i installed Debian stretch on my ezbook2 . One
problem is the wifi , the card a SDIO device , seems to be 02d0:a9a6
linux id or Broadcom AP6212 for windowsi installed deb package
firmware-brcm80211 and nvram sdio txt in /lib/firmware/brcm,
reloaded
, Paolo Bettini wrote:
Hi , i am Paolo and i installed Debian stretch on my ezbook2 . One
problem is the wifi , the card a SDIO device , seems to be 02d0:a9a6
linux id or Broadcom AP6212 for windowsi installed deb package
firmware-brcm80211 and nvram sdio txt in /lib/firmware/brcm,
reloaded
Paolo and i installed Debian stretch on my ezbook2 . One
problem is the wifi , the card a SDIO device , seems to be 02d0:a9a6
linux id or Broadcom AP6212 for windowsi installed deb package
firmware-brcm80211 and nvram sdio txt in /lib/firmware/brcm, reloaded
bcrmfmac module but nothing the card
on my ezbook2 . One
problem is the wifi , the card a SDIO device , seems to be 02d0:a9a6
linux id or Broadcom AP6212 for windowsi installed deb package
firmware-brcm80211 and nvram sdio txt in /lib/firmware/brcm, reloaded
bcrmfmac module but nothing the card seems invisible or dead i don't
know
wrote:
>>> Arend van Spriel ha scritto:
>>>> + linux-wireless On 07-08-17 21:38, Paolo Bettini wrote:
>>>>> Hi , i am Paolo and i installed Debian stretch on my ezbook2 . One
>>>>> problem is the wifi , the card a SDIO device , seems to be 02d0:a9a6
>>
+ linux-wireless
+ Larry
please keep linux-wireless in this thread.
On 08-08-17 08:21, Paolo Bettini wrote:
> Arend van Spriel ha scritto:
>> + linux-wireless On 07-08-17 21:38, Paolo Bettini wrote:
>>> Hi , i am Paolo and i installed Debian stretch on my ezbook2 . One
>&
+ linux-wireless
On 07-08-17 21:38, Paolo Bettini wrote:
> Hi , i am Paolo and i installed Debian stretch on my ezbook2 . One
> problem is the wifi , the card a SDIO device , seems to be 02d0:a9a6
> linux id or Broadcom AP6212 for windowsi installed deb package
> firmware-brcm802
On Sat, 2016-07-23 at 06:26 -0700, Christopher Williamson wrote:
> Quick follow-up - I suspected the issue may be with wpa_supplicant
> rather than udev / kernel config.
>
> Since this does connect properly on open wireless networks the issue
> is now only with WPA/WPA2.
>
> It seems even the
Quick follow-up - I suspected the issue may be with wpa_supplicant
rather than udev / kernel config.
Since this does connect properly on open wireless networks the issue
is now only with WPA/WPA2.
It seems even the latest dev builds of Ubuntu are still stuck using
wpa_supplicant 2.4.x rather
Just to follow up on this - I performed a minimal ubuntu server
install (16.04.1), commented out the crda udev rule (since that was
setting the weird country: 98 issue) and tried again and it still
didn’t work.
I did confirm that the md5 sums for the firmware included with Arch is
the exact same
Hi all,
So I decided to have another fiddle with this and managed to get the
WiFi working perfectly first time on an ArchLinux LiveCD so it looks
like this issue is Ubuntu specific.
I’m going to copy the firmware files and check if they’re responsible
and work my way through the various
I haven’t managed to get connected to a WPA network either so it looks
like open only at the moment but I fear that may just have been a
fluke.
A big problem I’m facing is that editing /etc/default/crda to
REGDOMAIN=GB wasn’t enough to set the wifi regulation mode to GB and I
have to set it
Disregard - I have actually managed to get this to connect to a open network!
# iw reg set GB
# iw reg get
country GB: DFS-ETSI
(2402 - 2482 @ 40), (N/A, 20), (N/A)
(5170 - 5250 @ 80), (N/A, 20), (N/A)
(5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS
(5490 - 5710 @ 160),
Ok so I created a guest wifi network without any encryption enabled at
all and the client still refuses to connect.
Again, the connection is made perfectly using the USB dongle I have
but not the built in libertas sd8686 chipset.
I do currently use pfSense as a firewall box behind my wireless
Hi Dan,
I will check out the WPA2 vs WPA vs open wireless thing in a few mins.
For now though - the iwlist scan results for both a USB device and the
libertas device:
USB: http://termbin.com/hdwl
Libertas: http://termbin.com/jxh7
Will follow up shortly with WPA and Open network configs.
On Fri, 2016-07-22 at 01:48 -0700, Christopher Williamson wrote:
> Looking through the log lines I see gaps between what WPA is doing
> and what
> dmesg reports and figured this is because of the libertas debugging
> level
> so I’ve set that to 0xfff (for libertas) and created a combined
> log
Looking through the log lines I see gaps between what WPA is doing and what
dmesg reports and figured this is because of the libertas debugging level
so I’ve set that to 0xfff (for libertas) and created a combined log of
the events from both sources labelled with either [wpa] or [dmesg] and
I was thinking about redirecting the wpa logging to syslog but figured
I’d take the lazy way out by abusing curl:
curl -s http://termbin.com/cx0e http://termbin.com/bvdj | sort
Resulting combined log file:
http://termbin.com/909y
Christopher Williamson
On 22 July 2016 at 09:09:59, Arend Van
On 22-7-2016 0:00, Christopher Williamson wrote:
> I’ve created cleaner logs (particularly the dmesg one) and have added
> timestamps line-by-line to both so it should be easier to track
> between the two log files:
>
> wpa_supplicant:
> http://termbin.com/cx0e
>
> dmesg | grep libertas:
>
I’ve created cleaner logs (particularly the dmesg one) and have added
timestamps line-by-line to both so it should be easier to track
between the two log files:
wpa_supplicant:
http://termbin.com/cx0e
dmesg | grep libertas:
http://termbin.com/bvdj
Christopher Williamson
On 21 July 2016 at
Sure!
wpa_supplicant logs:
http://termbin.com/z1hg
dmesg logs (grepped for libertas):
http://termbin.com/7rt5
Christopher Williamson
On 21 July 2016 at 21:38:26, Dan Williams
(d...@redhat.com(mailto:d...@redhat.com)) wrote:
> On Thu, 2016-07-21 at 11:55 -0700, Christopher Williamson
On Thu, 2016-07-21 at 11:55 -0700, Christopher Williamson wrote:
> Just to confirm - I can connect to the same network using the same
> configurations using a USB wifi adapter I tried.
Can you grab simultaneous driver debug logging and supplicant debug
logging? Unfortunately the 'status 1' is an
Just to confirm - I can connect to the same network using the same
configurations using a USB wifi adapter I tried.
Unfortunately it’s not ideal since the point of the Viliv N5 is that
it’s ultra portable so I would really like to get the inbuilt wifi
card working.
It seems odd that
Sure, here are the results:
http://termbin.com/e8e2
Christopher Williamson
On 21 July 2016 at 16:37:24, Dan Williams
(d...@redhat.com(mailto:d...@redhat.com)) wrote:
> On Wed, 2016-07-20 at 15:16 -0700, Christopher Williamson wrote:
> > I used NetworkManager in the previous test.
> >
> > This
On Wed, 2016-07-20 at 15:16 -0700, Christopher Williamson wrote:
> I used NetworkManager in the previous test.
>
> This time around I have used wpa_supplicant directly and get the
> following results:
>
> http://termbin.com/j8ea
>
> Thought I’d throw them on a pastebin since it’s over 700
Tried a few more things worth mentioning:
- Tried connecting with wpa_supplicant & dhclient only but sadly
wpa_supplicant still cannot seem to hold a connection to the base
station.
It looks like the relevant errors here may be:
ioctl[SIOCSIWENCODEEXT]: Invalid argument
wlan0: Trying to
I used NetworkManager in the previous test.
This time around I have used wpa_supplicant directly and get the
following results:
http://termbin.com/j8ea
Thought I’d throw them on a pastebin since it’s over 700 lines.
Christopher Williamson
On 20 July 2016 at 22:50:34, Dan Williams
On Wed, 2016-07-20 at 13:06 -0700, Christopher Williamson wrote:
> Hi Dan,
>
> Ah - yeah I hadn’t thought it may be a kernel build option. I’ve now
> built that and dmesg is a much more lively place!
>
> I’ve provided output logs for both when the device is connected and
> when a connection
Hi Dan,
Ah - yeah I hadn’t thought it may be a kernel build option. I’ve now
built that and dmesg is a much more lively place!
I’ve provided output logs for both when the device is connected and
when a connection attempt is made - hopefully this is useful.
When I first connect the device:
On Wed, 2016-07-20 at 02:53 -0700, Christopher Williamson wrote:
> Just following up from my previous email:
>
> I am actually setting the reg domain using: iw reg set GB
> (copy/pasted
> the IN from elsewhere - oops!)
>
> As for progress, however, I have tried the following:
>
> - setting the
Just following up from my previous email:
I am actually setting the reg domain using: iw reg set GB (copy/pasted
the IN from elsewhere - oops!)
As for progress, however, I have tried the following:
- setting the debug level to 0xfff. This still produces no
additional output even with 8 set
So I’ve now disabled IPv6 and have set the GB (Great Britain)
regulation code using:
iw reg set IN
Now when I try to connect to the network using wicd the system seems
to crash - I guess at least it’s doing something more than just asking
for the password again like it did with NetworkManager
Absolutely!
With the debug logging enabled I got the following:
Connecting the device initially with debug enabled:
[ 205.302685] libertas_sdio: Libertas SDIO driver
[ 205.302698] libertas_sdio: Copyright Pierre Ossman
[ 205.503465] cfg80211: World regulatory domain updated:
[ 205.503478]
On Tue, 2016-07-19 at 12:06 -0400, Christopher Williamson wrote:
> Hi everyone!
>
> I’ve just got myself a Viliv N5 and am trying to get the integrated
> Wifi chipset working on it.
>
> I am able to see networks around me but any attempts to connect them
> appear to time out and fail.
>
> I
Hi everyone!
I’ve just got myself a Viliv N5 and am trying to get the integrated
Wifi chipset working on it.
I am able to see networks around me but any attempts to connect them
appear to time out and fail.
I have filed a linux kernel bug related to this issue:
35 matches
Mail list logo
