removido
(usa Nenhuma)
Enviado em 08/08/2007 - 09:59h
Olá galera que curte fedora. Eu era usuário red hat e migrei para o fedora 7. No red hat eu conseguia me conectar beleza à internet usando um modem bem famoso: sm56 speaker phone da motorola.
Bom, instalei o fedora 7 gnome, quero me conectar à internet usando esse modem. Não sei como discar a conexão, e além disso, ao "passar" o scanmodem, obtive o seguinte arquivo modemdata.txt:
Only plain text email is forwarded by the DISCUSS@linmodems.org List Server.
Do use the following as the email Subject Line:
SomeName, YourCountry
Fedora release 7 (Moonshine)
Kernel kernel 2.6.21-1.3194.fc7
This will alert cogent experts, and distinguish cases in the Archives.
YourCountry will enable Country
Code guidance.
Occassionally responses are blocked by an Internet Provider mail filters.
So in a day, also check the Archived responses at
http://www.linmodems.org
.
Local Linux experts can be found through:
http://www.linux.org/groups/index.html
-------------------------- System information ----------------------------
CPU=i686, Fedora
release 7 (Moonshine)
Kernel
Linux version 2.6.21-1.3194.fc7 (kojibuilder@xenbuilder4.fedora.phx.redhat.com) (gcc version 4.1.2 20070502 (Red Hat 4.1.2-12)) #1 SMP
Wed May 23 22:35:01 EDT 2007
scanModem update of: 2007_August_04
ALSAversion 1.0.14rc2
USB modem not detected by lsusb
Modem or host audio card
candidates have firmware information:
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
00:09.0
1057:3052 1057:3020 Modem: Motorola SM56 Data Fax Modem
Modem interrupt assignment and sharing:
--- Bootup diagnostics for card in PCI
slot 00:09.0 ----
ACPI: PCI Interrupt 0000:00:09.0[A] -> GSI 17 (level, low) -> IRQ 16
0000:00:09.0: ttyS2 at I/O 0x9008 (irq = 16) is a 16450
0000:00:09.0: ttyS3 at I/O
0x9010 (irq = 16) is a 8250
Couldn't register serial port 0000:00:09.0: -28
=== Finished modem firmware and bootup diagnostics section. ===
=== Next deducing
cogent software ===
For candidate modem in PCI bus: 00:09.0
Class 0703: 1057:3052 Modem: Motorola SM56 Data Fax Modem
Primary PCI_id 1057:3052
Support type needed or chipset: slamr
1057:3052 has a Motorola chipset, poorly supported by Motorola itself
However Zello discovered that drivers written to
support Smartlink modems do support the 1057:3052 chipset!!
It sufficed to add 1057:3052 to the list of modem cards recognized by the Smartlink slamr driver.
There is
a ungrab-winmodem driver used in conjunction with slamr, which must have 1057:3052
similarly added. See messages from Zello:
http://linmodems.technion.ac.il/bigarch/archive-seventh/msg00846.html
http://linmodems.technion.ac.il/bigarch/archive-seventh/msg00848.html
and Alvaro Aguirre
about the ungrab-winmodem fix:
http://linmodems.technion.ac.il/bigarch/archive-seventh/msg00990.html
For general guidance on ungrab-winmodem + slamr usage,
read the Smartlink.txt
The modem is supported by the Smartlink slamr driver
plus the slmodemd helper utility. Read the
Smartlink.txt and Modem/YourSystem.txt for
follow through guidance.
Writing Smartlink.txt
============ end Smartlink section =====================
Completed candidate modem analyses.
The
base of the UDEV device file system is: /dev/.udev
The kernel was compiled with gcc version 4.1.2 and a compiler is not installed
Kernel-header resources needed for
compiling are not manifestly ready!
If compiling is necessary packages must be installed, providing:
gcc-4.1 kernel-source-2.6.21-1.3194.fc7
If a driver
compilation files with message including some lack of some FileName.h (stdio.h for example.
Some additional kernel-header files need installation to /usr/include.
For
Debian/Ubuntu related distributions, run the following command to display the needed package list:
$ sudo apt-get -s install linux-kernel-devel
While some of the files may
be on the install CD, others may have to be found through
http://packages.ubuntu.com
For Ubunut feisty, additional packages required were:
build-essential curl
debhelper dpkg-dev g++ g++-4.1 gettext git-core gitk
html2text intltool-debian kernel-package kernel-wedge libc6-dev
libcurl3-gnutls libdigest-sha1-perl liberror-perl
libstdc++6-4.1-dev
linux-libc-dev po-debconf rcs tcl8.4 tk8.4
Checking pppd properties:
-r-xr-xr-x 1 root root 312332 2006-12-01 09:54 /usr/sbin/pppd
In case of
an "error 17" "serial loopback" problem, see:
http://phep2.technion.ac.il/linmodems/archive-sixth/msg02637.html
To enable dialout without Root permission do:
$ su - root (not for Ubuntu)
chmod a+x /usr/sbin/pppd
or under Ubuntu related Linuxes
chmod a+x /usr/sbin/pppd
Checking settings of:
/etc/ppp/options
lock
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
Read Modem/YourSystem.txt concerning other COMM channels: eth0
Which can interfere with
Browser naviagation.
Don't worry about the following, it is for the 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:
/etc/udev/rules.d/50-udev.rules:KERNEL=="modems/mwave*",
NAME="%k", GROUP="uucp", MODE="0660"
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 --------
Para quem teve paciência de olhar esse documento, a minha pergunta é: já que ele identificou o meu modem, como ativá-lo?