I need help with my hard-modem
|
View:
New views
3 Messages
—
Rating Filter:
Alert me
|
 |
I need help with my hard-modem
by Alexei Timashkov
::
Rate this Message:
Thank you guys, in advance!
Only plain text email is forwarded by the Discuss@... List Server, as HTML can contain viruses. Use as the email Subject Line: YourName, YourCountry kernel 2.6.31-14-generic 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@... 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, Linux version 2.6.31-14-generic (buildd@rothera) (gcc version 4.4.1 (Ubuntu 4.4.1-4ubuntu8) ) #48-Ubuntu SMP Fri Oct 16 14:04:26 UTC 2009 scanModem update of: 2009_09_15 The dkms driver upgrade utilities are installed, There are no blacklisted modem drivers in /etc/modprobe* files Potentially useful modem drivers now loaded are: Attached USB devices are: ID 05ac:0221 Apple, Inc. Keyboard (Aluminium) (ISO) ID 04b8:010f Seiko Epson Corp. Perfection 1250 ID 07d1:3c03 D-Link System DWL-G122 802.11g Adapter [ralink rt73] ID 0aec:3260 Neodio Technologies Corp. 7-in-1 Card Reader ID 05ac:1006 Apple, Inc. Hub in Aluminum Keyboard ID 058f:6254 Alcor Micro Corp. USB Hub If a cellphone is not detected, see http://ubuntuforums.org/archive/index.php/t-878554.html A sample report is: http://linmodems.technion.ac.il/bigarch/archive-nineth/msg00578.html If a USB modem or cellphone is attached and was not detected, please provide available information in your request to discuss@... For candidate card in slot 05:07.0, firmware information and bootup diagnostics are: PCI slot PCI ID SubsystemID Name ---------- --------- --------- -------------- 05:07.0 12b9:1008 12b9:00d3 Serial controller: 3Com Corp, Modem Division 56K FaxModem Model 5610 Modem interrupt assignment and sharing: 17: 396 IO-APIC-fasteoi eth0, serial --- Bootup diagnostics for card in PCI slot 05:07.0 ---- [ 0.091260] pci 0000:05:07.0: reg 10 io port: [0xa000-0xa007] [ 0.091287] pci 0000:05:07.0: supports D2 [ 0.091290] pci 0000:05:07.0: PME# supported from D0 D2 D3hot D3cold [ 0.091293] pci 0000:05:07.0: PME# disabled [ 0.799714] serial 0000:05:07.0: PCI INT A -> Link[APC2] -> GSI 17 (level, low) -> IRQ 17 [ 0.799766] 0000:05:07.0: ttyS1 at I/O 0xa000 (irq = 17) is a 16550A The PCI slot 05:07.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@... if help is needed. === Finished firmware and bootup diagnostics, next deducing cogent software. === Predictive diagnostics for card in bus 05:07.0: Modem chipset detected on NAME="Serial controller: 3Com Corp, Modem Division 56K FaxModem Model 5610 " CLASS=0700 PCIDEV=12b9:1008 SUBSYS=12b9:00d3 IRQ=17 IDENT=USrobotics.serial For candidate modem in: 05:07.0 0700 Serial controller: 3Com Corp, Modem Division 56K FaxModem Model 5610 Primary device ID: 12b9:1008 Support type needed or chipset: USrobotics.serial Vendor 10b7 3COM Inc. purchased the vendor 12b9 US Robotics modem technology. Their winmodems have no Linux support. Their controller chipset modems are supported by the Linux serial drivers. The PCI id 12b9:1008 modem is Supported. PCI ID Name Support status ------------------------------------------------------------------------------- 10b7:1006 3COM 0038TA AC101 - TF Mini-PCI winmodem, not supported 10b7:1007 3COM 3C556 V.90 Mini-PCI winmodem, not supported 12b9:1006 US Robotics 3cp803598 Voice winmodem, not supported 12b9:1007 US Robotics ERL3263A-0 DF GWPCI PC99 winmodem, not supported 12b9:0062 US Robotics erk41926a-0.6 usr 56k serial driver supported 12b9:1008 US Robotics 3cp803598 serial driver supported sudo wvdialconf wvtest , should detect the modem. Read DOCs/Testing.txt ====== end 3COM section ======= Completed candidate modem analyses. The base of the UDEV device file system is: /dev/.udev Versions adequately match for the compiler installed: 4.4.1 and the compiler used in kernel assembly: 4.4.1 Minimal compiling resources appear complete: make utility - /usr/bin/make Compiler version 4.4 linuc_headers base folder /lib/modules/2.6.31-14-generic/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 settings of: /etc/ppp/options asyncmap 0 noauth crtscts lock hide-password modem proxyarp lcp-echo-interval 30 lcp-echo-failure 4 noipx 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 eth1 wlan0 wmaster0 Which can interfere with Browser naviagation. 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: Within /etc/modprobe.conf files: /etc/modprobe.d/alsa-base.conf:options snd-atiixp-modem index=-2 /etc/modprobe.d/alsa-base.conf:options snd-via82xx-modem index=-2 /etc/modprobe.d/blacklist-modem.conf:# Uncomment these entries in order to blacklist unwanted modem drivers /etc/modprobe.d/blacklist-modem.conf:# blacklist snd-atiixp-modem /etc/modprobe.d/blacklist-modem.conf:# blacklist snd-via82xx-modem Within any ancient /etc/devfs files: Within ancient kernel 2.4.n /etc/module.conf files: --------- end modem support lines -------- |
|
|
Re: I need help with my hard-modem
by Antonio Olivares-2
::
Rate this Message:
Alexei,
Your modem is supported through native serial driver as reported by scanModem. To access your modem, run $ sudo wvdialconf /etc/wvdial.conf and it should find your modem: <quote> For candidate modem in: 05:07.0 0700 Serial controller: 3Com Corp, Modem Division 56K FaxModem Model 5610 Primary device ID: 12b9:1008 Support type needed or chipset: USrobotics.serial Vendor 10b7 3COM Inc. purchased the vendor 12b9 US Robotics modem technology. Their winmodems have no Linux support. Their controller chipset modems are supported by the Linux serial drivers. The PCI id 12b9:1008 modem is Supported. PCI ID Name Support status ------------------------------------------------------------------------------- 12b9:1008 US Robotics 3cp803598 serial driver supported sudo wvdialconf wvtest , should detect the modem. Read DOCs/Testing.txt ====== end 3COM section ======= </quote> If wvdialconf does not find the modem, it could be because of: For candidate card in slot 05:07.0, firmware information and bootup diagnostics are: PCI slot PCI ID SubsystemID Name ---------- --------- --------- -------------- 05:07.0 12b9:1008 12b9:00d3 Serial controller: 3Com Corp, Modem Division 56K FaxModem Model 5610 Modem interrupt assignment and sharing: 17: 396 IO-APIC-fasteoi eth0, serial --- Bootup diagnostics for card in PCI slot 05:07.0 ---- [ 0.091260] pci 0000:05:07.0: reg 10 io port: [0xa000-0xa007] [ 0.091287] pci 0000:05:07.0: supports D2 [ 0.091290] pci 0000:05:07.0: PME# supported from D0 D2 D3hot D3cold [ 0.091293] pci 0000:05:07.0: PME# disabled [ 0.799714] serial 0000:05:07.0: PCI INT A -> Link[APC2] -> GSI 17 (level, low) -> IRQ 17 [ 0.799766] 0000:05:07.0: ttyS1 at I/O 0xa000 (irq = 17) is a 16550A The PCI slot 05:07.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@... if help is needed. Regards, Antonio On 11/1/09, Alexei Timashkov <timashkov@...> wrote: > Thank you guys, in advance! > |
|
|
|
| Free embeddable forum powered by Nabble | Forum Help |
