Link to home
Start Free TrialLog in
Avatar of torstena
torstena

asked on

SUSE 9.1 and serial port problem

I have installed SuSE 9.1 on a HP Netserver, and applied patches using on-line update.

I try to connect to a modem, but get no reply from modem. Have tried several types of serial devices, and my comm-package ("Modem is not ready") as well as minicom (no response).

Server is a rack, no keyboard or monitor when booting. I have tried exchanging the hardware, same result - must be OS-related.

From boot.msg:
--------
<6>Serial: 8250/16550 driver $Revision: 1.90 $ 48 ports, IRQ sharing enabled
<4>ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
----

Boot logging started on /dev/tty1(/dev/console) at Wed Nov 24 15:25:31 2004

<notice>run boot scripts (setserial boot.proc)
Configuring serial ports...
/dev/ttyS0 at 0x03f8 (irq = 4) is a 16550A
Configured serial ports
done<notice>exit status of (setserial boot.proc) is (0 0)  
-------

Using cat /proc/interrupts I get no lines with "serial", if I start the comm-program, I get:

         10          XT-PIC  serial

There seems to be no other leg-file entries related to this.

I have had the system running using same modem and software with an old SuSE 8, so I may be missing some banal change in SuSE 9.x

Thanks....
Avatar of wesly_chen
wesly_chen
Flag of United States of America image

> I try to connect to a modem, but get no reply from modem
So it is an external modem.
What brand/model it is? Did you install driver install for it?
I think you need to install the driver first.

Wesly
Avatar of torstena
torstena

ASKER

Yes, I try to connect to an external modem.

Or any serial devide for that matter. When my modem did not respond to "AT"-command I tried to connect to other devices (incl. a PC with terminal program). I simply cannot get anything out on the serial port. I should not need to worry about drivers until I can at least get simple communication of "AT" type functioning.

T
The problem have been resolved.

The problem was caused by the default setting in the server BIOS of COM1 being a Management Port.

SuSE 8.2 did not detect this, and therefore allowed the port to be used as a standard COM port.

SuSE 9.x detects the special state of the port, and thus do not allow it to be used as a COM port. The setserial utility detects the port correctly but access is not allowed (no errormessages given). Once the port was set to standard serial port in the BIOS (press F2 wheen booting) it works.

Torstena
Hi,

   Glad to know your problem resolved.
You can ask for the points refund.

Cheers,

Wesly
ASKER CERTIFIED SOLUTION
Avatar of Lunchy
Lunchy
Flag of Canada image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial