Anita RE: accepted location for compiling. You could also have worked in your personal /home/User/ folder. But the / folder on any folder with SYSTEm files should not be used. WHAT=something are created in memory space, and can be called/used from any folder. They can be displayed by: $ echo $WHAT WHAT=something Do a precautionary (assuming LoginName is anita) $ sudo chown -R anita:anita /usr/src/modules Then try the configure command again. Output on my SYstem is shown below If there is a failure, what is the output of $ ls -l /usr/bin/gcc* MarvS ------------------------------------------- marv@marvdesk:/usr/src/modules/alsa-1.0.15/alsa-driver-1.0.15$ ./configure --with-kernel=$HEADERS --with-build=$HEADERS --with-cards=hda-intel checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking for ranlib... ranlib checking for a BSD-compatible install... /usr/bin/install -c checking how to run the C preprocessor... gcc -E checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking for an ANSI C-conforming const... yes checking for inline... inline checking whether time.h and sys/time.h may both be included... yes checking whether gcc needs -traditional... no checking for current directory... /usr/src/modules/alsa-1.0.15/alsa-driver-1.0.15 checking cross compile... checking for directory with kernel source... /lib/modules/2.6.22-14-generic/build checking for directory with kernel build... /lib/modules/2.6.22-14-generic/build checking for kernel linux/version.h... yes checking for kernel linux/autoconf.h... yes checking for kernel version... 2.6.22-14-generic checking for GCC version... Kernel compiler: Used compiler: gcc (GCC) 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2) checking for built-in ALSA... no checking for existing ALSA module... yes checking for Red Hat kernel... auto checking for Red Hat kernel... no checking for SUSE kernel... auto checking for SUSE kernel... no checking for CONFIG_EXPERIMENTAL... yes checking for kernel linux/config.h... no Creating <linux/config.h>... checking to modify of kernel linux/kmod.h... no checking for kernel linux/utsrelease.h... yes checking for kernel linux/compiler.h... yes checking for kernel linux/pm.h... yes checking for kernel linux/spinlock.h... yes checking for kernel linux/irq.h... yes checking for kernel linux/threads.h... yes checking for kernel linux/rwsem.h... yes checking for kernel linux/gameport.h... yes checking for kernel media/v4l2-dev.h... yes checking for kernel linux/devfs_fs_kernel.h... no Creating a dummy <linux/devfs_fs_kernel.h>... checking for kernel linux/highmem.h... yes checking for kernel linux/workqueue.h... yes checking for kernel linux/dma-mapping.h... yes checking for kernel asm/hw_irq.h... yes checking for kernel linux/device.h... yes checking for kernel linux/platform_device.h... yes checking for kernel linux/isa.h... yes checking for kernel linux/jiffies.h... yes checking for kernel linux/compat.h... yes checking for kernel linux/log2.h... yes checking for kernel linux/adb.h... yes checking for kernel linux/cuda.h... yes checking for kernel linux/pmu.h... yes checking for kernel linux/moduleparam.h... yes checking for kernel linux/syscalls.h... yes checking for kernel linux/firmware.h... yes checking for kernel linux/err.h... yes checking for kernel linux/bitmap.h... yes checking for kernel linux/mutex.h... yes checking for kernel linux/latency.h... yes checking for kernel linux/kthread.h... yes checking for kernel asm/irq_regs.h... yes checking for kernel module symbol versions... yes checking for has ioport support... yes checking for PCI support in kernel... yes checking for I2C driver in kernel... module checking for I2C_POWERMAC in kernel... unknown checking for firmware loader... yes checking for input subsystem in kernel... yes checking for directory to store kernel modules... /lib/modules/2.6.22-14-generic/kernel/sound checking for verbose procfs... on checking for verbose printk... on checking for debug level... none checking for ISA support in kernel... yes checking for processor type... i586 checking for i386 machine type... default checking for ISA DMA API... yes checking for SMP... yes checking for Video device support in kernel... yes checking for ISA PnP driver in kernel... yes checking for PnP driver in kernel... yes checking for Kernel ISA-PnP support... yes checking for strlcpy... yes checking for snprintf... yes checking for vsnprintf... yes checking for scnprintf... yes checking for sscanf... yes checking for vmalloc_to_page... yes checking for old kmod... no checking for PDE... yes checking for pci_set_consistent_dma_mask... yes checking for pci_dev_present... yes checking for msleep... yes checking for msleep_interrupt... yes checking for msecs_to_jiffies... yes checking for tty->count is the atomic type... no checking for video_get_drvdata... yes checking for V4L1 layer... yes checking for io_remap_pfn_range... yes checking for kcalloc... yes checking for kstrdup... yes checking for kzalloc... yes checking for create_workqueue with flags... no checking for saved_config_space in pci_dev... yes checking for new pci_save_state... yes checking for register_sound_special_device... yes checking for driver version... 1.0.15 checking for sequencer support... yes checking for OSS/Free emulation... yes checking for OSS PCM plugin system inclusion... yes checking for RTC callback support in kernel... yes checking for HPET support... yes checking for dynamic minor numbers... no checking for support of old API... yes checking for Procfs support... yes checking for USB support... yes checking for class_simple... no checking for old driver suspend/resume callbacks... no checking for removal of page-reservation for nopage/mmap... yes checking for nested class_device... yes checking for new IRQ handler... yes checking for gfp_t... yes checking for PnP suspend/resume... yes checking for new unlocked/compat_ioctl... yes checking for x86-compatible PC... yes checking for High-Res timers... yes checking for kernel PCMCIA checking for PCMCIA support... yes checking for PC9800 support in kernel... no checking for parallel port support... yes checking for power management... yes checking for which soundcards to compile driver for... hda-intel configure: creating ./config.status config.status: creating version config.status: creating Makefile.conf config.status: WARNING: Makefile.conf.in seems to ignore the --datarootdir setting config.status: creating snddevices config.status: creating utils/alsa-driver.spec config.status: creating utils/buildrpm config.status: creating toplevel.config config.status: creating utils/alsasound config.status: creating utils/alsasound.posix config.status: creating include/pci_ids_compat.h config.status: creating include/i2c-id_compat.h config.status: creating include/config.h config.status: creating include/config1.h config.status: creating include/version.h config.status: include/version.h is unchanged config.status: creating include/autoconf-extra.h config.status: include/autoconf-extra.h is unchanged Hacking autoconf.h... marv@marvdesk:/usr/src/modules/alsa-1.0.15/alsa-driver-1.0.15$ On Sat, Mar 8, 2008 at 12:22 PM, Anita Kuno <ay.kuno@xxxxxxxxx> wrote: > Thank you, Marvin for providing me with the information about the > accepted location for compiling. > Your email was the first I had heard of it. > > I see that in this email the creation of HEADERS takes place within the > alsa-driver-1.0.16 directory, > whereas yesterday your email stated that I should create HEADERS whilst > in the alsa folder and then move into > the alsa-driver-1.0.16 directory. Since it is referencing an absolute > path, I am assuming that the location where > it is created is not of much importance, but I did notice a difference. > > You will find a terminal log from my latest attempt attached. I didn't > bother with the config.log > this time, but if that is of importance, I can include that as well next > time. > > > > Thanks, > Anita. > > > > Marvin Stodolsky wrote: > > Anita, > > Uninstall the sl-modem-daemon package. It only provides some automation. > > It is Not useful for your HDA modem at this stage and will only confuse issues. > > > > Your problem below is that you are trying to work in the root "/" > > partition and that is illegal under Unix/Linux > > The standard position for compiling stuff is in sub-folders of > > /usr/src/modules. So > > $ sudo mkdir -p /usr/src/modules > > $ sudo mv /alsa /usr/src/modules/ > > $ chown -R anita:anita /usr/src/modules > > gives anita to work therein without "sudo" > > $ cd /usr/src/modules/alsa/ alsa-driver-1.0.16/ > > $ HEADERS=/lib/modules/2.6.20-15-generic/build > > $ ./configure --with-kernel=$HEADERS --with-build=$HEADERS > > --with-cards=hda-intel > > will not have file creation problems now. > > > > Just beginners problems. > > > > MarvS > > > > On Fri, Mar 7, 2008 at 2:09 PM, Anita Kuno <ay.kuno@xxxxxxxxx> wrote: > > > >> So a number of people are asking me if I have sl-modem-daemon. > >> > >> And I didn't know. So it was suggested I run: > >> apt-cache policy sl-modem-daemon > >> > >> So I did: > >> /$ apt-cache policy sl-modem-daemon > >> W: Unable to locate package sl-modem-daemon > >> > >> So others seem to feel this is an important piece of information. > >> > >> How do people on this list feel? > >> > >> > >> > >> Thanks, > >> Anita. > >> > >> > >> > >> > >> > >> Marvin Stodolsky wrote: > >> > Anita, > >> > > >> > Looks like the long form of the configure command is necessary > >> > Make a useful definition: > >> > $ HEADERS=/lib/modules/2.6.20-15-generic/build > >> > > >> > Check for validity with: > >> > $ ls $HEADERS > >> > should show files like: > >> > arch include lib scripts > >> > block init Makefile security > >> > crypto ipc mm sound > >> > drivers fs kernel net usr > >> > ---------------- > >> > This definition does not survive a shutdown and must be redone upon reboot, > >> > when a new driver compiling is necessary. > >> > > >> > To compile the driver set, move into the driver folder: > >> > $ cd alsa-driver-1.0.16 > >> > > >> > Do the configuration with with the following command on ONE LINE: > >> > $ ./configure --with-kernel=$HEADERS --with-build=$HEADERS > >> > --with-cards=hda-intel > >> > > >> > On Fri, Mar 7, 2008 at 1:00 AM, Anita Kuno <ay.kuno@xxxxxxxxx> wrote: > >> > > >> >> $ mkdir alsa #worked > >> >> $ cd alsa #worked > >> >> > >> >> unpack with ( ../ means the next higher folder) > >> >> $ tar jxf ../alsa-*.tar.bz2 #had to sudo and unpack one at a time but done > >> >> > >> >> which will unpack both packages. Move into the driver folder > >> >> $ cd alsa-driver-1.0.16 > >> >> Browsen a bit, then do > >> >> $ ./configure --with-cards=hda-intel > >> >> > >> >> Got this far. The config.log is attached. It is very big. > >> >> > >> >> Thanks for all the help. > >> >> > >> >> > >> >> > >> >> Anita. > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> Marvin Stodolsky wrote: > >> >> > Anita, > >> >> > > >> >> > RE: If I may be so bold as to collaborate on this effort, I noticed the > >> >> > following lines in the logfile: > >> >> > <102.812335> open file: /var/lib/slmodem/data.hw:0,6... > >> >> > <102.812400> cannot open '/var/lib/slmodem/data.hw:0,6': No such file or > >> >> > directory > >> >> > ------------- > >> >> > This is seen also with functioning modems and is not important. > >> >> > > >> >> > The outstanding problem begins here: > >> >> > <124.211995> main: alsa_start... > >> >> > error: cannot setup hw params for playback: Invalid argument > >> >> > <124.212186> err: hw:0,6: modem start = -22: cannot start device. > >> >> > <124.212210> hw:0,6: modem_stop.. > >> >> > > >> >> > All you have done is technically correct. The next thing to try is > >> >> > upgrading snd-hda-intel and its dependent driver set. Give a first > >> >> > read to the example > >> >> > http://linmodems.technion.ac.il/archive-seventh/msg00282.html > >> >> > > >> >> > You will need to download from > >> >> > http://www.alsa-project.org/main/index.php/Main_Page > >> >> > The packages alsa-driver-1.0.16 and alsa-lib-1.0.16 > >> >> > $ mkdir alsa > >> >> > $ cd alsa > >> >> > unpack with ( ../ means the next higher folder) > >> >> > $ tar jxf ../alsa-*.tar.bz2 > >> >> > which will unpack both packages. Move into the driver folder > >> >> > $ cd alsa-driver-1.0.16 > >> >> > Browsen a bit, then do > >> >> > $ ./configure --with-cards=hda-intel > >> >> > If the configuration is successful, the driver set will be compiled with: > >> >> > $ make > >> >> > Get some coffee, this will take a while > >> >> > Do nothing in the alsa-lib-1.0.16/ folder. But it is used during the compile. > >> >> > > >> >> > The new driver set is displayed by: > >> >> > $ ls modules > >> >> > and installed by > >> >> > $ sudo make install > >> >> > > >> >> > THen reboot and retest the modem > >> >> > > >> >> > MarvS > >> >> > > >> >> > > >> >> > > >> >> > > >> >> > On Thu, Mar 6, 2008 at 10:10 PM, Anita Kuno <ay.kuno@xxxxxxxxx> wrote: > >> >> > > >> >> >> Some excellent diagnostic questions, thank you. > >> >> >> > >> >> >> I am dual booted. The modem/phone-line combination, that you are > >> >> >> helping to make work with feisty, is the same one that I am using to > >> >> >> communicate with you now. > >> >> >> > >> >> >> I am attaching the logfile. It is wordy. > >> >> >> > >> >> >> If I may be so bold as to collaborate on this effort, I noticed the > >> >> >> following lines in the logfile: > >> >> >> <102.812335> open file: /var/lib/slmodem/data.hw:0,6... > >> >> >> <102.812400> cannot open '/var/lib/slmodem/data.hw:0,6': No such file or > >> >> >> directory > >> >> >> > >> >> >> So I went looking for /var/lib/slmodem/data.hw:0,6 and I couldn't find it. > >> >> >> anita@anitas-computer:~$ cd / > >> >> >> anita@anitas-computer:/$ cd /var/lib > >> >> >> anita@anitas-computer:/var/lib$ ls > >> >> >> acpi-support dhcp3 logrotate synaptic > >> >> >> alsa dictionaries-common misc ucf > >> >> >> apt doc-base mozilla-firefox update-manager > >> >> >> aptitude dpkg mozilla-thunderbird update-notifier > >> >> >> aspell gcj-4.1 NetworkManager urandom > >> >> >> avahi-autoipd gconf python-support vim > >> >> >> belocs gdm scrollkeeper x11 > >> >> >> binfmts gstreamer security xkb > >> >> >> bittorrent initramfs-tools sgml-base xml-core > >> >> >> dbus initscripts slocate > >> >> >> defoma locales snmp > >> >> >> anita@anitas-computer:/var/lib$ > >> >> >> > >> >> >> So what step was supposed to create a directory and file in /var/lib ? > >> >> >> It seems that step did not have the expected result. > >> >> >> Or perhaps I am wrong? > >> >> >> > >> >> >> Thanks, > >> >> >> > >> >> >> > >> >> >> Anita. > >> >> >> > >> >> >> Marvin Stodolsky wrote: > >> >> >> > Anita, > >> >> >> > First, can you verify that your phone is Touch Tone dial rather than > >> >> >> > the older PULSE type? > >> >> >> > 2) Make sure an ordinary phone dials out on the line you are using, or > >> >> >> > that the modem works under Microsoft. > >> >> >> > > >> >> >> > 3) use the following setup > >> >> >> > $ sudo slmodemd -c CANADA -a --debug=2 --log hw:0,6 > >> >> >> > > >> >> >> > Then in the 2nd console the usual > >> >> >> > $ sudo wvdial > >> >> >> > > >> >> >> > After the failure, send us the generated logfile > >> >> >> > > >> >> >> > MarvS > >> >> >> > > >> >> >> > > >> >> >> > On Thu, Mar 6, 2008 at 9:10 PM, Anita Kuno <ay.kuno@xxxxxxxxx> wrote: > >> >> >> > > >> >> >> >> Thank you for the suggestion, Marvin. > >> >> >> >> > >> >> >> >> I tried this: > >> >> >> >> > >> >> >> >> [Dialer Defaults] > >> >> >> >> Init1 = ATZ > >> >> >> >> Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 > >> >> >> >> Modem Type = Analog Modem > >> >> >> >> Baud = 460800 > >> >> >> >> Modem = /dev/ttySL0 > >> >> >> >> ISDN = 0 > >> >> >> >> Phone = 7054579564 > >> >> >> >> Password = XXXXXXXX #protected for the purpose of the email > >> >> >> >> Username = XXXXXXXX #protected for the purpose of the email > >> >> >> >> Carrier Check = no > >> >> >> >> > >> >> >> >> And got this: > >> >> >> >> > >> >> >> >> anita@anitas-computer:~$ sudo wvdial > >> >> >> >> > >> >> >> >> --> WvDial: Internet dialer version 1.56 > >> >> >> >> --> 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: ATDT7054579564 > >> >> >> >> --> Waiting for carrier. > >> >> >> >> ATDT7054579564 > >> >> >> >> NO CARRIER > >> >> >> >> ERROR > >> >> >> >> > >> >> >> >> So then I tried this: > >> >> >> >> > >> >> >> >> [Dialer Defaults] > >> >> >> >> Init1 = ATZ > >> >> >> >> Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 > >> >> >> >> Modem Type = Analog Modem > >> >> >> >> Baud = 460800 > >> >> >> >> Modem = /dev/ttySL0 > >> >> >> >> ISDN = 0 > >> >> >> >> Phone = 7054579564 > >> >> >> >> Password = XXXXXXXX > >> >> >> >> Username = XXXXXXXX@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx #this > >> >> >> >> information I obtained by logging into irc and evaluating my personal > >> >> >> >> information. Thought I would give it a try. > >> >> >> >> Carrier Check = no > >> >> >> >> > >> >> >> >> And I got this: > >> >> >> >> > >> >> >> >> anita@anitas-computer:~$ sudo wvdial > >> >> >> >> > >> >> >> >> --> WvDial: Internet dialer version 1.56 > >> >> >> >> --> 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: ATDT7054579564 > >> >> >> >> --> Waiting for carrier. > >> >> >> >> ATDT7054579564 > >> >> >> >> NO CARRIER > >> >> >> >> ERROR > >> >> >> >> > >> >> >> >> What should I try next? > >> >> >> >> > >> >> >> >> Thank you, > >> >> >> >> Anita. > >> >> >> >> > >> >> >> >> > >> >> >> >> > >> >> >> >> > >> >> >> >> > >> >> >> >> Marvin Stodolsky wrote: > >> >> >> >> > Anita, > >> >> >> >> > Add a line to /etc/wvdial.conf > >> >> >> >> > Carrier Check = no > >> >> >> >> > and then retest as before. This line is necessary, because /dev/pts/N > >> >> >> >> > ports do not yet have "sound hearing" capability and hence cannot hear > >> >> >> >> > the Carrier signal. > >> >> >> >> > > >> >> >> >> > MarvS > >> >> >> >> > > >> >> >> >> > On Thu, Mar 6, 2008 at 4:33 PM, Anita Kuno <ay.kuno@xxxxxxxxx> wrote: > >> >> >> >> > > >> >> >> >> >> Thank you, Jacques, I did figure out that my problem from my last post > >> >> >> >> >> was that I had not configured the file by calling wvdialconf. Thank you > >> >> >> >> >> for your clarity. > >> >> >> >> >> > >> >> >> >> >> So after running wvdialconf, I configured the file as follows: > >> >> >> >> >> > >> >> >> >> >> [Dialer Defaults] > >> >> >> >> >> Init1 = ATZ > >> >> >> >> >> Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 > >> >> >> >> >> Modem Type = Analog Modem > >> >> >> >> >> Baud = 460800 > >> >> >> >> >> > >> >> >> >> >> Modem = /dev/ttySL0 > >> >> >> >> >> ISDN = 0 > >> >> >> >> >> Phone = 7054579564 > >> >> >> >> >> Password = XXXXXXXX #hidden for the purpose of this email > >> >> >> >> >> Username = XXXXXXXX #hidden for the purpose of this email > >> >> >> >> >> > >> >> >> >> >> And ran sudo wvdial: > >> >> >> >> >> $ sudo wvdial > >> >> >> >> >> > >> >> >> >> >> --> WvDial: Internet dialer version 1.56 > >> >> >> >> >> --> 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: ATDT7054579564 > >> >> >> >> >> --> Waiting for carrier. > >> >> >> >> >> ATDT7054579564 > >> >> >> >> >> NO CARRIER > >> >> >> >> >> ERROR > >> >> >> >> >> --> No Carrier! Trying again. > >> >> >> >> >> --> Sending: ATDT7054579564 > >> >> >> >> >> --> Waiting for carrier. > >> >> >> >> >> ATDT7054579564 > >> >> >> >> >> NO CARRIER > >> >> >> >> >> > >> >> >> >> >> So, NO CARRIER. What is it looking for and how do I give it what it wants? > >> >> >> >> >> > >> >> >> >> >> > >> >> >> >> >> Thanks, > >> >> >> >> >> Anita. > >> >> >> >> >> > >> >> >> >> >> > >> >> >> >> >> Jacques Goldberg wrote: > >> >> >> >> >> > Again > >> >> >> >> >> > > >> >> >> >> >> > 1-In one window, sudo slmodemd etc... > >> >> >> >> >> > 2-In an other window, sudo wvdialconf /etc/wvdial.conf > >> >> >> >> >> > Instead, you did sudo wvdial /etc/wvdial.conf > >> >> >> >> >> > but wvdialconf and wvdial are NOT the same thing. These are two > >> >> >> >> >> > DIFFERENT commands. One configures the modem once for all, the other, > >> >> >> >> >> > wvdial , makes the connection > >> >> >> >> >> > > >> >> >> >> >> > You must run wvdialconf as shown, at least ONCE, while slmodemd IS > >> >> >> >> >> > running > >> >> >> >> >> > wvdialconf will find your modem > >> >> >> >> >> > Edit the file /etc/wvdial.conf (username, password, phone . Remove > >> >> >> >> >> > leading ; and < > containers and replace parameter in container by > >> >> >> >> >> > value given to you by your ISP ) > >> >> >> >> >> > > >> >> >> >> >> > Only NOW can you try, as many times as you like sudo wvdial > >> >> >> >> >> > and note, NOT sudo wvdial /etc/wvdial.conf , just sudo wvdial > >> >> >> >> >> > wvdial knows that it has to use /etc/wvdial.conf > >> >> >> >> >> > > >> >> >> >> >> > And just to make sure: slmodemd MUST also be running while you try > >> >> >> >> >> > wvdial > >> >> >> >> >> > >> >> >> >> >> > >> >> >> >> >> > >> >> >> >> >> > Jacques > >> >> >> >> >> > > >> >> >> >> >> > Anita Kuno wrote: > >> >> >> >> >> >> Thank you, Jacques, you are entirely correct. I do not understand > >> >> >> >> >> >> the procedure. > >> >> >> >> >> >> > >> >> >> >> >> >> However, when I sent > >> >> >> >> >> >> Results from second terminal with first terminal running slmodemd: > >> >> >> >> >> >> that was my way of saying that I had done the first step as you > >> >> >> >> >> >> outlined: > >> >> >> >> >> >> 1-In one window, you start slmodemd and DO NOT STOP IT > >> >> >> >> >> >> > >> >> >> >> >> >> And when I also submitted: > >> >> >> >> >> >> anita@anitas-computer:~$ sudo wvdial /etc/wvdial.conf > >> >> >> >> >> >> Password: > >> >> >> >> >> >> --> WvDial: Internet dialer version 1.56 > >> >> >> >> >> >> --> Warning: section [Dialer /etc/wvdial.conf] does not exist in > >> >> >> >> >> >> wvdial.conf. > >> >> >> >> >> >> --> Cannot open /dev/modem: No such file or directory > >> >> >> >> >> >> --> Cannot open /dev/modem: No such file or directory > >> >> >> >> >> >> --> Cannot open /dev/modem: No such file or directory > >> >> >> >> >> >> > >> >> >> >> >> >> That was my way of demonstrating that I had: > >> >> >> >> >> >> 2-In an other window you start > >> >> >> >> >> >> sudo wvdialconf /etc/wvdial./.conf > >> >> >> >> >> >> > >> >> >> >> >> >> And I was hoping for: > >> >> >> >> >> >> which should find your modem > >> >> >> >> >> >> > >> >> >> >> >> >> And perhaps I mis-interpreted the result, but when I read: > >> >> >> >> >> >> --> Warning: section [Dialer /etc/wvdial.conf] does not exist in > >> >> >> >> >> >> wvdial.conf. > >> >> >> >> >> >> --> Cannot open /dev/modem: No such file or directory > >> >> >> >> >> >> --> Cannot open /dev/modem: No such file or directory > >> >> >> >> >> >> --> Cannot open /dev/modem: No such file or directory > >> >> >> >> >> >> I took that to mean that it couldn't find the modem. > >> >> >> >> >> >> > >> >> >> >> >> >> So I am wondering how to find the modem. > >> >> >> >> >> >> > >> >> >> >> >> >> Thanks, > >> >> >> >> >> >> Anita. > >> >> >> >> >> >> > >> >> >> >> >> >> > >> >> >> >> >> >> > >> >> >> >> >> >> > >> >> >> >> >> >> Jacques Goldberg wrote: > >> >> >> >> >> >>> I believe that you do not understand the procedure > >> >> >> >> >> >>> > >> >> >> >> >> >>> 1-In one window, you start slmodemd and DO NOT STOP IT > >> >> >> >> >> >>> 2-In an other window you start > >> >> >> >> >> >>> sudo wvdialconf /etc/wvdial./.conf > >> >> >> >> >> >>> which should find your modem > >> >> >> >> >> >>> When wvdialconf exits and has found a modem, you EDIT > >> >> >> >> >> >>> the file /etc/wvdial.conf to set username, password, phone > >> >> >> >> >> >>> as in > >> >> >> >> >> >>> username = tartempion > >> >> >> >> >> >>> phone = 0123456788 > >> >> >> >> >> >>> password = sunday_times > >> >> >> >> >> >>> After editing, you start wvdial as > >> >> >> >> >> >>> sudo wvdial > >> >> >> >> >> >>> and you do NOT stop wvdial until you want to close the phone call. > >> >> >> >> >> >>> You cannot use these two windows for anything else until you have > >> >> >> >> >> >>> ended wvdial and slmodemd > >> >> >> >> >> >>> > >> >> >> >> >> >>> Jacques > >> >> >> >> >> >>> > >> >> >> >> >> >>> Anita Kuno wrote: > >> >> >> >> >> >>>> Thank you Marvin and Antonio, > >> >> >> >> >> >>>> > >> >> >> >> >> >>>> Results from second terminal with first terminal running slmodemd: > >> >> >> >> >> >>>> > >> >> >> >> >> >>>> anita@anitas-computer:~$ sudo wvdial /etc/wvdial.conf > >> >> >> >> >> >>>> Password: > >> >> >> >> >> >>>> --> WvDial: Internet dialer version 1.56 > >> >> >> >> >> >>>> --> Warning: section [Dialer /etc/wvdial.conf] does not exist in > >> >> >> >> >> >>>> wvdial.conf. > >> >> >> >> >> >>>> --> Cannot open /dev/modem: No such file or directory > >> >> >> >> >> >>>> --> Cannot open /dev/modem: No such file or directory > >> >> >> >> >> >>>> --> Cannot open /dev/modem: No such file or directory > >> >> >> >> >> >>>> anita@anitas-computer:~$ > >> >> >> >> >> >>>> > >> >> >> >> >> >>>> > >> >> >> >> >> >>>> Marvin Stodolsky wrote: > >> >> >> >> >> >>>>> Anita, > >> >> >> >> >> >>>>> > >> >> >> >> >> >>>>> Just to clarify on Antonio's terse comment. > >> >> >> >> >> >>>>> After the successful: > >> >> >> >> >> >>>>> $ sudo slmodemd -c CANADA --alsa hw:0,6 > >> >> >> >> >> >>>>> leave slmodemd running. > >> >> >> >> >> >>>>> Open a 2nd console or new TAB on the same one and run the > >> >> >> >> >> >>>>> $ sudo wvdialconf /etc/wvdial.conf > >> >> >> >> >> >>>>> If this step succeeds: > >> >> >> >> >> >>>>> $ sudo gedit /etc/wvdial.conf > >> >> >> >> >> >>>>> and edit to a format like that below. > >> >> >> >> >> >>>>> > >> >> >> >> >> >>>>> Afterward with slmodemd still running, try a dialout with: > >> >> >> >> >> >>>>> $ sudo wvdial > >> >> >> >> >> >>>>> > >> >> >> >> >> >>>>> Please report back to the List, not to me directly: > >> >> >> >> >> >>>>> > >> >> >> >> >> >>>>> MarvS > >> >> >> >> >> >>>>> ----------------- > >> >> >> >> >> >>>>> [Dialer Defaults] > >> >> >> >> >> >>>>> Init1 = ATZ > >> >> >> >> >> >>>>> Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 > >> >> >> >> >> >>>>> Modem Type = Analog Modem > >> >> >> >> >> >>>>> Baud = 460800 > >> >> >> >> >> >>>>> New PPPD = yes > >> >> >> >> >> >>>>> Modem = /dev/ttySL0 > >> >> >> >> >> >>>>> ISDN = 0 > >> >> >> >> >> >>>>> Password = YourPassword > >> >> >> >> >> >>>>> Username = LoginName@xxxxxxxxxxxxxxxx > >> >> >> >> >> >>>>> Phone = 3015560020 > >> >> >> >> >> >>>>> # needed for usage with /dev/pts/N ports: > >> >> >> >> >> >>>>> Carrier Check = no > >> >> >> >> >> >>>>> > >> >> >> >> >> >>>>> > >> >> >> >> >> >>>>> > >> >> >> >> >> >>>>> > >> >> >> >> >> >>>>> On Wed, Mar 5, 2008 at 7:38 PM, Antonio Olivares > >> >> >> >> >> >>>>> <olivares14031@xxxxxxxxx> wrote: > >> >> >> >> >> >>>>> > >> >> >> >> >> >>>>>> When you did this > >> >> >> >> >> >>>>>> > >> >> >> >> >> >>>>>> > >> >> >> >> >> >>>>>> $ sudo slmodemd -c CANADA --alsa hw:0,6 > >> >> >> >> >> >>>>>> => SmartLink Soft Modem: version 2.9.11 Feb 17 2008 09:31:10 > >> >> >> >> >> >>>>>> => symbolic link `/dev/ttySL0' -> `/dev/pts/1' created. > >> >> >> >> >> >>>>>> => modem `hw:0,6' created. TTY is `/dev/pts/1' > >> >> >> >> >> >>>>>> =>Use `/dev/ttySL0' as modem device, Ctrl+C for termination. > >> >> >> >> >> >>>>>> > >> >> >> >> >> >>>>>> Did you CTRL+C to do sudo wvdialconf /etc/wvdial.conf ? > >> >> >> >> >> >>>>>> > >> >> >> >> >> >>>>>> open up another terminal or session and then type > >> >> >> >> >> >>>>>> > >> >> >> >> >> >>>>>> > >> >> >> >> >> >>>>>> $ sudo wvdialconf /etc/wvdial.conf > >> >> >> >> >> >>>>>> > >> >> >> >> >> >>>>>> That should find your modem, and get you setup. Please report > >> >> >> >> >> >>>>>> back if > >> >> >> >> >> >>>>>> you have trouble/questions. > >> >> >> >> >> >>>>>> > >> >> >> >> >> >>>>>> Regards, > >> >> >> >> >> >>>>>> > >> >> >> >> >> >>>>>> Antonio > >> >> >> >> >> >>>>>> > >> >> >> >> >> >>>>>> > >> >> >> >> >> >>>>>> > >> >> >> >> >> >>>>>> On 3/5/08, Anita Kuno <ay.kuno@xxxxxxxxx> wrote: > >> >> >> >> >> >>>>>> > I have unpacked SLMODEMD: > >> >> >> >> >> >>>>>> > $ tar -zxvf ./SLMODEMD.gcc4.1.tar.gz > >> >> >> >> >> >>>>>> > > >> >> >> >> >> >>>>>> > And I believe this makes SLMODEMD an executable file: > >> >> >> >> >> >>>>>> > $ chmod +x slmodemd > >> >> >> >> >> >>>>>> > $ sudo cp slmodemd /usr/sbin > >> >> >> >> >> >>>>>> > > >> >> >> >> >> >>>>>> > And I think this verifies the location: > >> >> >> >> >> >>>>>> > $ find /usr -name slmodemd > >> >> >> >> >> >>>>>> > => /usr/sbin/slmodemd > >> >> >> >> >> >>>>>> > > >> >> >> >> >> >>>>>> > So then I installed SLMODEMD: > >> >> >> >> >> >>>>>> > $ sudo slmodemd -c CANADA --alsa hw:0,6 > >> >> >> >> >> >>>>>> > => SmartLink Soft Modem: version 2.9.11 Feb 17 2008 09:31:10 > >> >> >> >> >> >>>>>> > => symbolic link `/dev/ttySL0' -> `/dev/pts/1' created. > >> >> >> >> >> >>>>>> > => modem `hw:0,6' created. TTY is `/dev/pts/1' > >> >> >> >> >> >>>>>> > =>Use `/dev/ttySL0' as modem device, Ctrl+C for termination. > >> >> >> >> >> >>>>>> > > >> >> >> >> >> >>>>>> > So then I worked on wvdial. > >> >> >> >> >> >>>>>> > $ which wvdial > >> >> >> >> >> >>>>>> > => /usr/bin/wvdial > >> >> >> >> >> >>>>>> > $ sudo wvdialconf /etc/wvdial.conf > >> >> >> >> >> >>>>>> > =>Editing `/etc/wvdial.conf'. > >> >> >> >> >> >>>>>> > => Scanning your serial ports for a modem. > >> >> >> >> >> >>>>>> > => Modem Port Scan<*1>: S0 S1 S2 S3 > >> >> >> >> >> >>>>>> > => Sorry, no modem was detected! Is it in use by another > >> >> >> >> >> >>>>>> program? > >> >> >> >> >> >>>>>> > => Did you configure it properly with setserial? > >> >> >> >> >> >>>>>> > => Please read the FAQ at http://open.nit.ca/wiki/?WvDial > >> >> >> >> >> >>>>>> > => If you still have problems, send mail to > >> >> >> >> >> >>>>>> <wvdial-list@xxxxxxxxxxxx>. > >> >> >> >> >> >>>>>> > > >> >> >> >> >> >>>>>> > I have tried the url to find the FAQ, can't find it. > >> >> >> >> >> >>>>>> > And I have emailed them to ask for the FAQ url, no response. > >> >> >> >> >> >>>>>> > > >> >> >> >> >> >>>>>> > So I have evaluated the sound card: > >> >> >> >> >> >>>>>> > $ cat /proc/asound/cards > >> >> >> >> >> >>>>>> > => 0 [Intel ]: HDA-Intel - HDA Intel > >> >> >> >> >> >>>>>> > => HDA Intel at 0xd8240000 irq 21 > >> >> >> >> >> >>>>>> > > >> >> >> >> >> >>>>>> > And run uname: > >> >> >> >> >> >>>>>> > $ uname -a > >> >> >> >> >> >>>>>> > Linux anitas-computer 2.6.20-15-generic #2 SMP Sun Apr 15 > >> >> >> >> >> >>>>>> 07:36:31 UTC > >> >> >> >> >> >>>>>> > 2007 i686 GNU/Linux > >> >> >> >> >> >>>>>> > > >> >> >> >> >> >>>>>> > And confirmed module-init-tools: > >> >> >> >> >> >>>>>> > $ dpkg -s module-init-tools > >> >> >> >> >> >>>>>> > => Package: module-init-tools > >> >> >> >> >> >>>>>> > => Status: install ok installed > >> >> >> >> >> >>>>>> > > >> >> >> >> >> >>>>>> > What is my next step? > >> >> >> >> >> >>>>>> > > >> >> >> >> >> >>>>>> > Thank you, > >> >> >> >> >> >>>>>> > Anita. > >> >> >> >> >> >>>>>> > > >> >> >> >> >> >>>>>> > > >> >> >> >> >> >>>>>> > > >> >> >> >> >> >>>>>> > > >> >> >> >> >> >>>>>> > > >> >> >> >> >> >>>>>> > >> >> >> >> >> >>>>>> > >> >> >> >> >> >>>>> > >> >> >> >> >> >>>>> > >> >> >> >> >> >>>> > >> >> >> >> >> >>> > >> >> >> >> >> >> > >> >> >> >> >> > > >> >> >> >> >> > >> >> >> >> >> > >> >> >> >> >> > >> >> >> >> > > >> >> >> >> > > >> >> >> >> > >> >> >> >> > >> >> >> >> > >> >> >> > > >> >> >> > > >> >> >> > >> >> >> > >> >> >> anita@anitas-computer:~$ sudo slmodemd -c CANADA -a --debug=2 --log hw:0,6 > >> >> >> Password: > >> >> >> SmartLink Soft Modem: version 2.9.11 Feb 17 2008 09:31:10 > >> >> >> <102.811403> SmartLink Soft Modem: version 2.9.11 Feb 17 2008 09:31:10 > >> >> >> <102.811493> hw:0,6: startup modem... > >> >> >> <102.811607> hw:0,6: update termios... > >> >> >> symbolic link `/dev/ttySL0' -> `/dev/pts/2' created. > >> >> >> modem `hw:0,6' created. TTY is `/dev/pts/2' > >> >> >> <102.812335> open file: /var/lib/slmodem/data.hw:0,6... > >> >> >> <102.812400> cannot open '/var/lib/slmodem/data.hw:0,6': No such file or directory > >> >> >> <102.821020> main: rt applyed: SCHED_FIFO, pri 99 > >> >> >> Use `/dev/ttySL0' as modem device, Ctrl+C for termination. > >> >> >> <123.805297> main: termios changed. > >> >> >> <123.805359> hw:0,6: update termios... > >> >> >> <123.899945> main: termios changed. > >> >> >> <123.899990> hw:0,6: update termios... > >> >> >> <123.999911> hw:0,6: run cmd: ATZ > >> >> >> <123.999954> hw:0,6: modem reset... > >> >> >> <123.999974> hw:0,6: modem set state: 1 --> 1... > >> >> >> <123.999997> hw:0,6: modem set mode: -> 0... > >> >> >> <124.000017> hw:0,6: modem report result: 0 (OK) > >> >> >> <124.100007> hw:0,6: run cmd: ATQ0V1E1S0=0&C1&D2+FCLASS=0 > >> >> >> <124.100058> hw:0,6: modem set mode: -> 0... > >> >> >> <124.100079> hw:0,6: modem report result: 0 (OK) > >> >> >> <124.200095> hw:0,6: run cmd: ATDT7054579564 > >> >> >> <124.200156> hw:0,6: modem dial: T7054579564... > >> >> >> <124.200177> hw:0,6: modem_dial_start... > >> >> >> <124.200985> hw:0,6: modem_start.. > >> >> >> <124.201010> hw:0,6: modem set state: 1 --> 2... > >> >> >> <124.201045> hw:0,6: new state: DP_ESTAB > >> >> >> <124.201069> main: alsa_ioctl: cmd 8, arg 3... > >> >> >> <124.201089> hw:0,6: modem set hook: 0 --> 1... > >> >> >> <124.201119> main: alsa_ioctl: cmd 2, arg 1... > >> >> >> <124.211866> main: alsa_ioctl: cmd 11, arg 0... > >> >> >> <124.211950> main: alsa_ioctl: cmd 4, arg 2580... > >> >> >> <124.211976> main: alsa_ioctl: cmd 7, arg 30... > >> >> >> <124.211995> main: alsa_start... > >> >> >> error: cannot setup hw params for playback: Invalid argument > >> >> >> <124.212186> err: hw:0,6: modem start = -22: cannot start device. > >> >> >> <124.212210> hw:0,6: modem_stop.. > >> >> >> <124.212227> hw:0,6: modem set hook: 1 --> 0... > >> >> >> <124.212246> main: alsa_ioctl: cmd 2, arg 0... > >> >> >> <124.219868> main: alsa_ioctl: cmd 8, arg 0... > >> >> >> <124.220007> hw:0,6: modem set state: 2 --> 1... > >> >> >> <124.220030> hw:0,6: new state: MODEM_IDLE > >> >> >> <124.220053> hw:0,6: modem report result: 3 (NO CARRIER) > >> >> >> <124.220081> hw:0,6: modem report result: 4 (ERROR) > >> >> >> <124.520058> hw:0,6: run cmd: ATDT7054579564 > >> >> >> <124.520122> hw:0,6: modem dial: T7054579564... > >> >> >> <124.520143> hw:0,6: modem_dial_start... > >> >> >> <124.520965> hw:0,6: modem_start.. > >> >> >> <124.520988> hw:0,6: modem set state: 1 --> 2... > >> >> >> <124.521023> hw:0,6: new state: DP_ESTAB > >> >> >> <124.521056> main: alsa_ioctl: cmd 8, arg 3... > >> >> >> <124.521089> hw:0,6: modem set hook: 0 --> 1... > >> >> >> <124.521121> main: alsa_ioctl: cmd 2, arg 1... > >> >> >> <124.531858> main: alsa_ioctl: cmd 11, arg 0... > >> >> >> <124.531945> main: alsa_ioctl: cmd 4, arg 2580... > >> >> >> <124.531974> main: alsa_ioctl: cmd 7, arg 30... > >> >> >> <124.531993> main: alsa_start... > >> >> >> error: cannot setup hw params for playback: Invalid argument > >> >> >> <124.539942> err: hw:0,6: modem start = -22: cannot start device. > >> >> >> <124.539978> hw:0,6: modem_stop.. > >> >> >> <124.539998> hw:0,6: modem set hook: 1 --> 0... > >> >> >> <124.540017> main: alsa_ioctl: cmd 2, arg 0... > >> >> >> <124.547855> main: alsa_ioctl: cmd 8, arg 0... > >> >> >> <124.547978> hw:0,6: modem set state: 2 --> 1... > >> >> >> <124.547997> hw:0,6: new state: MODEM_IDLE > >> >> >> <124.548019> hw:0,6: modem report result: 3 (NO CARRIER) > >> >> >> <124.548048> hw:0,6: modem report result: 4 (ERROR) > >> >> >> <124.848056> hw:0,6: run cmd: ATDT7054579564 > >> >> >> <124.848117> hw:0,6: modem dial: T7054579564... > >> >> >> <124.848138> hw:0,6: modem_dial_start... > >> >> >> <124.848943> hw:0,6: modem_start.. > >> >> >> <124.848967> hw:0,6: modem set state: 1 --> 2... > >> >> >> <124.849002> hw:0,6: new state: DP_ESTAB > >> >> >> <124.849035> main: alsa_ioctl: cmd 8, arg 3... > >> >> >> <124.849067> hw:0,6: modem set hook: 0 --> 1... > >> >> >> <124.849099> main: alsa_ioctl: cmd 2, arg 1... > >> >> >> <124.859854> main: alsa_ioctl: cmd 11, arg 0... > >> >> >> <124.859941> main: alsa_ioctl: cmd 4, arg 2580... > >> >> >> <124.859965> main: alsa_ioctl: cmd 7, arg 30... > >> >> >> <124.859984> main: alsa_start... > >> >> >> error: cannot setup hw params for playback: Invalid argument > >> >> >> <124.867934> err: hw:0,6: modem start = -22: cannot start device. > >> >> >> <124.867969> hw:0,6: modem_stop.. > >> >> >> <124.867988> hw:0,6: modem set hook: 1 --> 0... > >> >> >> <124.868007> main: alsa_ioctl: cmd 2, arg 0... > >> >> >> <124.875855> main: alsa_ioctl: cmd 8, arg 0... > >> >> >> <124.875980> hw:0,6: modem set state: 2 --> 1... > >> >> >> <124.875999> hw:0,6: new state: MODEM_IDLE > >> >> >> <124.876017> hw:0,6: modem report result: 3 (NO CARRIER) > >> >> >> <124.876043> hw:0,6: modem report result: 4 (ERROR) > >> >> >> <125.176053> hw:0,6: run cmd: ATDT7054579564 > >> >> >> <125.176123> hw:0,6: modem dial: T7054579564... > >> >> >> <125.176144> hw:0,6: modem_dial_start... > >> >> >> <125.176945> hw:0,6: modem_start.. > >> >> >> <125.176969> hw:0,6: modem set state: 1 --> 2... > >> >> >> <125.177003> hw:0,6: new state: DP_ESTAB > >> >> >> <125.177037> main: alsa_ioctl: cmd 8, arg 3... > >> >> >> <125.177068> hw:0,6: modem set hook: 0 --> 1... > >> >> >> <125.177101> main: alsa_ioctl: cmd 2, arg 1... > >> >> >> <125.187850> main: alsa_ioctl: cmd 11, arg 0... > >> >> >> <125.187935> main: alsa_ioctl: cmd 4, arg 2580... > >> >> >> <125.187961> main: alsa_ioctl: cmd 7, arg 30... > >> >> >> <125.187980> main: alsa_start... > >> >> >> error: cannot setup hw params for playback: Invalid argument > >> >> >> <125.195938> err: hw:0,6: modem start = -22: cannot start device. > >> >> >> <125.195974> hw:0,6: modem_stop.. > >> >> >> <125.195993> hw:0,6: modem set hook: 1 --> 0... > >> >> >> <125.196013> main: alsa_ioctl: cmd 2, arg 0... > >> >> >> <125.203844> main: alsa_ioctl: cmd 8, arg 0... > >> >> >> <125.203967> hw:0,6: modem set state: 2 --> 1... > >> >> >> <125.203986> hw:0,6: new state: MODEM_IDLE > >> >> >> <125.204005> hw:0,6: modem report result: 3 (NO CARRIER) > >> >> >> <125.204031> hw:0,6: modem report result: 4 (ERROR) > >> >> >> <125.504051> hw:0,6: run cmd: ATDT7054579564 > >> >> >> <125.504122> hw:0,6: modem dial: T7054579564... > >> >> >> <125.504144> hw:0,6: modem_dial_start... > >> >> >> <125.504949> hw:0,6: modem_start.. > >> >> >> <125.504973> hw:0,6: modem set state: 1 --> 2... > >> >> >> <125.505007> hw:0,6: new state: DP_ESTAB > >> >> >> <125.505041> main: alsa_ioctl: cmd 8, arg 3... > >> >> >> <125.505073> hw:0,6: modem set hook: 0 --> 1... > >> >> >> <125.505106> main: alsa_ioctl: cmd 2, arg 1... > >> >> >> <125.515841> main: alsa_ioctl: cmd 11, arg 0... > >> >> >> <125.515928> main: alsa_ioctl: cmd 4, arg 2580... > >> >> >> <125.515953> main: alsa_ioctl: cmd 7, arg 30... > >> >> >> <125.515972> main: alsa_start... > >> >> >> error: cannot setup hw params for playback: Invalid argument > >> >> >> <125.523920> err: hw:0,6: modem start = -22: cannot start device. > >> >> >> <125.523959> hw:0,6: modem_stop.. > >> >> >> <125.523978> hw:0,6: modem set hook: 1 --> 0... > >> >> >> <125.523997> main: alsa_ioctl: cmd 2, arg 0... > >> >> >> <125.531846> main: alsa_ioctl: cmd 8, arg 0... > >> >> >> <125.531970> hw:0,6: modem set state: 2 --> 1... > >> >> >> <125.531990> hw:0,6: new state: MODEM_IDLE > >> >> >> <125.532008> hw:0,6: modem report result: 3 (NO CARRIER) > >> >> >> <125.532034> hw:0,6: modem report result: 4 (ERROR) > >> >> >> <125.832041> hw:0,6: run cmd: ATDT7054579564 > >> >> >> <125.832109> hw:0,6: modem dial: T7054579564... > >> >> >> <125.832130> hw:0,6: modem_dial_start... > >> >> >> <125.832932> hw:0,6: modem_start.. > >> >> >> <125.832963> hw:0,6: modem set state: 1 --> 2... > >> >> >> <125.832997> hw:0,6: new state: DP_ESTAB > >> >> >> <125.833021> main: alsa_ioctl: cmd 8, arg 3... > >> >> >> <125.833041> hw:0,6: modem set hook: 0 --> 1... > >> >> >> <125.833072> main: alsa_ioctl: cmd 2, arg 1... > >> >> >> <125.843834> main: alsa_ioctl: cmd 11, arg 0... > >> >> >> <125.843925> main: alsa_ioctl: cmd 4, arg 2580... > >> >> >> <125.843949> main: alsa_ioctl: cmd 7, arg 30... > >> >> >> <125.843968> main: alsa_start... > >> >> >> error: cannot setup hw params for playback: Invalid argument > >> >> >> <125.851921> err: hw:0,6: modem start = -22: cannot start device. > >> >> >> <125.851957> hw:0,6: modem_stop.. > >> >> >> <125.851976> hw:0,6: modem set hook: 1 --> 0... > >> >> >> <125.851995> main: alsa_ioctl: cmd 2, arg 0... > >> >> >> <125.859832> main: alsa_ioctl: cmd 8, arg 0... > >> >> >> <125.859958> hw:0,6: modem set state: 2 --> 1... > >> >> >> <125.859978> hw:0,6: new state: MODEM_IDLE > >> >> >> <125.859996> hw:0,6: modem report result: 3 (NO CARRIER) > >> >> >> <125.860023> hw:0,6: modem report result: 4 (ERROR) > >> >> >> <126.160045> hw:0,6: run cmd: ATDT7054579564 > >> >> >> <126.160121> hw:0,6: modem dial: T7054579564... > >> >> >> <126.160141> hw:0,6: modem_dial_start... > >> >> >> <126.160954> hw:0,6: modem_start.. > >> >> >> <126.160978> hw:0,6: modem set state: 1 --> 2... > >> >> >> <126.161012> hw:0,6: new state: DP_ESTAB > >> >> >> <126.161036> main: alsa_ioctl: cmd 8, arg 3... > >> >> >> <126.161056> hw:0,6: modem set hook: 0 --> 1... > >> >> >> <126.161088> main: alsa_ioctl: cmd 2, arg 1... > >> >> >> <126.171827> main: alsa_ioctl: cmd 11, arg 0... > >> >> >> <126.171919> main: alsa_ioctl: cmd 4, arg 2580... > >> >> >> <126.171944> main: alsa_ioctl: cmd 7, arg 30... > >> >> >> <126.171964> main: alsa_start... > >> >> >> error: cannot setup hw params for playback: Invalid argument > >> >> >> <126.179911> err: hw:0,6: modem start = -22: cannot start device. > >> >> >> <126.179947> hw:0,6: modem_stop.. > >> >> >> <126.179967> hw:0,6: modem set hook: 1 --> 0... > >> >> >> <126.179986> main: alsa_ioctl: cmd 2, arg 0... > >> >> >> <126.187831> main: alsa_ioctl: cmd 8, arg 0... > >> >> >> <126.187956> hw:0,6: modem set state: 2 --> 1... > >> >> >> <126.187975> hw:0,6: new state: MODEM_IDLE > >> >> >> <126.187993> hw:0,6: modem report result: 3 (NO CARRIER) > >> >> >> <126.188019> hw:0,6: modem report result: 4 (ERROR) > >> >> >> <126.488026> hw:0,6: run cmd: ATDT7054579564 > >> >> >> <126.488096> hw:0,6: modem dial: T7054579564... > >> >> >> <126.488117> hw:0,6: modem_dial_start... > >> >> >> <126.488919> hw:0,6: modem_start.. > >> >> >> <126.488949> hw:0,6: modem set state: 1 --> 2... > >> >> >> <126.488971> hw:0,6: new state: DP_ESTAB > >> >> >> <126.488992> main: alsa_ioctl: cmd 8, arg 3... > >> >> >> <126.489013> hw:0,6: modem set hook: 0 --> 1... > >> >> >> <126.489044> main: alsa_ioctl: cmd 2, arg 1... > >> >> >> <126.499829> main: alsa_ioctl: cmd 11, arg 0... > >> >> >> <126.499927> main: alsa_ioctl: cmd 4, arg 2580... > >> >> >> <126.499953> main: alsa_ioctl: cmd 7, arg 30... > >> >> >> <126.499972> main: alsa_start... > >> >> >> error: cannot setup hw params for playback: Invalid argument > >> >> >> <126.507907> err: hw:0,6: modem start = -22: cannot start device. > >> >> >> <126.507944> hw:0,6: modem_stop.. > >> >> >> <126.507963> hw:0,6: modem set hook: 1 --> 0... > >> >> >> <126.507983> main: alsa_ioctl: cmd 2, arg 0... > >> >> >> <126.515817> main: alsa_ioctl: cmd 8, arg 0... > >> >> >> <126.515965> hw:0,6: modem set state: 2 --> 1... > >> >> >> <126.515986> hw:0,6: new state: MODEM_IDLE > >> >> >> <126.516004> hw:0,6: modem report result: 3 (NO CARRIER) > >> >> >> <126.516030> hw:0,6: modem report result: 4 (ERROR) > >> >> >> <126.728412> main: termios changed. > >> >> >> <126.728456> hw:0,6: update termios... > >> >> >> <126.728479> main: pty closed. > >> >> >> > >> >> >> > >> >> >> > >> >> >> > >> >> >> > >> >> >> > >> >> > > >> >> > > >> >> > >> >> > >> > > >> > > >> > >> > >> > > > > > > > anita@anitas-computer:~$ sudo updatedb > Password: > anita@anitas-computer:~$ locate sl-modem-daemon > anita@anitas-computer:~$ cd /usr/src/modules > anita@anitas-computer:/usr/src/modules$ ls > alsa > anita@anitas-computer:/usr/src/modules$ cd alsa > anita@anitas-computer:/usr/src/modules/alsa$ HEADERS=/lib/modules/2.6.20-15-generic/build > anita@anitas-computer:/usr/src/modules/alsa$ ls $HEADERS > arch fs kernel Module.symvers sound > block include lib net ubuntu > crypto init Makefile scripts usr > drivers ipc mm security > anita@anitas-computer:/usr/src/modules/alsa$ cd alsa-driver-1.0.16 > anita@anitas-computer:/usr/src/modules/alsa/alsa-driver-1.0.16$ ./configure --with-kernel=$HEADERS --with-build=$HEADERS --with-cards=hda-intel > checking for gcc... gcc > checking for C compiler default output file name... configure: error: C compiler cannot create executables > See `config.log' for more details. > anita@anitas-computer:/usr/src/modules/alsa/alsa-driver-1.0.16$ gedit config.log > anita@anitas-computer:/usr/src/modules/alsa/alsa-driver-1.0.16$ > > > >
