Date: Tue, 24 Aug 1999 13:43:03 +0200 (MET DST) From: Nick Hibma <nick.hibma@jrc.it> To: Andrew Grillet <andrew@grillet98.freeserve.co.uk> Cc: freebsd-bugs@FreeBSD.ORG Subject: Re: kern/13307: Cant build kernet for 2.2.8 Message-ID: <Pine.GSO.3.95q.990824134142.639D-100000@elect8> In-Reply-To: <199908240540.WAA52984@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Could you try the following entry? # The "unknown" device (uk? in pre-2.0.5) is now part of the base SCSI # configuration and doesn't have to be explicitly configured. controller scbus0 #base SCSI code device ch0 #SCSI media changers device sd0 #SCSI disks device st0 #SCSI tapes device cd0 #SCSI CD-ROMs device od0 #SCSI optical disk # The previous devices (ch, sd, st, cd) are recognized by config. # config doesn't (and shouldn't) know about these newer ones, # so we have to specify that they are on a SCSI bus with the "at scbus?" # clause. device worm0 at scbus? # SCSI worm device pt0 at scbus? # SCSI processor type device sctarg0 at scbus? # SCSI target This is the section taken from LINT. Cutting and pasting this into your kernel configuration should (hopefully) work rightaway. If this works, probably someone forgot to update the man page to reflect this. Nick On Mon, 23 Aug 1999, Andrew Grillet wrote: > The following reply was made to PR kern/13307; it has been noted by GNATS. > > From: Andrew Grillet <andrew@grillet98.freeserve.co.uk> > To: Sheldon Hearn <sheldonh@uunet.co.za> > Cc: > Subject: Re: kern/13307: Cant build kernet for 2.2.8 > Date: Mon, 23 Aug 1999 20:03:36 +0100 > > This is a multi-part message in MIME format. > --------------1F939406A0558CD3C2DB6C36 > Content-Type: text/plain; charset=us-ascii > Content-Transfer-Encoding: 7bit > > > > Sheldon Hearn wrote: > > > > Hi Andrew, > > > > Nick's already asked for your kernel config file, but something else > > that'd be useful is for you to describe _exactly_ what commands you type > > and _exactly_ what messages you get back from each command. Whether you > > cut'n'paste or use something like script(1) doesn't reall matter, so > > long as you provide more precise info. > > > much ftping and hacking later, I have a copy of my conf file. I ahve > added some theoretically helpful comments explaining my understanding > of the state of affairs. > > It is quite possible that the problem lies in my grasp of what is going > on > rather than a defect in code. However, I regard the docs as a necessary > part of the system. - after all, if it don't work, it don't work :-) > > I have a new problem - yesterday, I tried to send several e-mails > on this issue, including one to Nick Hibma. I got a message from > freeserve (my ISP) that I was not allowed to send the messages, but > they may have been sent anyway! > > This is NOT FreeBSD's fault, but may explain several copies of some > e-mails and none of others :-( [I blame B. Gates - its ALL his fault]. > > Andrew > --------------1F939406A0558CD3C2DB6C36 > Content-Type: text/plain; charset=us-ascii; > name="Turnip.cfg" > Content-Transfer-Encoding: 7bit > Content-Disposition: inline; > filename="Turnip.cfg" > > # TURNIP -- Andrew's Pentium with WD/AHx/NCR/BTx family disks > # > # For more information read the handbook part System Administration -> > # Configuring the FreeBSD Kernel -> The Configuration File. > # The handbook is available in /usr/share/doc/handbook or online as > # latest version from the FreeBSD World Wide Web server > # <URL:http://www.FreeBSD.ORG/>; > # > # An exhaustive list of options and more detailed explanations of the > # device lines is present in the ./LINT configuration file. If you are > # in doubt as to the purpose or necessity of a line, check first in LINT. > # > > machine "i386" > cpu "I386_CPU" > cpu "I486_CPU" > cpu "I586_CPU" > cpu "I686_CPU" > ident TURNIP > maxusers 32 > > 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 [KEEP THIS!] > 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 FAILSAFE #Be conservative > options USERCONFIG #boot -c editor > options VISUAL_USERCONFIG #visual boot -c editor > > config kernel root on wd0 > > controller isa0 > # I tried disabling the next line - it caused errors! > controller eisa0 > controller pci0 > > controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr > disk fd0 at fdc0 drive 0 > disk fd1 at fdc0 drive 1 > # Unless you know very well what you're doing, leave ft0 at drive 2, or > # remove the line entirely if you don't need it. Trying to configure > # it on another unit might cause surprises, see PR kern/7176. > # tape ft0 at fdc0 drive 2 > > options "CMD640" # work around CMD640 chip deficiency > controller wdc0 at isa? port "IO_WD1" bio irq 14 vector wdintr > disk wd0 at wdc0 drive 0 > disk wd1 at wdc0 drive 1 > > controller wdc1 at isa? port "IO_WD2" bio irq 15 vector wdintr > disk wd2 at wdc1 drive 0 > disk wd3 at wdc1 drive 1 > > options ATAPI #Enable ATAPI support for IDE bus > options ATAPI_STATIC #Don't do it as an LKM > device wcd0 #IDE CD-ROM > device wfd0 #IDE floppy (LS-120) > > # A single entry for any of these controllers (ncr, ahb, ahc, amd) is > # sufficient for any number of installed devices. > > controller ncr0 > controller amd0 > # controller ahb0 > controller ahc0 > # controller dpt0 > controller bt0 at isa? port "IO_BT0" bio irq ? vector bt_isa_intr > # controller uha0 at isa? port "IO_UHA0" bio irq ? drq 5 vector uhaintr > controller aha0 at isa? port "IO_AHA0" bio irq ? drq 5 vector ahaintr > controller aic0 at isa? port 0x340 bio irq 11 vector aicintr > # controller nca0 at isa? port 0x1f88 bio irq 10 vector ncaintr > # controller nca1 at isa? port 0x350 bio irq 5 vector ncaintr > # controller sea0 at isa? bio irq 5 iomem 0xc8000 iosiz 0x2000 vector seaintr > > options DPT_MEASURE_PERFORMANCE # Required by DPT driver?? > #options DPT_VERIFY_HINTR # Some hardware must have it! > #options DPT_TRACK_CCB_STATES # Some hardware must have it! > #options DPT_HANDLE_TIMEOUTS # Some hardware must have it! > #options DPT_TIMEOUT_FACTOR=4 # Some hardware needs more > > #***************************************************** > # This is where the problems start: > controller scbus0 at aha0 > # and stick the devices on the bus... > > disk worm0 at scbus0 target 6 unit 0 # requires explicit declaration > # You cannot connect the worm directly to the host adaptor - the kernel > just won't build. - that was my original problem. > # You also cannot do > # disk worm at scbus? > # it is not permitted for 'new' devices. > > # the above builds a worm device with no error messages, but > # it doesn't work 'device not configured' > > #******************************************************8 > # after this we are OK .... > device sd0 # scsi disk > > device od0 #optical disk - See LINT for possible `od' options. > > device st0 > > device cd0 #Only need one of these, the code dynamically grows > > # device wt0 at isa? port 0x300 bio irq 5 drq 1 vector wtintr > # device mcd0 at isa? port 0x300 bio irq 10 vector mcdintr > > # controller matcd0 at isa? port 0x230 bio > > # device scd0 at isa? disable port 0x230 bio > > # syscons is the default console driver, resembling an SCO console > device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr > # Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver > # device vt0 at isa? port "IO_KBD" tty irq 1 vector pcrint > #options XSERVER # support for X server > #options FAT_CURSOR # start with block cursor > # If you have a ThinkPAD, uncomment this along with the rest of the PCVT lines > #options PCVT_SCANSET=2 # IBM keyboards are non-std > > # Mandatory, don't remove > device npx0 at isa? port "IO_NPX" flags 0x1 irq 13 vector npxintr > > # > # Laptop support (see LINT for more options) > # > device apm0 at isa? disable # Advanced Power Management > options APM_BROKEN_STATCLOCK # Workaround some buggy APM BIOS > # PCCARD (PCMCIA) support > #controller card0 > #device pcic0 at card? > #device pcic1 at card? > > device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr > device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr > device sio2 at isa? disable port "IO_COM3" tty irq 5 vector siointr > device sio3 at isa? disable port "IO_COM4" tty irq 9 vector siointr > > device lpt0 at isa? port? tty irq 7 vector lptintr > device lpt1 at isa? disable port? tty > # device mse0 at isa? port 0x23c tty irq 5 vector mseintr > > device psm0 at isa? disable port "IO_KBD" conflicts tty irq 12 vector psmintr > > # Order is important here due to intrusive probes, do *not* alphabetize > # this list of network interfaces until the probes have been fixed. > # Right now it appears that the ie0 must be probed before ep0. See > # revision 1.20 of this file. > device de0 > device fxp0 > device tl0 > device tx0 > device vx0 > device xl0 > > device ed0 at isa? port 0x300 net irq 5 iomem 0xd0000 vector edintr > # device ie0 at isa? port 0x300 net irq 10 iomem 0xd0000 vector ieintr > # device ep0 at isa? port 0x300 net irq 10 vector epintr > # device ex0 at isa? port? net irq? vector exintr > # device fe0 at isa? port 0x300 net irq ? vector feintr > # device le0 at isa? port 0x300 net irq 5 iomem 0xd0000 vector le_intr > # device lnc0 at isa? port 0x280 net irq 10 drq 0 vector lncintr > # device ze0 at isa? port 0x300 net irq 5 iomem 0xd8000 vector zeintr > # device zp0 at isa? port 0x300 net irq 10 iomem 0xd8000 vector zpintr > # device cs0 at isa? disable port 0x300 net irq ? vector csintr > > pseudo-device loop > pseudo-device ether > pseudo-device log > pseudo-device sl 1 > pseudo-device ppp 1 > pseudo-device vn 1 > pseudo-device tun 3 > pseudo-device pty 16 > pseudo-device gzip # Exec gzipped a.out's > > # KTRACE enables the system-call tracing facility ktrace(2). > # This adds 4 KB bloat to your kernel, and slightly increases > # the costs of each syscall. > options KTRACE #kernel tracing > > # This provides support for System V shared memory. > # > options SYSVSHM > > > --------------1F939406A0558CD3C2DB6C36-- > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-bugs" in the body of the message > > -- ISIS/STA, T.P.270, Joint Research Centre, 21020 Ispra, Italy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.3.95q.990824134142.639D-100000>