How do I kill module ds9490r?
I use 1-wire devices -- little chips and buttons made by Dallas Semiconductors that can monitor temperature, humidity, voltages, and switch things on and off. In fact there is quite a community around them, with everything from home HVAC and weatherstations, to door access control. The devices connect through either a serial or USB adapter, and that's where my problem lies. I head a software effort that has adapted the chips to linux, as a filesystem, among other ways. See http://owfs.sf.net It worked perfectly until SuSE 9.2 -- and the reason is SUSE now includes a kernel module ds9490r that attaches to the 1-wire USB adapter. And does nothing. It is an idea with no implementation. Unfortunately, I have to manually rmmod the module before my software, which uses libusb can attach to the device. I understand the wish to make SuSE as totipotent as possible out of the box. Loading a module with no utility that breaks existing software doesn't help, however. So, as simpler question, how do I disable autoloading of the ds9490r? Paul
Please explain "1-wire device." I spent my life in electrical engineering, and with virtually zero exceptions, it always took at least 2 wires to transfer any information or control. (There was something called "G-Line" but I never saw an example of it. Supposedly, it worked as an RF transmission line, and needed launcher cables at each end of several feet.) I realize that an antenna can be thought of as a "1-wire" device, but I don't think that's what the writer had in mind. --doug At 06:05 PM 1/30/2005 -0500, Paul Alfille wrote:
I use 1-wire devices -- little chips and buttons made by Dallas Semiconductors that can monitor temperature, humidity, voltages, and switch things on and off.
In fact there is quite a community around them, with everything from home HVAC and weatherstations, to door access control.
The devices connect through either a serial or USB adapter, and that's where my problem lies. I head a software effort that has adapted the chips to linux, as a filesystem, among other ways. See http://owfs.sf.net
It worked perfectly until SuSE 9.2 -- and the reason is SUSE now includes a kernel module ds9490r that attaches to the 1-wire USB adapter. And does nothing. It is an idea with no implementation.
Unfortunately, I have to manually rmmod the module before my software, which uses libusb can attach to the device.
I understand the wish to make SuSE as totipotent as possible out of the box. Loading a module with no utility that breaks existing software doesn't help, however.
So, as simpler question, how do I disable autoloading of the ds9490r?
Paul
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Sunday 30 January 2005 09:51 pm, Doug McGarrett wrote:
Please explain "1-wire device." I spent my life in electrical engineering, and with virtually zero exceptions, it always took at least 2 wires to transfer any information or control. (There was something called "G-Line" but I never saw an example of it. Supposedly, it worked as an RF transmission line, and needed launcher cables at each end of several feet.) I realize that an antenna can be thought of as a "1-wire" device, but I don't think that's what the writer had in mind.
--doug
Look, it's marketing. A name. "1-wire" Trademarked. Actually, it's rather interesting. One wire, plus a ground. Two wires. The data line and the power line are the same. Power is obtained "parasitically" from the data line. The other interesting aspect is that each device has a unique 64 bit number lasered into it, and each device is individually addressable. That means a very simple TWO wire line can have multiple networked devices, each costing around $1 and capable of some interesting properties, as I listed before (temperature, voltage, switching, memory, timers, encryption, even a small Java processor). What I did was map this 1-wire bus into a filesystem. Listing the filesystem shows the (dynamic) list of devices connected (named by their unique ID number) as directories, and their properties as files. You can then do a command like: cat 10.00234000/temperature to get the temperture. You can even symlink it to a more readable name. You can access the bus over a network with my program as well. We even have a project to insert a 1-wire controller and software into a wireless router that runs embedded linux. Cheap remote scriptable linux-based sensors. For more about 1-wire see: www.maxim-ic.com For more about my filesystem, see owfs.sourceforge.net --Paul
Paul Alfille <palfille@earthlink.net> [Sun, 30 Jan 2005 18:05:18 -0500]:
So, as simpler question, how do I disable autoloading of the ds9490r?
alias ds9490r off in /etc/modprobe.conf? But if the module is loaded via hotplug, it gets trickier. Philipp
On Tuesday 01 February 2005 08:57, Philipp Thomas wrote:
Paul Alfille <palfille@earthlink.net> [Sun, 30 Jan 2005 18:05:18 -0500]:
So, as simpler question, how do I disable autoloading of the ds9490r?
alias ds9490r off
in /etc/modprobe.conf?
Hm, isn't that install ds9490r /bin/true in kernel 2.6 newspeak?
Anders Johansson <andjoh@rydsbo.net> [Tue, 1 Feb 2005 09:31:49 +0100]:
Hm, isn't that
install ds9490r /bin/true
in kernel 2.6 newspeak?
Yes, it is. Seems like I'm living in the past, at least partially :) Hmm, reminds me of a record I've not listened to for a long time. Philipp
On Tuesday 01 February 2005 02:57 am, Philipp Thomas wrote:
Paul Alfille <palfille@earthlink.net> [Sun, 30 Jan 2005 18:05:18 -0500]:
So, as simpler question, how do I disable autoloading of the ds9490r?
alias ds9490r off
in /etc/modprobe.conf?
But if the module is loaded via hotplug, it gets trickier.
Philipp
I guess I need trickier.
On Tuesday 01 February 2005 06:08 am, Paul Alfille wrote:
So, as simpler question, how do I disable autoloading of the ds9490r?
Johannes Erdfelt offered a solution within LIBUSB, the generic USB device handler: a function called USB_detach_kernel_driver_np which will free up the usb port.
Paul References: http://libusb.sourceforge.net/doc/function.usbgetdrivernp.html http://libusb.sourceforge.net/doc/function.usbdetachkerneldrivernp.html
participants (4)
-
Anders Johansson -
Doug McGarrett -
Paul Alfille -
Philipp Thomas