| View previous topic :: View next topic |
| Author |
Message |
javeree
Guru
Joined: 29 Jan 2006
Posts: 455
|
 Posted: Tue Jul 02, 2019 4:27 pm Post subject: no ip address with new kernel 5.1.5 |
 |
|
My setup with kernel 4.14.83 works without fault: pc boots, all services get started, including 'net.ethm', which gets an adress from dhcpcd.
After I move to 5.1.5 using olddefconfig, I get during boot messages that netmount and local are waiting for net.ethm. After login, I see that net.ethm is stopped. When I manually run /etc/init.d/net.ethm, I get:
| Quote: |
* Bringing up interface ethm
* config_ethm not specified; defaulting to DHCP
* dhcp ...
* Running dhcpcd ...sending commands to master dhcpcd process
[ ok ]
* received address
[ ok ]
|
Even though I see 'received address', ip addr still gives:
| Quote: | 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 brd 127.255.255.255 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: ethm: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
link/ether 00:26:18:67:b6:20 brd ff:ff:ff:ff:ff:ff |
I see there is 'NO-CARRIER', but this is the same cable as when I boot with the other kernel. There is absolutely no other difference between teh successful and the unsuccessful case except for the kernel!
for the record I put some information I gathered in both cases for comparison. I had a look at this myself, but could not find any meaningfull difference:
starting with kernel 4.14.83:
kernel configuration: https://pastebin.com/EEia0pXE
dmesg: https://pastebin.com/GJZXDs7m
lsmod: https://pastebin.com/P9pL7jhh
ip addr after boot: https://pastebin.com/HKL2214n
starting with 5.1.5
kernel configuration: https://pastebin.com/XhTbpsTS
dmesg: https://pastebin.com/EvBfZJsY
ip addr after boot: https://pastebin.com/CrctNV7d
lsmod: https://pastebin.com/me6Gtxds
Since it is only the kernels that make a difference (both are started without initramfs), I assume there must be a problem with the configuration. i spent some hours trying to find the correct configuration, but could not find anything so far. The only significant difference I found so far is in lsmod, where for some reason, in 4.14.83 module mii is loaded, and in 5.1.5 module libphy is loaded.
In 5.1.5, I modprobed the mii module and then restarted net.ethm, but that did not solve the issue 
Last edited by javeree on Sat Jul 06, 2019 8:03 pm; edited 1 time in total |
|
| Back to top |
|
 |
mike155
Advocate
Joined: 17 Sep 2010
Posts: 4438
Location: Frankfurt, Germany
|
| Posted: Tue Jul 02, 2019 9:56 pm Post subject: |
|
|
1) Thanks for all the data you posted. Unfortunately, something is wrong with the links. dmesg for 4.14.82 is the same as dmesg for 5.1.5. And lsmod for 4.414.83 is the same as ip addr and lsmod for 5.1.5... Please correct the links.
2) Please try kernel 4.19. Does this kernel still work? It would be nice to know if the change that causes the problem happened before or after 4.19. |
|
| Back to top |
|
|
javeree
Guru
Joined: 29 Jan 2006
Posts: 455
|
|
| Back to top |
|
|
mike155
Advocate
Joined: 17 Sep 2010
Posts: 4438
Location: Frankfurt, Germany
|
| Posted: Sat Jul 06, 2019 9:26 pm Post subject: |
|
|
| It seems that the Realtek driver was re-engineered just before kernel 4.19. Many users had or have problems. Search at Google for "linux 4.19 Realtek RTL8211B link down". You will find several discussion threads. This one, for example. Proposed solutions range from "change module load order of r8169, libphy and realtek' over 'build driver into the kernel (and not as a module)' to 'enable RANDOM_TRUST_CPU". I'm afraid there won't be an easy solution. But the discussion threads contain some proposals you could try. I don't think that there's anything wrong in your kernel config or on your machine. |
|
| Back to top |
|
|
Jaglover
Watchman
Joined: 29 May 2005
Posts: 8291
Location: Saint Amant, Acadiana
|
|
| Back to top |
|
|
javeree
Guru
Joined: 29 Jan 2006
Posts: 455
|
| Posted: Tue Jul 09, 2019 1:42 pm Post subject: |
|
|
Thanks for those pointers. At least I now know I am not going crazy !
I'll have a look at those suggestions abd report back if it works. |
|
| Back to top |
|
|
javeree
Guru
Joined: 29 Jan 2006
Posts: 455
|
| Posted: Tue Jul 23, 2019 10:42 am Post subject: |
|
|
Some intermediate result:
kernel 4.19 with module r8168 now sees the carrier: ethm: <BROADCAST,MULTICAST,UP,LOWER_UP>, but still receives a link-local address.
However, when I look on the side of the dhcp server with wireshark, I see the incoming dhcp request and the outgoing answer.
The next step is to have some way to dump the packages to/from the interface during startup (that is: I need to read the manpage of tcpdump as there is no X to run wireshark on) and check
* if the response is arriving
* if so, why dhcpcd does not assign it to the interface. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Kernel & Hardware
