Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.uwa.edu.au!classic.iinet.com.au!swing.iinet.net.au!news.uoregon.edu!usenet.eel.ufl.edu!tank.news.pipex.net!pipex!news.mathworks.com!newsfeed.internetmci.com!in2.uu.net!hoho.quake.net!usenet From: bard@tiamat.chaldea.com (David Hopper) Newsgroups: comp.unix.bsd.netbsd.misc Subject: Re: Rebuilding 1.0 Amiga kernel Followup-To: comp.unix.amiga Date: 1 Nov 1995 18:03:19 GMT Organization: Kitty Empire Lines: 47 Distribution: world Message-ID: <478cp7$drd@hoho.quake.net> References: <474c8m$48n@mirv.unsw.edu.au> Reply-To: bard@tiamat.chaldea.com NNTP-Posting-Host: tiamat.chaldea.com In article <474c8m$48n@mirv.unsw.edu.au>, amiga@cse.unsw.edu.au (Amiga Utilities) writes: > Hello everybody, > > I am trying to rebuild the Amiga 1.0 kernel from the 1.0 distribution. > When I get the GENERIC kernel happening I will fold in the FastLane > drivers. The problem I am having is that after I do a succesfull > make in the compile directory and /dev/reload the kernel, I get a > blank screen. You shouldn't /dev/reload a newly compiled kernel; you need to loadbsd the test kernel from AmigaDOS. Either get the kernel over to an Amiga partition (e.g. by FTP to a second machine) or use BFFS under AmigaDOS to mount the NetBSD root partition, then loadbsd -a BFFS:<path of new kernel>. > The hard drive seems to go through some initial boot > processing and the modem gets lots of data that makes it go repeatedly > onhook and offhook and then stopping with the TxD and RxD lights lit > up. The keyboard is dead too. 1) see the kernel problem above, or 2) Your /dev/tty*s may be broken... Become root and do a MAKEDEV all under /dev, and make sure that your /etc/ttys file reads 'off' for the /dev/tty00 entry, and 'on' only for your console of choice. > The reason I am not using -current is because it has problems with > both root and usr partitions. It thinks that they are not clean and > when fsck does it's bit they either get trashed even more, or just > not fixed. You've got to be sure to use a binary snapshot that closely matches the -current kernel sources you're compiling. If your 1.0 fsck smells a -current kernel, it's gonna choke. I would recommend waiting until Nov. 17 (or so), when 1.1 is frozen. Pull down a binary distribution then. After that, it will be easier to rebuild your kernel. > Peter Urbanec > /// amiga@cse.unsw.edu.au | David Hopper (bard@tiamat.chaldea.com) | Anthropology Major, Leland Stanford Junior University | Senior Technical Consultant, Excell Data Corporation @ Microsoft Corp. | NetBSD 1.1ALPHA (tiamat.chaldea.com) : NEXTSTEP 3.3 (marduk.chaldea.com)