Lucille, Then I believe that OpenSuse/Suse believes that your modem is supported by slmodemd + alsa which is not true, but it is not true. You need slamr driver which you can build by downloading and installing: http://linmodems.technion.ac.il/packages/smartlink/ungrab-winmodem-20080126.tar.gz http://linmodems.technion.ac.il/packages/smartlink/slmodem-2.9.11-20080817.tar.gz copy them to your linux partition/home folder and extract them with $ tar -zxvf ungrab-winmodem-20080126.tar.gz $ tar -zxvf slmodem-2.9.11-20080817.tar.gz $ cd $ slmodem-2.9.11--20080817/ $ make KERNEL_DIR=/lib/modules/2.6.25.5-1.1-pae/build $ make $ su passwd: # make install # cd ../ungrab-winmodem-20080126/ # make # make install # exit $ su - passwd: # modprobe ungrab-winmodem # modprobe slamr # slmodemd -c YOUR_COUNTRY /dev/slamr0 report back if you run into trouble or have succeeded connecting your machine to internet. Happy Holidays! Regards, Antonio On 12/23/08, Lucille <silentk@xxxxxxxxxxxx> wrote: > Antonio, > > This is the ModemData.txt from the ALi SmartLink modem. I'm using the LT > WinModem on this Windows computer to do my posting. I did send this same > data file with my registration, but in the registration message I used the > suggested title of Name, Country, Kernel, Distro, and Modem. > > Here it is again for continuity. Frank K > > -------------------------- System information ---------------------------- > CPU=i686, > Linux version 2.6.25.5-1.1-pae (geeko@buildhost) (gcc version 4.3.1 20080507 > (prerelease) [gcc-4_3-branch revision 135036] (SUSE Linux) ) #1 SMP > 2008-06-07 01:55:22 +0200 > scanModem update of: 2008_11_06 > > There are no blacklisted modem drivers in /etc/modprobe* files > Attached USB devices are: > ID 1d6b:0001 Linux Foundation 1.1 root hub > ID 1d6b:0001 Linux Foundation 1.1 root hub > ID 1d6b:0001 Linux Foundation 1.1 root hub > ID 1d6b:0002 Linux Foundation 2.0 root hub > > USB modems not recognized > > For candidate card in slot 01:0b.0, firmware information and bootup > diagnostics are: > PCI slot PCI ID SubsystemID Name > ---------- --------- --------- -------------- > 01:0b.0 10b9:5459 10a5:5459 Modem: ALi Corporation SmartLink > SmartPCI561 56K Modem > > Modem interrupt assignment and sharing: > 23: 0 IO-APIC-fasteoi ehci_hcd:usb2 > --- Bootup diagnostics for card in PCI slot 01:0b.0 ---- > PCI: Enabling device 0000:01:0b.0 (0004 -> 0007) > ACPI: PCI Interrupt 0000:01:0b.0[A] -> GSI 23 (level, low) -> IRQ 23 > 0000:01:0b.0: ttyS1 at I/O 0xb828 (irq = 23) is a 8250 > 0000:01:0b.0: ttyS2 at I/O 0xb840 (irq = 23) is a 8250 > 0000:01:0b.0: ttyS3 at I/O 0xb850 (irq = 23) is a 8250 > Couldn't register serial port 0000:01:0b.0: -28 > > === Finished firmware and bootup diagnostics, next deducing cogent software. > === > > Predictive diagnostics for card in bus 01:0b.0: > Modem chipset detected on > NAME="Modem: ALi Corporation SmartLink SmartPCI561 56K Modem" > CLASS=0703 > PCIDEV=10b9:5459 > SUBSYS=10a5:5459 > IRQ=23 > IDENT=slamr > > For candidate modem in: 01:0b.0 > 0703 Modem: ALi Corporation SmartLink SmartPCI561 56K Modem > Primary device ID: 10b9:5459 > Support type needed or chipset: slamr > > > ----------------end Softmodem section -------------- > The modem is supported by the Smartlink > plus the slmodemd helper utility. Read the > DOCs/Smartlink.txt and Modem/DOCs/YourSystem.txt for follow through > guidance. > > > For 2.6.25.5-1.1-pae compiling drivers is necessary. As of October 2007 the > current packages at > http://linmodems.technion.ac.il/packages/smartlink/ are the > ungrab-winmodem-20070505.tar.gz and slmodem-2.9.11-20080126.tar.gz > > Writing DOCs/Smartlink.txt > ============ end Smartlink section ===================== > > Completed candidate modem analyses. > > The base of the UDEV device file system is: /dev/.udev > > Versions adequately match for the compiler installed: 4.3.1 > and the compiler used in kernel assembly: 4.3 > > > > Minimal compiling resources appear complete: > make utility - /usr/bin/make > Compiler version 4.3 > linuc_headers base folder /lib/modules/2.6.25.5-1.1-pae/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 needed. The also > required headers of package libc6 are commonly installed by default. > Compiling hsfmodem drivers does require linux-libc-dev and libc6-dev > packages, for kernels 2.6.24 and later versions. > In not included on your install CD, search for them at > http://packages.ubuntu.com > or comparable Repository for other Linux distros. > 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 packages. > 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: > -rwxr-xr-x 1 root dialout 304644 2008-06-06 16:21 /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) > chmod a+x /usr/sbin/pppd > or under Ubuntu related Linuxes > chmod a+x /usr/sbin/pppd > > Checking settings of: /etc/ppp/options > noipdefault > noauth > crtscts > lock > modem > asyncmap 0 > nodetach > lcp-echo-interval 30 > lcp-echo-failure 4 > lcp-max-configure 60 > lcp-restart 2 > idle 600 > noipx > file /etc/ppp/filters > > In case of a message like: > Warning: Could not modify /etc/ppp/pap-secrets: Permission denied > see http://linmodems.technion.ac.il/bigarch/archive-sixth/msg04656.html > > > Don't worry about the following, it is for 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: > /etc/udev/rules.d/50-udev-default.rules:KERNEL=="mwave", > NAME="modems/mwave", GROUP="uucp" > /etc/udev/rules.d/77-network.rules:SUBSYSTEM=="net", > ENV{INTERFACE}=="ppp*|ippp*|isdn*|plip*|lo*|irda*|dummy*|ipsec*|tun*|tap*|bond*|vlan*|modem*|dsl*", > GOTO="skip_ifup" > Within /etc/modprobe.conf files: > /etc/modprobe.conf:# Linux ACP modem (Mwave) > Within any ancient /etc/devfs files: > > Within ancient kernel 2.4.n /etc/module.conf files: > > --------- end modem support lines -------- > > > | Please post the ModemData.txt and we can confirm if slamr, or SLMODEMD > will server at least one of your | modems. > | Regards, > | Antonio > > --- On Mon, 12/22/08, Lucille <silentk@xxxxxxxxxxxx> wrote: >> From: Lucille <silentk@xxxxxxxxxxxx> >> Subject: SmartLink w/Suse11.0 - My introduction! >> To: discuss@xxxxxxxxxxxxx >> Date: Monday, December 22, 2008, 12:33 PM >> Hello linmodem discussion, >> >> As a very new member, I may be rushing this post. My member >> confirmation has happened, but I haven't heard anything from the >> moderators regarding my scanModem data. I'm using my mother's >> computer, so her name appears on some of my posting. >> >> So if it's OK for me to start posting now, I'm >> Frank K from Oregon, visiting in Wisconsin, both USA. In Oregon I have >> a pair of USR internal HW modems running under openSuse10.2. In >> Wisconsin I have a pair of WinModems, either of which, I hope to make >> work with openSuse11.0. >> >> This link seems to imply that the slamr module my ALi 5459 SmartModem, >> AKA NetoDragon, wants is now incompatible with openSuse. The >> alternative Alsa driver mentioned "almost" works! >> http://en.opensuse.org/Smart_Link_Modem. >> >> For openers, I would like to know if any discussion members watching >> have built slamr with openSuse > 10. I'm capable of building my own if >> I can get all the pieces I would need. >> >> An easier get would be to learn the "magic" to >> making the Alsa driver work. openSuse11.0 comes with a SoftModem rpm >> that contains the slmodemd also provided by the slamr package. The >> /etc/init.d/slmodemd is part of the rpm "provides". It 's a script >> that will load slamr or defer to alsa depending on environment >> variables. >> >> My MB has an on-board iCH4 soundcard that takes the snd-intel8x0 >> referred to in the above link. My alsa version 1.0.16rc2 also has the >> snd-intel8x0m module referred to in the link. If I use the invocation >> shown in the link slmodemd errors out, complaining about hw:1. >> >> openSuse's Yast sets the environment variables that >> control the slmodemd script. Yast's instructions say to >> set the device variable to slamr0 if not alsa; otherwise modem:x or >> hw:x,y where x=card# and y=PCM#. Elsewhere I've read that "aplay -l" >> shows which PCM is the sound card and which PCM is the modem. >> >> In my case aplay -l shows two devices and doesn't >> chance with the modprobe snd-intel8x0m. If I set the >> slmodemd device to hw:0, "almost" everything works >> as described! The symlink /dev/sttSL0 to /dev/pts/3 is created and the >> modem becomes "animated". Meanwhile the system sound quits! >> >> With device hw.0, and the symlink, the "modem" >> the wouldn't open before will query and dial now, but it never touches >> the phone line! The dial errors out with "No Carrier". Killing >> slmodemd releases the system sound! >> >> I'm thinking that slmodemd using device hw:0 attaches >> to the soundcard instead of the modem. All of the trial and error >> devices I've tried have caused slmodemd to error out. >> >> If I can build slamr for 11.0 I think my problem will be solved, but >> failing that I need advice from an alsa expert to make slmodemd attach >> to the modem. I belong to the alsa-users list, but their business is >> sound and not modems, so I don't expect help from that quarter! >> >> Another option is to switch to the Lucent WinModem. As I understand >> Linuxant has a marginal Lucent driver for sale. It's not to late for >> me to switch distros if a more modem friendly exists. openSuse is my >> first choice and I love KDE! Last there are external modems that work >> and some used internal HW modems available. >> >> Well if anyone is still with me here, thanks for your patience! >> >> I'm hoping this discussion will lead me closer to SW >> solution to my modem problem. >> >> Pleased to meet you, members! Frank K > >
