Date: Mon, 5 Oct 1998 21:01:58 -0700 From: "iyengar" <SanatanaDharma@email.msn.com> To: "Greg Lehey" <grog@lemis.com>, <freebsd-questions@FreeBSD.ORG> Cc: <siyengar@mc.hl.siemens.de>, "Srinivasan Iyengar" <SanatanaDharma@email.msn.com> Subject: Re: sio1 problem, ppp problem and 3com 3c905B-TX problem Message-ID: <001401bdf0de$11bc4900$f90e2599@fvn6s>
next in thread | raw e-mail | index | archive | help
Hi Greg, Thanks for the replies. I initially left the default 0x2f8 address for the sio1 ( com2) port and found that FreeBSD did not find this on booting. I then went back to check for the location and found that MS windows 98 reported it at 0x100. It does find COM1 at 3xf8 and I am now using a 28.8 modem hooked up to that port externally while I have a 56k flex on the inside of the machine sitting idle since it is not found by the OS. As far as I can tell, there are no other helpful hints on dmesg regarding this issue. Com1 is found and com2 is not. BTW, I did an "upgrade" from 2.2.6 to 2.2.7 instead of fully loading the OS. There were several reasons for this. I had a dedicated Hard Drive for FreeBSD that I "moved" from an older PC to this one and I did not want to remove the directory structure and some changes I had made to some Packages on 2.2.6. Could this be one reason that the OS is not functioning optimally? As far as conflicts go - I have only two and these are related to the PS2 mouse and the sysconsole for which the message says "conflict allowed". I have removed the unwanted drivers in Userconfig. I do not have any conflicting irqs in the NETWORKING or the other sections of Userconfig. Thanks for taking the time to reply. Srini. -----Original Message-----freebsd-questions@FreeBSD.ORG From: Greg Lehey <grog@lemis.com> To: iyengar <SanatanaDharma@email.msn.com>; <freebsd-questions@FreeBSD.ORG> Date: Sunday, October 04, 1998 10:01 PM Subject: Re: sio1 problem, ppp problem and 3com 3c905B-TX problem >On Sunday, 4 October 1998 at 21:14:22 -0700, iyengar wrote: >> Hi Friends, >> >> I was wondering if anyone could give me a few pointers with 3 specific >> problems I am running into. >> >> I have a new Dell Dimension XPS R400. It has an internal modem which windows >> shows as hooked up to COM2. I checked the IRQ=3 and the port address=0x100. >> The IO range is 0x100 - 0x107. >> I changed the sio1 port address using userconfig from the default to 0x100. >> >> FreeBSD (2.2.7) comes up with the following messages : >> >> Sio1: Configured irq 3 not in bitmap of probed irqs 0 >> Sio1: irq maps 0x1 0x1 0x1 0x1 >> Sio1: Probe failed test(s): 1 4 6 7 9 >> Sio1: not found at 0x100 > >Oops, my last reply was incorrect. I saw COM2, and thought you were >talking about sio2. > >Is there anything else in the dmesg output which would help? >Theoretically you might be suffering from the sio problems described >at http://www.lemis.com/serial-port-patch.html, but I haven't heard of >that on Dells (though of course the fact that it's a modem might >change things). The I/O addresses are definitely funny; normally a >serial port is at 0x3f8 (primary) and 0x2f8 (secondary). Could it be >that Microsoft is lying? > >If it's the serial port bug described on the web page, it's fixed both >in 2.2-STABLE and 3.0 (which looks like it's what you want anyway). > >Greg >-- >See complete headers for address, home page and phone numbers >finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?001401bdf0de$11bc4900$f90e2599>