Windows says I have a "Toshiba Softmodem v90 56k". Not much else in details. Linux's "lspci" and "lspci -n" reveals:
00:1f.6 Modem: Intel Corp. 82801CA/CAM AC'97 Modem (rev 02) 00:1f.6 Class 0703: 8086:2486 (rev 02)
I found out more about AC97 from this site. It's an intel specification that separates the analog and digital portions of the audio subsystem of a PC. The softmodem has a little bit of hardware interface and inserts into an AMR slot which connects to the motherboard circuitry and software (AC97).
Ian said he was working on a midlevel driver for the AC97 codec.
According to Toshiba, the list the linux driver for the satellite pro 6000 as "development" when doing a linux hardware audit. It shows it as "Softmodem (Lucent SCORPIO)". The 6100 wasnt listed. Maybe I have a lucent too.
according to IBM, the lucent modem riser has the 8086:2486 chipset, which is under development.
linmodems.org is a site devoted to gathering drivers to make winmodems work in linux. ie, linmodems. I don't see it listed under Intel or Toshiba. I believe the intel 8086:2486 is used by many modems like lucent, conexant, pctel, so i'm not sure if it's just a matter of getting those drivers. I tried connexant's drivers for 8086:2486, but I think it only knows how to communicate with the MC97 controller and not the AC97. (see below)
According to a scanpci script, its comments state:
PCI_IDs of unsupported Lucent AMR modems include: Intel 8086:2416 8086:2426 8086:2446 8086:2486 8086:7196
according to: http://www.mbsi.ca/cnxtlindrv/hsf/, they have drivers that will recognize:
Intel MC97 Controller (ICH) PCI ID 8086:2416 PCI ID 8086:2446 PCI ID 8086:2486Those PCI IDs represent the Intel MC97 controller, to which various AC-Link modems can be connected. However, only those based on Conexant chips are supported.
My "lspci" shows:
00:1f.6 Modem: Intel Corp. 82801CA/CAM AC'97 Modem (rev 02)
"lspci -n" shows:
00:1f.6 Class 0703: 8086:2486 (rev 02)
"dmesg" shows:
ac97_codec: AC97 Modem codec, id: 0x5349:0x4c27 (Unknown)
I downloaded the source, ran "make install", then "hsfconfig"
hsfconfig detected my modem:
Selected PCI VendorID=8086 DeviceID=2486 and INF file /etc/hsf/inf/linux_intel_smartmc.inf
When I went "modprobe hsfserial", 4 modules showed up in "lsmod", but syslog reports:
Jul 29 21:18:49 weller kernel: PCI: Found IRQ 11 for device 00:1f.6 Jul 29 21:18:49 weller kernel: PCI: Sharing IRQ 11 with 00:1f.5 Jul 29 21:18:49 weller kernel: PCI: Sharing IRQ 11 with 02:0b.1 Jul 29 21:18:49 weller kernel: PCI: Setting latency timer of device 00:1f.6 to 64 Jul 29 21:18:49 weller kernel: HSF: MC97 VendorId1=0x5349 VendorId2=0x4c27 Jul 29 21:18:49 weller kernel: ERROR: did not find a supported MC97 controller ! (0x5349:0x4c27) Jul 29 21:18:49 weller kernel: hsf_request_port: ComCtrlOpen failed, r=1!It looks like it's looking for the MC97 controller, but is finding the AC97 controller instead (which is 0x5349 VendorId2=0x4c27).
Recursively grepping for the error "supported MC97" shows it's in .O files, which we don't have the source for :(
According to this device table PCI device id 8086:2486 is the same as the 2304WT V.92 MDC modem from PCTel. However, the PCTel driver does not seem to work with the modem as it reports "No device detected" during initialisation (after being compiled for the i810 HAL). Update [15 May 2]: I received the following suggestion from Etienne Roulland, but haven't had the time to actually try it out: I use the Pctel driver v 0.9 from Jan Stifter (http://www.medres.ch/~jstifter/pctel/index.html) on a 2.4.18 kernel without problem. I just change line 296 in ptserial.c into #define PCI_DEVICE_ID_I810_MR_LAPTOP 0x2486 and it works. Update [20 May 2]: so i tried it. 1120 tar -xzvf pctel-0.9.3.tar.gz 1121 cd pctel-0.9.3 1127 cd src/ptserial/ 1130 emacs ptserial-2.4.6.c 1131 emacs ptserial-2.4.7.c #define PCI_DEVICE_ID_I810_MR_LAPTOP 0x2486 //laptop (changed #) 1144 ./configure --with-hal=i810 --with-kernel-includes=/usr/src/linux-2.4.18- 3/include/ 1145 make 1146 make install 1149 modprobe ptserial syslog from modprobe: Jul 30 03:23:04 weller kernel: AC97 modem device found: devnum = 8000FE00, devid = 8086/2486 Jul 30 03:23:04 weller kernel: iobase_0=0x1800, iobase_1=0x1080,irq=255 Jul 30 03:23:04 weller kernel: PCTel driver version 0.9.3 [5.05c-4.27.215 (09-14-2001)] (MR) (2002-01-31) with MANY_PORTS SHARE_IRQ SERIAL_PCI AUDIO_ROUTING[INTEL] enabled. Jul 30 03:23:04 weller kernel: PCTel driver built on [Linux 2.4.18-3mw2 i686 unknown "2.4.18-3mw2 <132114>"] with gcc-2.96. Jul 30 03:23:04 weller kernel: ttyS15 at 0x1800 (irq = 255) is a PCTel Jul 30 03:23:04 weller kernel: PCI: Found IRQ 11 for device 00:1f.6 Jul 30 03:23:04 weller kernel: PCI: Sharing IRQ 11 with 00:1f.5 Jul 30 03:23:04 weller kernel: PCI: Sharing IRQ 11 with 02:0b.1 so far so good... [root@weller pctel-0.9.3]# /etc/ppp/ppp-on-winmodem [root@weller pctel-0.9.3]# Jul 30 03:24:31 weller pppd[7841]: pppd 2.4.1 started by root, uid 0 Jul 30 03:24:31 weller kernel: PCTel initialization. Country code is 0. Jul 30 03:24:31 weller pppd[7841]: pppd 2.4.1 started by root, uid 0 Jul 30 03:24:31 weller kernel: PCTel initialization. Country code is 0. Jul 30 03:24:32 weller last message repeated 2 times Jul 30 03:24:32 weller chat[7842]: Can't get terminal parameters: Input/output error Jul 30 03:24:32 weller pppd[7841]: Connect script failed Jul 30 03:24:32 weller last message repeated 2 times Jul 30 03:24:32 weller chat[7842]: Can't get terminal parameters: Input/output error Jul 30 03:24:32 weller pppd[7841]: Connect script failed Jul 30 03:24:33 weller pppd[7841]: Exit. Jul 30 03:24:33 weller pppd[7841]: Exit. so i guess it was wishful thinking that pctel would work. it could also be because i specificed i810. i have an i845 i think.