Dear JT, OpenSuse has an rpm but for the modems that are supported by slmodemd + alsa not the one that requires SLAMR. This is why the modem might have been identified. Unless you did this in 32 bit installation? If you installed 32 bit linux, then you may download the file I directed you to and the ungrab-winmodem source file as well, since the serial driver in the kernel interferes with smarlink hardware. Then read the file Slamr.txt as output by scanModem to see the instructions on how to install the drivers. But in 64 bit linux, the slamr kernel module won't build successfully as it was designed for 32 bit linux. Best Regards, Antonio On Fri, Mar 1, 2013 at 2:22 AM, JT Stimatz <janko52000@xxxxxxxxx> wrote: > Hey All (and, Antonio! :-)),... > > I was curious about of few things, ...not with ONLY SLAMR (I downloaded the WRONG VERSION :-?)...but, with scanModem, as well. > > I found the DEVICE, (SmartLink 56K Modem), and,even, the PCI -BUS info, in case I can MANUALLY INSTALL it (?). > But, some of the error messages aren't ANYTHING like what I was expecting. > > For Instance: > > QApplication::qAppName: Please instantiate the QApplication object first > kdeinit4: preparing to launch /usr/lib64/libkdeinit4_klauncher.so > Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) > kdeinit4: preparing to launch /usr/lib64/libkdeinit4_kded4.so > kdeinit4: preparing to launch /usr/lib64/libkdeinit4_kbuildsycoca4.so > kbuildsycoca4 running... > kdeinit4: preparing to launch /usr/lib64/libkdeinit4_kconf_update.so > Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) > kdeinit4: preparing to launch /usr/lib64/kde4/kio_trash.so > kdeinit4: preparing to launch /usr/lib64/kde4/kio_file.so > kdeinit4: preparing to launch /usr/lib64/libkdeinit4_kbuildsycoca4.so > <unknown program name>(9560)/ KStartupInfo::createNewStartupId: creating: "linux-86ix;1362081675;410170;9560_TIME0" : "unnamed app" > kbuildsycoca4 running... > YaST got signal 11 at YCP file hwinfo/routines.ycp:332 > /sbin/yast2: line 399: 9101 Segmentation fault $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS > > This SEEMS to have reference to ATTEMPTING TO INSTALL and CHECK w/ hardware.txt... > > And, then...(follow the arrows ;-))... > > Three Arrows (>>>) is the SmartLink Info, both PCI.., and, IRQ ... > > Four Arrows (>>>>) is miscellaneous Info that I am completely CONFUSED > about : > >>--- On Thu, 2/28/13, Antonio Olivares <olivares14031@xxxxxxxxx> wrote: > >> From: Antonio Olivares <olivares14031@xxxxxxxxx> >> Subject: Re:HELP: openSUSE 11.3 "Teal" - Kernel kernel 2.6.34-12-desktop >> Cc: Discuss@xxxxxxxxxxxxx > >> Date: Thursday, February 28, 2013, 1:00 PM >> Dear JT, >> >> scanModem reports that your modem would be supported but >> under 32 bit >> linux. You are using 64 bit linux which does not >> support your modem. >> >> Some modem drivers can only be used in 32 bit modem on >> x86_64 systems, >> while some others are competent on x86_64 Systems. >> Cases are: >> 1) http://linmodems.technion.ac.il/bigarch/archive-seventh/msg03119.html >> for the snd-hda-intel audio+modem driver. Also applicable to >> AC97 modem >> controllers. >> In both cases, 32 bit libraries must be installed to support >> the slmodemd >> helper having a precompiled 32 bit component. >> 2) For USB modems using the slusb.ko driver. 32 bit >> libraries must be >> installed to support the slmodemd helper having a >> precompiled 32 bit component >> 3) The hsfmodem and hcfpcimodem drivers for Conexant >> chipsest modes are x86_64 >> competent. >> 4) agrsm packages for LSI/AgereSystems softmodems are not >> competent on x86_64 >> systems. >> >>>>If you install 32 bit linux, then your modem would be >>>> supported by >>>> slmodem-2.9.X-`date +%Y%m%d`.tar.gz with %Y%m%d being the >>>> latest >>>> version available at linmodems modem driver section : >>>> http://linmodems.technion.ac.il/packages/smartlink/ >>>> The latest package is : > >>>> http://linmodems.technion.ac.il/packages/smartlink/slmodem-2.9.11-20110321.tar.gz >> >> Best Regards, >> >> >> Antonio >> >> >> On Thu, Feb 28, 2013 at 2:51 PM, JT Stimatz <janko52000@xxxxxxxxx> >> wrote: >> > Hey All! :-) >> > >> > Here is the MODEMdata.txt file. I wasn't sure if > >> > >> > There are no blacklisted modem drivers in >> /etc/modprobe* files >> > >>>> > http://ubuntuforums.org/archive/index.php/t-878554.html >>>> > A sample report is: http://linmodems.technion.ac.il/bigarch/archive- >>>> > nineth/msg00578.html > > > >>>>> > 00:05.0 Audio device: nVidia Corporation MCP61 High >>>>> Definition Audio (rev a2) >>>>> > High Definition Audio cards can host modem chips. >>>>> > >>>>> > For candidate card in slot 01:08.0, firmware >>>>> information and bootup >>>>> > diagnostics are: >> > PCI slot PCI >> ID SubsystemID >> Name >> > ---------- >> --------- >> --------- >> -------------- >> > 01:08.0 >> 10b9:545a 201f:545a >> Modem: ALi Corporation SmartLink >> SmartPCI563 >> > 56K Modem >> > >> > Modem interrupt assignment and sharing: >> > --- Bootup diagnostics for card in PCI slot >> 01:08.0 ---- >>>> > [ 0.379663] pci 0000:01:08.0: reg 10: [mem >>>> 0xfdbff000-0xfdbfffff] >>>> > [ 0.379668] pci 0000:01:08.0: reg 14: >>>> [io 0xcc00-0xccff] >>>> > [ 0.379697] pci 0000:01:08.0: PME# >>>> supported from D3hot D3cold >>>> > [ 0.379701] pci 0000:01:08.0: PME# >>>> disabled >>>> > [ 0.662971] serial 0000:01:08.0: PCI INT A >>>> -> Link[APC1] -> GSI 16 (level, >>>> > low) -> IRQ 16 > > >>>> > [ 0.663907] 0000:01:08.0: ttyS1 at I/O >>>> 0xcc28 (irq = 16) is a 8250 >>>> > [ 0.664512] 0000:01:08.0: ttyS2 at I/O >>>> 0xcc40 (irq = 16) is a 8250 >>>> > [ 0.665067] 0000:01:08.0: ttyS3 at I/O >>>> 0xcc50 (irq = 16) is a 8250 >>>> > [ 0.665613] 0000:01:08.0: ttyS4 at I/O >>>> 0xcc60 (irq = 16) is a 8250 >>>> > [ 0.666164] 0000:01:08.0: ttyS5 at I/O >>>> 0xcc70 (irq = 16) is a 8250 >> > >> > The PCI slot 01:08.0 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 >> DOCs/Bootup.txt about possible fixes. >> > Send dmesg.txt along with ModemData.txt to discuss@xxxxxxxxxxxxx >> > if help is needed. >> >> > a bootup process, but then enabled later. >> If modem drivers load >> > but the modem is not responsive, read >> DOCs/Bootup.txt about possible fixes. >> > Send dmesg.txt along with ModemData.txt to discuss@xxxxxxxxxxxx > > > >>>> > Predictive diagnostics for card in bus 01:08.0: >>>> > Modem >>>> chipset detected on >>>> > NAME="Modem: ALi Corporation SmartLink SmartPCI563 56K >>>> Modem" >>>> > CLASS=0703 >>>> > PCIDEV=10b9:545a >>>> > SUBSYS=201f:545a >>>> > IRQ=16 >>>> > HDA2=00:05.0 >>>> > IDENT=slamr >> > >> > For candidate modem in: 01:08.0 >> > 0703 Modem: ALi Corporation SmartLink >> SmartPCI563 56K Modem >> > Primary device ID: >> 10b9:545a >> > Support type needed or chipset: >> slamr >> > >> > >> > 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. >> >> > Support type needed or chipset: >> > >> > >> >> > If compiling is necessary packages must be >> installed, providing: >> > >> kernel-source-2.6.34-12-desktop >> > >> > >> > 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: >> > YourName, YourCountry >> > Welcome to openSUSE 11.3 "Teal" - Kernel kernel >> 2.6.34-12-desktop >> > >> > --------- end modem support lines -------- >> > >> > <<<----- I believe the modem is a : SMARTLINK >> Model SL1801 <??> Please help me >> > find a solution to using this with my NEWLY INSTALLED >> Linux System. > > I am also NOT running Unbutu, or, DEBIAN - type of Linux!?! > So, I cannot "COMPILE" a "SLAMR"-driver, with the current code... > AND...apparently the "packaged" -Precompile "SLAMR" is NOT up-to-date. > > I have all the 32-bit applications available, as you said, and still > IT (SLAMR) STILL WON'T INSTALL!!! > > I have been working on finding anything, EVEN MODPROBE and INSPROBE, for > slamr.ko (the driver-precompile), and, I get errors messages that seem almost MOCKING (LoL...my OpenSUSE ver. is 'Laughing At Me' almost I hard as I am at myself ;-) ). > > One other thing, as well... > > Is the SLMODEMD-pckg actually a "front-end"? After UN-archiving it, and, seeming yet more error-messages...I realized that it seems to just try and RUN, GRAPHICALLY-based apps, and, NOT EVEN "wvdial"!>?<! > > I hope this email is clear enough,...I have been working on this since I got home two - three hours ago, and, getting late in the evening here, and, I am getting tired. > > Please let me know if there is ANYTHING else I can do to make this INSTALL work with my Linux Box. > > Thanks, in advance... > > Sincerely, > > Jt <Janko52000@xxxxxxxxx> > > > TAG:"All these Moments will be LOST in Time,...like Tears, in the Rain." 'Roy to Deckard' from Ridley Scott's "Blade Runner", from the Book, "Do Androids Dream of Electric Sheep?" by Philip K. Dick >
