Marv,
If you check the ModemData.txt sent by John, Puppy linux does provide
the drivers:
-------------------------- System information ----------------------------
CPU=i686, Puppy Linux
Linux 2.6.25.16 [i686 arch]
Linux version 2.6.25.16 (root@(none)) (gcc version 4.2.2) #1 Tue Aug
26 10:45:53 GMT-8 2008
scanModem update of: 2009_04_11
The modem symbolic link is /dev/modem -> ttySAGR
There are no blacklisted modem drivers in /etc/modprobe* files
Potentially useful modem drivers now loaded are:
slamr agrmodem agrserial martian_dev
There is no need to compile anything :)
He has the drivers he needs right there! Puppy configured the modem
port /dev/modem --> ttySAGR
and it could have also loaded /dev/ttySM0 if it wanted to, also since
martian_dev is also present in this nice system.
The big question here is how come the modem works beautifully in Puppy
and not in Debian the installed system. He sees IRQ conflicts and in
Puppy it just works! This is the bigger question.
Regards,
Antonio
On Wed, Apr 29, 2009 at 10:29 PM, Marvin Stodolsky
<marvin.stodolsky@xxxxxxxxx> wrote:
> RE: > John I see that you have two modems
>
> 11c1:048c & Class 0780: 11c1:044e modem hardware may interfere with
> each other.
> Probably safest to only have only one at a time physically installed,
> while testing.
>
> I would recommend first testing the
> Class 0780: 11c1:044e modem
> which uses the martian drivers.
>
> However it is not obvious to me how to satisfy compiling requirements
> on a Puppy Linux system.
>
> MarvS
>
> On Wed, Apr 29, 2009 at 8:01 PM, Antonio Olivares
> <olivares14031@xxxxxxxxx> wrote:
>> AHA,
>>
>> John I see that you have two modems :)
>>
>> I did not notice that :(
>>
>> One is the agere SVP and the other one is supported by martian modem drivers.
>>
>> The modem symbolic link is /dev/modem -> ttySAGR
>> There are no blacklisted modem drivers in /etc/modprobe* files
>> Potentially useful modem drivers now loaded are:
>> slamr agrmodem agrserial martian_dev
>>
>> Checking /proc/bus/usb/devices
>> USB modem not detected among /proc/bus/usb/devices.
>>
>> For candidate card in slot 00:08.0, firmware information and bootup
>> diagnostics are:
>> PCI slot PCI ID SubsystemID Name
>> ---------- --------- --------- --------------
>> 00:08.0 11c1:048c 11c1:044c Class 0780: 11c1:048c
>>
>> Modem interrupt assignment and sharing:
>> 16: 531 IO-APIC-fasteoi
>> --- Bootup diagnostics for card in PCI slot 00:08.0 ----
>> ACPI: PCI Interrupt 0000:00:08.0[A] -> GSI 16 (level, low) -> IRQ 16
>>
>>
>> The agere SVP modem is loaded as the following shows:
>> The modem symbolic link is /dev/modem -> ttySAGR
>>
>> and also potential drivers are here as well :
>> Potentially useful modem drivers now loaded are:
>> slamr agrmodem agrserial martian_dev
>>
>> Magically, somehow puppy also takes care of the IRQ assignment. This
>> is where the trick might be to get it working with the installed
>> Debian system?
>>
>> The other modem is supported by martian_dev (martian-full-20080625.tar.gz)
>> Predictive diagnostics for card in bus 00:09.0:
>> Modem chipset detected on
>> NAME="Class 0780: 11c1:044e "
>> CLASS=0780
>> PCIDEV=11c1:044e
>> SUBSYS=1235:044e
>> IRQ=17
>> IDENT=Agere.DSP
>>
>> For candidate modem in: 00:09.0
>> 0780 Class 0780: 11c1:044e
>> Primary device ID: 11c1:044e
>> Support type needed or chipset: Agere.DSP
>>
>>
>>
>> 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.
>>
>> Thank you John for sharing this, hope that Marv and/or others can see
>> how to determine or find out which ones are used by puppy to make the
>> modem responsive.
>>
>> Regards,
>>
>> Antonio
>>
>>
>> On Wed, Apr 29, 2009 at 5:22 PM, John <johnlostworld@xxxxxxx> wrote:
>>> Antonio I have attached the scanModem file from puppy.
>>> Also I don't change any of puppys default boot parameters, I run it from
>>> cdrom.
>>>
>>>
>>> Thank you
>>>
>>>
>>> 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 Puppy Linux
>>> Linux 2.6.25.16 [i686 arch] kernel 2.6.25.16
>>> 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, Puppy Linux
>>> Linux 2.6.25.16 [i686 arch]
>>> Linux version 2.6.25.16 (root@(none)) (gcc version 4.2.2) #1 Tue Aug 26
>>> 10:45:53 GMT-8 2008
>>> scanModem update of: 2009_04_11
>>> The modem symbolic link is /dev/modem -> ttySAGR
>>> There are no blacklisted modem drivers in /etc/modprobe* files
>>> Potentially useful modem drivers now loaded are:
>>> slamr agrmodem agrserial martian_dev
>>>
>>> Checking /proc/bus/usb/devices
>>> USB modem not detected among /proc/bus/usb/devices.
>>>
>>> For candidate card in slot 00:08.0, firmware information and bootup
>>> diagnostics are:
>>> PCI slot PCI ID SubsystemID Name
>>> ---------- --------- --------- --------------
>>> 00:08.0 11c1:048c 11c1:044c Class 0780: 11c1:048c
>>>
>>> Modem interrupt assignment and sharing:
>>> 16: 531 IO-APIC-fasteoi
>>> --- Bootup diagnostics for card in PCI slot 00:08.0 ----
>>> ACPI: PCI Interrupt 0000:00:08.0[A] -> GSI 16 (level, low) -> IRQ 16
>>>
>>> For candidate card in slot 00:09.0, firmware information and bootup
>>> diagnostics are:
>>> PCI slot PCI ID SubsystemID Name
>>> ---------- --------- --------- --------------
>>> 00:09.0 11c1:044e 1235:044e Class 0780: 11c1:044e
>>>
>>> Modem interrupt assignment and sharing:
>>> 17: 0 IO-APIC-fasteoi 164x
>>> --- Bootup diagnostics for card in PCI slot 00:09.0 ----
>>> ACPI: PCI Interrupt 0000:00:09.0[A] -> GSI 17 (level, low) -> IRQ 17
>>>
>>> === Finished firmware and bootup diagnostics, next deducing cogent software.
>>> ===
>>>
>>> Predictive diagnostics for card in bus 00:08.0:
>>> Modem chipset detected on
>>> NAME="Class 0780: 11c1:048c "
>>> CLASS=0780
>>> PCIDEV=11c1:048c
>>> SUBSYS=11c1:044c
>>> IRQ=16
>>> IDENT=agrsm
>>>
>>> For candidate modem in: 00:08.0
>>> 0780 Class 0780: 11c1:048c
>>> Primary device ID: 11c1:048c
>>> Support type needed or chipset: agrsm
>>>
>>>
>>> Use agrsm-20080203a.tar.gz at
>>> http://linmodems.technion.ac.il/packages/ltmodem/sv92/
>>> Read Modem/DOCs/Agrsm.txt
>>> -------------- end Agere Systems section -------------------
>>>
>>>
>>> Predictive diagnostics for card in bus 00:09.0:
>>> Modem chipset detected on
>>> NAME="Class 0780: 11c1:044e "
>>> CLASS=0780
>>> PCIDEV=11c1:044e
>>> SUBSYS=1235:044e
>>> IRQ=17
>>> IDENT=Agere.DSP
>>>
>>> For candidate modem in: 00:09.0
>>> 0780 Class 0780: 11c1:044e
>>> Primary device ID: 11c1:044e
>>> Support type needed or chipset: Agere.DSP
>>>
>>>
>>>
>>> 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.
>>>
>>> At http://linmodems.technion.ac.il/packages/ltmodem/kernel-2.6/martian/ get
>>> the martian-full-20080625.tar.gz and follow Readme-NOW.html
>>> 0x044e -- Mars 3 Mercury data fax only
>>> -------------- end Agere Systems section -------------------
>>>
>>> Completed candidate modem analyses.
>>>
>>> The base of the UDEV device file system is: /dev/.udev
>>>
>>> The kernel was compiled with gcc version 4.2.2 and a compiler is not
>>> installed
>>>
>>> linux-headers-2.6.25.16 resources needed for compiling are not manifestly
>>> ready!
>>> The code linking utility, ld, may be needed and is provided in the binutils
>>> package
>>> The patch utility is needed and is needed for compiling ALSA drivers, and
>>> possibly others.
>>>
>>> If compiling is necessary packages must be installed, providing:
>>> gcc-4.2 make kernel-source-2.6.25.16
>>>
>>>
>>> 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:
>>> -r-xr-xr-x 1 root root 318816 2007-10-19 09:44 /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
>>> defaultroute
>>> noipdefault
>>> noauth
>>> usepeerdns
>>> modem
>>> 115200
>>> crtscts
>>> debug
>>> asyncmap 0
>>> name "barney"
>>>
>>> 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.
>>> ==========================================================
>>>
>>> #v413 Loads modules for modems not autodetected by kernel
>>>
>>> #Intel Corporation 536EP Data Fax Modem
>>> SYSFS{vendor}=="0x8086", SYSFS{device}=="0x1040",
>>> RUN+="/sbin/pup_event_backend_modprobe Intel536"
>>>
>>> #Intel Corporation 537EP Data Fax Modem
>>> SYSFS{vendor}=="0xe159", SYSFS{device}=="0x0001",
>>> RUN+="/sbin/pup_event_backend_modprobe Intel537"
>>>
>>> #Mwave modems
>>> SYSFS{vendor}=="0x1014", SYSFS{device}=="0x007d",
>>> RUN+="/sbin/pup_event_backend_modprobe mwave"
>>>
>>> #Agere modems
>>> SYSFS{vendor}=="0x11c1", SYSFS{device}=="0x048[cf]",
>>> RUN+="/sbin/pup_event_backend_modprobe agrserial"
>>>
>>>
>>> #Lucent Integrated ISA modems - implied by presence of PC-to-ISA bridge
>>> #If you need this rule, remove the "#" from the next line. Some PCs might
>>> show a modem installed even though not actually present. Uncomment the line
>>> only if you know you have a built-in Lucent modem that is not already
>>> recognized.
>>> #SYSFS{vendor}=="0x8086", SYSFS{device}=="0x7110",
>>> RUN+="/sbin/pup_event_backend_modprobe ltserial"
>>>
>>>
>>> Checking for modem support lines:
>>> --------------------------------------
>>> /device/modem symbolic link: lrwxrwxrwx 1 root root 7 2009-04-29 16:58
>>> /dev/modem -> ttySAGR
>>> slmodemd created symbolic link /dev/ttySL0:
>>> Within /etc/udev/ files:
>>> /etc/udev/rules.d/60-udev-modem.rules:#v413 Loads modules for modems not
>>> autodetected by kernel
>>> /etc/udev/rules.d/60-udev-modem.rules:#Mwave modems
>>> /etc/udev/rules.d/60-udev-modem.rules:#Agere modems
>>> /etc/udev/rules.d/60-udev-modem.rules:#Lucent Integrated ISA modems -
>>> implied by presence of PC-to-ISA bridge
>>> /etc/udev/rules.d/60-udev-modem.rules:#If you need this rule, remove the "#"
>>> from the next line. Some PCs might show a modem installed even though not
>>> actually present. Uncomment the line only if you know you have a built-in
>>> Lucent modem that is not already recognized.
>>> Within /etc/modprobe.conf files:
>>>
>>> Within any ancient /etc/devfs files:
>>>
>>> Within ancient kernel 2.4.n /etc/module.conf files:
>>> /etc/modules/firmware.dep.2.6.25.16:#a firmware pkg can have a post-install
>>> script -- see slmodem example.
>>> /etc/modules/firmware.dep.2.6.25.16:#analog modem drivers...
>>> /etc/modules/firmware.dep.2.6.25.16:dgcmodem:dgcusbdcp.ko
>>> /etc/modules/firmware.dep.2.6.25.16:ltmodem:ltserial.ko
>>> /etc/modules/firmware.dep.2.6.25.16:slmodem:slamr.ko,slusb.ko,snd-via82xx-modem.ko,snd-atiixp-modem.ko,snd-intel8x0m.ko,snd-hda-intel.ko
>>> --------- end modem support lines --------
>>>
>>>
>>>
>>
>
