Logo Hardware.com.br
SSteel
SSteel Veterano Registrado
1.7K Mensagens 10 Curtidas

Hsp56 cm8738, sem tom de linha, alguem me ajude por favor.

#1 Por SSteel 12/04/2006 - 23:19
Ola pessoal.
Preciso do drive do modem hsp56 onboard.Tai o lpci (desculpa por encher a pagina)
  • 0000:00:00.0 Host bridge: Silicon Integrated Systems [SiS] 630 Host (rev 21) 0000:00:00.1 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (rev d0)
    0000:00:01.0 ISA bridge: Silicon Integrated Systems [SiS] SiS85C503/5513 (LPC Bridge)
    0000:00:01.1 Ethernet controller: Silicon Integrated Systems [SiS] SiS900 PCI Fast Ethernet (rev 83)
    0000:00:01.2 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller(rev 07)
    0000:00:01.3 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller(rev 07)
    0000:00:02.0 PCI bridge: Silicon Integrated Systems [SiS] Virtual PCI-to-PCI bridge (AGP)
    0000:00:0d.0 Multimedia audio controller: C-Media Electronics Inc CM8738 (rev 10)
    0000:00:0d.1 Communication controller: C-Media Electronics Inc CM8738 (rev 10)
    0000:01:00.0 VGA compatible controller: Silicon Integrated Systems [SiS] 630/730PCI/AGP VGA Display Adapter (rev 21)


Muito obrigado.
Marcelo de Matos Soeiro
Marcelo de M... Super Zumbi Registrado
13.3K Mensagens 159 Curtidas
#16 Por Marcelo de M...
18/06/2006 - 18:43
Esse chipset, ao que tudo indica, é um Smart Link remarcado, o driver funciona, sim. O Amdreh, se não me engano, instalou um através de um tópico que eu fiz para esses modems. Ele fica neste link:

https://www.hardware.com.br/comunidade/viewtopic.php?t=268347&highlight=

Dá uma olhadinha, se ainda não viu, e veja se te ajuda.
Fique com Deus.
Mandriva 2010.2 | GNOME 2.30 | Xfce 4.6.1 | KDE 4.5.5
Linux User 169925
E há de ser que todo aquele que invocar o nome do Senhor será salvo; (Jl 2:32)
Marcelo de Matos Soeiro
Marcelo de M... Super Zumbi Registrado
13.3K Mensagens 159 Curtidas
#22 Por Marcelo de M...
19/06/2006 - 08:54
Erros na compilação?!?! Sugiro, então, desinstalar e tentar de novo, pausadamente... embora muitas vezes a gente achar que fizemos tudo certinho, um pequeno detalhe escapa...
Fique com Deus.
Mandriva 2010.2 | GNOME 2.30 | Xfce 4.6.1 | KDE 4.5.5
Linux User 169925
E há de ser que todo aquele que invocar o nome do Senhor será salvo; (Jl 2:32)
SSteel
SSteel Veterano Registrado
1.7K Mensagens 10 Curtidas
#23 Por SSteel
19/06/2006 - 09:40
error: mdm setup: cannot open dev `/dev/slamr0': No such device or address
error: cannot setup device `/dev/slamr0'

Esse erro, quando eu configuro o codigo de area.
Vou fazer uma ultima tentativa com esse drive.
Me fassa um passo a passo pra mim seguir.
obs: quando eu inicio o kurumin ele fala que os ttyS0,ttyS1,... nao existem tem algo a ver?
Servo
Servo Geek Registrado
3K Mensagens 27 Curtidas
#24 Por Servo
19/06/2006 - 11:38
Tenta de novo como o Marcelo disse, eu tive q tentar umas 4 vezes para funcionar no Mandriva, e quando instalei direito precisou do detalhe de um caminho para que o moden fosse reconhecido...tenha paciência, o seu moden tem chipset smartlink que é um dos melhores para instalar em linux. Ah eu tenho um pacote .deb feito pelo Alarcon que pode resolver teu problema automaticamente. Quando usei o kurumin e fui para o 6 o meu moden não foi mais reconhecido...com o pacote a instalação foi automática...Se quiser te passo este arquivo :wink:

Deus te abençoe!
Aptosid->> (Notebook)

Linux User: 422853

arkRed">Visite o site: www.euecristo.com.br


SSteel
SSteel Veterano Registrado
1.7K Mensagens 10 Curtidas
#25 Por SSteel
29/07/2006 - 17:32
Pessoal vou fazer uma ultima tentativa...
Por favor me passem um passo-a-passo para Kurumin.Vou seguir rigidamente todos os passos e qualquer erro apresentado vou postar.
E outra coisa como posso identificar erros na compilaçao.Aparentemente nenhum erro ocorre aqui, mas se eu souber +/- qual a messagem que vai ser apresentada no caso de algum erro fica mais facil.
Valeu pessoal, para todos aqueles me ajudaram.
Muito obrigado.

Edit: Pessoal... quando eu vou entrar no sistema aparece a seguinte menssagem load stat /dev/ttyS0 no souce file or directory

E tambem os slamr* e ttyS* nao existem na pasta /dev/ só aparecem em seguida na instalaçao do pacote depois somem.
Chino Ventura
Chino Ventur... Geek Registrado
2.7K Mensagens 78 Curtidas
#27 Por Chino Ventur...
31/07/2006 - 03:22
V o que está escrito no leia-me que está incluso no pacote do driver que uso, tenho um Pctel pci...:
PCTEL Driver for Linux Version 0.9.7-9-rht-6
============================================

This version (6) is modified to work with Kernel 2.6.16. It now uses
module_param instead of the deprecated MODULE_PARM. There is a fix for
excessive lock taking which was causing Fedora Core 4/5 to hang. There
is also an update to the FAQ regarding Fedora Core 5 kernels.
-- Robert Thornburrow <robert.thornburrow@tsac.fsnet.co.uk> 25/05/06

This version (5) is modified to work with Fedora Core 4, which had problems
controlling the mouse when the modem driver was loaded. The fix now correctly
saves and restores the FPU registers. There is also a fix to allow the driver
to work with kernel 2.6.13 which has an API change of pci_match_device() to
pci_match_id() and a fix for a compile error where linux/mca.h is not included.
There are also a number of fixes to the configure script to support udev and
setup now attempts to load the newly created modules.
-- Robert Thornburrow <robert.thornburrow@tsac.fsnet.co.uk> 02/04/06

This version (4c) is modified to include Gustavo Brabieri and Co's 2.6 driver
and some further changes to make the code fully 2.6 compatible, though the only
modem this currently works for is the pct789 (specifically PCI Id 134d:7897).
It also fixes a problem with some missing symbols in the via686a libraries,
which do not contain the audio routing symbols. There is also a fix for sis
which was broken by the previous release having an incorrect ifdef around the
i8xx HAL specific code. There are also fixes to the configure script to make
this work on 2.6 and with different versions of lspci. The install option now
contains the missing "/sbin/depmod -a".
This driver is known to cause problems with the mouse on Fedora Core 4 - this
is either a problem with the Fedora applied kernel patches, or the use of GCC
4.0 to compile the kernel. The best solution we have at the moment is to
downgrade to Fedora Core 3. No other distros seem to exhibit the same problem.
-- Robert Thornburrow <robert.thornburrow@tsac.fsnet.co.uk> 25/08/05

This version (3) is modified to print the codec vendor id when the "i8xx" HAL is
used, and also to report whether it is supported by the driver. Also added
Intel 82801DB/DBM AC'97 Audio Controller (8086:24c5) to the "i8xx" HAL.
-- Robert Thornburrow <robert.thornburrow@tsac.fsnet.co.uk> 07/05/04

This version (2) is modified to support Fedore Core, which defines tty->count
as atomic_t instead of int. The configure script detects this and sets an
appropriate define to make the code compile.
-- Robert Thornburrow <robert.thornburrow@tsac.fsnet.co.uk> 21/04/04

This version modified in order to support VendorId 8086:24c6
(Intel 82801DCM AC'97 Modem controller)
-- Robert Thornburrow <robert.thornburrow@tsac.fsnet.co.uk> 09/04/04


1. Installation
===============

1.1 Automatic installation (for beginners)
------------------------------------------
- You must be root
- You must have installed a c compiler and development tools like
make, perl, ...
- You must have lspci in a standard path (for automated install)
- You must have installed your kernel sources, which corresponds
to your current running kernel


a) tar zxvf pctel-version.tar.gz

b) cd pctel/

c) ./setup

If everything was ok, you will see the message "installation done" at the
end of the output.

1.2 Manual installation (for experts)
-------------------------------------
- You must be root for part (e), you can run (a)-(d) as an ordinary user if you
wish
- You must have installed a C compiler and development tools like
make, perl, ...
- You must have installed your kernel sources, which corresponds
to your current running kernel


a) tar zxvf pctel-v.w.x-y-rht-z.tar.gz

b) cd pctel-v.w.x-y-rht-z/src/

c) ./configure -manual

d) make

e) make install


2. Try your driver
==================
Just to try out, if your driver works:

2.4: 2.6:
insmod pctel modprobe linmodem
insmod ptserial modprobe pctel
modprobe pctel_hw
or

insmod -f pctel
insmod ptserial

-f means "force", which means, it will force loading the driver, even
with warnings.

then, look at:

lsmod

it should print pctel and ptserial (2.4) or linmodem, pctel and pctel_hw (2.6).

Look at the last few lines of dmesg to see whether the driver found the
modem or not:

dmesg | tail

If the driver is not finding the modem, and you have either a PCtel or
C-Media device you can try using the vendor_id and device_id arguments with
insmod(you can find these using lspci):

insmod ptserial vendor_id=0x1234 device_id=0x5678

Note that vendor_id and device_id do not work with Intel, Sis or Via devices.

3. Loading your driver permanently
==================================
NOT YET WRITTEN


Appendix I. PCI IDs of recognized modems
========================================
This table summarises the PCI devices that this driver supports. For AC'97
modems, this does not guarantee that the driver will work, as this is only part
of the modem - the other part, the codec, must also be compatible for the
driver to work.

PCI ID (x) Name Chip(set) HAL
~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~ ~~~~~~~
1039:7013* SiS AC'97 Modem Controller SIS540 MR sis
1106:3068* VIA Intel 537 [AC97 Modem] VIA686A MR via686a
134d:7890 PCtel HSP MicroModem 56 PCT789T-C1 pct789
134d:7891 PCtel HSP MicroModem 56 PCT 789T pct789
134d:7892 PCtel HSP MicroModem 56 PCT 789T-A pct789
134d:7893 PCtel HSP MicroModem 56 S911 K017 pct789
134d:7894 PCtel HSP MicroModem 56 FT13 pct789
134d:7895 PCtel HSP MicroModem 56 PCT789T-C1 pct789
134d:7896 PCtel HSP MicroModem 56 PCT789T-C1 pct789
134d:7897 PCtel HSP MicroModem 56 PCT789T pct789
13f6:0211 C-Media CM8738 CM8738 cm8738
8086:2416* Intel 82801AA (ICHAA) AC'97 Modem i810 MR i8xx
8086:2446* Intel 537 [82801BA/M (ICH2) AC'97 Modem] i820 i8xx
8086:2486* Intel 82801CA/M (ICH3) AC'97 Modem Ctlr i845 i8xx
8086:24c6* Intel 82801DB/M (ICH4) AC'97 Modem Ctlr i855PN laptop i8xx
8086:7196* Intel 82440MX (Banister) AC'97 Modem Ctlr i810 MR laptp i8xx

* No 2.6 support - these modems are only suppoerted under 2.4 kernels.


Appendix II. Supported AC'97 Codecs
===================================
This version (3) supports the printing of AC'97 Codec Vendor IDs when compiled
with the "i8xx" HAL (hopefully the "sis" and "via686a" HALs will follow). To
find out which codec your modem contains, you need to load "ptserial" (and
"pctel&quot modules and then start something like "minicom". The codec vendor id
will be printed when the modem device is used (usually /dev/modem, symlinked
/dev/ttyS15 under 2.4 and /dev/ttyS_PCTEL0 under 2.6). Look for a message
(using "dmesg | tail&quot of the form:

Found codec SIL33 of type 2

The codec vendor id is "SIL33" (note that the number is in decimal - slamr
prints the same thing in hex - duh! - so this would equate to "SIL21&quot. This
indicates a Silicon Laboratories Si3038 codec, as used by PCTel. The type 2
is an internal code, which catagorises the codec's compatability. It has no
meaning outside of this driver.

The following codecs are recognised by the "i8xx" HAL (and presumably the other
AC'97 HALs as well):

Codec Type Codec Name
~~~~~~ ~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DT2-49 1 (PCTel Delta?)
DT2-50 1 (PCTel Delta?)
SIL17 2 Silicon Laboratories Si???? (PCTel Stinger?)
SIL33 2 Silicon Laboratories Si3038 (PCTel)
TRA9 3 TriTech


Appendix III. ptserial Module Options
=====================================
The 2.4 "ptserial" module supports the following options:

Option Meaning
~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
country_code=n Sets the Country Code (see Appendix IV) to "n"
irq=n Attempts to attach the device to IRQ "n"
iobase=n Looks for a device at iobase address "n".

iobase1=n Forces the driver to load for the device with the given iobase,
iobase1 and irq. "i8xx" and "via686a" HALs only

vendor_id=n Forces the driver to load for the device with the given vendor
& device_id=n and device ids. "pct789" and "cm8738" HALs only


The 2.6 modules support the following options:

Option Module Meaning
~~~~~~~~~~~~~~ ~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
country_code=n pctel Sets the Country Code (see Appendix IV) to "n"
irq=n pctel_hw Attempts to attach the device to IRQ "n"


Appendix IV. Country Codes
==========================

Code Country Code Country Code Country
~~~~ ~~~~~~~~~~~~~ ~~~~ ~~~~~~~~~~~~~ ~~~~ ~~~~~~~~~~~~~~~
1 USA 12 KOREA 23 DENMARK
2 FRANCE 13 SWITZERLAND 24 AUSTRIA
3 GERMANY 14 NORWAY 25 S.AFRICA
4 ITALY 15 NETHERLANDS 26 CTR21 COUNTRIES
5 SWEDEN 16 BELGIUM 27 CHINA
6 UK 17 CANADA 28 MALAYSIA
7 JAPAN 18 IRELAND 29 LUXUMBURG
8 AUSTRALIA 19 PORTUGAL 30 GREECE
9 SPAIN 20 POLAND 31 ICELAND
10 TAIWAN 21 HUNGARY 32 NEW ZEALAND
11 SINGAPORE 22 FINLAND 33 BRAZIL


$Id: README,v 1.12 2006/04/04 14:45:04 robert Exp $


É isso aí...deve dar pra clarear um pouco mais..valeu!
______________________________________________
"Simple' is defined from a technical standpoint, not a usability standpoint. It is better to be technically elegant with a higher learning curve, than to be easy to use, and technically crap." by Aaron Griffin
Linux User: # 432048
SSteel
SSteel Veterano Registrado
1.7K Mensagens 10 Curtidas
#28 Por SSteel
31/07/2006 - 21:42
Digitei make e acontece isso:

LD binary.a
make -C /lib/modules/2.6.14-kanotix-6/build M=/home/kurumin/Meus Documentos/pctel-0.9.7-9-rht-6/src
make[1]: Entering directory `/usr/src/linux-headers-2.6.14-kanotix-6'
make[1]: *** Sem regra para processar o alvo `Documentos/pctel-0.9.7-9-rht-6/src'. Pare.
make[1]: Leaving directory `/usr/src/linux-headers-2.6.14-kanotix-6'
make: ** [all] Erro 2

Obs: Ele reconhece meu modem.
SSteel
SSteel Veterano Registrado
1.7K Mensagens 10 Curtidas
#30 Por SSteel
02/08/2006 - 21:49
Mas o que voces me dizem, o fato de que os ttyS* e os Slamr* sumirem apos o boot se deve a algum erro no pacote ou o problema é no meu Sistema ?
O Marcelo, o 2006 tambem nao funfo.Assim que instalei entrei no Kppp e recebi a menssagem ,"nao é possivel abrir o modem" pensei: nossa que bom agora vou só reiniciar e acho que vai dar certo ! Bom reiniciei e voltou no problema dos slamr* e os ttyS* sumirem apos reiniciar.
© 1999-2024 Hardware.com.br. Todos os direitos reservados.
Imagem do Modal