Re: badstuff9 USA kernel 2.6.31-19-generic

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

 



Here is the output of all I did based on your help:

root@system1:/# ls -l /dev/ttyACM*
ls: cannot access /dev/ttyACM*: No such file or directory
root@system1:/#


root@system1:/# sudo tail -f  /var/log/messages &
[1] 2556
root@system1:/# Mar 7 21:49:57 system1 pulseaudio[1408]: last message repeated 5 times
Mar  7 21:49:57 system1 pulseaudio[1408]: ratelimit.c: 8 events suppressed
Mar 7 21:49:59 system1 kernel: [ 47.515075] vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'. Mar 7 21:50:02 system1 pulseaudio[2346]: lock-autospawn.c: Cannot access autospawn lock. Mar 7 21:50:02 system1 kernel: [ 50.120598] 4:3:1: cannot get freq at ep 0x84 Mar 7 21:50:02 system1 pulseaudio[2321]: alsa-mixer.c: Your kernel driver is broken: it reports a volume range from 18.00 dB to 18.00 dB which makes no sense. Mar 7 21:50:02 system1 kernel: [ 50.179708] 4:3:1: cannot get freq at ep 0x84 Mar 7 21:50:02 system1 pulseaudio[2321]: alsa-mixer.c: Your kernel driver is broken: it reports a volume range from 18.00 dB to 18.00 dB which makes no sense.
Mar  7 21:50:07 system1 pulseaudio[2321]: last message repeated 5 times
Mar  7 21:50:07 system1 pulseaudio[2321]: ratelimit.c: 1 events suppressed
root@system1:/#


Then, I attached the fax/modem.....

root@system1:/# ls -l /dev/ttyACM*
crw-rw---- 1 root dialout 166, 0 2010-03-07 21:53 /dev/ttyACM0
root@system1:/#


root@system1:/# sudo ln -s /dev/ttyACM0 /dev/modem
root@system1:/#


root@system1:/# sudo wvdialconf  wvtest
Editing `wvtest'.

Scanning your serial ports for a modem.

Modem Port Scan<*1>: Scanning ttyACM0 first, /dev/modem is a link to it.
WvModem<*1>: Cannot get information for serial port.
ttyACM0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyACM0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttyACM0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
ttyS0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyS0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttyS0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
Modem Port Scan<*1>: S1 S2 S3

Sorry, no modem was detected!  Is it in use by another program?
Did you configure it properly with setserial?

Please read the FAQ at http://open.nit.ca/wiki/?WvDial

If you still have problems, send mail to <wvdial-list@xxxxxxxxxxxx>.
root@system1:/#




What do you think is wrong?

Marvin Stodolsky wrote:
Bad,

Boot up without the USB modem attached. Check for modem ports
$  ls -l /dev/ttyACM*

Display kernel messages:
$ sudo tail -f  /var/log/messages &

Attach the modem, copy out the new messages .
Check which port has created:
$ ls -l /dev/ttyACM*

Create a /dev/modem symbolic link to it:
$ sudo ln -s  /dev/ttyACM0  /dev/modem
If the new port was /dev/ttyACM1, then instead:
$ sudo ln -s  /dev/ttyACM1  /dev/modem

Again run:
$  sudo wvdialconf  wvtest

Marv S

On Sun, Mar 7, 2010 at 8:07 PM, badstuff9@xxxxxxx <badstuff9@xxxxxxx> wrote:
Thanks again Marvin.

I removed the hsfmodem stuff as you instructed.  It seemed to go just as you
described, no problems that I could see.

Then, I reran wvdialconf wvtest.  It provides this output, what steps should
I be taking at this point?

**************************************************
root@system1:/# wvdialconf wvtest
Editing `wvtest'.

Scanning your serial ports for a modem.

ttyS0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyS0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttyS0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
Modem Port Scan<*1>: S1   S2   S3   ACM0
WvModem<*1>: Cannot get information for serial port.
ttyACM1<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyACM1<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttyACM1<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.


Sorry, no modem was detected!  Is it in use by another program?
Did you configure it properly with setserial?

Please read the FAQ at http://open.nit.ca/wiki/?WvDial

If you still have problems, send mail to <wvdial-list@xxxxxxxxxxxx>.
********************************************************


Marvin Stodolsky wrote:

Bad,

The hsfmodem software is what supports in principle the Conexant modem.
Do
$ sudo apt-cache search hsfmodem
it should return the InstalledName of the software package. THen run
$ sudo apt-get remove InstalledName

If an InstalledName is not returned do:
$ sudo hsfconfig --help
to get the unistall syntax.  I thing it is
$ sudo hsfconfig --uninstall

MarvS

On Sun, Mar 7, 2010 at 3:45 PM, badstuff9@xxxxxxx <badstuff9@xxxxxxx> wrote:


Thank you for your help.  A few followup questions.

I don't know how to unload the hsfmodem software.  Can you explain how I do
that?  And, how would I make it permanently *not* load?  (I don't know what
the hsfmodem software is, nor who is loading it, nor why.)

I did the wvdial stuff.  Here is the output:

**********************************************************
root@system1:/# wvdialconf wvtest
Editing `wvtest'.

Scanning your serial ports for a modem.

ttyS0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyS0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttyS0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
Modem Port Scan<*1>: S1   S2   S3
WvModem<*1>: Cannot get information for serial port.
ttyACM0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyACM0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttyACM0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.


Sorry, no modem was detected!  Is it in use by another program?
Did you configure it properly with setserial?

Please read the FAQ at http://open.nit.ca/wiki/?WvDial

If you still have problems, send mail to <wvdial-list@xxxxxxxxxxxx>.
*************************************************************

Well, I don't know what to do at this point.  The web site
http://open.nit.ca/wiki/?WvDial is not valid, so I couldn't get any help
there.  What do you recommend as a next step?



Marvin Stodolsky wrote:

Badstuff,

The hsfmodem drivers you have installed does interfere with some other
modems, and does grab significant resources.  Try unloading the
hsfmodem software whike trying to get the USB modem functional.

If you first install the wvdial_karmic_i386.zip resources, you can
check for simple driver  cdc_acm access to the modem hardware with:
$ sudo wvdialconf  wvtest
Until this minimal test succeeds, nothing else will.

For guidance on FAX usage, get from
http://linmodems.technion.ac.il/packages/  get faxing.tar.gz
It has samples for a modem using port /dev/ttySL0, which must be
changed to match your modem's port.

MarvS

On Sun, Mar 7, 2010 at 2:47 PM, badstuff9@xxxxxxx <badstuff9@xxxxxxx> wrote:


I am trying to use a US Robotics model 5637 fax/modem plugged into a USB
port.
I am running Ubuntu 9.10.  The user on the system is set up with the "User
Priveleges" to "Send and Receive Faxes".  Also, this same user is part of
both the "dialout" and "fax" user groups.
When I try to send a postscript file using efax-gtk version 2, using serial
port ttyACM0, as a non-root user, I get this output in efax-gtk:
Socket running on port 9900
efax-0.9a: 13:14:34 Warning: /dev/ttyACM0 locked or busy - waiting
efax-0.9a: 13:14:42 Warning: /dev/ttyACM0 locked or busy - waiting
efax-0.9a: 13:14:51 Warning: /dev/ttyACM0 locked or busy - waiting
efax-0.9a: 13:15:07 Warning: /dev/ttyACM0 locked or busy - waiting
efax-0.9a: 13:15:39 Warning: /dev/ttyACM0 locked or busy - waiting

During this time, only the power light on the fax/modem is on, the data
light never comes on at all.
But, if I run efax-gtk as root, and then try to send the same fax, efax-gtk
gives these messages:
Socket running on port 9900
efax-0.9a: 13:33:07 opened /dev/ttyACM0
efax-0.9a: 13:33:13 sync: dropping DTR
efax-0.9a: 13:33:18 sync: sending escapes
efax-0.9a: 13:33:24 Error: sync: modem not responding
efax-0.9a: 13:33:24 failed page /home/main1/ourstuff/temporary/output.ps.001
efax-0.9a: 13:33:24 finished - no response from modem

During this time, the power light on the fax/modem is on, and the data light
does flash some.
The permisssions on /dev/ttyACM0 are these:
crw-rw---- 1 root dialout 166, 0 2010-03-07 13:39 ttyACM0

I have attached as a text file to this email the ModemData.txt file from the
scanModem program.
I read through the ModemData.txt file, I quickly got lost, I did not
understand about 90% of what it was trying to explain/recommend.
Thanks for any help.
badstuff9@xxxxxxx

 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.31-19-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=i686,  Ubuntu ,  ALSA_version=1.0.20
Linux version 2.6.31-19-generic (buildd@palmer) (gcc version 4.4.1 (Ubuntu
4.4.1-4ubuntu8) ) #56-Ubuntu SMP Thu Jan 28 01:26:53 UTC 2010
 scanModem update of:  2010_02_25

Distrib_ID=Ubuntu
DistribCodeName=karmic
AptRepositoryStem=http://us.archive.ubuntu.com/ubuntu/

The dialer utility package WVDIAL does not appear to be installed on your
System.
For Ubuntu users, there are at the bottom of
http://linmodems.technion.ac.il/packages/
packages with the files necessary to install wvdial, with names like:
    wvdial_jaunty_amd64.zip   for x86_64, 64 bit bus systems.
    wvdial_jaunty_i386.zip    for 32 bit systems.
    wvdial_karmic_i386.zip    for 32 bit systems.
These are about 1 MB in size.  After downloaded and copied into your Linux
partition:
$ unzip wv*.zip
Within the new folder:
$ sudo dpkg -i *.deb
will  complete the wvdial installation
Please read Modem/DOCs/wvdial.txt for usage information.

The dkms driver upgrade utilities are installed,

 There are no blacklisted modem drivers in /etc/modprobe*  files

 Potentially useful modem drivers now loaded are:
     cdc_acm snd_hda_intel

Attached USB devices are:
 ID 04b8:080d Seiko Epson Corp. Stylus CX4500/4600
 ID 19ff:0102 Dynex 1.3MP Webcam
 ID 046d:c214 Logitech, Inc. ATK3 (Attack III Joystick)
 ID 0451:2046 Texas Instruments, Inc. TUSB2046 Hub
 ID 0baf:0303 U.S. Robotics
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

Candidate PCI devices with modem chips are:
02:01.0 Communication controller: Conexant Systems, Inc. HSF 56k
Data/Fax/Voice/Spkp Modem (rev 01)
High Definition Audio cards can host modem chips.

For candidate card in slot 02:01.0, firmware information and bootup
diagnostics are:
 PCI slot       PCI ID          SubsystemID     Name
 ----------     ---------       ---------       --------------
 02:01.0        14f1:2016       13e0:0219       Communication controller:
Conexant Systems, Inc. HSF 56k Data/Fax/Voice/Spkp Modem

 Modem interrupt assignment and sharing:
 --- Bootup diagnostics for card in PCI slot 02:01.0 ----
[    0.107121] pci 0000:02:01.0: reg 10 32bit mmio: [0xfeae0000-0xfeaeffff]
[    0.107131] pci 0000:02:01.0: reg 14 io port: [0xd480-0xd487]
[    0.107180] pci 0000:02:01.0: PME# supported from D0 D3hot D3cold
[    0.107186] pci 0000:02:01.0: PME# disabled

 The PCI slot 02:01.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@xxxxxxxxxxxxx
 if help is needed.


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

Predictive  diagnostics for card in bus 001:
       Modem chipset  detected on
SLOT="Bus 001 Device 002:"
NAME="U.S. Robotics "
bus=001
USBmodemID=0baf:0303
IDENT=cdc_acm
Driver=cdc_acm

For a detailed USB cellphone usage report, see
http://linmodems.technion.ac.il/bigarch/archive-eighth/msg03240.html
 For candidate modem in:  001
   U.S. Robotics
     Primary device ID:  0baf:0303
 Support type needed or chipset:        cdc_acm



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

 From  http://www.linuxant.com/drivers//downloads-ubuntu-x86.php
 download -7.80.02.05full_k2.6.31_19_generic_ubuntu_i386.deb.zip
 Under Linux unpack with:
 $ unzip *.zip
 Then install with:
 $ sudo dpkg -i *.deb
 Subsequently, the modem should be found with
 $ sudo wvdialconf /etc/wvdial.conf
 Edit in your personal information with:
 $ sudo gedit /etc/wvdial.conf
 and try dialing out with:
 $ sudo wvdial.
 See DOCs/Testing.txt  for details.

 The directions following below need only be pursued, if the above
procedures are not adequate.
001
02:01.0
 Read DOCs/Conexant.txt

Writing DOCs/Conexant.txt



Predictive  diagnostics for card in bus 02:01.0:
       Modem chipset  detected on
NAME="Communication controller: Conexant Systems, Inc. HSF 56k
Data/Fax/Voice/Spkp Modem "
CLASS=0780
PCIDEV=14f1:2016
SUBSYS=13e0:0219
IRQ=11
IDENT=hsfmodem
Driver=hsfmodem-drivers

 For candidate modem in:  02:01.0
  0780 Communication controller: Conexant Systems, Inc. HSF 56k
Data/Fax/Voice/Spkp Modem
     Primary device ID:  14f1:2016
 Support type needed or chipset:        hsfmodem



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

 From  http://www.linuxant.com/drivers/hsf/full/downloads-ubuntu-x86.php
 download hsfmodem-7.80.02.05full_k2.6.31_19_generic_ubuntu_i386.deb.zip
 Under Linux unpack with:
 $ unzip hsfmodem*.zip
 Then install with:
 $ sudo dpkg -i hsfmodem*.deb
 Subsequently, the modem should be found with
 $ sudo wvdialconf /etc/wvdial.conf
 Edit in your personal information with:
 $ sudo gedit /etc/wvdial.conf
 and try dialing out with:
 $ sudo wvdial.
 See DOCs/Testing.txt  for details.

 The directions following below need only be pursued, if the above
procedures are not adequate.

Start at http://www.linuxant.com/drivers/hsf/downloads-license.php to find
the
hsfmodem package matching your System. For several Linux distros, there are
precompiled drivers matched to specific kernels. These have within the
FileName,
your KernelVersion:     2.6.31_19_generic
They can be found through
http://www.linuxant.com/drivers/hsf/full/downloads.php
A more precise location may be given a few paragraphs below.
If an EXACT Match with your your KernelVersion is not found, one of the
"Generic packages with source" near the bottom of the page must be used.
Downloaded packages must be moved into the Linux partition (home folder is
OK)
and unzipped with:
       unzip hsf*.zip
The installation command for a .deb suffic packages is, with root/adm
permission:
 sudo dpkg -i hsf*.deb
while for .rpm suffix it is, with:
 rpm -i hsf*.rpm
 Read DOCs/Conexant.txt

Writing DOCs/Conexant.txt


 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-19-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 pppd properties:
       -r-xr-xr-x 1 root dip 277352 2009-02-20 11:25 /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)
       sudo chmod a+x /usr/sbin/pppd
or under Ubuntu related Linuxes
       sudo chmod a+x /usr/sbin/pppd

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

For guidance on FAX usage, get from
http://linmodems.technion.ac.il/packages/  get faxing.tar.gz
It has samples for a modem using port /dev/ttySL0, which must be changed to
match your modem's port.

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/00-hsf.rules:KERNEL=="ttySHSF0", SYMLINK="modem"
    Within /etc/modprobe.conf files:
/etc/modprobe.d/hsf.conflicts.conf:install snd-via82xx-modem /bin/true #
temporarily disabled by hsf - conflicts with hsfmc97via
/etc/modprobe.d/hsf.conflicts.conf:install snd-atiixp-modem /bin/true #
temporarily disabled by hsf - conflicts with hsfmc97ati
/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
/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/hsf.conf:alias /dev/modem /dev/ttySHSF
/etc/modprobe.d/hsf.conf:install /dev/ttySHSF /sbin/modprobe hsfpcibasic2;
/sbin/modprobe hsfpcibasic3; /sbin/modprobe hsfmc97ich; /sbin/modprobe
hsfmc97via; /sbin/modprobe hsfmc97ali; /sbin/modprobe hsfmc97ati;
/sbin/modprobe hsfmc97sis; [ -e /lib/modules/`uname -r`/extra/hsfusbcd2.ko ]
&& /sbin/modprobe hsfusbcd2; /sbin/modprobe snd_hda_intel; [ -e
/lib/modules/`uname -r`/extra/snd-hda-codec-hsfmodem.ko ] && /sbin/modprobe
snd-hda-codec-hsfmodem; /bin/true
    Within any ancient /etc/devfs files:

    Within ancient kernel 2.4.n /etc/module.conf files:
/etc/modules.conf:alias /dev/modem /dev/ttySHSF
/etc/modules.conf:probeall /dev/ttySHSF hsfpcibasic2 hsfpcibasic3 hsfmc97ich
hsfmc97via hsfmc97ali hsfmc97ati hsfmc97sis hsfusbcd2 snd_hda_intel
snd-hda-codec-hsfmodem
--------- end modem support lines --------












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

  Powered by Linux