On Sun, 23 Jun 2019 08:31:45 -0700 (PDT) Anhangá <vischr...@gmail.com> wrote:
> Hi, > > I'm quite new using Qubes and I've never been so fond with Linux but > this changed last year so sorry for newbie questions in advance. > > I installed Qubes 4.0.1 using only wifi connection and it was working > 100% with wifi connections but I had to reinstall after a ssd upgrade > I did on my laptop and in this second time I used a wired connection > to do install Qubes 4.0.1. > > In this new installation, wifi connection is not working and I > counld't figure out why. The connections options only shows My Wired > Connection but none Wifi connection available as shown in the > attached Screenshot. > > I've tried the Qubes Wireless troubleshooting (resetting wireless > cards by reloading drivers) but didn't work. > > I tried some commands on sys-net to see some informations about my > wireless card and seems that everything is ok. > ---------------------------------------------------------------------------- > > > lspci -vv: > > 00:07.0 Network controller: Qualcomm Atheros QCA9377 802.11ac > Wireless Network Adapter (rev 31) Subsystem: Samsung Electronics Co > Ltd Device 4133 Physical Slot: 7 > Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- > ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- > FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- > INTx- Latency: 0 Interrupt: pin A routed to IRQ 72 > Region 0: Memory at f2000000 (64-bit, non-prefetchable) > [size=2M] Capabilities: [40] Power Management version 3 > Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA > PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst+ PME-Enable- > DSel=0 DScale=0 PME- Capabilities: [50] MSI: Enable+ Count=1/1 > Maskable- 64bit- Address: fee96000 Data: 4300 > Capabilities: [70] Express (v2) Endpoint, MSI 00 > DevCap: MaxPayload 256 bytes, PhantFunc 0, > Latency L0s unlimited, L1 <64us ExtTag- AttnBtn- AttnInd- PwrInd- > RBE+ FLReset- SlotPowerLimit 10.000W DevCtl: CorrErr- > NonFatalErr- FatalErr- UnsupReq- RlxdOrd+ ExtTag- PhantFunc- AuxPwr- > NoSnoop+ MaxPayload 128 bytes, MaxReadReq 512 bytes > DevSta: CorrErr- NonFatalErr- FatalErr- > UnsupReq- AuxPwr+ TransPend- LnkCap: Port #0, Speed 2.5GT/s, > Width x1, ASPM L0s L1, Exit Latency L0s <4us, L1 <64us ClockPM+ > Surprise- LLActRep- BwNot- ASPMOptComp+ LnkCtl: ASPM Disabled; > RCB 64 bytes Disabled- CommClk- ExtSynch- ClockPM- AutWidDis- BWInt- > AutBWInt- LnkSta: Speed 2.5GT/s (ok), Width x1 (ok) > TrErr- Train- SlotClk+ DLActive- BWMgmt- > ABWMgmt- DevCap2: Completion Timeout: Not Supported, TimeoutDis+, > LTR+, OBFF Via message AtomicOpsCap: 32bit- 64bit- 128bitCAS- > DevCtl2: Completion Timeout: 50us to 50ms, > TimeoutDis-, LTR-, OBFF Disabled AtomicOpsCtl: ReqEn- > LnkSta2: Current De-emphasis Level: -6dB, > EqualizationComplete-, EqualizationPhase1- EqualizationPhase2-, > EqualizationPhase3-, LinkEqualizationRequest- Kernel driver in use: > ath10k_pci Kernel modules: ath10k_pci > ---------------------------------------------------------------------------- > > > lshw: > > *-network:0 > description: Ethernet interface > product: RTL810xE PCI Express Fast Ethernet controller > vendor: Realtek Semiconductor Co., Ltd. > physical id: 6 > bus info: pci@0000:00:06.0 > logical name: ens6 > version: 07 > serial: 98:83:89:ca:86:9a > size: 100Mbit/s > capacity: 100Mbit/s > width: 64 bits > clock: 33MHz > capabilities: pm msi pciexpress vpd bus_master cap_list > ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation > configuration: autonegotiation=on broadcast=yes driver=r8169 > driverversion=2.3LK-NAPI duplex=full firmware=rtl8106e-1_0.0.1 > 06/29/12 ip=192.168.25.11 latency=64 link=yes multicast=yes port=MII > speed=100Mbit/s resources: irq:71 ioport:c200(size=256) > memory:f222a000-f222afff memory:f2224000-f2227fff *-network:1 > description: Network controller product: QCA9377 802.11ac Wireless > Network Adapter vendor: Qualcomm Atheros physical id: 7 bus info: > pci@0000:00:07.0 version: 31 > width: 64 bits > clock: 33MHz > capabilities: pm msi pciexpress bus_master cap_list > configuration: driver=ath10k_pci latency=0 > resources: irq:72 memory:f2000000-f21fffff > *-network:0 > description: Ethernet interface > physical id: 1 > logical name: vif6.0 > serial: fe:ff:ff:ff:ff:ff > capabilities: ethernet physical > configuration: broadcast=yes driver=vif ip=10.137.0.5 link=yes > multicast=yes *-network:1 > description: Ethernet interface > physical id: 2 > logical name: vif13.0 > serial: fe:ff:ff:ff:ff:ff > capabilities: ethernet physical > configuration: broadcast=yes driver=vif ip=10.137.0.5 link=yes > multicast=yes > ---------------------------------------------------------------------------- > > > service NetworkManager status: > > ● NetworkManager.service - Network Manager > Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; > enabled; vendor preset: enabled) > Drop-In: /usr/lib/systemd/system/NetworkManager.service.d > └─30_qubes.conf Active: active (running) since Sun 2019-06-23 > 11:38:31 -03; 48min ago Docs: man:NetworkManager(8) > Process: 389 > ExecStartPre=/usr/lib/qubes/network-manager-prepare-conf-dir > (code=exited, status=0/SUCCESS) Main PID: 412 (NetworkManager) Tasks: > 4 (limit: 393) Memory: 2.7M > CGroup: /system.slice/NetworkManager.service > ├─412 /usr/sbin/NetworkManager --no-daemon > └─582 /sbin/dhclient -d -q -sf /usr/libexec/nm-dhcp-helper > -pf /var/run/dhclient-ens6.pid > -lf > /var/lib/NetworkManager/dhclient-c5ed704a-0800-3a65-bcc5-83e48dd42086-ens6.lease > -cf /var/lib/NetworkMana> > > Jun 23 11:38:39 sys-net NetworkManager[412]: <info> > [1561300719.4213] manager: NetworkManager state is now CONNECTED_SITE > Jun 23 11:38:39 sys-net NetworkManager[412]: <info> > [1561300719.4214] policy: set 'Wired connection 1' (ens6) as default > for IPv4 routing and DNS Jun 23 11:38:39 sys-net NetworkManager[412]: > <info> [1561300719.4275] device (ens6): Activation: successful, > device activated. Jun 23 11:38:39 sys-net NetworkManager[412]: > <info> [1561300719.4280] manager: NetworkManager state is now > CONNECTED_GLOBAL Jun 23 11:38:39 sys-net NetworkManager[412]: <info> > [1561300719.4289] manager: startup complete Jun 23 11:38:39 sys-net > dhclient[582]: bound to 192.168.25.11 -- renewal in 42127 seconds. > Jun 23 11:57:16 sys-net NetworkManager[412]: <info> > [1561301836.0227] manager: (vif11.0): new Ethernet device > (/org/freedesktop/NetworkManager/Devices/4) Jun 23 11:57:16 sys-net > NetworkManager[412]: <info> [1561301836.0995] device (vif11.0): > carrier: link connected Jun 23 11:57:46 sys-net NetworkManager[412]: > <info> [1561301866.2265] manager: (vif13.0): new Ethernet device > (/org/freedesktop/NetworkManager/Devices/5) Jun 23 11:57:49 sys-net > NetworkManager[412]: <info> [1561301869.0588] device (vif13.0): > carrier: link connected > ---------------------------------------------------------------------------- > > > > > Anyone has any guess on how to solve this problem? > Are you using the normal full fedora template for sys-net? Does sys-net have the pci device selected in Qubes settings? Are the modules ath, ath10k_core, ath10k_pci, cfg80211 and mac80211 running in sys-net? Mike. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20190623174534.42a62bbf.mike%40keehan.net. For more options, visit https://groups.google.com/d/optout.
