Well, rather than just simply power cycling the computer as I had done, I instead shut down the comptuer from Windows, then pulled the plug for 20-30 seconds. Then I re-inserted the plug and powered up. I am now writing this email from Linux.

A power-down doesn't really cut the juice to the motherboard. Some lights inside the box will remain on, and I recall that the NIC is resident on the motherboard.

-------- Original Message --------
As stated, I have a desktop PC that is dual-boot, and where the network operates under Windows 10 but not Linux.

I have been referred to this mailing list from Ubuntu Studio, since this appears to be a more general kind of problem.

I followed some suggestions given by previous responders in other lists, regarding net commands to help diagnose the system.

It was of some interest that I found that my router is assigning a different IP to the Windows 10 hostname than for the Linux hostname. However, the listing below doesn't really show any IP.

The commands run were:
ip addr show
ip link show
dhclient -r eno1
sudo dhclient -v eno1

The typescript is below:

Script started on 2022-12-17 17:03:12-05:00
$ ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether d8:50:e6:4d:0c:da brd ff:ff:ff:ff:ff:ff
    altname enp0s25
    inet6 fe80::e8e4:6dba:23d6:c035/64 scope link noprefixroute
       valid_lft forever preferred_lft forever
$ ip link show
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:00 brd 00:00:00:00:00:00
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
    link/ether d8:50:e6:4d:0c:da brd ff:ff:ff:ff:ff:ff
    altname enp0s25
$ dhclient -r eno1
$ sudo dhclient -v eno1
[sudo] password for paul:
Internet Systems Consortium DHCP Client 4.4.1
Copyright 2004-2018 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/eno1/d8:50:e6:4d:0c:da
Sending on   LPF/eno1/d8:50:e6:4d:0c:da
Sending on   Socket/fallback
DHCPDISCOVER on eno1 to 255.255.255.255 port 67 interval 3 (xid=0x3a1ec029) DHCPDISCOVER on eno1 to 255.255.255.255 port 67 interval 5 (xid=0x3a1ec029) DHCPDISCOVER on eno1 to 255.255.255.255 port 67 interval 11 (xid=0x3a1ec029) DHCPDISCOVER on eno1 to 255.255.255.255 port 67 interval 18 (xid=0x3a1ec029) DHCPDISCOVER on eno1 to 255.255.255.255 port 67 interval 13 (xid=0x3a1ec029)
^C
$ exit

Script done on 2022-12-17 17:04:57-05:00 [COMMAND_EXIT_CODE="130"]

Thanks to anyone who can help or provide useful insight.

Paul King
---
Post to this mailing list [email protected]
Unsubscribe from this mailing list https://gtalug.org/mailman/listinfo/talk

Reply via email to