http://bugzilla.opensuse.org/show_bug.cgi?id=1108658 Dominik Heidler changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Network |Kernel Assignee|bnc-team-screening@forge.pr |kernel-maintainers@forge.pr |ovo.novell.com |ovo.novell.com -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1108658 http://bugzilla.opensuse.org/show_bug.cgi?id=1108658#c3 Dominik Heidler changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(dheidler@suse.com | |) | --- Comment #3 from Dominik Heidler --- Wired network worked (even the data led was blinking) when I installed and bootet kernel-default-4.12.14-lp150.130.1.g3315c9e.aarch64.rpm from that repo. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1108658 http://bugzilla.opensuse.org/show_bug.cgi?id=1108658#c5 --- Comment #5 from Dominik Heidler --- Blacklisting microchip with the original 4.17.13-1 tumbleweed kernel doesn't have any effect - it still loads the module and doesn't allow me to unload ("Module microchip is in use") Blacklisting it using the Kernel from Kernel:openSUSE-15.0 repo is possible but it works as well without blacklisting that module when using the Kernel:openSUSE-15.0 kernel. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1108658 http://bugzilla.opensuse.org/show_bug.cgi?id=1108658#c8 --- Comment #8 from Takashi Iwai --- (In reply to Dominik Heidler from comment #7)

With kernel 4.18.8-1.gf486469 from Kernel:stable I do get network connectivity. The blacklist of the microchip module works here. The orange data led on the RJ45 port does NOT blink here.

Not blacklisting the module doesn't change anything here.

So with 4.18.x, the initial issue got fixed? The fixed PHY support (commit 89b36fb5e53244) might be the relevant fix between 4.17 and 4.18. The LED behavior change might be the upstream change about LED status reading from DT (commit 1827b0678863). -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1108658 http://bugzilla.opensuse.org/show_bug.cgi?id=1108658#c10 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #10 from Takashi Iwai --- Then let's close, it'll hit to TW sooner or later ;) -- You are receiving this mail because: You are on the CC list for the bug.