Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.bhp.com.au!mel.dit.csiro.au!munnari.OZ.AU!news.ecn.uoknor.edu!news.ysu.edu!odin.oar.net!malgudi.oar.net!news2.ee.net!news.ee.net!imci2!newsfeed.internetmci.com!uwm.edu!math.ohio-state.edu!jussieu.fr!u-psud.fr!news.u-psud.fr!souchu From: souchu@garfield.news.u-psud.fr (Nicolas Souchu) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Boot failure, int 13h hangs !! Date: 30 Jan 1996 12:55:29 GMT Organization: Universite Paris-Sud, France. Lines: 35 Distribution: world Message-ID: <SOUCHU.96Jan30135529@garfield.news.u-psud.fr> NNTP-Posting-Host: garfield.lri.fr Hi, After reading boot1 and boot2 sources, I know why FreeBSD 2.1 fails to boot. boot1 is in real mode --> no disk error during int 13h. boot2 is in protected mode and goes back to real mode to call int 13h. In this case, my computer hangs when calling int 13h to read the partition table (cyl 0, head 0, sector "1-bios-numbering") or any other bios-int13h-function. This happens either with the 989,15,56 WDC-HD or with the 1654,16,63 WDC-HD. Anyway, when FreeBSD is booted (with the Fixit disk), no problem. I imagine this is because HD io are done in protected mode through the controller's ports. My EIDE controller adds an external bios to the system to support disk larger than 528 Mo. This external bios is located in high memory (default address D0000h). The board allows me to modify this address, but I really don't know which to choose to solve my problem (supposing this is the solution) Does anybody understand this and could help me ? Last, I may modify boot2 to read sectors with the controller's ports ? :^(( Thanks a lot in advance. nicolas -- -- Nicolas SOUCHU - DEA d'Architectures Paralleles 95 - LRI - France email: souchu@firtech.lri.fr - signature courte, le reseau dit "Ouf!"