Davide, If running scanModem generated in the Modem/ folder a file like ALSADdavide.tgz, please send it to me. If ---------- PCI slot PCI ID SubsystemID Name ---------- --------- --------- -------------- 00:1b.0 8086:284b 103c:30d8 Audio device: Intel Corporation 82801H ---------- is going to work with slmodemd support, the device name CANNOT be modem:0 . This is the audio function. THough competent with wvdialconf, it lacks the COMM support to get on line. Try: $ sudo slmodemd -c USA --alsa hw:0,1 and $ sudo slmodemd -c USA --alsa hw:0,6 MarvS On Jan 20, 2008 8:37 AM, Jacques Goldberg <Jacques.Goldberg@xxxxxxx> wrote: > Good > There is a small chance to find more in digging a bit deeper than you > did, but it is not a must, would just confirm that we are on the right > track. > Please understand that I am not a Windows expert, even not user. Win XP > was there on my newest laptop, I kept it in a small partition in order > not to give any chance to service my hardware because they something > else than Windows. > This said, here is what I did for you under XP, probably the same with > other versions: > Start->Contro_Panel>System->Hardware->Device_Manager->Modem > Click + for list of available modems. > Right click your modem for Properties > ->Details->in parallel: > Device Id > Hardware Id > Compatible IDs > Matching devices. > > Please look into the last four (i.e. the 4 first choices under Details) > if you see 11C1 and then tell us the rest of the line (may be 48C 48F > 620 ....). This will say for sure that the LINUX AGRSM driver is very > likely to be what your modem needs. > > But you may try without this extra data. > > From http://linmodems.technion.ac.il/ltmodem/sv92 > download the last update agrsm-20070804.tar.gz > Unpack with > tar zxf agrsm-20070804.tar.gz > Go into software > cd agrsm-20070804 > Read and do as in README, which boils down to: > make module > sudo make install > sudo modprobe agrmodem > sudo modprobe agrserial > Use > sudo lsmod | grep agr > to verify that the two modules agrserial.ko and agrmodem.ko are loaded > in memory after they have been compiled by make module and installed by > make install (make install is set to automatically do the modprobe > commands but the file ReadmeUpdate.txt next to README repeats them > explicitly). > > > The README file does not say but I understand to be necessary to > ln -s /dev/ttyAGS3 /dev/ttyAGR > ln -s /dev/ttyAGS3 /dev/modem > > before trying to connect with wvdial > (http://linmodems.technion.ac.il/wvdial.html) > or kppp or minicom as some people prefer to do. > > Note that this is very close to Hugo Canalli's message in this thread > except that Hugo, I believe, skipped the instructions to download, > compile and install the driver. > > PLEASE KEEP US INFORMED, wether success or failure. > > Jacques > > > Davide Rognoni wrote: > > OK, "Agere Systems HDA Modem" > > > > Driver files: > > C:\Windows\agrsmdel.exe > > C:\Windows\system32\agrscoin.dll > > C:\Windows\system32\agrsmsvc.exe > > C:\Windows\system32\DRIVERS\AGRSM.sys > > C:\Windows\system32\drivers\modem.sys > > > > On 1/19/08, Jacques Goldberg <Jacques.Goldberg@xxxxxxx> wrote: > >> The ICH chips control the AC'97 bus in the computer. Nothing in them > >> gives any information on the modem. > >> > >> The subsytem vendor 103c is Hewlett Packard, indicating a special > >> purpose chip produced by Hewlett Packard which almost certainly > >> comprises a "standard" modem subcomponent such as Agere, Conexant or > >> SmartLink.. > >> The device id 30d8 is not know to chipset tables. > >> HP often uses Lucent/Agere modems, but not exclusively. > >> > >> Davide, if you can boot Windows on the same machine, find the modem > >> driver used under Windows, such as LTMODEM, Conexant and others. > >> There are several ways to identify the driver. > >> You can open a Hyperterminal and query the modem from ATI0 to ATI10 and > >> will see the driver. > >> Or you can go to the System control from the Windows control panel and > >> browse the system hardware components until a step named driver which > >> will tell you which driver Windows uses. > >> From there it may be possible to define a suitable Linux driver. > >> Jacques > >> > >> Antonio Olivares wrote: > >>> Davide, > >>> > >>> You might be on the right track with using > >>> SLMODEMD.4.1.tar.gz > >>> > >>> I have checked on Linuxant page and it gives the > >>> following: > >>> > >>> INTEL AC-Link Controller (ICH) > >>> # PCI ID 8086:7186 > >>> # PCI ID 8086:7196 > >>> # PCI ID 8086:2416 > >>> # PCI ID 8086:2446 > >>> # PCI ID 8086:2486 > >>> # PCI ID 8086:24C6 > >>> # PCI ID 8086:24D6 > >>> # PCI ID 8086:266D > >>> # PCI ID 8086:2426 > >>> > >>> # PCI ID 10DE:00D9 (NVIDIA nForce3) > >>> # PCI ID 10DE:01C1 (NVIDIA) > >>> > >>> VIA AC-Link Controller > >>> # PCI ID 1106:3068 > >>> > >>> ALI AC-Link Controller > >>> # PCI ID {1025,10B9}:5453 > >>> # PCI ID {1025,10B9}:5457 > >>> > >>> The internal modem of HP omnibook xe4500 series > >>> machines should work with this driver. > >>> > >>> ATI AC-Link Controller > >>> # PCI ID 1002:434D > >>> # PCI ID 1002:4378 > >>> > >>> SIS AC-Link Controller > >>> # PCI ID 1039:7013 > >>> > >>> As far as wvdial try changing wvdial.conf from what > >>> you have in the init strings to what is specified in > >>> wvdial.txt like > >>> > >>> Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 > >>> # Lack of dialtone acquisition can be due to low line > >>> voltage, > >>> # a common problem in Italy. > >>> # Try inserting a "dial without waiting": X3 > >>> # Init2 = ATQ0 V1 E1 S0=0 X3 &C1 &D2 +FCLASS=0 > >>> # In case of connection instabilities, specify a > >>> lower frequency: > >>> # Init2 = ATQ0 V1 E1 S0=0 X3 &C1 &D2 +MS=34 > >>> # a MS=90 option is sometimes necessary for Internet > >>> Providers with buggy V92 protocols: > >>> # Init2 = ATQ0 V1 E1 S0=0 X3 &C1 &D2 +MS=90 > >>> > >>> Meaning instead of having the top line try the > >>> following: > >>> > >>> # Init2 = ATQ0 V1 E1 S0=0 X3 &C1 &D2 +MS=34 > >>> > >>> Report back if you are successful/unsuccesful. > >>> > >>> Regards, > >>> > >>> Antonio > >>> > >>> > >>> > >>> On Jan 18, 2008 4:24 PM, Davide Rognoni > >>> <davide.rognoni@xxxxxxxxx> wrote: > >>>> OK, I have a NO CARRIER error (X3 is the solution on > >>> windows): > >>> root@davide-laptop:/home/davide/Desktop/scanModem/SLMODEMD.gcc4.1# > >>>> ./slmodemd --debug --alsa -c ITALY modem:0 > >>>> SmartLink Soft Modem: version 2.9.11 Aug 6 2007 > >>> 22:02:27 > >>>> <680.660468> SmartLink Soft Modem: version 2.9.11 > >>> Aug 6 2007 22:02:27 > >>>> <680.660518> modem:0: startup modem... > >>>> <680.660604> modem:0: update termios... > >>>> symbolic link `/dev/ttySL0' -> `/dev/pts/1' created. > >>>> modem `modem:0' created. TTY is `/dev/pts/1' > >>>> <680.661147> open file: > >>> /var/lib/slmodem/data.modem:0... > >>>> <680.661541> main: rt applyed: SCHED_FIFO, pri 99 > >>>> Use `/dev/ttySL0' as modem device, Ctrl+C for > >>> termination. > >>>> <684.523022> main: termios changed. > >>>> <684.523039> modem:0: update termios... > >>>> <684.603114> main: termios changed. > >>>> <684.603128> modem:0: update termios... > >>>> <684.702980> modem:0: run cmd: ATZ > >>>> <684.702996> modem:0: modem reset... > >>>> <684.703001> modem:0: modem set state: 1 --> 1... > >>>> <684.703008> modem:0: modem set mode: -> 0... > >>>> <684.703013> modem:0: modem report result: 0 (OK) > >>>> <684.803022> modem:0: run cmd: > >>> ATQ0V1E1S0=0&C1&D2+FCLASS=0 > >>>> <684.803047> modem:0: modem set mode: -> 0... > >>>> <684.803052> modem:0: modem report result: 0 (OK) > >>>> <684.902980> modem:0: run cmd: ATX3 > >>>> <684.902994> modem:0: modem report result: 0 (OK) > >>>> <685.002978> modem:0: run cmd: ATL2 > >>>> <685.002996> main: alsa_ioctl: cmd 8, arg 0... > >>>> <685.003002> modem:0: modem report result: 0 (OK) > >>>> <685.103436> modem:0: run cmd: ATX3DT7020187187 > >>>> <685.103458> modem:0: modem dial: T7020187187... > >>>> <685.103463> modem:0: modem_dial_start... > >>>> <685.103486> modem:0: modem_start.. > >>>> <685.103491> modem:0: modem set state: 1 --> 2... > >>>> <685.103497> modem:0: new state: DP_ESTAB > >>>> <685.103501> main: alsa_ioctl: cmd 8, arg 2... > >>>> <685.103506> modem:0: modem set hook: 0 --> 1... > >>>> <685.103511> main: alsa_ioctl: cmd 2, arg 1... > >>>> <685.110905> main: alsa_ioctl: cmd 11, arg 0... > >>>> <685.111025> main: alsa_ioctl: cmd 4, arg 2580... > >>>> <685.111031> main: alsa_ioctl: cmd 7, arg 30... > >>>> <685.111036> main: alsa_start... > >>>> Hooks PCM > >>>> Its setup is: > >>>> stream : PLAYBACK > >>>> access : RW_INTERLEAVED > >>>> format : S16_LE > >>>> subformat : STD > >>>> channels : 1 > >>>> rate : 9600 > >>>> exact rate : 9600 (9600/1) > >>>> msbits : 16 > >>>> buffer_size : 2048 > >>>> period_size : 64 > >>>> period_time : 6666 > >>>> tick_time : 4000 > >>>> tstamp_mode : NONE > >>>> period_step : 1 > >>>> sleep_min : 0 > >>>> avail_min : 4 > >>>> xfer_align : 4 > >>>> start_threshold : 2147483647 > >>>> stop_threshold : 2048 > >>>> silence_threshold: 0 > >>>> silence_size : 0 > >>>> boundary : 1073741824 > >>>> Slave: Hardware PCM card 0 'HDA Intel' device 6 > >>> subdevice 0 > >>>> Its setup is: > >>>> stream : PLAYBACK > >>>> access : RW_INTERLEAVED > >>>> format : S16_LE > >>>> subformat : STD > >>>> channels : 1 > >>>> rate : 9600 > >>>> exact rate : 9600 (9600/1) > >>>> msbits : 16 > >>>> buffer_size : 2048 > >>>> period_size : 64 > >>>> period_time : 6666 > >>>> tick_time : 4000 > >>>> tstamp_mode : NONE > >>>> period_step : 1 > >>>> sleep_min : 0 > >>>> avail_min : 4 > >>>> xfer_align : 4 > >>>> start_threshold : 2147483647 > >>>> stop_threshold : 2048 > >>>> silence_threshold: 0 > >>>> silence_size : 0 > >>>> boundary : 1073741824 > >>>> Hooks PCM > >>>> Its setup is: > >>>> stream : CAPTURE > >>>> access : RW_INTERLEAVED > >>>> format : S16_LE > >>>> subformat : STD > >>>> channels : 1 > >>>> rate : 9600 > >>>> exact rate : 9600 (9600/1) > >>>> msbits : 16 > >>>> buffer_size : 2048 > >>>> period_size : 64 > >>>> period_time : 6666 > >>>> tick_time : 4000 > >>>> tstamp_mode : NONE > >>>> period_step : 1 > >>>> sleep_min : 0 > >>>> avail_min : 4 > >>>> xfer_align : 4 > >>>> start_threshold : 2147483647 > >>>> stop_threshold : 2048 > >>>> silence_threshold: 0 > >>>> silence_size : 0 > >>>> boundary : 1073741824 > >>>> Slave: Hardware PCM card 0 'HDA Intel' device 6 > >>> subdevice 0 > >>>> Its setup is: > >>>> stream : CAPTURE > >>>> access : RW_INTERLEAVED > >>>> format : S16_LE > >>>> subformat : STD > >>>> channels : 1 > >>>> rate : 9600 > >>>> exact rate : 9600 (9600/1) > >>>> msbits : 16 > >>>> buffer_size : 2048 > >>>> period_size : 64 > >>>> period_time : 6666 > >>>> tick_time : 4000 > >>>> tstamp_mode : NONE > >>>> period_step : 1 > >>>> sleep_min : 0 > >>>> avail_min : 4 > >>>> xfer_align : 4 > >>>> start_threshold : 2147483647 > >>>> stop_threshold : 2048 > >>>> silence_threshold: 0 > >>>> silence_size : 0 > >>>> boundary : 1073741824 > >>>> <685.175108> main: startup write: 384... > >>>> <685.205145> main: alsa xrun: try to recover... > >>>> <685.226934> main: alsa xrun: recovered. > >>>> <685.226943> main: dev read = 0 > >>>> <685.226951> main: alsa xrun: try to recover... > >>>> <685.250945> main: alsa xrun: recovered. > >>>> <685.250964> main: dev read = 0 > >>>> <685.280918> main: alsa xrun: try to recover... > >>>> <685.302943> main: alsa xrun: recovered. > >>>> <685.302962> main: dev read = 0 > >>>> ... > >>>> [LOOP FOREVER] > >>>> ... > >>>> <686.376013> main: signal 2: mark termination. > >>>> <686.376078> modem:0: modem_delete... > >>>> <686.376085> modem:0: shutdown modem... > >>>> <686.376089> modem:0: modem_stop.. > >>>> <686.376093> main: alsa_stop... > >>>> <686.398870> modem:0: modem set hook: 1 --> 0... > >>>> <686.398889> main: alsa_ioctl: cmd 2, arg 0... > >>>> <686.406905> main: alsa_ioctl: cmd 8, arg 0... > >>>> <686.406928> modem:0: modem set state: 2 --> 1... > >>>> <686.406934> modem:0: new state: MODEM_IDLE > >>>> <686.406947> modem:0: modem report result: 3 (NO > >>> CARRIER) > >>> root@davide-laptop:/home/davide/Desktop/scanModem/SLMODEMD.gcc4.1# > >>>> root@davide-laptop:/home/davide# cat > >>> /etc/wvdial.conf > >>>> [Dialer Defaults] > >>>> Modem = /dev/ttySL0 > >>>> Baud = 56000 > >>>> Init1 = ATZ > >>>> Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 > >>>> Init3 = ATX3 > >>>> Init4 = ATL2 > >>>> SetVolume = 1 > >>>> Dial Command = ATX3DT > >>>> Carrier Check = no > >>>> ;Stupid Mode = yes > >>>> ISDN = 0 > >>>> Modem Type = Analog Modem > >>>> Phone = 7020187187 > >>>> Username = telecom > >>>> Password = telecom > >>>> > >>>> > >>>> root@davide-laptop:/home/davide# wvdial > >>>> WvDial<*1>: WvDial: Internet dialer version 1.56 > >>>> WvModem<*1>: Cannot get information for serial port. > >>>> WvDial<*1>: Initializing modem. > >>>> WvDial<*1>: Sending: ATZ > >>>> WvDial Modem<*1>: ATZ > >>>> WvDial Modem<*1>: OK > >>>> WvDial<*1>: Sending: ATQ0 V1 E1 S0=0 &C1 &D2 > >>> +FCLASS=0 > >>>> WvDial Modem<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 > >>>> WvDial Modem<*1>: OK > >>>> WvDial<*1>: Sending: ATX3 > >>>> WvDial Modem<*1>: ATX3 > >>>> WvDial Modem<*1>: OK > >>>> WvDial<*1>: Sending: ATL2 > >>>> WvDial Modem<*1>: ATL2 > >>>> WvDial Modem<*1>: OK > >>>> WvDial<*1>: Modem initialized. > >>>> WvDial<*1>: Sending: ATX3DT7020187187 > >>>> WvDial<*1>: Waiting for carrier. > >>>> WvDial Modem<*1>: ATX3DT7020187187 > >>>> WvDial Modem<*1>: NO CARRIER > >>>> WvDial<Warn>: No Carrier! Trying again. > >>>> > >>>> > >>>> > >>>> On 1/13/08, Antonio Olivares > >>> <olivares14031@xxxxxxxxx> wrote: > >>>>> Marv, > >>>>> > >>>>> testing with ./scanModem reports > >>>>> > >>>>> Primary PCI_id 8086:284b > >>>>> Subsystem PCI_id 103c:30d8 > >>>>> Softmodem codec or chipset from diagnostics: > >>>>> from Archives: > >>>>> > >>>>> > >>>>> 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: > >>>>> > >>>>> Support can likely be achieved through two > >>> mutually exclusive alternatives: > >>>>> 1) The hsfmodem software for Conexant chipset > >>> modems: Read Conexant.txt > >>>>> The following ALSA alternative CANNOT work with > >>> Conexant modems. > >>>>> 2) An ALSA modem driver plus slmodemd. Read > >>> Smartlink.txt for details, and > >>>>> to test get the package SLMODEMD.gcc4.1.tar.gz > >>> from: > >>> http://linmodems.technion.ac.il/packages/smartlink/ > >>>>> Writing Intel.txt > >>>>> > >>>>> For owners of a Dell PCs with Conexant HSF modems, > >>> a driver source > >>>>> package with full speed enabled is available, but > >>> requires driver > >>>>> compiling. Read Conexant.txt > >>>>> > >>>>> Read Conexant.txt > >>>>> > >>>>> Writing Conexant.txt > >>>>> > >>>>> Writing Smartlink.txt > >>>>> ============ end Smartlink section > >>> ===================== > >>>>> Should Davide get SLMODEMD.gcc4.1.tar.gz? > >>>>> > >>>>> then also take care of his bootup/irq troubles > >>>>>> Modem interrupt assignment and sharing: > >>>>>> 16: 656 IO-APIC-fasteoi > >>> uhci_hcd:usb3, HDA Intel, > >>>>>> i915@pci:0000:00:02.0 > >>>>>> --- Bootup diagnostics for card in PCI slot > >>> 00:1b.0 ---- > >>>>>> [ 14.972000] ACPI: PCI Interrupt > >>> 0000:00:1b.0[A] -> GSI 16 (level, > >>>>>> low) -> IRQ 16 > >>>>>> [ 14.972000] PCI: Setting latency timer of > >>> device 0000:00:1b.0 to 64 > >>>>> Thanks, > >>>>> > >>>>> Antonio > >>>>> > >>>>> On Jan 12, 2008 11:49 AM, Davide Rognoni > >>> <davide.rognoni@xxxxxxxxx> wrote: > >>>>>> Hello, > >>>>>> what's the procedure, please? > >>>>>> > >>>>>> [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.22-14-generic > >>>>>> With this Subject Line cogent experts will be > >>> alerted, and useful > >>>>>> case names left in the Archive. > >>>>>> YourCountry will enable Country specific > >>> guidance. Your contry's > >>>>>> local Linux experts > >>>>>> can be found through: > >>> http://www.linux.org/groups/index.html > >>>>>> 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.22-14-generic (buildd@palmer) > >>> (gcc version 4.1.3 > >>>>>> 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)) > >>> #1 SMP Sun Oct 14 > >>>>>> 23:05:12 GMT 2007 > >>>>>> scanModem update of: 2008_03_01 > >>>>>> > >>>>>> > >>>>>> There are no blacklisted modem drivers in > >>> /etc/modprobe* files > >>>>>> The Advanced Linux Sound Architecture (ALSA) > >>> packages providing audio > >>>>> support, > >>>>>> also includes drivers for some modems. The ALSA > >>> diagnostics are written > >>>>> during > >>>>>> bootup to /proc/asound/ folders. > >>>>>> > >>>>>> > >>>>>> The ALSA verion is 1.0.14 > >>>>>> The modem cards detected by "aplay -l" are: > >>>>>> card 0: Intel [HDA Intel], device 6: Si3054 > >>> Modem [Si3054 Modem] > >>>>>> The /proc/asound/pcm file reports: > >>>>>> ----------------------- > >>>>>> 00-06: Si3054 Modem : Si3054 Modem : playback 1 > >>> : capture 1 > >>>>>> 00-00: AD198x Analog : AD198x Analog : playback > >>> 1 : capture 1 > >>>>>> about /proc/asound/cards: > >>>>>> ------------------------ > >>>>>> 0 [Intel ]: HDA-Intel - HDA Intel > >>>>>> HDA Intel at 0xe4624000 > >>> irq 16 > >>>>>> USB modem not detected by lsusb > >>>>>> > >>>>>> For candidate card in slot 00:1b.0, firmware > >>> information and bootup > >>>>>> diagnostics are: > >>>>>> PCI slot PCI ID SubsystemID > >>> Name > >>>>>> ---------- --------- --------- > >>> -------------- > >>>>>> 00:1b.0 8086:284b 103c:30d8 > >>> Audio device: Intel > >>>>> Corporation 82801H > >>>>>> Modem interrupt assignment and sharing: > >>>>>> 16: 656 IO-APIC-fasteoi > >>> uhci_hcd:usb3, HDA Intel, > >>>>>> i915@pci:0000:00:02.0 > >>>>>> --- Bootup diagnostics for card in PCI slot > >>> 00:1b.0 ---- > >>>>>> [ 14.972000] ACPI: PCI Interrupt > >>> 0000:00:1b.0[A] -> GSI 16 (level, > >>>>>> low) -> IRQ 16 > >>>>>> [ 14.972000] PCI: Setting latency timer of > >>> device 0000:00:1b.0 to 64 > >>>>>> === Finished modem firmware and bootup > >>> diagnostics section. === > >>>>>> === Next deducing cogent software === > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>>> The base of the UDEV device file system is: > >>> /dev/.udev > >>>>>> Versions adequately match for the compiler > >>> installed: 4.1.3 > >>>>>> and the compiler used in kernel > >>> assembly: 4.1.3 > >>>>>> > >>>>>> Minimal compiling resources appear complete: > >>>>>> make utility - /usr/bin/make > >>>>>> Compiler version 4.1 > >>>>>> linuc_headers base folder > >>> /lib/modules/2.6.22-14-generic/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 libc6-dev (and > >>>>>> for Debian/Ubuntu, linux-libc-dev). The also > >>> required headers of > >>>>>> package libc6 are commonly installed by default. > >>>>>> > >>>>>> > >>>>>> > >>>>>> 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 package > >>>>>> 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: > >>>>>> -rwsr-xr-- 1 root dip 269256 2007-10-04 > >>> 21:57 /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) > >>>>>> sudo chmod a+x /usr/sbin/pppd > >>>>>> or under Ubuntu related Linuxes > >>>>>> sudo chmod a+x /usr/sbin/pppd > >>>>>> > >>>>>> Checking settings of: /etc/ppp/options > >>>>>> asyncmap 0 > >>>>>> noauth > >>>>>> crtscts > >>>>>> lock > >>>>>> hide-password > >>>>>> modem > >>>>>> proxyarp > >>>>>> lcp-echo-interval 30 > >>>>>> lcp-echo-failure 4 > >>>>>> noipx > >>>>>> > >>>>>> 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/YourSystem.txt concerning other COMM > >>> channels: eth0 > >>>>>> Which can interfere with Browser naviagation. > >>>>>> > >>>>>> 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: > >>>>>> slmodemd created symbolic link /dev/ttySL0: > >>>>>> Within /etc/udev/ files: > >>>>>> > >>>>>> Within /etc/modprobe.conf files: > >>>>>> /etc/modprobe.d/alsa-base:options > >>> snd-atiixp-modem index=-2 > >>>>>> /etc/modprobe.d/alsa-base:options > >>> snd-via82xx-modem index=-2 > >>>>>> /etc/modprobe.d/blacklist-modem:# Uncomment > >>> these entries in order to > >>>>>> blacklist unwanted modem drivers > >>>>>> /etc/modprobe.d/blacklist-modem:# blacklist > >>> snd-atiixp-modem > >>>>>> /etc/modprobe.d/blacklist-modem:# blacklist > >>> snd-via82xx-modem > >>>>>> Within any ancient /etc/devfs files: > >>>>>> > >>>>>> Within ancient kernel 2.4.n > >>> /etc/module.conf files: > >>>>>> --------- end modem support lines -------- > >>>>>> > >>> > >>> > >>> > >>> > >> ____________________________________________________________________________________ > >>> Never miss a thing. Make Yahoo your home page. > >>> http://www.yahoo.com/r/hs >