Date: Tue, 16 Jul 2002 16:18:48 -0400 From: "Joe & Fhe Barbish" <barbish@a1poweruser.com> To: "Joshua Lee" <yid@softhome.net> Cc: "FBSDQ" <questions@FreeBSD.ORG> Subject: RE: FreeBSD 4.6 Modems Message-ID: <MIEPLLIBMLEEABPDBIEGKEJMCFAA.barbish@a1poweruser.com> In-Reply-To: <20020716151345.418e85f4.yid@softhome.net>
next in thread | previous in thread | raw e-mail | index | archive | help
I did not see any responses to your original post in this questions list where you were given an one line fix to the source for your problem. Please post that info for the list readers who will be searching the questions archives for the same solution. I have seen the irq sharing question posted many times by many different people. Your solution needs to be part of archive to help these people who follow you, and I would like to know also. -----Original Message----- From: owner-freebsd-questions@FreeBSD.ORG [mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of Joshua Lee Sent: Tuesday, July 16, 2002 3:14 PM To: Matthew Seaman Cc: iosphere@sonic.net; freebsd-questions@FreeBSD.ORG Subject: Re: FreeBSD 4.6 Modems On Mon, 15 Jul 2002 07:27:01 +0100 Matthew Seaman <m.seaman@infracaninophile.co.uk> wrote: > > with no fuss. It also lives on IRQ 9 here; that can cause conflicts, > > at least here where I'm trying to resolve a conflict between it and > > the second built-in USB hub on my computer. Other than that it's a > > That's a plug'n'play modem isn't it? If you make yourself a custom > kernel config where you comment out the sio2 and sio3 device lines > (which are disabled by default), then your internal modem will be > assigned to sio2 (/dev/cuaa2) on the IO_COM3 port and irq 5. Thanks. Someone else wrote me with a solution for the root cause of it though; apparantly the kernel assumes that a serial port (or serial-port emulating device like a PCI modem) cannot share IRQs. A one-line modification of the source fixes this, and now my USB bus and the device on it is detected according to the boot messages. I'm still having problems getting my printer to work though; instead of saying that the device doesn't exist it says /dev/ulpt0 and /dev/unlpt0 are "busy" in aspfilter's setup and also if I redirect text directly to the device on the command line. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message 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?MIEPLLIBMLEEABPDBIEGKEJMCFAA.barbish>