Unfortunately I no longer have the Asus notebook, I can't test current
version.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/451108
Title:
Asus Wireless button not updating WLED
To manage notifica
The patched kernel solves the Oops issue.
Also, the "CPU power or thermal limit exceeded" boot-time message disappeared.
--
ips-adjust - BUG: unable to handle kernel NULL pointer dereference at (null)
https://bugs.launchpad.net/bugs/632430
You received this bug notification because you are a memb
The integrated mic still doesn't work on Maverick. It works in kernel
2.6.36-rc4.
Here's the fix:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=840b64c08032a86ab39b85ddd342918da0d559c8
--
No internal mic / line-in on Intel HDA G45 DEVIBX / Realtek ALC 275
https:
Same oops using latest Linus kernel: 2.6.36-rc4.
--
ips-adjust - BUG: unable to handle kernel NULL pointer dereference at (null)
https://bugs.launchpad.net/bugs/632430
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs maili
** Attachment added: "AcpiTables.txt"
https://bugs.launchpad.net/bugs/632430/+attachment/1553790/+files/AcpiTables.txt
** Attachment added: "AlsaDevices.txt"
https://bugs.launchpad.net/bugs/632430/+attachment/1553791/+files/AlsaDevices.txt
** Attachment added: "AplayDevices.txt"
http
Public bug reported:
Oops during boot-up.
Immediately before oops, the following line is logged:
intel ips :00:1f.6: CPU power or thermal limit exceeded
ProblemType: KernelOops
DistroRelease: Ubuntu 10.10
Package: linux-image-2.6.35-19-generic 2.6.35-19.28
Regression: Yes
Reproducible: Yes
Pr
The problem has disappeared after update to Karmic.
--
[ASUSTeK Computer INC. V6V] suspend/resume failure
https://bugs.launchpad.net/bugs/357077
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lis
After latest updates all messages disappeared.
--
pci boot messages displayed
https://bugs.launchpad.net/bugs/413419
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.
Reference bug opened upstream:
http://dev.iksaif.net/issues/14
Now, I'm using acpi, all Asus V6V buttons work as expected.
--
Asus Wireless button not updating WLED
https://bugs.launchpad.net/bugs/451108
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
Update:
echo 1 >/sys/bus/pci/drivers/ipw2200/\:03\:02.0/rf_kill
switches off the radio.
But /sys/bus/pci/drivers/ipw2200/\:03\:02.0/led seems to be ignored.
--
Asus Wireless button not updating WLED
https://bugs.launchpad.net/bugs/451108
You received this bug notification because you are
After update to 9.10 final the wlan button doesn't switch off the radio.
The only way to disable wireless I found is to unload the ipw2200
module. There's no point in changing the led status if it doesn't
reflect the radio status.
--
Asus Wireless button not updating WLED
https://bugs.launchpad.n
The script could easily be fixed after release.
Let's reassign to kernel, for now.
--
Asus Wireless button not updating WLED
https://bugs.launchpad.net/bugs/451108
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing l
I read those bug reports before filing this and I agree with you on
potential regression problems.
Kernel 2.6.31 introduced a small change in asus-laptop.c:
#define ASUS_HOTK_FILE KBUILD_MODNAME
instead of
#define ASUS_HOTK_FILE "asus-laptop"
So, now, all asus-laptop specific se
Public bug reported:
Binary package hint: acpi-support
Ubuntu 9.10 beta, updated.
acpi-support 0.127
When I press the wireless button on my Asus V6V laptop, wireless lan is
disabled (radio off), but the wireless led remains switched on.
Changing the last line of /usr/share/acpi-support/state-fu
** Attachment added: "AlsaDevices.txt"
http://launchpadlibrarian.net/33022096/AlsaDevices.txt
** Attachment added: "AplayDevices.txt"
http://launchpadlibrarian.net/33022097/AplayDevices.txt
** Attachment added: "ArecordDevices.txt"
http://launchpadlibrarian.net/33022098/ArecordDevices.t
Public bug reported:
Message shown during boot:
pci :03:00.0 BAR 6:address space collision on of device
0xfbfc-0xfbfd
In Bug #424142 is mentioned http://patchwork.kernel.org/patch/39988/
ProblemType: Bug
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/
metacity (1:2.25.144-0ubuntu2) fixed the problem.
** Changed in: metacity (Ubuntu)
Status: New => Fix Released
--
[Regression] Maximized window behind panel in second screen (dual head)
https://bugs.launchpad.net/bugs/347366
You received this bug notification because you are a member of U
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/24946173/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/24946175/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/24946182/Dependencies.txt
** A
Public bug reported:
Notebook hanged when resuming after having disconnected the AC cord
while suspended.
ProblemType: KernelOops
Annotation: This occured during a previous suspend and prevented it from
resuming properly.
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/share/a
If I restart X after I moved the second panel on the second screen everything
works as expected.
If I start X with both panels on first screen and then move the second panel to
the second screen, maximized windows in second screen ignore panel and occupy
the whole screen, going behind the panel.
Public bug reported:
Binary package hint: metacity
Ubuntu: 9.04 Jaunty alpha
metacity: 1:2.25.144-0ubuntu1
I have a dual head "xinerama style" setup, with an additional panel at the
bottom of the second screen. When maximizing a window in the second screen the
window uses the whole screen, not
On Intrepid, I'm now using radeon driver and Virtualdesktop option in xorg.conf.
A big Virtualdesktop is more useful for me as I can move windows between
monitors.
I briefly tested fglrx and it doesn't log errors.
Log noise in Hardy disappeared after an update (see my previous
comment).
I'd clos
Log noise disappeared yesterday.
I found the following lines in /var/log/Xorg.0.log:
(WW) fglrx(0): ***
(WW) fglrx(0): * DRI initialization failed! *
(WW) fglrx(0): * (maybe driver kernel module missing or bad) *
(WW) fglrx(0): * 2D acce
I'm seeing bug 902. Even screensaver behaviour is the same.
But the workaround seems not working.
Are my modifications correct? Maybe my bigdesktop setup isn't correct.
--- /etc/X11/xorg.conf.good 2007-05-03 23:45:51.0 +0200
+++ /etc/X11/xorg.conf 2008-03-14 13:29:38.0 +0100
Public bug reported:
Both /var/log/gdm/:0.log and /var/log/Xorg.0.log are flooded with lines
like the following:
(EE) fglrx(1): [DRI] Locking deadlock.
Already locked with context 137016756,
trying to lock with context 2.
(EE) fglrx(1): [DRI] Unlocking inconsistency:
Conte
** Attachment added: "xorg.conf"
http://launchpadlibrarian.net/12275905/xorg.conf
--
[Hardy Alpha-5] fglrx log noise if dualhead
https://bugs.launchpad.net/bugs/196617
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs m
26 matches
Mail list logo
