From: Yury Chumak <sfynkx@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] Wifi Firmware "does not exist", but it does.
Date: Tue, 21 Mar 2023 13:24:41 +0200 [thread overview]
Message-ID: <CAOe=0deFOicB5PaotC5w9p52Sr=TjvWStgD6siuah=joLUANVA@mail.gmail.com> (raw)
In-Reply-To: <b50a5980-869c-99d9-9d72-72ccaa5ec010@posixcafe.org>
Same situation with the same wifi-card.
% pci -v
...
3.0.0: net 02.80.00 8086/08b1 4 0:a3100004 8192
Intel Corporation Wireless 7260
Firmware added and kernel rebuilded. Command:
% aux/wpa -p2 -s vega3 /net/ether1
asking password, returns '!' and exits. But next command ip/ipconfig returns:
ipconfig: no success with DHCP
DHCP is ok. It works good with other devices. DHCP-logs on server side
have not requests with wifi-card mac-address.
Trying to connect to mobile phone configured as hotspot takes the same
result - no success with DHCP.
Manual configuring:
% ip/ipconfig -g 192.168.7.1 ether /net/ether1 192.168.7.23 255.255.255.0
also not solve the situaton - ip/ping says about lost packets..
% cat /net/ether1/ifstats
essid: vega3
bssid: 045ea4e8e2ac
status: unassociated
channel: 06
brsne: .....
.....
..big list of available wifi-networks
Tried also configure hotspot as open network, without authorization -
same result, doesn't connect.
What could be the problem??
вт, 21 мар. 2023 г. в 08:17, Jacob Moody <moody@posixcafe.org>:
>
> On 3/21/23 00:08, zxcdewqa8@gmail.com wrote:
> > Ok...I recompiled the kernel...and I am getting this message...
> >
> >> #l1: firmware: iwm-7260-17, rev 11, build 3216344376, size [3] 14000+2c000 + [3] 14000+2c000 + 0
> >> iwl: no calibration results
> >
> > I then try the following...but get no result.
> >> term% bind -a '#l1' /net
> >> term% aux/wpa -2 -s MYHOMEWIFI -p /net/ether1
>
> Just one more step.
>
> % ip/ipconfig ether /net/ether1
>
> will do dhcp on the interface.
> aux/wpa only associates with the access point.
>
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T9b33abcfc0b8784b-M2da80fda217d1ef128cc3cdf
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2023-03-21 11:25 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 15:21 zxcdewqa8
2023-03-20 15:31 ` Jacob Moody
2023-03-21 6:08 ` zxcdewqa8
2023-03-21 6:17 ` Jacob Moody
2023-03-21 8:38 ` zxcdewqa8
2023-03-21 8:42 ` mkf9
2023-03-21 11:24 ` Yury Chumak [this message]
2023-03-21 14:13 ` Jacob Moody
2023-03-22 10:02 ` Yury Chumak
2023-03-22 10:17 ` Skip Tavakkolian
2023-03-22 12:40 ` Yury Chumak
2023-03-22 17:14 ` Ravi Raj
2023-03-22 19:37 ` Jacob Moody
2023-03-23 16:15 ` Ravi Raj
2023-03-23 17:46 ` Jacob Moody
2023-03-24 14:01 ` Ravi Raj
2023-03-24 14:10 ` Jacob Moody
2023-03-24 14:25 ` hiro
2023-04-03 16:56 ` Ravi Raj
2023-04-03 17:05 ` Jacob Moody
2023-04-05 17:06 ` Ravi Raj
2023-04-05 20:04 ` Yury Chumak
2023-04-08 16:15 ` Ravi Raj
2023-04-09 6:00 ` Yury Chumak
2023-04-09 14:45 ` ori
2023-04-10 14:07 ` Ravi Raj
2023-04-10 14:39 ` Jacob Moody
2023-04-16 15:18 ` Ravi Raj
2023-05-03 15:03 ` Ravi Raj
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAOe=0deFOicB5PaotC5w9p52Sr=TjvWStgD6siuah=joLUANVA@mail.gmail.com' \
--to=sfynkx@gmail.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).