Adrian Chadd wrote:
> Right, you need to create the interface:
>
> ifconfig wlan0 create wlandev iwn0
>
> then run wpa_spuplicant
>
> (or do it all in /etc/rc.conf .. :)
That seems to work. There seems to be something configured wrong for
wpa_supplicant but WLAN does react.
Thank you for a
On 3/1/16, Carsten Kunze wrote:
> Conrad Meyer wrote:
>
>> "[1] iwn0: mem 0xf7b0-0xf7b01fff
>> irq 18 at device 0.0 on pci3" is fine; "module iwn already present!"
>> is fine.
>>
>> What makes you say it isn't recognized or doesn't work?
>
> ifconfig iwn0 says "interface iwn0 does not e
Conrad Meyer wrote:
> "[1] iwn0: mem 0xf7b0-0xf7b01fff
> irq 18 at device 0.0 on pci3" is fine; "module iwn already present!"
> is fine.
>
> What makes you say it isn't recognized or doesn't work?
ifconfig iwn0 says "interface iwn0 does not exist". Also starting
wpa_supplicant doesn
Right, you need to create the interface:
ifconfig wlan0 create wlandev iwn0
then run wpa_spuplicant
(or do it all in /etc/rc.conf .. :)
-a
On 1 March 2016 at 14:13, Carsten Kunze wrote:
> Adrian Chadd wrote:
>
>> sysctl net.wlan.devices
>>
>> iwn0 no longer shows up in ifconfig -a .
>>
>>
Adrian Chadd wrote:
> sysctl net.wlan.devices
>
> iwn0 no longer shows up in ifconfig -a .
>
>
> -a
Ok, "sysctl -a|grep iwn" gives quite some output.
Actually I tried to start wpa_supplicant, but WLAN didn't react. Then--just
for testing--I wrote "ifconfig iwn0 up", where ifconfig reported
sysctl net.wlan.devices
iwn0 no longer shows up in ifconfig -a .
-a
On 1 March 2016 at 13:42, Conrad Meyer wrote:
> "[1] iwn0: mem 0xf7b0-0xf7b01fff
> irq 18 at device 0.0 on pci3" is fine; "module iwn already present!"
> is fine.
>
> What makes you say it isn't recognized or doesn't wor
"[1] iwn0: mem 0xf7b0-0xf7b01fff
irq 18 at device 0.0 on pci3" is fine; "module iwn already present!"
is fine.
What makes you say it isn't recognized or doesn't work?
On Tue, Mar 1, 2016 at 1:01 PM, Carsten Kunze wrote:
> Conrad Meyer wrote:
>
>> kldload iwn6000fw, iwn6000g2afw, iwn6000g2b
Conrad Meyer wrote:
> kldload iwn6000fw, iwn6000g2afw, iwn6000g2bfw.
This or edit loader.conf doesn't help, all these things had already been in the
kernel. dmesg stays the same.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/
kldload iwn6000fw, iwn6000g2afw, iwn6000g2bfw.
On Tue, Mar 1, 2016 at 12:48 PM, Carsten Kunze wrote:
> Larry Rosenman wrote:
>
>> Did you load the iwn firmware?
>
> How do I do this?
>
> I put "if_iwn_load="YES"" into /boot/loader.conf, now I get
> "module iwn already present!" in dmesg...
> ___
On 2016-03-01 14:48, Carsten Kunze wrote:
Larry Rosenman wrote:
Did you load the iwn firmware?
How do I do this?
I put "if_iwn_load="YES"" into /boot/loader.conf, now I get
"module iwn already present!" in dmesg...
___
freebsd-current@freebsd.org
Larry Rosenman wrote:
> Did you load the iwn firmware?
How do I do this?
I put "if_iwn_load="YES"" into /boot/loader.conf, now I get
"module iwn already present!" in dmesg...
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailm
On 2016-03-01 12:23, Carsten Kunze wrote:
Joe Nosay wrote:
Is the card removable? If so, have you tried plugging in one that
would
have the driver already included with the base - so to speak - system?
Have
you tried the card in another computer/laptop?
It is an integrated card. Theoretic
Joe Nosay wrote:
> Is the card removable? If so, have you tried plugging in one that would
> have the driver already included with the base - so to speak - system? Have
> you tried the card in another computer/laptop?
It is an integrated card. Theoretical it is removeable, but this is by design
Is the card removable? If so, have you tried plugging in one that would
have the driver already included with the base - so to speak - system? Have
you tried the card in another computer/laptop?
On Tue, Mar 1, 2016 at 10:47 AM, Carsten Kunze
wrote:
> Hello,
>
> the WLAN hardware of my Dell E6540
14 matches
Mail list logo
