Port Ethernet not found on Ubuntu 22.04 system
Port Ethernet not found on Ubuntu 22.04 system
Hi, I connected an ethernet cable to my Ubuntu machine because the Wi-Fi was really shaky. It functioned for about five hours before the computer crashed. Now it doesn’t recognize any cable—even though I used a brand new one, so the issue isn’t with the cable itself. On my router everything looks normal; the Ethernet port has a green light but my PC doesn’t show up. The ifconfig command shows only my PCIe Wi-Fi card. I also found something odd: the /etc/network/interfaces file isn’t present, and instead it seems to be missing entirely. Could anyone help me figure this out? Thanks! ^^ EDIT: Just confirmed the cable works on another PC, so it’s likely just this one.
00:00.0 Host bridge: Intel Corporation 10th Gen Core Processor Host Bridge/DRAM Registers (rev 03)
00:01.0 PCI bridge: Intel Corporation 6th-10th Gen Core Processor PCIe Controller (x16) (rev 03)
00:02.0 VGA compatible controller: Intel Corporation CometLake-S GT2 [UHD Graphics 630] (rev 03)
00:14.0 USB controller: Intel Corporation Tiger Lake-H USB 3.2 Gen 2x1 xHCI Host Controller (rev 11)
00:14.2 RAM memory: Intel Corporation Tiger Lake-H Shared SRAM (rev 11)
00:16.0 Communication controller: Intel Corporation Tiger Lake-H Management Engine Interface (rev 11)
00:17.0 SATA controller: Intel Corporation Device 43d2 (rev 11)
00:1c.0 PCI bridge: Intel Corporation Tiger Lake-H PCI Express Root Port #5 (rev 11)
00:1d.0 PCI bridge: Intel Corporation Device 43b2 (rev 11)
00:1f.0 ISA bridge: Intel Corporation Device 4388 (rev 11)
00:1f.3 Audio device: Intel Corporation Device f0c8 (rev 11)
00:1f.4 SMBus: Intel Corporation Tiger Lake-H SMBus Controller (rev 11)
01:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8812AE 802.11ac PCIe Wireless Network Adapter (rev 01) 6.2.0-26-generic The motherboard is a Gigabyte H510M
Unless it stops itself following a crash, I’ll verify it anyway, but if I don’t mention it afterward, I’ll take it as not disabled.
You're asking about the modprobe command. It seems you're trying to install a module without any arguments, but you're getting an error saying "Missing parameters." This usually happens when the system doesn't recognize the module name or the required options. Even with help, it can be confusing because the process might depend on additional settings or dependencies.
I'm not sure if this will serve its purpose, but it's better to be cautious. When I attempted ip link show instead of ifconfig, I received this output: 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00 brd 00:00:00:00 2: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000 link/ether d8:5e:d3:52:d9:f0 brd ff:ff:ff:ff:ff:ff 3: wlp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DORMANT group default qlen 1000 link/ether 5c:a6:e6:c6:04:4f brd ff:ff:ff:ff:ff:ff 4: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default link/ether 02:42:3b:d8:e2:5e brd ff:ff:ff:ff:ff:ff enp3s0 didn't appear in ifconfig, perhaps that matters? EDIT: I tried it: sudo lshw -class network [sudo] Password: *-network description: Interface réseau sans fil produit: RTL8812AE 802.11ac PCIe Wireless Network Adapter fabricant: Realtek Semiconductor Co., Ltd. identifiant matériel: 0 information bus: pci@0000:01:00.0 nom logique: wlp1s0 version: 01 numéro de série: 5c:a6:e6:c6:04:4f bits: 64 bits horloge: 33MHz fonctionnalités: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration : broadcast=yes driver=rtl8821ae driverversion=6.2.0-26-generic firmware=N/A ip=192.168.1.39 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources : irq:127 portE/S:4000(taille=256) mémoire:51200000-51203fff *-network description: Ethernet interface sans fil produit: RTL8812AE version: 02:42:3b:d8:e2:5e brd ff:ff:ff:ff:ff:ff enp3s0 n'a pas été affiché dans ifconfig, cela pourrait être significatif? EDIT: Résultat : j'ai exécuté la commande lshw -class network.* Mot de passe du serveur : *-network description: ...* -
Ensure enp3s0 is set as your local network adapter. Verify DHCP is active on the router and a device is connected. Run "ifup enp3s0" to activate it.
ifup enp3s0 returned an unknown interface name, yet it seems connected right now. I’m puzzled about why it didn’t recognize it, but maybe that’s intentional. This is odd because it didn’t identify the interface properly, though I won’t complain. I’ll note this as a possible solution, though it could just be luck. Hope this helps both of you!