Hi Marvin, I tried wvdial and this time it came back with "No Dial Tone" -- and indeed all you could hear over the laptop's speakers was noise and so forth, no dial tone. The Carrier Check statement was there and was set to no. Which slmodemd should I be downloading, is it? SLMODEMD.gcc4.3.tar.gz ? I note the readme in that archive mentions doing a modprobe with the low level driver, what should this be? I don't remember issuing a modprobe argument at any given time. Thanks! Vicky 2008/12/18 Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx>: > Vicky, > > # slmodemd -c UK --alsa modem:1 > is correct for your System > > Rather then using Kinternet try usging wvdial > # wvdialconf /etc/wvdial.conf > Then edit your personal info into /etc/wvdial.conf, > adding a line: > Carrier Check = no > which isn't implemented under Kinternet. > > Then with slmodemd still running, try a dialout from another console with: > # wvdial > > If that doesn't help, you should try compiling slmodemd on your own > System to get an optimal match with your "ALSA verion is 1.0.16" > > But first try using wvdial. > > MarvS > > On Wed, Dec 17, 2008 at 4:44 AM, Vicky Lamburn > <vicky.lamburn@xxxxxxxxxxxxxx> wrote: >> Hi Martin >> >> Many thanks for your really quick reply. >> >> This is the contents of my ModemData.txt file (below) >> >> Since then I have tried stopping slmodemd and running it as hinted >> with what looks like a correct ALSA argument: >> >> # slmodemd -c UK --alsa modem:1 >> >> Now when kinternet tries dialling, I can actually hear something on >> the laptop's speaker, lots of distorted noise crackling away -- but no >> actual dialling. >> >> Vicky >> >> --- Contents of my ModemData.txt --- >> >> Only plain text email is forwarded by the Discuss@xxxxxxxxxxxxx List Server, >> as HTML can contain viruses. Use as the email Subject Line: >> YourName, YourCountry kernel 2.6.25.18-0.2-default >> With this Subject Line cogent experts will be alerted, and useful >> case names left in the Archive. >> YourCountry will enable Country specific guidance. Linux experts in >> YourCountry >> can be found through: http://www.linux.org/groups/index.html. >> They will know your Country's modem code, which may be essential for >> dialup service. >> Responses from Discuss@xxxxxxxxxxxxx are sometimes blocked by an >> Internet Provider mail filters. >> So in a day, also check the Archived responses at http://www.linmodems.org >> -------------------------- System information ---------------------------- >> CPU=i686, >> Linux version 2.6.25.18-0.2-default (geeko@buildhost) (gcc version >> 4.3.1 20080507 (prerelease) [gcc-4_3-branch revision 135036] (SUSE >> Linux) ) #1 SMP 2008-10-21 16:30:26 +0200 >> scanModem update of: 2008_11_06 >> >> The slmodemd set symbolic link is /dev/ttySL0 -> /dev/pts/3 >> There are no blacklisted modem drivers in /etc/modprobe* files >> Attached USB devices are: >> ID 1d6b:0001 Linux Foundation 1.1 root hub >> ID 1d6b:0001 Linux Foundation 1.1 root hub >> ID 1d6b:0001 Linux Foundation 1.1 root hub >> ID 1d6b:0002 Linux Foundation 2.0 root hub >> >> USB modems not recognized >> >> For candidate card in slot 00:1f.6, firmware information and bootup >> diagnostics are: >> PCI slot PCI ID SubsystemID Name >> ---------- --------- --------- -------------- >> 00:1f.6 8086:24c6 1014:0524 Modem: Intel Corporation 82801DB/DBL/DBM >> >> Modem interrupt assignment and sharing: >> 11: 87010 XT-PIC-XT uhci_hcd:usb1, ehci_hcd:usb2, >> uhci_hcd:usb3, uhci_hcd:usb4, Intel 82801DB-ICH4, eth1, Intel >> 82801DB-ICH4 Modem, yenta, yenta, radeon@pci:0000:01:00.0, eth0 >> --- Bootup diagnostics for card in PCI slot 00:1f.6 ---- >> ACPI: PCI Interrupt 0000:00:1f.6[B] -> Link [LNKB] -> GSI 11 (level, >> low) -> IRQ 11 >> ACPI: PCI interrupt for device 0000:00:1f.6 disabled >> ACPI: PCI Interrupt 0000:00:1f.6[B] -> Link [LNKB] -> GSI 11 (level, >> low) -> IRQ 11 >> PCI: Setting latency timer of device 0000:00:1f.6 to 64 >> >> The PCI slot 00:1f.6 of the modem card may be disabled early in >> a bootup process, but then enabled later. If modem drivers load >> but the modem is not responsive, read DOCs/Bootup.txt about possible fixes. >> Send dmesg.txt along with ModemData.txt to discuss@xxxxxxxxxxxxx >> if help is needed. >> >> >> >> ===== Advanced Linux Sound Architecture (ALSA) diagnostics ===== >> The ALSA packages provide audio support and also drivers for some modems. >> ALSA diagnostics are written during bootup to /proc/asound/ folders. >> >> The ALSA verion is 1.0.16 >> The modem cards detected by "aplay -l" are: >> card 1: Modem [Intel 82801DB-ICH4 Modem], device 0: Intel ICH - Modem >> [Intel 82801DB-ICH4 Modem - Modem] >> >> The /proc/asound/pcm file reports: >> ----------------------- >> 00-04: Intel ICH - IEC958 : Intel 82801DB-ICH4 - IEC958 : playback 1 >> 00-03: Intel ICH - ADC2 : Intel 82801DB-ICH4 - ADC2 : capture 1 >> 00-02: Intel ICH - MIC2 ADC : Intel 82801DB-ICH4 - MIC2 ADC : capture 1 >> 00-01: Intel ICH - MIC ADC : Intel 82801DB-ICH4 - MIC ADC : capture 1 >> 00-00: Intel ICH : Intel 82801DB-ICH4 : playback 1 : capture 1 >> 01-00: Intel ICH - Modem : Intel 82801DB-ICH4 Modem - Modem : playback >> 1 : capture 1 >> >> about /proc/asound/cards: >> ------------------------ >> 0 [I82801DBICH4 ]: ICH4 - Intel 82801DB-ICH4 >> Intel 82801DB-ICH4 with AD1981B at irq 11 >> 1 [Modem ]: ICH-MODEM - Intel 82801DB-ICH4 Modem >> Intel 82801DB-ICH4 Modem at irq 11 >> >> Modem firmware information is in /proc/asound/card1/codec97#0/mc97#1-1 >> ----------------------------------------------- >> Extended modem ID: codec=1 LIN1 >> >> Lines in: /proc/asound/card1/codec97#0/mc97#1-1+regs >> ------------------------------- >> 0:7c = 5349 and 0:7e = 4c27 >> are translated from hexadecimal code into the modem chip identifier: SIL27 >> >> >> The driver snd-intel8x0m with its dependent drivers: >> snd_intel8x0m 22156 5 >> snd_ac97_codec 108580 2 snd_intel8x0m,snd_intel8x0 >> snd_pcm 87812 6 >> snd_pcm_oss,snd_intel8x0m,snd_intel8x0,snd_ac97_codec >> snd 67256 23 >> snd_pcm_oss,snd_mixer_oss,snd_seq,snd_seq_device,snd_intel8x0m,snd_intel8x0,snd_ac97_codec,snd_pcm,snd_timer >> snd_page_alloc 14984 3 snd_intel8x0m,snd_intel8x0,snd_pcm >> ---------- >> provide modem + audio support. >> >> === Finished firmware and bootup diagnostics, next deducing cogent software. === >> >> Predictive diagnostics for card in bus 00:1f.6: >> Modem chipset detected on >> NAME="Modem: Intel Corporation 82801DB/DBL/DBM " >> CLASS=0703 >> PCIDEV=8086:24c6 >> SUBSYS=1014:0524 >> IRQ=11 >> SOFT=8086:24c6.MC97 >> CodecArchived=SIL27 >> CodecDiagnosed=SIL27 >> CodecClass=SIL >> IDENT=slmodemd >> SLMODEMD_DEVICE=modem:1 >> Driver=snd-intel8x0m >> >> For candidate modem in: 00:1f.6 >> 0703 Modem: Intel Corporation 82801DB/DBL/DBM >> Primary device ID: 8086:24c6 >> Subsystem PCI_id 1014:0524 >> Softmodem codec or chipset from diagnostics: SIL27, an LSI/AgereSystems type >> from Archives: SIL27 >> >> >> >> Support type needed or chipset: slmodemd >> >> An ALSA (Advanced Linux Sound Architecture) modem driver: snd-intel8x0m >> provides Low Level support enabling contact with the modem hardware. >> For all BUT Conexant chip soft modems (using hsfmodem software) >> complementary High Level support is through a Smartlink utility: slmodemd >> >> Download from http://linmodems.technion.ac.il/packages/smartlink/ >> the package SLMODEMD.gcc4.3.tar.gz having a compiled slmodemd. Unpack >> under Linux with: >> $ tar zxf SLMODEMD.gcc4.3.tar.gz >> and read instructions therein. But briefly, the modem is setup with command: >> slmodemd -c YOUR_COUNTRY --alsa modem:1 >> reporting dynamic creation of ports: >> /dev/ttySL0 --> /dev/pts/N , with N some number >> Read DOCs/Smartlink.txt and Modem/DOCs/YourSystem.txt for follow >> through guidance. >> >> ----------------end Softmodem section -------------- >> >> Writing DOCs/Intel.txt >> Writing DOCs/Smartlink.txt >> ============ end Smartlink section ===================== >> >> Completed candidate modem analyses. >> >> The base of the UDEV device file system is: /dev/.udev >> >> Versions adequately match for the compiler installed: 4.3.1 >> and the compiler used in kernel assembly: 4.3 >> >> >> >> Minimal compiling resources appear complete: >> make utility - /usr/bin/make >> Compiler version 4.3 >> linuc_headers base folder /lib/modules/2.6.25.18-0.2-default/build >> >> However some compilations and executable functions may need additional files, >> in the FileNames.h (so called kernel "h"eaders) collection installed >> in /usr/include/ . >> For martian_modem, additional required packages are needed. The also >> required headers of package libc6 are commonly installed by default. >> Compiling hsfmodem drivers does require linux-libc-dev and libc6-dev >> packages, for kernels 2.6.24 and later versions. >> In not included on your install CD, search for them at >> http://packages.ubuntu.com >> or comparable Repository for other Linux distros. >> When compiling ALSA drivers, the utility "patch" will also be needed. >> >> >> >> >> If a driver compilation fails, with message including some lack of >> some FileName.h (stdio.h for example), then >> Some additional kernel-header files need installation to /usr/include. >> The minimal additional packages are libc6-dev >> and any of its dependents, under Ubuntu linux-libc-dev >> >> If an alternate ethernet connection is available, >> $ apt-get update >> $ apt-get -s install linux-kernel-devel >> will install needed packages. >> For Debian/Ubuntu related distributions, run the following command to >> display the needed package list: >> >> Otherwise packages have to be found through http://packages.ubuntu.com >> Once downloaded and transferred into a Linux partition, >> they can be installed alltogether with: >> $ sudo dpkg -i *.deb >> >> >> Checking pppd properties: >> -rwxr-xr-x 1 root dialout 304644 2008-06-06 22:21 /usr/sbin/pppd >> >> In case of an "error 17" "serial loopback" problem, see: >> http://linmodems.technion.ac.il/linmodems/archive-sixth/msg02637.html >> >> To enable dialout without Root permission do: >> $ su - root (not for Ubuntu) >> chmod a+x /usr/sbin/pppd >> or under Ubuntu related Linuxes >> chmod a+x /usr/sbin/pppd >> >> Checking settings of: /etc/ppp/options >> noipdefault >> noauth >> crtscts >> lock >> modem >> asyncmap 0 >> nodetach >> lcp-echo-interval 30 >> lcp-echo-failure 4 >> lcp-max-configure 60 >> lcp-restart 2 >> idle 600 >> noipx >> file /etc/ppp/filters >> >> In case of a message like: >> Warning: Could not modify /etc/ppp/pap-secrets: Permission denied >> see http://linmodems.technion.ac.il/bigarch/archive-sixth/msg04656.html >> >> Read Modem/DOCs/YourSystem.txt concerning other COMM channels: eth0 eth1 >> Which can interfere with Browser naviagation. >> >> Don't worry about the following, it is for experts should trouble >> shooting be necessary. >> ========================================================== >> >> Checking for modem support lines: >> -------------------------------------- >> /device/modem symbolic link: >> slmodemd created symbolic link /dev/ttySL0: lrwxrwxrwx 1 root root 10 >> 2008-12-17 09:11 /dev/ttySL0 -> /dev/pts/3 >> Within /etc/udev/ files: >> /etc/udev/rules.d/50-udev-default.rules:KERNEL=="mwave", NAME="modems/mwave", >> GROUP="uucp" >> /etc/udev/rules.d/77-network.rules:SUBSYSTEM=="net", >> ENV{INTERFACE}=="ppp*|ippp*|isdn*|plip*|lo*|irda*|dummy*|ipsec*|tun*|tap*|bond*|vlan*|modem*|dsl*", >> GOTO="skip_ifup" >> Within /etc/modprobe.conf files: >> /etc/modprobe.conf:# Linux ACP modem (Mwave) >> Within any ancient /etc/devfs files: >> >> Within ancient kernel 2.4.n /etc/module.conf files: >> >> --------- end modem support lines -------- >> >
