hi again.
I found the info somewhere on the web.. I don't remember where:
kernel_version=`hostname`
pcimap=/lib/modules/$kernel_version/modules.pcimap
alldev=$(lspci -n| sed -e 's/^.*:[[:blank:]]\+\([^[:blank:]]\+\).*$/\1/')
if [ -n "$alldev" -a -r $pcimap ]
then
for i in $alldev
do
vendor="$(echo $i| cut -d':' -f1)"
device="$(echo $i| cut -d':' -f2)"
all_modules=`grep "0x0000$vendor[[:blank:]]\+0x0000$device" $pcimap \
|awk '{ print $1 }'|sort -u`
for module in $all_modules
do
find /lib/modules/$kernel_version/kernel/drivers/net/ -name \
"$module.o"|grep $module > /dev/null
if [ $? = 0 ]
then
echo $module
fi
done
done
fi
This should give you what you are looking for.
Regards,
Damien.
"george_king"
ustc.edu
To:
01/04/2004 15:31 "damien.selles" , "george_king"
Please respond to cc:
george_king "suse-autoinstall "
Subject:
Re: Re: [suse-autoinstall] Two type network adapters problem
---------------------------------------------------------------------------------------------------------------------------------------------------
BTW, do you know how to identify the module name
used by a network interface?
Replyed From: george_king
<br><br>> <br>> Hi
Georges,<br>> <br>> I have had some similar issues
with several network cards in the server.<br>> And
I did not find any autoyast option/function to
solve it.<br>> The solution I found was a
postscript, as you mentionned.<br>> <br>> Now, if
you have only one network card to configure, to
can proceed that<br>> way:<br>> <br>> 1- identify
the Mac address of the used card<br>> 2- identify
the module used by this card<br>> 3- configure
"nameif" to create "your_eth" ... (man nameif
:p )<br>> 4- create the ifcfg-your_eth file<br>>
5- update /etc/modules.conf with "alias your_eth
module"<br>> <br>> it should bypass your iss
r>> other modules loaded.<br>> <br>> In case you
are relunctant to use nameif... well.. your post
script must be<br>> a bit more complex..<br>> but
it is still possible. :))<br>> <br>> hope it will
help.<br>> <br>> <br>> Regards,<br>> Damien.<br>>
<br>> <br>> <br>> <br>>
<br>>
<br>>
"george_king"
<br>>
<br>>
ustc.edu
<br>>
To:
<br>>
01/04/2004 13:56
"suse-autoinstall"
<br>>
Please respond to
cc:
<br>>
george_king
<br>>
<br>>
<br>>
<br>>
Subject:
<br>>
[suse-autoinstall]
Two type network adapters problem
<br>>
<br>>
-------------------------------------------------------------------------------------------------------------------------------------------------
<br>> <br>> <br>> <br>> Hi,<br>> <br>> I encounter
a problem when I use autoyast to<br>> install a
machine with two type network adapters.<br>> <br>>
The target machine have two types of network<br>>
adapter. Since the number of network adapters
is<br>> not fixed, I can not tell autoyast xml
file how<br>> many network interface should be
configured. I<br>> write a post-install script to
config the network<br>> adapter used for network
install. What I do is 1)<br>> add alias to
modules.conf 2) add ifcfg-eth? files.<br>> <br>>
The way can work in most of cases. But in
follow<br>> case, it fail --<br>> during
installation, autoyast find three interface<br>>
eth0 3c59x<br>> eth1 3c59x<br>> eth2 e100 --
It is for network install.<br>> <br>> My script
will add "alias eth2 e100" to<br>>
modules.conf.<br>> <br>> When the system reboot,
it can not bring up e100<br>> network adapter. I
can make it work by change<br>> "eth2" to eth0 .
It seems that kernel think e100<br>> is "eth0"
because 3c59x was not loaded.<br>> <br>> Since
network type and network adapter number is<br>>
not fixed, i can not make my script to config
all<br>> found network adapters. Does autoyast xml
can<br>> probe all found network adapter and
make<br>> configuration for all of them? If so,
what shall<br>> we do?<br>> <br>> <br>> --<br>>
USTC Alumni Email System<br>> <br>> <br>> <br>>
<br>> <br>> <br>> <br>> <br>> -- <br>> To
unsubscribe, e-mail:
suse-autoinstall-unsubscribe@suse.com<br>> For
additional commands, e-mail:
suse-autoinstall-help@suse.com<br>> <br>> <br><br>
--
USTC Alumni Email System
