Please help!

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

 



Ivan from Croatia!
Thx...
 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 
Welcome to openSUSE 10.3 (X86-64) - Kernel  kernel 2.6.22.5-31-default 
 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,  
Welcome to openSUSE 10.3 (X86-64) - Kernel 
Linux version 2.6.22.5-31-default (geeko@buildhost) (gcc version 4.2.1 (SUSE Linux)) #1 SMP 2007/09/21 22:29:00 UTC
 scanModem update of:  2008_06_05


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 hcflinmodem drivers for Conexant chipsest modes are x86_64 competent.

 There are no blacklisted modem drivers in /etc/modprobe*  files 
Checking  /proc/bus/usb/devices
 /proc/bus/usb/devices file not present, barring USB modem query.  

For candidate card in slot 00:07.0, firmware information and bootup diagnostics are:
 PCI slot	PCI ID		SubsystemID	Name
 ----------	---------	---------	--------------
 00:07.0	10de:055c	1025:0126	Audio device: nVidia Corporation MCP67 High Definition Audio 

 Modem interrupt assignment and sharing: 
 21:          0        750   IO-APIC-fasteoi   ohci_hcd:usb2, HDA Intel
 --- Bootup diagnostics for card in PCI slot 00:07.0 ----
ACPI: PCI Interrupt 0000:00:07.0[A] -> Link [LAZA] -> GSI 21 (level, low) -> IRQ 21
PCI: Setting latency timer of device 0000:00:07.0 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:07.0 has a High Definition Audio Card
 ---ALSA bootup diagnostics --- 

The ALSA verion is 1.0.14
The modem cards detected by "aplay -l"  are: None


The /proc/asound/pcm file reports:
-----------------------
00-02: ALC268 Analog : ALC268 Analog : capture 2
00-01: ALC268 Digital : ALC268 Digital : playback 1
00-00: ALC268 Analog : ALC268 Analog : playback 1 : capture 2

about /proc/asound/cards:
------------------------
 0 [NVidia         ]: HDA-Intel - HDA NVidia
                      HDA NVidia at 0xf0880000 irq 21
=== Finished firmware and bootup diagnostics, next deducing cogent software. ===

A candidate modem is not evident among the PCI devices:
------------------------------------------------
00:00.0 RAM memory: nVidia Corporation Unknown device 0547 (rev a2)
00:01.1 SMBus: nVidia Corporation Unknown device 0542 (rev a2)
00:01.2 RAM memory: nVidia Corporation Unknown device 0541 (rev a2)
00:01.3 Co-processor: nVidia Corporation Unknown device 0543 (rev a2)
00:06.0 IDE interface: nVidia Corporation MCP67 IDE Controller (rev a1)
00:07.0 Audio device: nVidia Corporation MCP67 High Definition Audio (rev a1)
00:09.0 IDE interface: nVidia Corporation Unknown device 0550 (rev a2)
00:0a.0 Ethernet controller: nVidia Corporation Unknown device 054c (rev a2)
01:04.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 05)
01:04.1 Generic system peripheral [Class 0805]: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 22)
01:04.2 System peripheral: Ricoh Co Ltd R5C843 MMC Host Controller (rev 12)
01:04.3 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 12)
01:04.4 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev 12)
02:00.0 VGA compatible controller: nVidia Corporation GeForce 8400M G (rev a1)
05:00.0 Ethernet controller: Atheros Communications, Inc. AR5006EG 802.11 b/g Wireless PCI Express Adapter (rev 01)
------------------------------------------------
 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:07.0:
	Modem chipset not detected on
CLASS="Class 0403: 10de:055c"
NAME="Audio device: nVidia Corporation MCP67 High Definition Audio "
SUBSYS=1025:0126
PCIDEV=10de:055c
IRQ=21
HDA=10de:055c
SOFT=10de:055c.HDA


 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 10de:055c.
 If another modem card is present, then most likely 10de:055c does not host a modem.
 If another modem card has not been detected, then possibilities are:
	1) A Conexant modem chip is present on 10de:055c, 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:07.0
   Class 0403: 10de:055c Audio device: nVidia Corporation MCP67 High Definition Audio 
      Primary device ID:  10de:055c
    Subsystem PCI_id  1025:0126 
    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.2.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 =====================


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

 The kernel was compiled with gcc version 4.2.1 and a compiler is not installed

 linux-headers-2.6.22.5-31-default resources needed for compiling are not manifestly ready!

 If compiling is necessary packages must be installed, providing:
	gcc-4.2 make kernel-source-2.6.22.5-31-default


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:
	-rwxr-xr-x 1 root dialout 347008 Sep 21  2007 /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
noipdefault
noauth
crtscts
lock
modem
asyncmap 0
nodetach
lcp-echo-interval 30
lcp-echo-failure 4
lcp-max-configure 60
lcp-restart 2
idle 600
noipx
file /etc/ppp/filters

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
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:
/etc/udev/rules.d/77-network.rules:SUBSYSTEM=="net", ENV{INTERFACE}=="ppp*|ippp*|isdn*|plip*|lo*|irda*|dummy*|ipsec*|tun*|tap*|bond*|vlan*|modem*|dsl*", GOTO="skip_ifup"
/etc/udev/rules.d/50-udev-default.rules:KERNEL=="mwave",		NAME="modems/%k", 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