Re: FC9, compile error, period size 48

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

 



Dear MarvS, 


On Monday June 30 2008, you wrote:
> Daniel,
> 
> There should be a
> Carrier Check = no
> in your /etc/wvdial.conf  file
> as /dev/pts/N ports do not yet have Sound capability.

I tried this.   The connection was a bit better, but I am 
not sure whether this slight improvement is related to 
the "Carrier Check = no" in wvdial.conf. 

> Even with
> Carrier Check = no
> there are occasionally still
> No Carrier outputs which are harmless
> 
> What is your modem type?

In a german forum, I was told that it is a Motorola HDAudio SM56, 
but I am not sure. 

> Wouldn't hurt to send me the ModemData.txt output
> of scanModem.  Sometimes resource conflicts are a problem.

I started scanmodem, and I saw on the screen: 

UPDATE=2008_06_21
 Continuing as this update is only 2 weeks old,
 but the current Update is always at: http://linmodems.technion.ac.il

grep: 01:00.1: No such file or directory
grep: 01:00.1: No such file or directory

Then, scanModem froze.   After a few minutes,  I killed the 

grep /dev/shm/0tmpfile.hda

process and scanModem terminated.   ModemData.txt is attached. 


> Do look at Jacques PostInstall Howto at
> http://linmodems.technion.ac.il
> Also make sure that your PPP related files are uptodate.
> 
> The default +MS=92 (compression) is poorly implemented at many IPs.
> Your can try as Init2 in /etc/wvdial.conf
> Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +MS=90
> or even
> Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +MS=34
> 
> With respect to disconnects, decreasing MTU (maximum transfer unit)
> can help.  See cogent sections of /etc/ppp/options and
> $ man pppd

At this point, I cannot efford time consuming experiments.   It took 
four days to install Fedora 9 (due to a DMA problem). Then, it took 
three more days to get the Xserver running. Now, I work for three 
days to get the modem working.....

For the next days, I will use my old vaio to work.  In a few days, 
I will either buy a "traditional modem" or I will even switch to 
Vista. 

> The lines are the end of /var/log/messages upon a failure are often informative.

Jun 30 12:42:24 hemlock pppd[3753]: pppd 2.4.4 started by root, uid 0
Jun 30 12:42:24 hemlock pppd[3753]: Using interface ppp0
Jun 30 12:42:24 hemlock pppd[3753]: Connect: ppp0 <--> /dev/pts/4
Jun 30 12:42:28 hemlock pppd[3753]: local  IP address 149.225.54.225
Jun 30 12:42:28 hemlock pppd[3753]: remote IP address 139.4.248.130
Jun 30 12:42:28 hemlock pppd[3753]: primary   DNS address 195.129.111.49
Jun 30 12:42:28 hemlock pppd[3753]: secondary DNS address 195.129.111.50
Jun 30 12:49:14 hemlock pppd[3753]: Terminating on signal 15
Jun 30 12:49:14 hemlock pppd[3753]: Connect time 6.8 minutes.
Jun 30 12:49:14 hemlock pppd[3753]: Sent 23344 bytes, received 56607 bytes.
Jun 30 12:49:17 hemlock pppd[3753]: Connection terminated.
Jun 30 12:49:17 hemlock pppd[3753]: Exit.

Thanks,  Daniel




 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 Fedora release 9 (Sulphur)
Kernel  kernel 2.6.25.6-55.dk13.fc9.i686 
 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,  Fedora release 9 (Sulphur)
Kernel 
Linux version 2.6.25.6-55.dk13.fc9.i686 (root@hemlock) (gcc version 4.3.0 20080428 (Red Hat 4.3.0-8) (GCC) ) #1 SMP Sun Jun 29 23:44:37 CEST 2008
 scanModem update of:  2008_06_21
The modem symbolic link is /dev/modem -> ttySL0
The slmodemd set symbolic link is /dev/ttySL0 -> /dev/pts/4
 There are no blacklisted modem drivers in /etc/modprobe*  files 
Attached USB devices are:
 ID 1d6b:0002 Linux Foundation 2.0 root hub
 ID 1d6b:0001 Linux Foundation 1.1 root hub
 ID 045e:007d Microsoft Corp. Notebook Optical Mouse
 ID 1d6b:0001 Linux Foundation 1.1 root hub
 ID 090c:1000 Feiya Technology Corp. Memory Bar
 ID 1d6b:0001 Linux Foundation 1.1 root hub
 ID 1d6b:0002 Linux Foundation 2.0 root hub
 ID 1d6b:0001 Linux Foundation 1.1 root hub
 ID 1d6b:0001 Linux Foundation 1.1 root hub

USB modems not recognized

For candidate card in slot 00:1b.0, firmware information and bootup diagnostics are:
 PCI slot	PCI ID		SubsystemID	Name
 ----------	---------	---------	--------------
 00:1b.0	8086:284b	1734:1107	Audio device: Intel Corporation 82801H 

 Modem interrupt assignment and sharing: 
 22:        104     128055   IO-APIC-fasteoi   HDA Intel
 --- Bootup diagnostics for card in PCI slot 00:1b.0 ----
ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 22 (level, low) -> IRQ 22
PCI: Setting latency timer of device 0000:00:1b.0 to 64

For candidate card in slot 01:00.1, firmware information and bootup diagnostics are:
 PCI slot	PCI ID		SubsystemID	Name
 ----------	---------	---------	--------------
 01:00.1	1002:aa08	1734:1107	Audio device: ATI Technologies Inc RV630/M76 audio device [Radeon HD 2600 Series]

 Modem interrupt assignment and sharing: 
 17:       2367      24392   IO-APIC-fasteoi   ahci, HDA Intel
 --- Bootup diagnostics for card in PCI slot 01:00.1 ----
ACPI: PCI Interrupt 0000:01:00.1[B] -> GSI 17 (level, low) -> IRQ 17
PCI: Setting latency timer of device 0000:01:00.1 to 64


===== Advanced Linux Sound Architecture (ALSA) diagnostics ===== 
The ALSA packages provide audio support and also drivers for some modems.
ALSA diagnostics are written during bootup to /proc/asound/ folders.

 PCI slot 00:1b.0
01:00.1 has a High Definition Audio Card
 The drivers are in the kernel modules tree at:
 /lib/modules/2.6.25.6-55.dk09.fc9.i686/kernel/sound/pci/hda/snd-hda-intel.ko
/lib/modules/2.6.25.6-55.dk13.fc9.i686/kernel/sound/pci/hda/snd-hda-intel.ko
/lib/modules/2.6.25.6-55.dk12.fc9.i686/kernel/sound/pci/hda/snd-hda-intel.ko
/lib/modules/2.6.25.6-55.dk11.fc9.i686/kernel/sound/pci/hda/snd-hda-intel.ko
/lib/modules/2.6.25.6-55.dk10.fc9.i686/kernel/sound/pci/hda/snd-hda-intel.ko
/lib/modules/2.6.22.14-72g/kernel/sound/pci/hda/snd-hda-intel.ko
/lib/modules/2.6.25.6-55.fc9.i586/kernel/sound/pci/hda/snd-hda-intel.ko
 New HDA card type: 
    
    

 ---ALSA bootup diagnostics --- 

The ALSA verion is 1.0.16
The modem cards detected by "aplay -l"  are: 
card 0: Intel [HDA Intel], device 6: Si3054 Modem [Si3054 Modem]

The /proc/asound/pcm file reports:
-----------------------
00-06: Si3054 Modem : Si3054 Modem : playback 1 : capture 1
00-02: ALC883 Analog : ALC883 Analog : capture 1
00-01: ALC883 Digital : ALC883 Digital : playback 1
00-00: ALC883 Analog : ALC883 Analog : playback 1 : capture 1
01-00: ATI HDMI : ATI HDMI : playback 1

about /proc/asound/cards:
------------------------
 0 [Intel          ]: HDA-Intel - HDA Intel
                      HDA Intel at 0xf0800000 irq 22
 1 [HDMI           ]: HDA-Intel - HDA ATI HDMI
                      HDA ATI HDMI at 0xcfeec000 irq 17
If not a Conexant modem, the driver snd-hda-intel with its dependent drivers:
snd_hda_intel         302328  5 
snd_pcm                60292  2 snd_hda_intel,snd_pcm_oss
snd_page_alloc         10888  2 snd_hda_intel,snd_pcm
----------
provide audio + modem support with the modem chip residing on the subsystem.
Any particular card can host any one of several soft modem chips. 

 The modem codec file for the HDA card is: 1
--------------------------------------------------------



Though a Conexant modem chipset has not been directly detected, 
the present of Vendor 14f1 Conexant audio chips, strongly suggests 
that if no other modem is detected, than a Conexant modem chip is hosted
on the Subsystem of the High Definition Audio card.

=== Finished firmware and bootup diagnostics, next deducing cogent software. ===

A candidate modem is not evident among the PCI devices:
------------------------------------------------
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03)
00:1f.1 IDE interface: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) IDE Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) SATA AHCI Controller (rev 03)
00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus Controller (rev 03)
01:00.0 VGA compatible controller: ATI Technologies Inc Unknown device 9583
01:00.1 Audio device: ATI Technologies Inc RV630/M76 audio device [Radeon HD 2600 Series]
04:00.0 Memory controller: Intel Corporation Turbo Memory Controller (rev 01)
05:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN Network Connection (rev 61)
06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 01)
07:00.0 Mass storage controller: Silicon Image, Inc. Sil 3531 [SATALink/SATARaid] Serial ATA Controller (rev 01)
08:00.0 SATA controller: JMicron Technologies, Inc. JMicron 20360/20363 AHCI Controller (rev 03)
08:00.1 IDE interface: JMicron Technologies, Inc. JMicron 20360/20363 AHCI Controller (rev 03)
09:04.0 FireWire (IEEE 1394): O2 Micro, Inc. Firewire (IEEE 1394) (rev 02)
------------------------------------------------
 with USB and bridge devices not displayed.

 If your modem is connected by an external serial cable,
 or mounted internally on an ISA card, scanModem would not access it. 
 Try with Root permission
 $  wvdialconf  /etc/wvdial.conf
 to detect these modem types and some USB modems.
 If the detection is successful, read the DOCs/wvdial.txt .
 Edit the /etc/wvdial.conf with Root permission:
 	  gedit  /etc/wvdial.conf
  will be able to dial out with Root permission:
	 wvdial

 Many modems for which scanModem fails have Conexant chips. 
 From http://www.linuxant.com/drivers/modemident.php
 get the ListModem tool, which will report on Conexant chipset modems

 If the above tests fail, please provide any independent information available on your modem.
 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. From the Driver Details TAB, copy out the 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.

 The /proc/asound/ audio+modem diagostics are being copied.
 Finished copy to Modem/ALSAroot.tgz

Predictive diagnostics for card in bus 00:1b.0:
	Modem chipset not detected on
NAME="Audio device: Intel Corporation 82801H "
CLASS=0403
PCIDEV=8086:284b
SUBSYS=1734:1107
IRQ=22
HDA=8086:284b
SOFT=8086:284b.HDA
SLMODEMD_DEVICE=hw:0,6
Driver=snd-hda-intel


 High Definition Audio (HDA) cards MAY host a modem chip in their Subsystem, 
 and many are supported by the ALSA audio+modem driver snd-hda-intel
 A modem was not detected on HDA card 8086:284b.
 If another modem card is present, then most likely 8086:284b does not host a modem.
 If another modem card has not been detected, then possibilities are:
	1) A Conexant modem chip is present on 8086:284b, as Conexant chips
 are frequently not detectable by ALSA diagnostics
	2) The modem may be of the older non-PCI Controller Chipset (hardware) type.
Try detection with Root permission:
	 wvdialconf  /etc/wvdial.conf

 For candidate modem in:  00:1b.0
   0403 Audio device: Intel Corporation 82801H 
      Primary device ID:  8086:284b
    Subsystem PCI_id  1734:1107 
    Softmodem codec or chipset from diagnostics: 
                               from    Archives: 
                        
      

Support type needed or chipset:	

Support can likely be achieved through two mutually exclusive alternatives:
1) The hsfmodem software for Conexant chipset modems: Read DOCs/Conexant.txt
The following ALSA alternative CANNOT work with Conexant modems.

2) An ALSA modem driver plus slmodemd.  Read DOCs/Smartlink.txt for details, and
to test get the package SLMODEMD.gcc4.3.tar.gz from:  
	http://linmodems.technion.ac.il/packages/smartlink/

----------------end Softmodem section --------------

For owners of a Dell PCs with Conexant HSF modems, a driver source package with full speed enabled is available, but requires driver compiling. Read DOCs/Conexant.txt

 Start at  http://www.linuxant.com/drivers/hsf/full for
 eventually download of a hsfmodem-7.68.00.07full_k.???.zip package
 with ??? the package type (deb, rpm, tar etc)
 These packages have compiled drivers but will also compile a driver, 
 if there is a mismatch between the resident kernel and provided driver.
 The generic hsfmodem-7.68.00.07full.tar.gz package only provides compiling support

 Read DOCs/Conexant.txt

Writing DOCs/Conexant.txt

Writing DOCs/Smartlink.txt
============ end Smartlink section =====================


Predictive diagnostics for card in bus 01:00.1:
	Modem chipset not detected on
NAME="Audio device: ATI Technologies Inc RV630/M76 audio device [Radeon HD 2600 Series]"
CLASS=0403
PCIDEV=1002:aa08
SUBSYS=1734:1107
IRQ=17

 For candidate modem in:  01:00.1
   0403 Audio device: ATI Technologies Inc RV630/M76 audio device [Radeon HD 2600 Series]
      Primary device ID:  1002:aa08
 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.



 The base of the UDEV device file system is: /dev/.udev

 Versions adequately match for the compiler installed: 4.3.0
             and the compiler used in kernel assembly: 4.3.0


 
 Minimal compiling resources appear complete:
   make utility - /usr/bin/make
   Compiler version 4.3
   linuc_headers base folder /lib/modules/2.6.25.6-55.dk13.fc9.i686/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 libc6-dev (and for Debian/Ubuntu,
 linux-libc-dev). 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 pppd properties:
	-r-xr-xr-x 1 root root 318024 2008-05-13 11:13 /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

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.
==========================================================

 Checking for modem support lines:
 --------------------------------------
     /device/modem symbolic link:   lrwxrwxrwx 1 root root 6 2008-06-30 12:35 /dev/modem -> ttySL0
slmodemd created symbolic link /dev/ttySL0:  
     Within /etc/udev/ files:
/etc/udev/rules.d/50-udev-default.rules:KERNEL=="mwave",		NAME="modems/mwave", GROUP="uucp"
     Within /etc/modprobe.conf files:

     Within any ancient /etc/devfs files:

     Within ancient kernel 2.4.n /etc/module.conf files:

--------- end modem support lines --------


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

  Powered by Linux