Brought new laptop today…WiFi works, but LAN doesn’t. Seen other posts about Qualcomm and support in older kernels, and their links to sites with issues or 404 responses…so they’re not overly helpful.
:~ # lspci -nnk | grep -A3 Ethernet
3d:00.0 Ethernet controller [0200]: Qualcomm Atheros Device [1969:e0b1] (rev 10)
Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:11ad]
3e:00.0 Network controller [0280]: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e] (rev 32)
Subsystem: Bigfoot Networks, Inc. Device [1a56:1535]
ScorpionSting:
Brought new laptop today…WiFi works, but LAN doesn’t. Seen other posts about Qualcomm and support in older kernels, and their links to sites with issues or 404 responses…so they’re not overly helpful.
:~ # lspci -nnk | grep -A3 Ethernet
3d:00.0 Ethernet controller [0200]: Qualcomm Atheros Device [1969:e0b1] (rev 10)
Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:11ad]
3e:00.0 Network controller [0280]: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e] (rev 32)
Subsystem: Bigfoot Networks, Inc. Device [1a56:1535]
P: /devices/pci0000:00/0000:00:1d.5/0000:3d:00.0
E: DEVPATH=/devices/pci0000:00/0000:00:1d.5/0000:3d:00.0
E: ID_PCI_CLASS_FROM_DATABASE=Network controller
E: ID_PCI_SUBCLASS_FROM_DATABASE=Ethernet controller
E: ID_VENDOR_FROM_DATABASE=Qualcomm Atheros
E: MODALIAS=pci:v00001969d0000E0B1sv00001462sd000011ADbc02sc00i00
E: PCI_CLASS=20000
E: PCI_ID=1969:E0B1
E: PCI_SLOT_NAME=0000:3d:00.0
E: PCI_SUBSYS_ID=1462:11AD
E: SUBSYSTEM=pci
E: USEC_INITIALIZED=4954883
Switching to a newer kernel is might be necessary, but in the meantime try adding the product and vendor ID like this
modprobe alx
echo 1969 e0b1 > /sys/bus/pci/drivers/alx/new_id
Does that work? It won’t survive a reboot, but can be added to a boot script if it works.
deano_ferrari:
Switching to a newer kernel is might be necessary, but in the meantime try adding the product and vendor ID like this
modprobe alx
echo 1969 e0b1 > /sys/bus/pci/drivers/alx/new_id
Does that work? It won’t survive a reboot, but can be added to a boot script if it works.
Thanks, that got eth0 up…will script it for now until an updated kernel comes out.
Will skip next post’s suggestion as don’t want to risk other issues that may occur