Quote:
Originally Posted by Mr.Snrub
lshw -c net
*-network UNCLAIMED
description: Network controller
product: Wireless 3165
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:02:00.0
version: 79
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress cap_list
configuration: latency=0
resources: memory:80100000-80101fff
*-network
description: Ethernet interface
physical id: 1
bus info: usb@1:5
logical name: usb0
serial: ca:88:d5:4e:13:2d
capabilities: ethernet physical
configuration: broadcast=yes driver=rndis_host driverversion=22-Aug-2005 firmware=RNDIS device ip=192.168.42.156 link=yes multicast=yes
lspci -knn | grep Net -A3; rfkill list
02:00.0 Network controller [0280]: Intel Corporation Wireless 3165 [8086:3165] (rev 79)
Subsystem: Intel Corporation Wireless 3165 [8086:8110]
Kernel modules: iwlwifi
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
Can anyone help me? As I said I am a total noob and would appreciate explicit instructions. I am tethering though my phone and can download whatever packages I might need. Many thanks!
|
What you post here does not match what you describe.
The output of lshw shows a wireless intel device, with an IP address assigned but using the RNDIS driver. Where did that driver come from?
Code:
driver=rndis_host driverversion=22-Aug-2005 firmware=RNDIS
The output of lspci shows what seems to be the same device with the iwlwifi driver.
I think that if you resolve how and where the rndis driver is getting loaded and remove it so it does not get loaded, the default iwlwifi driver for the intel chipset will take over and things should go better. 15 years ago the rndis driver may have been needed. Today not so much with the newer kernels and default firmware for intel devices.