ProLiant DL360 PCI modem not recognised

[Scarey]

I've added a USRV.92 Low Profile PCI Modem USR802981-OEM to my DL360 G4P.
I've installing LINUX ES10.

For some odd reason, the PCI card cannot be recognized properly.
In other words, LINUX doesn't see it as a modem at all It sees it as a serial device but the OS can't communicate with it.

I've tries OPEN Suse also, same issue.

Anyone any ideas what I can try next?

[Matti_Kurkela]

The traditional interface between a modem and a PC _is_ a serial port. If Linux detects your modem as a serial device, it is actually a good thing: it indicates that the modem might be a "real" modem, not a stripped-down "winmodem".

According to USR documentation, USR802981-OEM should actually be supported in Linux kernel 2.6.18 and newer:

http://www.usr.com/products/modem/modem-oem.asp
http://www.usr.com/support/product-template.asp?prod=oem#2980

There is also a USR-provided driver for Linux, but apparently you would have to re-compile your kernel to use it.

Please identify the PCI slot ID of your modem from the "lspci" listing. It should be something like XX:YY.Z.
Then please run "lspci -vvv -s XX:YY.Z" and post the output here.

Also please post the output of "setserial -g /dev/ttyS*".

Why have you come to the conclusion that the OS cannot communicate with the modem? What exactly have you tried?

MK

[Scarey]

Hi
lspci returns:

07:01.0 Serial controller: U.S. Robotics Device 0152 (rev 02)



Output of lspci -vvv -s 07:01.0

07:01.0 Serial controller: U.S. Robotics Device 0152 (rev 02) (prog-if 02 [16550])
Subsystem: Exar Corp. Device 0129
Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ Fa stB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR - Interrupt: pin A routed to IRQ 48
Region 0: Memory at fdff0000 (32-bit, non-prefetchable) [size=1K]



Output of setserial -g /dev/ttyS*

/dev/ttyS0, UART: 16550A, Port: 0x03f8, IRQ: 4
/dev/ttyS1, UART: 16550A, Port: 0x02f8, IRQ: 3



Maybe I was incorrect in saying the OS couldn't communicate with the modem, but when I look at the PCI info returned by LINUX it doesn't return much info compared to other servers that have similar PCI Modems.

[Jimmy Vance]

Most modems will show up as serial devices.

If the modem is being set to COM2 (/dev/ttyS1)it may be in contention with the VSP function of iLO as the VSP is on COM2 by default.

I'd put the modem on COM1, and disable COM1 in RBSU.

F9 to get into RBSU, then select System Options. The first to selections are Embedded Serial Port and Virtual Serial Port (VSP)

If you don't think you would ever use the VSP feature of iLO, you can disable it and leave the modem on COM2

[Scarey]

OK, thanks for the suggestion.

Did all that, but still no joy.

Linux still sees it as just a serial device, and doesn't classify it as anything other than a Serial Device.
Should it not be classified as modem/communication device.

On other servers (not of this type) similar hardware modems are classified correctly.

[Jimmy Vance]

with most distributions /dev/modem is just a symbolic link that points to /dev/ttySx where x is the serial device.

If you have minicom loaded see if it will talk to the modem on /dev/ttyS0 or /dev/ttyS1

[Scarey]

Hi,
yup, did all that but to no avail.
I think I'll ditch the PCI modem and run with an external serial port modem for now.
Bit of a nuisance though.

I can put the modem card into a normal PC and an OS like XP sees it fine.

I'll try a PC with LINUX and see how that goes.
If it works there then I'm pointing the finger of suspicion at the DL360.