Return to BSD News archive
Received: by minnie.vk1xwt.ampr.org with NNTP id AA843 ; Mon, 08 Feb 93 10:02:36 EST Path: sserve!manuel.anu.edu.au!munnari.oz.au!sgiblab!swrinde!gatech!emory!sol.ctr.columbia.edu!usc!cs.utexas.edu!qt.cs.utexas.edu!yale.edu!ira.uka.de!Germany.EU.net!hcshh!hm From: hm@hcshh.hcs.de (Hellmuth Michaelis) Newsgroups: comp.unix.bsd Subject: [386BSD] new bootblocks failing on EISA/Phoenix BIOS - help! Summary: Julian's new bootblocks fail to boot a EISA/Phoenix BIOS system. Keywords: 386BSD new bootblocks EISA Phoenix BIOS Julian Message-ID: <1636@hcshh.hcs.de> Date: 5 Feb 93 19:01:12 GMT Organization: HCS GmbH, Hamburg, Europe Lines: 36 Hi everyone, I am currently trying to install Julians new bootblocks onto a machine and ran into severe problems. The system is a 486 Kyocera EISA PC (EP-7000) using the Intel EISA-chipset and a Phoenix BIOS and is equipped with an Adaptec 1742 SCSI controller. Because of the 1742, i have to use the new bootblocks to boot the thing. After compiling and installing the bootblocks - same situation on IDE and SCSI (!) - the kernel prints the first 4 lines of the copyright messages (copyright1[] and copyright2[] in init_main.c) and stops. With the old bootblocks (on the IDE drive) the machine runs fine - same with SCSI, Julians SCSI driver runs very well (and FAST!). I'm just not able to boot from IDE/SCSI using the new bootblocks. I have looked after everything and anything i can think of; inserted printf's everywhere and tried all sorts of setups and hacks - the problem stays .... Has anyone gotten a similar combination to boot ? What is so special with a Phoenix BIOS ? Has the Intel (inside ..) chipset some specialities buried in it ? Has someone already modified the old bootblocks to boot from a 1742 ? Any clues? hellmuth (loosing hair ....) -- hellmuth michaelis HCS Hanseatischer Computerservice GmbH hamburg, europe hm@hcshh.hcs.de tel: +49/40/55903-170 fax: +49/40/5591486