[Bug 159064] Re: error getting ESSID for device eth1: Resource temporarily unavailable [IPW3945]
Thist must be a driver problem so I'm moving it to linux-ubuntu-modules (which holds the iwl3945.ko). ** Changed in: linux-ubuntu-modules-2.6.24 (Ubuntu) Sourcepackagename: network-manager = linux-ubuntu-modules-2.6.24 -- error getting ESSID for device eth1: Resource temporarily unavailable [IPW3945] https://bugs.launchpad.net/bugs/159064 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 159064] Re: error getting ESSID for device eth1: Resource temporarily unavailable [IPW3945]
I have now two times in a row successfully connected to my WLAN! For the first time ever without having to write my WPA2-PSK. Got something strange in the syslog though: Jan 30 20:19:05 pc-thnov-ubuntu kernel: [ 80.269883] WARNING: at /build/buildd/linux-2.6.24/net/mac80211/rx.c:1486 __ieee80211_rx() Jan 30 20:19:05 pc-thnov-ubuntu kernel: [ 80.269890] Pid: 0, comm: swapper Tainted: P2.6.24-5-generic #1 Jan 30 20:19:05 pc-thnov-ubuntu kernel: [ 80.269924] [f8af015f] __ieee80211_rx+0xb7f/0xcb0 [mac80211] Jan 30 20:19:05 pc-thnov-ubuntu kernel: [ 80.270037] [f8b41faf] iwl_rx_queue_restock+0xbf/0x140 [iwl3945] Jan 30 20:19:05 pc-thnov-ubuntu kernel: [ 80.270076] [f8ae231d] ieee80211_tasklet_handler+0xdd/0xf0 [mac80211] Jan 30 20:19:05 pc-thnov-ubuntu kernel: [ 80.270087] [hrtimer_get_next_event+0xe4/0xf0] hrtimer_get_next_event+0xe4/0xf0 Jan 30 20:19:05 pc-thnov-ubuntu kernel: [ 80.270153] [tasklet_action+0x4d/0xc0] tasklet_action+0x4d/0xc0 Jan 30 20:19:05 pc-thnov-ubuntu kernel: [ 80.270168] [__do_softirq+0x82/0x110] __do_softirq+0x82/0x110 Jan 30 20:19:05 pc-thnov-ubuntu kernel: [ 80.270190] [do_softirq+0x55/0x60] do_softirq+0x55/0x60 Jan 30 20:19:05 pc-thnov-ubuntu kernel: [ 80.270198] [irq_exit+0x6d/0x80] irq_exit+0x6d/0x80 Jan 30 20:19:05 pc-thnov-ubuntu kernel: [ 80.270200] [do_IRQ+0x40/0x70] do_IRQ+0x40/0x70 Jan 30 20:19:05 pc-thnov-ubuntu kernel: [ 80.270224] [common_interrupt+0x23/0x30] common_interrupt+0x23/0x30 Jan 30 20:19:05 pc-thnov-ubuntu kernel: [ 80.270245] [native_set_wallclock+0x4b/0x1b0] native_set_wallclock+0x4b/0x1b0 Jan 30 20:19:05 pc-thnov-ubuntu kernel: [ 80.270258] [f886f3e7] acpi_idle_enter_bm+0x25b/0x2ce [processor] Jan 30 20:19:05 pc-thnov-ubuntu kernel: [ 80.270292] [cpuidle_idle_call+0x7c/0xb0] cpuidle_idle_call+0x7c/0xb0 Jan 30 20:19:05 pc-thnov-ubuntu kernel: [ 80.270302] [cpu_idle+0x45/0xd0] cpu_idle+0x45/0xd0 Jan 30 20:19:05 pc-thnov-ubuntu kernel: [ 80.270312] [start_kernel+0x30a/0x3a0] start_kernel+0x30a/0x3a0 Jan 30 20:19:05 pc-thnov-ubuntu kernel: [ 80.270321] [unknown_bootoption+0x0/0x1e0] unknown_bootoption+0x0/0x1e0 Jan 30 20:19:05 pc-thnov-ubuntu kernel: [ 80.270348] === I'm now running linux-image-2.6.24-5-generic (2.6.24-5.8). $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=8.04 DISTRIB_CODENAME=hardy DISTRIB_DESCRIPTION=Ubuntu hardy (development branch) -- error getting ESSID for device eth1: Resource temporarily unavailable [IPW3945] https://bugs.launchpad.net/bugs/159064 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 159064] Re: error getting ESSID for device eth1: Resource temporarily unavailable [IPW3945]
Hmm, next two boots wireless was completely unuseless. $ iwlist wlan0_rename scan wlan0_rename No scan results $ iwconfig wlan0_rename wlan0_rename IEEE 802.11g ESSID: Mode:Managed Channel:0 Access Point: Not-Associated Tx-Power=0 dBm Retry min limit:7 RTS thr:off Fragment thr=2346 B 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 Tried scan for 10-20 times but nothing showed, it only hung for a couple of extra seconds a couple of times. Next boot of the PC 30 minutes later it worked immediately, without writing PSK just as the other successful times. What is needed to take this bug from incomplete to confirmed? -- error getting ESSID for device eth1: Resource temporarily unavailable [IPW3945] https://bugs.launchpad.net/bugs/159064 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 159064] Re: error getting ESSID for device eth1: Resource temporarily unavailable [IPW3945]
hum, well, I'll confirm the bug and see what a network-manager developer will say. ** Changed in: network-manager (Ubuntu) Assignee: Paul Dufresne (dufresnep) = (unassigned) Status: Incomplete = Confirmed -- error getting ESSID for device eth1: Resource temporarily unavailable [IPW3945] https://bugs.launchpad.net/bugs/159064 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 159064] Re: error getting ESSID for device eth1: Resource temporarily unavailable [IPW3945]
Ok. If anyone can point me to a way to setup the connection manually without NetworkManager I could try that. I have NEVER had any problems connecting to my wireless at my workplace which is just WEP encrypted so the problem is either with iwl3945 or wpa_supplicant (my guess). -- error getting ESSID for device eth1: Resource temporarily unavailable [IPW3945] https://bugs.launchpad.net/bugs/159064 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 159064] Re: error getting ESSID for device eth1: Resource temporarily unavailable [IPW3945]
There was https://help.ubuntu.com/community/WifiDocs/WPAHowTo but it seems outdated. I suggest you ask at: https://answers.launchpad.net/ubuntu/+source/network-manager/+addquestion -- error getting ESSID for device eth1: Resource temporarily unavailable [IPW3945] https://bugs.launchpad.net/bugs/159064 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 159064] Re: error getting ESSID for device eth1: Resource temporarily unavailable [IPW3945]
I have now tried with Hardy Alpha 3 and I had problems but I have attached an attempt which finally succeeded. I could not choose my network but I had to manually connect to it. I can't see that it's any better than before. There is a new error message now and the new one reads: Jan 14 21:21:21 ubuntu NetworkManager: WARN request_and_convert_scan_results(): card took too much time scanning. Get a better one. Jan 14 21:21:50 ubuntu last message repeated 2 times Jan 14 21:22:04 ubuntu NetworkManager: WARN request_and_convert_scan_results(): card took too much time scanning. Get a better one. ** Attachment added: syslog http://launchpadlibrarian.net/11338646/syslog -- error getting ESSID for device eth1: Resource temporarily unavailable [IPW3945] https://bugs.launchpad.net/bugs/159064 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 159064] Re: error getting ESSID for device eth1: Resource temporarily unavailable [IPW3945]
Hardy seems to support both drivers: ipw3945 and iwl3945. Some bug info I read suggest that iwl3945 is also available on 7.10 (Gutsy). Seems unlikely that ipw3945 will be fixed. So I guess you could forget requested information. What will really needed is to test latest Hardy. A new test version (Hardy Alpha 3) should come thursday (tomorrow), most probably accessible by friday. So what would really be helpful would be to test it. Watch http://www.ubuntu.com/testing/ That said, iwl3945 is known to have bugs: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/177624 (very poor signal reception) https://bugs.launchpad.net/ubuntu/+source/linux-ubuntu-modules-2.6.22/+bug/176271 (upload and download speed very different, not conviced it is a bug) https://bugs.launchpad.net/bugs/181255 (wireless LED is never on) https://bugs.launchpad.net/ubuntu/+bug/178530 (not working on Hardy alpha 2 for him) https://bugs.launchpad.net/ubuntu/+source/linux-ubuntu-modules-2.6.22/+bug/176602 (On Gutsy, cannot connect to encrypted (WEP or WAP) fixed in Hardy) https://bugs.launchpad.net/ubuntu/+source/linux-ubuntu-modules-2.6.22/+bug/130457 (supposedly just fixed in Hardy, Failure to suspend, shutdown, or hibernate) Well, that's mostly it. iwl3945 does not need anymore a daemon like ipw3945 did (ipw3945d). Well, good luck! -- error getting ESSID for device eth1: Resource temporarily unavailable [IPW3945] https://bugs.launchpad.net/bugs/159064 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 159064] Re: error getting ESSID for device eth1: Resource temporarily unavailable [IPW3945]
I'm attaching output from commands suggested in the Wiki. I have made some in-line comments in the logfile. ** Attachment added: syslog.log http://launchpadlibrarian.net/11213504/syslog.log -- error getting ESSID for device eth1: Resource temporarily unavailable [IPW3945] https://bugs.launchpad.net/bugs/159064 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 159064] Re: error getting ESSID for device eth1: Resource temporarily unavailable [IPW3945]
Maybe this attachment can be useful, a logfile containing a successful connect with another PCCARD which I inserted in the same laptop as I have problems using the Intel card on. ** Attachment added: syslog2.log http://launchpadlibrarian.net/11213522/syslog2.log -- error getting ESSID for device eth1: Resource temporarily unavailable [IPW3945] https://bugs.launchpad.net/bugs/159064 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 159064] Re: error getting ESSID for device eth1: Resource temporarily unavailable [IPW3945]
Reading syslog_small.txt, I find surprising the following: Nov 27 21:11:02 localhost NetworkManager: info Activation (eth1) Stage 2 of 5 (Device Configure) complete. Nov 27 21:11:02 localhost kernel: [ 2716.304000] ipw3945: Detected geography ABG (13 802.11bg channels, 23 802.11a channels) Nov 27 21:11:10 localhost NetworkManager: WARN nm_device_802_11_wireless_get_essid(): error getting ESSID for device eth1: Resource temporarily unavailable Nov 27 21:11:10 localhost kernel: [ 2723.90] ipw3945: Detected geography ABG (13 802.11bg channels, 23 802.11a channels) Nov 27 21:11:12 localhost ntpd[6640]: Deleting interface #5 eth1, fe80::218:deff:fe6f:5cfe#123, interface stats: received=0, sent=0, dropped=0, active_time=2400 secs Nov 27 21:11:17 localhost kernel: [ 2731.50] ipw3945: Detected geography ABG (13 802.11bg channels, 23 802.11a channels) Nov 27 21:11:25 localhost kernel: [ 2739.10] ipw3945: Detected geography ABG (13 802.11bg channels, 23 802.11a channels) Nov 27 21:11:32 localhost kernel: [ 2746.70] ipw3945: Detected geography ABG (13 802.11bg channels, 23 802.11a channels) Nov 27 21:11:40 localhost kernel: [ 2754.304000] ipw3945: Detected geography ABG (13 802.11bg channels, 23 802.11a channels) Nov 27 21:11:48 localhost NetworkManager: WARN nm_device_802_11_wireless_get_essid(): error getting ESSID for device eth1: Resource temporarily unavailable What is that? ntpd (time synchronization protocol) deciding to delete eth1? It makes me wonder if removing ntp package (you have it installed?) would help. I note that bug #163981 have the same message with same card, but is about firmware not loading (probably not releted, but who knows for sure). -- error getting ESSID for device eth1: Resource temporarily unavailable [IPW3945] https://bugs.launchpad.net/bugs/159064 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 159064] Re: error getting ESSID for device eth1: Resource temporarily unavailable [IPW3945]
bug #139642 (state:new) may have some related info, notably links to forums. -- error getting ESSID for device eth1: Resource temporarily unavailable [IPW3945] https://bugs.launchpad.net/bugs/159064 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 159064] Re: error getting ESSID for device eth1: Resource temporarily unavailable [IPW3945]
About ntpd, I think that is only that it deletes eth1 from it's source of possible interfaces to reach an ntp server. -- error getting ESSID for device eth1: Resource temporarily unavailable [IPW3945] https://bugs.launchpad.net/bugs/159064 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 159064] Re: error getting ESSID for device eth1: Resource temporarily unavailable [IPW3945]
Searching for bugs around ipw3945 show many: https://bugs.launchpad.net/ubuntu/+bugs?field.searchtext=ipw3945orderby=-importancesearch=Searchfield.status%3Alist=NEWfield.status%3Alist=INCOMPLETE_WITH_RESPONSEfield.status%3Alist=CONFIRMEDfield.status%3Alist=TRIAGEDfield.status%3Alist=INPROGRESSfield.status%3Alist=FIXCOMMITTEDfield.assignee=field.bug_reporter=field.omit_dupes=onfield.has_patch=field.has_no_package= Among them, bug #72925 is similar. -- error getting ESSID for device eth1: Resource temporarily unavailable [IPW3945] https://bugs.launchpad.net/bugs/159064 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 159064] Re: error getting ESSID for device eth1: Resource temporarily unavailable [IPW3945]
Also bug #134915 have some strange tricks. I don't understand much of that as a bug triager. -- error getting ESSID for device eth1: Resource temporarily unavailable [IPW3945] https://bugs.launchpad.net/bugs/159064 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 159064] Re: error getting ESSID for device eth1: Resource temporarily unavailable [IPW3945]
Possibly that bug #113645 is a duplicate. -- error getting ESSID for device eth1: Resource temporarily unavailable [IPW3945] https://bugs.launchpad.net/bugs/159064 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 159064] Re: error getting ESSID for device eth1: Resource temporarily unavailable [IPW3945]
hum, did I mention: http://www.intel.com/support/wireless/wlan/sb/cs-006205.htm -- error getting ESSID for device eth1: Resource temporarily unavailable [IPW3945] https://bugs.launchpad.net/bugs/159064 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 159064] Re: error getting ESSID for device eth1: Resource temporarily unavailable [IPW3945]
Zorael of bug #134915 suggest in: http://ubuntuforums.org/showthread.php?t=205586page=2 that maybe the driver module is sleeping (which would explain 'ressource temporarily unavailable' and give a link to the documentation of the driver: http://ipw3945.sourceforge.net/README.ipw3945 that give some info about power management inside ipw3945 module. -- error getting ESSID for device eth1: Resource temporarily unavailable [IPW3945] https://bugs.launchpad.net/bugs/159064 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 159064] Re: error getting ESSID for device eth1: Resource temporarily unavailable [IPW3945]
Where I have said bug #134915, you should have read :-) bug #134515 -- error getting ESSID for device eth1: Resource temporarily unavailable [IPW3945] https://bugs.launchpad.net/bugs/159064 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 159064] Re: error getting ESSID for device eth1: Resource temporarily unavailable [IPW3945]
bug #139642 have a surprising to me workaround: blacklist IPV6 Andy Leeman wrote: In a terminal; sudo gedit /etc/modprobe.d/blacklist Then add; #still trying to fix the gd wireless (or some other comment so you rememberwhy it was done) blacklist ipv6 May be worth to try. -- error getting ESSID for device eth1: Resource temporarily unavailable [IPW3945] https://bugs.launchpad.net/bugs/159064 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 159064] Re: error getting ESSID for device eth1: Resource temporarily unavailable [IPW3945]
I have tried blacklisting ipv6 but that doesn't seem to help and also played with iwpriv set_power but found that it is default to disabled (6 (AC) OFF) if AC is connected. I have been able to get my connection twice after unloading (modprobe -r) ipw3945 and re-loading (modprobe) it again. After a restart I tried it again but now I've tried it three times without managing to get a connection. I also get lots of rows about 'Detected geography ABG ...' and after enabling logging from ipw3945d I can see in that file that I very frequently get 'WARNING: In scan; requesting concurrent scan.' -- error getting ESSID for device eth1: Resource temporarily unavailable [IPW3945] https://bugs.launchpad.net/bugs/159064 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 159064] Re: error getting ESSID for device eth1: Resource temporarily unavailable [IPW3945]
I am just now realizing that Intel now consider ipw3945 driver deprecated. The new driver being iwlwifi. It is at: http://intellinuxwireless.org/ They have also their mac80211 project. And is in the main linux kernel at: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=tree;f=drivers/net/wireless/iwlwifi;h=ddfe649a582a964cd84f63eb965add036e74448d;hb=4150c57212ad134765dd78c654a4b9906252b66d -- error getting ESSID for device eth1: Resource temporarily unavailable [IPW3945] https://bugs.launchpad.net/bugs/159064 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 159064] Re: error getting ESSID for device eth1: Resource temporarily unavailable [IPW3945]
Thank you Thomas for this fast response. Well, frankly I was surprised that ipv6 had a link with that. I also get lots of rows about 'Detected geography ABG ...' yeah, seen that, others have reported that too, I don't know what to think, at least I am not convinced it is an error message. after enabling logging from ipw3945d I can see in that file that I very frequently get 'WARNING: In scan; requesting concurrent scan.' nice, how to you enable that logging? 'WARNING: In scan; requesting concurrent scan.' much like if scan was not supported and never finished, so an other scan request come in before the first one finished I begin to have a new vague hypothesis. In your log you have: Nov 27 21:11:48 localhost NetworkManager: WARN nm_device_802_11_wireless_get_essid(): error getting ESSID for device eth1: Resource temporarily unavailable Note the 802_11 part, refering to wireless protocol as far as I know. In the ipw3945 it is said: 3.6. IEEE 802.11h Details --- Only BASIC reporting is supported; CCA and RPI are optional and not implemented. The driver currently does not respond with the appropriate refusal frame if it receives a request that it will not provide a report for. Maybe this is exactly what is going on, driver receiving a request for which it is not responding with appropriate refusal frame. Well, I begin to think that I am clueless. It really begin to feel like a kernel bug to me. So I guess I will just ask you the usual information for kernel bug, then confirmed this bug so as to let a real developer take a look. Please include the following additional information, if you have not already done so (pay attention to lspci's additional options), as required by the Ubuntu Kernel Team: 1. Please include the output of the command uname -a in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture. 2. Please run the command dmesg dmesg.log after a fresh boot and attach the resulting file dmesg.log to this bug report. 3. Please run the command sudo lspci -vvnn lspci-vvnn.log and attach the resulting file lspci-vvnn.log to this bug report. For your reference, the full description of procedures for kernel- related bug reports is available at [WWW] http://wiki.ubuntu.com/KernelTeamBugPolicies. Thanks in advance! -- error getting ESSID for device eth1: Resource temporarily unavailable [IPW3945] https://bugs.launchpad.net/bugs/159064 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 159064] Re: error getting ESSID for device eth1: Resource temporarily unavailable [IPW3945]
And there is many bug similar on http://intellinuxwireless.org/ for the deprecated ipw3945 project: http://bughost.org/bugzilla/buglist.cgi?short_desc_type=allwordssubstrshort_desc=product=IPW3945long_desc_type=allwordssubstrlong_desc=bug_file_loc_type=allwordssubstrbug_file_loc=bug_status=NEWbug_status=REOPENEDemailassigned_to1=1emailtype1=substringemail1=emailassigned_to2=1emailreporter2=1emailcc2=1emailtype2=substringemail2=bugidtype=includebug_id=changedin=chfieldfrom=chfieldto=Nowchfieldvalue=newqueryname=field0-0-0=nooptype0-0-0=noopvalue0-0-0=order=bugs.bug_id -- error getting ESSID for device eth1: Resource temporarily unavailable [IPW3945] https://bugs.launchpad.net/bugs/159064 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 159064] Re: error getting ESSID for device eth1: Resource temporarily unavailable [IPW3945]
I'm afraid that was a bit too hasty. I only managed to connect that one time, the following maybe 20-30 connects have failed but it works fine if I try to boot up XP instead. This is still very much an issue. -- error getting ESSID for device eth1: Resource temporarily unavailable [IPW3945] https://bugs.launchpad.net/bugs/159064 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 159064] Re: error getting ESSID for device eth1: Resource temporarily unavailable [IPW3945]
I have upgraded to network-manager 0.6.5-0ubuntu16.7.10.0 and this seems to have helped! Just now I successfully connected to my wireless network at home for the first time without any problem (except for that I got a prompt about the WPA2 PSK). -- error getting ESSID for device eth1: Resource temporarily unavailable [IPW3945] https://bugs.launchpad.net/bugs/159064 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 159064] Re: error getting ESSID for device eth1: Resource temporarily unavailable [IPW3945]
You may want to try to activate the -proposed repository. It may help at least to avoid the crash, even if I doubt it will help for more. To activate it, open Synaptic, open Menu Settings/Repositories, select Update tab, there I hope you will find the pre-released updates (gutsy-proposed). And then click Reload, and see if you get new version for update-manager package. This is associated with bug #145683. ** Changed in: network-manager (Ubuntu) Assignee: (unassigned) = Paul Dufresne (dufresnep) Status: New = Incomplete -- error getting ESSID for device eth1: Resource temporarily unavailable [IPW3945] https://bugs.launchpad.net/bugs/159064 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 159064] Re: error getting ESSID for device eth1: Resource temporarily unavailable [IPW3945]
Didn't really get the part about tail -n0 /var/log/syslog /tmp/syslog, this just produces an empty file? Yeah, I had the same problem. I edited the page to add -f option (follow the file) that way, it just wait that new information be written to /var/log/syslog and write it in /tmp/syslog. Reread https://wiki.ubuntu.com/DebuggingNetworkManager -- error getting ESSID for device eth1: Resource temporarily unavailable [IPW3945] https://bugs.launchpad.net/bugs/159064 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
