Date: Fri, 14 Apr 1995 21:36:17 -0700 (PDT) From: kargl@crosby.apl.washington.edu (Steven G. Kargl) To: bde@zeta.org.au (Bruce Evans) Cc: freebsd-current@FreeBSD.org Subject: Re: 0412-SNAP is FUBAR Message-ID: <9504150436.AA13737@crosby.apl.washington.edu.apl.washington.edu> In-Reply-To: <199504150131.LAA31047@godzilla.zeta.org.au> from "Bruce Evans" at Apr 15, 95 11:31:59 am
next in thread | previous in thread | raw e-mail | index | archive | help
Bruce Evans > >>First, my hardware was running -current, but I wasn't using Bruce's >>diskslice stuff or the newer sysconfig stuff. I also needed to adjust >>my swapspace because of new 16MB SIMM. So, I decided to checkout >>the new SNAP-0412. > >>MISTAKE #1!!!!!! > >The SNAP isn't supposed to have diskslice stuff. This means that you >might have problems going back to it if you were current :-). > Hmmm... I thought I saw a message go by in cvs0-all about your commits of diskslice code for scsi disk. I do recall a long email describing the method of going from pre-slice to post-slice geometry. I thought the SNAP would have the scsi slice code included. I restoreing -current from tape, will sup, then rebuild the system. >>(2) Upon rebooting the installed kernel successfully probed my ep0 >> device as an wt0 device which, of course, screws FTP installation. > >Too many things probe at 0x300. > >>(6) Reboot and disable everything that conflicts with ep0 and disable ep0. >> System comes up fine. But, I can't install anything because the >> network is of course down. > >It looks like an ep0 problem. if_ep.c has been worked on a lot lately. > >Bruce > No. wt0 probes before the ep0 probe, so ep0 is not probed because wt0 was found. The wt0 driver incorrectly probes the 0x300 address space. When is the scsi version of the slice code scheduled for prime time use? Sgk
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9504150436.AA13737>