Acer Travelmate 2303 laptop, SUSE 9.0 Pro and winmodem story
I have an ACER travelmate 2303LM laptop an I tried to make it recognise the winmodem. I have installed Win XP Home and SUSE 9.0 Pro. My problem is the rocognition of the winmodem from Linux.
Available information through the ListMdm_v1.6 software (ran at Win) ===================================================================== = SYSTEM INFORMATION = ===================================================================== Date : 1/7/2005 ListMdm Ver : 1.6 Windows OS : Microsoft Windows XP Build Number : 2600 ===================================================================== = RESULT OF MODEM QUERY = ===================================================================== NUMBER OF MODEMS FOUND = 1 MODEM #1: PCI CONFIGURATION INFORMATION READ: VENDOR ID : 8086 DEVICE ID : 24C6 SUBVENDOR ID : 1025 SUBDEVICE ID : 0064 REVISION ID : 03 DEDUCED INFORMATION: VENDOR NAME : ICH DEVICE NAME : UNKNOWN SUBVENDOR NAME : ACER -- HTTP : / / W W W . ACERNETXUS.COM.TW MODEM TYPE : HSF WINXP INBUILD SUPPORT : NO Diagnostic Information from command lspci: 00:00.0 Host bridge: Intel Corp. 82852/855GM Host Bridge (rev 02) 00:00.1 System peripheral: Intel Corp.: Unknown device 3584 (rev 02) 00:00.3 System peripheral: Intel Corp.: Unknown device 3585 (rev 02) 00:02.0 VGA compatible controller: Intel Corp. 82852/855GM Integrated Graphics Device (rev 02) 00:02.1 Display controller: Intel Corp. 82852/855GM Integrated Graphics Device (rev 02) 00:1d.0 USB Controller: Intel Corp. 82801DB USB (Hub #1) (rev 03) 00:1d.1 USB Controller: Intel Corp. 82801DB USB (Hub #2) (rev 03) 00:1d.2 USB Controller: Intel Corp. 82801DB USB (Hub #3) (rev 03) 00:1d.7 USB Controller: Intel Corp. 82801DB USB2 (rev 03) 00:1e.0 PCI bridge: Intel Corp. 82801BAM/CAM PCI Bridge (rev 83) 00:1f.0 ISA bridge: Intel Corp. 82801DBM LPC Interface Controller (rev 03) 00:1f.1 IDE interface: Intel Corp. 82801DBM Ultra ATA Storage Controller (rev 03) 00:1f.3 SMBus: Intel Corp. 82801DB/DBM SMBus Controller (rev 03) 00:1f.5 Multimedia audio controller: Intel Corp. 82801DB AC'97 Audio Controller (rev 03) 00:1f.6 Modem: Intel Corp. 82801DB AC'97 Modem Controller (rev 03) 02:02.0 Ethernet controller: Broadcom Corporation BCM4401 100Base-T (rev 01) 02:06.0 CardBus bridge: Texas Instruments: Unknown device 8031 Diagnostic Information from "scanmodem" software: Providing detail for device at PCI_bus 00:1f.6 with vendor-ID:device-ID ----:---- Class 0703: 8086:24c6 Modem: Intel Corp. 82801DB AC'97 Modem Controller (rev 03) (prog-if 00 [Generic]) SubSystem 1025:0064 Acer Incorporated [ALI]: Unknown device 0064 Flags: bus master, medium devsel, latency 0, IRQ 10 I/O ports at 2400 [size=256] I/O ports at 2000 [size=128] -----PCI_IDs------- --CompilerVer- Feature List: Primary Subsystem Distr KernelVer kernel default CPU ./scanModem test 8086:24c6 1025:0064 SuSE 2.4.21-99-default 3.3.1 3.3.1 i686 The soft modem Subsystem operates under a controller 8086:24c6 82801DB ICH4 capable of supporting under Linux AT LEAST modem Subsystem chips from manufacturers: Broadcom AgereSystems Conexant Intel Smartlink The modem has a Conexant codec: CXT and there is support for the modem controller: 8086:24c6 82801DB ICH4 Some Linux Distributions include the hsfmodem driver. Search your packages information for "hsfmodem" and "Conexant". If not found there, download a hsfmodem package from http : / / w w w . linuxant.com . If there is not an exact match with your Linux distribution and your kernel version: 2.4.21-99-default then kernel-sources must be prepared as described in Modem/DriverCompiling.txt before the hsfmodem driver compiling can be successfull. Get and install hsfmodem drivers from http : / / w w w . linuxant.com Please browse the folder Modem/ containing the following files: 1stRead.txt General.txt Rational.txt SoftModem.txt UNSUBSCRIBE.txt DriverCompiling.txt ModemData.txt Slmodem.txt Testing.txt Diagnostic Information from YAST (Hardware Info): PCI 1f.6: 0703 Modem (Generic) [Created at pci.65] Unique ID: ORVU.wuCrdJaLnzF Hardware Class: modem Model: "Acer Incorporated [ALI] 82801DB AC'97 Modem Controller" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x24c6 "82801DB AC'97 Modem Controller" SubVendor: pci 0x1025 "Acer Incorporated [ALI]" SubDevice: pci 0x0064 Revision: 0x03 I/O Ports: 0x2400-0x24ff (rw) I/O Ports: 0x2000-0x207f (rw) IRQ: 10 (159 events) Config Status: cfg=yes, avail=yes, need=no, active=unknown Instructions I got from alt.linux: Your modem is probably set at ttyS14. To get it to run, you have two options. Either type in ttyS14 when you set the modem up in Yast on the line that reads "/dev/modem". You will be tempted to try to use the pull down menu. Don't just erase the /dev/modem and type ttyS14 in its place. - It didn't work for me The other option is create a symlink but if you are a true newbie, you may or may not want to try that. If you do, here is how. Open an "X" terminal (k menu, system, terminals) and type sux the enter your root password. You are now at root level. Now type /opt/kde3/bin/konqueror and you will open Konqueror file manager. Hit "F9" and click on the next to the last icon on the left hand side of the screen (little red folder). In the tree listing in the small window on the left side of the screen, click on the /dev folder. Now find mmodem and delete it. Now open another X terminal and do the sux password thingy. Now type, cd /dev and hit enter. Now type ln-s /dev/ttyS14 /dev/modem and hit enter (if you get an error reverse the two items you just typed and try again.) Your /dev/modem is now linked to your ttyS14 and you do not have to change your settings in the Yast modem setup. - I haven't tried it yet I tried to follow the instructions I found from a guide and make it work with the smartlink drivers: http : / / p o r t a l .suse.com/sdb/en/2004/05/thallma_91_smartlink.html 1. Boot the SUSE LINUX system and log in as a user. ok 2. Open a console and enter the command "sux -". ok 3. When prompted, enter the administrator password. ok 4. Enter the command yast -i smartlink-softmodem to install a background service needed for the SmartLink driver with YaST. ok 5. Leave the console open and, in the YaST Control Center, select System -> Editor for /etc/sysconfig Files. ok 6. In the tree structure to the left, select Hardware -> Modem -> SLMODEMD_DEVICE. - There wasn't a "modem option" 7. In this section, select the entry SLMODEMD_COUNTRY. If necessary, replace the data in the input field with the land in which you are located. For example, the entry for Germany is GERMANY. To view a complete list of supported countries, enter the command slmodemd --countrylist. see step 6 8. If you have an internal modem, skip the following step and continue with step 10. I jumped to step 10 9. If you have a USB modem, select the entry SLMODEMD_DEVICE in the opened section and replace the data in the input field with slusb0. 10. Click Finish and confirm the following change list with OK. ok 11. Change to the console and enter the following two commands in the indicated order: * insserv -d slmodemd insserv: slmodemd: No such file or directory * /etc/init.d/slmodemd start bash: /etc/init.d/slmodemd: No such file or directory 12. Close the console by pressing the key combination [CTRL]+[D] twice. ok 13. Change back to the YaST Control Center and select Network Devices -> Modem. ok 14. If you have already configured your modem with YaST, delete this information including the provider data under Change... and terminate the configuration dialog. Then reopen the modem configuration in the YaST Control Center. ok 15. Even if your modem is detected, selact Other (not detected) and click Configure.... ok 16. In Modem device, enter /dev/ttySL0 manually. ok 17. Click Details. ok 18. Set Baud rate to 115200. ok 19. Click OK then Next. ok 20. From this point, perform the settings as described in the User Guide from page 99, last paragraph. ok Then I downladed the 2.9.10 drivers for winmodem from w w w . s m l i n k . c o m for Linux and I tried to compile them. linux:/home/xxxxx # cd /home/xxxxx/Desktop/slmodem-2.9.10 linux:/home/xxxxx/Desktop/slmodem-2.9.10 # make KERNEL_DIR=/path/to/linux make -C modem all make[1]: Entering directory `/home/xxxxx/Desktop/slmodem-2.9.10/modem' rebuild profile... gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -o modem_main.o -c modem_main.c gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -o modem_cmdline.o -c modem_cmdline.c gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -o modem.o -c modem.c gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -o modem_datafile.o -c modem_datafile.c gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -o modem_at.o -c modem_at.c gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -o modem_timer.o -c modem_timer.c gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -o modem_pack.o -c modem_pack.c gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -o modem_ec.o -c modem_ec.c modem_ec.c:689: warning: `t403_timeout' defined but not used gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -o modem_comp.o -c modem_comp.c gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -o modem_param.o -c modem_param.c gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -o modem_debug.o -c modem_debug.c gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -o homolog_data.o -c homolog_data.c gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -o dp_sinus.o -c dp_sinus.c gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -o dp_dummy.o -c dp_dummy.c gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -o sysdep_common.o -c sysdep_common.c gcc -o slmodemd modem_main.o modem_cmdline.o modem.o modem_datafile.o modem_at.o modem_timer.o modem_pack.o modem_ec.o modem_comp.o modem_param.o modem_debug.o homolog_data.o dp_sinus.o dp_dummy.o dsplibs.o sysdep_common.o gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -o modem_test.o -c modem_test.c gcc -o modem_test modem_test.o modem_cmdline.o modem.o modem_datafile.o modem_at.o modem_timer.o modem_pack.o modem_ec.o modem_comp.o modem_param.o modem_debug.o homolog_data.o dp_sinus.o dp_dummy.o dsplibs.o sysdep_common.o make[1]: Leaving directory `/home/xxxxx/Desktop/slmodem-2.9.10/modem' linux:/home/xxxxx/Desktop/slmodem-2.9.10 # make make -C modem all make[1]: Entering directory `/home/xxxxx/Desktop/slmodem-2.9.10/modem' make[1]: Leaving directory `/home/xxxxx/Desktop/slmodem-2.9.10/modem' linux:/home/xxxxx/Desktop/slmodem-2.9.10 # make install make -C modem all make[1]: Entering directory `/home/xxxxx/Desktop/slmodem-2.9.10/modem' make[1]: Leaving directory `/home/xxxxx/Desktop/slmodem-2.9.10/modem' make -C drivers KERNEL_DIR=/lib/modules/2.4.21-99-default/build make[1]: Entering directory `/home/xxxxx/Desktop/slmodem-2.9.10/drivers' cc -I/lib/modules/2.4.21-99-default/build/include -o kernel-ver kernel-ver.c make all KERNEL_VER=2.6.0-test3 make[2]: Entering directory `/home/xxxxx/Desktop/slmodem-2.9.10/drivers' make modules -C /lib/modules/2.4.21-99-default/build SUBDIRS=/home/xxxxx/Desktop/slmodem-2.9.10/drivers make: *** /lib/modules/2.4.21-99-default/build: No such file or directory. Stop. make: Entering an unknown directorymake: Leaving an unknown directorymake[2]: *** [all] Error 2 make[2]: Leaving directory `/home/xxxxx/Desktop/slmodem-2.9.10/drivers' make[1]: *** [all] Error 2 make[1]: Leaving directory `/home/xxxxx/Desktop/slmodem-2.9.10/drivers' make: *** [drivers] Error 2 linux:/home/xxxxx/Desktop/slmodem-2.9.10 # AT+GCI=<T.35 22 > bash: syntax error near unexpected token `newline' linux:/home/xxxxx/Desktop/slmodem-2.9.10 # AT+GCI=T.35 22 bash: AT+GCI=T.35: command not found linux:/home/xxxxx/Desktop/slmodem-2.9.10 # AT17 bash: AT17: command not found linux:/home/xxxxx/Desktop/slmodem-2.9.10 # slmodem --country=MY_COUNTRY bash: slmodem: command not found linux:/home/xxxxx/Desktop/slmodem-2.9.10 # slmodem bash: slmodem: command not found linux:/home/xxxxx/Desktop/slmodem-2.9.10 # slmodemd --countrylist bash: slmodemd: command not found Guess it didn't work either. Then a guy told me that I should use the 2.7.10 drivers because the 2.9.10 didn't have support for the AC97 chipset but for the MC97 Chipset. I tried to use them: linux:/home/xxxxx/Desktop/ApegnosmeniProspatheia/slmdm-2.7.10 # vi Makefile I give you the modified makefile part as I have configured it according the following instructions: "Edit the Makefile and set the include path to point to kernel source. Find the following two separate lines: KERNEL_INCLUDES:= /usr/src/linux/include MODULES_DIR = /lib/modules/$(shell ./kernel-ver)/misc ...and modify them to... KERNEL_INCLUDES:= /lib/modules/`uname -r`/build/include /usr/src/linux-2.4/include MODULES_DIR = /lib/modules/`uname -r`/kernel/drivers/telephony /lib/modules/`uname -r`/kernel/misc" The final makefile part was somethinf like that: # Definitions MODULES_DIR = /lib/modules/`uname -r`/kernel/drivers/telephony /lib/modules/`uname -r`/kernel/misc MODEM_DEV := ttySL0 MODEM_LINK := modem MODULES_CONF:= /etc/modules.conf # Path to your kernel's includes ifndef KERNEL_INCLUDES KERNEL_INCLUDES= /lib/modules/`uname -r`/build/include /usr/src/linux-2.4/include endif I proceeded with the following commands: linux:/home/xxxxx/Desktop/ApegnosmeniProspatheia/slmdm-2.7.10 # make Makefile:36: *** missing separator. Stop. linux:/home/xxxxx/Desktop/ApegnosmeniProspatheia/slmdm-2.7.10 # Make bash: Make: command not found linux:/home/xxxxx/Desktop/ApegnosmeniProspatheia/slmdm-2.7.10 # make install-amr Makefile:36: *** missing separator. Stop. I am also giving you the KInternet logs: SuSE Meta pppd (smpppd-ifcfg), Version 1.06 on linux. Status is: disconnected trying to connect to smpppd connect to smpppd Status is: disconnected Status is: connecting pppd[0]: Plugin passwordfd.so loaded. pppd[0]: Failed to open /dev/ttySL0: No such device Status is: disconnected pppd[0] died: Serial port open failed (exit code 7) I am a bit dissappointed. Any suggestions? |
To find out which driver will work for your modem, you are probably best off posting your modemdata.txt on the linmodems help list. Once you have the right drivers, if you are getting compile errors, then post back here.
|
Thanks for replying.
any link for that list? |
Yep. Here you go.
Good luck |
I have exactly the same modem in an expensive smart IBM Thinkpad 40T -- doesn't belong to me though.
I tried the smartlink drivers in deb packages, and all kind of stuff as advised on Ubuntu forum. I didn't succed further than dialing phone number and then failure. those winmodem manufacturers ought to be shot -- only aiming to make profit out of rubbish. fed up to the backteeth, i must say. And the darned laptop doesn't have a serial port -- though I have a serial modem that is fine. only solution I suppose: building a local network. |
All times are GMT -5. The time now is 11:11 PM. |