bon du coup j'ai fait un petit coup de bittorrent et une gravure vitesse 4. Les tests (de fedora) étaient tous négatifs mais l'installation a marché nickel. Brèf, tout va bien ou prèsque.
Je crois que FC4 est trop gourmand en puissance pour l'ordi qu'on m'a confié du coup je le rebascule sous FC3. Est ce que quelqu'un sait comment je peux paramétrer un modem
"MDP3858-WE" sous FC3. Pour info voici le résultat du scanmodem que j'ai fait tourner (message ci-dessous).
Merci pour votre aide
A+
Petit Penguoin
YOURMODEM.TXT
If the Primary and Subsystem Vendor information was not adeqaute,
it may be useful to search at [
www.pcidatabase.com]
---------------------------------------------------------------------------------------------
The proprietary Binary component of the some current winmodem drivers were compiled with
version 2.9n gcc compiler. Red Hat 8.0 and Mandrake 9.0 releases utilize
version 3.nn gcc compilers. This currently is causing difficulties either
in compiling and/or insertion of updated winmodem drivers.
The gcc compiler version of this System is: none
It will likely be necessary to force (-f) insertion of winmodem drivers, with credit to
Jos Vos: [
phep2.technion.ac.il]
For the ltmodem drivers with proprietary binary provided by Agere Systems,
compiling with versions gcc=3.nn is successful.
A minor edit required to compile PCTEL drivers has also been reported:
[
phep2.technion.ac.il]
Simple driver insertion fails in these cases with a message like:
----begin error----
% insmod lt_modem
Using /lib/modules/2.4.18-14/ltmodem/lt_modem.o
/lib/modules/2.4.18-14/ltmodem/lt_modem.o: The module you are trying to
load (/lib/modules/2.4.18-14/ltmodem/lt_modem.o) is compiled with a gcc
version 2 compiler, while the kernel you are running is compiled with
a gcc version 3 compiler. This is known to not work.
-----end error-----
It is necessary as Root to force (-f) loading with commands like:
insmod -f pctel
respecting the dependency ordering of the drivers.
Then check for insertion with:
lsmod
If driver insertion is successful, the forcing can be automated
by putting the lines (credit to Bhaskaran Raman) like the following,
install pctel /sbin/insmod --force pctel
In order of preference depending on your particular Linux installation.
Put these lines into ONLY ONE of the following files,
within any modem loading subsection if present:
/etc/modutils/ltmodem
/etc/modutils/aliases
/etc/modules.conf
Then inform your System of the edit for Debian like Systems with
update-modules
which rewrites and reads /etc/modules.conf . For other System types
depmod -a
re-reads the edited /etc/modules.conf .
Thereafter module loading should behave as previously.
For the ltmodem drivers loading,
it should suffice to either start a ppp session or
modprobe ptserial
-----------------------------------------------------
The System has Ethernet capability. If not expert,
shut down ethernet before initiated modem usage with:
# ifconfig eth0 down
00:09.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
Subsystem: Realtek Semiconductor Co., Ltd. RT8139
Flags: bus master, medium devsel, latency 32, IRQ 10
I/O ports at e000
Memory at e2420000 (32-bit, non-prefetchable)
Expansion ROM at e0000000 [disabled]
Capabilities: <available only to root>
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 =============
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