Modem ne okrece broj?

• 0Niko još nije pohvalio poruku.
  Registruj se da bi pohvalio/la poruku!

Uzmi neki externi robotiks npr.

• 0Niko još nije pohvalio poruku.
  Registruj se da bi pohvalio/la poruku!

Strog ::Da, ja mislim da Lucenti sa Agere cipsetom nisu jos uvek podrzani pod Linuxom

Pa sto ne rece ranije
Ja sam se nevidjeno cimao oko toga i probavao sve i svasta sto sam znao i procitao ali nazalost bez rezultata

• 0Niko još nije pohvalio poruku.
  Registruj se da bi pohvalio/la poruku!

Što ti lepo ne preneseš ovde ModemData.txt kao što sam ti i predložio. Samo tako ćemo moći 100% da kažemo ima li ili nema drajvera!

• 0Niko još nije pohvalio poruku.
  Registruj se da bi pohvalio/la poruku!

Malo sam bio odsutan pa kasnim sa objavljivanjem fajla.

U medjuvremenu sam promenio modem i evo texta iz modemData:




DO use the following line as the email Subject Line, to alert cogent experts:
scanModem,
Welcome to kernel 2.4.29
Occassionally reponses are blocked by an Internet Provider mail filters.
So do in a day also check the Archived responses at [Link mogu videti samo ulogovani korisnici]
Code updated on: 2005_Oct_10
------------ -------------- System information ------------------------

Welcome to
on System with processor: i686
currently under kernel: 2.4.29
[Link mogu videti samo ulogovani korisnici] will help with Slackware problems
The kernel was assembled with compiler: 3.3.4
with current System compiler GCC=3.3.4
/usr/bin/gcc -> gcc-3.3.4

Checking for kernel-headers needed for compiling.
The kernel-headers have base folder:
/lib/modules/2.4.29/build -> /usr/src/linux-2.4.29
/usr/src/linux -> linux-2.4.29
/usr/src/linux-2.4.29
Wvdial is a dialout utility very useful for modem testing. If not encluded on
your installation media, check your distrbutions on line software repository.
An example is: [Link mogu videti samo ulogovani korisnici]

Modem symbolic link is: /dev/modem -> ttyS5

USB modem not detected.

00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 50)

Modem candidates are at PCI_buses: 00:0a.0

Providing detail for device at 00:0a.0
with vendor-ID:device-ID
----:----
Class 0780: 8086:1040 Communication controller: Intel Corp. 536EP Data Fax Modem
SubSystem 8086:1000 Intel Corp.: Unknown device 1000
Flags: bus master, medium devsel, latency 32, IRQ 10
Checking for IRQ 10 sharing with modem.
XT-PIC VIA8233, usb-uhci, usb-uhci


-----PCI_IDs------- --CompilerVer-
Feature List: Primary Subsystem Distr KernelVer kernel default CPU
./scanModem test 8086:1040 8086:1000 slackware 2.4.29 3.3.4 3.3.4 i686

Use driver resource Intel-536ep-MostRecentVersion.tgz
== Checking PCI IDs through modem chip suppliers ==

Vendor=8086 is Intel, Inc. producing HaM and 536ep host controller free (HCF) modems, 537 soft modem
and AC97 and MC97 controllers managing a varierty of non-Intel soft modem Subsystems.
These subSystems often have PCI_IDs assigned by the modem assembler, rather than the chip provider.
Download Intel-537ep drivers through: [Link mogu videti samo ulogovani korisnici]
Also check at: [Link mogu videti samo ulogovani korisnici]
for beta releases and perhaps Already compiled drivers for some Linux distributions
A very detailed installation report cogent to 537 type modems is at:
[Link mogu videti samo ulogovani korisnici]

Setup call id with:
Type 1 : When the phone line is not in use at+vcid=1
Type 2 : When the phone line is already in use on a call at+pcw=0
---------------------
:
The older 2.4.n driver pair have a dependency on one other.
with result that these messages may be seen upon driver loading:
depmod****Unable to resolve symbol in 536ep.o
depmod****Unable to resolve symbol in 536epcore.o
but function is NOT affected.
Bur when the message is any longer, the drivers probably have not been properly compiled.
In which case carefully read Modem/DriverCompiling.txt

A problem maintaining CONNECT under the version 4.62 drivers was resolved
by dropping back to the 4.60 version. See:
[Link mogu videti samo ulogovani korisnici]

The Intel-537ep-MostRecentVersion.tgz driver package may alternatively provide support.

For Debian like distros, a modified install script is:
[Link mogu videti samo ulogovani korisnici]


The September 2005 Intel-537 release is version 2.70.95.0, with a compile illustrated in
[Link mogu videti samo ulogovani korisnici] However an update supporting FC4
kernels is needed as there are failures under (at least) kenels 2.6.11-1.1369_FC4 , 2.6.12-1.1447_FC4smp
Intel has not yet decided whether to support FC4 kernels.
and there is a segmentation fault error with Slackware kernel 2.6.11.11
Pending an update from Intel, dropping back to a kernel_version less than 2.6.10
should allow recovery of function.


======= PCI_ID checking completed ======
Update=2005_Oct_10
A PCMCIA CardBus is not detected on this System.
GCCversion=3.3.4

For information on modem port creation under the UDEV device file system see:
[Link mogu videti samo ulogovani korisnici] for Conexnant modems
[Link mogu videti samo ulogovani korisnici] for Lucent/Agere DSP modems

The following information blocks just query some ppp support items.

====================================================
grep -rs ppp /etc/modules.conf
-------------------------------------

-------------------------------------

The following ppp related modules are likely unpacked during loading.
If not they should be unpacked by root with:
# gunzip PathTo/ModuleName.o.gz
----------------------------------------
/lib/modules/2.4.29/kernel/drivers/net/bsd_comp.o.gz
/lib/modules/2.4.29/kernel/drivers/net/ppp_async.o.gz
/lib/modules/2.4.29/kernel/drivers/net/ppp_generic.o.gz
/lib/modules/2.4.29/kernel/drivers/net/slhc.o.gz
/lib/modules/2.4.29/kernel/drivers/net/ppp_deflate.o.gz
/lib/modules/2.4.29/kernel/lib/zlib_deflate/zlib_deflate.o.gz

On most Systems, unpacking will driven by installing the wvdial.rpm
and/or the package providing the KPPP graphical dialing interface.

COMM services are not active
Be sure to read the section about ppp related modules and aliases in Modem/YourModem.txt
DEVPPP=crw-rw---- 1 root uucp 108, 0 2001-03-25 23:04 /dev/ppp

The current modem symbolic link is: /dev/modem -> ttyS5
The ports /dev/ttyS0 or 1,2,3 are for standard Controller chip modems


No devfsd.conf file found, indicated absense of the devfsd daemon package
for device file system (devfs) symbolic link support.

DEVFSD=
---- dmesg queries -------
slackware is not yet providing pre-compiled drivers for WinModems

• 0Niko još nije pohvalio poruku.
  Registruj se da bi pohvalio/la poruku!

Jel si podesio u kppp-u ATX3?
configure -> Modems -> Edit.. -> Modem -> Modem Commands... -> Initialization String 1: ATX3

• 0Niko još nije pohvalio poruku.
  Registruj se da bi pohvalio/la poruku!

Ti si instalirao lt* drajver, koji je za Lucent modem, a ustvari imaš Intel536EP modem, za koji ti trebaju Intelovi drajveri.

Skini drajvere sa Intelovog sajta: [Link mogu videti samo ulogovani korisnici] Vodi računa da skineš drajver za tvoj kernel 2.4.29! Možda čak ima i prekompajliranih drajvera za Slackware!

Dopuna: 01 Nov 2005 13:06

PS. Pre instalacije novih drajvera deinstaliraj stare! Pročitaj fajl INSTALL ili README iz lt* paketa u kome verovatno piše kako se drajver deinstalira. U 90% slučajeva trebaš da u direktorijumu gde si raspakovao drajvere izvršiš komandu, kao root:

make uninstall

• 0Niko još nije pohvalio poruku.
  Registruj se da bi pohvalio/la poruku!

Gore navedeni drajver sam instalirao sa predhodnim modemom koji je bio (a i jos je ) Lucent.Sada imam neki Intelov modem sa 536EP chipom i skidam drajver sa doticnog sajta na kojem nema drajvera bas za Slackware ali skidam neki za koji mislim da bi trebao da bude odgovarajuci.

Ako bude bilo problema....

• 0Niko još nije pohvalio poruku.
  Registruj se da bi pohvalio/la poruku!

Samo obavezno paste problema. I informacije u podesavanju modema moras reci da bi resili problem.

• 0Niko još nije pohvalio poruku.
  Registruj se da bi pohvalio/la poruku!

PROBLEM:

make clean i make 536 prodje ok,medjutim kod make install prijavi gresku.
Citajuci readme i koliko sam ja shvatio tada treba startovati 536_boot i 536_install sto sam i uradio.
Kod kkkp-a na Query modem kaze da je modem busy.

onda sam (citajuci gnuzilu iz februaru) radio nesto tipa

insmod -f Intel536.o
rm /dev/536ep (koliko sam primetio tu ne radi nista jer taj dir ne postoji)
mknod /dev/536ep c 240 1
ln -s /dev/536ep /dev/modem

I posle svega opet je modem busy.

Sta sada da radim???

Jos da dodam da sam skinu intel-536ep-4.69.tgz (nisam skidao drajvere za pojedinacne distribucije jer nema za Slackware).

• 0Niko još nije pohvalio poruku.
  Registruj se da bi pohvalio/la poruku!

A da prekompajliras kernel pa da ponovo pokusas?