Re: [DNG] Configuring ethernet port for IPv6 - broken hardware revealed by dmesg
On Fri, Jan 28, 2022 at 03:14:31PM -1000, Joel Roth via Dng wrote: > This is an older thinkpad, I think it's unlikely to need > extra firmware. When I try to install firmware-misc-nonfree I'm told: > > Package firmware-misc-nonfree is not available, but is referred to by another > package. > This may mean that the package is missing, has been obsoleted, or > is only available from another source > > I do have firmware-linux-nonfree installed. Hmmm, OK. Well, firmware-linux-nonfree should pull in firmware-misc-nonfree, so your probably fine as far as that goes, and you probably have a bad ethernet chip. Greg -- web site: http://www.gregn.net gpg public key: http://www.gregn.net/pubkey.asc skype: gregn1 (authorization required, add me to your contacts list first) If we haven't been in touch before, e-mail me before adding me to your contacts. -- Free domains: http://www.eu.org/ or mail dns-mana...@eu.org ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Configuring ethernet port for IPv6 - broken hardware revealed by dmesg
On Fri, Jan 28, 2022 at 05:50:37PM -0700, Gregory Nowak via Dng wrote: > On Fri, Jan 28, 2022 at 12:40:36PM -1000, Joel Roth via Dng wrote: > > On Fri, Jan 28, 2022 at 12:05:06PM -0700, Bob Proulx via Dng wrote: > > > Joel Roth wrote: > > > > Gregory Nowak wrote: > > > > > Is there anything different in the dmesg(1) output for eth1 than > > > > > for your other interfaces? > > > > > > > > bingo: > > > > > > > > [467072.902423] e1000e :00:19.0 eth1: Hardware Error > > > >... > > > > This is a used Thinkpad pad, recently purchased. > > > > Fortunately usb-ethernet adapters are easily available. > > I'm not sure, but is it possible your ethernet chip is one which > requires firmware from the firmware-misc-nonfree package? This is an older thinkpad, I think it's unlikely to need extra firmware. When I try to install firmware-misc-nonfree I'm told: Package firmware-misc-nonfree is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source I do have firmware-linux-nonfree installed. > Greg > > > -- > web site: http://www.gregn.net > gpg public key: http://www.gregn.net/pubkey.asc > skype: gregn1 > (authorization required, add me to your contacts list first) > If we haven't been in touch before, e-mail me before adding me to your > contacts. > > -- > Free domains: http://www.eu.org/ or mail dns-mana...@eu.org > ___ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng -- Joel Roth ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Configuring ethernet port for IPv6 - broken hardware revealed by dmesg
On Fri, Jan 28, 2022 at 12:40:36PM -1000, Joel Roth via Dng wrote: > On Fri, Jan 28, 2022 at 12:05:06PM -0700, Bob Proulx via Dng wrote: > > Joel Roth wrote: > > > Gregory Nowak wrote: > > > > Is there anything different in the dmesg(1) output for eth1 than > > > > for your other interfaces? > > > > > > bingo: > > > > > > [467072.902423] e1000e :00:19.0 eth1: Hardware Error > > >... > > > This is a used Thinkpad pad, recently purchased. > > > Fortunately usb-ethernet adapters are easily available. I'm not sure, but is it possible your ethernet chip is one which requires firmware from the firmware-misc-nonfree package? Greg -- web site: http://www.gregn.net gpg public key: http://www.gregn.net/pubkey.asc skype: gregn1 (authorization required, add me to your contacts list first) If we haven't been in touch before, e-mail me before adding me to your contacts. -- Free domains: http://www.eu.org/ or mail dns-mana...@eu.org ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Configuring ethernet port for IPv6 - broken hardware revealed by dmesg
On Fri, Jan 28, 2022 at 12:05:06PM -0700, Bob Proulx via Dng wrote: > Joel Roth wrote: > > Gregory Nowak wrote: > > > Is there anything different in the dmesg(1) output for eth1 than > > > for your other interfaces? > > > > bingo: > > > > [467072.902423] e1000e :00:19.0 eth1: Hardware Error > >... > > This is a used Thinkpad pad, recently purchased. > > Fortunately usb-ethernet adapters are easily available. > > This is very odd. Thinkpads have been very robust and reliable and > used so much that they have been somewhat of a reference platform for > many years. The e1000 driver family is very commonly used and is in > the kernel main. > > I suggest booting a live boot image on your Thinkpad and seeing if the > wired interface works using one of those. That would eliminate > something corrupted in your current installation. It's easy to do. > It is a good quick second opinion on the network hardware. > > Also, how did you install this system? Did you use a "netinstall" > image originally? Using the wired ethernet or WiFi? Because if you > installed using wired ethernet (the most typical way I install) then > at install time the netinstall image was working okay with your wired > ethernet. > > Booting a netinstall image in "Rescue Mode" (under the advanced > options) would also be a safe way to test if the hardware is working > under a live boot system. And if this is a recent install using a > netinstall image then it's one you already have available. Great suggestions. I think I've benefitted from your advice several times of the years, directly and from reading your posts. I booted from a different kernel, same result from ip addr show eth1. 2: eth1: mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000 link/ether 28:d2:44:1a:e0:ca brd ff:ff:ff:ff:ff:ff I'll try with a live CD, or USB drive. I've got a hard drive in the CD bay at the moment. The notebook is new used, but the system has been the same (with upgrades) for probably 15 years. I haven't done a fresh installation for a long time (except as a VM). What a great resource you are, oh bearded ones! > Bob > ___ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng -- Joel Roth ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Configuring ethernet port for IPv6 - broken hardware revealed by dmesg
Joel Roth wrote: > Gregory Nowak wrote: > > Is there anything different in the dmesg(1) output for eth1 than > > for your other interfaces? > > bingo: > > [467072.902423] e1000e :00:19.0 eth1: Hardware Error >... > This is a used Thinkpad pad, recently purchased. > Fortunately usb-ethernet adapters are easily available. This is very odd. Thinkpads have been very robust and reliable and used so much that they have been somewhat of a reference platform for many years. The e1000 driver family is very commonly used and is in the kernel main. I suggest booting a live boot image on your Thinkpad and seeing if the wired interface works using one of those. That would eliminate something corrupted in your current installation. It's easy to do. It is a good quick second opinion on the network hardware. Also, how did you install this system? Did you use a "netinstall" image originally? Using the wired ethernet or WiFi? Because if you installed using wired ethernet (the most typical way I install) then at install time the netinstall image was working okay with your wired ethernet. Booting a netinstall image in "Rescue Mode" (under the advanced options) would also be a safe way to test if the hardware is working under a live boot system. And if this is a recent install using a netinstall image then it's one you already have available. Bob signature.asc Description: PGP signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Configuring ethernet port for IPv6 - broken hardware revealed by dmesg
On Thu, Jan 27, 2022 at 04:38:37PM -0700, Gregory Nowak wrote: > Hi Joel, > redirecting back to the list. > > > On Thu, Jan 27, 2022 at 12:44:55PM -1000, Joel Roth wrote: > > Thank you for the response, Gregory. > > > > On Thu, Jan 27, 2022 at 03:33:01PM -0700, Gregory Nowak via Dng wrote: > > > On Thu, Jan 27, 2022 at 11:37:52AM -1000, Joel Roth via Dng wrote: > > > > It seems that my new router uses IPv6. Perhaps that means > > > > the ISP does so as well. > > > > > > Just because a router uses IPv6, doesn't necessarily mean the ISP > > > supports it. > > > > > > My problem is connecting via dhcp over ethernet. On IRC > > > > I was advised to try > > > > > > > > ping ff02::1%eth1 > > > > > Just to make sure, the interface connected to your router is in fact > > > eth1, and not eth0, right? > > > > Yes, it's eth1. > > > > > > which fails to get a response, indicating IPv6 is not enabled in my > > > > client. > > > > > > Posting the actual output might help. > > > > Usually ping (with no options) periodically returns a line > > with the time taken for the round trip. In this instance, > > one line beginning with PING and nothing more. > > > > > > I tried setting "iface eth1 inet6 dhcp" in /etc/network/interfaces, > > > > then "ifup eth1". This fails with > > > > > > > > no link-local IPv6 address for eth1 > > > > > > Even if your interface isn't able to configure a global IPv6 address, > > > it should still get a link local address starting with fe80. > > > > This is the problem. I don't have a link local address: > > > > $ ifconfig eth1 > > eth1: flags=4099 mtu 1500 > > ether 28:d2:44:1a:e0:ca txqueuelen 1000 (Ethernet) > > RX packets 0 bytes 0 (0.0 B) > > RX errors 0 dropped 0 overruns 0 frame 0 > > TX packets 0 bytes 0 (0.0 B) > > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > device interrupt 20 memory 0xf250-f252 > > You don't seem to have an IPv4 address, even for obtaining a dhcp > lease. Is this what you expect? If not, then the problem would seem to > be wider in scope than just IPv6. > > > > > > Also, before modifying /etc/network/interfaces, I would advise doing > > > ifdown eth1, modifying the file, and then ifup eth1. Instead of inet6 > > > dhcp, I would suggest: > > > > > > iface eth1 inet6 auto > > > > > > My understanding is this should use either dhcp6, or RA/NDP to > > > configure it. > > > > > What does the following output: > > > > > > cat /proc/sys/net/ipv6/conf/all/disable_ipv6 > > > cat /proc/sys/net/ipv6/conf/default/disable_ipv6 > > > cat /proc/sys/net/ipv6/conf/eth1/disable_ipv6 > > > > All zeroes. > > > > Do you have network-manager or the like installed which could be > trying to configure the interface on its own? > > Is there anything > different in the dmesg(1) output for eth1 than for your other > interfaces? bingo: [467072.085551] e1000e :00:19.0 eth1: PHY Wakeup cause - Unicast Packet [467072.902423] e1000e :00:19.0 eth1: Hardware Error [467081.10] e1000e :00:19.0 eth1: Hardware Error [467089.669913] e1000e :00:19.0 eth1: Hardware Error [467090.624833] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready [467097.725663] e1000e :00:19.0 eth1: PHY Wakeup cause - Unicast Packet [467098.549348] e1000e :00:19.0 eth1: Hardware Error [467243.278267] e1000e :00:19.0 eth1: Hardware Error [467243.588770] e1000e: eth1 NIC Link is Down [467248.986061] e1000e :00:19.0 eth1: Hardware Error [467249.940380] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready [467255.211266] e1000e :00:19.0 eth1: Could not acquire PHY [467255.211285] e1000e :00:19.0 eth1: PHY Wakeup cause - Unicast Packet [467255.918047] e1000e :00:19.0 eth1: Hardware Error This is a used Thinkpad pad, recently purchased. Fortunately usb-ethernet adapters are easily available. > Since ifconfig is depricated, what does: > > ip address show eth1 > > give you? 2: eth1: mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000 link/ether 28:d2:44:1a:e0:ca brd ff:ff:ff:ff:ff:ff > What does: > > cat /proc/sys/net/ipv6/conf/eth1/autoconf 1 > output? > Other than that, that's all I can think of at the moment. Thanks, Greg, you've been very helpful. -- Joel Roth ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
