hi, Am 2016-11-14 um 13:46 schrieb Andrei Borzenkov:
On Mon, Nov 14, 2016 at 3:24 PM, Rainer Klier <rainer.klier@xyzmo.com> wrote:
Am 2016-11-14 um 12:05 schrieb Andrei Borzenkov:
On Mon, Nov 14, 2016 at 1:55 PM, Rainer Klier <rainer.klier@xyzmo.com> wrote:
there are some reasons why i keep doing this: * i also recompile my wifi-driver wl.ko for my broadcom wifi card (hybrid-v35_64-nodebug-pcoem-6_30_223_271) * i also recompile the displaylink driver displaylink-driver-1.2.58
Care to provide link to both?
here are links to prepatched archives, so that the kernel modules can be built on tumbleweed with kernel 4.8.x: displaylink-driver-1.2.58: https://drive.google.com/open?id=0Bwpj5Wm8iVh-RHJVQmUtYWpEWDg hybrid-v35_64-nodebug-pcoem-6_30_223_271: https://drive.google.com/open?id=0Bwpj5Wm8iVh-VFZab1FLQVUzdGM
* last but not least: it doesn't hurt doing it.
It does. What you have there no more matches your running kernel.
why should it hurt? what do you mean? why should it not match the runing kernel? if it would be this case, all 4 kernel modules (nvidia, vmware, wl and displaylink) would not work. all i do is just prepare the /usr/src/linux-obj/x86_64/default folder for kernel module compiling. but when the next kernel update 4.8.8 arrives, i will try to make all 4 kernel modules WITHOUT the "make prepare" and "make modules_prepare". if it still works, then it is great to not need doing this on every kernel update. maybe this is not needed any more today for these 4 kernel modules. but it surely was. but i stll don't understand why it should be a problem doing it. -- Best Regards | Freundliche Grüße | Cordialement | Cordiali Saluti | *DI Rainer Klier* Research & Development, Technical Sales Consultant Namirial GmbH -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org