From owner-freebsd-questions Mon Dec 23 11:27:19 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA18169 for questions-outgoing; Mon, 23 Dec 1996 11:27:19 -0800 (PST) Received: from super-g.inch.com (super-g.com [204.178.32.161]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id LAA18163 for ; Mon, 23 Dec 1996 11:27:16 -0800 (PST) Received: from localhost (spork@localhost) by super-g.inch.com (8.8.4/8.6.9) with SMTP id OAA06763; Mon, 23 Dec 1996 14:31:50 -0500 (EST) Date: Mon, 23 Dec 1996 14:31:50 -0500 (EST) From: spork X-Sender: spork@super-g.inch.com To: Leslie Davisson cc: freebsd-questions@freebsd.org Subject: Re: customizing the kernel In-Reply-To: <9612231815.AA08760@handset.laa.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I recently customized my kernel for my i386 box using Section 5 of > the FreeBSD handbook. My kernel compiled and booted the machine. > However, none of my network functionality was present. There are a few other things you can look at while you're working on this; it looks as though you copied the LINT file and went with that... That's a bit counter-productive. For example, on this block, comment out all but the cpu that you are running: > > machine "i386" > cpu "I386_CPU" > cpu "I486_CPU" > cpu "I586_CPU" You have a name, your kernel should too! > ident GENERIC > maxusers 10 > > options MATH_EMULATE #Support for x87 emulation > options INET #InterNETworking > options FFS #Berkeley Fast Filesystem > options NFS #Network Filesystem > #options MSDOSFS #MSDOS Filesystem > options "CD9660" #ISO 9660 Filesystem > options PROCFS #Process filesystem > options "COMPAT_43" #Compatible with BSD 4.3 > options "SCSI_DELAY=15" #Be pessimistic about Joe > SCSI device > options BOUNCE_BUFFERS #include support for DMA > bounce buffers > #options UCONSOLE #Allow users to > grab the console > options "FAT_CURSOR" #block cursor in syscons or > pccons > options "NCONS=4" #4 virtual consoles > options USERCONFIG #Allow user configuration with -c ****** Below is a problem; you added IPfirewalling support, which by default denies everything... I'd leave this out until you catch a chance to read up on it. You probably don't need the gateway or the additional ICMP options either. ****** > options GATEWAY #Pass packets > options IPFIREWALL #firewall code > options IPFIREWALL_VERBOSE #Print information about > dropped packets > options IPBROADCASTECHO=1 #send reply to broadcast pings > options IPMASKAGENT=1 #send reply to icmp mask requests > #options SYSVSHM > #options SYSVSEM > #options SYSVMSG > > config kernel root on wd0 > > controller isa0 > #controller eisa0 > controller pci0 [snip] > device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr > device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr Do you need com3 and 4? They are vying for the same IRQ as one of your network cards... > device sio2 at isa? port "IO_COM3" tty irq 5 vector siointr > device sio3 at isa? port "IO_COM4" tty irq 9 vector siointr You also have two network cards set to the same IRQ... If you actually have two, one of them needs to be set to a different IRQ I believe. > device ed0 at isa? port 0x280 net irq 5 iomem 0xd8000 vector edintr > device ed1 at isa? port 0x300 net irq 5 iomem 0xd8000 vector edintr Unless you need it, this is not necessarily a good idea. > pseudo-device bpfilter 1 > > I think this helps? Charles