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.uoknor.edu!news.nodak.edu!netnews1.nwnet.net!news.u.washington.edu!lliu From: lliu@u.washington.edu (L. Liu) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: FreeBSD 2.1 can't boot with serial ports enabled Date: 25 Jan 1996 23:52:13 GMT Organization: University of Washington Lines: 26 Message-ID: <4e953d$j0e@nntp5.u.washington.edu> References: <4dvhd0$6lv@nntp5.u.washington.edu> <4e3sc1$6th@uriah.heep.sax.de> NNTP-Posting-Host: homer21.u.washington.edu NNTP-Posting-User: lliu j@uriah.heep.sax.de (J Wunsch) writes: >You've got one of the newer Mach64 video cards, right? >The sio driver touches the interrupt mode registers of ``well-known >serial ports''. This kills your Mach64. (Note: the system boots in >the background anyway.) >There's a fix in FreeBSD-current, though it doesn't patch well into >2.1R due to some modifications in adjacent portions of the sio driver. >The easiest way is to remove the address 0x2e8 from the list of >possible sio locations in sio.c. >-- >cheers, J"org >joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE >Never trust an operating system you don't have sources for. ;-) You're right. I finally found the problem is my ATI Mach64 card. I'll try to recompile the kernel according to your suggestion. Why did ATI want to use a well-know port address anyway? Thank you very much for your help. Eugene