Problema antenna wireless.

Pubblicità

roxnad94

Utente Èlite
Messaggi
3,279
Reazioni
579
Punteggio
75
allora, partiamo dal rpesupposto che di linux so zero. xD


ho appena installato fedora 18 sul mio compaq 2510p, dove ho visto in giro che è pienamente compatibile. infatti non ho nessun tipo di problema, ho smanettato un pochetto, provato el varie applicazioni, e va tutto al meglio... tranne che per la scheda wireless che sembra non esistere.

ho letto che devo utilizzare i driver intel IWL4965, che a quanto pare erano integrati nelle versioni piu vecchie ma non nella 18.

solo che gia è tanto se sono riuscito ad installare chrome, skype e il flash player, che erano nel pacchetto rpm, mentre quelli che ho trovato qui:

iwlegacy - Linux Wireless

sono quelli che mi vengono consigliati per la mia scheda. pero le poche cose che ho installate, le ho installate con un pacchetto rpm ed è stato molto semplice.

qui ho solo un readme, e un file ucode. ho dato un occhiata al readme per vedere cosa fare, ma non è che ci abbia capito molto.

se qualcuno è disponibile a darmi una mano (magari spiegando cosa fa) mi sarebbe molto d'aiuto =D
 
2. INSTALLATION


The iwlwifi-4965 driver will look for the file iwlwifi-4965-2.ucode using the
kernel's firmware_loader infrastructure. In order to function
correctly, you need to have this support enabled in your kernel. When
you configure the kernel, you can find this option in the following
location:


Device Drivers ->
Generic Driver Options ->
Hotplug firmware loading support




You can determine if your kernel currently has firmware loader support
by looking for the CONFIG_FW_LOADER definition on your kernel's
.config.


In addition to having the firmware_loader support in your kernel, you
must also have a working hotplug and udev infrastructure configured.
The steps for installing and configuring hotplug and udev are very
distribution specific.


Once you have the firmware loader in place (or if you aren't sure and
you just want to try things to see if it works), you need to install
the microcode file into the appropriate location.


Where that appropriate location is depends (again) on your system
distribution. You can typically find this location by looking in the
hotplug configuration file for your distro:


% grep \"^FIRMWARE_DIR\" /etc/hotplug/firmware.agent


This should give you output like:


FIRMWARE_DIR=/lib/firmware


If it lists more than one directory, you only need to put the
microcode in one of them. In the above example, installation is
simply:


% cp iwlwifi-4965-2.ucode /lib/firmware


You can now load the driver (see the INSTALL and README.iwlwifi provided with
the iwlwifi package for information on building and using that driver.)
 
eth0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 ether 00:1e:68:2b:f7:a2 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 22 memory 0xe0600000-e0620000


lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 0 (Local Loopback)
RX packets 4 bytes 276 (276.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 4 bytes 276 (276.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0




qui nemmeno l'ethernet era collegato
 
non che ne capisca molto di quello che ti sto passando, comunque la scheda di rete integrata non penso sia collegata ne in pci ne in usb..


se vado nelle impostazioni di rete, non mi da proprio un opzione wireless, come ho visto dovrebbe succedere, ma solo via cavo.


faccio l'update di qeusto post dal protatile con gli output

- - - Updated - - -

Bus 003 Device 002: ID 03f0:171d Hewlett-Packard Bluetooth 2.0 Interface [Broadcom BCM2045]
Bus 005 Device 002: ID 08ff:2580 AuthenTec, Inc. AES2501 Fingerprint Sensor
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub



00:00.0 Host bridge: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub (rev 0c)
00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) (rev 0c)
00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (secondary) (rev 0c)
00:19.0 Ethernet controller: Intel Corporation 82566MM Gigabit Network Connection (rev 03)
00:1a.0 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #4 (rev 03)
00:1a.1 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 (rev 03)
00:1a.7 USB controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 (rev 03)
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 (rev 03)
00:1c.1 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 2 (rev 03)
00:1d.0 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #1 (rev 03)
00:1d.1 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #2 (rev 03)
00:1d.2 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #3 (rev 03)
00:1d.7 USB controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev f3)
00:1f.0 ISA bridge: Intel Corporation 82801HEM (ICH8M-E) LPC Interface Controller (rev 03)
00:1f.1 IDE interface: Intel Corporation 82801HM/HEM (ICH8M/ICH8M-E) IDE Controller (rev 03)
02:06.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev ba)
02:06.1 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 04)
02:06.2 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 21)
10:00.0 Network controller: Broadcom Corporation BCM4311 802.11a/b/g (rev 02)





mmm gia leggendo qua mi sono accorto della cappellata, come scheda wireless c'è la bcm4311, quindi non servono quei driver ma quelli broadcom.. penso.
 
Pubblicità
Pubblicità
Indietro
Top