[opensuse] How to tell SuSE folks to NOT include yealink driver in their distro
The USB TelBox (allows your phone to send/receive both POTS and Skype calls) only works with the drivers from kb2skype.sourceforge.net. The Yealink driver only works with a closed-source front-end that (supposedly) worked in an old version of Fedora. I've talked to the folks at Yealink numerous times, and they have no intention to update the software for current distros, nor open source the front-end software, so there's absolutely no possibility this driver would work... yet every SuSE update includes this POS driver. Every time I get a kernel patch from SuSE, and reboot the system, this f*g yealink.ko driver loads, and I waste a few hours figuring out why my phone doesn't work... Yealink and kb2skype together cause system hangs and USB lock-ups. I see no reason why SuSE is including this driver (except to frustrate me). It has no useful purpose, and will not work under any conditions, and only causes grief. Who do we ask to get this POS removed from all future updates? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Mon, Nov 05, 2007 at 10:06:36AM -0600, Chris Worley wrote:
The USB TelBox (allows your phone to send/receive both POTS and Skype calls) only works with the drivers from kb2skype.sourceforge.net.
The Yealink driver only works with a closed-source front-end that (supposedly) worked in an old version of Fedora. I've talked to the folks at Yealink numerous times, and they have no intention to update the software for current distros, nor open source the front-end software, so there's absolutely no possibility this driver would work... yet every SuSE update includes this POS driver.
Every time I get a kernel patch from SuSE, and reboot the system, this f*g yealink.ko driver loads, and I waste a few hours figuring out why my phone doesn't work... Yealink and kb2skype together cause system hangs and USB lock-ups.
I see no reason why SuSE is including this driver (except to frustrate me). It has no useful purpose, and will not work under any conditions, and only causes grief.
Who do we ask to get this POS removed from all future updates?
Step 1. Open a bugreport. Since it is likely the kernel that contains this driver, assign to the Kernel component. Ciao, Marcus -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2007-11-05 at 10:06 -0600, Chris Worley wrote:
Who do we ask to get this POS removed from all future updates?
Open a bugzilla against the kernel, for instance. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFHL0UetTMYHG2NR9URAvK+AJ4teVHJw3mU1aEuZCY6NV/5jzUtawCeJo4L OmhX0QSEG0xiOAo2EK39fj8= =Ywh/ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2007-11-05 10:06:36 -0600, Chris Worley wrote:
Every time I get a kernel patch from SuSE, and reboot the system, this f*g yealink.ko driver loads, and I waste a few hours figuring out why my phone doesn't work... Yealink and kb2skype together cause system hangs and USB lock-ups.
you could blacklist the module. see /etc/modprobe.d/blacklist. darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday 05 November 2007 11:06, Chris Worley wrote:
The USB TelBox (allows your phone to send/receive both POTS and Skype calls) only works with the drivers from kb2skype.sourceforge.net.
The Yealink driver only works with a closed-source front-end that (supposedly) worked in an old version of Fedora. I've talked to the folks at Yealink numerous times, and they have no intention to update the software for current distros, nor open source the front-end software, so there's absolutely no possibility this driver would work... yet every SuSE update includes this POS driver.
Every time I get a kernel patch from SuSE, and reboot the system, this f*g yealink.ko driver loads, and I waste a few hours figuring out why my phone doesn't work... Yealink and kb2skype together cause system hangs and USB lock-ups.
I see no reason why SuSE is including this driver (except to frustrate me). It has no useful purpose, and will not work under any conditions, and only causes grief.
Who do we ask to get this POS removed from all future updates?
Someone smarter than me can probably write a script that will seek this out and delete it, as soon as it comes in, or at least, at a reboot. The gurus are invited here! --doug -- Blessed are the peacemakers ... for they shall be shot at from both sides. --A.M. Greeley -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Doug McGarrett escribió:
Someone smarter than me can probably write a script that will seek this out and delete it, as soon as it comes in, or at least, at a reboot.
not needed, modules can be blacklisted, see Marcus 's post. -- "Two things are infinite: the universe and human stupidity; and I'm not sure about the universe." --Albert Einstein Cristian Rodríguez R, Core Services SUSE LINUX Products GmbH Research & Development http://www.opensuse.org/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2007-11-05 at 21:10 -0300, Cristian Rodriguez wrote:
Doug McGarrett escribió:
Someone smarter than me can probably write a script that will seek this out and delete it, as soon as it comes in, or at least, at a reboot.
not needed, modules can be blacklisted, see Marcus 's post.
I believe that only has effect on automatic module loading. A script, for instance, can still load a blacklisted module. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFHL9yktTMYHG2NR9URAhmZAJ0b06dYvHA7FNiuChlXzfagUj7erACePGtM ctucxkuHmaWzyPf1m4SXK7U= =7D8W -----END PGP SIGNATURE-----
On 2007-11-06 04:16:49 +0100, Carlos E. R. wrote:
The Monday 2007-11-05 at 21:10 -0300, Cristian Rodriguez wrote:
Doug McGarrett escribió:
Someone smarter than me can probably write a script that will seek this out and delete it, as soon as it comes in, or at least, at a reboot.
not needed, modules can be blacklisted, see Marcus 's post.
I believe that only has effect on automatic module loading. A script, for instance, can still load a blacklisted module.
echo "install yealink /bin/true" >> /etc/modprobe.d/yealink should help with that too. darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
echo "install yealink /bin/true" >> /etc/modprobe.d/yealink
should help with that too.
darix
Can you kindly explain what effect this line has? I know that it will create/append a file named 'yealink' under /etc/modprobe.d, and that this file will contain the line 'install yealink /bin/true'. But what will happen when you do this? Thanks. Chua -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 06 November 2007 16:54:22 Chee How Chua wrote:
echo "install yealink /bin/true" >> /etc/modprobe.d/yealink
should help with that too.
darix
Can you kindly explain what effect this line has? I know that it will create/append a file named 'yealink' under /etc/modprobe.d, and that this file will contain the line 'install yealink /bin/true'. But what will happen when you do this?
It will prevent the module "yealink" from ever being loaded. The "install" directive tells modprobe what to do instead of loading the module. It can for example be used if certain commands need to be run before a module is loaded, in which case the line would contain those commands, and end with another call to modprobe In this case it will only run the command /bin/true, which does nothing and returns successfully Anders -- Madness takes its toll -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Chee How Chua wrote:
echo "install yealink /bin/true" >> /etc/modprobe.d/yealink
should help with that too.
Can you kindly explain what effect this line has? I know that it will create/append a file named 'yealink' under /etc/modprobe.d, and that this file will contain the line 'install yealink /bin/true'. But what will happen when you do this?
You should read "man modprobe.conf". An "install" primitive like the one mentioned above in modprobe's configuration file will tell modprobe to run the specified command /bin/true instead of actually inserting the module in the kernel. In other words, whenever modprobe receives the command to load the "yealink" module, it will run /bin/true instead which always returns successful. The solution presented above will therefore effectively prevent the loading of the yealink kernel module via modprobe. However, using insmod might still work for the yealink module. Cheers, Th. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Thanks for the clear explanation!
On Nov 7, 2007 2:41 AM, Anders Johansson
On Tuesday 06 November 2007 16:54:22 Chee How Chua wrote:
echo "install yealink /bin/true" >> /etc/modprobe.d/yealink
should help with that too.
darix
Can you kindly explain what effect this line has? I know that it will create/append a file named 'yealink' under /etc/modprobe.d, and that this file will contain the line 'install yealink /bin/true'. But what will happen when you do this?
It will prevent the module "yealink" from ever being loaded.
The "install" directive tells modprobe what to do instead of loading the module. It can for example be used if certain commands need to be run before a module is loaded, in which case the line would contain those commands, and end with another call to modprobe
In this case it will only run the command /bin/true, which does nothing and returns successfully
Anders
-- Madness takes its toll
On Nov 7, 2007 4:07 AM, Thomas Hertweck
Chee How Chua wrote:
echo "install yealink /bin/true" >> /etc/modprobe.d/yealink
should help with that too.
Can you kindly explain what effect this line has? I know that it will create/append a file named 'yealink' under /etc/modprobe.d, and that this file will contain the line 'install yealink /bin/true'. But what will happen when you do this?
You should read "man modprobe.conf". An "install" primitive like the one mentioned above in modprobe's configuration file will tell modprobe to run the specified command /bin/true instead of actually inserting the module in the kernel. In other words, whenever modprobe receives the command to load the "yealink" module, it will run /bin/true instead which always returns successful. The solution presented above will therefore effectively prevent the loading of the yealink kernel module via modprobe. However, using insmod might still work for the yealink module.
Cheers, Th.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (9)
-
Anders Johansson -
Carlos E. R. -
Chee How Chua -
Chris Worley -
Cristian Rodriguez -
Doug McGarrett -
Marcus Meissner -
Marcus Rueckert -
Thomas Hertweck