After all, it seems that Fedora can not see the serial ports.I tried everything I found around from books and other info for modem configuration. Connection script is trying to dial but finally...no modem is present!This is more peculiar than not recognizing modem.I think that drivers for serial ports recognition, is a must even for Fedora that can't have third-party or proprietary packages.Any idea about the files for serial port recognition?

I have tried to help many with serial modems and Fedora Core 6, none of them ever came back and said how they got it to work, possibly because they didn't get it to work. But the one thing I always mention is to visit linmodems.org and read the archives and also use scanModem tool.

Thanks for reply.I think that you are right, but the strange about all this is that the same configuration worked perfectly and in no time at all, for Linux Red Hat 9 one day before!

Most all Linux distributions used to play mp3 songs from a fresh installation, now in Fedora 6, you cannot because of licencing issues (so they say). Modem drivers are usually proprietary, not sure about serial modems but if Fedora won't include non-free items on the installation disc, maybe the same goes for proprietary software. But the best people to talk too would be the maintainers at linmodems, after running the scanModem tool, there is usually a .txt file produced that can be sent in to them to ask for assistance. Not sure if it will actually see a serial modem though.

If it's a serial modem is it a "linmodem". I thought linmodems were all inboard????

First serial modems don't need a software driver. I install not to long ago a serial RS-232 with Fedora Core 6, it works as expected.

What can go wrong, all modems use a init string, some modems are so off from the standard init string instructions that they simple not work. Or work far below what can be expected.

Without knowing the brand name of the modem in question, I will say that probably the best advice I can give at this moment is search internet (Google) for "init string modem brandname"

Then look at your dialer where you can insert the modified init string.

For future questions, it would be much more helpful if you include all relative information. Information like modem brand name, dialer program used will help others to help you better.

You are absolutely right about that: serial modems don't need drivers under Linux.I know about initialization string too.But the case here, is much more complicated:The certain modem(it is a serial Krypto IC 56 K),works fine on the same PC under a Red Hat 9 system.So, I gave in modem commands section, the same(exactly) commands and instead of connecting to Internet, in Fedora Core 6 ,when I press "connect", the script window opens, but execution of commands stucks in the first command(ATZ) and can not proceed.So, this is peculiar:the same modem in the first case executes all commands and in the second almost nothing happens.So I figure out that problem resides somewhere else.It can't be modem itself.I create over and over modem connection in the network administration section,but when I press "Activate" button, I take error messages back that complain that network device can't be activated.In the KPPP section everything seems fine, but as I mentioned above script execution stucks in the first command.So what problem can be?

Does lsmod show the module serial_cs being loaded?

It is for me a long time that I used Redhat 9, but if it was me having this problems I will look at the serial RS-232 driver.

It is surely possible that for more then one reason that Redhat/Fedora over the years changed the standard of addressing the RS-232 port. I see the same in other operating systems, why keep the serial port and a high baud rate if nobody uses it anyway.