JP,
If you run scanModem from Ubuntu 8.10, do you get Modem Interrupt Assignment?
For candidate card in slot 05:00.0, firmware information and bootup
diagnostics are:
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
05:00.0 10b9:5459 14fe:9100 Modem: ALi
Corporation SmartLink
SmartPCI561 56K Modem
Modem interrupt assignment and sharing:
21: 0 0 IO-APIC-fasteoi SL1800
--- Bootup diagnostics for card in PCI slot 05:00.0 ----
[ 0.187878] pci 0000:05:00.0: reg 10 32bit mmio: [0x30001000-0x30001fff]
[ 0.187889] pci 0000:05:00.0: reg 14 io port: [0x1000-0x10ff]
[ 0.187945] pci 0000:05:00.0: PME# supported from D3hot D3cold
[ 0.187952] pci 0000:05:00.0: PME# disabled
[ 0.276336] serial 0000:05:00.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21
[ 0.276970] 0000:05:00.0: ttyS1 at I/O 0x1028 (irq = 21) is a 8250
[ 0.277305] 0000:05:00.0: ttyS2 at I/O 0x1040 (irq = 21) is a 8250
[ 0.277532] 0000:05:00.0: ttyS3 at I/O 0x1050 (irq = 21) is a 8250
[ 0.277578] Couldn't register serial port 0000:05:00.0: -28
[ 12.745350] serial 0000:05:00.0: PCI INT A disabled
[ 12.803274] slamr 0000:05:00.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21
The PCI slot 05:00.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.
If you do, then you may want to include "Stupid Mode = yes" in your
wvdial.conf file. It would be nice to have logs say
$ sudo wvdial
output comparing the two sessions in parallel, ie. one that works and
the one that does not?
Regards,
Antonio
On 7/10/10, BP <bottomless.pete@xxxxxxxxx> wrote:
> Greetings.
>
> I have recently upgraded from Ubuntu 8.10 x86 to the newest LTS,
> 10.04 x86 (w/ kernel 2.6.32-21) and my modem will no longer connect.
> When I run wvdial to establish a connection, it verifies the
> initialization of the modem, but cannot/will not find a carrier,
> cycling through dial attempts until I manually kill the process. This
> happens with or without "Carrier Check = no" enabled in my wvdial.conf
> file.
>
> I have both distros on separate partitions on the same hardware, and
> the 8.10 version has no trouble detecting a carrier, so I am fairly
> certain it is not a hardware/line issue.
>
> I installed the daemon and drivers via the distro package of
> sl-modem-daemon, slmodem-2.9.11-20100106.tar.gz (since there is no
> pre-compiled slamr package for my kernel version as of yet), as well
> as installing ungrab-winmodem-20090116.tar.gz. And I have followed the
> given setup and troubleshooting steps in those installation packages,
> but no joy.
>
> Any advice in this matter would be greatly appreciated.
>
> Thanks,
> -- JP
>
> -------------------------- System information ----------------------------
> CPU=i686, Ubuntu , ALSA_version=1.0.21
> Linux version 2.6.32-21-generic (buildd@rothera) (gcc version 4.4.3
> (Ubuntu 4.4.3-4ubuntu5) ) #32-Ubuntu SMP Fri Apr 16 08:10:02 UTC 2010
> scanModem update of: 2010_05_29
> The modem symbolic link is /dev/modem -> ttySL0
> The slmodemd set symbolic link is /dev/ttySL0 -> /dev/pts/0
> Distrib_ID=Ubuntu
> DistribCodeName=lucid
>
>
> The dkms driver upgrade utilities are installed,
>
> There are no blacklisted modem drivers in /etc/modprobe* files
>
> Potentially useful modem drivers now loaded are:
> snd_hda_intel slamr
>
> slamrTest=mc97
> Attached USB devices are:
> ID 046d:c018 Logitech, Inc. Optical Wheel Mouse
> ID 046e:5542 Behavior Tech. Computer Corp.
> 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
>
> If a USB modem or cellphone is attached and was not detected, please
> provide available information in your request to discuss@xxxxxxxxxxxxx
>
> Candidate PCI devices with modem chips are:
> 05:00.0 Modem: ALi Corporation SmartLink SmartPCI561 56K Modem
> 00:1b.0 Audio device: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6
> Family) High Definition Audio Controller (rev 03)
> High Definition Audio cards can host modem chips.
>
> For candidate card in slot 05:00.0, firmware information and bootup
> diagnostics are:
> PCI slot PCI ID SubsystemID Name
> ---------- --------- --------- --------------
> 05:00.0 10b9:5459 14fe:9100 Modem: ALi Corporation SmartLink
> SmartPCI561 56K Modem
>
> Modem interrupt assignment and sharing:
> 21: 0 0 IO-APIC-fasteoi SL1800
> --- Bootup diagnostics for card in PCI slot 05:00.0 ----
> [ 0.187878] pci 0000:05:00.0: reg 10 32bit mmio: [0x30001000-0x30001fff]
> [ 0.187889] pci 0000:05:00.0: reg 14 io port: [0x1000-0x10ff]
> [ 0.187945] pci 0000:05:00.0: PME# supported from D3hot D3cold
> [ 0.187952] pci 0000:05:00.0: PME# disabled
> [ 0.276336] serial 0000:05:00.0: PCI INT A -> GSI 21 (level, low) -> IRQ
> 21
> [ 0.276970] 0000:05:00.0: ttyS1 at I/O 0x1028 (irq = 21) is a 8250
> [ 0.277305] 0000:05:00.0: ttyS2 at I/O 0x1040 (irq = 21) is a 8250
> [ 0.277532] 0000:05:00.0: ttyS3 at I/O 0x1050 (irq = 21) is a 8250
> [ 0.277578] Couldn't register serial port 0000:05:00.0: -28
> [ 12.745350] serial 0000:05:00.0: PCI INT A disabled
> [ 12.803274] slamr 0000:05:00.0: PCI INT A -> GSI 21 (level, low) -> IRQ
> 21
>
> The PCI slot 05:00.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.
>
>
> For candidate card in slot 00:1b.0, firmware information and bootup
> diagnostics are:
> PCI slot PCI ID SubsystemID Name
> ---------- --------- --------- --------------
> 00:1b.0 8086:2668 107b:4038 Audio device: Intel Corporation
> 82801FB/FBM/FR/FW/FRW
>
> Modem interrupt assignment and sharing:
> 16: 8278 0 IO-APIC-fasteoi uhci_hcd:usb5, i915, HDA
> Intel
> --- Bootup diagnostics for card in PCI slot 00:1b.0 ----
> [ 0.186175] pci 0000:00:1b.0: reg 10 64bit mmio: [0x301c0000-0x301c3fff]
> [ 0.186233] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
> [ 0.186241] pci 0000:00:1b.0: PME# disabled
> [ 11.107434] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 16 (level,
> low) -> IRQ 16
> [ 11.107470] HDA Intel 0000:00:1b.0: setting latency timer to 64
> [ 11.187217] input: HDA Digital PCBeep as
> /devices/pci0000:00/0000:00:1b.0/input/input6
>
> The PCI slot 00:1b.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 05:00.0:
> Modem chipset detected on
> NAME="Modem: ALi Corporation SmartLink SmartPCI561 56K Modem"
> CLASS=0703
> PCIDEV=10b9:5459
> SUBSYS=14fe:9100
> IRQ=21
> HDA2=00:1b.0
> slamrTest=mc97
> IDENT=slamr
>
> For candidate modem in: 05:00.0
> 0703 Modem: ALi Corporation SmartLink SmartPCI561 56K Modem
> Primary device ID: 10b9:5459
> Support type needed or chipset: slamr
>
>
>
> Writing DOCs/Intel.txt
> The modem is supported by the Smartlink
> plus the slmodemd helper utility. Read the
> DOCs/Smartlink.txt and Modem/DOCs/YourSystem.txt for follow through
> guidance.
>
>
> For 2.6.32-21-generic compiling drivers is necessary. As of October
> 2007 the current packages at
> http://linmodems.technion.ac.il/packages/smartlink/ are the
> ungrab-winmodem-20070505.tar.gz and slmodem-2.9.11-20080126.tar.gz
>
> Writing DOCs/Smartlink.txt
> ============ end Smartlink section =====================
>
>
> Predictive diagnostics for card in bus 00:1b.0:
> Modem chipset not detected on
> NAME="Audio device: Intel Corporation 82801FB/FBM/FR/FW/FRW "
> CLASS=0403
> PCIDEV=8086:2668
> SUBSYS=107b:4038
> IRQ=16
>
> For candidate modem in: 00:1b.0
> 0403 Audio device: Intel Corporation 82801FB/FBM/FR/FW/FRW
> Primary device ID: 8086:2668
> Support type needed or chipset:
>
>
> Completed candidate modem analyses.
>
> The base of the UDEV device file system is: /dev/.udev
>
> Versions adequately match for the compiler installed: 4.4.3
> and the compiler used in kernel assembly: 4.4.3
>
> The patch utility is needed for compiling ALSA drivers, and possibly
> others.
>
>
> Minimal compiling resources appear complete:
> make utility - /usr/bin/make
> Compiler version 4.4
> linuc_headers base folder /lib/modules/2.6.32-21-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:
> -rwsr-xr-x 1 root dip 273312 2010-03-06 22:59 /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
> debug
> 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.
>
>
> 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
> 2010-07-10 14:59 /dev/modem -> ttySL0
> slmodemd created symbolic link /dev/ttySL0: lrwxrwxrwx 1 root root 10
> 2010-07-10 14:59 /dev/ttySL0 -> /dev/pts/0
> Within /etc/udev/ files:
>
> Within /etc/modprobe.conf files:
> /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/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/sl-modem.conf:install slamr /sbin/modprobe -qb
> ungrab-winmodem; /sbin/modprobe --ignore-install slamr; test -e
> /dev/slamr0 && (chmod 660 /dev/slamr0 && chgrp dialout /dev/slamr0) ||
> (/bin/mknod -m 660 /dev/slamr0 c 242 0 2>/dev/null && chgrp dialout
> /dev/slamr0)
> /etc/modprobe.d/sl-modem.conf:install slusb /sbin/modprobe -qb
> ungrab-winmodem; /sbin/modprobe --ignore-install slusb; test -e
> /dev/slusb0 && (chmod 660 /dev/slusb0 && chgrp dialout /dev/slusb0) ||
> (/bin/mknod -m 660 /dev/slusb0 c 243 0 2>/dev/null && chgrp dialout
> /dev/slusb0)
> /etc/modprobe.d/sl-modem-daemon.conf:install slamr modprobe
> --ignore-install ungrab-winmodem ; modprobe --ignore-install slamr;
> test -e /dev/slamr0 || (/bin/mknod -m 660 /dev/slamr0 c 242 0
> 2>/dev/null && chgrp dialout /dev/slamr0)
> Within any ancient /etc/devfs files:
>
> Within ancient kernel 2.4.n /etc/module.conf files:
>
> --------- end modem support lines --------
>
- Prev by Date:
JP, USA, Kernel 2.6.32-21-generic, wvdial No Carrier
- Next by Date:
Re: JP, USA, Kernel 2.6.32-21-generic, wvdial No Carrier
- Previous by thread:
JP, USA, Kernel 2.6.32-21-generic, wvdial No Carrier
- Next by thread:
Re: JP, USA, Kernel 2.6.32-21-generic, wvdial No Carrier
- Index(es):
[Linux DVB]
[Asterisk]
[Photo]
[DCCP]
[Netdev]
[Xorg]
[Xfree86]
[Fedora Women]
[Linux USB]
