Date: Tue, 13 Feb 1996 13:48:37 +0100 From: souchu@firtech.lri.fr To: msmith@atrad.adelaide.edu.au Cc: bde@zeta.org.au, hackers@FreeBSD.org Subject: Re: EIDE 2300+ Promise Message-ID: <199602131248.NAA05614@batman.lri.fr> In-Reply-To: <199602110732.SAA27556@genesis.atrad.adelaide.edu.au> (message from Michael Smith on Sun, 11 Feb 1996 18:02:01 %2B1030 (CST))
next in thread | previous in thread | raw e-mail | index | archive | help
| | Bruce Evans stands accused of saying: | > | > >My controller EIDE 2300+ Promise fails at boot in int 13h or | > >just after when executing real_to_proc, I don't know exactly. | > | > >What's wrong ? | > | > I don't know. | | This one has been done to death, and a search of the list archives | should turn up the answer; the onboard BIOS on the 2300 is _broken_ and | must be disabled completely for FreeBSD to boot. If I do that, I loose the translation facilities and need to install OnTrack for my 850 Mo HD and reinstall every software (DOS, OS2) :^(( isn't it ? | I also recall reading that if you subsequently turn it back on, you can/will | hose your BSD partition. Sorry, but I don't understand this. | | > >I have an idea. Why not programming a sort of linux-lodlin that would | > >start FreeBSD from DOS after installing the Promise int 13h driver ? | > | > dosboot.exe in FreeBSD already does this. | | The Promise driver is 'installed' by having the BIOS on the card enabled, | it _is_ the source of the problem. You mean the DOSboot idea isn't the solution... the EIDE2300.SYS driver is just way to configure the board ? Anyway, any other system (Linux, OS2, DOS...) is able to boot with this controller, why not FreeBSD ? nicolas -- Nicolas SOUCHU - DEA d'Architectures Paralleles 95 - LRI - France email: souchu@firtech.lri.fr - signature courte, le reseau dit "Ouf!"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199602131248.NAA05614>