linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: George <george.news@gmx.net>
To: linux-wireless@vger.kernel.org
Subject: Compat-wireless N900
Date: Thu, 14 Oct 2010 10:24:55 +0200	[thread overview]
Message-ID: <4CB6BE57.8010401@gmx.net> (raw)

Hi all,

I'm trying to use compat-wireless to upgrade my n900 wireless driver. 
N900 is using WL1251 wireless driver and the omap1 kernel version used 
it 2.6.28.

The issue is that 2.6.28 does not have implemented many issues for 
nl80211 netlink family which I wanted to test on my n900.

I have recompiled the kernel to make cfg80211 and mac80211 modules, so I 
can use compat-wireless. After that I have compiled compat-wireless by 
selecting the driver family I need. All done under scratchbox.

# scripts/driver-select wl12xx
# make KLIB=/lib/modules/2.6.28-myversion \
    KMODPATH_ARG=/lib/modules/2.6.28-myversion
# make  KLIB=/lib/modules/2.6.28-myversion \
    KMODPATH_ARG=/lib/modules/2.6.28-myversion install

After that I have installed the new kernel and the drivers in the n900 
and the system starts. `uname -a` reports I'm using my custom kernel.

The problem is that the wireless modules are not working as expected and 
I cannot get access to my wifi networks. Actually bluetooth is not 
working as well, as far as I have tested.

dmesg reports --> http://pastebin.com/xskKcGnE

I have hightlighted the lines that seems to be reflecting what is not 
working. So it seems that on startup it is trying to upload the former 
wl12xx.ko module. Then I decided to manually upload the new modules to 
check them out.

$ sudo gainroot
# modprobe wl1251_spi
# ifconfig -a
---- no wlan0 iface ----
# iwconfig
---- no wireless devices ----

I have also tried with wl1251_sdio driver but I have the same problem. 
dmesg doesn't report any error while uploading these drivers, but I 
don't know why not a new wireless interface is not created.

BTW, the firmware is in /lib/modules/firmware so it is in a place that 
can be found. Do I have to change something?

What files do I need to reconfigure as to get the kernel to point to the 
correct driver upon booting?
How do I create a new wireless interface if the driver is uploaded 
properly but the interface is not created?
Any other issue that you find I'm not doing correctly?

Any help is welcome.

Regards,
George

             reply	other threads:[~2010-10-14  7:41 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-14  8:24 George [this message]
2010-10-14 15:57 ` Compat-wireless N900 Denis 'GNUtoo' Carikli
2010-10-14 17:17   ` Luis R. Rodriguez
2010-10-14 18:09     ` George
2010-10-14 18:03       ` Luis R. Rodriguez
2010-10-15  6:42         ` George
2010-10-15 18:01           ` Luis R. Rodriguez
2010-10-17  9:01             ` George
2010-10-18 16:34               ` George
2010-10-18 17:21                 ` Luis R. Rodriguez
2010-10-18 19:04                   ` George
2010-10-18 18:41                     ` Luciano Coelho
2010-10-18 19:02                       ` Luciano Coelho
2010-10-19  8:12                         ` George
2010-10-19 13:52                           ` Grazvydas Ignotas
2010-10-19 15:16                             ` George
2010-10-19 14:38                               ` Grazvydas Ignotas
2010-10-19 15:52                                 ` George
2010-10-19 15:18                                   ` Grazvydas Ignotas
2010-10-20  7:37                                     ` George
2010-10-20  8:44                                       ` Grazvydas Ignotas
2010-10-20 12:24                                         ` George
2010-10-25  2:03                                       ` Kalle Valo
2010-10-25  8:33                                         ` George
2010-10-19 15:18                               ` George
2010-10-14 17:29   ` George

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4CB6BE57.8010401@gmx.net \
    --to=george.news@gmx.net \
    --cc=linux-wireless@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).