https://bugzilla.suse.com/show_bug.cgi?id=1232668 https://bugzilla.suse.com/show_bug.cgi?id=1232668#c9 Keks Dose <cookie170@web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo? --- Comment #9 from Keks Dose <cookie170@web.de> --- (In reply to Takashi Iwai from comment #8)
(In reply to Joan Torres from comment #6)
The r8152 driver is already provided by kernel-default.
Could the lack of udev rules for r8152 make it use cdc_ncm instead of r8152?
Please, Keks, could you remove r8152-kmp-default and r8152-ueficert. And leave only the rules: r8152-udev-rules.
Does that make it work?
Takashi, who should we reach if something at r8152 driver is missing?
I guess that the upstream r8512 driver doesn't support this model (17ef:a359) yet.
The downstream r8152 driver has the support of the newer chip, and possibly this device belong to it. Or, if it's an old model but just missing the USB ID entry in the probe table, it's easy to activate with the upstream kernel driver, too.
Basically someone who worked on the downstream driver should send the fix patch to the upstream, but it didn't happen automagically, unfortunately.
So would it be helpful if I open an issue at the mentioned github r8152 site and refer to this conversation here? -- You are receiving this mail because: You are on the CC list for the bug.