could you please upload the drivers? thanks

drivers are included in kernel-power v47 for N900

i have tried for weeks to compile this driver for N900 and nothing. thanks very much you, PALI you are my hero, my god!!

I have conected via HEN my Alfa 1 w, and in the kelnel messages recognized the RTL8187 driver, but how do i get to work the N900 with the Alpha instead with the internal wifi card of the N900 ??

If i type in x terminal: airmon-ng only recognize the interface wlan0 with the w112xx driver, nothing else.

do i have rmmod the w112xx driver or something??

set up your RTL8187 device in usb host mode and then send output of command iwconfig (run as root)

if i type iwconfig

/home/user # iwconfig
lo no wireless extensions.

wmaster0 no wireless extensions.

wlan0 IEEE 802.11bg ESSID:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Tx-Power=0 dBm
Retry min limit:7 RTS thrff Fragment thr=2352 B
Encryption keyff
Power Managementff
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

phonet0 no wireless extensions.

if i type airmon-ng:

home/user # airmon-ng

Interface Chipset Driver

wlan0 Unknown wl12xx - [phy0]

if i type ifconfig:

/home/user # ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:235 errors:0 dropped:0 overruns:0 frame:0
TX packets:235 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:13992 (13.6 KiB) TX bytes:13992 (13.6 KiB)

phonet0 Link encap:UNSPEC HWaddr 15-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
UP POINTOPOINT RUNNING NOARP MTU:4000 Metric:1
RX packets:352 errors:0 dropped:0 overruns:0 frame:0
TX packets:212 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:13380 (13.0 KiB) TX bytes:5256 (5.1 KiB)

wlan0 Link encap:Ethernet HWaddr D8:**:**:**:**:**
inet addr:192.168.1.*** Bcast:192.168.1.*** Mask:255.255.255.0
inet6 addr: fe**::da**:**ff:fe**:**d/** Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:749 errors:0 dropped:0 overruns:0 frame:0
TX packets:769 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:863304 (843.0 KiB) TX bytes:200813 (196.1 KiB)

wmaster0 Link encap:UNSPEC HWaddr 00-1F-**-**-**-**-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

kernel messages:

1959.309020] /home/builder1/maemo-fremantle-armel-extras-devel/work/kernel-power-2.6.28/drivers/usb/core/inode.c: creating file '045'
[ 1959.309692] usb 1-1: New USB device found, idVendor=0bda, idProduct=8187
[ 1959.309753] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1959.309783] usb 1-1: Product: RTL8187_Wireless
[ 1959.309814] usb 1-1: Manufacturer: Manufacturer_Realtek_RTL8187_
[ 1959.309844] usb 1-1: SerialNumber: 00C0CA******
[ 1959.309875] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002
[ 1959.309967] hub 1-0:1.0: port 1 enable change, status 00000503

Maybe i am doing something wrong? i with HEN mode i have to put the device?? high speed hostmode or full speed hostmode?

Kernel does not see your second wifi card (not shown in iwconfig). This may be because kernel module is not loaded or your device is not supported...

Does your wifi card work on linux desktop?

well I have the same, kernel messages "see" the device but its not showing up as wireless extension =/ and my wireless card works with a linux desktop pc(ubuntu 10.10)

try load rtl kernel module manualy.

iwconfig doesn't show it, but why HEN kernel messages recognice it??

my wifi card is the famous alfa awus036h 1000 mw, works in any linux desktop i have proved, and i prove it in a lot of linux distros: ubuntu, linux mint, debian, backtrack...

The driver isn't loading and taking control of the device. Manually modprobe/insmod after syslog reports it's connected and see what dmesg spits out.