1) I have an HSF modem. Can I use these drivers?

	No, these drivers are only for the Conexant HCF (controllerless) family,
	not for the HSF (softmodem) chips.
	HSF drivers are available from http://www.mbsi.ca/cnxtlindrv/hsf

2) The modem returns "NO DIALTONE" when I try to dial

	Please check your line cord and country settings
	(with hcf{pci|usb}config --country).
	If they are correct and the "NO DIALTONE" problems persist, you
	may try disabling dialtone detection with the "ATX3" command.

	If this still doesn't work, you should report the problem to us.

3) The modem returns CONNECT messages with bogus connection speeds, like
   "CONNECT 9600" or "CONNECT 115200"

	Use "ATW1" to enable reporting of line speed, error correction protocol
	and DTE speed. See the command set reference manual
	(100498D_RM_HxF_Released.pdf) for details.

4) The modem works, but I can't hear anything when dialing

	Please check the Ln and Mn settings in AT&V. They should be L1 and M1.
	If not, change them with the command: ATL1M1&W

	If you still cannot hear any call progress sounds, and use a
	modem model that does not have its own speaker (such as on a notebook),
	verify your audio mixer settings (using aumix or equivalent utility) to
	ensure that the volume levels are high enough and that the "PhoneIn"
	channel is not muted. 

5) My modem's PCI ID is 127a:1025 or 127a:2005 and it doesn't work

	You probably should try the HSF driver. Some early HSF modems are
	incorrectly identified as HCF in some versions of the PCI ID lists
	used by lspci and the linux kernel. Also, a few modem vendors have
	tried to save costs by omitting the EEPROM where device IDs are stored,
	causing the same default ID built into the bus interface chip to be
	used for both HCF and HSF devices.

6) Changing serial port parameters with "setserial" on ttySHxF0 or /dev/modem
   doesn't work.

	Since this modem driver provides a virtual serial interface, which
	is not directly connected to a physical UART like a normal serial
	port, it is not possible and would not make sense to configure
	it with "setserial". Therefore you shouldn't use this command
	on the ports associated with this driver.
	
7) I installed the driver, and now the /dev/ttySHxF0 or /dev/modem device is
   supposed to be there but it doesn't exist.

	On devfs-based systems (such as Mandrake), the missing device node
	is often a sign that the driver modules didn't load or initialize
	properly. Try "modprobe hcfpciserial" (or hcfusbserial), then check
	the /var/log/messages file or or run "dmesg" to see any kernel error
	messages that could provide a clue as to why loading of the driver
	failed.

8) I have a USB HCF modem. Why don't you provide an x86 version of the
   hcfusbmodem package?

	Unfortunately the hcfusbmodem driver only supports the Cadmus2
	chipset internally used by Apple in later generation PowerPC desktop
	and notebook machines. Most if not all external USB HCF modems
	on the market use an earlier chipset (Cadmus1), which requires too many
	workarounds and excessive polling by the CPU to be well supported
	under Linux.