Ariel, Please try to get diagnostic information under Microsoft, as instructed earlier. MarvS On Fri, Mar 13, 2009 at 12:34 PM, Ariel Talavera <talavera@xxxxxxxxxx> wrote: > Hi there, > > I tried to install the driver for the modem as mentioned below with no > success. The computer still not recognizing the modem. More help with this > problem will be extremely appreciated. > > Best regards, > Ariel > > > Marvin Stodolsky wrote: >> >> Attached is a scanModem update. >> >> MarvS >> >> On Tue, Mar 10, 2009 at 7:11 PM, Marvin Stodolsky >> <marvin.stodolsky@xxxxxxxxx> wrote: >> >>> >>> Ariel, >>> >>> your system, CPU=x86_64, Linux version 2.6.27-13-generic, with >>> >>> High Definition Audio card , hardware type 0403, and PCI identifier >>> 1002:aa20 has not been encountered before under Linux. It is not >>> responding to diagnostics which would reveal the largest family of >>> modem chips it could host, leaving the possibility of a Conexant chip. >>> See the appended section on Microsoft diagnostics, for running tests >>> thereunder. >>> >>> Separately I'll send you a scanModem update, but most likely further >>> info may not be obtained. >>> >>> After these added diagnostics, most likely will have to proceed with >>> the following, for Conexant chip modems. >>> From http://www.linuxant.com/drivers/hsf/downloads.php get from near the >>> bottom >>> hsfmodem-7.80.02.03x86_64full.tar.gz >>> Unpack with: >>> $ tar zxf hsf*.tar.gz >>> and follow the instructions in the new folder. Prefix the recommended >>> COMMANDs as: >>> $ sudo COMMAND >>> as root permission will be needed. >>> >>> MarvS >>> >>> Using MicroSoft(MS) Windows: >>> ----------------------------- >>> MS installations do generally have adequate diagostic capability. Try >>> the following >>> routine 1), beginning with mouse clicks on: >>> 1) 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. 14F1 is the Vendor ID for Conexant. >>> >>> Click the DriverDetails Tab, to reveal Ven_ID Dev_ID details too >>> >>> Click the Diagnostics Tab (if present). 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. >>> >>> 2) Open a COMM console. Send ATI commands to the modem (ATI, ATI1, >>> ATI2, etc) >>> which may elicit chipset and driver information. Here is an example: >>> ATI3 - Agere SoftModem Version 2.1.22 >>> ATI5 - 2.1.22, AMR Intel MB, AC97 ID:SIL REV:0x27 >>> successfully identifying an Agere SoftModem chipset, both by name and >>> through >>> the softmodem SIL ID: AC97 ID:SIL REV:0x27 >>> >>> On Tue, Mar 10, 2009 at 3:44 PM, Ariel Talavera <talavera@xxxxxxxxxx> >>> wrote: >>> >>>> >>>> Hi there, >>>> >>>> I am having problems to recognize the modem of the laptop HP 8530p. >>>> >>>> The output of the command "$ sudo lspci -s 01:00.1 -nv" is >>>> >>>> 01:00.1 0403: 1002:aa20 >>>> Subsystem: 103c:aa20 >>>> Flags: bus master, fast devsel, latency 0, IRQ 17 >>>> Memory at d8310000 (64-bit, non-prefetchable) [size=16K] >>>> Capabilities: [50] Power Management version 3 >>>> Capabilities: [58] Express Legacy Endpoint, MSI 00 >>>> Capabilities: [a0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 >>>> Enable- >>>> Capabilities: [100] Vendor Specific Information <?> >>>> Kernel driver in use: HDA Intel >>>> Kernel modules: snd-hda-intel >>>> >>>> >>>> And after running ./scanModem I got the following ModemData.txt >>>> >>>> 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 kernel 2.6.27-13-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@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=x86_64, Linux version 2.6.27-13-generic (buildd@crested) (gcc >>>> version >>>> 4.3.2 (Ubuntu 4.3.2-1ubuntu12) ) #1 SMP Thu Feb 26 07:31:49 UTC 2009 >>>> scanModem update of: 2009_03_01 >>>> >>>> >>>> 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. >>>> >>>> There are no blacklisted modem drivers in /etc/modprobe* files >>>> Potentially useful modem drivers now loaded are: >>>> snd_hda_intel >>>> >>>> >>>> Thanks in advanced, >>>> Ariel >>>> >>>> >>>> >>>> >>>> >>>> > >
