Anyway, disabling the avahi.daemon, upgrading and re-enabling it works fine...
Did not had the chance of trying last bypass from lathiat, but will fdbk
if/when I'll do.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Had the same problem on Ubuntu 14.04 64bit.
Solved by installing rdesktop.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1324648
Title:
Dependency on rdesktop package not resolved during install
#24 solved for me: Lenovo W500 with dual graphic disabled in BIOS (use only ATI
3650) and 11.10 Alternate install with full disk encryption (LUKS) with /boot
unencrypted.
Still having trouble with compiz andwobbly windows... but GRUBis fine now.
--
You received this bug notification because
@Everyone: pls make sure, very sure, your HW enables the Wifi chip/radio.
BIOS first, then check hardware buttons/sliders and finally (it's the case with
IBM's and Lenovo's notebooks) the Fn/F5 or any other combo key your PC may
have.
rfkill is very useful to understand which one is off (soft
Chase, you're absolutely right... and I should have known since I've been using
IBM iron all my (technical) life.
W500 is no exception. Let me try this out a bit and I'll be back. Thanks
--
ifconfig returns SIOCSIFFLAGS: Unknown error 132 when running commad ifconfig
wlan0 up
Chase, the idea is good... but, alas, it looks like that both the hard
and the soft switches cannot lift the Hard block on the w500 wireless
wifi device.
Putting rfkill to listen (event) and trying the different combinations
always leave the wifi device (idx 2) hard blocked:
t0:
rfkill list
0:
Chase, I agree with your decision to relate this issue to HW management.
windows is not an option, but I guess I will peer into the BIOS settings as
soon as possible (this means having to wait till this evening). I'll be back as
soon as possible.
By the way, we have 2 other W500 here with Win7
Thanks for your support...
Tried the following:
$ sudo modprobe -r iwl3945
$ sudo rfkill block wifi
$ sudo rfkill unblock wifi
$ sudo modprobe iwl3945
$ sudo ifconfig wlan0 up
SIOCSIFFLAGS: Unknown error 132
$ lsmod | grep -i iw
iwl394574588 0
iwlagn123428 0
Chase, here the telling output:
rfkill list
0: tpacpi_bluetooth_sw: Bluetooth
Soft blocked: no
Hard blocked: no
2: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
3: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
--
ifconfig returns
...and here's the same cmd output run after I switched off the wireless
button on the front on the PC:
rfkill list
0: tpacpi_bluetooth_sw: Bluetooth
Soft blocked: yes
Hard blocked: yes
2: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: yes
feels like the system
Has anyone made any progress on this problem? I had to return to lay
patches in my kitchen... which is rather annoying!
--
ifconfig returns SIOCSIFFLAGS: Unknown error 132 when running commad ifconfig
wlan0 up
https://bugs.launchpad.net/bugs/464559
You received this bug notification because you
No way... tried Lucid this morning for a few minutes, enough to see that on my
Lenovo W500 the Wifi was not enabled and grayed out: same trouble as Karmic.
lsmod and modprobe -l showed the same stuff as that on 9.10.
I've got to work... so if you need other info from 10.04 let me know and I'll
Hello everybody. I've just installed Karmic on a Lenovo Thinkpad W500 sporting
a Intel Wireless WiFi Link 5300 WiFi adapter (I understand the chip should be
the same as the 4965AGN one).
I cannot make either the network-manager to enable the device or the
wpa_supplicant to get access to it...
Hi all,
has anybody pursued this bug further?
I still have shaky wireless connection with Network Manager is the network
signal has a medium stregth (when its below 70% it disconnects happily and I
have to click it back!)
Thanks, Truxpin
--
iwl3945 not able to associate with kernel 2.6.26
.
I'll try to collect dmesg and daemon logs of a disconnection (in my case
I can connect but get a 5mins max up time - then it disconnects... a
couple of clicks and it is connected again and so on).
Truxpin
** Attachment added: filtered daemon.log of a successful NM and wlan0
connection
http
Got very similar problem with nm but with 2.6.24-21.
It looks to me that it may be related to the signal strength and or the
proximity of another AP with signal level close to the one to which i'm
connected at the moment.
If I work at a couple of meter from my home AP nm seems to never lose
16 matches
Mail list logo
