Robert,
Do these lines need updating for current /etc/modprobe/ syntax??
---------------------
In 2.6, the relevant file is /etc/modprobe.conf and the lines are:
# for pctel modem
alias char-major-62 linmodem
below linmodem pctel
below pctel pctel_hw
# country code for pctel modem
options pctel country_code=13
---
see my PS at the End.
Santiago,
Robert Thornburrow is the PCtel maintainer.
The scanModem diagnostics only reveal a
For candidate modem in PCI bus: 00:0b.0
Class 0703: 134d:7890 Modem: PCTel Inc HSP MicroModem 56
Primary PCI_id 134d:7890
Support type needed or chipset: PCTEL
----------
Where does the info on a Smartlink SL2801 come from?
It would not be a surprise to have a Pctel hardware shoved into a
Smartlink box, as both Pctel and Smartlink modem sectors are now
owned by Conexant.
For Microsoft service, Conexant may well co-pack Pctel, Smartlink,
and Conexant modem chipset support in a single installer package.
The serial driver is compiled into the kernel, as
$ grep SERIAL /boot/config-2.6.22-14-generic
CONFIG_SERIAL_8250=y
and subsequent SERIAL lines confirm.
This if is not manifest as a module.
Loading of the ungrab-winmodem.ko driver is necessary
for subsequent loading of the Smartlink slamr.ko driver,
though it would not surprise me if it is necessary for the Pctel
drivers too. This port "grabbing" has been reported as a SERIAL
driver bug and should disappear in some future kernel update.
As you mostly related,
BEFORE loading the pctel drivers do:
$ sudo modprobe -r ptserial
just in case they autoloaded
$ sudo modprobe ungrab-winmodem
Then
$ sudo insmod linmodem
$ sudo insmod ptserial
$ sudo insmod pctel_hw
there should be a creation of
/dev/ttyS_PCTEL0 with specs: c 62 69
Check with
# ls -l /dev/ttyS_PCTEL0
If not, create with:
$ sudo mknod /dev/ttyS_PCTEL0 c 62 69
Then try finding the modem with:
$ sudo wvdialconf /etc/wvdial.conf
If found, put in your personal info with:
$ sudo gedit /etc/wvdial.conf
removing the symbols ; < >
Then try a dialout with
$ sudo wvdial
MarvS
scanModem maintainer
PS
>From out experience with slamr, the following would likely work in a
/etc/modprobe.d/pctel file
## # for pctel modem
# country code for pctel modem in USA
options pctel country_code=1
#Loads drivers and creates a device node
# the following should be on one line
install pctel_hw --ignore-install ungrab-winmodem ; --ignore-install
ptserial ; --ignore-install pctel_hw ; --ignore-install ptserial ;
test -e /dev/ttyS_PC || (/bin/mknod -m 660 /dev/ttyS_PCTEL0 c 62
69>/dev/null && chgrp dialout /dev/ttyS_PCTEL0 c 62)
# group dialout is used for Debian related distros
On Dec 23, 2007 4:19 PM, Santiago Bruno <bananabruno@xxxxxxxxx> wrote:
> Hi list, I'm trying to install a modem with the Smartlink SL2801 chip
> in Ubuntu Gutsy and I need some help. Is it supported or I'm wasting
> time trying?
>
> lspci reports it as:
> 00:0b.0 Modem: PCTel Inc HSP MicroModem 56 (rev 02) (prog-if 00 [Generic])
> Subsystem: PCTel Inc PCT789 adapter
> Flags: medium devsel, IRQ 16
> I/O ports at e400 [size=64]
> Capabilities: [40] Power Management version 2
>
> I tried running the setup script from pctel-0.9.7-9-rht-8. It compiled
> and installed everything fine, linmodem, pctel and pctel_hw modules
> are loaded when system starts, the /dev/modem link is correct, and I
> don't know if it was this script that made it, but now "PCTEL hardware
> modem driver: binary part of driver" appears in the restricted
> controllers tool of Ubuntu, as Enabled and in use.
> But I get no response from the modem. Tried to run the test with
> wvdial, and made the modem queries with kppp with no result. Except
> when I run the script for the first time and it install the drivers.
> At that moment, if I run the ATI Queries with kppp, they are all made,
> but the results are all empty.
>
> Also, here is a snippet from dmesg:
> [ 47.209606] linmodem(1265): linmodem v0.1 loaded
> [ 47.266449] pctel_hw: module license 'GPL linked with proprietary
> libraries' taints kernel.
> [ 47.269469] pctel_hw(155): PCTel hardware driver version
> 0.9.7-9-rht-8 for PCT789
> [ 47.269472]
> [ 47.311891] pctel(477): pctel v0.1 loaded
> [ 47.311913] pctel_pci(728): device 134d:7890 is grabbed by driver
> serial: try to release
> [ 47.311916]
> [ 47.314384] ACPI: PCI interrupt for device 0000:00:0b.0 disabled
> [ 47.314449] ACPI: PCI Interrupt 0000:00:0b.0[A] -> GSI 18 (level,
> low) -> IRQ 16
> [ 47.314461] pctel_pci(233): PCTel device[0000:00:0b.0](0x58) found
> 134d:7890 (rev 02), iobase=0xe400, irq=16.
> [ 47.314465] pctel_pci(609): Setup PCI port: port 0xe400, irq 16,
> type 0, membase 00000000, ops 00000000
> [ 47.314477] ttyS_PCTEL0 at I/O 0xe400 (irq = 16) is a PCTel
>
> Something that worried me was that line that says that the device is
> grabed by driver serial, but there is no module serial loaded, and I
> disabled all serial ports from the bios, but this message is still
> there.
> So i tried with ungrab-winmodem, after unloading the modem modules and
> loading ungrab-winmodem, loading modem modules didn't show that
> message, but still there was no answer from the modem, I was again in
> the case where empty values were returned from the ATI queries.
>
> I attach the ModemData.txt output of scanModem for more details.
>
> Thank you very much,
>
> Merry Christmas and Happy New year to everybody
>
> Santiago.
>
