This bug was filed against a series that is no longer supported and so
is being marked as Won't Fix. If this issue still exists in a supported
series, please file a new bug.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
On 11-07-14 02:29 PM, Brad Figg wrote:
This bug was filed against a series that is no longer supported and so
is being marked as Won't Fix. If this issue still exists in a supported
series, please file a new bug.
Ahhh. The old ignore bugs until the automated script comes along and
closes them
** Tags removed: regression-potential
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/464559
Title:
ifconfig returns SIOCSIFFLAGS: Unknown error 132 when running commad
ifconfig wlan0 up
--
** Changed in: linux (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/464559
Title:
ifconfig returns SIOCSIFFLAGS: Unknown error 132 when running commad
** Tags added: acpi-parse-exec-fail
** Tags added: embedded-controller
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/464559
Title:
ifconfig returns SIOCSIFFLAGS: Unknown error 132 when running
Jeremy Foshee wrote on 2010-06-14 (less than a month after the most recent post
to this bug):
This bug report was marked as Incomplete and has not had any updated comments
for quite some time. As
a result this bug is being closed. Please reopen if this is still an issue in
the current
I know this has been closed. I don't think it should, since many people
are affected by this. Today, I found the post with a probable solution.
It seems, indeed that it has to do with the SOFT and HARD locks. The
link to the solution is posted at the end of:
Sorry to bother you again, but this is not solved for me yet. I changed
my location and the wlan does not detect any networks. I wonder why.
Doing
modprobe -r ath5k
rfkill block wifi
rfkill unblock wifi
modprobe ath5k
ifconfig wlan0 up
results in: SIOCSIFFLAGS: Unknown error 132
--
ifconfig
SOLVED on 2 machines!
I tryed ALL things including recompiling drivers etc..
On Ubuntu 10.04(ath5k on Acer One) i solved with:
- (for a temporary solution) try the rfkill thingy(rmmmod ath5k;rfkill block
all;rfkill unblock all;modprobe ath5k;rfkill unlock all;ifconfig wlan0 up)
- finally solved
Jan,
Please open a new bug for your issue. This bug was expired due to lack of a
response from the original reporter.
Thanks!
~JFo
** Changed in: linux (Ubuntu)
Status: New = Invalid
--
ifconfig returns SIOCSIFFLAGS: Unknown error 132 when running commad ifconfig
wlan0 up
After turning on the WLAN card wifi doesn't work.
Wifi module: ath5k
System: Linux mrstrauss-laptop 2.6.32-22-generic #36-Ubuntu SMP Thu Jun 3
19:31:57 UTC 2010 x86_64 GNU/Linux
Description: Ubuntu 10.04
Release: 10.04
Network manager tells Funknerzwerk deaktiviert (wlan disabled) in applet.
This bug report was marked as Incomplete and has not had any updated
comments for quite some time. As a result this bug is being closed.
Please reopen if this is still an issue in the current Ubuntu release
http://www.ubuntu.com/getubuntu/download . Also, please be sure to
provide any requested
** Tags added: kernel-net
--
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 are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
vasdi, What do you mean by Try to push it during the BIOS.? Do you
mean while youre in the BIOS config or while in the bootup POST screen?
--
ifconfig returns SIOCSIFFLAGS: Unknown error 132 when running commad ifconfig
wlan0 up
https://bugs.launchpad.net/bugs/464559
You received this bug
Do you have a wifi button? Try to push it during the BIOS. For some
reason it helped me.
--
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 are a member of Ubuntu
Bugs,
I had the same problem as mentioned above on my EEEpc 1005HA running the
netbook remix of Lucid Beta 2 (I had no problems with Karmic):
i.e. rfkill list showed:
...
2: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
After reading through all of this, I checked the BIOS and found that
** Changed in: linux (Ubuntu)
Status: Triaged = Incomplete
--
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 are a member of Ubuntu
Bugs, which is subscribed to
@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 Douglas wrote:
@TDB:
I'll only make this comment once. The issues outlined in this bug seem
to be hardware issues. We have diagnosed them down to hard blocks in the
hardware that are keeping wifi from being enabled. There is nothing that
can be done from within linux of any form to
I have a laptop here that I upgraded to 9.10, this issue then suddenly
appeared. This issue did not exist prior to 9.10.
Same here!
@Chase Douglas: I don't know what you're talking about... what hard
switches? There are no hard switches in these laptops. Just throw in 9.04 or
windows and the
Agreed. Using Ubuntu since eft, and the issue with wireless got a lot
better with Jaunty. Through Jaunty, and Intrepid I was not experience
any issues with wireless, even Ath or broadcom. Enter, Karmic and these
issues have magically cropped back up.
Note, as has pointed out this is a kernel bug,
I got mixed up in this bug report. Part of the problem is that there are
many rfkill issues on different hardware. I was working with Truxpin for
a while, and his issue is different than the original issue reported in
this bug. So we need to clean things up a bit to ensure we have
everything
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:
@Truxpin:
If you still have Windows around, you may want to try booting into it to
see if you can enable wifi in windows. Maybe the windows driver can
unblock the hard block somehow? You should also double check your bios,
as there may be a switch in there for wireless.
--
ifconfig returns
@Everyone:
First, everything in this bug looks to be hardware related due to all
the rfkill issues. The issues are not related to Lucid or Karmic or any
other Linux, unfortunately. Because of this, I am moving the bug state
to Invalid so that it is removed from the bugs we are tracking as
Sure! Let's swipe it under the carpet and ship Lucid with broken wifi
stack (yet again)! Sorry...
On Wed, Mar 3, 2010 at 9:11 AM, Chase Douglas
chase.doug...@canonical.com wrote:
@Truxpin:
If you still have Windows around, you may want to try booting into it to
see if you can enable wifi in
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
@TDB:
I'll only make this comment once. The issues outlined in this bug seem
to be hardware issues. We have diagnosed them down to hard blocks in the
hardware that are keeping wifi from being enabled. There is nothing that
can be done from within linux of any form to turn off a hard block. If
the
@Truxpin:
A relative of mine recently bought a Lenovo Y450. Even under windows, we
couldn't get wireless to work out of the box as it came from the factory
(amazing engineering there...). We finally found out through a google
search that there are two rf switches (I cannot fathom why they thought
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
@Truxpin:
I'm just learning about rfkill myself. Can you try running 'rfkill
list'?
--
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 are a member of Ubuntu
Bugs, which
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
@Truxpin:
Can you try the rfkill workaround mentioned in comment #4?
--
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 are a member of Ubuntu
Bugs, which is subscribed
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
Could someone please test lucid to determine if the issue still
persists? Booting a daily live cd build should be sufficient:
http://cdimage.ubuntu.com/daily-live/current/
Thanks
--
ifconfig returns SIOCSIFFLAGS: Unknown error 132 when running commad ifconfig
wlan0 up
Triaged for let the developers get further information
** Tags added: regression-potential
** Changed in: linux (Ubuntu)
Status: Incomplete = Triaged
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
--
ifconfig returns SIOCSIFFLAGS: Unknown error 132 when running commad
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...
Update: Tested Karmic system 4 feet (1 meter) from access point, same problems.
Tested same system using Windows 2000 at 4' and at 20' (7 meters), no problem.
Tested Karmic w/100 Mbps 3COM wired Ethernet, no problem wired. Disabled wired
/ enabled wireless, same problems.
--
ifconfig returns
Same here as AZ wrote. I have exactly the same WiFi chip as AZ (lsusb:
Bus 001 Device 007: ID 148f:2570 Ralink Technology, Corp. 802.11g WiFi).
The workaround using rfkill works only party for me. I only have a very,
very low bandwidth with the device and the connection is very unstable.
By the
I've the same problem with a rt2500usb (148f:2570 Ralink Technology,
Corp. 802.11g WiFi) on karmic 32bit and 2.6.32 does not fix this for me.
The workaround using rfkill does work for me.
--
ifconfig returns SIOCSIFFLAGS: Unknown error 132 when running commad ifconfig
wlan0 up
I should also add I'm using a DESKTOP system with Linksys WMP54G v3
wireless NIC. There is no 'disable wireless networking' button on the
desktop.
I am NOT using NDIS wrapper, but using the Broadcom drives directly (see
'drivers' section below).
lspci -vnn | grep 14e4
14e4:4320 BCM4306
** Tags added: karmic
--
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 are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I am running kernel 2.6.31-17-generic and discovered 'ifconfig wlan0 up' does
not work,
BUT
ifconfig wlan0 192.168.0.2 netmask 255.255.255.0 up
works fine!!!
'ifconfig wlan0 down' when the device is already down won't let it come
back up without a system reboot.
Basically, it seems any
Hi all,
Please can you try with last kernel version, which is located on
http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.32/
Thanks in advance.
** Changed in: linux (Ubuntu)
Status: New = Incomplete
--
ifconfig returns SIOCSIFFLAGS: Unknown error 132 when running commad ifconfig
System: Linux ubuntu 9.10
kernel: 2.6.31-17-generic-pae #54-Ubuntu SMP Thu Dec 10 17:23:29 UTC 2009 i686
GNU/Linux
wlan card: RT2500 USB (build in card)
error at the step:
ifconfig wlan0 up
SIOCSIFFLAGS: Unknown error 132
--
ifconfig returns SIOCSIFFLAGS: Unknown error 132 when running commad
Same problem here, but now when I upgrade the kernel to the nevest
version: 2.6.31-17-generic on 2.6.31-16-generic works correctly, I cant
locate the error, don't know how to debug it with dgb, so I can't paste
a debug symbols or something else. Syslog nothing return when I type:
sudo ifconfig
I am experience the same issue for an ath9k device on HP DV7 3060US
Wifi module: ath9k
System: Linux ubulap 2.6.31-17-generic #54-Ubuntu SMP Thu Dec 10 17:01:44 UTC
2009 x86_64 GNU/Linux
lspci
Card:08:00.0 Network controller: Atheros Communications Inc. AR928X Wireless
Network Adapter
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/34674099/AlsaDevices.txt
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/34674101/BootDmesg.txt
** Attachment added: Card0.Amixer.values.txt
On my MSI M670 Laptop (Kernel wifi module rt61pci) the same problem came up
after upgrading to Karmic.
The problem was caused by wifi on/off hardware button, which suddenly started
to work (it never worked before).
After pressing this button the system brought the interface up automatically
Many thanks for help but threre is no hardware button on my EEE PC.
There is only keyboard shortcut which doesn't work either. I think it
is kernel problem because i found similar problems on other
distributions forums. I hope it will be repaired soon.
2009/10/30 apocalyp_sys
I'm also affected by this bug. I didn't had a clue about what happened at first
until I saw this post. Then I tried to reproduce the flasher's workaround by
doing only:
modprobe -r ath9k
rfkill block wifi
rfkill unblock wifi
modprobe ath9k
while NetworkManager was still running, and eeePC
The problem is that if I not execute workaround script I'm not able to
activate my wifi interface. So I guess it is not Network manager bug
because it is trying to activate interface automaticaly but it is not
possible before executing workaround script. So maybe there is problem
between wifi
55 matches
Mail list logo
