Navigacija
Lista poslednjih: 16, 32, 64, 128 poruka.

SuSe 9.3 + Intel 536ep

[es] :: Linux mreže :: SuSe 9.3 + Intel 536ep

Strane: 1 2 3

[ Pregleda: 13714 | Odgovora: 50 ] > FB > Twit

Postavi temu Odgovori

Autor

Pretraga teme: Traži
Markiranje Štampanje RSS

redfusion

Član broj: 12651
Poruke: 113
*.neobee.net.

ICQ: 346105695


Profil

icon SuSe 9.3 + Intel 536ep21.04.2005. u 23:41 - pre 204 meseci
Os:Suse 9.3 Professional
Kde 3.4
Modem:Intel 536ep

Problem:
Nakon uspesne instalacije modema i pozivanja linkovanja /dev/536ep sa /dev/mod, Kinternet iz svog loga daje sledece:

Citat:
SuSE Meta pppd (smpppd-ifcfg), Version 1.58 on linux.
Status is: disconnected
trying to connect to smpppd
connect to smpppd
Status is: disconnected
Status is: connecting
pppd[0]: Plugin passwordfd.so loaded.
pppd[0]: --> WvDial: Internet dialer version 1.54.0
pppd[0]: --> Initializing modem.
pppd[0]: --> Sending: ATM1
pppd[0]: --> Sending: ATQ0
pppd[0]: --> Re-Sending: ATM1
pppd[0]: --> Modem not responding.
pppd[0]: Connect script failed
Status is: disconnected
pppd[0] died: Connect script failed (exit code 8)


Kako da resim ovaj problem. Cini mi se da sam nikada blizi da proradi, cak i komandom "lsmod" dobijam kao prvi na listi "Intel536ep"
Kada iz Kppp taba za modem odem na Kvajeri, podesivsi modem u njemu na /dev/mod/ Kppp kaze da je naso modem, Modem Ready, uradi onae AT testove i na kraju kada izbaci prozor da je zavrsio u poljima pored At ne stoji nista, prazna su.


Molim za pomoc, jer mi je jako hitno da imam modem koji radi. Hvala.
Ne znam da sve znam da ništa ne znam!
 
Odgovor na temu

Danilo Cvjeticanin
Danilo Cvjeticanin
Apatin-Beograd

Član broj: 9614
Poruke: 3517
*.apatinonline.net.



+37 Profil

icon Re: SuSe 9.3 + Intel 536ep22.04.2005. u 08:18 - pre 204 meseci
Kojim nacinom si resio drajver?
Koju si verziju drajvera skinuo? I koji Kernel imas?
 
Odgovor na temu

mmirilovic
Mladen Mirilović
Čačak

Član broj: 10462
Poruke: 721
*.co.yu
Via: [es] mailing liste



+1 Profil

icon Re: SuSe 9.3 + Intel 536ep22.04.2005. u 10:01 - pre 204 meseci
Skini sledeću skriptu http://linmodems.technion.ac.il/packages/scanModem.gz
pokreni je i pošalji nam rezultat. A možeš i da malo pogledaš upustva o
instalaciji modema na istom sajtu.
Pozdrav.
 
Odgovor na temu

redfusion

Član broj: 12651
Poruke: 113
*.neobee.net.

ICQ: 346105695


Profil

icon Re: SuSe 9.3 + Intel 536ep22.04.2005. u 10:07 - pre 204 meseci
Posle dosta isprobavanja, shvatio sam da je onaj driver koji dolazi sa distribucujom odlican(na netu najnoviji je 4.69.1, a i ovaj na CD1 je isto). Ne treba se muciti sa make i kompajlirati da bi se dobio isti drajver. Samo ga instaliraj iz svog usera, nemoj ici u root(user) ali kada ti yast trazi sifru upisi.

Znaci instalirao sam ga sa Yastom, i pozvao is shella-root
ln sa odgovarajucim opcijama za linkovanje.

I dalje dobijam gresku kao iznad u citiranom pravougaoniku, mislim da znam zasto. Nisam pravilno koristio LN komandu u shellu.

Dakle, pitanje je:
1)Kako da otkrijem source destinaciju modema(da li je recimo "/dev/536ep0" ili "/dev/536ep". Dali je to ono sto pise u yastu kad odem na configure modem?

2)Kada pokusam da LN-om linkujem ovako "ln -sv /dev/536ep /dev/modem
On napise da linkuje, ovo sa ovim i posle u produzetku red"File Exist"
KAKO DA OBRISEM TAJ FILE< PA DA ONDA OCE DA NAPRAVI SYMBOLIC LINK?

3)Hvala svim Linuxasima, posto sam novi korisnik i vidim kako je ovo komplikovano, imam veliki respect za sve koji su stekli znanje o Linu i koriste ga everyday. Svaka vam cast. Jel zna neko odgovor na ova dva pitanja iznad? Mislim da ako mi na to odgovorite moj modem ce konacno uspeti da dialuje.
Ne znam da sve znam da ništa ne znam!
 
Odgovor na temu

redfusion

Član broj: 12651
Poruke: 113
*.neobee.net.

ICQ: 346105695


Profil

icon Re: SuSe 9.3 + Intel 536ep22.04.2005. u 10:38 - pre 204 meseci
Pri samom startovanju:

Citat:


UPDATE=2005_April_19

ONLY use scanModem downloaded as: http://linmodems.technion.ac.il/packages/scanM

odem.gz



./scanModem should ONLY be run within a Linux/UNIX partition.

If within a MicroSoft/DOS partition, abort with Ctrl-C now !!!

Copy scanModem.gz to your Linux partition and restart.



PCIBUS=0000:02:09.0



Providing detail for device at PCI_bus 0000:02:09.0

with vendor-ID:device-ID

----:----

Class 0780: 8086:1040 Communication controller: Intel Corporation 536EP Data F ax Modem

SubSystem 8086:1000 Intel Corporation: Unknown device 1000

Flags: bus master, medium devsel, latency 64, IRQ 11

Memory at fe400000 (32-bit, non-prefetchable) [size=4M]

Capabilities: [e0] Power Management version 2



-----PCI_IDs------- --CompilerVer-

Feature List: Primary Subsystem Distr KernelVer kernel default CPU

./scanModem test 8086:1040 8086:1000 SuSE 2.6.11.4-20a-default 3.3.5 3.3.5 i 686





A subfolder Modem/ has been written, containing these files with more detai led Information:

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

1stRead.txt ATI.txt DriverCompiling.txt General.txt ModemData.txt Rational.txt Slmodem.txt SoftModem.txt Testing.txt UNSUBSCRIBE.txt

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

Please read 1stRead.txt first for Guidance.





1srRead.txt:

Citat:




The files in this Modem/ folder have the following roles:



ModemData.txt - Diagnostics and accumulated information cogent to your modem.

If further help is needed, send a description of your problem to:

[email protected]

with ModemData.txt attached as a PLAIN TEXT file.

Always send the ENTIRE ModemData.txt, as It includes subtle diagnostic ouputs needed to best guide you.

If your PC is a laptop, please provide Make and Model information.



ModemData.txt with companion files on specific modems/situations may suffice to solve your problems.

It recommends sites for needed software, or additional tests You must perform.

Always use the most recent update of scanModem accessed ONLY at

http://linmodems.technion.ac.il/packages/scanModem.gz

to produce ModemData.txt

URLs to cogent advice are regularly updated, so your problem may be solved therein.



Rational.txt - Motivations of this scanModem package.



DriverCompiling.txt - Explains the roles of additional files which may have to be installed

to support compiling of modem drivers, and the steps to take.



SoftModem.txt - Information and instructions about "soft modems".

For these modems, additional steps may be necessary for choice of supporting software.

The primary PCI ID is that of the "modem controller", which can support diverse Subsystems.

It is the "modem codec" of the Subsystem which determines the software needed.



Slmodem.txt - The slmodem software from SmartLink supports a variety of soft modems.

However new Users need to be aware of its special port setup features.



ATI.txt - This file with be generated it there is a ATI modem controller,

for which support is still emerging.

.

ModemTesting.txt SHOULD be read, but after drivers have been installed.



General.txt has general information about the status of winmodem support under Linux,

Do read it ModemData.txt reports that your current modem is not supported under Linux.



Any additional files are specific to your modem and should be read.



If you are Linux newcomer, please do locate your local Linux group through:

http://www.linux.org/groups/index.html . If you are not comfortable with English,

a local Linux user can often be of substantial assistance in your own language.





Ati.txt:

Citat:




The 1002:434d ATI is a soft modem controller with a variety of Subsystems.

For those with a Conexant Subsystem there is a supporting hsfmodem package from

http://www.linuxant.com

For many other Subsystems, the instructions below on using SmartLink slmodem software

in ALSA mode is cogent. Slmodem.txt and Testing.txt complements the information of this ATI.txt



There is a modem driver, snd-atiixp-modem.ko in the 2.6.n kernel releases.

It provides a low level, hardware interface service.

The complementary port creation is manged through the SmartLink slmodem software,

whose slmodemd creates ports and provides higher level COMM functions.

The slmodemd need NOT be recompiled with each kernel upgrade.

For history see: http://website.lineone.net/~bryanrpoole/atiixp-modem.htm



This support is still emerging and requires that the snd-atiixp_modem.ko be derived from

an ALSA release of at least 1.0.6a or later version. Check with

# alsactl --version

alsactl version 1.0.6

on my Debian 2.6.10 System. So more current code is necessary.

Download is from download from http://www.alsa-project.org.

Both alsa-lib and alsa-driver packages are necessary. Make a folder:

# mkdir newALSA

Unpack both packages in the newALSA/

Follow the compilation and installation instructions therein, which will

install an updated snd-atiixp-modem.ko and complementary software.



For a source of slmodemd, use the slmodem-2.9.9b.tar.gz downloaded from

http://linmodems.technion.ac.il/packages/smartlink/

It has been patches to function with 2.6.10 kernels. Before using it, there MUST be installed,

a package libasound2-dev, which will be provided by your Linux distrbution

It provides header files for the slmodemd compilation. For for Mandrake/Mandriva, the package name is libalsa2-devel



Then within the slmodem/ folder do:

# make clean

# make

# make install

This installs the slmodemd. Do NOT try to use the slamr.ko driver co-installed.

It is NOT compatible with the ATI modem.



To being testing login as

Watch your kernel messages with:

# tail -f /var/log/messages &

The "&" just "backgrounds the process, or else the command prompt is lost.

The low level interface driver is loaded with:

# modprobe snd-atiixp-modem

Then

# slmodemd -a --c USA modem:0 &

will creat a /dev/pts/N and a symbolic link

/dev/ttySL0 --> /dev/pts/N

and provide higher level functions of the slmodem code

The first functionality test is:

# vwdialconf wvdialtest.txt

if the modem is thus found prospects are good for success.



For Redhat and Fedora, use the Internet Wizard within the popup menus to

configure a dialout, A file /etc/wvdial.conf will be created.




For other Linux distros do:

# wvdialconf /etc/wvdial.conf

Edit three lines of your personal information into /etc/wvdial.conf



In both cases add to /etc/wvdial.conf a line needed by slmodemd

Carrier Check = no

Using other dialer utilties (such as KPPP) is OK and they will not beed the:

Carrier Check = no



Then try a dialout.







Driver Compilling.txt:

Citat:




================================================================

COMPILING DRIVERS, for Linux Newbies



This text provides a very minimal introduction to compiling drivers,

particularly WinModem drivers under Linux. All points are covered in

much more detail in the Linux Kernel-HOWTO which is likely included

in the documentation set, installed within /usr/share/doc/ folders.



A necessary step is acquiring "kernel-headers" which are essential to compiling processes. Their installation or preparation varies with the Linux distribution and also KernelVersion, with KernelVersion displayed by:

uname -r

The kernel-headers are acquired in a few different ways.

A) Debian and derivative distributions - just install the kernel-headers-KernelVersion.deb, Knoppix includes them on the bootable CD.

B) SuSE with KernelVersion 2.4.21-144-* or later - install the matching kernel-source package, which does also contain the kernel-headers

C) for Fedora with KernelVersion of 2.6.6 or later, kernel-headers are coinstalled with the kernel package

D) for all other cases, the kernel-headers must be prepared from kernel-source.

The preparation can be summarised in a few steps/actions:

Install a kernel-source package representing your kernel.

Change directory (cd) into its base folder. The kernel-source in general

will match only one of several kernels that could have been installed

and NOT necessarily yours. Thus clean out any remnants of earlier usages with:

make mrproper

Copy in your kernel configuration file and have it read with:

make oldconfig

If necessary edit ONLY the fourth line of the Makefile, which completes

the specification of where drivers will be installed to (details below).

The kernel-headers are then assembelled by either:

a) for 2.4.nn kernels by

make dep

b) for 2.6.n kernels,

make bzImage

which includes an integral "make dep" step.



Whether provided by a Linux distro or assembelled from kernel-source, the sought kernel-headers are a LARGE set of FileNames.h typically located at:

/usr/src/kernel-source(or header)-KernelVersion/include/linux/FileNames.h

For some Linux Distros, the name of the Base Folder is instead:

/usr/src/linux-KernelVersion/

For more recent Redhat/Fedora releases, the location is:

/lib/modules/KernelVersion/build/

These FileNames.h are generally read during kernel and driver compiling processes.

They are text files which co-direct which code pieces are to be incorporated.



COMPILING is the process of converting human readable source code

into compact binary code that the Operating System (OS) uses most quickly.

For winmodems, code components from the modem chipset provider

are combined with KERNEL-HEADER information, thus generating one or more binary modem drivers.

They are commonly compiled as ModuleNames.o for 2.4.n kernels and ModuleNames.ko

for 2.6.n kernels. They are installed into sub-folders of:

/lib/modules/kernel-version/

Therefrom they can be dynamically inserted into the boot kernel of the

Operating System (OS) when needed, sometimes with auxiliary instructions from

/etc/modules.conf for 2.4.n kernels, and

/etc/modprobe.conf for 2.6.n kernels

Modules can be removed from the kernel when there service is over,

thus economizing on System resources.



With kernel_headers first acguired, the modem driver compilation and installation

proceeds within its own resource package, with the included README providing these details.

Quite commonly there are only three commands like:

make clean

make DriverName

make install

which will compile the drivers and install them properly.

The remainder of this text just expands on these issues and steps,

with more "theoretical issues at the end.



Modem related resources may or may not have been installed during the primary Linux installation,

as WinModem hardware is often NOT recognized. Search your Distro's package

descriptions for "modem" to reveal the status of related resources. Read

the package description to determine whether pre-compiled modem drivers were provided.

RESOURCES of a few types are needed to get on line. Do PREFERABLE use your System's

package maintenance system for the installation. This should guarantee that

any DEPENDENT packages will be called into the installation process. As a preliminary

1) Install your distributions package providing the KPPP, WVDIAL and MINICOM dialer utilities.

Dependencies within such packages will also drive the unpacking of ppp related modules

from compressed to a functional form :

module.o.gz --> modules.o

or for 2.6.n kernels

module.ko.gz --> module.ko

In addition these dialers will later aid testing and configuration,

which is to be performed only AFTER, the modem's drivers are installed.



2) Download if necessary and modem driver package specific to your modem hardware.

3a) Install your distrbution's kernel-source package, necessary for preparing kernel-headers.

Or for Debian style distributions,

3b) install the kernel-header-2.6.11.4-20a-default.deb package matching your kernel version 2.6.11.4-20a-default.



The KERNEL-HEADERs have FileNames.h can can be read with a text browser.

There is always a SMALL set or FileNames.h installed to

/usr/include/

that are needed to support diverse functions.

However the /usr/include/FileNames.h collection are TOO FEW to support compiling,



A KERNEL-SOURCE package must more generally be installed, if a full kernel-header set

is not otherwise provided. Kernel-source packages are now some 30-40 MB now even in compressed form.

The package provided by your Linux Distro SHOULD preferentially be used.

It will usually have some differences from that initially released at http://www.kernel.org .

Typically the installation process will set two symbolic links:

/lib/modules/2.6.11.4-20a-default/build --> PATH_to/kernel-source-version/

/usr/src/linux --> PATH_to/kernel-source-version/

These latyer enable access to the kernel-headers needed during the modem driver compiling. Check with:

ls -l /lib/modules/2.6.11.4-20a-default/build

ls -l /usr/src/linux

The former link is more usefull for Systems with alternative boot kernels,

and is mandatory for some modem compiler packages.



HIGHLY IMPORTANT: the kernel-source as installed in generally does NOT

represent your current kernel version, EVEN if the kernel-version is the same.

Only one of several possible kernels was installed on your System,

and the unpacked kernel-source need NOT represent it exactly!!!

For example, in the RedHat Distro there is a set of kernel-configuration files within

/usr/src/linux/configs/

Each is specialized for a different CPU (i586, i686, K6, etc),

Yet each will be represented by the VERY SAME version name: "uname -r" .

!!!! Thus a PROPER CONFIGURATION MUST BE DONE by You, before compiling drivers !!!!



Examples provided below are partially customized from your System settings.

CONFIGURATION is started by moving into the kernel-source folder with one of:

cd /lib/modules/2.6.11.4-20a-default/build

cd /usr/src/linux



There is a Makefile on your System at: /lib/modules/2.6.11.4-20a-default/build/Makefile

with first few lines:



VERSION = 2

PATCHLEVEL = 6



KERNELSRC := ../../../linux-2.6.11.4-20a



For your current kernel, the fourth line should be

EXTRAVERSION = -.4

where -.4 has been read from your current kernel version: 2.6.11.4-20a-default.

But it this does not match what is Actually in the Makefile,

then it represents a Different kernel-header set then that of your kernel!!!



For Mandrake Linux their will generally be an included "mdk", such as:

EXTRAVERSION = -3.1mdk

SuSE 9.0 had:

EXTRAVERSION = -99-default

The first four makefile lines specify that:

a) the compiled kernel modules/drivers will have encoded version labels such as:

2.4.21-3.1mkd OR 2.4.21-99-default

b) such modules including modem drivers are installed into sub-folders of

/lib/modules/2.4.21-3.1mkd/

/lib/modules/2.4.21-99-default/

The major points are that compiled drivers must be both

kernel-release (the 2.4.21) AND EXTRAVERSION matched with the installed kernel.

Otherwise they may be installed uselessly and not be detected by the kernel

OR there will be a failure upon attempted insertion, with message including:

a list of "unresolved symbols ".



Kernel-headers may be resident from a prior usage of the kernel-source/.

Check with:

ls include/linux/

which may display abundant FileNames.h

The version of these headers will be in the UTS line displayed by

cat include/linux/version.h

#define UTS_RELEASE "2.4.21-3.1mdk" (as an example)



Next, list completely the contents of the kernel-source with:

ls -a

Where the " -a " additionally reveals ".dot-prefixed-confguration-files" such as

.config .hdepend .depends

which may be left over from the prior usage of the kernel-source. Below is an example:

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

.config .hdepend .depends

COPYING Makefile Rules.make init mm

CREDITS README arch drivers ipc net

Documentation conf.vars fs kernel scripts

MAINTAINERS REPORTING-BUGS crypto include lib



Configuration of the kernel-source is where almost all the Mistakes occur!!!

Here is a way to do it correctly (but read through EXCEPTIONAL CASES below).

1)Within kernel-source/ folder, browse the README file for general guidance.

It will relate that the command:

# make mrproper

cleans up leftovers from any previous usage .dot-files and the include/linux/ folder.

Additionally you may need to do an edit within Makefile, but ONLY that 4th line.

2) If necessary to edit, FIRST make a backup:

cp Makefile Makefile.backup

then edit ONLY the 4th line of Makefile to match the EXTRAVERSION of 2.6.11.4-20a-default

EXTRAVERSION = -

NEVER change anything else within the Makefile.



3) Set the dependencies of the current kernel.

For SuSE 9.0 and later, there is a command which does the following steps

# make cloneconfig && make dep

Also browse the excellent README.SuSE in the kernel-source/ folder

For other Distros, the following steps are necessary, within the kernel-source/ folder

copy the kernel-config file to .config

and DO SPECIFY that " . "

But where is it? For many Distros, it will be the file like

/boot/config-2.6.11.4-20a-default

matching the output of:

uname -r

Or it may be the target of a symbolic link: /boot/config -->

So

cp /boot/config-2.6.11.4-20a-default .config

For SuSE 8.0 and earlier versions it is:

cp /boot/vmlinuz.config .config

PLEASE do not omit that "." in .config as it is crucially necessary.

View .config with a text browser.

It is simply a listing of the code components used in the kernel and its modules:

#

# Automatically generated make config: don't edit

#

CONFIG_X86=y

# CONFIG_SBUS is not set

CONFIG_UID16=y

etc.



4) The .config file will be read during

# make oldconfig

which feeds its specifications through a process specifying

the SAME inter-dependencies previously used in compiling your kernel,

and may generate additional .dot-config files . They can be displayed with:

# ls -al



5) Though it may be redundant after "make mrproper", it will do no harm to:

make clean

5a) For the SuSe Linux versions 8.0 and previous , there will exist files:

/boot/vmlinuz.autoconf.h

/boot/vmlinuz.version.h

They MUST be copied as:

cp /boot/vmlinuz.autoconf.h /usr/src/linux/include/linux/autoconf.h

cp /boot/vmlinuz.version.h /usr/src/linux/include/linux/version.h



6) Now build kernel-headers with:

make dep

for 2.4.n kernels or for 2.6.n kernels

make bzImage

during which you can walk your dog, take a shower, have tea, etc.

7) Check for resultant FileNames.h with:

ls include/linux/

and

cat include/linux/version.h

to verify the version.



COMPILING the MODEM DRIVERS can now finally be done.

Unpack the compiler kit for your modem drivers,

cd into its folder, read any README or INSTALL files,

make clean

FINALLY, your modem drivers will compiled by a command like

make OR make ModuleName

or perhaps

make all

During this process, some of the kernel-header code with be joined

with the supplied modem specific code, and ModemDrivers.o will be produced.

Follow and further instructions in the modem code resource

to install the drivers, often with:

make install



THEORETICAL ISSUES



WinModem driver packages commonly include:

1) a readible Open Source component, which can be readily debugged by

experts in code. This component provides "wrappers" to common

kernel functions for an already complied, or BINARY format, component of the modem code.



2) A Closed Source component compiled into the binary form, in which

proprietary information is encrypted. This will include the copyrighted Vn.nn compression algorithms.

In 2004, pre-compiled modem drivers are beginning to be included

for a few winmodems by some Linux distributions.

But the binary format precludes incorporation of the modem drivers in some Linux distributions

for legal reasons, practical reasons, and/or reasons of principle.



Since almost all the newer PCs are now equipped with WinModems,

many users will have to compile their own linux modem drivers.

Exceptions are the more expensive modems with Controller chipsets,

characteristic of the earliest modems.

They are supported by Open Source serial code included in Linux

distributions (Distros hereafter).



Winmodems are less expensive because of greatly reduced hardware costs.

They lack Controller chips of the earliest modems, and may additionally lack Digital Signal Processor (DSP) chips of second generation modems.

Functions of Controller based chipsets are replaced by a combination of

software code and/or other System hardware.



Modems without a controller chip are referred to as "controllerless modems" and

modems lacking both a DSP and controller chips are referred to as "soft modems".

With faster central processor units (CPU), some processing tasks are performed

by the CPU for the controllerless modems. The CPU does nearly all

the signal processing for the "soft modems" lacking a DSP.



AC97 or MC97 soft modems conform to an ac97_codec, and can host a variety of Subsystems It is the CODEC of the Subsystem which determines which software should be utilized!!

and any modem controllers can host one of a variety of soft modem Subsystems.

There are additionally soft PCI modems without such controllers, which still utilize

the common ac97_modem.o driver. In general it will be YOUR task to identify

the Subsystem codec and compile the needed driver.



## end Modem/DriverCompiling.txt







General.txt

Citat:






If the Primary and Subsystem Vendor information was not adeqaute,

it may be useful to search at http://www.pcidatabase.com/





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

The System has Ethernet capability. If not expert,

shut down ethernet before initiated modem usage with:

# ifconfig eth0 down



0000:00:05.0 Bridge: nVidia Corporation CK8S Ethernet Controller (rev a2)

Subsystem: ASUSTeK Computer Inc.: Unknown device 80a7

Flags: bus master, 66Mhz, fast devsel, latency 0, IRQ 9

Memory at febfc000 (32-bit, non-prefetchable) [size=4K]

I/O ports at ec00 [size=8]

Capabilities: [44] Power Management version 2







Attempted or effective networking links are displayed by command:

# /sbin/ifconfig

A block with "lo" is an internal loopback test and harmless.

However, ethernet "eth0" can be problematic for PPP connections,

because of competition for DNS (domain name service).

The default is to use the DNS specified for etherenet and

without expert configuration, this will block browser naviagation through PPP.

========== ifconfig test =============

eth0 Link encap:Ethernet HWaddr 00:11:D8:06:B1:E8

inet6 addr: fe80::211:d8ff:fe06:b1e8/64 Scope:Link

lo Link encap:Local Loopback



If is wisest to disable bootup establishment of ethernet in your Control Center.

Depending on your Linux distribution,

one of the following Root commands way alternatively be effective:

# ifdown eth0

# ifconfig eth0 down

# /etc/init.d/network stop

# /etc/init.d/networking stop





Do NOT send this Modem/General.txt with common information to [email protected]

There are instructions to UNSUBSCRIBE from [email protected] at http://www.linmodems.org

==============

RATIONAL

This ./scanModem service is sadly necessary because of the pre-compiled format

(binary, Closed Source) of some modem supporting code. Intellectual property

is protected within the binary component. But this prevents compatibility

assessments/debugging against Linux Open Source code. Skipping many details,

the consequence is that some Linux distributions do not deliver Closed Source code,

or tools adequate to fully identify the modem chipset.

This script tries to close this information gap.



Several sections are included in this file:

The Summary of modem Support under Linux

description of the soft modem identity tests: SIL ids

some output from scanModem specific to your System

an explanation of the GCC 2.95 compiler warning

ethernet Interference with DNS (domain name service)

Please Linux Newbies read carefully, the companion

Modem/DriverCompiling.txt and its

Followup Modem/DriverTesting.txt section with dialout examples.



USB modems will not be detected through the

acm.o driver with port /dev/ttyACM0

UNTIL proper USB support is installed.

See http://www.linux-usb.org/USB-guide/x332.html,

Linux_kernel_source/Documentation/usb/acm.txt, and

http://www.usb.org/developers/devclass_docs/usbcdc11.pdf (page 15)

Among the USB modems with proprietary interfaces, there is support for

USB Vendor ID: 0572 Product ID: 1290 (Cadmus2 HCF, Conexant)

USB Vendor ID: 05AC Product ID: 8202 (Cadmus2 HCF, Apple)

USB Vendor/Product ID: 0483:7554 SmartUSB56 (ST7554) based modems

The SWEEX USB modem has the ST7554 chipset

Drivers are at http://www.smlink.com/main/index1.php?ln=en&main_id=40

http://linmodems.technion.ac.il/archive-fourth/msg00176.html is an installation report.

To write out Smartlink information, use the proxy entry

./scanModem test 1131:3400



PCMCIA card modems can serve if your laptops modem is not supported under Linux.

http://freewebhosting.hostdepa...om/g/gromitkc/pcmcia_list.html

The 3COM,Inc 3CXM556 and AgereSystems FM560LK chip modems use the Open Source serial-cs.o driver.



It is the CHIPSET, and Not the modem BrandName which is informative for Linux support.

For modems not recognized by ./scanModem, chipset information may be obtained under Microsoft Windows through:

1) Start > Settings > Control Panel > Classical View (for WinXP) > Modem , or alternatively,

Start > Settings > Control Panel > Classical View (for WinXP) > System > Devices > Modem

Do the modem diagnostics test, if available, looking for manufacturer chipset,

It is within information output in lines: ATI - specifications

Try to identify the modem setup file, with name perhaps MODEM.INF

2) Open a COMM console, and send ATI commands to the modem (ATI, ATI1, ATI2, etc)

which may elicit chipset and driver information. Here is an example

ATI3 - Agere SoftModem Version 2.1.22

ATI5 - 2.1.22, AMR Intel MB, AC97 ID:SIL REV:0x27

successfully identifying an Agere SoftModem chipset, both by name and through

the:softmodem SIL ID: AC97 ID:SIL REV:0x27



SUPPORT SUMMARY - as of 2005_April_19

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

Controller chipsets are used in the most expensive modems and are supported.

They utilize the same driver, serial.o , and most commonly the ports /dev/ttyS0 thru 3.

Such chipsets are produced by 3Com, AgereSystems (the Venus chipset),

Topic Semiconductor Corp., and others. But the same companies may

produce unsupported WinModems. Do not depend on the Brand Name.

Look for an explicit statement of Linux support



AVOID the following modem chipsets:

ESS - no formal support since 2.2.2 kernels, though there are kluges:

http://andywettstein.home.comcast.net/ess/

http://tx.technion.ac.il/~raindel/

3Com/US Robotics winmodems - never supported under Linux



SmartLink - newer chipsets are supported: http://www.smlink.com

ftp://ftp.smlink.com/linux/unsupported/

Moreover, the slmodem-2.9.10 drivers will support Many but not all modem Ssubsystems

that serve under AC97/MC97 controllers.



Conexant - all modems supported with drivers at: http://www.linuxant.com

Testcode for slow 14,400 mH support is free, BUT

there is a one time charge for the full speed support.



Intel Inc. - http://developer.intel.com/design/modems/support/drivers.htm

For early releases check at: http://linmodems.technion.ac.il/resources.html

The HaM modem is supported, but code is no longer being updated;

there will likely be failures under emerging 2.6 kernels.

The 536ep and five Intel537 modem chipset variants are actively supported.



Lucent /AgereSystems

The Venus chipset modem uses the serial.o driver and is thus supported.

Modems with digital signal processing (DSP) chipsets are supported: http:/ltmodem.heby.de

For AC97/MC97 soft modems. Initiate software access through code sponsor IBM:

http://www-3.ibm.com/pc/suppor...document.do?lndocid=MIGR-52698

Coding of support for has Not yet begun PCI soft modems with PCI_IDs 11c1:048?

and probably will first be available within 2004.



Motorola support is at: http://www.motorola.com/softmodem/sm56_download.htm

through 2.4.22 kernels.



PCTel modem business has been sold to Conexant

Driver compiler resources are at: http://pctelcompdb.sourceforge.net/

However, the pre-compiled binary component is yet to be assembled

with the gcc 3.nn used in newer Linux releases,

so forced (-f) insertions may be necessary:

insmod -f pctel

Some of the HSP soft modems are supported by the SmartLink slmodem-2.9.10 drivers.



Broadcom modems in Dell laptops and PCs - can be made to function under 2.4 kernels, but code has not been updated recently.



--------- end chipset section ----------------------



SUPPORT under the emerging 2.6.nn kernels.



The more expensive Controller chipset modems are functioning.

SmartLink slmodem-2.9.9 drivers are functioning.

Conexant has 2.6.n support

The Lucent/Agere digital signal processing (DSP) chipsets do have

informal service into 2.6.n kernels and an AgereSystems release is soon expected.

Intel, Agere Systems and Linuxant are firmly expected to continue support into 2.6.nn,

though the Intel HaM software will not be updated to 2.6.n service



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

Preparing winmodem drivers will generally require compiling.

If you are not familar with this process DEFINITELY read carefully

the Modem/DriverCompiling.txt





ModemData.txt:



Citat:






DO use the following line as the email Subject Line, to alert cogent experts:

scanModem,

Welcome to kernel 2.6.11.4-20a-default

Occassionally reponses are blocked by an Internet Providers mail filters.

So do in a day also check the Archived responses at [email protected]

Code updated on: 2005_April_19

------------ -------------- System information ------------------------



Welcome to SuSE Linux 9.3 (i586) - Kernel

on System with processor: i686

currently under kernel: 2.6.11.4-20a-default



There are emerging complications under 2.6.10 kernels. Concerning code for:

Smartlink slmodem :

slmodem-2.9.9b.tar.gz at http://linmodems.technion.ac.il/packages/smartlink/

has the current fixes. Related messages are:

http://www.datiku.com/documents/2610_migration.php

http://www.ussg.iu.edu/hypermail/linux/kernel/0409.3/0345.html

http://linmodems.technion.ac.il/archive-fourth/msg03736.html .

Lucent/Agere DSP/ltmodem:

http://linmodems.technion.ac.il/archive-fourth/msg03733.html

Concerning Intel-536ep and 537

http://linmodems.technion.ac.il/archive-fifth/msg00280.html

http://linmodems.technion.ac.il/archive-fifth/msg00881.html





The kernel-2.6.11.4-20a-default was compiled with CONFIG_REGPARM, providing more compact and faster code.



The kernel was assembled with compiler: 3.3.5

with current System compiler GCC=3.3.5



Checking for kernel-headers needed for compiling.

kernel-headers have base folder /lib/modules/2.6.11.4-20a-default/build

kernel-headers have base folder /usr/src/linux

kernel-headers have base folder /usr/src/linux-2.6.11.4-20a



Modem symbolic link is: /dev/modem -> /dev/536ep0

Checking for USB modems

None found



Modem candidates are at PCI_buses: 0000:02:09.0



Providing detail for device at PCI_bus 0000:02:09.0

with vendor-ID:device-ID

----:----

Class 0780: 8086:1040 Communication controller: Intel Corporation 536EP Data Fax Modem

SubSystem 8086:1000 Intel Corporation: Unknown device 1000

Flags: bus master, medium devsel, latency 64, IRQ 11

Memory at fe400000 (32-bit, non-prefetchable) [size=4M]

Capabilities: [e0] Power Management version 2



-----PCI_IDs------- --CompilerVer-

Feature List: Primary Subsystem Distr KernelVer kernel default CPU

./scanModem test 8086:1040 8086:1000 SuSE 2.6.11.4-20a-default 3.3.5 3.3.5 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 available drivers through: http://developer.intel.com/design/modems/support/drivers.htm with Intel-537 types at:

http://downloadfinder.intel.co...;ProductID=1230&page_nbr=2

Also check at: http://linmodems.technion.ac.il/packages/Intel/537/

for beta releases and perhaps Already compiled drivers for some Linux distributions

A very detailed installation report cogent to 537 type modems is at:

http://linmodems.technion.ac.il/archive-fifth/msg00541.html

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:

http://linmodems.technion.ac.il/archive-third/msg02127.html



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



For Debian like distros, a modified install script is:

http://members.lycos.co.uk/per...ntel536ep/Intel536_inst_debian





======= PCI_ID checking completed ======

Update=2005_April_19

A PCMCIA CardBus is not detected on this System.



For information on modem port creation under the UDEV device file system see:

http://linmodems.technion.ac.il/archive-fourth/msg03299.html for Conexnant modems

http://linmodems.technion.ac.il/archive-fifth/msg01177.html for Lucent/Agere DSP modems



The following information blocks just query some ppp support items.



====================================================

grep -rs ppp /etc/modprobe.*

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

/etc/modprobe.conf:# ppp over ethernet

/etc/modprobe.conf:# the kernel 2.2 uses pppox

/etc/modprobe.conf:# the kernel 2.4 uses pppoe

/etc/modprobe.conf:alias char-major-108 ppp_generic

/etc/modprobe.conf:alias char-major-144 pppoe

/etc/modprobe.conf:alias net-pf-24 pppoe

/etc/modprobe.conf:# the kernel 2.2 uses ppp.o as ppp driver,

/etc/modprobe.conf:# the kernel 2.4 uses ppp_generic.o

/etc/modprobe.conf:alias ppp0 ppp_generic

/etc/modprobe.conf:alias ppp1 ppp_generic

/etc/modprobe.conf:alias tty-ldisc-3 ppp_async

/etc/modprobe.conf:alias ppp-compress-18 ppp_mppe

/etc/modprobe.conf:alias ppp-compress-21 bsd_comp

/etc/modprobe.conf:alias ppp-compress-24 ppp_deflate

/etc/modprobe.conf:alias ppp-compress-26 ppp_deflate

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

Resident PPP support modules are properly uncompressed .

----active COMM services are ------------

eth0 Link encap:Ethernet HWaddr 00:11:D8:06:B1:E8

inet6 addr: fe80::211:d8ff:fe06:b1e8/64 Scope:Link

This COMM mode should be closed before using the modem, or DNS services may fail.

Be sure to read the Ethernet section of Modem/General.txt

DEVPPP=crw-rw---- 1 root root 108, 0 Mar 19 20:36 /dev/ppp



The current modem symbolic link is: /dev/modem -> /dev/536ep0

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 -------

ACPI: local apic disabled

ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 7 9 10 11 12 14 15) *0, disabled.

ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 7 9 11 12 14 15) *0, disabled.

ACPI: PCI Interrupt Link [LKMO] (IRQs 3 4 5 7 9 10 11 12 14 15) *0, disabled.

ACPI: PCI Interrupt Link [LKSM] (IRQs 3 4 5 7 9 10 11 12 14 15) *0, disabled.

ACPI: PCI Interrupt Link [LTIE] (IRQs 10) *0, disabled.

apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac)

apm: overridden by ACPI.

audit: initializing netlink socket (disabled)



SuSE 9.0 has pre-compiled drivers supporting the following modem chipsets:

Intel HaM and 536ep

Conexant HSF (but not the HCF)

Lucent/AgereSystems ltmodem (Digital Siggnal Processing type)

IBM wmave

Smart Link soft modems

Unfortunately only the Intel HaM and 536ep are on the 3 CD Personal set, pending an update.

Locations on the 6 CD Professional set are:

CD4/suse/i586/smartlink-softmodem-2.7.9-89.i586.rpm - the slmodemd daemon

CD3/suse/i586/km_smartlink-softmodem-2.7.9-89.i586.rpm - slmodem driver compiling

CD4/suse/i586/hsfmodem-5.03.27mbsibeta02122600-92.i586.rpm - softmodem configuration

CD4/suse/i586/km_hsfmodem-5.03.27mbsibeta02122600-92.i586.rpm -softmodem driver code

installation report - http://linmodems.technion.ac.il/archive-fourth/msg00350.html

CD4/suse/i586/ltmodem-8.26a-54.i586.rpm - a patch from SuSE may be needed for function

installation report - http://linmodems.technion.ac.il/archive-fourth/msg00458.html

CD4/suse/i586/Intel-536ep-4.51-200.i586.rpm

CD4/suse/i586/Intel-v92ham-4.51-244.i586.rpm

CD4/suse/i586/mwavem-1.0.4-110.i586.rpm

Some pre-compiled SuSE 9.0 packages for the 2.4.21-99-default kernel are available at:

http://linmodems.technion.ac.il/packages/SuSE-9.0/

including AgereSoftModem and the Intel537 modems



IMPORTANT - The kernel-source-144/README.SuSE informs that the pre-assembled kernel-headers installed

from the 9.0 kernel-source-99 have some flaws. Upgrading to a later kernel, such as 2.4.21-144 with matching kernel-source is the simplest may of avoiding problems.



SuSE 9.1 comes with a SmartLink slamr.ko driver installed,

aiding identification of softmodem codecs by:

dmesg | grep slamr



For the 9.1 Personal (single CD installation) winmodem packages

have be downloaded from the SuSE 9.1 repository

Should compiling drivers may be necessary, the following additional packages

will have to be downloaded and installed:

make, glibc-devel, gcc-3.3.3 and kernel-source.

The kernel-headers are co-installed with the kernel-source.

Thus subsequent driver compiling does Not require additional preparations.





Evo, to su fajlovi koje kreira scanmodemGZ koji si preoporucio.


Ne znam da sve znam da ništa ne znam!
 
Odgovor na temu

mmirilovic
Mladen Mirilović
Čačak

Član broj: 10462
Poruke: 721
*.co.yu
Via: [es] mailing liste



+1 Profil

icon Re: SuSe 9.3 + Intel 536ep22.04.2005. u 10:41 - pre 204 meseci
Prvo uradi sledeće:
la /dev/modem

Ako na ekranu dobiješ nešto ovako:
/dev/modem -> /dev/536ep
onda je modem već link ka odgovarajućem uređaju i ne moraš po tom pitanju
ništa da intervenišeš.

U suprotnom, kao root, uradi sledeće:
rm /dev/modem
ln -s /dev/536ep /dev/modem

Jesi li siguran da je 536ep a ne 536EP. Ja nemam taj modem, tako da ne znam.
Linux pravi razliku između ova dva!

Ako ovo ne proradi, ne budi lenj, pogledaj onu skriptu.
Pozdrav.
 
Odgovor na temu

mmirilovic
Mladen Mirilović
Čačak

Član broj: 10462
Poruke: 721
*.co.yu
Via: [es] mailing liste



+1 Profil

icon Re: SuSe 9.3 + Intel 536ep22.04.2005. u 11:17 - pre 204 meseci
Pratim forum preko mail-a, pa nisam video da si ti već poslao poruku u vezi
skripte. Otud i moja prethodna zakasnela poruka.

Ti kažeš da ti lsmod izlistava modul za tvoj drajver? Ali modem ti ne radi.
Znači da ili drajver nije odgovarajući, ili nisi lepo podesio modem u YaST-u.
Proveri još jednom ta podešavanja, pa ako ništa ne uradiš skini drajver sa
http://developer.intel.com/design/modems/support/drivers.htm i instaliraj ga
prema uputstvima koja se sigurno nalaze u okviru njega!

Inače modem ti se nalazi na /dev/536ep0 (nula a ne slovo o), pa pokušaj da to
upišeš u YaST-u.
Pozdrav.
 
Odgovor na temu

redfusion

Član broj: 12651
Poruke: 113
*.neobee.net.

ICQ: 346105695


Profil

icon Re: SuSe 9.3 + Intel 536ep22.04.2005. u 11:54 - pre 204 meseci
To i pise u yastu.
Inace, od komande la /dev/modem dobijem ovo(radi):

linux:/dev # la /dev/modem
lrwxrwxrwx 1 root root 11 Apr 22 09:58 /dev/modem -> /dev/536ep0



Ne znam da sve znam da ništa ne znam!
 
Odgovor na temu

redfusion

Član broj: 12651
Poruke: 113
*.neobee.net.

ICQ: 346105695


Profil

icon Re: SuSe 9.3 + Intel 536ep22.04.2005. u 14:38 - pre 204 meseci
Evo, nisam bio lenj. Probao sam i da kompajliram najnovije source drajvera,i y yastu da podesavam
I da linkujem svasta
probao sam i sa originalnim driverima iz paketa sve to, ali najdalje sto ode je ona greska od gore (exitcode8)


Sta je to zaboga?

Ne znam da sve znam da ništa ne znam!
 
Odgovor na temu

mmirilovic
Mladen Mirilović
Čačak

Član broj: 10462
Poruke: 721
*.co.yu
Via: [es] mailing liste



+1 Profil

icon Re: SuSe 9.3 + Intel 536ep22.04.2005. u 23:56 - pre 204 meseci
Probaj da čekiraš Stupid Mode u YaST-u.
Pozdrav.
 
Odgovor na temu

redfusion

Član broj: 12651
Poruke: 113
*.neobee.net.

ICQ: 346105695


Profil

icon Re: SuSe 9.3 + Intel 536ep23.04.2005. u 11:34 - pre 204 meseci
Probao, isto se desava. Ja bi nekeko najradije ako mogu da kupim modem exteran koji ce ta radi odma bez problema. Kazi mi molim te za koji znas da ce da radi, tj posto sam cuo da ima i externih soft modema, koji je pravi 100% hardwerski?
Ne znam da sve znam da ništa ne znam!
 
Odgovor na temu

tdjokic
Tomislav Djokic
u penziji
Beograd

Član broj: 6736
Poruke: 8305
*.bg.wifi.vline.verat.net.

Sajt: www.distrowatch.com


+209 Profil

icon Re: SuSe 9.3 + Intel 536ep23.04.2005. u 19:04 - pre 204 meseci
Citat:
redfusion: da kupim modem exteran koji ce ta radi odma bez problema. Kazi mi molim te za koji znas da ce da radi, tj posto sam cuo da ima i externih soft modema, koji je pravi 100% hardwerski?
Eksterni, seriski modemi, RS232, oni koji se prikljucuju na com portove su hardverski i rade pod svim OS-ima bez drajvera. Poznat je 1 ili 2 slucaja da su i tu napravili nesto softversko, ali veoma sumnjam da ces naici na tako nesto. Najprostija identifikacija je preko broja LED - ako ima recimo 4 LED onda je sumnjiv, mora imati vise.

Softverski su USB modemi. Neki od njih takodje rade pod Linuxom, ali to je nalik na PCI winmodeme - treba ti drajver itd.

Moras biti svestan cinjenice da eksternom, seriskom modemu ne treba drajver, ali ipak treba nesto malo podesiti, pa se moze desiti da ti se i taj "zaglavi" zbog neke sitnice.
Na svetu postoje samo 2 OS-a: 1. Mint, 2. svi ostali!
 
Odgovor na temu

mmirilovic
Mladen Mirilović
Čačak

Član broj: 10462
Poruke: 721
*.blueisp.co.yu.



+1 Profil

icon Re: SuSe 9.3 + Intel 536ep24.04.2005. u 10:53 - pre 204 meseci
U jednoj poruci si rekao da si kompajlirao drajvere. Jesi li i prošao kroz
instalacionu proceduru? Meni je zaista čudno da ti modem ne radi. Masa ljudi
je instalirala taj modem, i to na SuSE. Pogledaj po forumu. Nećeš ništa
spektakularno dobiti zamenom modema. Jer je taj modem provereno podržan
drajverima. Čak i ona skripta to potvrđuje. A kažeš i da lsmod izlistava
module za modem. Što znači da je drajver učitan. Ja sam siguran da je problem
u podešavanjima, i načinu kako si instalirao modem. Ili iz nekog razloga nisu
instalirani svi potrebni softverski paketi. Ili zbog podzemnih voda. Zaista
iz ove perspektive ne mogu da kažem gde da tražiš problem. Čak i sa novim
modemom, nema garancija da nećeš imati iste probleme.

Poslednji pokušaj.
wvdial je konzolni dialer. Na osnovu podešavanja u konfiguracionom
fajlu /etc/wvdial.conf konektuje se na internet. Kao root pokreni
"wvdialconf /etc/wvdial.conf". Ovo pi trebalo da "napuni" konf fajl
odgovarajućim opcijama. Zatim u tom konfiguracionom fajlu dodaj broj telefona
tvog provajdera, username i lozinku. Eventualno dodaj "Stupid Mode = 1". I
izbriši ; ispred tih redova. Kada sve to lepo uradiš, konektuješ se sa
"wvdial" kao root.
Pozdrav.
 
Odgovor na temu

tdjokic
Tomislav Djokic
u penziji
Beograd

Član broj: 6736
Poruke: 8305
*.COOL.ADSL.VLine.Verat.NET.

Sajt: www.distrowatch.com


+209 Profil

icon Re: SuSe 9.3 + Intel 536ep24.04.2005. u 19:32 - pre 204 meseci
... ili nabavi Mepis 2004.06 i PCI winmodem Lucent / Agere, ali ne softverski nego onaj malo bolji, koga sada zovu hardverski, tu nema sta da podesavas, drajveri za njega su vec instalirani i podeseni i odmah radi (naravno - moras upisati svoje korisnicko ime, pasvord, tel.br. provajdera)
Na svetu postoje samo 2 OS-a: 1. Mint, 2. svi ostali!
 
Odgovor na temu

redfusion

Član broj: 12651
Poruke: 113
*.neobee.net.

ICQ: 346105695


Profil

icon Re: SuSe 9.3 + Intel 536ep24.04.2005. u 22:30 - pre 204 meseci
Zao mi je, ali nista nije vredelo, u svakom slucaju hvala.
Sutra dobijam 2 modema da probam. Jedan je Conexant Soft k 56 data fax modem, a drugi je nekakav Lucent hardwerski serial externi 56k. Znam da je ovaj drugi bolji ali je i skuplji jel. Pokusao sam danas da pogledam na netu drivere za taj conexant, i video sam na www.linuxant.com da nisu besplatni, tj ako su free onda je ogranicen protok na 14. kbps. Ej, naplacivati drajvere za modem?

Jel znate gde se nalaze besplatni driveri za taj modem?

Sutra je dan D.
Ne znam da sve znam da ništa ne znam!
 
Odgovor na temu

tdjokic
Tomislav Djokic
u penziji
Beograd

Član broj: 6736
Poruke: 8305
*.COOL.ADSL.VLine.Verat.NET.

Sajt: www.distrowatch.com


+209 Profil

icon Re: SuSe 9.3 + Intel 536ep24.04.2005. u 23:14 - pre 204 meseci
Govorim napamet, jer nemam SUSE, ali mislim da je instalacija drjavera za Intel 536ep i taj Conexant Soft priblizno ista vrsta i kolicina maltretiranja za korisnika, plus sto za Conexant moras da dodatno trazis resenje za izbegavanje ogranicenja na 14.4k. Steta je sto si relativno brzo i olako napustio Intel 536ep, koji je kvalitetan modem i mnogima radi. Mislim da ti se isplati cak i da reinstaliras SUSE zbog toga, da ne bi morao da juris po sistemu sta je gde zaostalo od pre. Jos nesto - SUSE 9.3 je relativno sveza stvar, mozda ce se za koji dan javiti neko ko ima istu kombinaciju distribucije i modema i recu u cemu je problem prilikom instalacije. Ovde smo resili neke takve probleme, bas za SUSE (9.2 mislim), udruzenim snagama, malo kopajuci po Google, malo po sistemu i bilo se ispostavilo da jedan fajl nedostaje a da se modul ne ucitava prilikom starta. Pogledaj ovaj sajt http://start.linux.org.ba/I536ep, tu su izlistani neki problemi, ali za sada jos nema za 9.3.
Na svetu postoje samo 2 OS-a: 1. Mint, 2. svi ostali!
 
Odgovor na temu

redfusion

Član broj: 12651
Poruke: 113
*.neobee.net.

ICQ: 346105695


Profil

icon Re: SuSe 9.3 + Intel 536ep25.04.2005. u 11:49 - pre 203 meseci
Stigli su, evo bas ih testiram.
Prvi je Lucent i u winxp ga registruje kao Lucent win modem, a i izgleda nista bolje od onog soft(istog dizajna od prilike)

Drugi je IBM data fax modem, sa Conexant chipovima i jednom ogromnom crnom kutijom na sebi koja je valjda dokaz da je hardwerski. To je kako sam zamislio kontroler.

Ali, mrzim ovu rec, prvi ima line in i line out(ja sam koristio jedan kabel za u medem a jedan dalje za telefon, ranije) a ovaj meni bolji IBM ima samo jednu rupicu, tj za ulaz linije. Ne znam sta da radim, izgleda da cu seckati kablove.

Idem sada da instaliram SuSEtinu.
Ne znam da sve znam da ništa ne znam!
 
Odgovor na temu

redfusion

Član broj: 12651
Poruke: 113
*.neobee.net.

ICQ: 346105695


Profil

icon Re: SuSe 9.3 + Intel 536ep25.04.2005. u 13:44 - pre 203 meseci
Mamicu mu hebem!!!! -Susetu, ne prepoznaje IBM, a sekao sam kablove 20 minuta!!!

Idem da probam lucenta, ako me nema, za 1 sat zovite hitnu.
Ne znam da sve znam da ništa ne znam!
 
Odgovor na temu

redfusion

Član broj: 12651
Poruke: 113
*.neobee.net.

ICQ: 346105695


Profil

icon Re: SuSe 9.3 + Intel 536ep25.04.2005. u 14:46 - pre 203 meseci
Dialuje taj Lucen, pise connected 46xxx(sta vec)
i onda posle 30 sec izbaci da nije mogao da pokrene PPP
Sta da radim?
kako da manuelno podesim PPP?
--To je sa kinternetom, sa KPPP govori logging on to network i opet ne uspe zbog ppp. Kako da resim problemcinu.
Ne znam da sve znam da ništa ne znam!
 
Odgovor na temu

redfusion

Član broj: 12651
Poruke: 113
*.neobee.net.

ICQ: 346105695


Profil

icon Re: SuSe 9.3 + Intel 536ep25.04.2005. u 15:43 - pre 203 meseci
Mis'im sta reeeci....
Ne znam da sve znam da ništa ne znam!
 
Odgovor na temu

[es] :: Linux mreže :: SuSe 9.3 + Intel 536ep

Strane: 1 2 3

[ Pregleda: 13714 | Odgovora: 50 ] > FB > Twit

Postavi temu Odgovori

Navigacija
Lista poslednjih: 16, 32, 64, 128 poruka.