Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!howland.reston.ans.net!europa.eng.gtefsd.com!uunet!mcsun!sun4nl!fwi.uva.nl!vdlinden From: vdlinden@fwi.uva.nl (Frank van der Linden) Newsgroups: comp.os.386bsd.bugs Subject: [NetBSD 0.9] comm-driver (solved) Date: 13 Sep 1993 23:01:16 GMT Organization: FWI, University of Amsterdam Lines: 25 Distribution: world Message-ID: <272u3s$q2b@mail.fwi.uva.nl> NNTP-Posting-Host: carol.fwi.uva.nl In a previous posting, I mentioned (next to the 'harddisk-light-on-hang-bug') that the serial driver seemed to give me some trouble. Indeed, it did. That is, it hardly worked: I could not get tip to access my modem properly, nor did X start up (because it somehow hung when initializing the mouse). However, the solution was simple: the GENERICAHA kernel comes with com2 and com3 (COM3 and COM4 in the DOS world) configured on the IRQs 5 and 9 (or was it 9 and 5). Anyway, I had my suspicions about these lines, and, while I have 4 com ports, they are all configured to IRQ 4 or 3. So I removed the lines from the config, and recompiled. It worked. I think someone also said that the HD trouble could be caused by another driver interfering. I didn't have any HD trouble after I took the extra 2 serial ports out of the config, but that's probably coincidence. A fellow netter was kind enough to send me a patch he'd previously posted, so if the trouble comes back, I'll apply that. Later, Frank -- +----------------------------------------------------------------------------+ | I am not sure what a .signature is for, but my mom told me to make one. | | Frank van der Linden, vdlinden@fwi.uva.nl | +----------------------------------------------------------------------------+