Return to BSD News archive
Newsgroups: comp.os.386bsd.bugs Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!sleeper!quentin From: quentin@sleeper.uucp (Quentin Conner) Subject: Re: patchkit-0.2.2 kernel re-build too big!? Message-ID: <C4GAGv.JxF@sleeper.uucp> Organization: Indepth Data Inc. X-Newsreader: TIN [version 1.1 PL8] References: <1993Mar23.182207.25592@melb.bull.oz.au> Date: Thu, 25 Mar 1993 15:17:18 GMT Lines: 72 Simon J Gerraty (sjg@melb.bull.oz.au) wrote: : File too big to load - didn't load 386bsd The solution to this problem is to use the bootblocks from Julian Eishcner. I grabbed them off ref some time ago and just put them on last night. His version of wdboot/bootwd will load larger kernels and seems to work fine. I was motiviated by my ongoing problem -> running two ESDI drives and two SCSI drives. I can separately disklabel each ESDI and SCSI drive but get kernel panics: kmem_map too small when I attempt to access the fourth drive (or the third if my CMOS has both ESDI's configured). Solution (I am told) is to run Julians SCSI driver. Okay, get the sources, config, make, install -> File too big problem. Below is how I installed the bootblock, although I can't get my new kernel to see my Adaptec 1542B card (But I'm making progress and learing a great deal in the process...) 0) RTM. Check disklabel(8), disktab(5) 1) Try agate:unofficial/from.ref/julian-bootblocks Put them in /sys/i386/boot. 2) Make. 3) Edit the Makefile entry for wd0 (if you are talking ESDI) and put in your disktab entry and label. BE SURE THAT YOUR /etc/disktab has the CORRECT entry for your current wd0 disk! You can get it from disklabel -r. 4) Make wd0 (or Make sd0 for SCSI). This should replace the distribution bootblocks in /usr/mdec and on your disk. You might want to save the ones in /usr/mdec just in case. 5) When you reboot, you'll know if you got it right ;-) ==================== Now, if someone wants to help me: 1) Do I have to set sf in my disktab to take advantage of bad 144 sector remapping? My drives are junkers, and I need to remap some places. Do some controllers (WD1007) not support this? Mine seems to work either way although I haven't tried remapping. 2) Is there a format(8) program like on SunOs? I wrote a cheesey verify program of my own to find the bad places. 3) Is the AHBTEST configuration file correct for Julian's scsi drivers? It doesn't spell out the I/O address nor the DMA channel. The IRQ is at 12 though. I have tried it several ways and the kernel never finds my 1542B. I have not tried the latest patchkit 0.2.2 since I want to get Julians SCSI from 0.2.1 working first. 4) I have recompiled the entire system and had a lot of fun doing it. Learned a lot too. I hope everyone else is enjoying this as much as I am... Quentin Conner -------------- sleeper!quentin@kittyhawk.ecn.uoknor.edu or sleeper!quentin@occrsh.att.com or ...!kittyhawk.ecn.uoknor.edu!sleeper!quentin or ...!uunet!att!occrsh!sleeper!quentin -- Quentin Conner -------------- sleeper!quentin@kittyhawk.ecn.uoknor.edu or sleeper!quentin@occrsh.att.com