[driverloader] unresolved symbols?

burgeke at HQ.VerizonWireless.com burgeke at HQ.VerizonWireless.com
Thu Apr 22 08:02:39 EDT 2004


Glad you got it worked out!

-----Original Message-----
From: Doug Gallarda [mailto:driverloader at gallarda.net] 
Sent: Wednesday, April 21, 2004 9:25 PM
To: burgeke at HQ.VerizonWireless.com; driverloader at lists.linuxant.com;
tobin at coziahr.com
Subject: RE: [driverloader] unresolved symbols?

--On Wednesday, April 21, 2004 3:06 PM -0400 burgeke at HQ.VerizonWireless.com
wrote:

> Not using Sun JDS by chance are you? It is based off of SLED 1.0 but 
> has a slightly different patched kernel.
>
> I was able to use the generic RPM without error under JDS.

Yes, I am using Sun JDS.  I tried the generic RPM and it installed fine.
Thanks for your response!

The licensing web page worked great, but I ran into two more problems before
I could start using the card:

1) An ifcfg-eth1 file was created in /etc/sysconfig/network, but it was
empty.  I had to populate the file by hand because Yast didn't like an empty
file.  Here's what I used:

DHCLIENT_PRIMARY_DEVICE='yes'
BOOTPROTO='dhcp'
DHCLIENT_SET_DOWN_LINK='yes'
STARTMODE='onboot'
WIRELESS='yes'
WIRELESS_ESSID='MySSID'
WIRELESS_MODE='Managed'
REMOTE_IPADDR=''
UNIQUE=''
WIRELESS_KEY=''
WIRELESS_NICK=''
WIRELESS_NWID=''

2) The "driverloader" module was not loading at boot.  I noticed that
eth1 did not have an alias entry in /etc/modules.conf.  After I added the
following alias entry the module loads fine:

alias eth1 driverloader

Thanks again for the help!

Doug.


More information about the driverloader mailing list