Ayuda para conectar Ubuntu con Dial Up

No puedo hacer la coneccion Dial Up e icesword me comento que hiciera lo siguiente:
"busca el archivo deteccionmodem.txt en tu carpeta personal y metelo en un pen o pasalo a la particion de windows copia abrilo copia y pega la info que te da ese comando aca asi vemos que modem tenes y como podes instalarlo"

Aqui dejo la informacion, y les comento que el drive de el modem ( tengo el CD ) viene una carpeta que dice Linux, quise instalarlo desde el CD pero no pude en el ubuntu. Sigo atento a las instrucciones...

Cordial saludo

Da error el adjunto, de última copiá y pegá acá que dice el log o bien usá alguna página como www.binpaste.com para pegarlo.

si y en lo posible trata de responder en el mismo tema que abris asi es mas facil seguir los progresos de tu problema

Buen dia , antes que nada les agradezco y a la vez les comento que este es el resultado. Ok, seguire sus recomendaciones.

Saludos

http://www.binpaste.com/v.php?id=3sw4g

00:00.0 Host bridge: Intel Corporation 82946GZ/PL/GL Memory Controller Hub (rev 02)
00:02.0 VGA compatible controller: Intel Corporation 82946GZ/GL Integrated Graphics Controller (rev 02)
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 01)
00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 01)
00:1c.2 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 3 (rev 01)
00:1c.3 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 4 (rev 01)
00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 (rev 01)
00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 (rev 01)
00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 (rev 01)
00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 (rev 01)
00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 01)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev e1)
00:1f.0 ISA bridge: Intel Corporation 82801GB/GR (ICH7 Family) LPC Interface Bridge (rev 01)
00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 01)
00:1f.2 IDE interface: Intel Corporation 82801GB/GR/GH (ICH7 Family) SATA IDE Controller (rev 01)
00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 01)
04:00.0 Modem: Intel Corporation FA82537EP 56K V.92 Data/Fax Modem PCI (rev 04)
04:01.0 Multimedia controller: Philips Semiconductors SAA7130 Video Broadcast Decoder (rev 01)
04:08.0 Ethernet controller: Intel Corporation PRO/100 VE Network Connection (rev 01)

He estado buscando en google y nada. Ahora solo les pido una recomendacion ...que version de ubuntu se facilitaria para conectarme a internet con Dial up?
y bueno espero seguir contando con su apoyo .

04:00.0 Modem: Intel Corporation FA82537EP 56K V.92 Data/Fax Modem PCI (rev 04)

Ahí te da la info de tu modem. Ahora, lo que yo haría es ir a los foros oficiales de Ubuntu y empezar a buscar temas relacionados con tu modem. Por ej.
https://help.ubuntu.com/community/DialupModemHowto/Intel537EP

http://ubuntuforums.org/showthread.php?t=1183886&highlight=FA82537EP
http://ubuntuforums.org/showthread.php?t=1181859&highlight=FA82537EP

Ponete tranquilo, con paciencia, lee y tratá de hacerlo andar.

Hola Brothers.
Les comento que consegui la version 8.4 y esta disco que me grabaron si me da la opcion de "Instalar dentro de Windows" .
Para eso me pide que me conecte con Dial Up, hasta ahi todo bien.
Tengo preguntas:
1. Cuando termine de descargarse de esta forma Ubuntu ...ya no tendre problemas con la coneccion Dial Up en Ubuntu ?

2. En esta forma de instalacion corre solo Ubuntu sin que tenga nada que ver WindowsXp ?

Gracias

Ya instale la version 9.04 de ubuntu , pero aun no logro conectrme, segui un tutorial
http://ar.geocities.com/novatocba/

Mi pc tiene AMD Athlon 1.20 GHz 768 RAM disco dro de 40GB y uso el winXP.

Ya fue reconocido el modem Intel 536EP configure el documento de wvdial.conf, despues ejecute en la Terminal sudo pppconfig y segui todos los pasos;me encontre con una ventana donde dice que hay que elegir PAP, CHAT elegi CHAT (estoy bien?); cuando llegue para indicar donde esta el modem (en xp se usa el puerto COM3) pero en ubunto me dice que es /dev/ttySL0, este SL0 no existe solo S0 y pertenece a al puerto COM1, le deje SL0;finalmente cree 2 lanzadores en el escritorio son sudo wvdial (conectar)y sudo killall wvdial (desconectar) cual es la forma correcta para usarlos?

Aqui dejo la informacion de ModemData.txt
Only plain text email is forwarded by the Discuss@Linmodems.org List Server,
as HTML can contain viruses. Use as the email Subject Line:
YourName, YourCountry kernel 2.6.28-11-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@Linmodems.org 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,
Linux version 2.6.28-11-generic (buildd@palmer) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC 2009
scanModem update of: 2009_07_02

The dialer utility package WVDIAL does not appear to be installed on your System.
Please read Modem/DOCs/wvdial.txt

There are no blacklisted modem drivers in /etc/modprobe* files
Potentially useful modem drivers now loaded are:


Attached USB devices are:
ID 13fe:1d00 Kingston Technology Company Inc. DataTraveler 2.0 1GB/4GB Flash Drive / Patriot Xporter 4GB Flash Drive
If a cellphone is not detected, see http://ubuntuforums.org/archive/index.php/t-878554.html

If a USB modem or cellphone is attached and was not detected, please
provide available information in your request to discuss@linmodems.org

For candidate card in slot 00:0a.0, firmware information and bootup diagnostics are:
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
00:0a.0 8086:1040 8086:1000 Communication controller: Intel Corporation 536EP Data Fax Modem

Modem interrupt assignment and sharing:
10: 8468649 XT-PIC-XT ehci_hcd:usb1, ohci_hcd:usb3, uhci_hcd:usb5, ALI 5451
--- Bootup diagnostics for card in PCI slot 00:0a.0 ----
[ 0.305493] pci 0000:00:0a.0: reg 10 32bit mmio: [0xdf800000-0xdfbfffff]
[ 0.305524] pci 0000:00:0a.0: supports D2
[ 0.305527] pci 0000:00:0a.0: PME# supported from D2 D3hot D3cold
[ 0.305533] pci 0000:00:0a.0: PME# disabled
[ 2.399187] uhci_hcd 0000:00:09.1: sharing IRQ 10 with 0000:00:0a.0

The PCI slot 00:0a.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@linmodems.org
if help is needed.


For candidate card in slot 00:03.0, firmware information and bootup diagnostics are:
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
00:03.0 10b9:5451 10b9:5451 Multimedia audio controller: ALi Corporation M5451 PCI AC-Link Controller Audio Device

Modem interrupt assignment and sharing:
10: 8469677 XT-PIC-XT ehci_hcd:usb1, ohci_hcd:usb3, uhci_hcd:usb5, ALI 5451
--- Bootup diagnostics for card in PCI slot 00:03.0 ----
[ 0.305079] pci 0000:00:03.0: reg 10 io port: [0xd800-0xd8ff]
[ 0.305087] pci 0000:00:03.0: reg 14 32bit mmio: [0xdfffe000-0xdfffefff]
[ 0.305113] pci 0000:00:03.0: supports D1 D2
[ 0.305117] pci 0000:00:03.0: PME# supported from D2 D3hot D3cold
[ 0.305124] pci 0000:00:03.0: PME# disabled
[ 13.824183] ALI 5451 0000:00:03.0: assigned PCI INT A -> IRQ 10

The PCI slot 00:03.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@linmodems.org
if help is needed.



===== Advanced Linux Sound Architecture (ALSA) diagnostics =====
The ALSA packages provide audio support and also drivers for some modems.
ALSA diagnostics are written during bootup to /proc/asound/ folders.

The ALSA verion is 1.0.18
The modem cards detected by "aplay -l" are: None


The /proc/asound/pcm file reports:
-----------------------
00-00: ALI 5451 : ALI 5451 : playback 32 : capture 1

about /proc/asound/cards:
------------------------
0 [A5451 ]: ALI5451 - ALI 5451
ALI 5451 at 0xd800, irq 10
=== Finished firmware and bootup diagnostics, next deducing cogent software. ===

Predictive diagnostics for card in bus 00:03.0:
Modem chipset detected on
NAME="Multimedia audio controller: ALi Corporation M5451 PCI AC-Link Controller Audio Device "
CLASS=0401
PCIDEV=10b9:5451
SUBSYS=10b9:5451
IRQ=10
SOFT=10b9:5451.MC97
IDENT=slmodemd
SLMODEMD_DEVICE=hw:0,1
Driver=snd-ali5451

For candidate modem in: 00:03.0
0401 Multimedia audio controller: ALi Corporation M5451 PCI AC-Link Controller Audio Device
Primary device ID: 10b9:5451
Subsystem PCI_id 10b9:5451
Softmodem codec or chipset from diagnostics:
from Archives:



Support type needed or chipset: slmodemd

An ALSA (Advanced Linux Sound Architecture) modem driver: snd-ali5451
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:
sudo slmodemd -c YOUR_COUNTRY --alsa -shw:0,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.

Writing DOCs/Smartlink.txt
============ end Smartlink section =====================


Predictive diagnostics for card in bus 00:0a.0:
Modem chipset detected on
NAME="Communication controller: Intel Corporation 536EP Data Fax Modem"
CLASS=0780
PCIDEV=8086:1040
SUBSYS=8086:1000
IRQ=10
IDENT=INTEL536EP

For candidate modem in: 00:0a.0
0780 Communication controller: Intel Corporation 536EP Data Fax Modem
Primary device ID: 8086:1040
Support type needed or chipset: INTEL536EP



Completed candidate modem analyses.

The base of the UDEV device file system is: /dev/.udev

Versions adequately match for the compiler installed: 4.3.3
and the compiler used in kernel assembly: 4.3.3

The patch utility is needed and is needed for compiling ALSA drivers, and possibly others.


Minimal compiling resources appear complete:
make utility - /usr/bin/make
Compiler version 4.3
linuc_headers base folder /lib/modules/2.6.28-11-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 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


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:
/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
Within any ancient /etc/devfs files:

Within ancient kernel 2.4.n /etc/module.conf files:

--------- end modem support lines --------

Aqui dejo el wvdial.txt

Modem usage is accomplished through drivers, sometimes some helper software,
and the core communication work horse "pppd". Usually it will be found at
/usr/sbin/pppd with permissions shown on my Ubuntu system by:
$ ls -l /usr/sbin/pppd
-rwsr-xr-- 1 root dip 257720 2006-07-05 08:58 /usr/sbin/pppd
The s means "sticky" meaning only one person can use pppd at a time.
As installed, it requires Root/Adm permissions to use pppd, directly or
through front end dialer tools. This is a security precaution common to
all COMM channels. But if you want to enable a simple User to dialout,
as is basically OK for a single user PC, do:
$ su - root
# chmod a+x /usr/sbin/pppd
or for Ubuntu:
$ sudo chmod a+x /usr/sbin/pppd
after which there will be seen:
$ ls -l /usr/sbin/pppd
-rwsr-xr-x 1 root dip 257720 2006-07-05 08:58 /usr/sbin/pppd
with the last x meaning any one can execute pppd, either directly or
much more commonly through a front end dialer such as wvdial of KPPP.

The preferred dialer utility for modem testing is wvdial, having a configuration utility: conf
wvdialconf is called during testing of some modem drivers. Particularly if your
modem uses the driver martian_dev of helper utility slmodemd, please install the
wvdial package!! For other drivers, dialers such as gnomeppp or kppp may be adequate.
but wvdial is still preferred for testing.

Configuration file for wvdial
-------------------------------
There is a very smart dialer utility "wvdial"
which can be used once basic modem setup is accomplished. A configuration file
is needed, which begins below with [Dialer defaults]. This file can be accessed
any where by:
$ wvdial --config Path_to/configuration_file
Most commonly the configuration file is saved as:
/etc/wvdial.conf
whereat it will serve all Users of the computer. If saved as:
/home/LoginName/.wvdial.rc
it will be found and used before /etc/wvdial.conf. Note that "." beginning
a file name means "do not show it", except through usage of:
$ ls -a
Many local configuration files are thus "hidden" in your /home/LoginName/ folder

Some Linux installations have dialup tools like Kinternet, GnomePPP, and the
Redhat/Fedora Internet Connection Wizard which are front ends for wvdial and
will write /etc/wvdial.conf files. For this reason, it is advisable to test
your configuration file first, before copying it to /etc/wvdial.conf. Typically
a first test is run with:
$ sudo wvdialconf wvtest
which will search ports with names: /dev/modem /dev/ttyS* /dev/rfcomm*.
A successful ouput include a section like:
WvModem<*1>: Cannot get information for serial port.
ttySL0<*1>: ATQ0 V1 E1 -- OK
ttySL0<*1>: ATQ0 V1 E1 Z -- OK
ttySL0<*1>: ATQ0 V1 E1 S0=0 -- OK
ttySL0<*1>: ATQ0 V1 E1 S0=0 &C1 -- OK
ttySL0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 -- OK
ttySL0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK
Note: above lines are testing the driver, modem firmware is then first read by ATI
ttySL0<*1>: Modem Identifier: ATI -- SmartLink Soft Modem
ttySL0<*1>: Speed 4800: AT -- OK
ttySL0<*1>: Speed 9600: AT -- OK
ttySL0<*1>: Speed 19200: AT -- OK
ttySL0<*1>: Speed 38400: AT -- OK
ttySL0<*1>: Speed 57600: AT -- OK
ttySL0<*1>: Speed 115200: AT -- OK
ttySL0<*1>: Speed 230400: AT -- OK
ttySL0<*1>: Speed 460800: AT -- OK
ttySL0<*1>: Max speed is 460800; that should be safe.
ttySL0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK

Found a modem on /dev/ttySL0.
Modem configuration written to wvtest.
ttySL0<Info>: Speed 460800; init "ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0"
------
will be included in a successful run, where in this case /dev/ttySL0
is the responding device port. The generated wvtest file is:
[Dialer Defaults]
Modem = /dev/ttySL0
Baud = 460800
Init1 = ATZ
Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
ISDN = 0
Modem Type = Analog Modem
; Phone = <Target Phone Number>
; Username = <Your Login Name>
; Password = <Your Password>

which at a minimim must be edited to a form like:
[Dialer Defaults]
Modem = /dev/ttySL0
Baud = 115200
Init1 = ATZ
Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
ISDN = 0
Modem Type = Analog Modem
Phone = 14759108
Username = 1501286793@ilimitado.com
Password = 139932

Additional if your modem port is of the type /dev/pts/N , with N a number,
then there MUST be added a line:
Carrier Check = no
This requirement currently applies to dialups using the helper utility: slmodemd
together with slamr, slusb or ALSA modem drivers, OR the " " : martian_helper
used with the martian_dev for Lucent/Agere modems with DSP chipsets.

Then a test dialput can be done with:
$ sudo wvdial --config wvtest

There are some Systems for which the wvdialconf test will stall at rfcomm ports.
This is a wvdialconf bug and can be bypassed by just using wvdial with a trial
wvtest, but you need to specify the port appropriate to your modem.

If the configuration file below, lines beginning with # are comments.
Removing a # will activate a line with wvdial instructions appropriate to
special circumstances.


[Dialer defaults]
# Lines begining with # are comments.
# wvdial will look for this file at /etc/wvdial.conf or /home/LoginName/.wvdial.rc

# Redhat/Fedora have an Internet Connection Wizard in the popup menus
# ICW will write a two part /etc/wvdial.conf supporting multiple modem usage.

Modem = ModemPort
# typically a symbolic link to the true port is used, /dev/modem or /dev/ttyS*
# wvdialconf will test all port names /dev/modem and /dev/ttyS*

Init1 = ATZ
Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
# Lack of dialtone acquisition can be due to low line voltage,
# a common problem in Italy.
# Try inserting a "dial without waiting": X3
# Init2 = ATQ0 V1 E1 S0=0 X3 &C1 &D2 +FCLASS=0
# In case of connection instabilities, specify a lower frequency:
# Init2 = ATQ0 V1 E1 S0=0 X3 &C1 &D2 +MS=34
# a MS=90 option is sometimes necessary for Internet Providers with buggy V92 protocols:
# Init2 = ATQ0 V1 E1 S0=0 X3 &C1 &D2 +MS=90
ISDN = 0
Modem Type = Analog Modem
# Dial Command = ATDP
## replaces Touch Tone prefix ATDT to Dialout_phone_number, with older Pulse prefix ATDP

Phone = Dialout_phone_number
# if going through a switch board, a perhaps necessary pause can produced with a comma:
# Phone = 1,Dialout_phone_number
Username = LoginName
# if Internet Provider is MSN.net or uses CHAP authentication, use under Linux:
#Username = MSN/LoginName

Password = YourPassWord

# the following lines is NEEDED only for usage with slmodemd or martian_helper
Carrier check = no
# Kinternet appears to add it automatically.

## If CONNECT is achieved but browsing fails, try activating the following line
# Auto DNS = yes
## To make a logfile wvdial.out
# wvdial 2>&1 | tee wvdial.out
# # For some Internet providers, the following line is necessary
# Stupid Mode = yes
## for other wvdial options, do "man wvdial" or see the documentation in
## /usr/share/doc/wvdial/

# to dial an alternate provide use "wvdial 2nd" which will preferentially read:
[Dialer 2nd]
Phone = 2nd_phone_number
Username = 2nd_LoginName
Password = 2nd_PassWord

## End wvdial config file

Ayudenme plis, creo k ya estoy cerca, me interesan sus opiniones.

Gracias comunidad

La ventana al terminar la configuracion del Dial up quedo asi:
Utilidad de configuracion GNU/Linux PPP>>>

<<Propiedades de todito>>
selecciones la propiedad qu desea modificar, seleccione <<Cancelar>> para
Number <Aqui anote el numero que voy a marcar:14759108>
ISPLogin <Anote el numero de usuario:1501286793@ilimitado.com >
User < todito> Nombre de usuario ISP
ISPPrompt < 139932 > pregunta de contraseña
Password <Contraseña ISP 139932>
Speed < Velocidad de puerto 115200 >
Com < /dev/ttyS0 > puerto com del módem
Method < chat > método de autentificacion

Advance Opciones avanzadas

Finished Escribir....
Previous Volver...
Quit Salir .....

Despues de tantos intentos, finalmente opte por contratar banda ancha, ahora todo anda bien en la PC el cual tiene conectado una impresora y escaner los cuales Ubuntu 9.04 los reconocio sin ningun problema.

Gracias a El-NoXa y a icesword por su valioso tiempo.....

Por ultimo como cierro este tema?

Cordial saludo.