[Announce] bleeding-edge wl1251 wifi driver for Maemo Fremantle - Page 38 - maemo.org

Active Topics

Camera phone competition March 2023 "Endless" (35)
to General by Maemish - 1 day, 22 hrs ago
TLS 1.2 for N9 is ready (28)
to MeeGo / Harmattan by smartblu9 - 1 day, 23 hrs ago
Maemo repository (3)
to Community by torsen - 2 days, 15 hrs ago
Error after installing Leste on sdcard (11)
to Maemo 7 / Leste by Maemish - 3 days, 13 hrs ago
Introducing ubiboot N9 (multiboot OS loader) (1,393)
to Alternatives by smatkovi - 4 days, 19 hrs ago
more...

Page 38 of 53

Thread Tools

stlpaul	2011-03-18 , 15:12
Posts: 1,141 \| Thanked: 781 times \| Joined on Dec 2009 @ Magical Unicorn Land	#371

When using these drivers for normal wifi operations it sometimes crashes and wifi doesn't work until i reload the drivers. I cannot reproduce it and it seems to happen randomly and infrequently. dmesg showed this when it occurred just now:

Code:

[ 1806.541778] ------------[ cut here ]------------
[ 1806.541839] WARNING: at /home/r00t/MyDocs/compat-wireless-2.6/net/wireless/core.c:645 wdev_cleanup_work+0x60/0xf0 [cfg80211]()
[ 1806.541839] Modules linked in: ext2 tun pn_pep wl1251_spi wl1251 mac80211 cfg80211 rfkill_backport compat lirc_rx51 lirc_dev vfat fat sd_mod scsi_mod iphb rfcomm panic_info_buff sco l2cap ext3 jbd omaplfb pvrsrvkm bridgedriver ipv6 g_file_storage uinput board_rx51_camera et8ek8 omap_previewer_hack omap34xxcam_mod isp_mod iovmm videobuf_dma_sg videobuf_core omap3_iommu iommu2 iommu dspbridge ssi_mcsaab_imp mmc_block phonet omap_hsmmc cmt_speech joydev hci_h4p smc91x mii crc7 omap_ssi omap_wdt mmc_core nokia_av tsc2005 bluetooth fmtx_si4713 adp1653 ad5820 smia_sensor rtc_twl4030 leds_twl4030_vibra lis302dl smiaregs videodev v4l1_compat compat_ioctl32 tsl2563 twl4030_wdt leds_lp5523 led_class rtc_core v4l2_int_device [last unloaded: cfg80211]
[ 1806.542175] [<c0030470>] (dump_stack+0x0/0x14) from [<c00574ac>] (warn_on_slowpath+0x4c/0x68)
[ 1806.542724] [<c0057460>] (warn_on_slowpath+0x0/0x68) from [<bf3303b4>] (wdev_cleanup_work+0x60/0xf0 [cfg80211])
[ 1806.542846]  r6:ce6980c0 r5:ce698000 r4:c64c63d0
[ 1806.542877] [<bf330354>] (wdev_cleanup_work+0x0/0xf0 [cfg80211]) from [<c0069a6c>] (run_workqueue+0xd4/0x198)
[ 1806.542999]  r9:00000000 r8:bf330354 r7:c64c63d0 r6:cff54640 r5:cfc36000
[ 1806.543029] r4:c64c63d4
[ 1806.543029] [<c0069998>] (run_workqueue+0x0/0x198) from [<c006a80c>] (worker_thread+0xf0/0x104)
[ 1806.543060]  r9:00000000 r8:00000000 r7:cff54640 r6:cfc36000 r5:c9d60f00
[ 1806.543090] r4:cfc37fb8
[ 1806.543121] [<c006a71c>] (worker_thread+0x0/0x104) from [<c006da90>] (kthread+0x54/0x80)
[ 1806.543151]  r7:00000000 r6:00000000 r5:c006a71c r4:cff54640
[ 1806.543182] [<c006da3c>] (kthread+0x0/0x80) from [<c005a950>] (do_exit+0x0/0x7bc)
[ 1806.543212]  r5:00000000 r4:00000000
[ 1806.543243] ---[ end trace e1c47d2c59bbb4f0 ]---
[ 1806.543395] ------------[ cut here ]------------
[ 1806.543426] WARNING: at /home/r00t/MyDocs/compat-wireless-2.6/net/wireless/scan.c:89 cfg80211_scan_done+0x40/0x7c [cfg80211]()
[ 1806.543426] Modules linked in: ext2 tun pn_pep wl1251_spi wl1251 mac80211 cfg80211 rfkill_backport compat lirc_rx51 lirc_dev vfat fat sd_mod scsi_mod iphb rfcomm panic_info_buff sco l2cap ext3 jbd omaplfb pvrsrvkm bridgedriver ipv6 g_file_storage uinput board_rx51_camera et8ek8 omap_previewer_hack omap34xxcam_mod isp_mod iovmm videobuf_dma_sg videobuf_core omap3_iommu iommu2 iommu dspbridge ssi_mcsaab_imp mmc_block phonet omap_hsmmc cmt_speech joydev hci_h4p smc91x mii crc7 omap_ssi omap_wdt mmc_core nokia_av tsc2005 bluetooth fmtx_si4713 adp1653 ad5820 smia_sensor rtc_twl4030 leds_twl4030_vibra lis302dl smiaregs videodev v4l1_compat compat_ioctl32 tsl2563 twl4030_wdt leds_lp5523 led_class rtc_core v4l2_int_device [last unloaded: cfg80211]
[ 1806.543731] [<c0030470>] (dump_stack+0x0/0x14) from [<c00574ac>] (warn_on_slowpath+0x4c/0x68)
[ 1806.543792] [<c0057460>] (warn_on_slowpath+0x0/0x68) from [<bf335424>] (cfg80211_scan_done+0x40/0x7c [cfg80211])
[ 1806.543884]  r6:00000001 r5:00000001 r4:c5182900
[ 1806.543914] [<bf3353e4>] (cfg80211_scan_done+0x0/0x7c [cfg80211]) from [<bf35ea24>] (__ieee80211_scan_completed+0xd0/0xec [mac80211])
[ 1806.545257]  r5:00000000 r4:ce698280
[ 1806.545288] [<bf35e954>] (__ieee80211_scan_completed+0x0/0xec [mac80211]) from [<bf35f690>] (ieee80211_scan_work+0x440/0x480 [mac80211])
[ 1806.545532]  r7:ce698914 r6:ce698280 r5:00000001 r4:ce698914
[ 1806.545562] [<bf35f250>] (ieee80211_scan_work+0x0/0x480 [mac80211]) from [<c0069a6c>] (run_workqueue+0xd4/0x198)
[ 1806.545684] [<c0069998>] (run_workqueue+0x0/0x198) from [<c006a80c>] (worker_thread+0xf0/0x104)
[ 1806.545715]  r9:00000000 r8:00000000 r7:cfc86140 r6:ce704000 r5:c9d60000
[ 1806.545745] r4:ce705fb8
[ 1806.545745] [<c006a71c>] (worker_thread+0x0/0x104) from [<c006da90>] (kthread+0x54/0x80)
[ 1806.545776]  r7:00000000 r6:00000000 r5:c006a71c r4:cfc86140
[ 1806.545806] [<c006da3c>] (kthread+0x0/0x80) from [<c005a950>] (do_exit+0x0/0x7bc)
[ 1806.545837]  r5:00000000 r4:00000000
[ 1806.545867] ---[ end trace e1c47d2c59bbb4f0 ]---

I don't know if that's showing the reason for the wifi dying or just something broken as a result of it.

Quote & Reply |

Mentalist Traceur	2011-03-18 , 19:00
Posts: 2,225 \| Thanked: 3,822 times \| Joined on Jun 2010 @ Florida	#372

stlpaul - did you also install the osso-wlan fix? Other than that, I think I have had one or two similar problems, but it's very very rare for me. I typically use the bleeding edge driver as my default wifi driver anyway.

Quote & Reply |

tehowe	2011-03-25 , 19:54
Posts: 45 \| Thanked: 5 times \| Joined on Oct 2008	#373

I've used this with no problems in the past... however now when I attempt to

Code:

sh load.sh

the following errors are returned...

Code:

insmod: error inserting 'cfg80211.ko': -1 invalid parameters
insmod: error inserting 'mac80211.ko': -1 Unknown symbol in module
insmod: error inserting 'wl1251.ko': -1 Unknown symbol in module
insmod: error inserting 'wl1251_spi.ko': -1 Unknown symbol in module
ifconfig: SIOCGIFFLAGS: No such device

The same messages are returned if I attempt loading the driver through the FAS script

Argh! What did I do? Your help is appreciated.

Edit: Note, I am running the required modified kernel at 2.6.28.20power46 as the Conky application puts it... sudser & aircrack, etc packages are installed.

Last edited by tehowe; 2011-03-26 at 01:57.

Quote & Reply |

zitstif	2011-04-02 , 01:15
Posts: 24 \| Thanked: 26 times \| Joined on Feb 2011	#374

tehowe, try doing this before you run load.sh

Make sure you're not connected to any ap point and do this:

Code:

ifconfig wlan0 down

Also make sure you're running the load.sh from the directory that contains those files.

Quote & Reply |

The Following User Says Thank You to zitstif For This Useful Post:
tehowe

tehowe	2011-04-05 , 11:44
Posts: 45 \| Thanked: 5 times \| Joined on Oct 2008	#375

Originally Posted by zitstif

tehowe, try doing this before you run load.sh

Make sure you're not connected to any ap point and do this:
Code:
ifconfig wlan0 down
Also make sure you're running the load.sh from the directory that contains those files.

Didn't work. I did however see it complain about an additional two insmod insertion errors: compat.ko and rfkill_backport.ko, when I ran load.sh (from its native directory).

Running sudo sh load.sh had it back to the set of errors I posted above.

Removing the wl1251 package and 'reinstalling' it isn't going to be a solution since the problem doesn't appear to be missing or damaged files... would reflashing the power kernel make any sense? Not sure where the solution to this one lies.

Quote & Reply |

Tigerite	2011-04-06 , 21:19
Posts: 284 \| Thanked: 320 times \| Joined on May 2010 @ Peterborough, UK	#376

It's in the kernel - those messages occur because it can't insert the modules due to header and/or version mismatch. Are you using the default power46, or the modified one posted by lxp? I would assume the former based on the errors.

Quote & Reply |

The Following User Says Thank You to Tigerite For This Useful Post:
tehowe

	windows7	2011-04-06 , 21:49
	Posts: 435 \| Thanked: 160 times \| Joined on Dec 2009	#377

This does not work! I have given up.

__________________
http://www.speedtest.net/result/999667849.png
_________________________________________
Royality free icons for web and software developers

QT Training Videos

BleachBit : cleans unnecessary files to free disk space and maintain privacy

How to edit & modify desktop shortcuts manually

Check out the n900 power here!

maemo.org power search

Quote & Reply |

tehowe	2011-04-07 , 00:20
Posts: 45 \| Thanked: 5 times \| Joined on Oct 2008	#378

Originally Posted by Tigerite

It's in the kernel - those messages occur because it can't insert the modules due to header and/or version mismatch. Are you using the default power46, or the modified one posted by lxp? I would assume the former based on the errors.

Yes... I discovered this today and must fess up, mea culpa. This is what comes of rushing to reinstall absolutely everything in a day when your N900 throws a memory fault - I neglected to unpackage the modules, headers, flash patch etc this time around, and simply copied the directory into place. So, if you're doing this for the first time don't skip this step either after you untar the files...

Code:

* Gain root access

    ~/MyDocs$ sudo gainroot

  * Install customized power kernel

    # cd wl1251-maemo/binary/kernel-power
    # dpkg -i kernel-power_2.6.28-maemo46-wl1_armel.deb
    # dpkg -i kernel-power-headers_2.6.28-maemo46-wl1_armel.deb
    # dpkg -i kernel-power-modules_2.6.28-maemo46-wl1_armel.deb
    # dpkg -i kernel-power-flasher_2.6.28-maemo46-wl1_armel.deb

Quote & Reply |

stlpaul	2011-04-07 , 03:52
Posts: 1,141 \| Thanked: 781 times \| Joined on Dec 2009 @ Magical Unicorn Land	#379

Originally Posted by Mentalist Traceur

stlpaul - did you also install the osso-wlan fix? Other than that, I think I have had one or two similar problems, but it's very very rare for me. I typically use the bleeding edge driver as my default wifi driver anyway.

Yeah. It also has a habit of not realizing I'm out of wifi range. For example I'll leave home, and an hour later it still thinks I'm connected to my home wifi network. It doesn't happen every time, but every once in a while. It's not a big deal.

Quote & Reply |

RedMatterInc	2011-04-11 , 02:10
Posts: 6 \| Thanked: 2 times \| Joined on Jan 2011	#380

Originally Posted by stlpaul

Yeah. It also has a habit of not realizing I'm out of wifi range. For example I'll leave home, and an hour later it still thinks I'm connected to my home wifi network. It doesn't happen every time, but every once in a while. It's not a big deal.

Sounds like it might be the same bug that I'm running into when trying to inject lots of packets. Aside from injection, it works fine, but it's a drag to have to wait for packets especially given the fact that I'm almost always working off battery power.

I did manage to get gcc, g++ and gdb installed on the N900, however the SDK for maemo 5 doesn't seem to like my desktop nor my laptop (presumably because it warns me that 64-bit is unsupported but gives me the option to try anyway). Unfortunately, this project has now fallen to the back burner since I don't have time to learn about debugging on the N900 (which I'm told is different than debugging on anything else), to get a core file, where to start putting debugging statements in the code, etc. I might get to it one of these days, but don't hold your breath.