[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-developers] qube3 - eth2
- Subject: Re: [cobalt-developers] qube3 - eth2
- From: Harald Kapper <hk@xxxxxxxxxx>
- Date: Wed Jun 5 01:46:01 2002
- Organization: kapper.net
- List-id: Discussion Forum for developers on Sun Cobalt Networks products <cobalt-developers.list.cobalt.com>
On Mon, 03 Jun 2002 13:25:21 -0700, you wrote:
>Harald Kapper wrote:
>
>>>>anyone got a 3com vortex module for the 2.2.16C32_III+VPN kernel?
>>>>
>>>you can always compile your own... :)
>>>
>>
>>hi
>>well, if I only found the srpm's for this very kernel..
>>
>
>ftp://ftp-eng.cobalt.com/pub/products/qube3/RPMS/kernel-source-2.2.16C32_III+VPN-2.i386.rpm
>
>Sources, not the srpm.
hi
thanks to will - now it works ;-)
anyone else who might seek a 3com-card-solution for the qube3 (as the third NIC),
I point here: http://archive.kapper.net/ftp/unix/cobalt-qube3/nic-modules/
btw. only 3com-vortex compatibles supported (anyone else needs other modules, I'll try to build if required)
of course the following procedure is unsupported and might break your warranty:
check that you really have the latest kernel by logging into your qube and
do:
ls /lib/modules/ -la <enter>
here is what I get:
total 10
drwxr-xr-x 8 root root 1024 Mar 19 02:28 .
drwxr-xr-x 4 root root 3072 Jun 3 07:00 ..
drwxr-xr-x 2 root root 1024 Jul 3 2001 2.2.16C24_III
drwxr-xr-x 2 root root 1024 Jan 5 13:51 2.2.16C27_III
drwxr-xr-x 2 root root 1024 Mar 19 02:28 2.2.16C32_III
drwxr-xr-x 9 root root 1024 Mar 19 02:30 2.2.16C32_III+VPN
drwxr-xr-x 2 root root 1024 Jul 3 2001 2.2.16C7
drwxr-xr-x 2 root root 1024 Mar 19 02:28 phoenix
the provided 3com-module is only for the kernel:
2.2.16C32_III+VPN
so if you don't have it it won't work.
the su to root:
su - <enter>
<enter your root password>
do:
cat /proc/sys/kernel/osrelease <enter>
should give:
2.2.16C32_III+VPN
(ok this is just to make really sure what we got)
now move the 3c59x.o module into this directory:
/lib/modules/2.2.16C32_III+VPN/net/
now make a backup of your /etc/modules.conf file (before you edit)
eg.
cp /etc/modules.conf /etc/modules.conf.originalcobalt (or so)
then edit modules.conf with your favorite editor and find two lines:
# the default network card to look for in the PCI slot
alias eth2 off
change this lines to
# the default network card to look for in the PCI slot
alias eth2 3c59x
(telling the init scripts to load the 3com at startup finally)
now make a backup of your:
/lib/modules/2.2.16C32_III+VPN/modules.dep file to eg. /lib/modules/2.2.16C32_III+VPN/modules.dep.originalcobalt
and then edit this one and probably search for a line like:
/lib/modules/2.2.16C32_III+VPN/net/eepro100.o:
(this btw. shows that the eepro100 module does not depend on any other modules)
copy the above line and change your new copy to:
/lib/modules/2.2.16C32_III+VPN/net/3c59x.o:
(telling the system we don't have dependencies for the 3com either)
now reboot the box.
finally the pkgmaster.com eth2 package for the qube now should be able to startup the 3com and configure it.
you can always check back by ssh'ing into your qube and saying "ifconfig" - it should show you eth0, eth1, eth2 (at least if it's configured).
hope this helps
hk
ps. I strongly encourage sun/cobalt to include at least support for major brands of hardware in their future releases, because it's definitely hard to tell to our customers that even 3com hardware is not supported by sun...