Re: ICd2 header files released
Patrik Flykt <[EMAIL PROTECTED]> writes: > Hi, Moi, > It's been a while, but the promised ICd2 header files are released for > Diablo[1]. Very good, I'm glad to see this. Thank you for doing this Patrik. > With the help of the ICd2 header files networks such as USB and BT > PAN can be integrated more tightly into ICd2 without relying on glue > provided by the dummy network. Also it should possible to make a wpa_supplicant icd2 plugin and bypass wlancond/eapd altogether. I think the plugin would be just a simple proxy between icd2 API and wpa_supplicant's d-bus interface. It would be very cool if someone had time to work on that because I don't :/ -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: stlc45xx: open source WLAN driver for N800 and N810
"ext Andrew Zabolotny" <[EMAIL PROTECTED]> writes: > From Tue, 23 Sep 2008 14:46:56 +0300 > Kalle Valo <[EMAIL PROTECTED]> wrote: > >> The discussion on stlc45xx might get very technical (at least I'm >> hoping so) and I doubt that very few people in maemo-developersare >> interested about that. > > As a compromise I would propose to cross-post important > messages/announcements to both lists :-) Sounds good, I'll do that. -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: stlc45xx: open source WLAN driver for N800 and N810
"ext David Greaves" <[EMAIL PROTECTED]> writes: > Kalle Valo wrote: > >> From now on I will not send any more stlc45xx news to >> maemo-developers. Everyone interested should subscribe to >> stlc45xx-devel or follow stlc45xx category from my blog[1]: > > Hi Kalle Hello David, > I'm delighted that you're doing this work - can I ask you to please > continue to post to maemo-developers - there appears to be a lot of > interest and IMO we just don't need the fragmentation at this point. > I don't want to subscribe to yet another list and I won't get round > to following a blog; I suspect I'm not alone. The discussion on stlc45xx might get very technical (at least I'm hoping so) and I doubt that very few people in maemo-developersare interested about that. I don't know how many people are currectly subscribed to maemo-developers, but I would guess that very few of them are really interested in technical aspects of the wlan driver. Most of the people just want the driver to work, they don't care about anything else. > We get a few messages a day - if this was lkml and the flood of > messages drowned you out (or if you intend to flood the list!) then > I'd understand; equally if you were working on something that was > not maemo-specific then it would make sense. The archive for stlc45xx-devel should be open, so you can always check from there what's happening. And if something newsworthy has happened, I can always drop a note to maemo-developers as well. > Otherwise I'd like to see you hang out here :) Don't worry, I'm not going anywhere. I just won't be talking about stlc45xx all the time :) -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: stlc45xx: open source WLAN driver for N800 and N810
"ext Lorn Potter" <[EMAIL PROTECTED]> writes: >> I'm sending this from Helsinki-Vantaa airport on my way to Berlin. I >> will be giving a presentation about stlc45xx at the Maemo Summit on >> Friday 15:00. See you there! > > hopefully these will be recorded for those on the other side of the planet. Luckily my presentation was not recorded :) But I have made the slides available here: http://stlc45xx.garage.maemo.org/stlc45xx-maemo-summit-2008.pdf >From now on I will not send any more stlc45xx news to maemo-developers. Everyone interested should subscribe to stlc45xx-devel or follow stlc45xx category from my blog[1]: http://kvalo.wordpress.com/category/stlc45xx/ [1] Yes, I now have a blog even though I'm old school. Just don't tell my co-workers, otherwise I will be laughed out from the coffee room... -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: stlc45xx: open source WLAN driver for N800 and N810
"ext John Holmblad" <[EMAIL PROTECTED]> writes: > Kalle, John, > thanks for sharing that info. That suggests to me that there may be a > performance security tradeoff when using the N800/N810 with > encryption. Is the software implementation of the AES algorithm fast > enough to be useable without noticing a performance degradation on the > N800? Don't make too fast conclusions :) stlc45xx is work in progress and the reason why TKIP or CCMP is done is software is just that I haven't had the time to implement the hard encryption. It should be relative easily todo, patches welcome :) > I surmise that the use of TKIP (RC4 based) encryption would be > faster although less secure than AES/CCMP. Do you know if there is > any noticeable degradation with AES? No, I haven't seen any measurement results about this. > Also, is the "wpa_supplicant" a standard part of the Nokia OS200X or > is it a maemo garage type of software component? I already answered this one. But here's the link to wpa_supplicant page: http://w1.fi/wpa_supplicant/ -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: stlc45xx: open source WLAN driver for N800 and N810
"ext John Holmblad" <[EMAIL PROTECTED]> writes: > Kalle, Hello John, > I took a look at the OS2008 wireless supplicant and it looks like it > supports WPA and WPA with EAP but I do not see WPA2. eapd (the supplicant in OS2008) does support WPA2. I think the UI just doesn't make a difference between WPA1 and WPA2, there's just a very well hidden "use only WPA2" setting somewhere. > That suggests to me then that the supplicant referred to in this > thread is NOT the standard one. Yes, use of wpa_supplicant in OS2008 needs a patched version of cx3110x. Currently the supplicant is called eapd and made by Nokia. -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: stlc45xx: open source WLAN driver for N800 and N810
ext Raphaël Jacquot <[EMAIL PROTECTED]> writes: > Kalle Valo wrote: >> I'm excited to announce a new project called stlc45xx, an open source >> WLAN driver for Nokia N800 and N810. It's using mac80211 stack >> included in Linux since 2.6.22. Even though I currently classify the >> driver as alpha quality I have managed to transfer 1.2 GB of data with >> iperf. > > great. so I gather we should see a working kismet package rapidely ? The driver is not ready for normal users yet. -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: stlc45xx: open source WLAN driver for N800 and N810
"ext Frantisek Dufka" <[EMAIL PROTECTED]> writes: > Kalle Valo wrote: >> Nokia 770 has stlc4370 and documentation for that chipset is not >> available. I'm not aware of the differences between stlc4370 and the >> newer chips so I cannot say how much work there is needed to get the >> driver working in 770. > > Not good :-( Yeah, I know. > But still, the driver talks to the firmware and so far you were > shipping both (3825/3826.arm) firmwares together so I hoped they > offer same API when accessed over SPI. Let's hope so. > Or do you have some special and different 3826.arm firmware now for > open source driver? There is no separate firmware, stlc45xx uses the same firmware as cx3110x/umac combination. > Or is the difference in umac.ko for 770 vs N8x0? I hope not, I think > Poky people were succesfull with 2.6.18 kernel and umac.ko for N800 > runing on 770. So can we take the firmware as working black box > offering same functionality for both chips? I can't comment on this. This is also a bit grey area for me because the documentation covers only stlc4550 and stlc4560. I don't know the legal situation with stlc4370. -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: stlc45xx: open source WLAN driver for N800 and N810
"ext Andrea Grandi" <[EMAIL PROTECTED]> writes: > Does it support packet injection :) ? > > I want that featur :D The best part with mac80211 design is that the driver doesn't care[1], it's up to mac80211 if packet injection works or not. I haven't tested it myself, but my understanding is that mac80211 supports packet injection now. [1] Of course the driver might have a bug which prevents packet injection, but that's just a bug. The driver itself doesn't need to be know where the transmitted packet is coming from. -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: stlc45xx: open source WLAN driver for N800 and N810
"ext Andrew Barr" <[EMAIL PROTECTED]> writes: > Kalle Valo nokia.com> writes: > >> I recommend anyone interested about the project joining >> stlc45xx-devel. Unfortunately the garage project is closed currently, >> but it will be opened as soon as possible. The garage project is open now, or at least it should be. Please let me know if there are problems. > Does this mean we cannot download the source code I put the source code temporarily to the webpage but in the future all releases are available from the project page: https://garage.maemo.org/frs/?group_id=774 > or does this mean that joining the mailing list and/or the garage > project is closed? They should work now as the garage project is open. > Also, since the tablets are currently using a 2.6.21 kernel, what > is the recommended source tree (e.g. linux-omap) and/or version > to upgrade so we can test the driver? I used stlc45xx 0.1.3 against this commit from linux-omap: commit de1121fdb899f762b9e717f44eaf3fae7c00cd3e Author: Daniel Stone <[EMAIL PROTECTED]> Date: Wed Aug 27 04:31:59 2008 +0300 ARM: OMAP2: Fix definition of SGX clock register bits > Also, if you are free to answer this question, what is the > "officiality" of this project? Is this done with the blessing > of Conexant? Does anyone have access to documentation or is > this all done by reverse engineering? Everything is fully legal and official, no reverse engineering were done. This all was made possible by good co-operation with ST NXP Wireless. As someone said, the homepage constains a bit more information, like the link to the firmware documentation. I'll make better webpage next week. -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: stlc45xx: open source WLAN driver for N800 and N810
"ext Lorn Potter" <[EMAIL PROTECTED]> writes: > Kalle Valo wrote: >> I'm excited to announce a new project called stlc45xx, an open source >> WLAN driver for Nokia N800 and N810. It's using mac80211 stack >> included in Linux since 2.6.22. Even though I currently classify the >> driver as alpha quality I have managed to transfer 1.2 GB of data with >> iperf. > > Excellent news! our sales and marketing will love you! Heh. This release is for developers, definitely not for users. But maybe some day... >> I'm sending this from Helsinki-Vantaa airport on my way to Berlin. I >> will be giving a presentation about stlc45xx at the Maemo Summit on >> Friday 15:00. See you there! > > hopefully these will be recorded for those on the other side of the planet. I hope not because I suck as a presenter =) -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: stlc45xx: open source WLAN driver for N800 and N810
"ext John Holmblad" <[EMAIL PROTECTED]> writes: > Kalle, Hi John, > does this driver provide full support for 802.11i-2004 (sometimes > refereed to as WPA enterprise or WPA2 enterprise^1 ) or does it only > support pre-shared key authentication? Actually the driver doesn't care, this is entirely up to the supplicant (in user space). I have used wpa_supplicant while testing the driver which supports also WPA enterprise (and almost any other method available). Actually currently the driver knows nothing about encryption or decryption because mac80211 encrypts all the frames in CPU. Hardware crypto support is in the TODO list. -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: stlc45xx: open source WLAN driver for N800 and N810
"ext Frantisek Dufka" <[EMAIL PROTECTED]> writes: >> Our aim is to run the project in community mode and all community >> contribution is very welcomed. > > Will definitely try. 770 support comes to my mind first, current > stlc45xx_readXX/writeXX code uses SPI framework, 770 has the chip > connected over McBSP port. Should be posible to either resurrect > direct McBSP code back or maybe add its driver it into SPI framework. Nokia 770 has stlc4370 and documentation for that chipset is not available. I'm not aware of the differences between stlc4370 and the newer chips so I cannot say how much work there is needed to get the driver working in 770. -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
stlc45xx: open source WLAN driver for N800 and N810
I'm excited to announce a new project called stlc45xx, an open source WLAN driver for Nokia N800 and N810. It's using mac80211 stack included in Linux since 2.6.22. Even though I currently classify the driver as alpha quality I have managed to transfer 1.2 GB of data with iperf. Our aim is to run the project in community mode and all community contribution is very welcomed. A git repository will be set up soon to make it easier for the developers to work on the driver. The project web page will contain more information as it comes available: http://stlc45xx.garage.maemo.org/ I recommend anyone interested about the project joining stlc45xx-devel. Unfortunately the garage project is closed currently, but it will be opened as soon as possible. I'm sending this from Helsinki-Vantaa airport on my way to Berlin. I will be giving a presentation about stlc45xx at the Maemo Summit on Friday 15:00. See you there! Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: umac.ko for 2.6.26
"ext Gregoire Gentil" <[EMAIL PROTECTED]> writes: > [ 274.247192] umac: module license 'Proprietary' taints kernel. > [ 1328.262176] sm_drv_spi_probe > [ 1328.262237] sm_drv_netdev_create > [ 1328.262298] Registering WLAN platform device > [ 1328.262847] Creating WLAN sysfs > [ 1328.463775] sm_drv_statistics > [ 1328.465545] cx3110x: chip variant STLC4550. > [ 1328.465606] sm_drv_fetch_firmware > [ 1328.465606] firmware: requesting 3826.arm > [ 1328.708282] sm_drv_fetch_firmware: file 3826.arm (31284 bytes) > [ 1328.708343] cx3110x: firmware version 2.13.0.0.a.22.8. > [ 1328.708740] cx3110x: driver version 2.0.15 loaded. > [ 1370.573364] GET RANGE > [ 1370.573455] cx3110x: WARNING SoftMAC not initialized, chip not booted (get > oid 0x1712) > > The last message means that lp->sm_initialization = 0. Indeed, > sm_drv_spi_initialize is not reached. sm_drv_spi_wq which > calls sm_drv_spi_initialize, seems also never reached - so > no ifconfig! -:( I checked that INIT_WORK(&lp->work,sm_drv_spi_wq); > is reached inside sm_drv_spi_probe. > > So why don't we get this first crucial interrupt? > Kalle? A little bit of help? ;-) Sorry, can't help you. -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: umac.ko for 2.6.26
"ext Gregoire Gentil" <[EMAIL PROTECTED]> writes: > Hello, Hi, > I'm experimenting with 2.6.26 on N810. I have successfully compiled > cx3110x but I need umac.ko. How can I get this proprietary module > compiled for 2.6.26? (Obviously, I can't insmod the 2.6.21 version). You simply can't. But we are very aware of the problem and are trying solve it somehow. I'm not aware of any hack about how to load the 2.6.21 version but Poky has some linker tricks, you might want to check that. Also there was discussion on cx3110x-devel about struct net_device changes. -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: WLAN driver for STLC4550 - 11n BT HomeHub2
"ext Gottfried F. Zojer" <[EMAIL PROTECTED]> writes: > Hello to all, > > Can someone advise me where to find more information about the WLAN > connection of the N800. There isn't that much of documentation available. The kernel driver consists of open cx3110x.ko and closed umac.ko modules. > I m aware that he is using a STLC4550 chip and was working fine so far with > all AP i was using. > > That changed since i swapped to BT HomeHub2 what runs 11n.Since that time > the device isnot recognizing the new Hub. You have to give more information so that we can help you. But first I recommend you to file a bug: https://bugs.maemo.org/ Add me to CC and we can start from that. Also here's a short list of what kind information is needed: * What AP you have? o Make and model? o Firmware version? o Hardware revision? o What are the encryption settings? (open/WEP/WPA-PSK/WPA-EAP) * What's the distance to the AP? * How many APs do you have? Also please be very specific what you are doing (which buttons you press etc) and what happens on the screen. > Expect when I but the setting on ad hoc,then I can see the Hub but no > connection to internet possible. I'm sorry, but I don't understand this. -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: USB Networking doesn't work on my N810 (diablo) and Ubuntu Linux 8.04
"ext Andrea Grandi" <[EMAIL PROTECTED]> writes: > 2008/8/4 Aleksandar Stojiljkovic <[EMAIL PROTECTED]>: >> >> Hello, >> Andrea, don't know if following info helps,... acceptable workaround (for >> maemo pc connectivity over usb) is to use ssh, sshfs and sbrsh over wlan. >> Works nice from Eclipse esbox. >> Best Regards, >> Aleksandar > > ssh over wlan should work without problems the only problem is > that is very very slow, compared with usb-networking :( WLAN shouln't be that slow. Sure, theoretically WLAN is slower than USB networking, but in practise it should be fast enough for ssh use. Try disabling WLAN Power Save Mode, because it creates quite a lot of latency. The amount of latency varies with your AP settings (beacon interval, DTIM), though. -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Please do not use this email-address anymore!
"ext Johannes Hoffmann" <[EMAIL PROTECTED]> writes: > I will be out of the office starting 15.07.2008 and will not return until > 31.12.2042. Away for 34 years? Lucky you! And I thought we have long vacations here in Finland... ;) -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Newbie questions
ext Javier Gálvez Guerrero <[EMAIL PROTECTED]> writes: > Through mail > archives<http://www.mail-archive.com/maemo-developers@maemo.org/msg11043.html>I've > noted that I'd need access to information included in wlancond.h and > wlancond-dbus.h header files from osso-wlan-dev library, not included in > osso-wlan, so it seems I have nothing to do with this alternative, > do I? osso-wlan-dev seems to be available now: https://bugs.maemo.org/show_bug.cgi?id=1790#c3 > Wireless tools seem to be the only way to get this kind of information. Wireless Extensions is widely used, yes, but you have to be careful when using on it N800/N810 because using at the same time with wlancond will create complications. For example, wlancond can change the interface status to down anytime and scanning would not work after that. Using wlancond D-BUS interface would avoid that, I think, but I'm not that familiar with wlancond and I cannot say anything definitive. Also please note that using WE or wlancond interfaces is not officially supported. You are on your own with that. > By the way, what about WiMAX, 3G and DVB-H networks? Any way to get these > networks information with Maemo? I have no idea. -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Newbie questions
ext Javier Gálvez Guerrero <[EMAIL PROTECTED]> writes: > And what about LibConIC <http://maemo.org/api_refs/4.0/libconic/index.html>? libconic provides only a very high level interface. If you want to know a list of available WLAN APs, you have to use low level APIs. -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Newbie questions
ext Javier Gálvez Guerrero <[EMAIL PROTECTED]> writes: > It seems that with Internet Connectivity API and others I can get some > information. What I really need is quite simple. Basically, I need to get > the signal strength fluctuations and scan the radio interface for available > access points or points or attachement. I supposed that I was able to get > this kind information from the specific hardware devices as it would make no > sense to provide with this API if they can not be used. Are these APIs for > what I think they are? You have two options, either use Wireless Extensions directly on wlan0 interface or wlancond's D-BUS interface. Most probably the latter is easier to implement, but there isn't any documentation available. You would need to check wlancond's sources from osso-wlan to see how it is used. For examples how to use Wireless Extensions see iwconfig sources from wireless-tools package. -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: USB Networking doesn't work on my N810 (diablo) and Ubuntu Linux 8.04
"ext Andrea Grandi" <[EMAIL PROTECTED]> writes: > When I try to do this on my PC, I get these errors: > > 1) I bring up usb0 on tablet using the control panel applet > > 2) I connect the usb cable to both PC and tablet > > 3) I do this: > > [EMAIL PROTECTED]:/home/andy80# ifup usb0 > usb0: ERROR while getting interface flags: No such device > SIOCSIFADDR: No such device > usb0: ERROR while getting interface flags: No such device > SIOCSIFNETMASK: No such device > SIOCSIFBRDADDR: No such device > usb0: ERROR while getting interface flags: No such device > usb0: ERROR while getting interface flags: No such device > Failed to bring up usb0. Did you get these errors from from your PC or tablet? I didn't quite understand that. I'm guessing that you did that on your PC and it happened because cdc_ether module was missing. > The device should be ok: g_ether module is loaded and usb0 interface > (with ip 192.168.2.15) is up. > I think the problem is my Ubuntu, because if I try to bring up the > same module, I get this error: > > [EMAIL PROTECTED]:/home/andy80# modprobe g_ether > FATAL: Error inserting g_ether > (/lib/modules/2.6.24-19-generic/kernel/drivers/usb/gadget/g_ether.ko): > No such device g_ether is the gadget side driver, you shouldn't use that on your PC. On PC side you should use cdc_ether module. On my debian box it's loaded automatically, but I don't why it didn't happen for you. Try reinserting USB cable, for example. Outputs from 'ifconfig -a', 'lsmod' and 'dmesg', both from the PC and the tablet, help diagnose the problem better. -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Corporate ownership of open source projects [LWN]
"ext Marcin Juszkiewicz" <[EMAIL PROTECTED]> writes: >> Finally we have the WLAN module and FW, which are again developed under >> NDA and it's quite unlikely that the manufacturer is willing to release >> the source. > > Wlan situation was wrong from beginning - when 770 was released. N8x0 just > use newer version of 770 driver. Too bad that no one was working on it to > make it work with standard linux wlan components like WPA supplicant. Lauro Venancio wrote a patch to support wpa_supplicant: https://garage.maemo.org/pipermail/cx3110x-devel/2007-November/05.html -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: wlan power management
"ext Tuomas Kulve" <[EMAIL PROTECTED]> writes: > Kalle Valo wrote: >> "ext Tuomas Kulve" <[EMAIL PROTECTED]> writes: >> >>> Is there a way to adjust the power saving options for wlan? With iwconfig? >>> >>> I tried "iwconfig wlan0 power X Y" with different X and Y options but I >>> always got invalid argument. >> >> See this: >> >> http://maemo.org/community/wiki/wifipsm/ > > So the gconf values are read by ICd which then sets the power saving > mode of the device through some other API? Nope, wlancond reads them from gconf and passes them to cx3110x using Wireless Extensions. > Is that API closed or open? wlancond is open. -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: wlan power management
"ext Tuomas Kulve" <[EMAIL PROTECTED]> writes: > Is there a way to adjust the power saving options for wlan? With iwconfig? > > I tried "iwconfig wlan0 power X Y" with different X and Y options but I > always got invalid argument. See this: http://maemo.org/community/wiki/wifipsm/ And google for wlan_sleep_timeout and inactive_wlan_sleep_timeout. -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: WLAN Horrible Roaming Performance (N800, OS2008), Software or Hardware Problem ?
"ext Siarhei Siamashka" <[EMAIL PROTECTED]> writes: > A while ago I looked for various kernel docs to see what's happening in the > wlan driver and what can be done to reduce cpu load. My impression was that > tasklet can be only preempted by hardware interrupts, so it is impossible to > sleep in it and give cpu resources to userland applications. If that is true, > no matter if n800 driver looks nicer, it must end up busylooping too. Nope, on N800 cx3110x and omap2_mcspi do not busyloop during the DMA transfer. They use workqueues to allow sleeping, and completions for signalling. To be exact both cx3110x and omap2_mcspi do busyloop on certain occasions (waking up the chip etc.), but they do not busyloop during DMA. -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: WLAN Horrible Roaming Performance (N800, OS2008), Software or Hardware Problem ?
"ext Frantisek Dufka" <[EMAIL PROTECTED]> writes: > So you need to be familiar with the driver and tell us if it is > possible to sleep inside cx3110x_spi_dma_read and > cx3110x_spi_dma_write. cx3110x uses tasklets and it's not possible sleep in a tasklet. > And one also needs to be familiar with kernel programming and > waiting primitives to suggest how to sleep and wait for the callback > (if possible in this context) and how to wake up the sleeping code > from the dma callback. Basically I see two choices here, either you could either convert the driver to use a workqueue and use wait_for_completion()/complete() or convert the interrupt handling to use asynchronous calls. The latter is more difficult, but you might get some performance savings. You could ditch tasklet altogether and use interrupt handler. But I can't spend any time on the 770 driver, I can only wish you good luck. -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Confused: Python bindings to D-Bus - OSSO.RPC or DBUS module? Also: wlancond question
"ext Nadav Aharony" <[EMAIL PROTECTED]> writes: > Second issue- controlling the WLAN connection > From my reading I saw that for the networking stuff I would need to > connect to "wlancond" and to "ICD". I saw discussions about them not > being open source, but that there is some API available. icd is closed but wlancond is open. You can find wlancond sources from osso-wlan package: http://repository.maemo.org/pool/maemo4.0/free/source/o/osso-wlan/ > Could anyone direct me to those APIs and some way to use them > through Python? This might help you: http://maemo.org/development/documentation/how-tos/4-x/maemo_connectivity_guide.html > Can I have access to all of the settings that are possible through > the network configuration GUI application? The network settings are stored to GConf. I don't remember the exact location, but it should be quite easy to find them. > Is there any example of setting WLAN connection and IP settings > (e..g static IP address) through python? Create a new network connection (aka. IAP) to GConf and connect to that IAP using libconic. -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: WLAN Horrible Roaming Performance (N800, OS2008), Software or Hardware Problem ?
"ext Frantisek Dufka" <[EMAIL PROTECTED]> writes: >> [50622.038146] We haven't got a READY interrupt from WAKEUP. (firmware >> crashed?) >> [50622.038269] Try again... >> [50622.038330] succeeded!!! >> >> I'm attaching the same patch here. It is not very clean, but it does >> the job (for Nokia 770). > > Not seeing whole code now but I wondered before - isn't it possible > just to increase timeout inside 'if (time_after(jiffies, timeout))' > instead of two passes in loop? I also haven't seen the full code, only took a quick look at the patch. But what I saw is that the whole frame is retransmitted, instead of just waiting for the WR_READY interrupt from the firmware. In other words, if the frame is lost during the tranmission to firmware, the firmware won't receive the frame and it will not assert the WR_READY interrupt. So it doesn't help even if the driver waits longer, only frame restransmission helps. > The N800 code looks nicer, where the CPU is burnt there? The N800/N810 driver uses omap2_mcspi and SPI framework for accessing the SPI bus. Basically omap2_mcpi waits for DMA interrupts to know when the transfer has finished. But there are lots context switching between cx3110x and omap2_mspi threads, that might consume some extra CPU cycles. -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: WLAN Horrible Roaming Performance (N800, OS2008), Software or Hardware Problem ?
"ext Siarhei Siamashka" <[EMAIL PROTECTED]> writes: > With a simple patch that just retries operation on such error, > wireless connection got stable. After a long test with the test > script, no problems were detected. The following lines could be > occasionally seen in dmesg log and it proves that there were > potential connection drops encountered, but they all did not cause any > troubles in reality (MD5 of downloaded file was always OK): > [50559.494232] Dynamic PSM > [50559.494323] PSM timeout 1000 ms > [50622.038146] We haven't got a READY interrupt from WAKEUP. (firmware > crashed?) > [50622.038269] Try again... > [50622.038330] succeeded!!! Yeah, sounds like the SPI bus is not reliable because retransmitting the frame succeeds. > I'm attaching the same patch here. It is not very clean, but it does > the job (for Nokia 770). Thanks. I'm sure this patch helps with SPI problems. > And I have encountered other problems with WLAN driver that are yet to > be solved. For example, sometimes speed drops to ~30KB/s (that's still > an unresolved mystery to me). Do you see this only with 770 or also with N800/N810? > Also CPU usage is very high because of busyloop when waiting till > DMA transfer is done. Tasklet, which executes the code can't be > easily preempted, as far as I understand kernel documentation. Maybe > it is possible to split tasklet into several parts, one of them > could be responsible for initiating DMA transfer, the other could be > activated on DMA transfer completion? This all is important for > video streaming as any excessive CPU resources consumption by WLAN > driver negatively impacts video playback performance. Sorry, I'm not familiar with OMAP 1710 McBSP, so I can't comment. -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: WLAN Horrible Roaming Performance (N800, OS2008), Software or Hardware Problem ?
. You need to run 'ifconfig wlan0 down', but that doesn't work because wlancond does not follow wlan0 interface status. I think the easiest would be to send disconnected signal to wlancond using D-BUS, for example with dbus-send commandline tool. Unfortunately I don't have any examples at hand, but osso-wlan sources might help you. -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: WLAN Horrible Roaming Performance (N800, OS2008), Software or Hardware Problem ?
"ext Benno Senoner" <[EMAIL PROTECTED]> writes: >> > The question is could it be that the socket remains stuck due to the >> > roaming and is not able to recover ? >> >> TCP doesn't fit wireless networks that well, it usually takes a long >> time to cover from packet lost. Most probably what happens for you is >> that some packets are lost due to roaming, and TCP thinks that there's >> congestion and stops sending packets for a while. >> >> Most probably the connection would recover after a while, and the >> while here being several minutes with the default TCP settings. > > > You think those time outs are really that long ? Yeah, they are quite long. I have heard about long timeouts with other applications using TCP. An easy way to confirm, if this is a TCP problem or something else, is to run ping in the background and see how long timeouts (ie. how much you see packet loss) you get with it. ICMP ping does not have any of problems that TCP has. > the strange thing is if I go around the area with my Dell Laptop > (under Windows) with VNC open it does not suffer from those extreme > slow downs. I'm guessing that the laptop is roaming more aggressively than the N800 and TCP works fine because of that. >> iwconfig is handy. Also checkout iwevent, for example you can easily >> follow whenever roaming to different AP happens. > > > so does iwevent emit an event when the n800 roams ? Yes. > yes it could be useful, tanks for the tip I wil try. I usually run 'iwevent &' to get it running in the background so that I can easily see what's happening. Very handy. > Aaah, I did not know that wlancond would overwrite those values, thanks alot > I will try to use the method you proposed, perhaps it will help. > > gconftool-2 --set --type int >> '/system/osso/connectivity/IAP/bgscan_threshold' '70' >> gconftool-2 --set --type int >> '/system/osso/connectivity/IAP/bgscan_interval' '20' Sorry, I made a mistake here! Unit of bgscan_interval is milliseconds, not seconds as I say above. So the correct way to set background scan interval is this: gconftool-2 --set --type int \ '/system/osso/connectivity/IAP/bgscan_interval' '2' I'm sorry about this. > As for the network lock ups we are experiencing (you have to > disable,enable wlan on the n800 to make it work again) Does ping work when that happens? For example, you could try to ping your gateway. Also can you send me the output from dmesg after you experience this, please? > other users reported it too as Luca Olivetti pointed out. and it > seems like the problem and fix is described here: > > http://internettablettalk.com/forums/showpost.php?p=134914&postcount=15 > > at least for the 770 the fix seems to exist, What I read from the link, someone had written a workaround to try again whenever the chip is responding. That would good a feature, but I would like to get more information about what's happening in this case. > I hope it is not hard to implement this on the N800 too. I have a > few 770 too so I can try to apply the fix described in the forum and > see if my wlan lockup problems disappear. 770 has quite old software, so I would prefer if you can send me more information with N800. > Since the 770 is out of production and we will buy n800 and > successors it is fundamental that the n800 (OS 2008) gets this fix > ASAP. With WLAN driver changes ASAP usually means quite a long time due to all the risks, testing and certification involved. -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: WLAN Horrible Roaming Performance (N800, OS2008), Software or Hardware Problem ?
"ext Frank Banul" <[EMAIL PROTECTED]> writes: > I'm a home user with two access points. I've noticed that the N810 holds on > to the connection with the established AP far longer than the 770 seemed to. > I expect to never see low strength signals as the two APs cover my home > nicely. But I have not noticed any problems associated with this apparent > change in behavior. If you don't see any problems (slow connections etc.) I'm happy. The low signal itself isn't a problem. Thanks for the feedback. -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: WLAN Horrible Roaming Performance (N800, OS2008), Software or Hardware Problem ?
"ext Luca Olivetti" <[EMAIL PROTECTED]> writes: >> Sometimes it even happens that the operator when roaming and wanting to >> use the N800 >> the VNC session got stuck and nothing works, so he has to power cycle it. > > This also happens with no roaming at all (i.e. the connection manager > show the tablet as associated but it's not possible to transfer any > data). It's random and not related to activity/inactivity (I can work > for a whole day or get stuck after 10 minutes). Usually I just > re-connect to the access point, I don't need to power cycle the tablet. I think that this is a different problem than what Benno is having. -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Slow operations trough ssh, connected to my N810
"ext Andrea Grandi" <[EMAIL PROTECTED]> writes: > Hi, > >> My guess is that your router 100 ms beacon interval and DTIM is 2. If >> you change DTIM to 1 the latency would be a bit less, but power >> consumption would increase. > > I didn't change any value on the router No, DTIM 2 is a good default setting. But you can change it, if you want decrease latency on your network. > but yes, if I disable power management on my N810, the ping time is > around 2 ms. Anyway I've no problem when I use my N810 to browse > internet, make calls ecc... That's normal. When you are making a connection FROM N810 packets can be sent immeadiately to the air. > I've these problems only when I try to connect from my notebook to > it trough ssh. Here N810 needs to woken up by sending the packet TO N810, and that can only happen in DTIM beacon (the only time radios are turned on while device is otherwise idle). That's why PSM is slow. -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Slow operations trough ssh, connected to my N810
"ext Andrea Grandi" <[EMAIL PROTECTED]> writes: > I tried turning the power management off, and these are the ping results: > > Nokia-N810-50-2:~# ping 192.168.0.1 > PING 192.168.0.1 (192.168.0.1): 56 data bytes > 64 bytes from 192.168.0.1: seq=0 ttl=255 time=5.2 ms > 64 bytes from 192.168.0.1: seq=1 ttl=255 time=4.9 ms > 64 bytes from 192.168.0.1: seq=2 ttl=255 time=4.7 ms > 64 bytes from 192.168.0.1: seq=3 ttl=255 time=4.7 ms > 64 bytes from 192.168.0.1: seq=4 ttl=255 time=4.7 ms > 64 bytes from 192.168.0.1: seq=5 ttl=255 time=4.5 ms > 64 bytes from 192.168.0.1: seq=6 ttl=255 time=4.7 ms > 64 bytes from 192.168.0.1: seq=7 ttl=255 time=4.7 ms > > --- 192.168.0.1 ping statistics --- > 8 packets transmitted, 8 packets received, 0% packet loss > round-trip min/avg/max = 4.5/4.7/5.2 ms You are pinging the wrong way, you should ping from network to N810. >From N810 to network it's always fast. > result: the power management of N810 really SUCKS!!! Power Save Mode adds latency significantly, and that's how it is designed. You cannot break laws of physics, you know. But you can always disable Power Save Mode, which again means that the battery will ran out within ten hours even if the display is turned off and CPU is sleeping. So (again) it's either low latency or minimum power consumption, not both. -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Slow operations trough ssh, connected to my N810
"ext william maddler" <[EMAIL PROTECTED]> writes: > time > 10ms sounds strange to me, being on the same network... It's normal for N810 when pinging from network and WLAN Power Save Mode is enabled. With beacon interval 100 ms and DTIM 2 the latency will be approximately between 0-300 ms when pinging from network to N810. -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Slow operations trough ssh, connected to my N810
"ext Andrea Grandi" <[EMAIL PROTECTED]> writes: > this is the ping result: > > [EMAIL PROTECTED]:~$ ping 192.168.0.102 > PING 192.168.0.102 (192.168.0.102) 56(84) bytes of data. > 64 bytes from 192.168.0.102: icmp_seq=1 ttl=64 time=9.03 ms > 64 bytes from 192.168.0.102: icmp_seq=2 ttl=64 time=69.9 ms > 64 bytes from 192.168.0.102: icmp_seq=3 ttl=64 time=283 ms > 64 bytes from 192.168.0.102: icmp_seq=4 ttl=64 time=5.71 ms > 64 bytes from 192.168.0.102: icmp_seq=5 ttl=64 time=132 ms > 64 bytes from 192.168.0.102: icmp_seq=6 ttl=64 time=26.3 ms > 64 bytes from 192.168.0.102: icmp_seq=7 ttl=64 time=296 ms > 64 bytes from 192.168.0.102: icmp_seq=8 ttl=64 time=218 ms > 64 bytes from 192.168.0.102: icmp_seq=9 ttl=64 time=140 ms My guess is that your router 100 ms beacon interval and DTIM is 2. If you change DTIM to 1 the latency would be a bit less, but power consumption would increase. -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Slow operations trough ssh, connected to my N810
"ext Andrea Grandi" <[EMAIL PROTECTED]> writes: > I've openssh and ssh client installed on my N810. Sometimes I need to > connect to the N810 using ssh, from my notebook (they're both on the > same lan). Very often I experiment that connection is very very slow > :( > > Cannot understand why...if I open an Xterm on N810 and I execute: ssh > [EMAIL PROTECTED], everything looks fast. No process is taking 100% or > something similar > > Anyone experienced the same problem? Try disabling WLAN power save from Connectivity Control Panel Applet. -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: WLAN Horrible Roaming Performance (N800, OS2008), Software or Hardware Problem ?
Currently we have strived for better power consumption and unfortunately your use case suffers from that. I don't know if it's correct decision or not. I'm all ears. > I hope the N800 hardware is not flawed and that a fix can be found, > thanks everyone in advance for your advices and help ! This is not a hardware problem, if that's what you are referring here. > I think this kind of roaming performance tuning is important to many > others too It would nice to get real statistics about this, but my guess is that most of the people don't need roaming (think home users). Or if they need it, they need very rarely. > and I hope that they can profit from the discussion that will come > out too. At least I will certainly benefit from the discussion. -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: KProbe for kernel 2.6.21
"ext Leandro Sales" <[EMAIL PROTECTED]> writes: >why I can't see CONFIG_KPROBES symbol nor KPROBES module for the > kernel 2.6.21 for maemo? Is there something that I have to do to have > this option enabled? My first question is that does Kprobes really support ARM? I recall that it does not. [some googling] Yes, it seems that ARM support wasn't official at the time 2.6.21 was released (2007-04-26): http://sourceware.org/ml/systemtap/2007-q1/msg00082.html -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: busybox applet selection (again)
"ext Damien Moore" <[EMAIL PROTECTED]> writes: > On 1/2/08, Kalle Valo <[EMAIL PROTECTED]> wrote: >> I have to agree with Eero here. It's much more useful to have the >> original tools available instead of (too) simple busybox variants. > > what I'm suggesting would be an optional package that, if set up correctly, > won't break anything (but will block the installation of overlapping tools > in other packages). Users who want original tool sets could take the > standard busybox package and install separate tools packages. If having the > original tools is always better perhaps busybox shouldn't be used at all? That's what Eero is proposing here: disable certain tools, for example ping, from busybox and install the "full" versions, for example iputils-ping. >> example, you need to be root to run busybox ping and it does not >> support flood ping. > > for good or bad the root problem is overcome with > # chmod 4777 /bin/busybox I'm not even going to comment on that. >> Having iputils-ping would fix both of these >> problems. > > why not take all of iputils? Sure, if there is a need. ping was just an example. -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: busybox applet selection (again)
"ext Damien Moore" <[EMAIL PROTECTED]> writes: > https://bugs.maemo.org/show_bug.cgi?id=989 > > the bug was marked WONTFIX > > Eero Tamminen's resolution was to not add any additional applets to > BusyBox because in his opinion those needs can best be met by creating > full versions of the tools in separate packages. I don't think this is > a good idea because it creates a proliferation of unnecessarily > bloated packages with the attendant problems of maintaining multiple > packages (keeping in mind that the target hardware is a capacity > constrained tablet). The benefit of busybox is that most appplets add > just a few kb to the binary size and all of them sit inside a single > binary. I have to agree with Eero here. It's much more useful to have the original tools available instead of (too) simple busybox variants. For example, you need to be root to run busybox ping and it does not support flood ping. Having iputils-ping would fix both of these problems. -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: python2.5 - unnecessary multiple processes forked
"ext Frantisek Dufka" <[EMAIL PROTECTED]> writes: >> I can't >> imagine any valid reason for gtk/hildon to fork more processes just to >> show a GUI dialog. Does anyone know? > > I'm not sure but think it is because of gnome-vfs. Don't know proper > terminology but maybe each vfs 'provider' in the dialog (like mmc, phone > etc.) starts new process or something like that. I think you are correct. I heard that some gnome-vfs plugins, for example UPnP, start their own thread (or something like that). But I'm a network guy, I know jack about our UI. So I might be wrong here. -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Kismet on N800 stops running after 1-2 minutes
"ext Ryan Pavlik" <[EMAIL PROTECTED]> writes: > That is a wireless driver error (probably has nothing to do with > auto-search), and because the driver is closed source, Dragorn can't fix it. Parts of it are open: https://garage.maemo.org/projects/cx3110x/ -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: N810 Resets
"ext Alex Iliadis" <[EMAIL PROTECTED]> writes: > After running again my code and introducing a small delay factor, I noticed > the following warning in ksyslogd saved logfile: > > WARNING: prism_softmac_frame_tx_done() returned an empty frame That happens all the time, I just have recently added warning for this. You can ignore it for now, it does not cause any crashes. -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: umac.ko
"ext [EMAIL PROTECTED]" <[EMAIL PROTECTED]> writes: > I also very much would like this to work with packet injection, Me too. > and be able to modify the source completely for other reasons. I also would like you to be able to modify the source code, no doubt about that. I'm a strong supporter of Open Source and I'm certain that having an open WLAN driver would benefit both the community and Nokia. But as life in general, things are not that simple. It's not that we just need to decide that we will have an open driver. There are various aspects and requirements involved, and all them need to solved before an open driver would be reality. > So in this case can't we just get the full data sheet for the chip > and we're off to the races. Program it to do anything we need. > Third party manu. so I'm assuming the full data sheet is not top > secret...? Only public data sheet I'm aware of is here: http://www.st.com/stonline/products/literature/bd/12063/stlc4550.htm But that's not going to help you at all. If we could publish a complete data sheet of the WLAN chip in Nokia tablets, we would have done that a long time ago. Heck, I would have even written the driver on my free time if that would have been possible. The problems here are not technical, but something else. -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: OS2008 on n800 - Nice Job
"ext Igor Stoppa" <[EMAIL PROTECTED]> writes: > Unfortunately our dear legal department wants to keep dsme and mce > closed, but apart from waiting some time and blanking the screen and > changing the wireless timeout, they don't do anything that is > power-saving related. The wireless timeout is controlled by wlancond which issues the command to cx3110x. wlancond just listens to a display status signal from DSME. -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Bugfix in cx3110
"ext Steven Walter" <[EMAIL PROTECTED]> writes:
> While reading through the wireless card driver (what source is
> available), I noticed what is almost certainly a bug:
>
> --- sm_drv_ioctl_umac.c~ 2007-12-06 22:34:03.0 -0500
> +++ sm_drv_ioctl_umac.c 2007-12-06 22:34:05.0 -0500
> @@ -2024,7 +2024,7 @@
> if (ret < 0)
> return ret;
> } else {
> - if (!crypt_info->flags & IW_ENCODE_MODE) {
> + if (!(crypt_info->flags & IW_ENCODE_MODE)) {
> /* we cannot do anything. Complain. */
> return -EINVAL;
> }
> --
>
> The old test is equivalent to if (0), which means its not possible
> to set the ENCODE_MODE without also setting a key.
You are right. Thanks for telling us.
I noticed that you already filed a bug about, that's really good:
https://bugs.maemo.org/show_bug.cgi?id=2504
For a faster response time I recommend to use cx3110x-devel. I do
follow maemo lists, but very infrequently.
--
Kalle Valo
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: umac.ko
"ext Luca Olivetti" <[EMAIL PROTECTED]> writes: >> I find that very unlikely. If you can come with a good business _and_ >> use case, I might reconsider taking this to higher-ups. But the >> reasons would have to be really good. > > Mmh, so I guess that ranking better on > http://www.aircrack-ng.org/doku.php?id=compatibility_drivers > wouldn't be enough. Sorry, that's not enough. Fixing bugs and improving performance is far more important. -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: umac.ko
"ext Luca Olivetti" <[EMAIL PROTECTED]> writes: > En/na Kalle Valo ha escrit: >> "ext Alex Iliadis" <[EMAIL PROTECTED]> writes: [packet injection] >>> Is there a way that we can modify the source of the umac.ko module supplied >>> with the N810 or N800? >> >> The answer is plain and simple no. The umac.ko module is proprietary >> and the source code is not available. Sorry. > > But somebody has access to that sources, so he or she could add this > often requested feature, right? I find that very unlikely. If you can come with a good business _and_ use case, I might reconsider taking this to higher-ups. But the reasons would have to be really good. -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: web based local application GUIs
"ext Tomi Ollila" <[EMAIL PROTECTED]> writes: > On Wed 05 Dec 2007 19:09, Kalle Valo <[EMAIL PROTECTED]> writes: >> In tablets applications request connections through libconic and after >> that they can open sockets as usual. If some applications request >> connections to localhost from libconic, that's a bug in the >> application, not in lower levels. > > OK! So next the big question: If I open default browser and try to connect > http://127.0.0.1/ and I have application in port 80 serving http requests > should that work? (with all / which IT OS versions?) No idea, it depends how the browser is implemented. If it's clever enough, it won't request a connection from libconic for localhost connections. I'm not involved in browser development and I can't give you an answer for this one. >> Exception: there was a preload library (which name I don't even >> remember anymore) in osso-ic-lib which wrapped socket() and close() >> functions and did just what you described here. But I doubt (and hope) >> that nobody uses it anymore. > > What is someone wants to take some unix software, compile it unmodified > for internet tables and expect it to make internet connections as the > browser does now (i.e. automatically start connection over wlan/bt) ? Then the preload library is the only option. But in that case I think it's better that the user is forced to open the connection manually. The library is a hack and only deity knows what kind of problems it might create. When an application is really ported to maemo platform, it's trivial to add libconic support. This all is IMHO, of course. I finally checked the name of the preload library I have been talking about. It's libosso-ic-preload.so and doesn't seem to be included in OS2008 anymore. -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: web based local application GUIs
"ext Tomi Ollila" <[EMAIL PROTECTED]> writes: > So I remember incorrectly -- the real reason is (probably) that when > socket(2) system call is started, these Internet Tablets tries to make > internet connection up (either via wlan, or bt-connected phone) > and if that cannot be made, socket(2) fails. > There is no way knowing at socket(2) time that user wants to connect(2) > 127.0/8 addresses. There is probably good reason to wrap socket() instead > of connect(), bind() (and some other system calls.. timeouts maybe...). Nope, any of the calls you mentioned are not modified (or wrapped) in any way. They work similarly in Nokia tablets as in normal Linux PCs. In tablets applications request connections through libconic and after that they can open sockets as usual. If some applications request connections to localhost from libconic, that's a bug in the application, not in lower levels. Exception: there was a preload library (which name I don't even remember anymore) in osso-ic-lib which wrapped socket() and close() functions and did just what you described here. But I doubt (and hope) that nobody uses it anymore. -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: umac.ko
"ext Alex Iliadis" <[EMAIL PROTECTED]> writes: > Is there a way that we can modify the source of the umac.ko module supplied > with the N810 or N800? The answer is plain and simple no. The umac.ko module is proprietary and the source code is not available. Sorry. -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: debugging spontaneous reboot issues with N800/N810
"ext Aleksandr Koltsoff" <[EMAIL PROTECTED]> writes: > cat 32wd_to: > 2 > Question: Does this count the times that the hw-watchdog was triggered > so far (after last flash)? Yes. > cat sw_rst: > 1 > Question: Number of times "critical 'system' application crashing or > being killed by the kernel OOM-killer" happened? (quoted text from the > wiki page) More like number of reboots issued after a critical system application crashed. More than one critical application can crash at the same time :) > cat lifeguard_restarts: > /usr/bin/esd : 1 > /usr/sbin/multimediad : 1 > /usr/sbin/dsp_dld -p --disable-restart \ > -c /lib/dsp/dsp_dld_avs.conf : 1 * > (line continuation in the last one was made by me) > > Question: Now this is the interesting part: > 1) Am I correct to assume that each line records the name of the program > that was running when the hw watchdog triggered? No. This file tells that how many times each application has been restarted. These are not "critical system applications" in a sense that there is no need to restart (reboot) the whole device, only the application is restarted. If the application crashed many times in a row after the device will be restarted. Or at least I think that's how the things are. DSME terms are a bit confusing and I always mix them up. But here's how I see them: reset = whole device is rebooted restart = application is restarted but device is not rebooted > 2) And the number after each records the times that the programs were > running when the watchdog tripped? No. It's the number of times an application is restarted. > 3) Asterisk marks the application that caused the last wd timeout > operation? (so in this case, the spontanous reboot was caused by dsp_dld > or it at least seems so?) There is no way to know what cause hardware watchdog reboot. It can be a problem in kernel, or some userspace application taking all the CPU time. So in a summary: 32wd_to: a number of times a watchdog reboot has happened, reason unknown sw_rst: a number of times the device is rebooted due to a critical application crashing lifeguard_resets: detailed statistics which application crashed and how many times have caused device reboot (excluding watchdog reboots) lifeguard_restarts: statistics about which applications have crashed but have not caused device reboot -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
cx3110x-devel
It seems that there has been a cx3110x-devel mailing list for ever and I have just missed it: https://garage.maemo.org/mail/?group_id=12 Thanks to Frantisek Dufka for noticing that. I'm trying to active that list now, because I have hard time following maemo lists. So if you have development related questions or patches for cx3110x, please send them to cx3110x-devel. For general user problems I still recommend to send them to maemo-users. (cx3110x = WLAN/Wi-Fi driver for 770/N800/N810) -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Error shutting down os2008 in n800
"ext Jose Antonio Vacas Martinez" <[EMAIL PROTECTED]> writes: > I've installed os2008 in mi n800 (following this > recipe<http://www.news.com/8301-10784_3-9816300-7.html?tag=nefd.only>) > and it works really, really good (goog jobs nokia!!). > Only got a weird behaviour: when shutting down using the menu (short press > the on/off button) the screen became black but the n800 is not shut down > properly (2-3 hours later the battery is drained). When press the on/off > button the system doesn't start, I've to remove the battery in order to make > the system run. I'm not suprised. If you make a hack something like that, some software parts might (will?) be broken. My advice: wait for the official image. (Disclaimer: this is strictly a personal comment, not an official statement from Nokia etc.) -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: SPIM (MIPS assembly emulator) ported to Chinook: could someone test it?
"ext Marcelo Lira" <[EMAIL PROTECTED]> writes: > to check which files where installed by a .deb file use this command: > > dpkg -L packagename Or if you don't want to install the package: dpkg --contents package.deb -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Data corruption on N770 in OS2007 HE
"ext Alex DAMIAN" <[EMAIL PROTECTED]> writes: > the modified cx3110x driver works ok. I think it's a bit weird that my > WRT router would assign different IP addresses depending on the driver > loaded, but it's not an inconvenience after all. Did you remember to run wlan-cal after loading cx3110x? http://maemo.org/development/documentation/how-tos/3-x/howto_kernel_guide_bora.html -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: How to setup ad-hoc wireless network N770 <> PC Windows XP ? (pls don't delete)
"ext Darius Jack" <[EMAIL PROTECTED]> writes: > already spent more than 24 hors trying to setup ad-hoc wireless > network, connecting N770 to PC running XP Windows (no router, no > AP). > [...] > creating an ad-hoc network August 20th, 2007 by 4d770 > > ifdown wlan0 > ifconfig wlan0 169.254.1.9 > iwconfig wlan0 mode ad-hoc > iwconfig wlan0 ssid > iwconfig wlan0 channel 1 > ifconfig wlan0 up > > but > iwconfig wlan0 ssid doesn't work on maemo I would do it in this order: ifconfig wlan0 up ifconfig wlan0 169.254.1.9 iwconfig wlan0 mode ad-hoc iwconfig wlan0 channel 1 iwconfig wlan0 essid tempvalo Just tested this with two N810s by copy&pasting the command to the other device and connecting with the other. The WLAN driver does not support Wireless Extensions fully, so you have to be carefull when using it. The order matters and especially the interface must be up (ie. ifconfig wlan0 up) before doing any configuration. I know, this sucks. -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: WPA? Re: WLAN connectivity using only wireless-tools
"ext Frantisek Dufka" <[EMAIL PROTECTED]> writes: > Kalle Valo wrote: >>> I don't see any PSM lines for example, while with the ITOS I do. >> >> Yeah, you have to enable PSM with the power iwconfig parameter. >> Otherwise PSM is disabled. >> > > Interestingly this parameter need values less than 1 for sensible > timeout, something like "iwconfig wlan0 power timeout 0.0002" gives me > 200ms That's weird. I'll take a look at it. > Yesterday I tried to bring up wireless via wireless-tools too but it > looks like it doesn't support WPA-PSK at all. It this correct? Yes. > How the system does it anyway? In 770/N800/N810 we do it with combination of wlancond (from osso-wlan, GPL) and eapd (from osso-wlan-security, proprietary). > Then I tried to compile latest (v0.5.8) wpa_supplicant with just > [...] > it prints two pages of scanning output but then segfaults and causes > kernel to crash inside wlan driver. unfortunately the Wireless Extension support in cx3110x does not yet support wpa_supplicant. But the driver shouldn't crash anyway. > Is there any way how to make WPA running from command line? There's no easy solution. > I was actually trying to do it early on boot from initfs > as per comment #7, http://bugs.maemo.org/show_bug.cgi?id=2006 > so I have whole memory free. Looks like I really need to downgrade > security on my router to attach to it from command line? I'm afraid so. -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Cisco leap support for maemo / wpa-supplicant
"ext Rainer Dorsch" <[EMAIL PROTECTED]> writes: > Since wpa-supplicant is supporting leap since a long time, does anybody know, > if wpa-supplicant supports the cx3110x chip? Not yet. The Wireless Extension interface in cx3110x does not support WE-18 which wpa_supplicant needs. -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Nokia N810 Q
"ext Peter Robinson" <[EMAIL PROTECTED]> writes: > There is only one removable SD slot. Its a miniSD slot that can take > either miniSD or microSD (with a converter). The "internal 2GB card" > is 2GB of flash built in (chip on mainboard I suspect) so there is > actually only one SD slot. You are correct. -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: How can Nokia N770 gain the WEB KEY automaticly
ext 无无 <[EMAIL PROTECTED]> writes: > My campus wireless net need the Nokia N770 gain the WEB KEY automaticly ( > visit the > http://www.depts.ttu.edu/helpcentral/general/wireless/wirelessPPC2003_X30.php > for detail), > > but there is no this optional, what should I do ? Is there any software can > do this ? It seems that the university network supports IEEE 802.1x with PEAP (which means using WEP encryption). Unfortunately Nokia 770 or N800 does not support that. We only support PEAP with WPA (ie. with TKIP or AES encryption). -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: WLAN connectivity using only wireless-tools
"ext Kalle Vahlman" <[EMAIL PROTECTED]> writes: >> But it might that you were just lucky this time. If only two channels >> are scanned, most of the time the driver won't be able to associate >> because it can't find the AP. How many channels did it scan? > > On boot, it says two channels was scanned. Association hasn't failed > on me yet, so perhaps I'm a very lucky guy :P On what channel is your AP? > Running iwlist scanning by hand reports 13 channels afterwards though. That sounds normal. > And shows one result with zeroed values (I think I've seen > discussion on this bug though). What values were zero? > On a related matter, I tried to build the modules from garage sources > and although it seemingly worked, replacing the modules on board left > me with non-functional wlan. Being a smart guy (not just lucky), I had > a way to go back to the original drivers of course. The umac.ko is an empty module, don't use that. Only use cx3110x.ko. > I didn't yet dig deeper and gather logs (IIRC the firmware or driver > was resetting the chip after any commands to the interface), since I > wanted to know first if they are known to be compatible with the > current ITOS2007 release (initfs) or was it just me? Sources for ITOS2007 releases are available from repository.maemo.org. See my post here: https://garage.maemo.org/forum/forum.php?forum_id=1236 -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: WLAN connectivity using only wireless-tools
"ext Kalle Vahlman" <[EMAIL PROTECTED]> writes: >> > ifconfig wlan0 up >> > iwlist wlan0 scanning > /wlan-list >> > iwconfig wlan0 mode managed >> > iwconfig wlan0 ap auto >> > iwconfig wlan0 essid "xxx" >> >> I don't use the ap command at all, try without it first. > > I don't remember if I ever tried without it, but at least now it works > when I removed all but the essid command. Go figure :) Yeah, basically scan, mode and ap commands are not needed because the defaults are the same as you set here. But it might that you were just lucky this time. If only two channels are scanned, most of the time the driver won't be able to associate because it can't find the AP. How many channels did it scan? -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: WLAN connectivity using only wireless-tools
"ext Kalle Vahlman" <[EMAIL PROTECTED]> writes: >> I assume that you didn't modify initfs. > > Apart from installing bootmenu, no. It's the exact same initfs that I > use daily with the ITOS. Good, then WLAN module should be loaded correctly. >> Not a problem, should work just fine. Occasionally I also use >> wireless-tools directly. > > The version available for ITOS seems to be 28, while I have 29. I > don't think that should be a problem though? I'm not familiar with wireless-tools internals, but I remember the maintainer mentioning something about wireless-tools being backward compatible. So that it shouldn't be a problem, but maybe you could downgrade it, if nothing else helps. >> You just have to do ifconfig wlan0 up before using wireless-tools. >> When the interface is down, the driver doesn't accept any commands. > > Here's everything in a nutshell: > > Currently I do: > > ifconfig wlan0 up > iwlist wlan0 scanning > /wlan-list > iwconfig wlan0 mode managed > iwconfig wlan0 ap auto > iwconfig wlan0 essid "xxx" I don't use the ap command at all, try without it first. Note that scanning with iwlist buggy, you get incomplete results (bug #1106). > after which iwconfig says: > > wlan0 IEEE 802.11b/g ESSID:off/any > Mode:Managed Channel:0 Access Point: Not-Associated > Bit Rate=0 kb/s Tx-Power=19 dBm Sensitivity=0/200 > RTS thr:off Fragment thr:off > Encryption key:off > Power Management:off > 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 > > ie. nothing happened with the iwconfig commands cx3110x has "a feature" that essid will be shown only after an succesfull association. Yes, it is annoying and will be fixed in future. So this is normal in a situation where association fails. > , and the dmesg log doesn't contain much either: > > <4>[8.456665] umac: module license 'Proprietary' taints kernel. > <4>[8.621368] CX3110x chip variant: STLC4550 > <4>[8.699401] CX3110x: firmware version: 2.13.0.0.a.22.8 > <4>[8.708160] Loaded CX3110x driver, version 0.8 > [snip unrelated mmc/ext3 mumble] > <4>[ 10.249450] Loading 3826.arm firmware > <4>[ 10.493041] (c)opyright 2004 Conexant > <4>[ 10.496917] > <4>[ 10.496917] build info: PRISM SoftMAC > <4>[ 10.496948] creator: [kvalo] > <4>[ 10.496948] date: [07/05/03-10:28] > <4>[ 10.496978] > <4>[ 10.512023] CX3110x: MAC address 00:19:4f:xx:xx:xx > <4>[ 14.845031] Scan complete, scanned 2 channels Only two channels? Should be 13 with devices sold in Finland. Strange. > <4>[ 14.895599] Using default authentication order > <4>[ 15.628631] sm_drv_transmit: sm_frame_tx returned error -9 > [snip few more identical lines from trying to send unconnected] > > And that's it. The errors at the bottom are clear now, but... And I > can even see my AP in the 'iwlist scanning' output, but the interface > acts dead for me. I think the only problem is that the association is failing for some reason. First ditch the ap command from your script, see if that helps. I can't think of anything else. > I just can't think of or find anything in the ITOS boot scripts might > be setting up, that's why I thought maybe wlancond or someone did some > powerup stuff. I just checked from wlancond sources, it doesn't set anything in WLAN driver during boot. So it should just work. I'm on a train now, so I can't test this with real device. But I'll try to do that later. > I don't see any PSM lines for example, while with the ITOS I do. Yeah, you have to enable PSM with the power iwconfig parameter. Otherwise PSM is disabled. -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: wlancond and dbus
"ext Gabriel Grise" <[EMAIL PROTECTED]> writes: > Because i saw some questions about how to access to wlancond with dbus > And because I had the same question last week, i decided to send to this > list a code sample. This code sample simulate an "iwlist scan" call. > > I hope this will be useful for someone. Excellent, people have been asking for this. > #the first parameter seem to be the power level, WLANCOND_TX_POWER10 > or WLANCOND_TX_POWER100 > #but i have no idea of what value have these two constants, so i > found one of them with a strace. It's about 10 mW or 100 mW transmit power, which is configurable from UI. -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: WLAN connectivity using only wireless-tools
"ext Kalle Vahlman" <[EMAIL PROTECTED]> writes: > I'm trying to construct myself a small rootfs that would boot up and > connect to my (open) WLAN. I assume that you didn't modify initfs. > For this I'd very much like to avoid any unneccesary and/or closed > bits, so I thought no prob, I'll just install wireless-tools there > and put few commands to my bootup script. Not a problem, should work just fine. Occasionally I also use wireless-tools directly. > Alas, things didn't go that easily. For whatever reason, the wlan0 > interface (although seemingly up & running) refuses to take on the > essid I set with iwconfig, or any other command I try. Examples and full output from kernel, please. > So, the question is, is there some special setup needed for the wlan0 > to come to life or do I really need to bring in the likes of wlancond > (whatever it's role in this might be)? You just have to do ifconfig wlan0 up before using wireless-tools. When the interface is down, the driver doesn't accept any commands. > What I'm seeing in dmesg is the following line: > > <4>[ 11.625122] sm_drv_transmit: sm_frame_tx returned error -9 > reported multiple times, but I guess this could be just the dhclient > trying to talk over non-connected interface. Yes. It means that you try send a packet but you are not associated to the AP. > Any hints? Can't think of anything sensible. Try 'iwconfig wlan0 mode managed', but don't know if that makes any difference. It shouldn't. -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Network connection with hildon-app-mgr in the scratchbox
ext Mario Sánchez Prada <[EMAIL PROTECTED]> writes: > Thanks for your suggestion, but IMHO that doesn't fix the real problem > behind the scenes... I mean, why some applications (such as the > osso-xterm) can use a network connection inside the scratchbox while > hildon-app-mgr can't? Application Manager uses libconic and it's supported properly only on a real device. -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: dbus api for wlancond
Tim Teulings <[EMAIL PROTECTED]> writes: >> You can use sudo to gain root privileges on N800. > > I'm speaking of an potential enhancement for a GUI program, namely > WifiInfo, wich you also can find in it in the application catalog. so > doing a sudo is not what I would like the user to do :-) One way to use sudo with a GUI application is to start it with a script which just starts the applications using sudo. Like this: #!/bin/sh sudo mycoolapp Just add the script to the application menu, update sudoers from postinst and that's it. Yeah, it's ugly but works. I have never even bothered to see how to set setuid bits from a debian package. If anyone has better way to do that, I'm all ears. -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: udhcpc and hostname
Guard][an <[EMAIL PROTECTED]> writes: >> It's not hardcoded, it should use the device name from Bluetooth >> Control Panel applet. If not, that's a bug. >> > > it does not seem to work any more since the last os 2007 update :( > > which script should i hack to add a -H option to the udhcpc invocation ? Sorry, I don't know. -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: dbus api for wlancond
"ext Tim Teulings" <[EMAIL PROTECTED]> writes: > I now have some C++ code to poll the list of access points similar to > the way ooso-wlan does. On my desktop PC it seems however that I need > root rights to execute the underlying ioctl. Is this true for the > 770/800, too? Do I thus need S-Bit for my application (and how do I do > this in my debian package?) or is there another way to gain the > necessary rights? You can use sudo to gain root privileges on N800. -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: dbus api for wlancond
"ext Jussi Kukkonen" <[EMAIL PROTECTED]> writes: >> Thanks for the response. However I had looked at the source for >> wlancond previously. In the source the strings for the DBUS api can't >> be seen since they >> are stored in header files (wlancond-dbus.h or wlancond.h) that aren't >> included in the source osso-wlan. >> >> Do you know where these are? >> >> I saw a message by Patrik Flykt on this >> message board saying these files were in fact in osso-wlan-dev. But >> this does not seem to be in repository.maemo.org/ from what I could >> see. > > In that same discussion Kalle Valo promises to get back to the issue of > missing header files (April 4th) :) Yeah, sorry about that. I blame on missing PIM functionality in N800 ;) > Filed a bug: https://bugs.maemo.org/show_bug.cgi?id=1790 Good. That way it's easier to track the issue. -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: dbus api for wlancond
"ext nic" <[EMAIL PROTECTED]> writes: > Thanks for the response. However I had looked at the source for > wlancond previously. In the source the strings for the DBUS api > can't be seen since they are stored in header files (wlancond-dbus.h > or wlancond.h) that aren't included in the source osso-wlan. > > Do you know where these are? > > I saw a message by Patrik Flykt on this message > board saying these files were in fact in osso-wlan-dev. But this does not seem > to be in repository.maemo.org/ from what I could see. Oh yeah, forgot about that one. Yes, Patrik is correct. The files are in osso-wlan-dev, but it's not published for some reason. I'll ask again what's happening. -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: dbus api for wlancond
"ext nic" <[EMAIL PROTECTED]> writes: > I posted a message a week ago about trouble scaning the wifi card for > APs. Apparently there is a bug when using iwlist. I saw a comment > about using the dbus interface to use wlancond directly. However I > can't find documentation for this interface. It has been asked frequently, but I think there's no such documentation currently. But there's definitely a need for it. But it wouldn't be too hard write one. There's only one request and reply IIRC. And osso-wlan sources are available, so you don't have to guess anything: http://repository.maemo.org/pool/maemo3.2/free/source/osso-wlan_1.2.1.tar.gz Maybe you could write one and share it with community? If you have any questions, post them here and I'll try to answer them. -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: WLAN power saving
"ext Klaus Anderson" <[EMAIL PROTECTED]> writes: >> Is there any way to completely disable WLAN power saving on the N800? > > I believe setting the 'wlan_sleep_timeout' and > 'inactive_wlan_sleep_timeout' gconf values to something large will do > what you want. You are correct. Set both of them to 12 and WLAN Power Save Mode will be completely disabled. -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Features to improve the platform
"ext Frantisek Dufka" <[EMAIL PROTECTED]> writes: >> Yeah, we do that also in-house sometimes. It's just pain to setup >> (remove and insert kernel modules etc.), I wish that there would be an >> easier way to do that. > > Never tried usbnet but with bluetooth PAN it is really painless once > you have it set up once (see > http://www.internettablettalk.com/forums/showthread.php?p=52174#post52174 > except the dummy_wlan_down part and default gateway and dns setup). No > messing with modules except inserting bnep.ko once on N770. Thanks. I'll have to try it sometime. > I guess usb can be more problematic if you need usb storage too. Yes, that's a problem. Does USB support multiple profiles at the same time? What I'm after here is that N800 would have both USB mass storage and usbnet enabled concurrently. That would be really cool. > Bluetooth is ideal for this if you have BT on PC (unless you perhaps > care about the WLAN radio part which may be affected by bluetooth). Under really heavy load you might experience some slowdown, but it should work just fine. (I bet that after saying this someone reports a serious problem with the coexistence...) -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Features to improve the platform
"ext Frantisek Dufka" <[EMAIL PROTECTED]> writes: > You don't need Connection manager and maemo IAP connections for ssh. You > can easily bypass it and connect to device over bluetooth PAN or usbnet > and then play with wi-fi and Connection manager to your heart's content > while your ssh connection is still running. Works fine, I have tried > this many times. Yeah, we do that also in-house sometimes. It's just pain to setup (remove and insert kernel modules etc.), I wish that there would be an easier way to do that. -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Question about WLAN
"ext swaroop k.s" <[EMAIL PROTECTED]> writes: > Unfortunately, the problem still remains. I think the bug suggests > that not all visible APs will be reported (4K limit?). That was reporters opinion but I think he is wrong. Unfortunately I didn't get any replies to my questions so I cannot be sure. > But, what I am experiencing is that the scan reports only 1 AP, the > one to which N800 is connected to. I think that's the same problem as in bug report. > I looked at osso-wlan, it sends a ioctl request with SIOCGIWSCAN, and > reports the results. Look again. First osso-wlan sends SIOCSIWSCAN ioctl request, then it waits for SIOCGIWSCAN event from netlink and only after that it will query the results with SIOCGIWSCAN ioctl. > But, for some reason, it just reports one AP. I even tried issuing > SIOCSIWSCAN to initiate a scan, but the call is always returning -1. > I'm not really sure why. See my explanation above. > I did not completely follow how to wait for the wireless scan event. > Can you expand a little more on that? The Wireless Extension events are sent through the netlink interface, for example iwevent uses that. > or point me in the right direction? Grep for SIOCGIWSCAN and SIOCSIWSCAN from osso-wlan. You will figure it out. > But, as I mentioned earlier, if I use the provided UI (to select the > AP), through the "Change Connection.." option, I do get more than 1 > result. So, what is the method call through the "change connection..." > option? is it available to the public? All WLAN scan results go through wlancond (from osso-wlan package). So osso-wlan will provide you all the answers. -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Question about WLAN
"ext swaroop k.s" <[EMAIL PROTECTED]> writes: > I went through the lists to see if I could get my question answered > there, but could not find enough information. > > I am developing an application which will need information about the > visible WiFi access points at periodic intervals. But, (possibly due > to the power saving mode) N800 does not list all the visible APs > through the wireless extensions (iwlist), especially when the device > is already associated with an access point. You are seeing this bug: https://bugs.maemo.org/show_bug.cgi?id=1106 It's a bug in WLAN driver. The results are not ready until driver sends SIOCGIWSCAN event. The results will be partial until the event is sent. > Things I've tried so far: > 1. Tried setting the WLAN_SLEEP_TIMEOUT thorugh gconftool > 2. Tried fiddling with the osso-wlan sources > 3. Tried using the conic api > > But, the problem seems to be something beyond all these? am I right? > Also, I do see there is something that can solve this. Through the > WLAN connectivity UI, if I select "Change connections", I can see all > the access points in the user Interface. So, I think there is a way of > getting this information. Can anyone shed some light on this? > > Does anyone know how to get around this? You can workaround this by waiting for the wireless extensions scan event before getting the scan results from the driver. See how osso-wlan does it. But as I said, this a bug in WLAN driver and will be fixed some time in future. -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: udhcpc and hostname
"ext Guard][an" <[EMAIL PROTECTED]> writes: > hello, > > i logged to my n800 tablet using "ssh [EMAIL PROTECTED]" then changed > /etc/hostname and /etc/hosts files. You should change the device name from UI (Control Panel/Bluetooth). > i chose to use "n800" as the hostname, then rebooted. > > the tablet gets its network connectivity through wifi and i noticed that > the hostname registered with the local dhcp+dns servers setup is always > "nokian800.domain.tld". > > is there a way to configure this from a configuration file ? > > (dhclient has /etc/dhcp3/dhclient.conf send host-name ""; >option). > > or is it currently hardcoded and should i fill a bug ? It's not hardcoded, it should use the device name from Bluetooth Control Panel applet. If not, that's a bug. -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: wifi of 770 goes blind
"ext Neil MacLeod" <[EMAIL PROTECTED]> writes: > I asked the OP via a PM on the ITT forum to post an update to the > mailing list, and he replied that he had replaced the battery which > resolved the issue... quote: > > "I got the wifi working by replaced a battery, therefore I think it's > a power suppily problem." > > Not really sure why a new battery would fix the problem, unless the > act of removing and reinserting the battery reset something. Anyway, > problem solved. :) That sounds really strange, but I have learned that everything is possible. But I'll remember this and see if if this comes up again somewhere else. Thanks for the info! -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: Kismet on the N800/Maemo Platform?
"ext Mike Kershaw" <[EMAIL PROTECTED]> writes: > Once a pile of issues (launching menus, having to load in unofficial > csx1211 kernel modules to keep the wireless from locking up dead on the > 800), etc are fixed What's csx1211 module? And what kind of locking issues are you seeing? -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: wifi of 770 goes blind
"ext Neil MacLeod" <[EMAIL PROTECTED]> writes: > Kalle Valo wrote: >> "ext Long" <[EMAIL PROTECTED]> writes: >> >>> my 770 wifi goes blind all in a sudden, I use a Dlink D614 without >>> any encry. reflash to OS from 2007 hack to 2006 betas and final, >>> the wifi remains blind all the time. tried to power off and >>> detached the battery for a day, still blind. >> What do you mean with blind? Please describe the symptoms in more >> detail. I couldn't understand from your description what's >> happening. >> >> Also, if possible, post the output of dmesg when this happens. > > There is additional background detail in a thread[1] that appeared on > ITT Ah, thanks. These links helped a bit. > in it I asked the OP to post in the developers mailing list as I had > a hunch you might be the best person to assist! :) Good advice. I don't follow any forums (even though way seem to quite active!) because I don't have the time. Gotta do some real work too, you know ;) Please post any WLAN problems to maemo-users list and preferably CC me (so that I don't miss it). I'll try to help as much as I can. > It seems as though the 770 WiFi worked for a short while (2 hours) but > has since failed to work at all - the 770 doesn't detect any networks > despite reflashing with previous, current and hacker edition 770 > firmwares. Hmm, symptoms sound like WLAN firmware is crashing. I would like to see dmesg output. Does it contain "firmware crashed?" messages? Also the message should be in syslog, if syslogd is installed. BTW, installing syslogd was a good advice. Also, I would like to hear if this happens only in one specific location. If he could test it elsewhere where there is less WLAN traffic and APs. It might be related to the radio environment. > Command line tools appear to suggest the WiFi interface is a little > confused[2]. That's a feature. The interface must be up when scanning. So do a 'ifconfig wlan0 up' before running 'iwlist wlan0 scan'. But as you noted, iwlist scan is buggy. I'll fix it. -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: purpose of the interface wlan0:1
"ext Michael Stepanov" <[EMAIL PROTECTED]> writes: >> If you use WEP, check that your WEP key is correct. > > Most probably I put incorrect WEP key. It's only one explanation what I > have. It's also possible that the software is buggy, either in AP or in 770 :) But check the WEP key first. Let's see what happens. -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: wifi of 770 goes blind
"ext Long" <[EMAIL PROTECTED]> writes: > my 770 wifi goes blind all in a sudden, I use a Dlink D614 without > any encry. reflash to OS from 2007 hack to 2006 betas and final, the > wifi remains blind all the time. tried to power off and detached the > battery for a day, still blind. What do you mean with blind? Please describe the symptoms in more detail. I couldn't understand from your description what's happening. Also, if possible, post the output of dmesg when this happens. -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: purpose of the interface wlan0:1
"ext Michael Stepanov" <[EMAIL PROTECTED]> writes: > I have a problem with that interface. After flashing my Nokia770 by its > latest image I cannot connect to the my WiFi access point with wlan0. By > some reason it brings up wlan0:1 instead. I didn't change any connection > settings. So, I have no idea how to solve that problem. I guess DHCP client is not receiving IP from DHCP server, most probably some WLAN problem. Could you provide more details about your setup? For example make and model of the WLAN Access Point and it's settings. If you use WEP, check that your WEP key is correct. -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: RE : Re: RE : Re: Establish wifi connection from command line
"ext magda chelly" <[EMAIL PROTECTED]> writes: > I developed an application to read and scan wifi card > on the Nokia N800, but I discovered in that case the > connection to a wireless network isn't possible du to > fact that the wifi card could not be scanned excatly. > Have someone an idea how to parse this difficulty. Sorry, I don't understand what you are saying here. If you mean that 'iwlist wlan0 scan' does show all scan results, that's this bug: https://bugs.maemo.org/show_bug.cgi?id=1106 -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: RE : Re: Establish wifi connection from command line
"ext magda chelly" <[EMAIL PROTECTED]> writes: > It tells me that the udhcp is not found!!! > I had installed the wireless tools. Sorry, it's udhcpc. Missed the letter c at end. -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: Establish wifi connection from command line
"ext magda chelly" <[EMAIL PROTECTED]> writes: > Please could someone tell me, about the possibilty to > connect my Nokia N800 to a wifi network from command > line. ifconfig wlan0 up iwconfig wlan0 essid mynetworkname udhcp -i wlan0 You need to install wireless-tools package to do that, but I would assume there's a deb available for armel somwhere. -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: connectivity status cb not called.
"ext Antonio Gomes" <[EMAIL PROTECTED]> writes: > solved by replacing old osso_iap by conic api ;) Good. I was just about to recommend you using libconic instead :) -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: format string vuln in the wifi "applet"
"ext Volker Braun" <[EMAIL PROTECTED]> writes: > On a slightly related note, can anyone point me in the right direction > for the implementation of the EAP-TTLS MSchap authentification? That's closed source. Sorry. But what you could do is to port the WLAN driver cx3110x to use the latest wireless extensions and make it work with wpa_supplicant. It shouldn't be too hard. -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: Localhost unavailable when wi-fi offline or not connected
"ext David Hagood" <[EMAIL PROTECTED]> writes: > The current method Maemo uses to detect an application wanting to access > the Internet (by using ld.so tricks to hook into the socket() call) > seems kind of kludgy to me Actually libconic is the preferred way. The preload library is just for unmodified applications. > - why not use the same sort of trick that PPP uses, where a network > interface always exists and is tied to the default route, and when a > packet is delivered to that interface for routing THEN bring up the > appropriate connections. > > It would take modifications to the kernel - ideally some sort of DBUS > message when a packet needs to be routed - but this would remove the > need to hook into applications, and allow ANY app to generate a request > for connection. Sounds a bit complicated to do this in kernel. How would the application notify that it doesn't need the connection anymore? -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: Localhost unavailable when wi-fi offline or not connected
"ext Mike Cowlishaw" <[EMAIL PROTECTED]> writes: > While trying to test this on an aeroplane at the weekend -- with Wi-Fi > offline, of course -- the browser would not connect to the server. I've > since experimented further and find a similar (or the same) problem occurs > online if no Wi-Fi connection is active. > > This is a showstopper for my application as it means I cannot easily view my > data unless online and connected -- is there a fix/workaround? There is/was dummy IAP support which you could use here: http://maemo.org/maemowiki/DummyIAP But it accidentally went kaput at some stage. Patrik, what's the status with that? -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: Fwd: Compiling latest kernel (from kernel.org, linux-omap git version) in n800
"ext Leandro Melo de Sales" <[EMAIL PROTECTED]> writes: > So, finally. Is the unique solution to wait nokia until they release > the umac.ko source and live with n800 + latest linux-omap kernel > version without WLAN support? That's the case, unfortunately. > Kallo, can you please explain us what is the main problem that > nokia doesn't release the umac.ko source code? Sorry, I can't answer. -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: Fwd: Compiling latest kernel (from kernel.org, linux-omap git version) in n800
"ext Andreas Orfanos" <[EMAIL PROTECTED]> writes: > It is against Open Source Software ethics to keep kernel modules > proprietary. Definitely there is a GPL violation here. Nokia's tables > exist today because people kept those GPL moral obligations. > > Release functional source code of umac.ko please. Creating a device like Internet Tablet is not just writing software, it's a lot more. For example, one has to consider hardware design, costs, manufacturing, schedules and other issues. And when all these aspects are combined, the solution isn't always optimal. Just like the case is right now, as you have pointed out. I do understand the frustration of not having umac.ko sources available. I personally believe that having an open driver would improve the quality and make my job a lot easier. But that's just not possible currently and this is something we have to live with. Disclaimer: These are my own opinions and not of Nokia. -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: Fwd: Compiling latest kernel (from kernel.org, linux-omap git version) in n800
"ext Leandro Melo de Sales" <[EMAIL PROTECTED]> writes: > It is a bad news! :( Is there a plan to make umac.ko source code > available? Unfortunately no. > And about cx3110x updates, when do you plan to update it? I cannot make any promises, sorry. > What is the latest linux-omap kernel version that it is possible > to compile cx3110x and flash it into n800? I don't know. -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: init start/stop script won't work when battery is charging
"ext wolfg" <[EMAIL PROTECTED]> writes: > My init script works fine on 770/N800 when not charging. But if the > charger is connected, turn device off then on, it doesn't work. How > to solve this problem? When you turn off with charger connected, only the runlevel is changed. Make sure that your init script run when changing to that runlevel. -- Kalle Valo ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
