Ciao...come risaputo ci sono componenti hardware che (aimè) vengono riconosciuti solo da windows, tipo i win modem (ma a me succede anche con lo slot PCMCIA).
Dato che linux non riconosce questi componenti vorrei cercarne i driver, prima però dovrei sapere almeno la marca e il modello della perifeica...la domanda è, sapete se esiste un tool di diagnstica o simile che permette di identificare in linux l'hardware installato?
Drinking an eggs white each morning builds a man!
lspci
lsusb
Spulcia il FileSystem /proc
ma i comandi sopracitati non fanno altro che dare le stesse info che si possono ricavare con hwdrake o simili...e cioè restituiscono l'elenco dell'hardware riconosciuto.....come posso, invece, ricavare informazioni sull'hardware sconosciuto...
Per esempio, mi sono trovato a dover reinstallare windows 2000, alla fine dell'installazione la scheda video non era stata riconosciuta: non compariva neanche nell'elenco delle periferiche rilevate....ho scaricato un software di diagnostica (aida) che mi ha aiutato dicendomi che modelloera la cheda video, così ho potuto scaricarne i driver corretti e utilizzarne a pieno le caratteristiche.
posso fare la stessa cosa in linux (uso Mandrake10.0)?
Drinking an eggs white each morning builds a man!
il problema secondo me è da ricercare nei venditori di computer che molto spesso dimenticano cose fondamentali quali i manuali d'istruzioni. non tanto per le istruzioni me per le specifiche dell'ardware che hai comprato.
comunque in /proc qualcosa dovresti riuscire a trovarla, solo c'è da avere un po' di fantasia, io ancora ci capisco poco là dentro
@_=(115,-17,6);print+map{chr$_[$.=$_-$_]*$_**$.+++$_[$.]*$_**$.+++$_[$.]*$_**$.}$.-$...$#_
incolla i risultati di dmesg magari riusciamo a trovare qualche info
guarda da windows come vengono riconosciute e che driver usano
Con lspci a me spesso mi è capitato di vedere marca e modello di componenti non supportati da linux, tipo winmodem...Originariamente inviato da karloweb
ma i comandi sopracitati non fanno altro che dare le stesse info che si possono ricavare con hwdrake o simili...e cioè restituiscono l'elenco dell'hardware riconosciuto.....come posso, invece, ricavare informazioni sull'hardware sconosciuto...
Per esempio, mi sono trovato a dover reinstallare windows 2000, alla fine dell'installazione la scheda video non era stata riconosciuta: non compariva neanche nell'elenco delle periferiche rilevate....ho scaricato un software di diagnostica (aida) che mi ha aiutato dicendomi che modelloera la cheda video, così ho potuto scaricarne i driver corretti e utilizzarne a pieno le caratteristiche.
posso fare la stessa cosa in linux (uso Mandrake10.0)?
Tieni conto che con linux ho scoperto la marca della mia porta irda, cosa che con win non potevo fare, dato che nemmeno sulla scatola c'era scritto il nome del chip.
Powered by Slackware64 on Intel i7 920!
su linmodem mi sembra ho trovato "scanModem"...una simpatica utility, che tra l'altro mi usa le pciutils (tra le quali sono inclusi i comandi lspci e lsusb) la quale spuclia nel filesystem /proc alla ricerca di un modem e mi restituisce dei file formato ASCII che riportano un report completo della scansione e dei suggerimenti su come installare l'eventuale modem trovato.
Il problema è che i file sono scritti in inglese e io, ahimè, non ho molta dimistichezza con tale idioma per cui sto cercando di decifrare il risultato di scanModem al fine di scegliere la migliore soluzione da adottare (spero di non dover ricompilare il kernel!)..
Drinking an eggs white each morning builds a man!
allego il mio file generato , spero qualcuno possa aiutarmi:
(qui allego la prima parte del file visto che questo forum mi limita nel numero di caratteri che posso inserire)
ModemData.txt
The most recent update of scanModem accessed at http://linmodems.technion.ac.il/packages/scanModem.gz
should ALWAYS be used!! Current UPDATE=2004_Sept_19
URLs to cogent advice are regularly entered and updated, and your problem may be solved therein.
If further help is needed, send a description of your problem to: discuss@linmodems.org
with this ModemData.txt Attached, using the following in the email Subject Line:
scanModem, mandrake kernel 2.6.3-7mdk
Always send this ENTIRE Modem/ModemData.txt. It includes subtle diagnostic ouputs needed to best guide you.
If your PC is a laptop, please provide Make and Modem information.
For instructions to UNSUBSCRIBE from discuss@linmodems.org,
send an email to: discuss-help@linmodems.org
-------------- System information ------------------------
mandrake Mandrake Linux release 10.0 (Official) for i586
on System with processor: i686
supported by kernel: 2.6.3-7mdk
assembled with compiler: 3.3.2
with current System compiler GCC=3.3.2
/usr/bin/gcc -> /etc/alternatives/gcc
A /dev/modem symbolic link is not set.
----active COMM services are ------------
eth0 Link encap:Ethernet HWaddr 00:90:F5:1E:3A1
This COMM mode should be closed before using the modem, or DNS services may fail.
Under 2.6.n kernels, there is currently modem support by:
the more expensive Controller chipset modems using the open source serial code
Conexant software downloaded through http://www.linuxant.com
SmartLink slmodem drivers, including USB hardware
USB modems using the Open Source acm.ko driver
Lucent DSP (digital signal processing) chipsets but NOT:
soft modems ( though some are supported by slmodem drivers)
Intel 536EP and 537 modems
For all other modems, support projections are not available as of this update=2004_Sept_19
The following ppp related modules should be unpacked by root with:
# gunzip PathTo/ModuleName.ko.gz
/lib/modules/2.6.3-7mdk/kernel/drivers/net/bsd_comp.ko.gz
/lib/modules/2.6.3-7mdk/kernel/drivers/net/ppp_async.ko.gz
/lib/modules/2.6.3-7mdk/kernel/drivers/net/ppp_generic.ko.gz
/lib/modules/2.6.3-7mdk/kernel/drivers/net/slhc.ko.gz
/lib/modules/2.6.3-7mdk/kernel/drivers/net/ppp_deflate.ko.gz
/lib/modules/2.6.3-7mdk/kernel/lib/zlib_deflate/zlib_deflate.ko.gz
On most Systems, this will driven by installing the wvdial.rpm and the package providing the KPPP graphical dialing interface.
mandrake is not yet providing pre-compiled drivers for WinModems
An AC97 modem codec was not detected
---------- End SIL_id section ---------------
Path to lspci is: /usr/bin/lspci
--------- lspci scan ----------------
PCI_bus
00:00.0 Host bridge: Intel Corp. 82845 845 (Brookdale) Chipset Host Bridge (rev 11)
00:01.0 PCI bridge: Intel Corp. 82845 845 (Brookdale) Chipset AGP Bridge (rev 11)
00:1e.0 PCI bridge: Intel Corp. 82801BAM/CAM PCI Bridge (rev 42)
00:1f.0 ISA bridge: Intel Corp. 82801CAM ISA Bridge (LPC) (rev 02)
00:1f.1 IDE interface: Intel Corp. 82801CAM IDE U100 (rev 02)
00:1f.3 SMBus: Intel Corp. 82801CA/CAM SMBus Controller (rev 02)
00:1f.5 Multimedia audio controller: Intel Corp. 82801CA/CAM AC'97 Audio Controller (rev 02)
00:1f.6 Modem: Intel Corp. 82801CA/CAM AC'97 Modem Controller (rev 02)
01:00.0 VGA compatible controller: ATI Technologies Inc Radeon R250 Lf [Radeon Mobility 9000 M9] (rev 01)
02:04.0 FireWire (IEEE 1394): Texas Instruments TSB43AB21 IEEE-1394a-2000 Controller (PHY/Link)
02:06.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
02:07.0 CardBus bridge: ENE Technology Inc CB1410 Cardbus Controller
02:0a.0 USB Controller: VIA Technologies, Inc. USB (rev 50)
02:0a.1 USB Controller: VIA Technologies, Inc. USB (rev 50)
02:0a.2 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 51)
-------------------------------------
Modem candidates are at PCI_buses: 00:1f.6
Providing detail for device at PCI_bus 00:1f.6
with vendor-ID:device-ID
----:----
Class 0703: 8086:2486 Modem: Intel Corp. 82801CA/CAM AC'97 Modem Controller (rev 02) (prog-if 00 [Generic])
SubSystem 1558:5600 CLEVO/KAPOK Computer: Unknown device 5600
Flags: medium devsel, IRQ 11
I/O ports at 2400 [size=256]
I/O ports at 2000 [size=128]
Internal_test: ./scanModem test 8086:2486 1558:5600 mandrake 2.6.3-7mdk 3.3.2
The soft modem Subsystem operates under a controller
8086:2486 82801CA/CAM AC97 ICH3 capable of supporting modem Subsystem chips from:
Pctel
AgereSystems
Conexant
Intel
Smartlink
Softmodem chipset identification is ambiguous because modem drivers
are themselves necessary to surely identity the Subsystem softmodem chip.
Follow the guidance in Modem/1stRead.txt and Modem/General.txt for identifying the chip under Microsoft;
include the ATI output information and Modem/ModemData.txt with your email to discuss@linmodems.org
Alternatively install the slmodem-2.9.9 SmartLink drivers.
which also support MANY non-Smartlink softmodem chips.
BE CAREFUL, slmodem-2.9.10 and later versions NO LONGER have this capability.
At a minimum the driver can serve in identifying the true chipset
even if it does not fully support the modem. After installing the driver, reboot and rerun
./scanModem
The Smartlink section below has implementation details.
First accessing chipset provider and modem assembler information
for the modem SubSystem under the AC97 or MC97 Controller.
=== Checking 1558 through chipset providers and modem assemblers ====
Vendor 1558 is Clevo/Kapok Computer
The Intel AC97 8086:2486 controller can host
modem SubSystem 1558:1800
Vendor=134d is PCTel and Vendor=134c is Chori Joho System Co. Ltd,
producing idenitcal devices including deviceIDs:
7890 PCT789T-C1 HSP MicroModem 56
7891 PCT 789T HSP MicroModem 56
7892 PCT 789T-A HSP MicroModem 56
7893 S911 K017 HSP MicroModem 56
7894 FT13 HSP MicroModem 56
7895 PCT789T-C1 HSP MicroModem 56
7896 pct789t-c1 HSP MicroModem 56
7897 97860963 HSP MicroModem 56
9714 PCT 288-1A PCTEL
D800 pct388p-a pctel 56k modem
The latest code releases are at http://linmodems.technion.ac.il/pctel-linux .
and is the first Fedora competent release for Via, Asus, CM8x, SiS, PCT and AMR based modems. The ISA card pct388p is not supported by this driver series.
For some modems, it seems to be stable now, for others, support is still broken.
The PCTel Inc., modem sector has been sold to Conexant, with future updates for Linux support in doubt.
There are No success reports under the 2.6.nn kernels using PCTel code.
For compiling and installing the pctel drivers, read the
PCTel minHOWTO: http://www.peacefulaction.org/sayamindu/docs.php
Details on PCtel usage that have been written to Modem/General.txt
After installing the drivers add to /etc/modules.conf
####### for pctel modem ######
alias char-major-62 pctel
alias /dev/modem ptserial
install pctel /sbin/insmod "-f" "pctel"
post-install pctel /sbin/insmod ptserial
# country code for pctel modem, for USA
options ptserial country_code=1
######## pctel end ####
then
# depmod -a
# modprobe ptserial
should then load both drivers,
Read ModemTesting.txt for implementing
# wvdialconf /etc/wvdial.conf
for a first functionality check.
For some Pctel soft modems under 8086:2486 82801CA/CAM AC97 ICH3 ,
the SmartLink slmodem-2.9.n serve.
The advantage is current updates, extending into the 2.6.n kernels.
Vendors 127a and 14f1 are Conexant, successor to Vendor=148d Rockwell technology.
With respect to software support there are two main types, hcflinmodem* and hsflinmodem* .
The HCF (Host Controller Free) which have a digital signal processsing (DSP) chipset,
while the HSF in the soft modem family without a dsp.
HSF support of version 5.03 is included with SuSE 9.0 for support of 2.4.21 version kernels.
For support of 2.6.n kernels, new releaseses are provided at http://www.Linuxant.com/drivers/
Linuxant is providing free test packages for low speed CONNECTs.
There is a one time subscription fee for full high speed support.
A detailed software installation example is provided at:
http://linmodems.technion.ac.il/arch.../msg00350.html
SuSE Conexant installation Re: Emergency!!! /Date:/ Wed, 11 Feb 2004 06:10:39 -0500
Modems with the following PCI_IDs also have Conexant HCF (Controller free) chipsets.
1024:1024 (Zenith Data Systems)
148D:1003 (DIGICOM Systems)
158B:0015 (Allied Data Technologies Tornado VFM56x-PRC)
141A:1035 (Apache Micro)
The following six may be either HCF of HSF modems. Test the HSF package first
(127a,14f1)1025,1085, 2005)
Should a HCF driver installation fail to serve among there,
then uninstall and instead try the HSF driver resource.
Subsystem HSF Conexant soft modems serve under AC97 or MC97 controllers. These include:
14f1
SubSystem 104d:814e under a 1039:7013 Silicon Integrated Systems modem controlled has a Conexant chip
After loading of HSF drivers, there will be displayed by command: /sbin/lsmod
Module Size Used by Tainted: P
hsfich 119116 0 (autoclean)
hsfserial 26388 0 (autoclean)
hsfengine 1126348 0 (autoclean) [hsfserial]
hsfosspec 35328 0 (autoclean) [hsfich hsfserial hsfengine]
plus many others not modem related.
While drivers are pre-compiled for some Linux distributions,
the installation of the HCF/HSF packages DOES in general require kernel-source/ preparation,
as described in ModemDriverCompiling.txt.
A post install suggestion for adjusting PCI latency is:
http://phep2.technion.ac.il/linmodem.../msg05210.html
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 from: http://developer.intel.com/design/mo...rt/drivers.htm
Also check at: http://linmodems.technion.ac.il/resources.html
for beta releases and perhaps Already compiled drivers for some Linux distributions
---------------------
The installer code candidate is:
Intel_secure-537AA-2.37.50.1.tgz
But the Intel 537 readout needs confirmation !!
Sadly there are a few mis-designations in the pciids dataset, which ./scanModem relies on
Too many modems are being labeled Intel537 types.
http://linmodems.technion.ac.il/arch.../msg02463.html
http://linmodems.technion.ac.il/arch.../msg02476.html
This includes the distinct Agere, Conexant and SmartLink chipsets types. Conseqeuntly
YOU must manually obtain further information under Microsoft Windows through modem ATI tests/queries
as instructed in Modem/General.txt Please include this information in any report to discuss@linmodems.org
Vendor 11c1 corresponds to Lucent Technologies or subsidiary Agere Systems, Inc.
Information is at: http://www.agere.com/client/modem_dsp.html
-----------
Under the controller 8086:2486 82801CA/CAM AC97 ICH3 ,
the modem subSystem 1558:5600
will ONLY be supported by AgereSoftModem drivers if it has an Agere chipset.
Thus establish identity of the softmodem chipset through tests described in Modem/General.txt
-----------
Software access is initiated through code sponsor IBM:
http://www-3.ibm.com/pc/support/site...cid=MIGR-52698
AC97/MC97 link modems may evoke a modem_codec with SIL_id = 39.
Should the Agere software fail the SmartLink slmodem-2.9.n or slmdm-2.7.10 may serve.
Current support from AgereSystems is only under 2.4.n kernels and for the following modem controllers:
8086
1039:7013 SIS
1106:3068 VIA
----------------
The ltmodem drivers do NOT support this modem.
Under the controller 8086:2486 82801CA/CAM AC97 ICH3 ,
the modem subSystem 1558:5600
may be supported by the SmartLink slmodem-2.9.n drivers, even for non-SmartLink chipsets.
------------------------------
Drinking an eggs white each morning builds a man!
ecco la seconda parte)))
SmartLink at http://www.smlink.com/ owns vendor IDs 163c 2000 2003 2004
Download software through: http://www.smlink.com/main/index1.php?ln=en&main_id=40
Use slmodem-2.9.9 for service of non-SmartLink chipsets.
There may be a warning about a not-SmartLink modem as the drivers load.
But just proceed with modem functionality tests, as described in ModemTesting.txt
A report on the softmodem chipset identity after slamr driver installation by:
# modprobe slamr
# dmesg | grep slam
The Intel ICH softmodem controllers can utilize the a driver provided along with the
ALSA sound support software: snd-intel8x0m.ko . Use the slmodem-2.9.9-alsa package to compile the slmodemd for managing the complementary modem ports and fax service.
The slmodem-2.9.10 and later versions service ONLY SmartLink chipsets!
For guidance see slmodem-2.9.6 installation report: http://linmodems.technion.ac.il/arch.../msg00176.html
is cogent to both USB and PCI modems, except that for PCI modems,
the driver is slamr.o and the port created with:
slmodemd --country=YourCountry /dev/slamr0
See IMPORTANT details concerning slmodem usage in Modem/General.txt
If wvdial is being used for dialout, there must be added to /etc/wvdial.conf
Carrier Check = no
Smartlink products include the:
163c:5459 SmartPCI561 modem and chipsets for other Brandname PCI modems;
a chipset for USB modems, the SmartUSB56 (ST7554) based modems
with vendor/product usb ids: 0483:7554 supported,
and a chipset incorporated in many BrandName softmodems.
=== Checking 8086 through chipset providers and modem assemblers ====
======= PCI_ID checking completed ======
Update=2004_Sept_19
Analyzing information for PCMCIA device at PCI Bus 02:07.0
GREPping for an inserted PCMCIA modem with filter: ommunication
If a PCMCIA modem is currently inserted and the sockets activated by
/etc/init.d/pcmcia start
then the PCMCIA bridge is NOT transparent.
If the modem is known to have a Lucent digital signal processing chipset,
then PCMCIA.tar.gz variant assembled by Joern Wustenfeld is necessary,
rather than the standard ltmodem-8.26a9.tar.gz at http://ltmodem.heby.de/
The following information blocks just query some ppp support items.
================================================== ==
grep ppp /etc/modprobe.conf
-------------------------------------
-------------------------------------
Be sure to read the section about ppp related modules and aliases in Modem/General.txt
Be sure to read the Ethernet section of Modem/General.txt
DEVPPP=crw------- 1 root root 108, 0 gen 1 1970 /dev/ppp
DEVFS=active
DEVFSD=/etc/devfsd.conf
---- dmesg queries -------
ACPI disabled because your bios is from 92 and too old
You can enable it with acpi=force
Kernel command line: root=/dev/hda1 devfs=mount acpi=ht splash=silent vga=788
No local APIC present or hardware disabled
ACPI: Interpreter disabled.
apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac)
hub 1-0:1.0: connect-debounce failed, port 2 disabled
The ModemDriverCompiling.txt is a MUST READ,
if you are not experienced in configuring kernel-source/
or get "unresolved symbols" upon driver insertion.
Most recent WinModem fixes are in: http://linmodems.technion.ac.il/FAQ.html
Drinking an eggs white each morning builds a man!
Permessi di invio
Rispondi quotando