Re: modem problems

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

 



Mario,

Good work, even though the modem is not working/connecting you to the internet:

You did do what scanModem recommends:
Support type needed or chipset:	slmodemd

 An ALSA (Advanced Linux Sound Architecture) modem driver:  snd-intel8x0m
 provides Low Level support enabling contact with the modem hardware.
 For all BUT Conexant chip soft modems (using hsfmodem software)
 complementary High Level support is through a Smartlink utility:  slmodemd

 Download from http://linmodems.technion.ac.il/packages/smartlink/
 the package SLMODEMD.gcc4.3.tar.gz having a compiled slmodemd. Unpack
under Linux with:
 	$ tar zxf SLMODEMD.gcc4.3.tar.gz
 and read instructions therein. But briefly, the modem is setup with command:
 	 slmodemd -c YOUR_COUNTRY --alsa modem:1
 reporting dynamic creation of ports:
	/dev/ttySL0 --> /dev/pts/N   , with N some number
 Read DOCs/Smartlink.txt and Modem/DOCs/YourSystem.txt for follow
through guidance.

Also you provided examples of your wvdial connections and also did
send in the dmesg.txt like this part suggested:

 Modem interrupt assignment and sharing:
  5:        736    XT-PIC-XT        Intel 82801DB-ICH4 Modem, yenta,
Intel 82801DB-ICH4
 --- Bootup diagnostics for card in PCI slot 00:1f.6 ----
ACPI: PCI Interrupt 0000:00:1f.6[B] -> Link [LNKB] -> GSI 5 (level,
low) -> IRQ 5
ACPI: PCI interrupt for device 0000:00:1f.6 disabled
ACPI: PCI Interrupt 0000:00:1f.6[B] -> Link [LNKB] -> GSI 5 (level,
low) -> IRQ 5
PCI: Setting latency timer of device 0000:00:1f.6 to 64

 The PCI slot 00:1f.6 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.


This is your wvdial.conf file:

[Dialer Defaults]
Init1 = ATZ
Init2 = ATQ0 X3 V1 E1 S0=0 &C1 &D2 +FCLASS=0
Modem = /dev/ttySL0
Phone = 7007000055
Idle Seconds = 300

Modem Type = Analog Modem
Stupid Mode = yes
Baud = 460800
Auto DNS = 1
Dial Command = ATDT
Ask Password = 1
ISDN = 0
Username = *myusername*
Password = *mypassword*
Carrier Check = no
Auto Reconnect = 0
Login Prompt = 1

I would try the following changes: add X3 and +MS=34 or +MS=90

[Dialer Defaults]
Init1 = ATZ
Init2 = ATQ0 X3 V1 E1 S0=0 X3 &C1 &D2 +MS=34
Modem = /dev/ttySL0
Phone = 7007000055
Modem Type = Analog Modem
Stupid Mode = yes
Baud = 460800
ISDN = 0
Username = *myusername*
Password = *mypassword*
Carrier Check = no

Also part of dmesg shows an eth0 device,

eth0: RealTek RTL8139 at 0xde826000, 00:40:d0:75:02:ec, IRQ 3
eth0:  Identified 8139 chip type 'RTL-8100B/8139D'


before you attempt a dialup you should do a
# ifconfig eth0 down

that way eth0 won't interfere with connection.  I also see this part:

intel8x0_measure_ac97_clock: measured 55357 usecs
intel8x0: clocking to 48000

that might/might not affect the connection.

Hope this helps in some way.

Regards,

Antonio

On Thu, Oct 9, 2008 at 11:36 AM, mario carlotti <carlotti.m@xxxxxxxxx> wrote:
> First of all thanks for your help.
> I didn't get my modem working till now, so I try another time.
> I'm getting tired, maybe it is better to disinstall openSuse and try
> another distribution; what do you think about that?
> I attach ModemData, plus dmesg and a file with the description of what
> my modem does(does not).
> Thanks again
> Mario Carlotti
>

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

  Powered by Linux