What steps will reproduce the problem? 1. On a laptop with an ALSA built-in modem, boot up in any of the kernel-2.6.30.6 versions of puppy 4.3.1. 2. 3.

What is the expected output? What do you see instead? Modem should probably be seen as ttySL0. In the "small" distro and possibly others, the modem is not shown as detected; if modem is supported by the HSF driver as well as the ALSA driver, it is detected as ttySHSF0, but may not be verified when pupdial is activated.

What version of the product are you using? On what operating system? Puppy 4.3.1 (k2.6.30.5)

Please provide any additional information below. Two causes are identified: 1. The "daemon" that should support ALSA modems has been replaced in the k2.6.30.5 versions of 4.3.1 with a version that was built without ALSA-modem support. The daemon resides in the firmware tarball for SmartLink and other modems. The firmware should not be kernel dependent -- the replacement was in error. The solution is to replace the firmware tarball with the version in the k2.6.25.16 puppy 4.3.1 distro/iso.

2. For ALSA modems supported by both the ALSA (SmartLink) and Linuxant HSF drivers, Puppy chooses the HSF driver. If the modem is not actually appropriate for the HSF driver, "HSF ERROR" messages appear in /var/log/messages, and the modem is not verified by pupdial. Although a "preference" can be set in BootManager to override the selection of HSF, there appears to be sufficient information available for Puppy to be able to select the ALSA driver if the HSF driver fails.

The firmware tarball is /lib/modules/all-firmware/slmodem.