Good morning Vatsala
I can see that took a lot of typing! at the very least we should be able to sort out your LAN tonight and save having to do that again. Lesson in softmodems: (some of this is covered in the info from scanModem) soft modems have two layers of complexity fromour point of view. There is a controller chipset, in this case SiS 1039:7013. These are really common, the desktop I am sitting at has one as well. Whats under that is whats really important, there is a chipset and/or codec which may or may not be supported under linux. The codec in your modem does not appear to be recognised, but we may strike it lucky! Time will tell. I see you have posted to the linmodems list and they told you to post back the results of scanModem - can you do that asap so that any uselful info gets to us before this evening? On Mon, 01 Nov 2004 11:16:23 +1300 eBhakta <[EMAIL PROTECTED]> wrote: > Good Morning all! > > Here are the (typed) results (in WinXP)... > > ============================ > ============================ > > "General" tab: > > "Agere Systems AC'97 Modem" > > Location: PCI bus 0, device 2, function 6 > > "The device is working properly." > > ============================ > > "Diagnostics" tab: "Modem Information" > > Hardware ID: PCI\VEN_1039&DEV_7013&SUBSYS_82161033&REV_A0 > > ============================ > > "Query Modem" results: > > ATQ0V1E0 => Success > AT+GMM => H.324 video-ready rev. 1.0 > AT+FCLASS=? => 0,1,8 > AT#CLS=? => COMMAND NOT SUPPORTED > AT +GCI? => +GCI:7E > AT+GCI=? => > +GCI:(00,04,07,09,0A,0D,0F,14,16,19,1B,20,25,26,27,2B,2D,2E,31,33,35,36,37,3 > C,3D,46,49,4F,50,51,52,53,54,57,58,59,5E,61,62,64,68,69,6C,70,73,77,7B,7E,7F > ,82,83,84,85,87,88,89,8A,8B,8C,8E,98,9C,9F,A0,A1,A5,A6,A9,AE,B2,B3,B4,B5,B7, > B8,BB,BC,C1) > ATI1 => Success > ATI2 => Success > ATI3 => Agere SoftModem Version 2.1.29 > ATI4 => Built on 04/29/2003 09:58:20 > ATI5 => 2.1.29, AMR SIS MB, AC97 ID:SIL REV:0x27, 09 > ATI6 => Success > ATI7 AMR SiS MB > > ================================== > End of results in WinXP for NEC Versa C160. > ================================== > ================================== > > Now for the (typed) scanModem "ModemDATA.txt" file results in Linux > ubuntu... > > ================================== > > ------------ System information ------------- > debian testing/unstable on System with processor: i686 > support by kernel: 2.6.8.1-3-386 > assembled with compiler: 3.3.4 > no gcc compiler installed > A /dev/modem symbolic link is not set. > COMM services are not active > > Under 2.6.n kernels, there is currently modem support by: > the more expensive Controller chipset modems using the open > source serial code > Conexant software downloaded through http://www.linuxant.com > Smartlink slmodem drivers, including USB hardware > USB modems using the Open Source acm.ko driver > Lucent DSP (digital signal processing) chipsets but NOT: > soft modems (though some are supported by slmodem drivers) > Intel 536EP and 537 modems > For all other modems, support projections are not available as of this > update=2004_Oct_26 > > Resident PPP support modules are properly uncompressed. > An AC97 modem codec was not detected > > --------------- End SIL_id section ---------------- > > Path to lspci is: /usr/bin/lspci > --------------- lspci scan -------------------- > PCI_bus > 0000:00:00.0 Host bridge: Silicon Integrated Systems [SiS] 740 Host (rev 01) > 0000:00:01.0 PCI bridge: Silicon Integrated Systems [SiS] Virtual PCI-to-PCI > bridge (AGP) > 0000:00:02.0 ISA bridge: Silicon Integrated Systems [SiS] SiS962 [MuTIOL > Media IO] (rev 25) > 0000:00:02.1 SMBus: Silicon Integrated Systems [SiS]: Unknown device 0016 > 0000:00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] > 0000:00:02.6 Modem: Silicon Integrated Systems [SiS] AC'97 Modem Controller > (rev a0) > 0000:00:02.7 Multimedia audio controller: Silicon Integrated Systems [SiS] > Sound Controller (rev a0) > 0000:00:03.0 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 > Controller (rev 0f) > 0000:00:03.1 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 > Controller (rev 0f) > 0000:00:03.2 USB Controller: Silicon Integrated Systems [SiS] USB 2.0 > Controller > 0000:00:04.0 Ethernet controller: Silicon Integrated Systems [SiS] SiS900 > PCI Fast Ethernet (rev 91) > 0000:00:0a.0 CardBus bridge: Texas Instruments PCI4510 PC card Cardbus > Controller (rev02) > 0000:00:0a.1 Firewire (IEEE 1394): Texas Instruments PCI 4510 IEEE-1394 > Controller > 0000:01:00.0 VGA compatible controller: Silicon Integrated Systems [SiS] > 65x/M650/740 PCI/AGP VGA Display Adapter > ------------------------------------------------- > > Modem candidates are at PCI_busses: 0000:00:02.6 > Providing detail for device at PCI_bus 0000:00:02.6 > with vendor-ID:device-ID > ----:---- > Class0703: 1039:7013 Modem: Silicon Integrated Systems [SiS] AC'97 Modem > Controller (rev a0) > (prog-if 00 [Generic]) > Subsystem 1033:8216 NEC Corporation: Unknown device 8216 > Flags: medium devsel, IRQ 5 > I/O ports at 1000 > I/O ports at 2400 [size=128] > > Internel_test: ./scanModem test 1039:7013 1033:8216 debian 2.6.8.1-3-386 > 3 > > The soft modem Subsystem operates under a controller > 1039:7013 SiS 630 > capable of supporting under Linux AT LEAST modem Subsystem chips from > manufacturers: > Pctel > AgereSystems > Intel > Smartlink > Checking Subsystem against prior reports to [EMAIL PROTECTED] > From prior reports, the codec of the Subsystem is: > The Codec is not recognized. > > Information on several modem chipset providers is provided below, > because ambiguities remain on the correct choice of supporting software. > > === Checking PCI IDs through chipset providers and modem assemblers === > > Vendor 11c1 corresponds to Lucent Technologies or subsidiary Agere Systems, > Inc. > Information is at: http://www.agere.com/client/modem_dsp.html. Produced are > both: > 1) modems identifiable from their primary PCI IDs and > 2) soft modem Subsystem chips requiring identification through codec > readouts. > > AgereSoftModem drivers only support AC97 or MC97 modem controllers with > codecs characterized by one of: > SIL_id = 39 > mc97 codec is SIL27 > 0x27 , as output by modem diagnostics under Microsoft Windows (Note: > this is there in the WinXP diagnostics results above:) > If uncertain, identify the softmodem codec through tests described in > Modem/SoftModem.txt > Support is currently ONLY for 2.4.n kernels (Note: looks like the kernel > will need to be recompiled... as Nick concluded correctly) and the following > modem controllers: > 8086: (2416 2426 2446 7196 2486 24C6), with 8086 == Intel > 1039:7013 SiS :) > 1106:3068 VIA > Access the soft modem software through code sponsor IBM at: > http://www-3.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-52698 > The SmartLink slmodem-2.9.9 may serve for modems not served by this > AgereSystems software. > > The ltmodem drivers do NOT support this modem: 1039:7013 :( > > SmartLink at http://www.smlink.com/ owns vendor IDs 163c 2000 2003 2004 > Products include the: > 163c:5459 SmartPC1561 modem and chipsets for other Brandname PCI modems; > a chipset for USB modems, the SmartUSB56 (ST7554) based modems > with vendor/product usb ids: 0483:7554 supported. > Fax support is provided, though the AT&F command is not supported by the > drivers. > Multiple modems on the same PC are supported. > There is a success report for 64 bit AMD x86_64 processor mother boards: > http://linmodems.technion.ac.il/archive-fourth/msg02594.html > > Download software through: > http://www.smlink.com/main/index1.php?ln=en&main_id=40 > with backups at http://linmodems.technion.ac.il/resources.html > > There are two support options: > 1) The slmodem-2.9.n series provides after compiling: > slamr - the low level driver > slusb - the low level driver for USB modems > slmodemd - a daemon creating modem ports and providing higher level > functions. > Loading of slamr with: > # modprobe slamr > will generate a warning, for soft modems with non-SmartLink chips. > So long as the driver loads, just ignore it. Read related kernel messages > with: > # dmesg | grep slamr > which may give a report including: "slamr: mc97 codec is SILnm" , with n,m > numbers > a) For such responses, there are good prospects for the modem being > supported. > b) For a response like: slamr: mc97 codec is BCM64 > the soft modem has a Broadcom codec and the 2nd alternative must be > tested. > > 2) In recent 2.6.n kernel releases there is a driver snd-intel8x0m.ko , > for which the slmodem-2.9.9-alsa slmodemd provides port creation and high > level services. > Even if 1) serves well, it is worth testing 2) because: > a) The driver snd-intel8x0m.ko will come with future kernel releases, > while YOU would have to compile slamr with every kernel upgrade. > b) The slmodemd remains functional with minor 2.6.n upgrades, and thus > does NOT have to be > compiled again. > c) there will not be a warning about "Tainted kernel" upon driver > insertion. > > For further implementation tails on 1) and 2), read Modem/Slmodem.txt > > === Checking PCI IDs through chipset providers and modem assemblers === > Vendor 1039 is SiS, Silicon Integrated System. > > ===== PCI_ID checking completed ===== > Update=2004_Oct_26 > > Analyzing information for PCMCIA device at PCI Bus 00:0a.0 > GREPping for an inserted PCMCIA modem with filter: (?)ommunication > If a PCMCIA modem is currently inserted and the sockets activated by > /etc/init.d/pcmcia start > then the PCMCIA bridge is NOT transparent. (Note: no PCMCIA modem > installed) > > If the modem is known to have a Lucent digital signal processing chipset, > then PCMCIA.tar.gz variant assembled by Joern Wustenfeld is necessary, > rather then the standard ltmodem-8.26a9.tar.gz at http://ltmodem.heby.de/ > GCCCversion= > The following information blocks just query some ppp support items. > > ====================================== > grep ppp /etc/modprobe.conf > --------------------------------------------- > > Be sure to read the section about ppp related modules and aliases in > Modem/General.txt > > A port needed for the PPP protocol is absent!!! (Note: Uh oh... modem > "PPP" works okay under WinXP) > echo " crw------- 1 root root 108, 0 Dec 31 1969 /dev/ppp" > > A /dev/modem symbolic link is not present > > No devfsd.conf file found, indicated absense of the devfsd daemon > package > for device file system (devfs) symbolic link support. > > DEVFSD= > ------ dmesg queries ------ > Enabling disabled K7/SSE Support. > ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 7 10) *0, disabled. > > There are Debian packages with modem drivers from Smartlink: > sl-modem-daemon - SmartLink software modem daemon > sl-modem-source - SmartLink software modem driver - module building > source > Many modem subSystems serving under AC97/MC97 Controllers are also > supported. > > The Modem/DriverCompiling.txt is a MUST READ, > if you are experienced in configuring kernel-source/ (Note: newbie here...) > or get "unresolved symbols" upon driver insertion. > > Most recent WinModem fixes are in: > http://linmodems.technion.ac.il/FAQ.html > > ======================================= > End of results in Linux "ubuntu" for NEC Versa C160. > ======================================= > ======================================= > > Seems from these results the modem should be go under Linux... (all going > well, say a prayer...). Thanks for all the help. Next step is obviously the > compiling etc., to get the thing going... :$ Hmm... Help! > > Regards, > Bhaktavatsala Dasa (Vatsala) > > @ http://homepages.ihug.co.nz/~vatsalaji - Hare Krishna! > > ----- Original Message ----- > From: "Rik Tindall" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> > Sent: Sunday, October 31, 2004 11:24 PM > Subject: Re: Fw: Re:Getting connected with Linux... > > > > Nick Rout wrote: > > > > > <>On Sun, 2004-10-31 at 22:50, Rik Tindall wrote: > > > > > >>A simple other option: > > >> > > >>If the laptop still boots WinXP, go to Control Panel - System - Hardware > > >>Devices .. > > >> > > >>Post us back exactly what the modem is listed as there - brand, model, > > >>number etc. > -- Nick Rout <[EMAIL PROTECTED]>
