Return to BSD News archive
Newsgroups: comp.os.386bsd.bugs Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!howland.reston.ans.net!pipex!uknet!mcsun!chsun!hslrswi!aut!nbladt From: nbladt@autelca.ascom.ch (Norbert Bladt) Subject: [FreeBSD-1.0 RELEASE] won't install on my system - 386BSD-0.1 runs fine Message-ID: <CG89vB.Avu@autelca.ascom.ch> Organization: Ascom Autelca AG, Guemligen, Switzerland Date: Tue, 9 Nov 1993 14:06:47 GMT Lines: 85 Hello FreeBSD-1.0 'hackers' ! Last weekend I tried to install FreeBSD-1.0 on my system at home. First, I tried to boot with the kcopy-ah-floppy. It booted fine, but a prompt was displayed kc> As it was not what was described in the install notes, I remembered that I tried to install Linux on the same drive and some Linux filesystems could be left on the disk. So, I did boot MS-DOS from floppy, deleted all the partitions and create a primary DOS partition (25 MB). The next time I booted with the kcopy-ah-floppy, it did ask for the filesystem floppy. I did put the filesystem-floppy in. It started to load /386bsd. It started to detect the 'sio', even the type was right (I have one 16450 and on 16550). It detected my harddisk controller (Adaptec 1742 in standard mode) and the devices connected to it (Fujitsu harddisk and Archive streamer). Now I got three different results: 1. A reboot. This clears the display very fast and I can't exactly tell what the last message on the screen was - I remember seeing st0: drive empty as one of the last messages. 2. A panic (with slightly different codes every time) a) trap type 12 code=fdbf0000 eip=fe05a57c cs=fdbf0008 eflags=10246 cr2 0 cpl ffffffff panic: trap hit reset please b) trap type 12 code=fe180000 eip=fe05a57c cs=fe080008 eflags=10246 cr2 0 cpl ffffffff panic: trap hit reset please c) trap type 12 code=fdbf0000 eip=fe05a57c cs=fdbf0008 eflags=13246 cr2 0 cpl ffffffff panic: trap hit reset please 3. I remembered something about the 'turbo' button. So, I slowed my system down by using the 'turbo' button. Now, the result is different: ... Insert filesystem floppy ... ... ahb0: ... changing root device to ... warning : no swap space present (yet) signal system call failed signal system call failed (it seems to me this occurs in an endless loop). My system configuration: EISA mainboard with Intel chipset, 16 MB RAM (detected by the boot prog) Adaptec 1742A SCSI controller in standard mode (detected by FreeBSD) Conner 100 MB SCSI harddisk (detected by FreeBSD) Archive 5252S streamer (detected by FreeBSD) ATI Ultra Graphics Pro EISA (2 MB VRAM) (VGA: detected by FreeBSD) 2 serial ports (one 16450, 16550 - detected fine by FreeBSD) 1 parallel port (don't know whether it was detected or not) Advanced Gravis Ultrasound Board I thought this was one of the usual setups for a system the *BSD like. I will try to install NetBSD the next weekend and see what happens. I can exchange the ATI board with an S3 board, if that will make a difference. I would like to switch from 386BSD-0.1 which runs fine on this system because I would like to use the XFree86-2.0 Xserver for my ATI board. Now I am using the 8514/A server for 386BSD and it runs fine, but I would like it to be a little faster. And I would like to use my high speed modem for FAX and data transfer in combination with the 16550A UART I have. Thanks for your help (and for FreeBSD !), Norbert. P.S. I will send a copy of this article to the FreeBSD-bugs list. I don't know, however, whether this is a FreeBSD bug or not :-) It's definitely a boot-problem, though :-( -- Norbert Bladt, Ascom Autelca AG, Worbstr. 201, CH-3073 Guemligen, Switzerland Phone: +41 31 999 65 52 FAX: +41 31 999 65 44 Mail: nbladt@autelca.ascom.ch UUCP: ..!uunet!mcsun!chsun!hslrswi!aut!nbladt