Hi. I bought a Ximeta Netdisk (http://ximeta.com/products/netdisk.html) which is an external HDD with both USB and network connectivity. The company explicitly states that the device works with Red Hat 8 and 9, but I've had no luck with it. The drivers are available only as RPMs, no source provided. It's network attached, but it doesn't use a standard protocol. The RPM is supposed to install two modules, nd.o and lpx.o, but they don't show up with lsmod. When I try to load them with insmod or modprobe, I get a bunch of error messages about "unresolved symbols". I though it may have been a dependency problem, so I recompiled to load network block device (nbd.o), but that had no effect. I've tried both RH 8 and 9 fresh stock installs with the same results. Ximeta has stated that they will provide me a new driver, but I'm not holding my breath. Any suggestions? Thanks.
On Wed, Feb 11, 2004 at 10:47:47AM -0500, Clint Moyer wrote:
I've tried both RH 8 and 9 fresh stock installs with the same results. Ximeta has stated that they will provide me a new driver, but I'm not holding my breath.
Any suggestions?
Return it? Seriously, if you can't get a stock install of the claimed compatible distributions to work, how long do you think the company will continue to update the binary-only drivers for future kernel releases/distributions?
On Wed, Feb 11, 2004 at 10:47:47AM -0500, Clint Moyer wrote:
It's network attached, but it doesn't use a standard protocol. The RPM is supposed to install two modules, nd.o and lpx.o, but they don't show up with lsmod. When I try to load them with insmod or modprobe, I get a bunch of error messages about "unresolved symbols". I though it may have been a dependency problem, so I recompiled to load network block device (nbd.o), but that had no effect.
I'd attack this two ways. First, did you drop them into /lib/modules/whatever and run "depmod -a"? You'll need that to figure out the dependencies, so that modprobe can auto-load dependent modules. Second, if you have the kernel source, you can search for the names of the unresolved symbols and find out what drivers provide them. -Chuck
On Wed, Feb 11, 2004 at 11:08:45AM -0500, Charles R. Anderson wrote:
Any suggestions?
Return it? Seriously, if you can't get a stock install of the claimed compatible distributions to work, how long do you think the company will continue to update the binary-only drivers for future kernel releases/distributions?
Ummm... that too. A binary-only driver has a wiked short shelf-life. Unless you talk driver source code out of them, or never upgrade your kernel (once you finally get it working), this will be a pain in your ass forever. -Chuck
participants (3)
-
Charles R. Anderson -
Chuck Homic -
Clint Moyer