------- Forwarded message follows ------- From: Leandro G. do Rosário <leandro.rosario@xxxxxxxxxxxxxxxxx> To: dISCUSS@xxxxxxxxxxxxx Subject: Leandro G. do Rosario, Brazil, kernel 2.6.22-14-generic Date sent: Sun, 06 Jan 2008 02:29:06 -0200 Good morning! I still haven't found what I'm looking for... I still doing something wrong with the comand lines you sent me. Must I login as 'root' to execute the comands? I tried to do in a terminal window, but I got error messages asking for 'root privileges' or something else. I tried to execute the file named 'setup', but the install process seems to result incomplete: two files, ungrab-winmodem and slamr (I think) remains not found inside the folder they were intended to be found. The system don't detect the modem! Do the comand lines below need some complements that I don't know? Can the process be done with the graphic interface/window manager tools? Sorry for calling you again, but this modem is burning my brain. Best regards. On 17 Nov 2007 at 22:43, Marvin Stodolsky wrote: > Leandro > > The modem is supported by the Smartlink slamr driver > plus the slmodemd helper utility. > > Download slamr-2.6.20-16-generic.tar.gz from > http://linmodems.technion.il/packages/smartlink/Ubuntu/ > under Linux, open a terminal and unpack with: > $ tar zxvf slamr*.tar.gz > Move into the unpacked folder > $ cd slamr-2.6.20-16-generic > Look around > $ ls > Run the > $ sudo ./setup > > Also run > $ ./scanModem test 1057:3052 1057:3020 > and there will be additional information in the new Modem/ folder. > This should have been already displayed, but for a bug I'm fixing > > MarvS > scanModem maintainer > > On Nov 17, 2007 8:23 PM, Leandro G. do Rosário > <leandro.rosario@xxxxxxxxxxxxxxxxxx> wrote: > > Hi! > > > > Below is the text of ModemData.txt > > > > The refered modem is distributed by Phitronics (www.phitronics.com.br), and is reported to > > be Linux compatible. The packaged CD contains a wide number of diferent drivers (both > > Windows and Linux), but the Debian driver didn't work with my Ubuntu copy. The help files > > that come with the modem are not suficient, and are too technical. There was no indication if > > the driver was built for Ubuntu (but it was a .deb file). > > > > Best regards. > > > > > > ======================================================= > > 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: 20071109 > > The modem symbolic link is /dev/modem -> /dev/sm56 > > > > There are no blacklisted modem drivers in /etc/modprobe* files > > ---ALSA bootup diagnostics --- > > > > The Advanced Linux Sound Architecture (ALSA) packages providing audio support on your > > System, > > also includes drivers for some modems. High Definition Audio (HDA) cards can themselves > > host > > a softmodem chipset, with both audio+modem supported by a snd-hda-intel driver. > > The ALSA diagnostics are written during bootup to /proc/asound/ folders. > > > > > > Modem not detected though HDA card diagnostics, though not excluding > > a possible Conexant modem chip impervious to ALSA diagnostics. > > Proceeding through alternative possibilties. > > > > Summary card and chipset information is in: > > /proc/asound/cards: > > 0 [I82801DBICH4 ]: ICH4 - Intel 82801DB-ICH4 > > Intel 82801DB-ICH4 with AD1885 at irq 21 > > 1 [SAA7134 ]: SAA7134 - SAA7134 > > saa7133[0] at 0xe0001000 irq 19 > > > > /proc/asound/pcm: > > 01-00: SAA7134 PCM : SAA7134 PCM : capture 1 > > 00-04: Intel ICH - IEC958 : Intel 82801DB-ICH4 - IEC958 : playback 1 > > 00-03: Intel ICH - ADC2 : Intel 82801DB-ICH4 - ADC2 : capture 1 > > 00-02: Intel ICH - MIC2 ADC : Intel 82801DB-ICH4 - MIC2 ADC : capture 1 > > 00-01: Intel ICH - MIC ADC : Intel 82801DB-ICH4 - MIC ADC : capture 1 > > 00-00: Intel ICH : Intel 82801DB-ICH4 : playback 1 : capture 1 > > > > A copy of /proc/asound had been copied to Modem/ALSAleandro.tgz > > USB modem not detected by lsusb > > > > For candidate card, firmware information and bootup diagnostics are: > > > > PCI slot PCI ID SubsystemID Name > > ---------- --------- --------- -------------- > > 01:01.0 1057:3052 1057:3020 Modem: Motorola SM56 Data Fax Modem > > > > Modem interrupt assignment and sharing: > > 16: 0 IO-APIC-fasteoi eth0 > > --- Bootup diagnostics for card in PCI slot 01:01.0 ---- > > [ 28.213257] ACPI: PCI Interrupt 0000:01:01.0[A] -> GSI 21 (level, low) -> IRQ 16 > > [ 28.214048] 0000:01:01.0: ttyS1 at I/O 0xc008 (irq = 16) is a 16450 > > [ 28.214618] 0000:01:01.0: ttyS2 at I/O 0xc010 (irq = 16) is a 8250 > > [ 28.215203] 0000:01:01.0: ttyS3 at I/O 0xc018 (irq = 16) is a 16450 > > [ 28.215594] Couldn't register serial port 0000:01:01.0: -28 > > > > === Finished modem firmware and bootup diagnostics section. === > > === Next deducing cogent software === > > > > > > There is candidate modem software. > > > > Completed candidate modem analyses. > > > > 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 pacakage > > 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-x 1 root dip 269256 2007-10-04 16: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: lrwxrwxrwx 1 root root 9 2007-11-17 14:45 /dev/modem -> > > /dev/sm56 > > 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 -------- > > > > > > --- > > avast! Antivirus: Outbound message clean. > > Virus Database (VPS): 071117-0, 17/11/2007 > > Tested on: 17/11/2007 23:24:04 > > avast! - copyright (c) 1988-2007 ALWIL Software. > > http://www.avast.com > > > > > > > > ------- End of forwarded message ------- --- avast! Antivirus: Outbound message clean. Virus Database (VPS): 080106-0, 06/01/2008 Tested on: 7/1/2008 03:24:16 avast! - copyright (c) 1988-2008 ALWIL Software. http://www.avast.com
