Re: Piyush, India Ubuntu 6.10 kernel 2.6.17-11-386

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Piyush

From archival info
     Primary PCI_id  8086:266d
   Subsystem PCI_id  1014:0576
   Softmodem codec or Vendor from diagnostics:
                             from    Archives: CXT, a Conexant type,

So follow the info of the attached Conexant.txt

MarvS
scanModem maintainer

On 3/6/07, piyushs@xxxxxxxxxx <piyushs@xxxxxxxxxx> wrote:
Hello,
My Modemdata.txt follows.It is for an IBM Thinkpad R52 laptop.

Thanks
Piyush.
Only plain text email is forwarded by the  DISCUSS@xxxxxxxxxxxxx List Server.
 Do use the following as the email Subject Line:
           SomeName, YourCountry Ubuntu 6.10  kernel 2.6.17-11-386
 This will alert cogent experts, and  distinguish cases in the Archives.
YourCountry will enable Country Code guidance.
 Occassionally responses are blocked by an Internet Provider mail filters.
So in a day, also check the Archived responses at
http://www.linmodems.org . Local Linux experts can be found through:
http://www.linux.org/groups/index.html
--------------------------  System information
---------------------------- CPU=i686,  Ubuntu 6.10
Linux version 2.6.17-11-386 (root@terranova) (gcc version 4.1.2 20060928
(prerelease) (Ubuntu 4.1.1-13ubuntu5)) #2 Thu Feb 1 19:50:13 UTC 2007
(Ubuntu 2.6.17-11.35-386)
 scanModem update of:  2007_March_05


USB modem not detected by lsusb

Modem or host audio card candidates have firmware information:

 PCI slot       PCI ID          SubsystemID     Name
 ----------     ---------       ---------       --------------
 00:1e.3        8086:266d       1014:0576       Modem: Intel Corporation 82801FB/FBM/FR/FW/FRW

 Modem interrupt assignment and sharing:

 --- Bootup diagnositcs for card in PCI slot 00:1e.3 ----
[17179572.232000] ACPI: PCI Interrupt 0000:00:1e.3[B] -> GSI 23 (level,
low) -> IRQ 217
[17179572.232000] ACPI: PCI interrupt for device 0000:00:1e.3 disabled

 The PCI slot 00:1e.3 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 Bootup.txt about possible fixes.
Send dmesg.txt along with ModemData.txt to discuss@xxxxxxxxxxxxx
 if help is needed.


 === Finished modem firmware and bootup diagnostics section. ===
 === Next deducing cogent software ===

ALSAversion 1.0.11
The audio card is not a modem hosting type.






 
 Conexant chipset modems section  
 --------------------------------

 Vendors 14f1 is Conexant, inheritor of the former vendor 127a Rockwell modem 
 technology.  There are also Conexant chipsets in some modems from vendors:
 	158b Allied Data Tech., 
 	1024 Zenith 
 	141a Apache Micro 
 	148d Digicom Systems.

 Linux drivers for Conexant chipset modems are provided ONLY through 
 http://www.linuxant.com/drivers.  The HCF chipset modems have a dsp 
 (digital signal processing) chip,  while the HSF lack a  dsp and 
 this function is performed by the CPU  under software direction.
 

For a crash issue with the 2.6.16 kernel, please make sure that your
kernel was not compiled with the CONFIG_4KSTACKS option is not set as
the HSF modem driver is known to requires more than 4K of stacks in a
few cases.  The are several alternate kernels supporting hsfmodem 
available at http://www.linuxant.com.  Look for their Link/URL on the
page with your needed hsfmodem package.

 To get software, go to http://www.linuxant.com/drivers
-Find the HCF or HSF menu in the left part of the screen.
-Read README.
-Read INSTALLATION.
-Click DOWNLOAD.
-Accept conditions.
-Find text: "You can download HCF (or HSF) modem packages from the driver
            download page." and click there.
-Look for your distribution, your processor, and your kernel.
-Download the matching file.
-Read again and, if you do this under Windows, print the installation
 instructions matching the kind of driver file which you downloaded.
-Now just follow these instructions.

http://www.linuxant.com/drivers/hsf/downloads-patches.php has patches
    that may be necessary for recent kernels. 

 A detailed software installation example is provided at:
   http://linmodems.technion.ac.il/archive-fourth/msg00350.html

 After loading of HSF drivers, there will be selective displayed by command: 
 #  /sbin/lsmod | grep hsf
 with an output like:
-----------
Module                  Size  Used by    Tainted: P
hsfich                119116   0  (autoclean)
hsfserial              26388   0  (autoclean)
hsfengine            1126348   0  (autoclean) [hsfserial]
hsfosspec              35328   0  (autoclean) [hsfich hsfserial hsfengine]
---------
 plus many others not modem related.
 While drivers are pre-compiled for some Linux distributions,
 the installation of the HCF/HSF packages DOES in general require kernel-source/ 
 preparation, as described in Modem/DriverCompiling.txt.

 There is good support from Linuxant.com, but first gather data. 
 In a terminal
 # su - root or prefix commands with sudo for Ubuntu related distributions.
    hsfconfig --dumpdiag
 If this command crashes your machine, please try instead:
    hsfconfig --dumpdiag --noprobe
 Send the hsfdiag.txt located in the folder /tmp/ 
 to MODEM.SUPPORT@xxxxxxxxxxxx

 There is a conflict between modules snd-intel8x0m and  hsfmc97ich.
 The snd-intel8x0m Must be loaded first or the system may hang upon hsfmc97ich insertion.
      http://linmodems.technion.ac.il/archive-fourth/msg03027.html
	 
 Rafael Espindola <rafael.espindola  AT  gmail.com> has ported old version 
 5.03.27 driver code to 2.6.12.  This is an Experts ONLY resource with current 
 information at http://www.ubuntuforums.org/showthread.php?t=180632 

 From http://www.linuxant.com/drivers,
 get  package(s) with 2.6.17.14_marv3 included in the filename.
 If such a package cannot be found, get the generic package,
 for which compiling drivers will be necessary. 

 Copy the package to your Linux partition. Unpack with:
    unzip *.zip
 Under root/admin permission, install with package with
 	sudo dpkg -i *.deb
 Should the modem hardware not be a Conexant type,
    the installation will ABORT with an informative message.

 Continue with any output instructions. Following a successfull installation,
 The modem should be detected during the root/admin command:
	wvdialconf /etc/wvdial.conf
 Edit your personal information in with:
 $  sudo gedit /etc/wvdial.conf
 See details on dialout usage in Testing.txt

	====== end Conexant section section =======

[Index of Archives]     [Linux Media Development]     [Asterisk]     [DCCP]     [Netdev]     [X.org]     [Xfree86]     [Fedora Women]     [Linux USB]

  Powered by Linux