Hi.
Just reinstalled an old faxserver with the latest ubuntu amd64, but I cannot get Hylafax to detect it. Well, neither wvdial.
I'm attaching ModemData here. From what I could understand from that file and from other google searches the modem should be working fine with no additional drivers, but in fact it is not.
The only information I found is here [1], and says
Looks like it stopped working around kernel 2.6.35 to 2.6.37
I don't know if it can be real or just an OpenSUSE issue.
Anyone knows if there is a real problem with recent kernels and this modem?
thanks
[1] https://bugzilla.novell.com/show_bug.cgi?id=709711
--
Lorenzo Milesi - lorenzo.milesi@xxxxxxxxxx
YetOpen S.r.l. - http://www.yetopen.it/
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 3.13.0-24-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=x86_64, Ubuntu , ALSA_version=k3.13.
Linux version 3.13.0-24-generic (buildd@batsu) (gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ) #47-Ubuntu SMP Fri May 2 23:30:00 UTC 2014
scanModem update of: 2011_08_08
Distrib_ID=Ubuntu
DistribCodeName=trusty
AptRepositoryStem=http://it.archive.ubuntu.com/ubuntu/
Presently install your Linux Distributions dkms package. It provides for automated driver updates,
following upgrade of your kernel. For details see http://linux.dell.com/projects.shtml#dkms
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 hcfpcimodem drivers for Conexant chipsest modes are x86_64 competent.
4) agrsm packages for LSI/AgereSystems softmodems are not competent on x86_64 systems.
There are no blacklisted modem drivers in /etc/modprobe* files
Potentially useful modem drivers now loaded are:
snd_hda_intel
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:
00:03.0 Communication controller: Intel Corporation 4 Series Chipset HECI Controller (rev 03)
00:03.3 Serial controller: Intel Corporation 4 Series Chipset Serial KT Controller (rev 03)
04:02.0 Communication controller: LSI Corporation Venus Modem (V90, 56KFlex)
00:1b.0 Audio device: Intel Corporation 82801JD/DO (ICH10 Family) HD Audio Controller (rev 02)
High Definition Audio cards can host modem chips.
For candidate card in slot 00:03.0, firmware information and bootup diagnostics are:
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
00:03.0 8086:2e14 1028:027f Communication controller: Intel Corporation 4 Series Chipset HECI Controller
Modem interrupt assignment and sharing:
50: 9 9 PCI-MSI-edge mei_me
--- Bootup diagnostics for card in PCI slot 00:03.0 ----
[ 0.577579] pci 0000:00:03.0: [8086:2e14] type 00 class 0x078000
[ 0.577603] pci 0000:00:03.0: reg 0x10: [mem 0xfeda6000-0xfeda600f 64bit]
[ 0.577685] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
[ 0.623597] pci 0000:00:03.0: no compatible bridge window for [mem 0xfeda6000-0xfeda600f 64bit]
[ 0.679207] pci 0000:00:03.0: BAR 0: assigned [mem 0xf0400800-0xf040080f 64bit]
[ 8.925676] mei_me 0000:00:03.0: irq 50 for MSI/MSI-X
For candidate card in slot 00:03.3, firmware information and bootup diagnostics are:
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
00:03.3 8086:2e17 1028:027f Serial controller: Intel Corporation 4 Series Chipset Serial KT Controller
Modem interrupt assignment and sharing:
17: 15 8 IO-APIC-fasteoi uhci_hcd:usb4, uhci_hcd:usb7
--- Bootup diagnostics for card in PCI slot 00:03.3 ----
[ 0.578509] pci 0000:00:03.3: [8086:2e17] type 00 class 0x070002
[ 0.578530] pci 0000:00:03.3: reg 0x10: [io 0xec98-0xec9f]
[ 0.578540] pci 0000:00:03.3: reg 0x14: [mem 0xfebd8000-0xfebd8fff]
[ 1.169214] 0000:00:03.3: ttyS4 at I/O 0xec98 (irq = 17, base_baud = 115200) is a 16550A
For candidate card in slot 04:02.0, firmware information and bootup diagnostics are:
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
04:02.0 11c1:0480 11c1:5656 Communication controller: LSI Corporation Venus Modem
Modem interrupt assignment and sharing:
18: 32 37 IO-APIC-fasteoi ata_generic, uhci_hcd:usb8
--- Bootup diagnostics for card in PCI slot 04:02.0 ----
[ 0.586224] pci 0000:04:02.0: [11c1:0480] type 00 class 0x078000
[ 0.586240] pci 0000:04:02.0: reg 0x10: [mem 0xfe5ff000-0xfe5ff0ff]
[ 0.586249] pci 0000:04:02.0: reg 0x14: [io 0xc800-0xc8ff]
[ 0.586259] pci 0000:04:02.0: reg 0x18: [io 0xcc00-0xccff]
[ 0.586268] pci 0000:04:02.0: reg 0x1c: [io 0xc478-0xc47f]
[ 0.586316] pci 0000:04:02.0: supports D2
[ 0.586317] pci 0000:04:02.0: PME# supported from D2 D3hot D3cold
[ 1.203183] 0000:04:02.0: ttyS5 at I/O 0xc800 (irq = 18, base_baud = 115200) is a 16550A
For candidate card in slot 00:1b.0, firmware information and bootup diagnostics are:
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
00:1b.0 8086:3a6e 1028:027f Audio device: Intel Corporation 82801JD/DO
Modem interrupt assignment and sharing:
51: 1604 1595 PCI-MSI-edge snd_hda_intel
--- Bootup diagnostics for card in PCI slot 00:1b.0 ----
[ 0.581151] pci 0000:00:1b.0: [8086:3a6e] type 00 class 0x040300
[ 0.581165] pci 0000:00:1b.0: reg 0x10: [mem 0xfebdc000-0xfebdffff 64bit]
[ 0.581225] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
[ 9.050864] snd_hda_intel 0000:00:1b.0: irq 51 for MSI/MSI-X
[ 9.433450] input: HDA Intel Front Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input9
[ 9.433607] input: HDA Intel Line Out as /devices/pci0000:00/0000:00:1b.0/sound/card0/input8
[ 9.433743] input: HDA Intel Line as /devices/pci0000:00/0000:00:1b.0/sound/card0/input7
[ 9.433876] input: HDA Intel Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input6
=== Finished firmware and bootup diagnostics, next deducing cogent software. ===
Predictive diagnostics for card in bus 04:02.0:
Modem chipset detected on
NAME="Communication controller: LSI Corporation Venus Modem "
CLASS=0780
PCIDEV=11c1:0480
SUBSYS=11c1:5656
IRQ=18
IDENT=Agere.Venus_serial_drivers
For candidate modem in: 04:02.0
0780 Communication controller: LSI Corporation Venus Modem
Primary device ID: 11c1:0480
Support type needed or chipset: Agere.Venus_serial_drivers
Writing DOCs/Intel.txt
Predictive diagnostics for card in bus 00:03.0:
Modem chipset not detected on
NAME="Communication controller: Intel Corporation 4 Series Chipset HECI Controller "
CLASS=0780
PCIDEV=8086:2e14
SUBSYS=1028:027f
IRQ=50
HDA2=00:1b.0
For candidate modem in: 00:03.0
0780 Communication controller: Intel Corporation 4 Series Chipset HECI Controller
Primary device ID: 8086:2e14
Support type needed or chipset:
Predictive diagnostics for card in bus 00:03.3:
Modem chipset not detected on
NAME="Serial controller: Intel Corporation 4 Series Chipset Serial KT Controller "
CLASS=0700
PCIDEV=8086:2e17
SUBSYS=1028:027f
IRQ=17
For candidate modem in: 00:03.3
0700 Serial controller: Intel Corporation 4 Series Chipset Serial KT Controller
Primary device ID: 8086:2e17
Support type needed or chipset:
Predictive diagnostics for card in bus 00:1b.0:
Modem chipset not detected on
NAME="Audio device: Intel Corporation 82801JD/DO "
CLASS=0403
PCIDEV=8086:3a6e
SUBSYS=1028:027f
IRQ=51
For candidate modem in: 00:1b.0
0403 Audio device: Intel Corporation 82801JD/DO
Primary device ID: 8086:3a6e
Support type needed or chipset:
Completed candidate modem analyses.
The base of the UDEV device file system is: /dev/.udev
The kernel was compiled with gcc version 4.8.2 and a compiler is not installed
linux-headers-3.13.0-24-generic resources needed for compiling are not manifestly ready!
The code linking utility, ld, may be needed and is provided in the binutils package
If compiling is necessary packages must be installed, providing:
gcc-4.8 make linux-headers-3.13.0-24-generic
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-- 1 root dip 343168 gen 22 2013 /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
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:
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 --------
