Public bug reported:
The libsbigudrv2 package contains several minor udev rule errors that
prevents firmware from loading. These include queries to SYSFS instead
of ATTR, assignment of ENV{DEVTYPE}, and a missing comma (causing
1801362). These items cause the rule to not apply to the underlying
Great. So to other users affected by this bug, simply apply the
broadcom-kernel-source package from saucy as described in post #18
above.
** Changed in: bcmwl (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I've been trying the drivers from saucy (i.e.
6.30.223.30-bdcom0-ubuntu1) for the last week or so. The interference
issue is either entirely gone or significantly reduced. If this is true
for other users, we should probably suggest upgrading as a workaround
(to the driver from here
No, no kernel panic for me with the saucy drivers
(6.30.223.30-bdcom0-ubuntu1) running iwconfig via. sudo:
$ sudo iwconfig eth1
[sudo] password for bkloppenborg:
eth1 IEEE 802.11abg ESSID:XX
Mode:Managed Frequency:2.412 GHz Access Point: 00:1C:28:XX:XX:XX
The merger of Bug #1174145 into this group is inappropriate. This bug
appears to be related to getting brcmsmac selected by default, whereas
Bug #1174145 is related to a WLAN interference issue that popped up
between bcmwl-kernel-source versions 5.100.82.112+bdcom-0ubuntu3 shipped
with 12.10 and
Unmarked this bug as a duplicate of 1097519 for reasons explained here:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1097519/comments/30
** This bug is no longer a duplicate of bug 1097519
Wrong driver used for older Broadcom chipsets
--
You received this bug notification because you
Interference cause tracked to changes of bcmwl-kernel-source between
5.100.82.112 and 6.20.155.1.
** Package changed: ubuntu = bcmwl (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1174145
To make my comment above a little more specific, the version of bcmwl-
kernel-source that does not cause interference in my tests is
5.100.82.112+bdcom-0ubuntu3 (the last release for quantal).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
And fixing a typo in #12, the quantal version comes from here:
http://packages.ubuntu.com/quantal/amd64/bcmwl-kernel-source/download
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1174145
Title:
I just compared the current version (6.20.155.1) of bcmwl-kernel-source
against the 5.100.82.112 version of the driver from quantal (downloaded
from http://packages.ubuntu.com/raring/amd64/bcmwl-kernel-
source/download)
Experimental setup was as follows:
Computer A: BCM4313 on Windows pinging
Same issue here (HUD would return no results, regardless of
application/query string). I had just updated from 10.04 to 12.04 and
was missing indicator-appmenu. Installing via. apt fixed the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I too have been experiencing problems with 11.04 not redrawing. I think
this problem resides upstream (i.e. in Gnome or X) as I have experienced
the same and additional redrawing problems with Banshee, Rhythmbox,
Nautilus, Thunderbird, and Chrome as what you illustrate above. The
primary problem
Similar issues reported elsewhere, but with different applications.
Very similar problem, but with a different application:
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/756560
Another redrawing issue with similar sounding experiences, thinks problem is in
Compiz:
I can confirm the same issue with the Dvico FusionHDTV7. Firmware
upload successful, but any attempt to tune in channels using either
MythTV's built-in scanner or the dvb-apps scan utility result in above
bug. Partial dmesg report attached.
lspci:
Multimedia video controller: Conexant Systems,
I just upgraded to 9.04 over the weekend. The persons who solved this
problem in 8.10 (kernel 2.6.27-11) are again working towards a solution
for 9.04 (kernel 2.6.28-11). I suggest that all further discussion of
this bug be directed to Bug 12011 instead
Please note that the current work to fix the bug is hosted on
bugzilla.kernel.org not on launchpad. Follow the explicit http link
above (http://bugzilla.kernel.org/show_bug.cgi?id=12011), not the Bug
12011 link.
--
Battery Status Detected Incorrectly (MSI-1719 / GX700)
I've been running the kernel with Timo's patch for four days now without
any kernel parameters. The battery status has always been detected
correctly.
The patch in question is found here:
http://bugzilla.kernel.org/show_bug.cgi?id=12011#c105
And is compiled by normal means (see discussion and
Timo, thank you for the update. Do you need another tester or do you
anticipate that the patch will be released in the mainstream kernel
anytime soon? Lastly, does this patch fix both issues I discussed
above, namely can I run my laptop without the acpi=noirq kernel
parameter or does this just
I just finished compiling the kernel with Timo's patch. One hour and 30
minutes of uptime (without any kernel parameters) and my battery is
still detected. I'll post back if it disappears. Way to go!
--
Battery Status Detected Incorrectly (MSI-1719 / GX700)
Given that Zygfryd
(http://bugzilla.kernel.org/show_bug.cgi?id=12011#c110) isn't having
luck with his GX700, this doesn't seem like an option at the moment.
I'll continue checking in on that bug report from time to time.
--
Battery Status Detected Incorrectly (MSI-1719 / GX700)
The battery disappeared after the laptop was running for ~10 hours on AC
power WITH the acpi=noirq kernel parameter specified.
** Attachment added: Tarball of the /proc/acpi directory WITH the acpi=noirq
kernel parameter specified after the battery disappears.
Because this got moved to the acpi section, I've included the standard
information.
$ uname -a
Linux Lappy 2.6.27-11-generic #1 SMP Thu Jan 29 19:28:32 UTC 2009 x86_64
GNU/Linux
Attached is lspci output
** Attachment added: lspci.txt
http://launchpadlibrarian.net/22082037/lspci.txt
--
From $ sudo dmidecode dmidecode.txt
** Attachment added: dmidecode.txt
http://launchpadlibrarian.net/22082045/dmidecode.txt
--
Battery Status Detected Incorrectly (MSI-1719 / GX700)
https://bugs.launchpad.net/bugs/323823
You received this bug notification because you are a member of Ubuntu
Tarball of the /proc/acpi directory with the acpi=noirq kernel parameter
specified while the battery is detected (I'll post another copy of this
when the battery is not detected).
cp -r /proc/acpi /tmp
sudo tar -cvjf ~/acpi.tar.bz /tmp/acpi
** Attachment added: acpi.tar.bz
** Attachment added: Tarball of the /proc/acpi directory without any
acpi-related kernel parameters specified.
http://launchpadlibrarian.net/22085069/acpi.normal.tar.bz
--
Battery Status Detected Incorrectly (MSI-1719 / GX700)
https://bugs.launchpad.net/bugs/323823
You received this bug
** Attachment added: Tarball of the /proc/acpi directory without any
acpi-related kernel parameters specified after the battery disappears.
http://launchpadlibrarian.net/22085082/acpi.batgone.tar.bz
--
Battery Status Detected Incorrectly (MSI-1719 / GX700)
Public bug reported:
Although it was closed and a patch released, bug
147560(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/147560)
pertaining to the battery status being incorrectly detected still
persists in Ubuntu 8.10 x86_64, kernel 2.6.27-11-generic and in Ubuntu
9.04 alpha3 except now
** Description changed:
Although it was closed and a patch released, bug
-
[url=https://bugs.launchpad.net/ubuntu/+source/linux/+bug/147560]147560[/url]
+ 147560(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/147560)
pertaining to the battery status being incorrectly detected still
This bug still persists in 8.10. The acpi=noirq kernel parameter
fixed the symptoms, with 2.6.27-11 I still loose the correct battery
status WITH the acpi=noirq kernel option, although it takes ~1-2 hours
before it happens.
Because bug is closed, with a patch released and then broken, I have
Again, another workaround but this one doesn't involve compiling
anything... simply replace the executable.
Instructions below for 64-bit Linux (32-bit packages here: http://hea-
www.harvard.edu/RD/ds9/)
wget
http://hea-www.harvard.edu/saord/download/ds9/linux64/ds9.linux64.5.4.tar.gz
tar xvf
*** This bug is a duplicate of bug 147560 ***
https://bugs.launchpad.net/bugs/147560
Further details of this bug can be found here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/147560
** This bug has been marked a duplicate of bug 147560
Kernel detects battery management wrong
*** This bug is a duplicate of bug 147560 ***
https://bugs.launchpad.net/bugs/147560
By reading the above thread, these issues appear to be caused by a
problem in the Linux Kernel itself as described here:
https://bugs.launchpad.net/ubuntu/+source/linux-
source-2.6.22/+bug/147560/
A bug fix
32 matches
Mail list logo
