Fedora Core 4

No se por que no habia visto la notificacion de tu pregunta .. como vas ..¿?
Lo primero es que no vas a ver e la montada de XP lo que debes ver son las carpetas y archivos que tienes alla adentro ..
¿Lo otro es que validaste tu version del kernel que estuviera able para hacer eso ..?
Pasame los datos de tu ISP para ver que es lo que estas poniendo o dime que es lo que sale cuando le haces un ifconfig a tu tarjeta ..
El sub portatile deberia reconocertelo apenas lo pones .. no es asi ..¿?

Hola, ya he solucionado lo de las particiones y el usb.
También los del idioma, pero no lo de la targeta inalambrica.
He estado buscando info y me he descargado los controladores del modelo de targetWiFi para linux, teniendo en cuenta el kernel,etc...
viene en un archivo tar que descomprimo pero no so capaz de instalar, he probado a ejecutar el makefile que trae pero me dice que no engo permisos, lo he intentado como root, y le he dado todos los permisos a todos los archivos del paquete pero me sigue diciendo lo mismo, seguramente lo esté haciendo mal porque es lo primero que instalo en linux desde terminal.
Alguna idea de lo que estoy haciendo mal?
Gracias de nuevo por todo.

ahí van los nombres de los archivos:
CHANGES
INSTALL (archivo de texto)
LICENSE
README.ipw2200
idvals
ieee80211_crypt.c
ieee80211_crypt_ccmp.c
ieee80211_crypt_wep.c
ieee80211_rx.c
ieee80211_wx.c
ipw2200.h
unload
FILES
ISSUES
Makefile
dvals
ieee80211.h
ieee80211_crypt.h
ieee80211_crypt_tkip.c
ieee80211_module.c
ieee80211_tx.c
ipw2200.c
load

Cuentame el listaod de cosas que se descomprimieron del tar .. así tendré una mejor idea de que tienes ..
Por si lo estas haciendo como root no deberías tener porblemas ..
¿Qué permisos le estás poniendo 755 ..?

¿Tienes 755 para todos esos files .?
Then que dice el readme ..¿?
Normalmente estas cosas son make luego make install
en el archivo readme o en install debe haber algunos datyos interesantes de que es lo que debes correr primero o si te hace falta algo para correr ..
http://intercentres.cult.gva.es/cefire/12400551/asesorias/informat/manual-knoppix/x1068.html
Dale un chamod + 755 a toda la carpeta de esos files yu verifica con ls -lah como quedaron ..
Deben haber quedado asi
Drwxrwxrwx

Perdona por la tardanza, toi un poco liado.
Sí, le he dado a todos los archivos 755.
El readme está en inglés, lo he leido por encima pero no me aclaro, si quieres te lo copio aki a ver si sacas algo en claro.
Desde terminal me dice que todos los archivo tienen:
-rwxr-xr-x
¿esto se correspone con 755?
Bueno muchas gracias por tu interes en ayudarme. Un saludo.javiR

Pegame el readme para ver que le encontramos .. siempre son de gran ayuda ..
Eso es 655 por que 755 son todos
-Rwxrwxrwx
Osea
- ( No es directorio )
R : read ( lectura )
w : write ( escritura )
X : execute ( ejecución )
Estos son los tres tipos de permiso que se dan para usuarios, grupos, o todos ..

Ok vamos por partes.
¿Ti tienes el kernal 2.6.8 + right .?
¿Ya has hecho un modproble para ver si hay modulos instalados .?
$ modprobe ipw2200
Leyendo me encontré este manual paso a paso ..
http://www.aei.mpg.de/~pau/amilo_1425_linux_en.html
Y este para inslar los RPM ( muuuuchoooo más facil )
y este rpm que es una herramienta para trabjar con las tarjetas wireless ..
dime como teva ..
http://rpmfind.net/linux/RPM/suse/9.3/i386/suse/i586/wireless-tools-28pre4-16.2.i586.html

Y EN EL INSTAL PONE ESTO:
Intel PRO/Wireless 2200BG and 2915ABG Linux Driver
Copyright (C) 2004, Intel Corporation
For additional information, contact James Ketrenos <[email protected]>
NOTE ON UPGRADING FROM PRIOR VERSIONS
--------- ------ ---- --- -- -- - -
Whenever you upgrade your driver, you need to make sure that your system
no longer has older versions of the modules in various locations that
could be found by modprobe instead of the new version. If you see
problems about unresolved symbols, chances are good you have an old
module someplace. You can typically find the offending modules via:
% for i in ieee80211 ipw2200; do \
find /lib/modules/`uname -r` -iname ${i}*; done
And then you can go and remove whatever that finds.
You should also check your kernel's configuration for any old declrations
from old installs:
% for i in IEEE80211 IPW; do \
% grep CONFIG_${i} \
/lib/modules/`uname -r`/build/include/linux/autoconf.h
KERNEL REQUIREMENTS - 2.6
--------- ------ ---- --- -- -- - -
This driver is currently a 2.6 only driver. Due to time
constraints, we can not maintain a 2.4 backport of the driver.
If you would like to assist in this and maintain 2.4 backports,
please let us know.
INSTALLING THE BITS
------------ ----- ----- ---- --- -- -
Before installing ipw2200.ko, both firmware_class and ieee80211 need to
be installed first. For now the ieee80211 module code is included with
the ipw2200 code, so building and installing the ipw2200 should enable
you to:
$ modprobe ipw2200
Or... you can modprobe ieee80211 and firmware_class first, and then manually
insmod your build of ipw2200.ko
KERNEL REQUIREMENTS - Crypto Library
---------- -------- --------- ----- ----- --- -- -
IPW2200 uses the WEP encryption and decryption algorimths provided
by the Linux kernel. As such, in order to use WEP you must enable the
Crypto library support (CONFIG_CRYPTO) and the following algorithms:
ARC4 cipher algorithm (CONFIG_CRYPTO_ARC4)
You also need to enable the following from Library routines:
CRC32 (CONFIG_CRC32)
BUILDING EXTERNAL
----------- ----- ---- ---- --- -- - -
First, you need to unpack the source code:
% tar xzvf ipw2200-1.0.0.tgz
% cd ipw2200-1.0.0
The driver package contains a Makefile that can be used for building the driver
outside of the kernel tree. To build it for the currently running kernel,
simply type:
% make
NOTE: If you see any errors during the build process be sure to check the
Issues section on the http://ipw2200.sf.net website as a patch may be available
for your specific kernel configuration.
To build it for a different kernel than the running one, use the KSRC
parameter:
% make KSRC=/path/to/kernel
BUILDING IN THE KERNEL SOURCE TREE
-------- ------ ----- ---- --- --- -- - -
Not supported at this time.
CONFIGURING THE KERNEL
------------ ----- ----- ---- --- -- -
You need to enable firmware loading
The kernel must be configured to enable wireless capabilities
(CONFIG_NET_RADIO=y).
Failure to do this will result in the Wireless Tools (iwconfig, iwlist,
etc.) not functioning.
You can check if your kernel is configured with CONFIG_NET_RADIO by
running:
% grep CONFIG_NET_RADIO \
/lib/modules/`uname -r`/build/include/linux/autoconf.h
You should see the line:
#define CONFIG_NET_RADIO 1
If you have to turn on CONFIG_NET_RADIO in your kernel configuration, make
sure you also rebuild, install, and reboot to the new kernel image. For help
or instructions on configuring and building the kernel please consult the
documentation contained in your distribution.
You also need to enable the firmware loading capabilities of hotplug.
Do do this, see below.
LOADING FIRMWARE VIA HOT-PLUG
------- ---- -- - - -
Before you can load the driver, you need the firmware image. You can find
instructions for obtaining the firmware by going to
http://ipw2200.sf.net/firmware.php.
Once you have the firmware, unzip the archive. You should find five
files within it:
LICENSE A copy of the firmware license
ipw2200_boot.fw Boot strap image
ipw2200_bss.fw BSS mode
ipw2200_ibss.fw IBSS mode
ipw2200_ucode.fw Used by BSS and IBSS mode
You need to place all of these files into the hotplug firmware directory
(typically /usr/lib/hotplug/firmware/ -- check the contents of the
/etc/hotplug/firmware.agent to determine the specific location for your
distribution)
NOTE: Loading the firmware image will not affect the IPW2200 in any other
operating systems you may boot. The firmware is loaded onto the hardware
every time the card is initialized--regardless of the operating system.
The IPW2200 supports loading of firmware via the Linux firmware hotplug
capability. In order to use this, you must enable CONFIG_FW_LOADER in
your kernel configuration. In 2.6.x this option is enabled via:
Device Drivers ->
Generic Driver Options ->
Hotplug firmware loading support
In addition, you will need the Linux hotplug scripts dated later than
2003_10_07 (if you do not have /etc/hotplug/firmware.agent then you need
to upgrade).
You will also need to have sysfs mounted. You can do this by adding an
entry to /etc/fstab similar to this:
none /sys sysfs defaults 0 0
If the directory /sys does not already exist, you will need to create it:
% mkdir /sys
You can then mount the sysfs partition via:
% mount -a
You can obtain the latest hotplug scripts via the following link:
http://sourceforge.net/project/showfiles.php?group_id=17679
LOADING THE DRIVER
------------ ----- ----- ---- --- -- -
Loading the driver (as root):
% . load
Unloading the driver (as root):
% . unload
The above scripts will allow you to load the required modules without
performing a make install. If you do a make install, then you can load the
driver by simply running (as root):
% modprobe ipw2200
INSTALLING IN YOUR DISTRIBUTION
------------ ----- ----- ---- --- -- -
As the specifics for each distribution varies, we can not cover the
steps required to install and configure your device for the distribution
being used.
Please refer to the documentation for your distribution on issues
related to auto-detection and installation of the driver within your
environment.

Intel PRO/Wireless 2200 802.11bg Driver for Linux
README.ipw2200
1.0.0
January 31, 2005
NOTE: As of January 31, this is a preliminary README.ipw2200
incorporated into the intial 1.0.0 snapshot made available on SourceForge.
Index
-----------------------------------------------
1. Introduction
1.1. Overview of features
1.2. Module parameters
1.3. Wireless Extension Private Methods
1.4. Sysfs Helper Files
2. Introduction to Wireless
2.1 Infrastructure mode (aka BSS, Managed)
2.2 Ad-Hoc mode (aka IBSS, Independent)
3. Working with your distribution
4. Working with Open Source Software
5. Support
6. License
1. Introduction
-----------------------------------------------
The following sections attempt to provide a brief introduction to using
the Intel PRO/Wireless 2200 and 2915 Network Connection Adapters on
Linux. This document is not meant to be a comprehensive manual on
understanding or using wireless technologies, but should be sufficient
to get you moving without wires on Linux.
1.1. Overview of Features
-----------------------------------------------
The current release (1.0.0) supports the following features:
+ BSS mode (Infrastructure, Managed)
+ IBSS mode (Ad-Hoc)
+ WEP (OPEN and SHARED KEY mode)
+ 802.1x EAP via wpa_supplicant and xsupplicant
+ Wireless Extension support
+ long/short preamble support
+ Full B and G rate support (2200 and 2915)
+ Full A rate support (2915 only)
+ Transmit power control
+ S state support (ACPI suspend/resume)
1.2. Command Line Parameters
-----------------------------------------------
Like many modules used in the Linux kernel, the ipw2200 driver allows
certian configuration options to be provided as module parameters. The
most common way to specify a module parameter is via the command line.
The general form is:
% modprobe ipw2200 parameter=value
Where the supported parameter are:
associate
Set to 0 to disable the auto scan-and-associate functionality of the
driver. If disabled, the driver will not attempt to scan
for and associate to a network until it has been configured with
one or more properties for the target network, for example configuring
the network SSID. Default is 1 (auto-associate)
Example: % modprobe ipw2200 associate=0
auto_create
Set to 0 to disable the auto creation of an Ad-Hoc network
matching the channel and network name parameters provided.
Default is 1.
channel
channel number for association. The normal method for setting
the channel would be to use the standard wireless tools
(i.e. `iwconfig eth1 channel 10`), but it is useful sometimes
to set this while debugging. Channel 0 means 'ANY'
debug
If using a debug build, this is used to control the amount of debug
info is logged. See the 'dval' and 'load' script for more info on
how to use this (the dval and load scripts are provided as part
of the ipw2200 development snapshot releases available from the
SourceForge project at http://ipw2200.sf.net)
ifname
Can be used to override the default interface name of eth%. For
example:
modprobe ipw2200 ifname=wlan%d
You can also specify a specific interface number -- be warned
that if that number conflicts with an already assigned interface
the driver will not load correctly.
mode
Can be used to set the default mode of the adapter.
0 = Managed, 1 = Ad-Hoc
1.3. Wireless Extension Private Methods
-----------------------------------------------
As an interface designed to handle generic hardware, there are certain
capabilities not exposed through the normal Wireless Tool interface. As
such, a provision is provided for a driver to declare custom, or
private, methods. The ipw2200 defines several of these to configure
various settings.
The general form of using the private wireless methods is:
% iwpriv 6988IFNAME method parameters
Where 6988IFNAME is the interface name the device is registered with
(typically eth1, customized via the ifname module parameter or one of
the various network interface name managers, such as ifrename and
ifname)
The supported private methods are:
get_mode
Can be used to report out which IEEE mode the driver is
configured to support. Example:
% iwpriv eth1 get_mode
eth1 get_mode:802.11bg (6)
set_mode
Can be used to configure which IEEE mode the driver will
support.
Usage:
% iwpriv eth1 set_mode {mode}
Where {mode} is a number in the range 1-7:
1 802.11a (2915 only)
2 802.11b
3 802.11ab (2915 only)
4 802.11g
5 802.11ag (2915 only)
6 802.11bg
7 802.11abg (2915 only)
1.4. Sysfs Helper Files:
-----------------------------------------------
The Linux kernel provides a pseudo file system that can be used to
access various components of the operating system. The ipw2200 driver
exposes several configuration parameters through this mechanism.
An entry in the sysfs can support reading and/or writing. You can
typically query the contents of a sysfs entry through the use of cat,
and can set the contents via echo. For example:
% cat /sys/bus/pci/drivers/ipw2200/debug_level
Will report the current debug level of the driver's logging subsystem
(only available if CONFIG_IPW_DEBUG was configured when the driver was
built).
You can set the debug level via:
% echo 6988VALUE > /sys/bus/pci/drivers/ipw2200/debug_level
Where 6988VALUE would be a number in the case of this sysfs entry. The
input to sysfs files does not have to be a number. For example, the
firmware loader used by hotplug utilizes sysfs entries for transfering
the firmware image from user space into the driver.
The ipw2200 exposes sysfs entries at two levels -- driver level, which
apply to all instances of the driver (in the event that there are more
than one device installed) and device level, which applies only to the
single specific instance.
1.4.1 Driver Level Sysfs Helper Files
-----------------------------------------------
For the driver level files, look in /sys/bus/pci/drivers/ipw2200/
debug_level
This controls the same global as the 'debug' module parameter
1.4.2 Device Level Sysfs Helper Files
-----------------------------------------------
For the device level files, look in
/sys/bus/pci/drivers/ipw2200/{PCI-ID}/
For example:
/sys/bus/pci/drivers/ipw2200/0000:02:01.0
For the device level files, see /sys/bus/pci/[drivers/ipw2200:
command_event_reg
read access to the the Command Event register
eeprom
reading from this fill will cause our private copy of the
contents of the EEPROM to be flushed to the log
eeprom_sram
reading this file will behave like the 'eeprom' file, except
that instead of pulling from the device's cached copy of the
eeprom data, the region of the device's sram that should
hold eeprom data is dumped.
eeprom_clear
reading from this file will cause the eeprom info in sram to be
cleared.
error_log
reading this file will cause the contents of the device's error
log to be flushed to our log. normally the event_log is empty,
but if the device's fw get's into an odd state, this log contains
some hints.
fw_date
read-only access to the firmware release date
fw_version
read-only access to the firmware release version
rf_kill
read -
0 = RF kill not enabled (radio on)
1 = SW based RF kill active (radio off)
2 = HW based RF kill active (radio off)
3 = Both HW and SW RF kill active (radio off)
write -
0 = If SW based RF kill active, turn the radio back on
1 = If radio is on, activate SW based RF kill
NOTE: If you enable the SW based RF kill and then toggle the HW
based RF kill from ON -> OFF -> ON, the radio will NOT come back on
ucode
read-only access to the ucode version number
rtc
read-only access the the device's real-time clock
[in]direct_byte
[in]direct_word
enables read-only access to the device's sram by first writing
the address of the data to read, and then reading from the file
will return the word/byte the address points to.
5. Support
-----------------------------------------------
For general information and support, go to:
http://ipw2200.sf.net/
6. License
-----------------------------------------------
Copyright(c) 2003 - 2004 Intel Corporation. All rights reserved.
This program is free software; you can redistribute it and/or modify it
under the terms of the GNU General Public License version 2 as
published by the Free Software Foundation.
This program is distributed in the hope that it will be useful, but WITHOUT
ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for
more details.
You should have received a copy of the GNU General Public License along with
this program; if not, write to the Free Software Foundation, Inc., 59
Temple Place - Suite 330, Boston, MA 02111-1307, USA.
The full GNU General Public License is included in this distribution in the
file called LICENSE.
Contact Information:
James P. Ketrenos <[email protected]>
Intel Corporation, 5200 N.E. Elam Young Parkway, Hillsboro, OR 97124-6497

Bueno el kernel es 2.6.13-1.1532_FC4,
este paquete funciona solo para el 2.6.8 o para todos los 2.6....?
Bueno he mirado en la pagina donde descargué el paquete y solo encuentro esta versión estable.
Probé el modprobe pero me dice que no encuentra el comando.
En cuanto al manual paso a paso, no se si es problema del navegador pero no me finciona el linck.
La herramienta para trabajar con las wireless ya la tego instalada, esta es una versión más reciente y se ha actualizado al instalarla.
En FC4 los rpm se instalan con solo hacer doble click sobre el paquete, que lujo, jaja.
Entonces que crees que puedo hacer?

Vamos pasito a pasito .. +
Hecha a andar el modprobe y mira a ver que modulos ( si es que acaso tienes ) instalados ..