I am using Fedora Core 1 and am trying to connect to the internet via a dial-up connection. I have done some research on what types of modems to purchase and have in the end decided on the Best Data 56K v.92/v.44 External Data, Fax Modem [Smart One Series Model No. 56SX-92]. It connects to the computer via a serial cable (I guess it makes it a hardware modem as opposed to a winmodem or linmodem?).

I was hoping it would work on Fedora Core, since I have read multiple reviews by Linux users who successfully connected to the internet with this type of modem. However, when I powered it on and booted Linux, Kudzu does not detect any new hardware device so nothing got configured. I also tried going into Kppp and did a 'Query Modem' command using various device location options (/dev/modem, /dev/ttyS0, etc., going down the list). I either get a "Unable to open modem." or "modem is busy." message. Why would it say "modem is busy" anyway? Is it detecting something? But if it did detect the modem, then why didn't Kudzu make any move?

I'm not sure how to make this work (or if it's even supposed to work -- does Best Data 56K v.92 simply not work with Fedora Core? Am I missing something?). I'm about to return the modem to the store, but wanted to make sure there's no other alternative.

If any of you have encountered a similar problem before (or have a clue as to what may be happening), I would really appreciate any help. Thanks!

i do not know why it does not work for as it does here

http://www.linuxquestions.org/hcl/sh...p?product=1203

may you would like to consult them

also do u get this modem listing in

lspci

regards

fedora 1 is buggy you can try to use configure network devices through the menu or try wvdial or gnome-ppp see if minicom can detect it. I have the same modem it works. Gnome-ppp is just a frontend to wvdial so try wvdial

I am not sure on Fedora but my Best Data works great with KPPP with Debian, Mandrake, and Knoppix. Better than any other i have tried so far, and I don't have the best phone lines in my rural area. One of my boxes I had to turn on serial support in the bios settings, it had the same symptoms you have. The serial ports and parallel ports weren't turned on as a default.

Thanks to all those who replied. The problem was with the BIOS settings, as 'brainiac' suggested. The serial port where I had the modem connected to was set to 'Auto' instead of 'Enabled'. Changing it to 'Enabled' solved the problem.