Enviada: Seg Dez 04, 2006 10:56 am Assunto: Modem Lucent não aparece nem placa de tv pci nFedora Core 5?
Estive tentando instalar o modem Lucent V90 no Fedora Core 5.
Constatei que o modem não aparece na lista de dispositivos PCI atraves do comando lspci:
[root@localhost ~]# /sbin/lspci
00:00.0 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge
00:00.1 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge
00:00.2 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge
00:00.3 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge
00:00.4 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge
00:00.7 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge
00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI bridge [K8T800/K8T890 South]
00:0f.0 IDE interface: VIA Technologies, Inc. VT8251 AHCI/SATA 4-Port Controller
00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 07)
00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 90)
00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 90)
00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 90)
00:10.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 90)
00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 90)
00:11.0 ISA bridge: VIA Technologies, Inc. Unknown device 3287
00:11.7 Host bridge: VIA Technologies, Inc. VT8251 Ultra VLINK Controller
00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 7c)
00:13.0 PCI bridge: VIA Technologies, Inc. VT8251 PCI to PCIE Bridge
00:13.1 PCI bridge: VIA Technologies, Inc. VT8251 PCI to PCI Bridge
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
01:00.0 VGA compatible controller: nVidia Corporation NV34 [GeForce FX 5200LE] (rev a1)
02:00.0 PCI bridge: VIA Technologies, Inc. VT8251 PCIE Root Port
02:00.1 PCI bridge: VIA Technologies, Inc. VT8251 PCIE Root Port
02:01.0 Audio device: VIA Technologies, Inc. VIA High Definition Audio Controller
[root@localhost ~]# /sbin/lspci
00:00.0 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge
00:00.1 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge
00:00.2 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge
00:00.3 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge
00:00.4 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge
00:00.7 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge
00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI bridge [K8T800/K8T890 South]
00:0f.0 IDE interface: VIA Technologies, Inc. VT8251 AHCI/SATA 4-Port Controller
00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 07)
00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 90)
00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 90)
00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 90)
00:10.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 90)
00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 90)
00:11.0 ISA bridge: VIA Technologies, Inc. Unknown device 3287
00:11.7 Host bridge: VIA Technologies, Inc. VT8251 Ultra VLINK Controller
00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 7c)
00:13.0 PCI bridge: VIA Technologies, Inc. VT8251 PCI to PCIE Bridge
00:13.1 PCI bridge: VIA Technologies, Inc. VT8251 PCI to PCI Bridge
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
01:00.0 VGA compatible controller: nVidia Corporation NV34 [GeForce FX 5200LE] (rev a1)
02:00.0 PCI bridge: VIA Technologies, Inc. VT8251 PCIE Root Port
02:00.1 PCI bridge: VIA Technologies, Inc. VT8251 PCIE Root Port
02:01.0 Audio device: VIA Technologies, Inc. VIA High Definition Audio Controller
Este é o que me retornou o utilitario scanmodem:
[root@localhost scanModem]# ./scanModem
From http://linmodems.technion.ac.il , get a recent update of scanModem,
if this copy was not there obtained. There are weekly updates.
Updated on: 2006_November_07
Identifying PCI bus slots with candidate modems.
=== Finished modem firmware and bootup diagnostics section. ===
=== Next deducing cogent software ===
Analysing card in PCI bus 02:01.0, writing to scanout.02:01.0
The modem driver snd-intel8x0m is Not loaded.
To enable functional diagnostics, please either briefly login as Root:
su - root (Not for Ubuntu)
and unload and reload the modem driver
modprobe -r snd-intel8x0m
modprobe snd-intel8x0m
Exit Root status
exit
and rerun
./scanModem
2nd run of scanModem
Checking for match with Archived softmodem information.
IDENT=
Using scanout.02:01.0 data, and writing guidance to ModemData.txt
Writing residual guidance customized to your System.
A subfolder Modem/ has been written, containing these files with more detailed Information:
------------------------------------------------------------------------------------------
1stRead.txt DriverCompiling.txt InfoGeneral.txt ModemData.txt
Rational.txt scanout.02:01.0 SoftModem.txt Testing.txt
UNSUBSCRIBE.txt wvdial.txt YourSystem.txt
-------------------------------------------------------------------------------------------
Please read 1stRead.txt first for Guidance.
ModemData.TXT
Only plain text email is forwarded by the DISCUSS@linmodems.org List Server.
Do use the following as the email Subject Line:
SomeName, YourCountry Fedora Core release 5 (Bordeaux)
Kernel kernel 2.6.15-1.2054_FC5
This will alert cogent experts, and distinguish cases in the Archives.
YourCountry will enable Country Code guidance.
Occassionally responses are blocked by an Internet Provider mail filters.
So in a day, also check the Archived responses at http://www.linmodems.org .
Local Linux experts can be found through: http://www.linux.org/groups/index.html
-------------------------- System information ----------------------------
Fedora Core release 5 (Bordeaux)
Kernel
Linux version 2.6.15-1.2054_FC5 (bhcompile@hs20-bc1-7.build.redhat.com) (gcc version 4.1.0 20060304 (Red Hat 4.1.0-3)) #1 SMP Tue Mar 14 15:48:20 EST 2006
scanModem update of: 2006_November_07
USB modem not detected.
New HDA card type:
Modem or host audio card candidates have firmware information:
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
02:01.0 1106:3288 1043:818f Audio device: VIA Technologies, Inc. VIA High Definition Audio Controller
Modem interrupt assignment and sharing:
17: 11585 IO-APIC-level HDA Intel
--- Bootup diagnositcs for card in PCI slot 02:01.0 ----
ACPI: PCI Interrupt 0000:02:01.0[A] -> GSI 17 (level, low) -> IRQ 17
PCI: Via IRQ fixup for 0000:02:01.0, from 11 to 1
PCI: Setting latency timer of device 0000:02:01.0 to 64
=== Finished modem firmware and bootup diagnostics section. ===
=== Next deducing cogent software ===
For candidate modem in PCI bus: 02:01.0
Class 0403: 1106:3288 Audio device: VIA Technologies, Inc. VIA High Definition Audio Controller
Primary PCI_id 1106:3288
Support type needed or chipset:
scanModem could not identify the Support Type needed from diagnosics or archives.
If an alternative boot into Microsoft windows can be done, do mouse
clicks on:
Start > Settings > Control Panel > Classical View (for Window XP) > System
> Hardware > Device Manager > Modems > Click on the + > Modem. Double click to
expand the graphic. Manufacturer information may be displayed. For example, CXT
stands for Conexant. Click the Diagnostics Tab. Record any hardware ID or vendor
and device information.
Next do the Query Modem and record the ATI specifications displayed such as:
ATI3 - Agere SoftModem Version 2.1.22
ATI5 - 2.1.22, AMR Intel MB, AC97 ID:SIL REV:0x27
Try to identify the modem setup file, with name perhaps MODEM.INF.
If may contain chipset Vendor informaton.
Completed candidate modem analyses.
The base of the UDEV device file system is: /dev/.udev
Versions adequately match for the compiler installed: 4.1.0
and the compiler used in kernel assembly: 4.1.0
Compiling resources appear complete:
make utility - /usr/bin/make
Compiler version 4.1
kernel_headers base folder /lib/modules/2.6.15-1.2054_FC5/build
To enable dialout without Root permission do:
$ su - root (not for Ubuntu)
chmod a+x /usr/sbin/pppd
or under Ubuntu related Linuxes
chmod a+x /usr/sbin/pppd
Checking settings of: /etc/ppp/options
lock
Don't worry about the following, it is for the experts
should trouble shooting be necessary.
==========================================================
Checking for modem support lines:
--------------------------------------
/device/modem symbolic link:
slmodemd created symbolic link /dev/ttySL0:
Within /etc/udev/ files:
/etc/udev/rules.d/50-udev.rules:KERNEL=="modems/mwave*", NAME="%k", GROUP="uucp", MODE="0660"
Within /etc/modprobe.conf files:
Within any ancient /etc/devfs files:
Alguem pode me ajudar a instala-lo? Pois no windows em dual boot, ele funciona perfeitamente.
Processador: Atlhon 3500+ 64bit
Motherboard: Asus A8V-X
Video: Geforce 5200 LE
Captura de Video: Pinnacle 110i
Modem: Lucent
Enviada: Sáb Dez 16, 2006 3:15 pm Assunto: Resolvi este problema mas apareceu outro.
Coloquei uma opção de inicialização na linha do kernel "pci=conf1", apareceu o modem e a placa de captura atravez do comando "lspci", fiz download e segui os procedimentos descritos em http://martian.barrelsoutofbonf.org, fiz algumas tentativas depois de instalar o modem depois adivinha? Consegui conectar uma vez fiquei um bom tempo conectado mas não consigo mais, simplesmente quando disco para internet o kppp trava, coisa que estava acontecendo antes de eu conseguir também, alguem pode me ajudar neste problema?[/url]