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

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

> 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.

torstenaAuthor Commented:
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.

torstenaAuthor Commented:
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.


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


Closed, 250 points refunded.
Friendly Neighbourhood Community Support Admin

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.