Hi Jacques, down in the message there is the lsmod exit I post it again Thanks P >> > root@paolo-pc:/# lsmod | grep snd >> > snd_intel8x0m 18956 0 >> > snd_intel8x0 35356 0 >> > snd_atiixp_modem 17544 0 >> > snd_via82xx_modem 16264 0 >> > snd_trident 44324 3 >> > gameport 16008 2 snd_trident >> > snd_ac97_codec 101028 5 snd_intel8x0m,snd_intel8x0,snd_atiixp_modem,snd_via82xx_modem,snd_trident >> > ac97_bus 3072 1 snd_ac97_codec >> > snd_pcm_oss 42144 0 >> > snd_mixer_oss 17920 1 snd_pcm_oss >> > snd_pcm 78596 7 snd_intel8x0m,snd_intel8x0,snd_atiixp_modem,snd_via82xx_modem,snd_trident,snd_ac97_codec,snd_pcm_oss >> > snd_page_alloc 11400 6 snd_intel8x0m,snd_intel8x0,snd_atiixp_modem,snd_via82xx_modem,snd_trident,snd_pcm >> > snd_util_mem 5632 1 snd_trident >> > snd_mpu401_uart 9728 1 snd_trident >> > snd_seq_dummy 4868 0 >> > snd_seq_oss 35584 0 >> > snd_seq_midi 9376 0 >> > snd_rawmidi 25760 2 snd_mpu401_uart,snd_seq_midi >> > snd_seq_midi_event 8320 2 snd_seq_oss,snd_seq_midi >> > snd_seq 54224 6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event >> > snd_timer 24836 2 snd_pcm,snd_seq >> > snd_seq_device 9612 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq >> > snd 56996 22 snd_intel8x0m,snd_intel8x0,snd_atiixp_modem,snd_via82xx_modem,snd_trident,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_mpu401_uart,snd_seq_dummy,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device >> > soundcore 8800 1 snd >> > root@paolo-pc:/# -----Messaggio originale----- Da: Jacques Goldberg [mailto:Jacques.Goldberg@xxxxxxx] Inviato: giovedì 12 giugno 2008 16.42 A: Barbieri Arnaldi Paolo Cc: Discuss@xxxxxxxxxxxxx Oggetto: Re: R: R: PaoloBarbieri, ITALY kernel 2.6.24-16-generic Paolo Send us the output of lsmod so that we can see which software uses your trident driver. Technique: sudo /sbin/lsmod > lsmod.txt and send us the resulting file lsmod.txt Jacques Barbieri Arnaldi Paolo wrote: > Hi friends, > I tried the instructions: > > modprobe -r snd-intel8x0m > modprobe -r snd-intel8x0 > modprobe -r snd-trident > > and the reloading > > the problem is that > snd-trident cannot be unloaded because in use > > I tried to look for the snd-trident.ko but I could not find it in the folder /lib/modules/2.6.17-10-generic/kernel/sound......... > Where is that file in ubuntu 8.04? > > In addition I think that unloading snd-trident will mean may be to have the modem but to lose the audio. What do you think? > > Anyway I will try again following the Antonio and Marvin help and then I'll post the results > > Thanks guys > > > > > > -----Messaggio originale----- > Da: Marvin Stodolsky [mailto:marvin.stodolsky@xxxxxxxxx] > Inviato: giovedì 12 giugno 2008 4.20 > A: Barbieri Arnaldi Paolo > Cc: Linmodems > Oggetto: Re: R: PaoloBarbieri, ITALY kernel 2.6.24-16-generic > > Barbieri, > > These drivers > snd_atiixp_modem > snd_via82xx_modem > are for other modem hardware. It will do no harm and may help to > blacklist them: > > $ sudo gedit /etc/modprobe.d/local > just create to lines: > blacklist snd-atiixp-modem > blacklist snd-via82xx-modem > > Do an extra return, then Save. > When you reboot they shouldn't be loaded. > $ lsmod | grep modem > should not display them. > > The other guidance below is correct. > > MarvS > scanModem maintainer > > > On 6/11/08, Antonio Olivares <olivares14031@xxxxxxxxx> wrote: >> On Wed, Jun 11, 2008 at 3:35 AM, Barbieri Arnaldi Paolo >> <paolo.barbieri.arnaldi@xxxxxx> wrote: >> > >> > >> > Hi antonio, >> > thanks for your help. >> > Tell me if I must post on the list also... >> > >> It is the recommended way to do things, since there are others on the >> list that might have encountered your problem and have a solution that >> you can try out. >> >> There is a conflict with the sound drivers :( >> >> <direct from scanModem> >> The snd-trident driver is not fully compatible with slmodemd support. >> The may be errors written to /var/log/messages like: >> codec_semaphore: semaphore is not ready [0x1][0x1300] >> Check with: >> $ dmesg | grep semaphore >> >> A potential work around is to unload drivers: >> # modprobe -r snd-intel8x0m >> # modprobe -r snd-intel8x0 >> # modprobe -r snd-trident >> >> Then reload only: >> # modprobe snd-intel8x0 >> # modprobe snd-intel8x0m >> and test the modem. >> >> If snd-trident cannot be unloaded, it may be necessary to disable it by: >> # cd /lib/modules/2.6.17-10-generic/kernel/sound/pci/trident/ >> # mv snd-trident.ko snd-trident.ko~ >> After a reboot, verify that the driver is not loaded. It should NOT be >> disaplayed by: >> $ lsmod | grep snd-trident. >> >> Once a success with the modem has been obtained, the setup can be made easier by >> adding to /etc/modprobe.d/blacklist (or equivalent on your System) >> blacklist snd_intel8x0m >> blacklist snd_trident >> >> and to /etc/modules >> snd_intel8x0 >> snd_intel8x0m >> </direct quote from scanModem> >> >> Please try the above instructions and hopefully you can get connected. >> Report back if this solved your problem. >> >> Regards, >> >> Antonio >> >> > >> > I tried to follow the instructions but this is the system answer >> > >> > >> > root@paolo-pc:/# slmodemd --alsa -c ITALY modem:1 >> > error: mixer setup: attach hw:1 error: No such file or directory >> > ALSA lib conf.c:3952:(snd_config_expand) Unknown parameters 1 >> > ALSA lib pcm.c:2145:(snd_pcm_open_noupdate) Unknown PCM modem:1 >> > error: alsa setup: cannot open playback device 'modem:1': Invalid argument >> > error: cannot setup device `modem:1' >> > root@paolo-pc:/# slmodemd --alsa -c ITALY modem:0 >> > ALSA lib conf.c:3952:(snd_config_expand) Unknown parameters 0 >> > ALSA lib pcm.c:2145:(snd_pcm_open_noupdate) Unknown PCM modem:0 >> > error: alsa setup: cannot open playback device 'modem:0': Invalid argument >> > error: cannot setup device `modem:0' >> > root@paolo-pc:/# >> > >> > >> > I tried to install the sl-modem-daemon also, >> > but without any result >> > >> > the /dev/ttySL0 does not exist >> > >> > some additional info about the system at now are: >> > >> > root@paolo-pc:/# lsmod | grep snd >> > snd_intel8x0m 18956 0 >> > snd_intel8x0 35356 0 >> > snd_atiixp_modem 17544 0 >> > snd_via82xx_modem 16264 0 >> > snd_trident 44324 3 >> > gameport 16008 2 snd_trident >> > snd_ac97_codec 101028 5 snd_intel8x0m,snd_intel8x0,snd_atiixp_modem,snd_via82xx_modem,snd_trident >> > ac97_bus 3072 1 snd_ac97_codec >> > snd_pcm_oss 42144 0 >> > snd_mixer_oss 17920 1 snd_pcm_oss >> > snd_pcm 78596 7 snd_intel8x0m,snd_intel8x0,snd_atiixp_modem,snd_via82xx_modem,snd_trident,snd_ac97_codec,snd_pcm_oss >> > snd_page_alloc 11400 6 snd_intel8x0m,snd_intel8x0,snd_atiixp_modem,snd_via82xx_modem,snd_trident,snd_pcm >> > snd_util_mem 5632 1 snd_trident >> > snd_mpu401_uart 9728 1 snd_trident >> > snd_seq_dummy 4868 0 >> > snd_seq_oss 35584 0 >> > snd_seq_midi 9376 0 >> > snd_rawmidi 25760 2 snd_mpu401_uart,snd_seq_midi >> > snd_seq_midi_event 8320 2 snd_seq_oss,snd_seq_midi >> > snd_seq 54224 6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event >> > snd_timer 24836 2 snd_pcm,snd_seq >> > snd_seq_device 9612 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq >> > snd 56996 22 snd_intel8x0m,snd_intel8x0,snd_atiixp_modem,snd_via82xx_modem,snd_trident,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_mpu401_uart,snd_seq_dummy,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device >> > soundcore 8800 1 snd >> > root@paolo-pc:/# >> > root@paolo-pc:/# lspci >> > 00:00.0 Host bridge: Silicon Integrated Systems [SiS] 630 Host (rev 31) >> > 00:00.1 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (rev d0) >> > 00:01.0 ISA bridge: Silicon Integrated Systems [SiS] SiS85C503/5513 (LPC Bridge) >> > 00:01.2 USB Controller: Silicon Integrated Systems [SiS] USB 1.1 Controller (rev 07) >> > 00:01.4 Multimedia audio controller: Silicon Integrated Systems [SiS] SiS PCI Audio Accelerator (rev 02) >> > 00:01.6 Modem: Silicon Integrated Systems [SiS] AC'97 Modem Controller (rev a0) >> > 00:02.0 PCI bridge: Silicon Integrated Systems [SiS] Virtual PCI-to-PCI bridge (AGP) >> > 00:08.0 CardBus bridge: Texas Instruments PCI1225 (rev 01) >> > 00:08.1 CardBus bridge: Texas Instruments PCI1225 (rev 01) >> > 01:00.0 VGA compatible controller: Silicon Integrated Systems [SiS] 630/730 PCI/AGP VGA Display Adapter (rev 31) >> > 02:00.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 61) >> > 02:00.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 61) >> > 02:00.2 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 63) >> > 02:00.3 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 80) >> > root@paolo-pc:/# dmesg | grep semaphore >> > [ 5129.417751] ALSA /build/buildd/linux-ubuntu-modules-2.6.24-2.6.24/debian/build/build-generic/sound/alsa-driver/pci/../alsa-kernel/pci/intel8x0m.c:337: codec_semaphore: semaphore is not ready [0x1][0x300] >> > [ 5129.418854] ALSA /build/buildd/linux-ubuntu-modules-2.6.24-2.6.24/debian/build/build-generic/sound/alsa-driver/pci/../alsa-kernel/pci/intel8x0m.c:337: codec_semaphore: semaphore is not ready [0x1][0x300] >> > [ 5129.419981] ALSA /build/buildd/linux-ubuntu-modules-2.6.24-2.6.24/debian/build/build-generic/sound/alsa-driver/pci/../alsa-kernel/pci/intel8x0m.c:337: codec_semaphore: semaphore is not ready [0x1][0x300] >> > [ 5129.421081] ALSA /build/buildd/linux-ubuntu-modules-2.6.24-2.6.24/debian/build/build-generic/sound/alsa-driver/pci/../alsa-kernel/pci/intel8x0m.c:337: codec_semaphore: semaphore is not ready [0x1][0x300] >> > [ 5129.431106] ALSA /build/buildd/linux-ubuntu-modules-2.6.24-2.6.24/debian/build/build-generic/sound/alsa-driver/pci/../alsa-kernel/pci/intel8x0m.c:337: codec_semaphore: semaphore is not ready [0x1][0x300] >> > [ 5129.432220] ALSA /build/buildd/linux-ubuntu-modules-2.6.24-2.6.24/debian/build/build-generic/sound/alsa-driver/pci/../alsa-kernel/pci/intel8x0m.c:337: codec_semaphore: semaphore is not ready [0x1][0x300] >> > [ 5129.437717] ALSA /build/buildd/linux-ubuntu-modules-2.6.24-2.6.24/debian/build/build-generic/sound/alsa-driver/pci/../alsa-kernel/pci/intel8x0m.c:337: codec_semaphore: semaphore is not ready [0x1][0x300] >> > [ 5129.438817] ALSA /build/buildd/linux-ubuntu-modules-2.6.24-2.6.24/debian/build/build-generic/sound/alsa-driver/pci/../alsa-kernel/pci/intel8x0m.c:337: codec_semaphore: semaphore is not ready [0x1][0x300] >> > [ 5129.439939] ALSA /build/buildd/linux-ubuntu-modules-2.6.24-2.6.24/debian/build/build-generic/sound/alsa-driver/pci/../alsa-kernel/pci/intel8x0m.c:337: codec_semaphore: semaphore is not ready [0x1][0x300] >> > [ 5129.441045] ALSA /build/buildd/linux-ubuntu-modules-2.6.24-2.6.24/debian/build/build-generic/sound/alsa-driver/pci/../alsa-kernel/pci/intel8x0m.c:337: codec_semaphore: semaphore is not ready [0x1][0x300] >> > [ 5129.451205] ALSA /build/buildd/linux-ubuntu-modules-2.6.24-2.6.24/debian/build/build-generic/sound/alsa-driver/pci/../alsa-kernel/pci/intel8x0m.c:337: codec_semaphore: semaphore is not ready [0x1][0x300] >> > [ 5129.452309] ALSA /build/buildd/linux-ubuntu-modules-2.6.24-2.6.24/debian/build/build-generic/sound/alsa-driver/pci/../alsa-kernel/pci/intel8x0m.c:337: codec_semaphore: semaphore is not ready [0x1][0x300] >> > [ 5129.457833] ALSA /build/buildd/linux-ubuntu-modules-2.6.24-2.6.24/debian/build/build-generic/sound/alsa-driver/pci/../alsa-kernel/pci/intel8x0m.c:337: codec_semaphore: semaphore is not ready [0x1][0x300] >> > [ 5129.458961] ALSA /build/buildd/linux-ubuntu-modules-2.6.24-2.6.24/debian/build/build-generic/sound/alsa-driver/pci/../alsa-kernel/pci/intel8x0m.c:337: codec_semaphore: semaphore is not ready [0x1][0x300] >> > root@paolo-pc:/# >> > root@paolo-pc:/# wvdialconf /etc/wvdial.conf >> > Editing `/etc/wvdial.conf'. >> > >> > Scanning your serial ports for a modem. >> > >> > ttyS0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud >> > ttyS0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud >> > ttyS0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up. >> > Modem Port Scan<*1>: 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>. >> > root@paolo-pc:/# >> > >> > >> > >> > >> > >> > Thanks >> > paolo >> > _________________________________ >> > >> > -----Messaggio originale----- >> > Da: Antonio Olivares [mailto:olivares14031@xxxxxxxxx] >> > Inviato: martedì 10 giugno 2008 17.36 >> > A: Barbieri Arnaldi Paolo >> > Cc: Discuss@xxxxxxxxxxxxx >> > Oggetto: Re: PaoloBarbieri, ITALY kernel 2.6.24-16-generic >> > >> > Paolo, >> > >> > scanModem reports >> > \beqin{QUOTE} >> > For candidate modem in: 00:01.6 >> > Class 0703: 1039:7013 Modem: Silicon Integrated Systems [SiS] AC'97 >> > Modem Controller >> > Primary device ID: 1039:7013 >> > Subsystem PCI_id 1631:3005 >> > Softmodem codec or chipset from diagnostics: >> > from Archives: >> > >> > >> > >> > Support type needed or chipset: slmodemd >> > >> > An ALSA (Advanced Linux Sound Architecture) modem driver: >> > 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.2.tar.gz having a compiled slmodemd. Unpack >> > under Linux with: >> > $ tar zxf SLMODEMD.gcc4.2.tar.gz >> > and read instructions therein. But briefly, the modem is setup with command: >> > sudo 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. >> > \en{QUOTE} >> > >> > Do download SLMODEMD.gcc4.2.tar.gz, also read Smartlink.txt and >> > Modem/YourSystem.txt for further instructions. >> > >> > Regards, >> > >> > Antonio >> > >> > On Tue, Jun 10, 2008 at 10:20 AM, Barbieri Arnaldi Paolo >> > <paolo.barbieri.arnaldi@xxxxxx> wrote: >> >> >> >> Somebody can help me step by step? >> >> Thanks a lot >> >> Paolo >> >> >> >> >> >> 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.24-16-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. >> >> 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.24-16-generic (buildd@palmer) (gcc version 4.2.3 (Ubuntu 4.2.3-2ubuntu7)) #1 SMP Thu Apr 10 13:23:42 UTC 2008 >> >> scanModem update of: 2008_05_02 >> >> >> >> There are no blacklisted modem drivers in /etc/modprobe* files >> >> Attached USB devices are: >> >> ID 08ec:0015 M-Systems Flash Disk Pioneers >> >> ID 05e3:1205 Genesys Logic, Inc. Afilias Optical Mouse H3003 >> >> >> >> USB modems not recognized >> >> For candidate card in slot 00:01.6, firmware information and bootup diagnostics are: >> >> PCI slot PCI ID SubsystemID Name >> >> ---------- --------- --------- -------------- >> >> 00:01.6 1039:7013 1631:3005 Modem: Silicon Integrated Systems [SiS] AC'97 Modem Controller >> >> >> >> Modem interrupt assignment and sharing: >> >> 11: 5 XT-PIC-XT acpi >> >> --- Bootup diagnostics for card in PCI slot 00:01.6 ---- >> >> [ 30.824656] ACPI: PCI Interrupt 0000:00:01.6[C] -> Link [LNKC] -> GSI 11 (level, low) -> IRQ 11 >> >> [ 30.824676] ACPI: PCI interrupt for device 0000:00:01.6 disabled >> >> >> >> The PCI slot 00:01.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. >> >> >> >> >> >> >> >> ===== 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.15 >> >> The modem cards detected by "aplay -l" are: >> >> >> >> >> >> The /proc/asound/pcm file reports: >> >> ----------------------- >> >> 00-01: trident_dx_nx IEC958 : Trident 4DWave IEC958 : playback 1 >> >> 00-00: trident_dx_nx : Trident 4DWave : playback 32 : capture 1 >> >> >> >> about /proc/asound/cards: >> >> ------------------------ >> >> 0 [SI7018 ]: SI7018 - SiS SI7018 >> >> SiS SI7018 PCI Audio at 0x1000, irq 9 >> >> === Finished firmware and bootup diagnostics, next deducing cogent software. === >> >> >> >> Predictive diagnostics for card in bus 00:01.6: >> >> Modem chipset detected on >> >> CLASS="Class 0703: 1039:7013" >> >> NAME="Modem: Silicon Integrated Systems [SiS] AC'97 Modem Controller " >> >> SUBSYS=1631:3005 >> >> PCIDEV=1039:7013 >> >> IRQ=11 >> >> SOFT=1039:7013.MC97 >> >> IDENT=slmodemd >> >> SLMODEMD_DEVICE=modem:1 >> >> >> >> For candidate modem in: 00:01.6 >> >> Class 0703: 1039:7013 Modem: Silicon Integrated Systems [SiS] AC'97 Modem Controller >> >> Primary device ID: 1039:7013 >> >> Subsystem PCI_id 1631:3005 >> >> Softmodem codec or chipset from diagnostics: >> >> from Archives: >> >> >> >> >> >> >> >> Support type needed or chipset: slmodemd >> >> >> >> An ALSA (Advanced Linux Sound Architecture) modem driver: >> >> 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.2.tar.gz having a compiled slmodemd. Unpack under Linux with: >> >> $ tar zxf SLMODEMD.gcc4.2.tar.gz >> >> and read instructions therein. But briefly, the modem is setup with command: >> >> sudo 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. >> >> >> >> ----------------end Softmodem section -------------- >> >> Writing Smartlink.txt >> >> >> >> Message http://linmodems.technion.ac.il/bigarch/archive-seventh/msg01358.html >> >> is in part summarized below. >> >> >> >> The snd-trident driver is not fully compatible with slmodemd support. >> >> The may be errors written to /var/log/messages like: >> >> codec_semaphore: semaphore is not ready [0x1][0x1300] >> >> Check with: >> >> $ dmesg | grep semaphore >> >> >> >> A potential work around is to unload drivers: >> >> # modprobe -r snd-intel8x0m >> >> # modprobe -r snd-intel8x0 >> >> # modprobe -r snd-trident >> >> >> >> Then reload only: >> >> # modprobe snd-intel8x0 >> >> # modprobe snd-intel8x0m >> >> and test the modem. >> >> >> >> If snd-trident cannot be unloaded, it may be necessary to disable it by: >> >> # cd /lib/modules/2.6.17-10-generic/kernel/sound/pci/trident/ >> >> # mv snd-trident.ko snd-trident.ko~ >> >> After a reboot, verify that the driver is not loaded. It should NOT be disaplayed by: >> >> $ lsmod | grep snd-trident. >> >> >> >> Once a success with the modem has been obtained, the setup can be made easier by >> >> adding to /etc/modprobe.d/blacklist (or equivalent on your System) >> >> blacklist snd_intel8x0m >> >> blacklist snd_trident >> >> >> >> and to /etc/modules >> >> snd_intel8x0 >> >> snd_intel8x0m >> >> >> >> On Ubuntu systems such edits of Root permission files can be done with: >> >> $ sudo gedit path_to/FileName >> >> >> >> ============ 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.2.3 >> >> and the compiler used in kernel assembly: 4.2.3 >> >> >> >> >> >> >> >> Minimal compiling resources appear complete: >> >> make utility - /usr/bin/make >> >> Compiler version 4.2 >> >> linuc_headers base folder /lib/modules/2.6.24-16-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. 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 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://linmodems.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 >> >> >> >> >> >> 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/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 >> >> /etc/modprobe.d/alsa-base:options snd-atiixp-modem index=-2 >> >> /etc/modprobe.d/alsa-base:options snd-via82xx-modem index=-2 >> >> Within any ancient /etc/devfs files: >> >> >> >> Within ancient kernel 2.4.n /etc/module.conf files: >> >> >> >> --------- end modem support lines -------- >> >> >> > >> > ------------------------------------------------------------------------------------------------------------------------------------------ >> > >> > >> > > ------------------------------------------------------------------------------------------------------------------------------------------ > Message for the recipient only, if received in error, please notify the sender and read http://www.eni.it/disclaimer/ ------------------------------------------------------------------------------------------------------------------------------------------ Message for the recipient only, if received in error, please notify the sender and read http://www.eni.it/disclaimer/
