Description of problem:
Sealevel 8 port serial card is not currently supported in the version of the
kernel distributed by Red Hat. According to the manufacturer, it is supported
in kernel 2.6.12
Version-Release number of selected component (if applicable):
Install serial card with dongle/break-out cable, install OS
Steps to Reproduce:
1. Insert Hardware
2. Install RHEL 4 AS u3 x86_64
Only 1 serial port is useable
All 8 ports should be useable
Customer (ITT Systems at Patrick Air Force Base) recompiled stock kernel with
patch, included below, and the card worked. This was on a Dell PE 6850 w/ 4
Here is some card related output:
[root@dev-laps-svr2 ~]# dmesg|egrep -i "serial|sealevel"
Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing enabled
[root@dev-laps-svr2 ~]# lspci|grep -i sealevel
pcilib: Resource 5 in /sys/bus/pci/devices/0000:00:1f.1/resource has a 64-bit
0f:02.0 Serial controller: Sealevel Systems Inc: Unknown device 7804 (rev 01)
Here is the official link:
Ultra COMM 8.PCI
PCI RS-232, RS-422, RS-485 Serial Interface**
Created attachment 130005 [details]
Patch supplied by Sealevel, the manufacturer of the card
I agree with this patch (matches upstream).
Do we have the hardware to test here at Westford? If not, can someone
tell us how to gain access to test?
any news on the acquisition of this hardware?
The customer had actually added this patch to the kernel while I was there in
May. The card was recognized and all 8 ports were working.
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
committed in stream U5 build 42.30. A test kernel with this patch is available
QE ack for RHEL4.5.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.