You are not logged in.
- Topics: Active | Unanswered
Pages: 1
#1 Re: Hardware & System Configuration » wireless problem on qemu » 2018-04-30 11:43:27
...
btw, there is also the iw tool (from wireless-tools) for# iw dev wlan0 scanRumours has it that sometimes that works where iwlist fails.
same error
- what can I view about:
wlan0 Interface doesn't support scanning : Device or resource busyp.s.
I virtualized:
kubuntu16.04 works OK
kubuntu18.04 dont works
ubuntu14.04 works OK
#2 Re: Hardware & System Configuration » wireless problem on qemu » 2018-04-30 09:51:49
- rfkill are not blocked
- auto or allow-hotplug same problem
- is OK that I view nothing running:
dmesg|grep wlan?
#3 Re: Hardware & System Configuration » wireless problem on qemu » 2018-04-29 07:40:07
other info from dmesg:
[ 106.224185] usb 1-1: new full-speed USB device number 2 using uhci_hcd
[ 106.645996] usb 1-1: config 1 interface 0 altsetting 0 endpoint 0x1 has invalid maxpacket 512, setting to 64
[ 106.646006] usb 1-1: config 1 interface 0 altsetting 0 endpoint 0x82 has invalid maxpacket 512, setting to 64
[ 106.646009] usb 1-1: config 1 interface 0 altsetting 0 endpoint 0x5 has invalid maxpacket 512, setting to 64
[ 106.646012] usb 1-1: config 1 interface 0 altsetting 0 endpoint 0x6 has invalid maxpacket 512, setting to 64
[ 106.659511] usb 1-1: New USB device found, idVendor=0846, idProduct=9030
[ 106.659524] usb 1-1: New USB device strings: Mfr=16, Product=32, SerialNumber=48
[ 106.659530] usb 1-1: Product: WNA1100
[ 106.659534] usb 1-1: Manufacturer: NETGEAR WNA
[ 106.659538] usb 1-1: SerialNumber: 12345
[ 106.715384] usb 1-1: ath9k_htc: Firmware htc_9271.fw requested
[ 106.716669] usb 1-1: firmware: direct-loading firmware htc_9271.fw
[ 106.717127] usbcore: registered new interface driver ath9k_htc
[ 107.060489] usb 1-1: ath9k_htc: Transferred FW: htc_9271.fw, size: 50980
[ 107.323928] ath9k_htc 1-1:1.0: ath9k_htc: HTC initialized with 33 credits#4 Re: Hardware & System Configuration » wireless problem on qemu » 2018-04-23 18:46:53
same problem
p.s.
adding other info
iwlist scan
ens3 Interface doesn't support scanning.
wlan0 Interface doesn't support scanning : Device or resource busy
lo Interface doesn't support scanning.
#5 Re: Hardware & System Configuration » wireless problem on qemu » 2018-04-23 15:38:35
this is my /etc/wpa_supplicant/wpa_supplicant.conf
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
update_config=1network={
ssid="NETGEAR"
proto=WPA
key_mgmt=NONE
pairwise=TKIP
group=TKIP
}
but after reboot, same problem:
eth0 have an IP
wlan0 no
#6 Re: Hardware & System Configuration » wireless problem on qemu » 2018-04-23 15:19:17
my network has only essid NETGEAR
no any other key/password
what I have to set this:
ssid="network_id"
psk="password"
proto=WPA
key_mgmt=WPA-PSK
pairwise=TKIP
group=TKIP
?
#7 Re: Hardware & System Configuration » wireless problem on qemu » 2018-04-23 14:51:06
in both systems I dont have wpasupplicant
#8 Hardware & System Configuration » wireless problem on qemu » 2018-04-23 11:32:05
- sacarde
- Replies: 13
hi,
I use same usb-wireless (Atheros AR9271) in 2 virtualized system:
1) debian/sid
2) devuan
I use same configuration:
allow-hotplug wlan0
iface wlan0 inet dhcp
wireless-essid NETGEAR
in debian system, wlan0 get IP address OK
in devuan system I receive error:
ifup wlan0
Internet Systems Consortium DHCP Client 4.3.1
Copyright 2004-2014 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/Listening on LPF/wlan0/e0:46:9a:0d:72:0c
Sending on LPF/wlan0/e0:46:9a:0d:72:0c
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 17
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 1
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
in both system eth0 in dhcp works OK
what can I check?
thank you
Pages: 1
Board footer
