@Pablo,
The 'wapf=4' parameter is applicable ONLY to 'asus-nb-wmi' driver. What
you have created will simply be ignored as this parameter does not exist
for rtlwifi driver.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The recommended method now is sudo apt-get install
firmware-b43-installer, if a temporary connection can be arranged to
download the firmware from internet.
Alternatively, if the target system can't be connected to internet, the
entire b43 firmware directory can also be extracted and copied from
Just because I'm affected too. Really annoying when you need at least
the real size!
Ubuntu 12.04, nautilus 3.4.2.
I'm sure I noticed it on a Live session of Ubuntu 14.04.1 also, but
can't be sure as I don't have a way to check it right now.
--
You received this bug notification because you
Xprogrammer,
Could you give us the pastebin link to you full wireless_script report?
: http://ubuntuforums.org/showpost.php?p=13024222
In case it is not directly related to the bug, an Ubuntu Forums thread
(or IRC channel #ubuntu) may be a better place for further
troubleshooting, if possible at
Hello Graham,
I've been following this bug for quite sometime, just out of curiosity.
However, many of the comment posts here look like common issues that may
or may not be related to this particular bug. Yours sounds similar. Oh,
but not really same as #205 (Venkatesha). His was not connecting
It's in the upper right of the page as dmesg.log.
Yup, found that now, a place I never noticed before.
Also, your problem may indeed be related to this bug, I'm just not sure
and I know there are some other reasons too leading to same or similar
behaviour. So potentially is the keyword in your
And I very seriously believe that it is the /DEBIAN/control file
within the .deb package that is causing the trouble.
Line #15 in it seems to be an accidental copy-paste, confusing dpkg (a
super long Modalias line). Needs to be fixed (deleted) immediately
before plenty of more The update broke my
Hmm.. so I guess we finally completed a full circle to get back to the
old-school sudo apt-get firmware-b43-installer huh? Nice!
Does anyone already have the right to distribute I hate Broadcom badges? Caps
T-Shirts maybe?
If not, I'd love to grab the opportunity.
--
You received this bug
@adam,
If it is not a UEFI based installation, try a BIOS reset (to factory
defaults). Or, if it is dual-booting with Windows 8, try a hot-reboot
while the wifi is active.
If these don't help, I suggest you start a thread at ubuntuforums.org
with the description of the problem and the
Just dealt with the problem of an affected user here :
http://ubuntuforums.org/showthread.php?t=2240240
But I guess adding myself to the Affects Me list would be cheating?
Since it is not me who is affected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@adam,
Xubuntu Live will be okay. Not all fixes/workarounds can be tried on a Live
System. But let's just see an initial report first.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1173681
Title:
@Adam,
If you have an Ubuntu Forums thread about your problem, I'd like to see
the wireless_script report on it.
Wireless_script : http://ubuntuforums.org/showpost.php?p=13024222
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
update: updated the BIOS to the latest version but the problem persists.
Booting with the older kernel (latest linux kernel from 12.10) every thing
works fine. After upgrading to Raring Ringtail Ubuntu 13.04, with the new
kernel, hardware get blocked/disabled and
Based on confirmations in comment #59 here, and comment #22 in the
related bug #1277959 , I have edited the ubuntuforums post
(http://ubuntuforums.org/showthread.php?t=2181558) to change the wapf
value from 1 to 4, and added the request to post the command output for
model number.
Still unsure
@Ant,
Your model does not use the asus_nb_wmi driver which the bug is about,
so your problem is not related to this particular bug, nor is the
workaround for you. Blindly applying patches/workarounds not meant for
your model would only make the problem worse.
If you have a thread on the problem
Until this bug gets fixed, a working workaround :
http://ubuntuforums.org/showthread.php?t=2181558
Post #1 of the above thread is about how to enable the WiFI, Post #2 is a crude
workaround for the Fn+F2 keys.
Hope it gets permanently fixed before next LTS (14.04) is out. It has
already been
@sioban,
For UEFI issues, this might be helpful :
http://ubuntuforums.org/showthread.php?t=2147295
If you are on the forums (ubuntuforums.org), and have any wifi threads, let me
know. I'd be interested in looking at it.
--
You received this bug notification because you are a member of Ubuntu
Not promoting the WORKAROUND here, but as long as people coming to this page
have to resort to it, I've re-written it in a cleaner and more comprehensive
manner in this thread : http://ubuntuforums.org/showthread.php?t=2181558
(also includes how to quickly completely revert back)
Post #1 in it
Hello Rahul,
Did the link provided by Dave work for you?
I am trying to troubleshoot the same problem for a different user here
(particularly from post #11 onwards) -
http://ubuntuforums.org/showthread.php?t=2083339
The modem does not get probed as a modem because its VID:PID
19 matches
Mail list logo
