Subject: RE: FW: Multia pcmcia NIC adapter... I can't get it up!
To: 'Matt Thomas' <>
From: David Woyciesjes <>
List: port-alpha
Date: 04/26/2000 14:14:18
I'll give it a whack. Just send me the info and instructions...
In the meantime, I'm gonna jump in feet first and try building my own
John sent this to me, I'll just follow this... Please let me know if there
are any corrections or other notes. I also grabbed the NetBSD Kernel
Documentation too.

>Well, the question then becomes, can the support for the card definitely be
>enabled? Or would it be trial and error? What do you guys think? Is it
>it? Is there anyone else here who is in a similar spot? (PCMCIA NIC in a

As I said, it looks like one of the other kernel configs has support for 
it, and that means it can be enabled. It looks like pcmci support is not 
in the generic kernel - I don't know why, perhaps pcmci is just rare on 
multia systems, I don't know enough about alpha's to make a guess. A 
quick look through the ENIWETOK config shows nothing really out of the 
ordinary. My guess is that it's nothing special or difficult, and that 
means there's not much trial and error involved, just compile and build. 
The NetBSD folks are very conservative, if they feel support is not rock 
solid they will usually say so in the config files.

Here's a short version of what you have to do:

1. from, install the following packages:


2. (that means, download them, and do this, for all packages)

cd /
tar xzf comp.tgz

Here's the build steps (copied from a html page):

3. Building a kernel involves using a tool called config. Here's how to 
build that:

"cd /usr/src/usr.sbin/config ; make && make install" 

"cd /sys/arch/<ARCH>/conf"
where <ARCH> is your machine's architecture such as 'i386', 'sparc', 

where <MYCONF> is your name for this configuration. You could use your 
hostname, the machine type, or even your first name. Keep to letters, 
numbers, and _ characters. 

6.	Edit <MYCONF>
Initially you can skip this stage. You can remove drivers for CPU types, 
hardware, and devices you do not have or use, or even enable options, 
such as on i386 commenting out the 'pc0' line and enabling the 'vt0' to 
gain virtual consoles. A good start to determing what hardware drivers 
you definitely need to keep is to read the output of "dmesg" or "dmesg | 
grep ' at '". For evey line containing '<XXX> at <YYY>' you need to keep 
the entries for both <XXX> and <YYY>. You should also read "options(4)" 
for information on the different kernel configuration options. 

7.	"config <MYCONF>"
This will generate the kernel build directory for <MYCONF>. 

8.	"cd ../compile/<MYCONF>"
Change to the kernel build directory. 

9.	"make depend"
This generates a '.depend' file that enables the make program to what 
needs to be rebuilt (at this point it will be everything!). 

10.	"make"
This will compile the kernel. If all goes well you will be left with a 
'netbsd' kernel. This may take some significant time if you are on a VAX, 
very little time on a big Alpha, and somewhere inbetween for the rest of 

11.	"mv /netbsd /netbsd.old ; mv netbsd /"
This saves your current kernel, (_very_ important), and moves the new 
kernel ready to be booted. 

12.	"reboot"
This should reboot using your new kernel - the boot messages should 
contain a line of the form: 'NetBSD <VERSION> (<MYCONF>) #0: 

13.	If you have any problems:
You should boot your 'netbsd.old' kernel in single user mode. The 
procedure varies from port to port depending on the boot procedure, but 
on i386 it would be: 
1.	Press SPACE when the first NetBSD message appears
2.	"boot -s netbsd.old"
Then swap your kernel back: 
1.	"fsck /"
2.	"mount /"
3.	"mv netbsd.old netbsd"
4.	"exit"

In your case, you'd add these lines to the config file:

pcmcia*   at   pcic? controller    ?    socket    ?
ep*  at   pcmcia?   function  ?    # 3com 3c589 and 3c562


---   David A Woyciesjes
---   C & IS Support Specialist
---   Yale University Press
---   (203) 432-0953
---   ICQ # - 905818

> ----------
> From: 	Matt Thomas
> Sent: 	Wednesday, April 26, 2000 1:40 PM
> To: 	David Woyciesjes
> Subject: 	Re: FW: Multia pcmcia NIC adapter... I can't get it up!
> Pretty much.  However I'm building a new GENERIC kernel with
> PCMCIA support right now. (1.4X)  Let me know if you'd want to
> try it...
> -- 
> Matt Thomas               Internet:
> 3am Software Foundry      WWW URL:
> Cupertino, CA             Disclaimer: I avow all knowledge of this message