Sorry, mea culpa, mea culpa, it was all my own fault!
I somehow mixed up zImage-su-18-200625-2gb-mmcplus52Mhz and zImage-su-18-200639-2gb-mmcplus52Mhz When I reported the problem, I was running *200625* on 2.2006.39-14, which indeed fails to load cx3110x and umac... Everything is fine with *200639* on 2.2006.39-14. Thanks, Frantisek! regards, Armin. On 11/28/06, Larry Battraw <[EMAIL PROTECTED]> wrote:
Actually, I noticed the same thing although I'll have to go back and make sure it wasn't all of the kernels that had problems with WEP. I was never able to get it working although WPA is fine. Larry On 11/28/06, Frantisek Dufka <[EMAIL PROTECTED]> wrote: > Armin M. Warda wrote: > > I repeated the test three times, the result was always reproduced. > > > > regards, Armin. > > > > Huh, that's weird. wi-fi driver and 802.11 protocol is even not in > kernel but in extra module. The only changes in that kernel are: > 1 extended backlight control (patch on my site) > 2 high speed mmc patch (on my site) > 3 kernel has enabled crypto API (disabled in nokia build) for PPTP module > > Any dmesg errors while connecting? Are you running correct IT2006 > version for the kernel (i.e. not running older 1.2006 with disabled > lifeguard or watchdog by chance)? Are you booting otherwise same systems > (preferably from flash)? > > Works for me fine with WPA with Asus WL-500G deluxe. > Just also flashed that kernel and tried also ad-hoc WEP conection with > my notebook and it works too. > > I simply don't have any idea why it should affect wi-fi network at all > except when possibly using with older IT2006 from July (so the cx3110x > and umac modules cannot load) which normally causes reboot loop. > > Frantisek
_______________________________________________ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
