[Bug 1914940] [NEW] libsbigudrv2 contains udev rules prevent firmware from loading
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
devices and the firmware load command not to run.
I have fixed all of these locally. Is there an upstream package to which
these should be contributed? If not, how do I submit a patch here?
** Affects: sbig (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1914940
Title:
libsbigudrv2 contains udev rules prevent firmware from loading
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sbig/+bug/1914940/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1174145] Re: Broadcom 4313 causes heavy interference with wireless clients after 13.04 upgrade
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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1174145 Title: Broadcom 4313 causes heavy interference with wireless clients after 13.04 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1174145/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1174145] Re: Broadcom 4313 causes heavy interference with wireless clients after 13.04 upgrade
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 https://launchpad.net/ubuntu/saucy/+package /bcmwl-kernel-source) and close this bug. M le, do the saucy drivers work for you? -- 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: Broadcom 4313 causes heavy interference with wireless clients after 13.04 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1174145/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1174145] Re: Broadcom 4313 causes heavy interference with wireless clients after 13.04 upgrade
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 Bit Rate=54 Mb/s Tx-Power=200 dBm Retry long limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on Link Quality=55/70 Signal level=-55 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 That's after 2 days, 12 hours of uptime through two sleep/resume cycles. -- 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: Broadcom 4313 causes heavy interference with wireless clients after 13.04 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1174145/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1097519] Re: Wrong driver used for older Broadcom chipsets
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 6.20.155.1+bdcom-0ubuntu6 shipped in 13.04. Therefore I have unmarked Bug #1174145 as being a duplicate of the bug discussed in this thread. If someone feels this is in error, please provide sufficient justification on Bug #1174145. In relation to this bug, although my BCM4313 (PCI ID 14e4:4727) does work with the brcmsmac driver, the performance of brcmsmac leaves much to be desired compared with bcmwl-kernel-source. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1097519 Title: Wrong driver used for older Broadcom chipsets To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1097519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1174145] Re: Broadcom 4313 causes heavy interference with wireless clients after 13.04 upgrade
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 are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1174145 Title: Broadcom 4313 causes heavy interference with wireless clients after 13.04 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1174145/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1174145] Re: Broadcom 4313 causes heavy interference with wireless clients after 13.04 upgrade
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 Title: Broadcom 4313 causes heavy interference with wireless clients after 13.04 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1174145/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1174145] Re: Broadcom 4313 causes heavy interference with wireless clients after 13.04 upgrade
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 Ubuntu. https://bugs.launchpad.net/bugs/1174145 Title: Broadcom 4313 causes heavy interference with wireless clients after 13.04 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1174145/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1174145] Re: Broadcom 4313 causes heavy interference with wireless clients after 13.04 upgrade
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: Broadcom 4313 causes heavy interference with wireless clients after 13.04 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1174145/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1174145] Re: Broadcom 4313 causes heavy interference with wireless clients after 13.04 upgrade
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 off-site machine Computer B: BCM4313 Linux box pinging same off-site machine Prior to activating computer B's wifi, computer A had no ping timeouts in five minutes. After activating wifi on computer B with the 6.x driver, computer A had several ping timeouts within 1 minute. Upon shutting off wifi on computer B, computer A had no ping timeouts. This behavior has already been established by posts above, but is confirmed on my machine. Then I installed the 5.x version of the driver using `dpkg -i` and repeated the experiment. As before prior to activating wifi on machine B, there were no ping timeouts on computer A. I turn on computer B's wifi and started pinging. Computer A had NO ping timeouts within three minutes. Then I started watching a video on YouTube. Computer A's ping times increased slightly (competing for bandwidth). After five minutes, only ONE ping timeout on computer A occurred. So it would appear something changed between the 5.100.82.112 and 6.20.155.1 version of the drivers. Because I have a nice setup here and there were seven commits between these driver versions so I can probably debug this. Prior to me doing this though, can someone else check that they receive no interference with the 5.100.82.112 version of the driver. Thanks. -- 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: Broadcom 4313 causes heavy interference with wireless clients after 13.04 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1174145/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 996966] Re: No results from HUD search
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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/996966 Title: No results from HUD search To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/996966/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 775071] Re: UI not properly redrawing
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 I've had with Rhythmbox is only a portion of the screen is redrawn until I move it. For example, anything covered by a window in the foreground is not redrawn when Rhythmbox is brought to the foreground (I'll post a screenshot next time it happens). Because I've seen redrawing problems elsewhere, might this issue reside upstream? The attached image shows the result of a right click in Chrome did to a section of the Thunderbird window. Again this was fixed when I moved the window. I looked through the logs and didn't find any errors/warnings in: /var/log/dmesg /var/log/syslog /var/log/Xorg.0.log /var/log/gdm/* I'm running Ubuntu 11.04 x86_64 on NVidia 270.41.06. I'll be happy to include any additional details needed if asked. ** Attachment added: Redrawing Issues with Thunderbird https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/775071/+attachment/2112274/+files/Selection_001.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/775071 Title: UI not properly redrawing -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 775071] Re: UI not properly redrawing
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: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/776904 Possibly related to Nvidia driver issue? https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/750440 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/775071 Title: UI not properly redrawing -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 659348] Re: Kernel Oops - unable to handle kernel paging request; EIP is at videobuf_dma_unmap+0x43/0xb0
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, Inc. CX23885 PCI Video and Audio Decoder (rev 02) ** Attachment added: dmesg https://bugs.launchpad.net/ubuntu/+source/linux/+bug/659348/+attachment/1696771/+files/FirmwareBug -- Kernel Oops - unable to handle kernel paging request; EIP is at videobuf_dma_unmap+0x43/0xb0 https://bugs.launchpad.net/bugs/659348 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 323823] Re: Battery Status Detected Incorrectly (MSI-1719 / GX700)
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 (http://bugzilla.kernel.org/show_bug.cgi?id=12011). -- 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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 323823] Re: Battery Status Detected Incorrectly (MSI-1719 / GX700)
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) https://bugs.launchpad.net/bugs/323823 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 323823] Re: 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 links in that thread). If anyone else would like to try the kernel, I have built a .deb for the kernel and headers (2.6.27-11 amd64) and can place it in a public place. Send me an email if you are interested. Provided that the patch stays in the kernel and is not overwritten (unlike the previous patch), I think this problem is solved. ** Changed in: acpi (Ubuntu) Status: Triaged = Fix Released -- 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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 323823] Re: Battery Status Detected Incorrectly (MSI-1719 / GX700)
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 fix the battery disappearing issue? Thanks for your hard work. -- 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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 323823] Re: Battery Status Detected Incorrectly (MSI-1719 / GX700)
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) https://bugs.launchpad.net/bugs/323823 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 323823] Re: 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) https://bugs.launchpad.net/bugs/323823 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 323823] Re: 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. http://launchpadlibrarian.net/22358574/acpi.noirq.tar.bz -- 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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 323823] Re: Battery Status Detected Incorrectly (MSI-1719 / GX700)
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 -- 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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 323823] Re: Battery Status Detected Incorrectly (MSI-1719 / GX700)
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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 323823] Re: Battery Status Detected Incorrectly (MSI-1719 / GX700)
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 http://launchpadlibrarian.net/22082087/acpi.tar.bz -- 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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 323823] Re: Battery Status Detected Incorrectly (MSI-1719 / GX700)
** 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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 323823] Re: Battery Status Detected Incorrectly (MSI-1719 / GX700)
** 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) https://bugs.launchpad.net/bugs/323823 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 323823] [NEW] 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 the acpi=noirq kernel parameter appears to do nothing to rectify the situation. While running without the acpi=noirq kernel parameter, the battery erroneously disappears. The battery is detected during boot: $ dmesg | grep battery [ 12.305116] ACPI: Battery Slot [BAT1] (battery present) and appears to work fine for a while: $ cat /proc/acpi/battery/BAT1/info present: yes design capacity: 4400 mAh last full capacity: 3255 mAh battery technology: rechargeable design voltage: 10800 mV design capacity warning: 0 mAh design capacity low: 0 mAh capacity granularity 1: 1 mAh capacity granularity 2: 1 mAh model number:MS-1719 serial number: battery type:LION OEM info:MSI Corp. $ cat /proc/acpi/battery/BAT1/state present: yes capacity state: ok charging state: charged present rate:0 mA remaining capacity: 3255 mAh present voltage: 12506 mV $ acpi -bs Battery 0: Full, 100% But after ~10 minutes, it disappears $ cat /proc/acpi/battery/BAT1/info present: no $ cat /proc/acpi/battery/BAT1/state present: no $ acpi -bs [nothing] I receive similar results WITH the acpi=noirq kernel parameters, except it will take ~1-2 hours before the battery disappears. Problem persists whether or not the AC power is plugged in. When I boot into Ubuntu 8.10, kernel 2.6.27-9-generic, the acpi=noirq kernel parameter works and I never lose the battery. Please let me know what other information I can provide or if you need someone to test out patches, I would be willing to do so. ** Affects: ubuntu Importance: Undecided Status: New -- 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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 323823] Re: Battery Status Detected Incorrectly (MSI-1719 / GX700)
** 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 persists in Ubuntu 8.10 x86_64, kernel 2.6.27-11-generic and in Ubuntu 9.04 alpha3 except now the acpi=noirq kernel parameter appears to do nothing to rectify the situation. While running without the acpi=noirq kernel parameter, the battery erroneously disappears. The battery is detected during boot: $ dmesg | grep battery [ 12.305116] ACPI: Battery Slot [BAT1] (battery present) and appears to work fine for a while: $ cat /proc/acpi/battery/BAT1/info present: yes design capacity: 4400 mAh last full capacity: 3255 mAh battery technology: rechargeable design voltage: 10800 mV design capacity warning: 0 mAh design capacity low: 0 mAh capacity granularity 1: 1 mAh capacity granularity 2: 1 mAh model number:MS-1719 serial number: battery type:LION OEM info:MSI Corp. $ cat /proc/acpi/battery/BAT1/state present: yes capacity state: ok charging state: charged present rate:0 mA remaining capacity: 3255 mAh present voltage: 12506 mV $ acpi -bs Battery 0: Full, 100% But after ~10 minutes, it disappears $ cat /proc/acpi/battery/BAT1/info present: no $ cat /proc/acpi/battery/BAT1/state present: no $ acpi -bs [nothing] I receive similar results WITH the acpi=noirq kernel parameters, except it will take ~1-2 hours before the battery disappears. Problem persists whether or not the AC power is plugged in. When I boot into Ubuntu 8.10, kernel 2.6.27-9-generic, the acpi=noirq kernel parameter works and I never lose the battery. Please let me know what other information I can provide or if you need someone to test out patches, I would be willing to do so. -- 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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 147560] Re: Kernel detects battery management wrong (MSI PR200 / System76)
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 opened a new bug report: https://bugs.launchpad.net/ubuntu/+bug/323823 -- Kernel detects battery management wrong (MSI PR200 / System76) https://bugs.launchpad.net/bugs/147560 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 292998] Re: ds9 does not work on intrepid amd64
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 ds9.linux64.5.4.tar.gz sudo mv ./ds9 /usr/bin/ds9 -- ds9 does not work on intrepid amd64 https://bugs.launchpad.net/bugs/292998 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 287093] Re: wrong battery management (MSI PR200/System76 daru2)
*** 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 (MSI PR200 / System76) -- wrong battery management (MSI PR200/System76 daru2) https://bugs.launchpad.net/bugs/287093 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 190000] Re: g-p-m does not indicate battery state correctly + changing brightness to random values.
*** 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 was released and worked fine until 2.6.27-7 was released. I would suggest moving discussion over to that thread. ** This bug has been marked a duplicate of bug 147560 Kernel detects battery management wrong (MSI PR200 / System76) -- g-p-m does not indicate battery state correctly + changing brightness to random values. https://bugs.launchpad.net/bugs/19 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
