Very Computer

What is the rationale behind setting pccom2 to be at irq 5 in the standard
kernel?

Correct me if I'm wrong, but isn't the standard x86 way of doing things to
have the third serial port be at IRQ 4?

It just might be configured for irq 5, _if_ it is there. OTOH, you can
always change its irq at boot time, if you need it for your installation.

Quote:> Correct me if I'm wrong, but isn't the standard x86 way of doing things to
> have the third serial port be at IRQ 4?

No.

The next part is confusing.
You are not expected to understand this.[0]

The `standard' (original ibm, whatever) way is:

com 1 irq 4
com 2 irq 3
com 3 irq 4
com 4 irq 3

But since doubly used irqs (not counting multiple serial boards using
one irq per board, not port) cause problems, the `standard' way to
work around that is assign com 3 and 4 irqs 5 and 2/9. irq 5 is 2nd lpt,
too, and 2(remap to 9) is cascade and 2(remap back from 9) is also vga,
if in use. Because those can get used in Other Ways, too, (think sound
card) they tend to get replaced by yet something else.

Bottom line: In effect, after com 2 irqs are all non standard enough to
never know for sure just what they will be on any random system.

[0] Couldn't resist.

--
  j p d (at) d s b (dot) t u d e l f t (dot) n l .

JPD, you seem to know a lot about pccom/com, so perhaps you would like to
help me.  I am running openBSD 3.0 and XFree86 4.1.0.  Can't get my mouse
configured appropriately.  It's a serial, Logitech, MouseMan, 3 button,
mouse and it is connected to my Matrox Millenium II video card.  Now, under
Windows, my mouse is recognized as connected on COM1, IRQ 4.  Originally,
when I installed openBSD, the system would not find the mouse at all.  It
would load the pccom0 driver on Port 0x3f8, Irq 4 and the mouse drivers
(lms, mms) would probe Port 0x23e, Irq 5 (or something like that, excuse my
ignorance).  Now, I recompiled the kernel, commenting out the pccom0 device,
and modifying the lms driver to look at Port 0x3f8, Irq 4.  It appeared to
work.  The lms driver loaded and wsmouse attached to lms.  Now, the problem
is that no matter how I configure X, my mouse would not move (the pointer
sits right in the center of the screen and it's well... quite dead)

I have the nagging feeling that my mouse, as a serial device, needs to be
configured at tty0? or cua0?, but I don't know enought about it.  I read the
man pages and consulted the Unix System Administration Handbook, but
couldn't get the mouse to work.  Any ideas?

Ivaylo

It's not possible for your mouse to be connected to the Matrox.  but
otherwise:

Quote:> Now, under
> Windows, my mouse is recognized as connected on COM1, IRQ 4.  Originally,
> when I installed openBSD, the system would not find the mouse at all.  It
> would load the pccom0 driver on Port 0x3f8, Irq 4 and the mouse drivers
> (lms, mms) would probe Port 0x23e, Irq 5 (or something like that, excuse my
> ignorance).  Now, I recompiled the kernel, commenting out the pccom0 device,
> and modifying the lms driver to look at Port 0x3f8, Irq 4.  It appeared to
> work.

That's probably not a good idea.  I think the lms driver is meant for a
special addon card, not a serial mouse.  If it's a serial mouse, or in
fact a computer new enough to have Millenium2, it's not a true bus mouse.

Quote:> The lms driver loaded and wsmouse attached to lms.  Now, the problem
> is that no matter how I configure X, my mouse would not move (the pointer
> sits right in the center of the screen and it's well... quite dead)

You didn't tell use how you tried configuring X.

Quote:> I have the nagging feeling that my mouse, as a serial device, needs to be
> configured at tty0? or cua0?, but I don't know enought about it.

You almost certainly want pccom in your kernel.  What you did kinda/sorta
worked, but it's probably not "right".  I use /dev/tty0 for a serial
mouse, though /dev/cua0 might work too.

--
Ted, toll collector of the information superhighway

Yes, Ted, it is not.  Dugh.  It is connected to another card, which I
suspect is my IDE controller.

Quote:> > Now, under
> > Windows, my mouse is recognized as connected on COM1, IRQ 4.
Originally,
> > when I installed openBSD, the system would not find the mouse at all.
It
> > would load the pccom0 driver on Port 0x3f8, Irq 4 and the mouse drivers
> > (lms, mms) would probe Port 0x23e, Irq 5 (or something like that, excuse
my
> > ignorance).  Now, I recompiled the kernel, commenting out the pccom0
device,
> > and modifying the lms driver to look at Port 0x3f8, Irq 4.  It appeared
to
> > work.

> That's probably not a good idea.  I think the lms driver is meant for a
> special addon card, not a serial mouse.  If it's a serial mouse, or in
> fact a computer new enough to have Millenium2, it's not a true bus mouse.

Exactly.  I now it is not a good idea, but I don't know any better.  I
bought myself the UNIX System Administration Handbook, and I am filling the
gaps.  But it does not tell me how to configure my mouse device in the
kernel to map to COM1, IRQ 4.  I don't even know if there is a driver for my
serial mouse at all.  I mean, the man pages for mms and lms say bus mouse,
and I assumed it meant serial bus mouse.  Am I wrong?

Quote:> > The lms driver loaded and wsmouse attached to lms.  Now, the problem
> > is that no matter how I configure X, my mouse would not move (the
pointer
> > sits right in the center of the screen and it's well... quite dead)

> You didn't tell use how you tried configuring X.

I tried to configure XFree86Config to use the following protocols and
devices:
"Intellimouse", /dev/wsmouse0
"MouseMan", /dev/wsmouse0
"Auto", /dev/wsmouse0
"wsmouse", /dev/wsmouse0

Using xmseconfig I also tried /dev/tty00 and /dev/cua00, but the mouse would
not start moving, so I assumed it is wrong.  A rushed decision, I suppose.
I should have applied the setting and rebooted.  But it was very late
night... so... [sigh]

Quote:

> > I have the nagging feeling that my mouse, as a serial device, needs to
be
> > configured at tty0? or cua0?, but I don't know enought about it.

> You almost certainly want pccom in your kernel.  What you did kinda/sorta
> worked, but it's probably not "right".  I use /dev/tty0 for a serial
> mouse, though /dev/cua0 might work too.

That's it, but are you saying I should use my original kernel configuration
and try to tell X to look at
/dev/tty0 using one of these protocols- Logitech, Microsoft, Intellimouse,
Auto ?

Thanks for all your help, it's good to have someone confirm your insanity.

Ivaylo

Quote:

> --
> Ted, toll collector of the information superhighway

You're confused as to what driver you want, and where it is.  There are
no mouse drivers in the kernel.  The lms driver is more of an interface
that another driver can use to talk to the mouse.  Leave the kernel alone.
A bus mouse is rather old.  It was a mouse that attached to a special
card, that only worked with that mouse.  If Windows used it attached to
com1, you have a serial mouse, not a bus mouse.

Quote:> I tried to configure XFree86Config to use the following protocols and

/etc/XF86Config right?

Quote:> devices:
> "Intellimouse", /dev/wsmouse0
> "MouseMan", /dev/wsmouse0
> "Auto", /dev/wsmouse0
> "wsmouse", /dev/wsmouse0

Of these, only the last would work.  Do you have console mouse working?

Quote:> Using xmseconfig I also tried /dev/tty00 and /dev/cua00, but the mouse would
> not start moving, so I assumed it is wrong.  A rushed decision, I suppose.
> I should have applied the setting and rebooted.  But it was very late
> night... so... [sigh]

Boot the generic kernel, but do not start wsmoused, or kill if it has
already started.  Then try /dev/tty0 and protocol microsoft.  Next
protocol logitech.

--
Ted, toll collector of the information superhighway

Thanks, Ted!  I configured /etc/XF86Config to look for the mouse at
/dev/tty00 and it worked.
I guess it was wrong of me, earlier on, to assume that by applying the
settings in xmseconfig, I would get the mouse working without restarting X.
Oh, well, lesson learned- be patient and read the documentation.  Thanks,
again.

Ivaylo

On Sat, 23 Feb 2002 12:50:48 -0400,

I happen to know a bit about peecee cruftyness. No guarantees I know about
your specific hardware cruftiness, too. :-)

Quote:>  I am running openBSD 3.0 and XFree86 4.1.0.  Can't get my mouse
> configured appropriately.  It's a serial, Logitech, MouseMan, 3 button,
> mouse and it is connected to my Matrox Millenium II video card.

This simply does not compute here.

Quote:>  Now, under
> Windows, my mouse is recognized as connected on COM1, IRQ 4.

Could be some emulation driver. Please check.

Quote:>  Originally,
> when I installed openBSD, the system would not find the mouse at all.

OpenBSD doesn't find serial mice. It only finds serial ports.

Quote:>  It
> would load the pccom0 driver on Port 0x3f8, Irq 4 and the mouse drivers
> (lms, mms) would probe Port 0x23e, Irq 5 (or something like that, excuse my
> ignorance).

Sounds pretty important detail. Maybe go back and check?
What does dmesg say?

ObOtherpost already pointed out lms and mms only are interfaces that
check if the interface hardware is there. Doesn't mean they actually
check for mice, too.

Quote:>  Now, I recompiled the kernel, commenting out the pccom0 device,
> and modifying the lms driver to look at Port 0x3f8, Irq 4.  It appeared to
> work.  The lms driver loaded and wsmouse attached to lms.  Now, the problem
> is that no matter how I configure X, my mouse would not move (the pointer
> sits right in the center of the screen and it's well... quite dead)

Then it doesn't work, no?

Quote:> I have the nagging feeling that my mouse, as a serial device, needs to be
> configured at tty0? or cua0?, but I don't know enought about it.  I read the
> man pages and consulted the Unix System Administration Handbook, but
> couldn't get the mouse to work.  Any ideas?

Check what plug is at the end of your mouse and where it plugs into, exactly?

[snip old message. you could've done that, too, you know]

--
  j p d (at) d s b (dot) t u d e l f t (dot) n l .