Ayako
First complete compiling support:
compiling is necessary packages must be installed, providing:
gcc-4.2 make kernel-source-2.6.24.7-desktop586-1mnb
Then for the modem specific issues:
Support packages for 2.6.n kernels are at:
http://linmodems.technion.ac.il/packages/ltmodem/kernel-2.6/martian/
Always use the most update for kernels after 2.6.20, currently
martian-full-20080625.tar.gz
For kernels 2.6.20 and less, usr martian-full-20080407.tar.gz.
MarvS
scanModem maintainer
On Mon, Nov 3, 2008 at 11:31 PM, Ayako Keogh <ayako.keogh@xxxxxxxxx> wrote:
> Hi All,
>
> I am trying to get one of the two (!) Lucent chipset modems on my system
> working.
>
> I have a Xircom Realport PCMCIA LAN + Modem Combo card and also an internal
> modem on the laptop.
>
> I am running:
> Mandriva 2008
> Toshiba 4090XDVD
>
> I have looked at the Martian packages listed on
> linmodems.technion.ac.il/packages/ltmodem/kernel-2.6/martian/ (and also in
> other directories) but I cannot find an RPM for Mandriva. Does one exist?
>
> Attached is my ModemData.txt file. Please advise if there is any help for
> me!
> Thanks,
> Matt
>
>
>
> 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 Mandriva Linux release 2008.1 (Official) for
> i586
> Kernel 2.6.24.7-desktop586-1mnb on an i686 / kernel
> 2.6.24.7-desktop586-1mnb
> With this Subject Line cogent experts will be alerted, and useful case
> names left in the Archive.
> YourCountry will enable Country specific guidance. Linux experts in
> YourCountry
> 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, Mandriva Linux release 2008.1 (Official) for i586
> Kernel 2.6.24.7-desktop586-1mnb on an i686 /
> Linux version 2.6.24.7-desktop586-1mnb (qateam@xxxxxxxxxxxxxxxxxx) (gcc
> version 4.2.3 (4.2.3-6mnb1)) #1 SMP Mon Jul 28 15:01:18 EDT 2008
> scanModem update of: 2008_10_24
> The modem symbolic link is /dev/modem -> ttyS2
> There are no blacklisted modem drivers in /etc/modprobe* files
> Attached USB devices are:
> ID 045e:00f6 Microsoft Corp.
>
> USB modems not recognized
>
> For candidate card in slot 00:07.0, firmware information and bootup
> diagnostics are:
> PCI slot PCI ID SubsystemID Name
> ---------- --------- --------- --------------
> 00:07.0 11c1:0441 1179:0001 Communication controller:
> Agere Systems 56k WinModem
>
> Modem interrupt assignment and sharing:
> 3: 6298 XT-PIC-XT
> --- Bootup diagnostics for card in PCI slot 00:07.0 ----
>
> For candidate card in slot 00:0a.0, firmware information and bootup
> diagnostics are:
> PCI slot PCI ID SubsystemID Name
> ---------- --------- --------- --------------
> 00:0a.0 1179:0701 1179:0001 Communication controller:
> Toshiba America Info Systems FIR Port
>
> Modem interrupt assignment and sharing:
> 11: 20977 XT-PIC-XT uhci_hcd:usb1, yenta, yenta, ESS
> Maestro, eth0
> --- Bootup diagnostics for card in PCI slot 00:0a.0 ----
> ACPI: PCI Interrupt 0000:00:0a.0[A] -> Link [LNKC] -> GSI 11 (level, low) ->
> IRQ 11
>
> For candidate card in slot 16:00.1, firmware information and bootup
> diagnostics are:
> PCI slot PCI ID SubsystemID Name
> ---------- --------- --------- --------------
> 16:00.1 115d:0103 115d:1181 Serial controller: Xircom
> Cardbus Ethernet + 56k Modem
>
> Modem interrupt assignment and sharing:
> 11: 20977 XT-PIC-XT uhci_hcd:usb1, yenta, yenta, ESS
> Maestro, eth0
> --- Bootup diagnostics for card in PCI slot 16:00.1 ----
> PCI: Enabling device 0000:16:00.1 (0000 -> 0003)
> ACPI: PCI Interrupt 0000:16:00.1[A] -> Link [LNKA] -> GSI 11 (level, low) ->
> IRQ 11
> 0000:16:00.1: ttyS1 at I/O 0x1080 (irq = 11) is a 16550A
>
> === Finished firmware and bootup diagnostics, next deducing cogent software.
> ===
>
> Predictive diagnostics for card in bus 00:07.0:
> Modem chipset detected on
> NAME="Communication controller: Agere Systems 56k WinModem "
> CLASS=0780
> PCIDEV=11c1:0441
> SUBSYS=1179:0001
> IRQ=3
> IDENT=Agere.DSP
>
> For candidate modem in: 00:07.0
> 0780 Communication controller: Agere Systems 56k WinModem
> Primary device ID: 11c1:0441
> Support type needed or chipset: Agere.DSP
>
>
> ----------------end Softmodem section --------------
>
> The modem has a Lucent/Agere/LSI Mars or Apollo DSP (digital signal
> processing) chipset.
> Support packages for 2.6.n kernels are at:
> http://linmodems.technion.ac.il/packages/ltmodem/kernel-2.6/martian/
> Always use the most update for kernels after 2.6.20, currently
> martian-full-20080625.tar.gz
> For kernels 2.6.20 and less, usr martian-full-20080407.tar.gz.
>
> See DOCs/AgereDSP.txt for Details.
>
>
> Vendor 115d is XIRCOM, which was purchased by Intel
> The following devices have Lucent/AgereSystems DSP chipsets supported by
> the
> Martian variant of the AgereSystems ltmodem software.
>
> XIRCOM 0x115d 0x0000-0x000F
> XIRCOM 0x115d 0x0440-0x045c
> XIRCOM 0x115d 0x0010-0x03ff
>
>
>
> Predictive diagnostics for card in bus 16:00.1:
> Modem chipset detected on
> NAME="Serial controller: Xircom Cardbus Ethernet + 56k Modem "
> CLASS=0700
> PCIDEV=115d:0103
> SUBSYS=115d:1181
> IRQ=11
> IDENT=Agere.DSP
>
> For candidate modem in: 16:00.1
> 0700 Serial controller: Xircom Cardbus Ethernet + 56k Modem
> Primary device ID: 115d:0103
> Support type needed or chipset: Agere.DSP
>
>
> ----------------end Softmodem section --------------
>
> The modem has a Lucent/Agere/LSI Mars or Apollo DSP (digital signal
> processing) chipset.
> Support packages for 2.6.n kernels are at:
> http://linmodems.technion.ac.il/packages/ltmodem/kernel-2.6/martian/
> Always use the most update for kernels after 2.6.20, currently
> martian-full-20080625.tar.gz
> For kernels 2.6.20 and less, usr martian-full-20080407.tar.gz.
>
> See DOCs/AgereDSP.txt for Details.
>
>
> Vendor 115d is XIRCOM, which was purchased by Intel
> The following devices have Lucent/AgereSystems DSP chipsets supported by
> the
> Martian variant of the AgereSystems ltmodem software.
>
> XIRCOM 0x115d 0x0000-0x000F
> XIRCOM 0x115d 0x0440-0x045c
> XIRCOM 0x115d 0x0010-0x03ff
>
>
>
> Predictive diagnostics for card in bus 00:0a.0:
> Modem chipset not detected on
> NAME="Communication controller: Toshiba America Info Systems FIR Port "
> CLASS=0780
> PCIDEV=1179:0701
> SUBSYS=1179:0001
> IRQ=11
>
> For candidate modem in: 00:0a.0
> 0780 Communication controller: Toshiba America Info Systems FIR Port
> Primary device ID: 1179:0701
> Support type needed or chipset:
>
>
> ----------------end Softmodem section --------------
>
> scanModem could not identify the Support Type needed from diagnosics or
> archives.
> If an alternative boot into Microsoft windows can be done, do mouse
> clicks on:
> Start > Settings > Control Panel > Classical View (for Window XP) > System
>> Hardware > Device Manager > Modems > Click on the + > Modem. Double click
>> to
> expand the graphic. Manufacturer information may be displayed. For example,
> CXT
> stands for Conexant. Click the Diagnostics Tab. Record any hardware ID or
> vendor
> and device information.
> Next do the Query Modem and record the ATI specifications displayed such as:
> ATI3 - Agere SoftModem Version 2.1.22
> ATI5 - 2.1.22, AMR Intel MB, AC97 ID:SIL REV:0x27
> Try to identify the modem setup file, with name perhaps MODEM.INF.
> If may contain chipset Vendor informaton.
>
>
> Vendor 115d is XIRCOM, which was purchased by Intel
> The following devices have Lucent/AgereSystems DSP chipsets supported by
> the
> Martian variant of the AgereSystems ltmodem software.
>
> XIRCOM 0x115d 0x0000-0x000F
> XIRCOM 0x115d 0x0440-0x045c
> XIRCOM 0x115d 0x0010-0x03ff
>
>
> Completed candidate modem analyses.
>
> The base of the UDEV device file system is: /dev/.udev
>
> The kernel was compiled with gcc version 4.2.3 and a compiler is not
> installed
>
> linux-headers-2.6.24.7-desktop586-1mnb resources needed for compiling are
> not manifestly ready!
>
> If compiling is necessary packages must be installed, providing:
> gcc-4.2 make kernel-source-2.6.24.7-desktop586-1mnb
>
>
> 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:
> -rwsr-xr-t 1 root root 316424 2008-06-03 16:32 /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
> lock
> noauth
> noipdefault
> usepeerdns
>
> 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/DOCs/YourSystem.txt concerning other COMM channels: eth0
> Which can interfere with Browser naviagation.
>
> Don't worry about the following, it is for experts should trouble shooting
> be necessary.
> ==========================================================
>
> L modem ttyS2
> M slamr0 c 242 0
> M slamr1 c 242 1
> M slusb0 c 243 0
> M slusb1 c 243 1
> Checking for modem support lines:
> --------------------------------------
> /device/modem symbolic link: lrwxrwxrwx 1 root root 5 2008-11-03 20:20
> /dev/modem -> ttyS2
> slmodemd created symbolic link /dev/ttySL0:
> Within /etc/udev/ files:
> /etc/udev/devices.d/modem.nodes:L modem ttyS2
> /etc/udev/rules.d/50-udev-default.rules:KERNEL=="mwave",
> NAME="modems/mwave", GROUP="uucp"
> /etc/udev/rules.d/00-hsf.rules:KERNEL=="ttySHSF0", SYMLINK="modem"
> Within /etc/modprobe.conf files:
>
> Within any ancient /etc/devfs files:
>
> Within ancient kernel 2.4.n /etc/module.conf files:
> /etc/modules.conf:alias /dev/modem /dev/ttySHSF
> --------- end modem support lines --------
>
>
>
