Marko, There is clearly a protocol problem in authentication, having nothing to do with the driver per se. Look through the PostInstall Howto at http://linmodems.technion.ac.il There occassional Internet Providers which are "Linux hostile" You might check with your closest Linux group to assess which IPs dialin logons are efffective with. Also try substituting for you LoginName, Your_IP_Domain/LoginName such as VERIZON.NET/LoginName This syntax is needed under some CHAP protocols. MarvS On 9/12/07, Marko Hilse <marko@xxxxxxxxxx> wrote: > Hi and thy for helping, > > i got my Modem running, but i Can not dial in. Whether with Kinternet > nor with wvdial. > > If I try with wvdial I get the output: > > sudo wvdial > root's password: > --> WvDial: Internet dialer version 1.56 (abuild@roth) > --> Cannot get information for serial port. > --> Initializing modem. > --> Sending: ATZ > ATZ > OK > --> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 > ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 > OK > --> Modem initialized. > --> Sending: ATDT08003334450 > --> Waiting for carrier. > ATDT08003334450 > CONNECT 46667 > --> Carrier detected. Waiting for prompt. > CC > ********************************************************************** > * __ __ * > * _ _____ ______________ _/ /____ / / * > * | | / / _ \/ ___/ ___/ __ `/ __/ _ \/ / * > * | |/ / __/ / (__ ) /_/ / /_/ __/ / * > * |___/\___/_/ /____/\__,_/\__/\___/_/ * > * * > ********************************************************************** > * No unauthorized access, misuse or other unlawful activities * > * with any of our equipment. This may result in legal actions * > ********************************************************************** > * In case of operational problems contact info@xxxxxxxxxxx * > * In case of abuse problems contact abuse@xxxxxxxxxxx * > ********************************************************************** > You are at 'ber022ir002' on port '"Modem Dialin"1/8/79' > ********************************************************************** > (c) v e r s a t e l www.versatel.de > Username: > User Access Verification > Username: > --> Looks like a login prompt. > --> Sending: quedel > quedel > Password: > --> Looks like a password prompt. > --> Sending: (password) > % Authentication failed. > User Access Verification > Username: > --> Looks like a login prompt. > --> Sending: quedel > quedel > Password: > --> Looks like a password prompt. > --> Sending: (password) > % Authentication failed. > User Access Verification > Username: > --> Looks like a login prompt. > --> Sending: quedel > --> Don't know what to do! Starting pppd and hoping for the best. > --> Starting pppd at Wed Sep 12 21:54:03 2007 > --> Pid of pppd: 4516 > --> Using interface ppp0 > --> pppd: h[0e][06][08]8![06][08] > --> pppd: h[0e][06][08]8![06][08] > > Caught signal 2: Attempting to exit gracefully... > --> Terminating on signal 15 > --> pppd: h[0e][06][08]8![06][08] > --> pppd: h[0e][06][08]8![06][08] > --> Disconnecting at Wed Sep 12 21:55:19 2007 > > Only plain text email is forwarded by the DISCUSS@xxxxxxxxxxxxx List Server. > Do use the following as the email Subject Line: > SomeName, YourCountry > Welcome to openSUSE 10.3 (i586) Alpha5plus - Kernel kernel 2.6.18.8-0.5-default > This will alert cogent experts, and distinguish cases in the Archives. > YourCountry will enable Country Code guidance. > Occassionally responses are blocked by an Internet Provider mail filters. > So in a day, also check the Archived responses at http://www.linmodems.org . > Local Linux experts can be found through: http://www.linux.org/groups/index.html > -------------------------- System information ---------------------------- > CPU=i686, > Welcome to openSUSE 10.3 (i586) Alpha5plus - Kernel > Linux version 2.6.18.8-0.5-default (geeko@buildhost) (gcc version 4.1.2 20061115 (prerelease) (SUSE Linux)) #1 SMP Fri Jun 22 12:17:53 UTC 2007 > scanModem update of: 2007_Sept_07 > The modem symbolic link is /dev/modem -> /dev/ttySL0 > The slmodemd set symbolic link is /dev/ttySL0 -> /dev/pts/3 > > There are no blacklisted modem drivers in /etc/modprobe* files > USB modem not detected by lsusb > > > Several modems are supported by drivers with ALSA, the Advanced Linux Sound Architecture software. > Copying ALSA diagnostics to Modem/ALSAroot.tgz > ALSAversion = 1.0.14 > > Modem or candidate host audio card have firmware information and diagnostics: > > PCI slot PCI ID SubsystemID Name > ---------- --------- --------- -------------- > 00:1f.6 8086:24c6 1025:0035 Modem: Intel Corporation 82801DB/DBL/DBM > > Modem interrupt assignment and sharing: > 10: 133372 XT-PIC uhci_hcd:usb2, uhci_hcd:usb3, ehci_hcd:usb4, eth1, ohci1394, yenta, yenta, Intel 82801DB-ICH4 Modem, Intel 82801DB-ICH4, eth0 > --- Bootup diagnostics for card in PCI slot 00:1f.6 ---- > ACPI: PCI Interrupt 0000:00:1f.6[B] -> Link [LNKB] -> GSI 10 (level, low) -> IRQ 10 > ACPI: PCI interrupt for device 0000:00:1f.6 disabled > PCI: Enabling device 0000:00:1f.6 (0000 -> 0001) > ACPI: PCI Interrupt 0000:00:1f.6[B] -> Link [LNKB] -> GSI 10 (level, low) -> IRQ 10 > 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 Bootup.txt about possible fixes. > Send dmesg.txt along with ModemData.txt to discuss@xxxxxxxxxxxxx > if help is needed. > > > === Finished modem firmware and bootup diagnostics section. === > === Next deducing cogent software === > > Modem not detected though HDA card diagnostics > For candidate modem in PCI bus: 00:1f.6 > Class 0703: 8086:24c6 Modem: Intel Corporation 82801DB/DBL/DBM > Primary PCI_id 8086:24c6 > Subsystem PCI_id 1025:0035 > Softmodem codec or Vendor from diagnostics: SIL27, an AgereSystems type. > from Archives: SIL27, an AgereSystems type. > > > Lacking a dsp (digital signal processing) chip, the modem is a software > intensive or "softmodem" type. Its primary controller manages the traffic > with the CPU. But the software needed is specified in the Subsystem. > ----------------------------------------- > 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.1.tar.gz having a compiled slmodemd. Unpack under Linux with: > $ tar zxf SLMODEMD.gcc4.1.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 Smartlink.txt and Modem/YourSystem.txt for follow through guidance. > > Already loaded into the kernel is snd-intel8x0m and audio drivers it depends on, > displayed by: lsmod | grep snd_intel8x0m > Module Size Used by > ------------------------------------- > snd_intel8x0m 21388 6 > snd_ac97_codec 97568 2 snd_intel8x0,snd_intel8x0m > snd_pcm 88068 6 snd_pcm_oss,snd_intel8x0,snd_intel8x0m,snd_ac97_codec > snd 61572 22 snd_seq_dummy,snd_pcm_oss,snd_mixer_oss,snd_seq,snd_seq_device,snd_intel8x0,snd_intel8x0m,snd_ac97_codec,snd_pcm,snd_timer > snd_page_alloc 14472 3 snd_intel8x0,snd_intel8x0m,snd_pcm > > > The diagnostic outputs for this softmodem section have their raw information in > folders and text files under /proc/asound/ which you can browse. The information > is from files: > /proc/asound/pcm > ------------------------------- > 01-00: Intel ICH - Modem : Intel 82801DB-ICH4 Modem - Modem : playback 1 : capture 1 > 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 > > /proc/asound/modules > ------------------------------- > 0 snd_intel8x0 > 1 snd_intel8x0m > /proc/asound/card1/codec97#0/mc97#1-1+regs > ------------------------------- > 0:7c = 5349 and 0:7e = 4c27 > which were translated from hexadecimal code into: SIL27 > > /proc/asound/card1/codec97#0/mc97#1-1 > ------------------------------- > Extended modem ID: codec=1 LIN1 > > and from the command: > aplay -l | grep -i modem > card 1: Modem [Intel 82801DB-ICH4 Modem], device 0: Intel ICH - Modem [Intel 82801DB-ICH4 Modem - Modem] > > ----------------end Softmodem section -------------- > > Writing Intel.txt > Writing 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.1.2 > and the compiler used in kernel assembly: 4.1.3 > > linux-headers-2.6.18.8-0.5-default resources needed for compiling are not manifestly ready! > > If compiling is necessary packages must be installed, providing: > kernel-source-2.6.18.8-0.5-default > > > If a driver compilation files with message including some lack of some FileName.h (stdio.h for example. > Some additional kernel-header files need installation to /usr/include. > For Debian/Ubuntu related distributions, run the following command to display the needed package list: > $ sudo apt-get -s install linux-kernel-devel > While some of the files may be on the install CD, others may have to be found through http://packages.ubuntu.com > > For Ubuntu Feisty, additional packages required were: > libc6-dev linux-libc-dev > available through http://packages.ubuntu.com/ , if not on the install CD. > Such packages may have different names for other Linux distributions. > Try installing just the libc6-dev, then test the compile again. > > > Checking pppd properties: > -rwxr-xr-x 1 root dialout 299576 12. Jul 04:32 /usr/sbin/pppd > > In case of an "error 17" "serial loopback" problem, see: > http://phep2.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 > > > Don't worry about the following, it is for the experts > should trouble shooting be necessary. > ========================================================== > > Checking for modem support lines: > -------------------------------------- > /device/modem symbolic link: lrwxrwxrwx 1 root root 11 12. Sep 21:54 /dev/modem -> /dev/ttySL0 > slmodemd created symbolic link /dev/ttySL0: lrwxrwxrwx 1 root root 10 12. Sep 21:29 /dev/ttySL0 -> /dev/pts/3 > Within /etc/udev/ files: > /etc/udev/rules.d/50-udev-default.rules:KERNEL=="mwave", NAME="modems/%k", 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) > /etc/modprobe.d/blacklist:# ALSA PCI sound/modem modules - should be configured via yast > /etc/modprobe.d/blacklist:blacklist snd-atiixp-modem > /etc/modprobe.d/blacklist:blacklist snd-via82xx-modem > Within any ancient /etc/devfs files: > > Within ancient kernel 2.4.n /etc/module.conf files: > > --------- end modem support lines -------- > > >
