On Wed, 2 Apr 2003, Cagle, John (ISS-Houston) wrote:
> Thanks! It was an ACPI-related problem. I disabled ACPI
> (hint.acpi.0.disabled="1" in /boot/device.hints) and rebooted and now
> both com ports show up properly as they did with FreeBSD 4.8. (These
> are just standard com ports, btw.)
We
port detection. That's
weird.
Thanks,
John
> -Original Message-
> From: Bruce Evans [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, April 02, 2003 9:17 PM
> To: Cagle, John (ISS-Houston)
> Cc: [EMAIL PROTECTED]
> Subject: Re: sio problem in -current (COM1)
>
On Wed, 2 Apr 2003, Cagle, John (ISS-Houston) wrote:
> I'm having a problem with -current on a ProLiant BL10e blade server. On
> the blade server, we use a serial console on sio0/COM1. This works
> perfectly with 4.8, but for some reason, the sio driver doesn't see COM1
> at all, and assigns COM
"Cagle, John (ISS-Houston)" wrote:
> I'm having a problem with -current on a ProLiant BL10e blade server. On
> the blade server, we use a serial console on sio0/COM1. This works
> perfectly with 4.8, but for some reason, the sio driver doesn't see COM1
> at all, and assigns COM2 resources to sio0
I'm having a problem with -current on a ProLiant BL10e blade server. On
the blade server, we use a serial console on sio0/COM1. This works
perfectly with 4.8, but for some reason, the sio driver doesn't see COM1
at all, and assigns COM2 resources to sio0. Any pointers to where I
should look woul
