$ md5sum /lib/firmware/rtlwifi/rtl8192cfw.bin
fd118c183ad9e11060a6e575b472280e /lib/firmware/rtlwifi/rtl8192cfw.bin
Saw this and also noticed that I had another file (same name, but with
.bin.bak extension) that matched the md5sum @Larry posted, so I swapped
them around and ran
$ sudo rmmod
Koen: I'm glad that resolved things for you.
However, simply copying in the RealTek-supplied firmware has never made
any difference for me. It's not just a simple matter of what is/isn't
packaged with Ubuntu, as far as all my efforts to date go.
--
You received this bug notification because you
Well, no, we can't. I can't, at least.
Look, I came here to report that I was having issues with a particular
card. It doesn't work the way it's supposed to. I'm here because this is
the open-source community's forum for announcing and working toward
fixing bugs in arbitrary, probably-proprietary
Echoing the incredulity of this being marked invalid.
This is still very much a problem and continues to affect distros into
13.04 with the specific card mentioned. The card, as mentioned, cannot
be easily swapped due to hardware whitelisting by Lenovo, so a solution
is still necessary.
Please
** Changed in: linux (Ubuntu)
Status: Invalid = Confirmed
** Changed in: linux (Ubuntu Precise)
Status: Invalid = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/902557
Title:
Are there any negative reprocussions that might result from uninstalling
acpi-support and acpid?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/902557
Title:
Wireless not working in 12.04 for
I was afraid of that; the system having this trouble for me is a laptop,
so I'm leery of removing those.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/902557
Title:
Wireless not working in 12.04
No joy for me, Pauli. I tried simply copying the firmware included with
the new driver into /lib/firmware/rtlwifi and verified the SHA1 sum
matched the one you listed. I rebooted the machine (to avoid dealing
with any rmmod/modprobe shenanigans) and continue to see ~10% packet
loss due to repeated
Sorry, I thought I made it clear with my reply that I checked the
sha1sum on the firmware and it matched the one you listed.
No joy for me, Pauli. I tried simply copying the firmware included with
the new driver into /lib/firmware/rtlwifi and verified the SHA1 sum
matched the one you listed.
Just tried that, a7x. If anything, performance actually seems worse now.
I'm now seeing close to 40% packet loss coupled with rapid, frequent
Reason 6 dissociations (the cause of said packet loss).
My /lib/firmware/rtlwifi/rtl8192cfw.bin still has the sha1 sum listed by
Pauli earlier, so
Thanks, peter b, but I'm not even at that stage yet. The issue I am
having is that I cannot compile the driver because of apparent code
errors reported by the compiler.
If/when I can get the thing to compile, I will be sure to follow your
tips from #193/194.
--
You received this bug
Paul, can you post the exact steps you went through to obtain and build
both the latest driver and firmware, just so we have it here for
posterity?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/902557
For my part, I cannot get past the MAKE portion due to an apparent Error
in the included pci.h file on line 247.
error: expected '=', ',', ';', 'asm' or '__attribute__' before
'rtl_pci_probe'
This causes an Error 1 building base.o, which then causes an Error 2 in
the overall process. I'm afraid
I did. For my part, I cannot get past the MAKE portion due to an
apparent Error in the included pci.h file on line 247.
Here's uname -a, as well:
Linux *** 3.8.0-27-generic #40-Ubuntu SMP Tue Jul 9 00:17:05 UTC 2013
x86_64 x86_64 x86_64 GNU/Linux
Here's the full output from make:
Public bug reported:
Upgraded to Raring last night and since doing so, the tray indicator for
XChat is no longer present. There's an entry for XChat under the
messaging center icon, but it does not react when alert events
(highlight, channel message, etc.) trigger.
Previously, I was using the
I have installed the new driver, confirmed that it is being used (or, at
least, that the date on the driver in /lib/modules/3.5.0-23-generic/
that matches the name of the driver listed in lspci -v matches today's
date), and can at least report that it does not offer worse performance
(that is, I
No improvement with the new driver/firmware. Still seeing 10-20% packet
loss, due to Reason 6 dissociation errors.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/902557
Title:
Wireless not working
This is the file listed on RealTek's website in their download section,
to which I thought you referred in comment #203.
Linux driver for kernel 2.6.24 (and later) 0011.0128.2013
2013/1/28 12823k
I downloaded this driver and ran make, make install.
--
You received this bug
@Ekimia: Rev 01.
Is there some field other than srcversion I should be checking to verify
whether or not I'm using the new driver?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/902557
Title:
Just after I posted that, it dawned on me to just check the file date of
the .ko file listed in modinfo. Sure enough, I'm using the drivers from
/lib/modules/3.5.0-18-generic/updates/cw-3.6 (file date in mid-October)
instead of /lib/modules/3.5.0-18-generic/kernel/drivers/net/wireless,
which have
Okay, I uninstalled compat-wireless and restarted the system. modinfo
rtlwifi, et. al. now show each of the modules pointing at the correct
driver file, with the expected file date of yesterday.
However, I'm still getting ~10% packet loss even with the new driver,
and still seeing a ton of Reason
I had installed compat-wireless yesterday, but uninstalled it between
#182 and #184 (as mentioned in the first line of #184). The drivers I'm
presently using are ones I compiled yesterday from the RealTek website's
download section, with version 0007.*
To ensure that having compat-wireless
No, modprobe is not pointing at that folder. As I said in #184, modinfo
rtlwifi, et. al. now show each of the modules pointing at the correct
driver file, with the expected file date of yesterday.
Uninstalling compat-wireless did remove the cw-3.6 directory completely.
modinfo rtlwifi
filename:
The vendor driver is what I want to be using, isn't it -- the newest one
direct from RealTek?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/902557
Title:
Wireless not working in 12.04 for rtl8192ce
#166 did NOT fix the issue for me. I tried downloading and compiling the
new drivers (locally; didn't use the git-clone/dpkg method mentioned),
but am still experiencing the exact same issue with Reason 6 messages
and ~11% packet loss.
Can someone who found success with the new drivers confirm
Cross-posting from the Ubuntu Forums thread -- I tried the new driver.
Other than improving the signal strength when the connection is up, it
does not improve the stability of the connection or the spate of Reason
6 errors.
--
You received this bug notification because you are a member of Ubuntu
CaptSaltyJack: Yes, still an issue in 3.2.0-26. Also an issue in 3.4
alpha 6, last I checked.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/902557
Title:
Wireless not working in 12.04 for rtl8192ce
Still no brilliant ideas on my end.
New notes since my last comments:
1) I have elected to return to the Ralink USB adapter, since it was
exhibiting the same trouble, independent of which Ubuntu machine it was
attached to.
2) The RealTek adapter connects without issue on my wireless G network
Fed up with trying to make the on-board RealTek chip work, I acquired a
wireless USB device...which exhibits the exact same problems. It's a
Ralink device, rather than RealTek, using a completely separate driver.
I've also tried using the upstream 3.4 rc6 kernel
(3.4.0-030400rc6-generic) to no
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu10
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 1: Generic_1 [HD-Audio Generic], device 0: CONEXANT Analog [CONEXANT
Analog]
Subdevices: 1/1
Subdevice
apport information
** Attachment added: AcpiTables.txt
https://bugs.launchpad.net/bugs/902557/+attachment/3201687/+files/AcpiTables.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/902557
apport information
** Attachment added: AlsaDevices.txt
https://bugs.launchpad.net/bugs/902557/+attachment/3201688/+files/AlsaDevices.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/902557
apport information
** Attachment added: AplayDevices.txt
https://bugs.launchpad.net/bugs/902557/+attachment/3201689/+files/AplayDevices.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/902557
apport information
** Attachment added: BootDmesg.txt
https://bugs.launchpad.net/bugs/902557/+attachment/3201690/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/902557
Title:
apport information
** Attachment added: CRDA.txt
https://bugs.launchpad.net/bugs/902557/+attachment/3201691/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/902557
Title:
Wireless
apport information
** Attachment added: Card0.Codecs.codec.0.txt
https://bugs.launchpad.net/bugs/902557/+attachment/3201692/+files/Card0.Codecs.codec.0.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: Card1.Amixer.values.txt
https://bugs.launchpad.net/bugs/902557/+attachment/3201693/+files/Card1.Amixer.values.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: Card1.Codecs.codec.0.txt
https://bugs.launchpad.net/bugs/902557/+attachment/3201694/+files/Card1.Codecs.codec.0.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/902557/+attachment/3201695/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/902557
apport information
** Attachment added: IwConfig.txt
https://bugs.launchpad.net/bugs/902557/+attachment/3201696/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/902557
Title:
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/902557/+attachment/3201697/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/902557
Title:
apport information
** Attachment added: Lsusb.txt
https://bugs.launchpad.net/bugs/902557/+attachment/3201698/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/902557
Title:
apport information
** Attachment added: PciMultimedia.txt
https://bugs.launchpad.net/bugs/902557/+attachment/3201699/+files/PciMultimedia.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/902557
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/902557/+attachment/3201700/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/902557
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/902557/+attachment/3201701/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/902557/+attachment/3201702/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/902557
apport information
** Attachment added: PulseList.txt
https://bugs.launchpad.net/bugs/902557/+attachment/3201703/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/902557
Title:
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/902557/+attachment/3201704/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/902557
Title:
apport information
** Attachment added: UdevLog.txt
https://bugs.launchpad.net/bugs/902557/+attachment/3201705/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/902557
Title:
apport information
** Attachment added: WifiSyslog.txt
https://bugs.launchpad.net/bugs/902557/+attachment/3201706/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/902557
I just plugged the Ralink USB adapter into my (otherwise working)
ThinkPad T61 (as mentioned, also running 12.04 64-bit) and it started
providing Reason 6 disconnects as well (wlan1). The Intel wireless
adapter (wlan0) continues to encounter no Reason 6 issues.
Is it possible BOTH Ralink and
On a lark, I tried the latest Live CD version of Linux Mint 13 +
Cinnamon.
Same Reason 6 error there, too. Same terrible connection fidelity.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/902557
Also, for whatever it's worth, the wireless connection works fine on
unsecured APs. I don't know if it has he same effect on a WEP-secured or
WPA1-secured AP; my AP is using WPA2-Personal (AES+TKIP, though I tried
just AES with no change in the results).
--
You received this bug notification
Disregard previous message -- the connection stayed up longer without
wireless encryption, but it eventually suffered the usual Reason 6 error
as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Ubuntu 12.04, 64bit, Lenovo ThinkPad E525, RTL8188CE. Affected by
problems.
I've been watching the output to syslog and have noticed a few things.
* When the card is actually up, it works great.
* When the card goes into poor performance, it's actually rapidly negotiating
and losing
Seeing this and worse on a Lenovo ThinkPad T61 with nVidia Quadro 140M.
Anytime the lid is closed (whether this prompts suspend or not, whether
this locks the screen or not), re-opening the lid presents the desktop
view as it existed prior to closing the lid (if screen lock is not
enabled), with
To add further clarification:
- I experience the effects described in the initial report *any time* the lid
is closed, with 100% reproducible results. Suspend, screen lock, etc. have no
extra effect. Close the lid, X is completely locked up other than the mouse
cursor.
- I only started
Managed to fix my issue by switching to the nVidia proprietary driver. I
had a look at my Xorg.0.log and noticed that *none* of the drivers
seemed to be activating successfully. It looks like Nouveau eventually
kicked in, even after showing a failed to load message, but I'm not sure
what the
This happened again this morning.
--
Continuous hard disk IO and system usage
https://bugs.launchpad.net/bugs/609931
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Stopped it this time by running compiz --replace several times,
followed by killall -v metacity several times. And by several, I mean
twenty or so, in rapid succession. Something is continually spawning
metacity processes and a single issuance of killall -v metacity or
compiz --replace is not
I came to my laptop this morning to find this happening once again. No
intervening reboot occurred for this to have been a startup-specific
process. My fans are whirring away at maximum speed just to keep my
processor/GPU at 70 C. This is entirely unaccpeptable.
killall metacity has no effect
Why is this marked 'low' importance? Burning out hardware is a critical
issue, even if it only happens intermittently.
--
Continuous hard disk IO and system usage
https://bugs.launchpad.net/bugs/609931
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
Binary package hint: gconf
Periodically after a reboot, my system CPU usage will rise to 100% and
the hard disk IO light will continuously flicker. The computer fan will
increase to full speed and both the CPU and GPU temperature monitors
read in excess of 70 degrees C
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/52513336/Dependencies.txt
** Attachment added: ProcMaps.txt
http://launchpadlibrarian.net/52513337/ProcMaps.txt
** Attachment added: ProcStatus.txt
http://launchpadlibrarian.net/52513338/ProcStatus.txt
--
Continuous
I had the same issue. I used Greg Lund-Chaix's suggestion and it seems
to have resolved it.
--
package python-xml 0.8.4-10.1ubuntu2 failed to install/upgrade:
https://bugs.launchpad.net/bugs/367955
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
I'm using a Thinkpad T61 with Gusty fully up to date. My T61 has the
Intel 3945 integrated wireless chip, and is using the IWL3945 drivers.
In general, the drivers work as expected. However, if ever the wireless
connection drops for whatever reason (signal strength too low,
Matt: Ah, okay.
Alex: Did you try the two commands I mentioned in my previous comment?
It looks like you're doing something functionally similar, but without
forcibly removing the problem components.
It seems that the core of the problem is that nvidia_new is not
overriding nvidia_legacy or
No, although I'm now getting a different error message in Xorg.0.log.
Also, using nv doesn't work -- all I get is a black screen. I can't
switch to a console, though I can reboot with ctrl-alt-delete.
New error from Xorg.0.log. Full log attached.
(EE) NVIDIA(0): Failed to initialize the
Sorry, correction -- there is no difference for me at this juncture.
The error messages are the same as before.
--
latest xorg / nvidia-glx-new /linux-restricted-modules breaks xserver
https://bugs.launchpad.net/bugs/151213
You received this bug notification because you are a member of Ubuntu
I tried dmesg | grep -nv and found this:
[13.044000] nvidia: module license 'NVIDIA' taints kernel
That doesn't sound good.
I also tried the advice from http://forum.ubuntu-
fr.org/viewtopic.php?id=154950, but to no avail.
The most damning indicator continues to be the Xorg error (that weirdly
Okay, I fixed it -- once.
The problem appears to have been that the nvidia.ko and nvidia_legacy.ko
module files were still hanging around. I discovered this by using
modprobe -l nv*
I deleted them forcibly, leaving only the nvidia_new.ko. Starting X (I
was in a terminal) immediately presented
Sorry for the rapid-fire comment spam.
I have, I think, fixed it. The fix required forcibly deleting the
.mod.o files, rather than the .ko files. The commands I used were:
sudo rm -r /lib/linux-restricted-modules/2.6.22-14-generic/nvidia
sudo rm -r
Matt,
Previously, sudo modprobe nvidia resulted in an error, as you say.
However, I just tried it just now and got no reaction (other than a
return to the prompt). This has not changed the status of the issue,
though, as switching to nvidia still yields an error. Vesa continues to
function.
Confirming this problem, too -- I think. Any time I attempt to enable
nvidia as the driver, it is rejected and I am dropped back to vesa.
--
latest xorg / nvidia-glx-new /linux-restricted-modules breaks xserver
https://bugs.launchpad.net/bugs/151213
You received this bug notification because
Are you getting any debug info from the various system logs?
--
Upgrade to 2.6.22.12 - NVidia driver does not work
https://bugs.launchpad.net/bugs/144551
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Yep, it's working now. I did a search for the file after updating and
was very excited to find it. Rebooting activated it and everything is
once again functioning as expected.
Thanks!
--
[Gutsy] Upgrade to 2.6.22-12 causes iwl3945 to stop functioning
https://bugs.launchpad.net/bugs/144252
You
K8BeBop:
This sounds like a different problem. My problem with the nVidia drivers was
just a kernel version mismatch; I could see as much in the system logs.
Probably worth opening a new bug for your specific issue.
I'm a total newb to Ubuntu and linux in general (but enough of a
computer
Specified the suspected package to which this bug pertains.
** Changed in: linux-ubuntu-modules-2.6.22 (Ubuntu)
Sourcepackagename: None = linux-ubuntu-modules-2.6.22
--
[Gutsy] Upgrade to 2.6.22-12 causes iwl3945 to stop functioning
https://bugs.launchpad.net/bugs/144252
You received this bug
Affirming error, just did an update.
--
[apport] NetworkManager crashed with signal 5 in main()
https://bugs.launchpad.net/bugs/85113
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Public bug reported:
I have a ThinkPad T61 running Gutsy.
Since upgrading to the 2.6.22-12 kernel in yesterday's batch of updates,
I have been unable to use either the nVidia drivers or the iwlwifi
drivers. The nVidia drivers appear to have a kernel mismatch, while the
iwlwifi drivers for the
It looks like the update to the nVidia drivers was just released, so
that's now working on 2.6.22-12.
However, the iwlwifi/3945 issue is still present. I'm not even sure
where to begin looking to address this.
** Summary changed:
- [Gutsy] 2.6.22-12 does not recognize nVidia or iwlwifi drivers
81 matches
Mail list logo
