|
|
 |
Olivier$2002318 Olivier
15/11 :: 20:49
Habitué
| | J'ai besoin d'un petit dépannage si possible. Je débute avec le pinguin et il se rebelle.
Voilà : je viens de passer sous LINUX Red Hat 7.3 et j'ai quelques problèmes pour me connecter à Internet : c'est simple je n'y arrive pas.
Je n'y parviens que sous Windows. Mon DD est partitionné bien sûr.
Je pense correctement avoir paramétré ma connexion avec l'assistant. Lorsque je lance Kppp et que je me connecte, j'ai aussitôt un message me disant qu'il est busy, donc oqp, et malgré l'avoir configuré avec le son à fond, je ne l'entends pas composer le n°.
J'ai traîné par ci par là sur quelques sites et j'ai entendu parlé de winmodem ou linmodem. Le mien en fait parti. C'est un Micromodem HSP56 de chez Pctel, installé sur le port COM 4 de ma machine, son chip de type 8738.
Par chance et ce qui est rare pour ce genre de modem, j'ai réussi à me dégoter les pilotes correspondants, et un mini HOW TO en anglais.
J'ai amorcé le détarage et l'install. Mais, lors de la configuration j'ai eu droit à :
checking for /usr/src/linux/include/linux/modversions.h... no
configure: error: modversions.h is missing - you should configure your kernel first!
et impossible donc de poursuivre. Que dois-je faire exactement pour configurer le kernel?
Dans le post ci dessous le copier/coller de la console avec l'erreur.
J'ai vérifié le kernel de ma distribution avec uname -r c'est ok d'après le HOWTO.
[root@localhost root]# cd /home/olivier
[root@localhost olivier]#
[root@localhost olivier]# uname -r
2.4.18-3
[root@localhost olivier]# cd /home/olivier
[root@localhost olivier]# ls
pctel-0.9.4.tar.gz
[root@localhost olivier]# tar -xzvf pctel-0.9.4.tar.gz
pctel-0.9.4/
pctel-0.9.4/misc/
pctel-0.9.4/misc/Makefile.am
pctel-0.9.4/misc/Makefile.in
pctel-0.9.4/misc/SlackBuild.in
pctel-0.9.4/misc/build_rpms.sh.in
pctel-0.9.4/misc/pctel.spec.in
pctel-0.9.4/misc/autogen.sh
pctel-0.9.4/misc/pctel.spec
pctel-0.9.4/README
pctel-0.9.4/AUTHORS
pctel-0.9.4/COPYING
pctel-0.9.4/ChangeLog
pctel-0.9.4/INSTALL
pctel-0.9.4/Makefile.am
pctel-0.9.4/Makefile.in
pctel-0.9.4/NEWS
pctel-0.9.4/acinclude.m4
pctel-0.9.4/aclocal.m4
pctel-0.9.4/configure
pctel-0.9.4/configure.in
pctel-0.9.4/install-sh
pctel-0.9.4/missing
pctel-0.9.4/mkinstalldirs
pctel-0.9.4/cvscompile.sh
pctel-0.9.4/FAQ
pctel-0.9.4/src/
pctel-0.9.4/src/Makefile.am
pctel-0.9.4/src/Makefile.in
pctel-0.9.4/src/module/
pctel-0.9.4/src/module/Makefile.am
pctel-0.9.4/src/module/Makefile.in
pctel-0.9.4/src/module/ptmodule.c
pctel-0.9.4/src/ptserial/
pctel-0.9.4/src/ptserial/Makefile.am
pctel-0.9.4/src/ptserial/Makefile.in
pctel-0.9.4/src/ptserial/ptserial-2.4.6.c
pctel-0.9.4/src/ptserial/ptserial-2.4.7.c
pctel-0.9.4/lib/
pctel-0.9.4/lib/asus/
pctel-0.9.4/lib/asus/dsp.a
pctel-0.9.4/lib/asus/i810hal.a
pctel-0.9.4/lib/cm8738/
pctel-0.9.4/lib/cm8738/pctel-cm8738.o
pctel-0.9.4/lib/pct789/
pctel-0.9.4/lib/pct789/dsp.a
pctel-0.9.4/lib/pct789/pcthal.a
pctel-0.9.4/lib/sis/
pctel-0.9.4/lib/sis/dsp.a
pctel-0.9.4/lib/sis/i810hal.a
pctel-0.9.4/lib/via/
pctel-0.9.4/lib/via/dsp.a
pctel-0.9.4/lib/via/via686ahal.a
pctel-0.9.4/lib/Makefile.am
pctel-0.9.4/lib/Makefile.in
pctel-0.9.4/lib/control.a
pctel-0.9.4/lib/vuart.o
pctel-0.9.4/modules/
pctel-0.9.4/modules/Makefile.am
pctel-0.9.4/modules/Makefile.in
pctel-0.9.4/include/
pctel-0.9.4/include/pctel.h
pctel-0.9.4/include/halwraps.h
pctel-0.9.4/include/vuart.h
pctel-0.9.4/include/Makefile.am
pctel-0.9.4/include/Makefile.in
pctel-0.9.4/m4/
pctel-0.9.4/m4/Makefile.am
pctel-0.9.4/m4/Makefile.in
pctel-0.9.4/m4/_pctel.m4
[root@localhost olivier]# cd pctel-0.9.4/
[root@localhost pctel-0.9.4]# ./configure -with-hal=cm8738
checking for a BSD compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for mawk... no
checking for gawk... gawk
checking whether make sets ${MAKE}... yes
checking build driver for... HAL_CM8738
checking for gcc... gcc
checking for C compiler default output... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for executable suffix...
checking for object suffix... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for style of include used by make... GNU
checking dependency style of gcc... none
checking whether make sets ${MAKE}... (cached) yes
checking for a BSD compatible install... /usr/bin/install -c
checking whether ln -s works... yes
checking for mawk... (cached) gawk
checking how to run the C preprocessor... gcc -E
checking for /usr/src/linux/include/linux/modversions.h... no
configure: error: modversions.h is missing - you should configure your kernel first!
[root@localhost pctel-0.9.4]#
| |
|
habana$2002318 habana
15/11 » 21:16
Admin
| | il y avait cette doc qui semble te concerner (la page originelle a disparue):
ps: c'est au chapitre 8
si tu as besoin de trad , fais moi signe
***********************************************************
FAQ - Frequently Asked Questions
--------------------------------
Table of Contents:
------------------
1. Will my modem XXX work with this driver?
2. What is needed to compile this driver?
3. How do I install this driver?
4. How do I load the driver in the boot-up?
5. Do you work for PCTEL?
6. Module options
7. Country Code selection
8. Compile error: no modversions.h
9. Unresolved Symbols
10. Modem not responding
1. Will my modem XXX work with your driver?
-------------------------------------------
Go to "Linux/Modem Compatibility Knowledge Base" at
http://www.idir.net/~gromitkc/winmodem.html
and follow the instructions to find your modem.
If you don't know, just try it!
2. What is needed to compile this driver?
-----------------------------------------
* kernel-sources
* a working compiler (preferably gcc)
* development tools (make, awk, ...)
3. How do I install this driver?
--------------------------------
Please read the INSTALL file.
4. How do I load the driver in the boot-up?
--------------------------------------------
If you have sucessfully done "make install", the driver is located
in /lib/modules/"your-kernel-number"/misc/
The driver consists of two parts:
pctel.o
ptserial.o
You insert these drivers with the command
insmod pctel
insmod ptserial
You have to make sure, that these two commands are run every time you
reboot your machine, by adding these two commands to an init script,
according to your distribution.
If you want to enable autoloading of the modules,
the following lines in /etc/modules.conf would suffice:
# for pctel modem
alias char-major-62 ptserial
below ptserial pctel
# country code for pctel modem
options ptserial country_code=13
Make sure, you run "depmod -a" after you changed your /etc/modules.conf.
Then starting ppp would autoload the modules,
or "modprobe ptserial" will insert them.
5. Do you work for PCTEL?
-------------------------
I don't work for PCTEL, i am maintainig this driver in my free time.
6. Module options
-----------------
You can add some module parameters in you /etc/modules.conf or at
insmod/modprobe time:
For all HALs:
- country_code: Country code (see below).
- irq: Force to using irq #.
- iobase: Force to use iobase for modem detection.
Only for I81X/VAI686A HALs:
- iobase1: Force the iobase 1
NOTE: if you want to set iobase or iobase1, you should use
irq/iobase/iobase1 at same time.
Only for CM8738/PCT789 HALs:
- vendor_id: vendor ID of the modem
- device_id: device ID of the modem.
NOTE: vendor_id and device_id should be used at the same time,
but you cannot combinate this two options with
iobase, iobase prevail to (vendor/device)_id detection.
7. Country Code selection
-------------------------
The PCTEL modem has the possibility to select a country code.
If the country code is not selected, the default country code,
which is USA, will be used and it should work for most countries.
However, there is a way that you can select the country code for
better performance.
To select the country code, instead of "insmod ptserial.o" do:
insmod ptserial.o country_code=X
Table of country codes:
country_code country_name
1 USA
2 FRANCE
3 GERMANY
4 ITALY
5 SWEDEN
6 UK
7 JAPAN
8 AUSTRALIA
9 SPAIN
10 TAIWAN
11 SINGAPORE
12 KOREA
13 SWITZERLAND
14 NORWAY
15 NETHERLANDS
16 BELGIUM
17 CANADA
18 IRELAND
19 PORTUGAL
20 POLAND
21 HUNGARY
22 FINLAND
23 DENMARK
24 AUSTRIA
25 S.AFRICA
26 CTR21 COUNTRIES
27 CHINA
28 MALAYSIA
29 LUXUMBURG
30 GREECE
31 ICELAND
32 NEW ZEALAND
33 BRAZIL
8. Compile error: no modversions.h
----------------------------------
If you see something like:
configure: error: modversions.h is missing - you should configure
your kernel first!
then, you either have:
a) not installed your kernel sources - install them
b) your kernel sources at a different path - specify the path with:
./configure --with-kernel-includes=DIR
c) no "modversions.h" in your kernel sources -
create the modversions.h by running
$ cd [...] (where you have your kernel sources, default is
/usr/src/linux)
$ make dep
this should make you a modversions.h in [...]/linux/include/
If this did not work, an ugly hack is to create an empty file there:
$ mkdir -p [...]/linux/include/linux
$ touch [...]/linux/include/linux/modversions.h
9. Unresolved Symbols
---------------------
The unresolved symbols arise when there is a mismatch between the
versions of the running kernel & the kernel-headers used to compile the
driver.
These symbol differences can often be masked across flavor differences
and even some larger differences through use of Mark Speith's fixscript,
available at: www.medres.ch/~jstifter/linux/pctel.html (links section).
Of course, the robust cure (and much better)
is too use the same kernel-headers as were used
in the compile of the running kernel. Unfortunately the kernel-header
packages provided by some Linux distros are not exactly version matched
with the stock kernels.
If you do a
depmod -e pctel.o
or
depmod -e ptserial.o
you can generate an "unresolved symbols" report.
If you have unresolved symbols:
1) download fixscript.gz
2) unpack it with "gzip -d fixscript.gz"
3) make it executable with "chmod +x fixscript"
4) install all modules, needed for your system
5) run fixscript with
./fixscript old_module.o new_module.o
this will create you the new module, which you can try to insert
with "insmod new_module.o"
If fixscript reports an error like
objcopy: --redefine-sym: Symbol "" is target of more than one redefinition
then, fixscript can not help you.
In this case, you have to compile yourself a kernel. Ask the linmodems
mailing list if you have problems - it is not that hard!
10. Modem not responding
------------------------
If wvdial reports that the modem is not responding, pppd locks up, or
minicom blocks keyboard input, this could be due to a conflict with
the sound driver (this problem has been observed in an on-board sound
system involving the SiS7018 audio controller, but may affect other
systems too). Unfortunately in this situation sound and modem support
are mutually exclusive. To use the modem it is necessary to disable
the kernel sound driver. Either use a kernel without built in sound
support, or in the case of a modularised kernel, disable loading of
the sound driver module. This can be done by editing the file
/etc/modules.conf and commenting out the line associating a sound
slot with the sound driver module, ie.
#alias sound-slot-0 trident
---
Jan Stifter, 2001-10-29
j.stifter@[no-spam]medres.ch
http://www.medres.ch/~jstifter/pctel
| |
|
Olivier$2002321 Olivier
18/11 :: 09:23
Habitué
| | Merci habana, je vais regarder à çà j'avais une doc similaire, je vais essayer  | |
|
habana$2002321 habana
18/11 :: 13:02
Admin
| | en dernier recours, il te reste la possibilité de mettre un fichier vide du même nom ...
( mmm, pas très classe cette méthode  )
dis moi si ça avance
| |
|
Olivier$2002321 Olivier
18/11 :: 20:23
Floodeur en herbe
| | Bon, je ne te refais pas un copier coller de la console, mais quoi que je fasse il me demande d'installer les sources du kernel et là .... terrain obscur pour moi, pour l'instant.
je pense que mon pb est par rapport à ce point là :
8. Compile error: no modversions.h
----------------------------------
If you see something like:
configure: error: modversions.h is missing - you should configure
your kernel first!
then, you either have:
a) not installed your kernel sources - install them
b) your kernel sources at a different path - specify the path with:
./configure --with-kernel-includes=DIR
c) no "modversions.h" in your kernel sources -
create the modversions.h by running
$ cd [...] (where you have your kernel sources, default is
/usr/src/linux)
$ make dep
this should make you a modversions.h in [...]/linux/include/
If this did not work, an ugly hack is to create an empty file there:
$ mkdir -p [...]/linux/include/linux
$ touch [...]/linux/include/linux/modversions.h
Je vais insister, çà va peut-être me tilter.
 | |
|
habana$2002322 habana
19/11 :: 00:07
Admin
| | mes expli par email t'ont un peu aidées ?
allez, te cogne pas trop fort, tu pourras plus profiter de ta distrib 
tu as installé quoi, au fait ? | |
|
Olivier$2002323 Olivier
20/11 :: 20:21
Floodeur en herbe
| | Red Hat 7.3. Je me cogne la chetron uniquement pour cette foutu histoire de modem & de kernel à configurer. le reste c'est le pied ! merci pour tes explications, oui, effectivement, j'ai compris deux ou 3 bricoles avec. mais je préfére continuer le reste du pb en private. Jettes un coup d'oeil à tes messages privés | |
|
philou$2003086 philou
28/03 :: 07:59
Membre inscrit
| | slt .......
moi aussi g exactement le meme pb ...... sous une mandrake 8.0
... il faut les sources du kernel dans /usr/src/linux/include je crois pour qu'il puisse complier .... dans un 1 er temps g cru ne pas les avoir ... donc je les ai dl , mais meme en les remplacant ou en indiquant le path du kernel dans mon reprtoire /home ou /root avec l'option --with-kernel=path/de/mon/kernel , ca marche po
meme chose pour la compilation de mes drivers realtek ethernet ..... kelk'un a une idée pourkoi il voit pas mes sources ???
p.s : le modversions.h semble vide , juste 2 lignes de commentaires .... ke doit il y avoir en théorie ???
merci de l'aide
++ | |
|
habana$ habana
28/03 :: 10:03
Admin
| | cette page pourra t'aider:
http://www.destination-linux.org/forums/index.php?s=5f2c144adb443a47087f8e88d3684684&act=ST&f=13&t=250&hl= | |
|
zakaria600$2003113 zakaria600
24/04 :: 16:19
Membre inscrit
| |  slt .......
moi aussi j'avais exactement le meme pb avec le Micromodem HSP56 sous mandrake 9.0 et g pu le regler c'etait tres facile
si tu n'as pas encore regler le probleme voici mon E-mail:
zakaria600@caramail.com
ok | |
|
qwerty_x$ qwerty_x
07/05 :: 13:51
Anonyme
| | ben alors vas y moi aussi j'ai le même blem ): ! | |
|
zakaria600$2003113 zakaria600
07/05 :: 14:10
Membre inscrit
| | Dans le rep /usr/src/ tu trouveras 2 ou 3 reps
1)-linux
2)-linux xxmdkxxx
bon tu n'auras qu'a renommer le rep linux-xx-mdk-xx en linux tout simplement.
tester avec PCTEL Linux PCI driver, version 0.9.6 | |
