The upgrade from 12.04 to 12.10 seems to be stable this way (I made no changes
and I've no kernel panics). However, I've got the following problem:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1066410
Can anyone confirm that or please help me with it?
Thank you very much. For me that is
@ambidextrvs - Yes you're right - I tried both openSUSE and Ubuntu
running mainline 3.6 kernel and didn't observe this problem anymore.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1041883
Title:
R
By the way, mainline kernel 3.6 seems to fix the issue without the need
for a workaround. I've been using it for over a week with no crashes and
working fn-keys (except screen brightness)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On Sun, Oct 7, 2012 at 12:43 AM, BlueHawk <1041...@bugs.launchpad.net> wrote:
> Ok. Tested for a few more days from completely cold starts. Seems stable
> now. No panics. Seems like that is the real fix for the boot.
Well, it's more a real workaround :/
--
Corentin Chary
http://xf.iksaif.net
--
Yes, same here. Thanks @Ash!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1041883
Title:
Recent patch to asus-wmi module makes system unbootable
To manage notifications about this bug go to:
https
Ok. Tested for a few more days from completely cold starts. Seems stable
now. No panics. Seems like that is the real fix for the boot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1041883
Title:
Re
Sorry about the typo - the commands should have been:
echo "blacklist btusb" | sudo tee /etc/modprobe.d/blacklist-btusb.conf
echo "/sbin/modprobe btusb" | sudo tee /etc/rc.local
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
I've tried the fix so far and it seems stable. But I'll try again
tonight from a cold start, since my problem manifested itself badly when
the machine is cold - I'd say the settling times are longer when the
components are cold, increasing the likelihood for the race conditions.
@zubozrout - the i
This morning when I turned on my device kernel panic occurred again. I
don't know why it was working with no problems yesterday (and I rebooted
more than 5 times), but it seems that the problem is not completely
solved. (I am booting off a regular HDD, not SSD).
--
You received this bug notificat
@Ash - Thanks for your solution. It works great (up until now I've been
using the noapic linux kernel option). And it works even better than the
noapic solution, because somehow, more applications were crashing with
noapic = apport was more active and always ended with some "lack of ram"
error mess
Hi, this is great, seems like a possible explanation. I just tested with
kernel from #80 and 3.5.0-16 and the computer didn't boot correctly. Then
tested with mainline 3.6.0 , it booted correctly and I have all fn-keys
working (except screen brightness)
I'll update tomorrow if the situation ch
I was seeing this problem with Ubuntu 12.04 booting off SSD (similar to
my earlier openSUSE setup).
After a little fiddling around based on the info in this thread
(especially about asus_wmi_rfkill_init()) and the asus-wmi.c, I think
I've found the problematic module which seems to cause the race
I have an UX32VD and I boot a 3.5.x kernel (from openSUSE). I can
confirm I have the exact same problem and hang as described in this
thread. (with the caps lock key LED flashing).
It takes me somewhere between 5 and 10 tries to get a working bootable
system when asus-wmi driver is not blacklisted
I have a UX32V not VD (the only difference is the display resolution
though, afaik). I have not yet have the chance to test the -16 kernel,
will report back as soon as I do.
On Sun, Sep 30, 2012 at 5:15 PM, BlueHawk <1041...@bugs.launchpad.net> wrote:
> Can't confirm fix as I can't find a 3.5.0-16
Can't confirm fix as I can't find a 3.5.0-16.24 AMD64 build as yet and
I'm not keen on building one from scratch. Maybe we need to log the ASUS
UX32A problem as separate since although the symptoms are the same as
@peterrus his went away with one of the mods here but he had a UX32VD.
--
You recei
Should I open another bug? Was this bug fixed for everybody?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1041883
Title:
Recent patch to asus-wmi module makes system unbootable
To manage notificat
This bug was fixed in the package linux - 3.5.0-16.25
---
linux (3.5.0-16.25) quantal-proposed; urgency=low
[ g...@status.e4ward.com ]
* SAUCE: input: Cypress PS/2 Trackpad fix multi-source, double-click
- LP: #1055788
[ Tim Gardner ]
* [Config] revert '[Config] enable
@peterrus
No, the "caps lock" key just kept blinking.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1041883
Title:
Recent patch to asus-wmi module makes system unbootable
To manage notifications a
@ambidextrvs
*
*
*Does closing the lid, and then reopening it give you a working image?
*
On Fri, Sep 28, 2012 at 10:50 PM, ambidextrvs wrote:
> I should also say that adding "nolapic" to the grub seems to be a
> workaround for the problem as @Tommy Nevtelen (dal) said.
> Tested it in Linux zenb
I should also say that adding "nolapic" to the grub seems to be a workaround
for the problem as @Tommy Nevtelen (dal) said.
Tested it in Linux zenbook 3.5.0-15-generic #23~lp1041883v4 SMP Wed Sep 26
16:53:03 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug notification because
Hi, I don't think a picture would help since the screen is blank but
here is a video. I entered the edit menu on grub at the beginning to
show the text output.
** Attachment added: "boot.mp4"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1041883/+attachment/3353373/+files/boot.mp4
--
@ambidextrvs and @Carsten Otto,
Can you post a screen capture or digital picture of the panic you are
seeing? That way we can see if this is the same issue or not.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
I experience the problem (blank screen, nothing works for 19 out of 20
boots) with a hand-made kernel that does not have CONFIG_X86_32 set. I
guess the bug is caused by something else.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
Hi, I just tested the kernel from comment #80 and I still get the kernel
panic with the flashing "caps lock" key.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1041883
Title:
Recent patch to asus-w
UBUNTU: [Config] revert 'UBUNTU: [Config] enable CONFIG_X86_X32=y'
** Changed in: linux (Ubuntu Quantal)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/10418
Can other folks affected by the original panic described in this bug
report test the kernel mentioned in comment #80? For all other issues,
it is best to open a new bug report, so those other issues can be
addressed individually.
Thanks again everyone for testing!
--
You received this bug notif
I do indeed not encounter this panic:
https://launchpadlibrarian.net/113647137/2012-08-26%2019.05.22.jpg
This black screen issue is probably unrelated to this bug, open a new
bugreport?
On Fri, Sep 28, 2012 at 4:37 PM, Joseph Salisbury <
joseph.salisb...@canonical.com> wrote:
> @peterrus, but yo
@peterrus, but you don't get the panic that you saw when originally
opening this bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1041883
Title:
Recent patch to asus-wmi module makes system unboot
peterrus@host:~$ uname -a
Linux host 3.5.0-15-generic #23~lp1041883v4 SMP Wed Sep 26 16:53:03 UTC
2012 x86_64 x86_64 x86_64 GNU/Linux
peterrus@host:~$ cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-3.5.0-15-generic
root=UUID=9bb3948b-2fd3-46c4-b0bb-0ae32a87278a ro nosplash vt.handoff=7
System boots,
Disregard last, I was still booting a -11 kernel, and we were now actually
testing a -15 one, will report back in a few minutes
On Fri, Sep 28, 2012 at 3:44 PM, PJ P wrote:
> Strange I can seem to completely reproduce the problem on the v4 kernel,
> what I did:
>
> First try: Normal boot, with s
Strange I can seem to completely reproduce the problem on the v4 kernel,
what I did:
First try: Normal boot, with splash etc: boot became stuck, with the purple
Ubuntu splash showing, and all five polka-dots being red-ish.
Second try: this time I removed the 'quiet' kernel parameter and added
'no
On Fri, Sep 28, 2012 at 12:11:57PM -, Corentin Chary wrote:
> > When booting through the recovery mode, I not only can't change the
> > brightness, but it seem there is also a problem running 3D games. So, in
> > this case, Unity runs only through the llvmpipe and some games are not
> > play
@peterrus,
In comment #83 you say the v4 test kernel does not boot. Are you
getting any messages on the screen? Is there a system panic? If so,
can you capture a screen shot and post it to the bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
Also, blacklisting these modules did not prevent them from loading for some
reason
On Fri, Sep 28, 2012 at 2:54 PM, PJ P wrote:
> 3D Drivers do not work in recovery mode ;)
>
>
> On Fri, Sep 28, 2012 at 2:11 PM, Corentin Chary
> wrote:
>
>> > When booting through the recovery mode, I not only c
3D Drivers do not work in recovery mode ;)
On Fri, Sep 28, 2012 at 2:11 PM, Corentin Chary
wrote:
> > When booting through the recovery mode, I not only can't change the
> brightness, but it seem there is also a problem running 3D games. So, in
> this case, Unity runs only through the llvmpipe an
> When booting through the recovery mode, I not only can't change the
> brightness, but it seem there is also a problem running 3D games. So, in this
> case, Unity runs only through the llvmpipe and some games are not playable at
> all:
> using GL_RENDERER "Gallium 0.4 on llvmpipe (LLVM 0x301)"
One more thing to add:
When booting through the recovery mode, I not only can't change the brightness,
but it seem there is also a problem running 3D games. So, in this case, Unity
runs only through the llvmpipe and some games are not playable at all:
using GL_RENDERER "Gallium 0.4 on llvmpipe (L
Just upgraded to beta 2 and even though no kernel update was included, I
had once again the luxury of booting without kernel panic. But then
again, I am stacked with the error again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
Yes, sounds exactly like the problem
On Sep 28, 2012 10:55 AM, "zubozrout" wrote:
> Hmm, same problem here with Quantal. As described, system won't boot
> unless the procedure is made through the recovery option in the grub.
> This way Ubuntu loads but brightness of the screen can not be changed
Hmm, same problem here with Quantal. As described, system won't boot
unless the procedure is made through the recovery option in the grub.
This way Ubuntu loads but brightness of the screen can not be changed
because "/sys/class/backglight/..." thing is not up.
Somehow, after upgrade, it once boot
Does not seem to boot
On Thu, Sep 27, 2012 at 9:43 PM, Joseph Salisbury <
joseph.salisb...@canonical.com> wrote:
> @peterrus,
>
> Can you also test the kernel at:
> http://people.canonical.com/~jsalisbury/lp1041883
>
> --
> You received this bug notification because you are subscribed to the bug
@peterrus,
Can you also test the kernel at:
http://people.canonical.com/~jsalisbury/lp1041883
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1041883
Title:
Recent patch to asus-wmi module makes syst
ok. Tried v4. That still has the random kernel panic issue with flashing
caps lock. When it does boot and get to the login, you can't tell
because the screen is black - the original 12.04 kernel problem. Logging
in blind, suspending (closing the lid) and then coming out of suspend by
opening the li
I built a test kernel with the config option CONFIG_X86_X32 diabled.
This kernel is available in the top level directory at:
http://people.canonical.com/~jsalisbury/lp1041883
Can you test that kernel and report back if it has the bug or not?
--
You received this bug notification because you are
The bisect pointed to the following commit as the first bad one:
commit d3a67dbe37d32ba10da0de2f14151d606856e5d2
Author: Leann Ogasawara
Date: Thu Aug 16 09:01:00 2012 -0700
UBUNTU: Ubuntu-3.5.0-11.11
This indicates the bug is due to a config file change in 3.5.0-11.11. The one
that sticks o
If it is suspected to be related to ivy bridge or hd4000 (vga), will it
be worthwhile to disable some power-saving feature, i.e. rc6?
for example, i915.i915_enable_rc6=-1 (please correct me if I am
mistaken)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
3.5.0-15 does not work on the UX32A. Anecdotally, lp1041883v3 seems to
be less stable on a cold UX32A than the last v2. Same errors though.
Either kernel panic with flashing caps lock or just a black screen and
unresponsive. Even after booting from recovery sometimes hangs. Goes
away after system w
Linux host 3.5.0-11-generic #11~lp1041883v3 SMP Mon Sep 24 20:45:53 UTC
2012 x86_64 x86_64 x86_64 GNU/Linux
_works_
ubuntu 3.5.0-15 does not work
On Mon, Sep 24, 2012 at 11:45 PM, Joseph Salisbury <
joseph.salisb...@canonical.com> wrote:
> I built the next test kernel, which is up to commit:
>
I built the next test kernel, which is up to commit:
41d572a1eb382b033a93f80e01450425d641dc05
This kernel is available in the top level directory at:
http://people.canonical.com/~jsalisbury/lp1041883
Can you test that kernel and report back if it has the bug or not?
--
You received this bug not
Thanks for testing @peterrus. I will update the bisect and kick off the
next test kernel build.
While the test kernel is building, can you confirm you are still
affected by this bug by testing the latest Quantal kernel again. It
would be good to ensure you can still reproduce this bug, so we kno
running:
Linux host 3.5.0-11-generic #11~lp1041883v2 SMP Wed Sep 19 18:55:52 UTC
2012 x86_64 x86_64 x86_64 GNU/Linux
Everything still works
On Sat, Sep 22, 2012 at 8:42 PM, VJ wrote:
> I can confirm that the intermittent boot behavior occours on the UX32a
> when running 3.5.0.15 on a 32 and 64
I can confirm that the intermittent boot behavior occours on the UX32a
when running 3.5.0.15 on a 32 and 64 bit install.
(This is booting from the SSD, with /home mounted on the HDD.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
@jsalisbury
I would open a different bug, but I believe we are all experiencing the
same one, at least we all share the same "symptoms". However it is an
intermittent bug, triggered by special conditions (as @BlueHawk's
comments can confirm I think) which I think could explain why @peterrus
is
Ok. Tried this afternoon, after leaving off all day and without AC
power. Booted without AC power and agin have the kernel panic issue and
consistently - even from recovery. It's got to be something related to
Ivy Bridge and the Intel HD 4000 I think. It gets to recovery, which
isn't switching to t
I've tested the latest build on the UX32A. This seems a bit more stable.
I cold-booted after letting it stand overnight and it comes up fine.
However, I did have issues last night on first install - it didn't get
to a kernel panic with the caps lock light flashing, but the system
didn't go to a bla
@peterus
Have you had a chance to test the kernel mentioned in comment #65? We
probably only have a couple more kernels to test to identify the
offending commit.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
@ambidextrvs,
Yes, correct. This bisect is being performed for the issue @peterrus is
seeing. You may be hitting a different issue. It might be best to open
a new/separate bug, so we can focus specifically on your issue.
--
You received this bug notification because you are a member of Ubuntu
@jsalisbury
It still has the bug.
If I understand correctly, the bisect you're performing is because 3.5.2 worked
for @peterrus which led to the hypothesis that it was a Ubuntu specific
problem, however I tested it too (see comment #59) and it didn't worked for
me, so I don't think it has be
I built the next test kernel, which is up to commit:
c7f240a0b0ea5c489aabf65b3399f192a6f6fc53
This kernel is available in the top level directory at:
http://people.canonical.com/~jsalisbury/lp1041883
Can you test that kernel and report back if it has the bug or not?
--
You received this bug not
@peterrus - yes, I was talking about today's build.
Ok. I started the laptop from a completely cold state. The problem came
back with hangs at boot (flashing caps). Even recovery hung. After a
while, when the system had warmed up again, the hangs went away.
--
You received this bug notification
Second boot went well also, about the wifi status light: at an older
kernel, (3.5.0-8) the wifi light often only worked after doing 4 or so
toggles, with this kernel it seems to work like it should.
On Wed, Sep 19, 2012 at 8:34 PM, PJ P wrote:
> If so: boots the first time, will try a few more b
If so: boots the first time, will try a few more boots after this post.
Everything working as reported earlier (except screenbrightness ofcourse).
I notice, by the way, that the wifi toggle light (there is a led inside the
wifi toggle button) isn't reverted anymore, so wifi off = led off, wifi on
Assuming you are talking about this one:
http://people.canonical.com/~jsalisbury/lp1041883/linux-image-3.5.0-11-generic_3.5.0-11.11~lp1041883v2_amd64.deb(and
its accompanying debs)
On Wed, Sep 19, 2012 at 7:21 PM, BlueHawk
<1041...@bugs.launchpad.net>wrote:
> I've tested the latest build on my U
I've tested the latest build on my UX32A. It seems stable - but the
previous one seemed stable as well until I tried booting again this
morning (I did have a few different issues though with yesterday's build
- this morning it would occasionally not come up with flashing caps lock
flashing, but it
Hi, so I tested 3.5.2 again (http://kernel.ubuntu.com/~kernel-
ppa/mainline/v3.5.2-quantal/) and it didn't work for me. So I don't
think this is a Ubuntu specific problem. I would think it has more to do
with the "race condition" that @Dassburger is suggesting.
@peterrus do you have any specific
@peterrus,
It would be good to know if the bug also exists in the test kernel I
posted.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1041883
Title:
Recent patch to asus-wmi module makes system unb
I think the bug is still there. I wasn't able to boot with the kernel
from http://people.canonical.com/~jsalisbury/lp1041883/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1041883
Title:
Recent patc
The kernel can be downloaded from:
http://people.canonical.com/~jsalisbury/lp1041883/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1041883
Title:
Recent patch to asus-wmi module makes system unboot
Joseph: Do you have a link, or is it still being built?
On Wed, Sep 19, 2012 at 4:34 PM, Joseph Salisbury <
joseph.salisb...@canonical.com> wrote:
> The current bisect I am performing is focusing on systems being un-
> bootable. For all other issues, it would be helpful to open new bugs,
> so we
Strange I can control them just fine, and everything still seems to working
after a few boots, I did have one occurence of the system not coming out of
suspend, but that might just be a unrelated issue
On Wed, Sep 19, 2012 at 4:29 PM, BlueHawk
<1041...@bugs.launchpad.net>wrote:
> @jonathan.ernst
The current bisect I am performing is focusing on systems being un-
bootable. For all other issues, it would be helpful to open new bugs,
so we can focus on one issue at a time.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
I built the next test kernel, which is up to commit:
490c8669007cb7ab08b9c06176d0c01531688fbb
This kernel is available from:
http://people.canonical.com/~jsalisbury/lp1041883
Can you test that kernel and report back if it has the bug or not?
--
You received this bug notification because you are
@jonathan.ernst Cpas lock flashing means that the kernel panic occurred
- which is the original problem we've all been having.
I spoke too soon. The problem re-occurred this morning. I removed
acpi_osi=Linux and i915.modeset=1 from the boot params in my grub setup
and it went away again. So there
I still cannot boot with jsalisbury on my ux32v (previous kernel version
works but also give me a black screen if I patch in Asus wmi) .
Sometimes caps locks keep on blinding with no screen, other times I just
don't have a screen at all. I'm also using my ssd to boot.
Thanks for your help
--
You
@Bluehawk: Are you sure keyboard backlight doesn't work? the 32A and 32V
should be nearly identical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1041883
Title:
Recent patch to asus-wmi module makes
@Dassburger, it calls bios's wmi function and probably reads from ec
which generates interrupts (GPE events).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1041883
Title:
Recent patch to asus-wmi mo
lp1041883 works for the UX32A as well - at least this particular bug is
gone, and the display comes up without nomodeset. Function keys work
except for display brightness (expected) and keyboard backlight. Screen
switches off when you close the lid and comes back on when you open it
again.
--
You
It does not have the bug, also the rfkill button works, (which it
probably should)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1041883
Title:
Recent patch to asus-wmi module makes system unbootabl
I reset my Quantal tree to Ubuntu-3.5.0-11.11 and kicked off a bisect
between f0d8bd83 and Ubuntu-3.5.0-11.11.
I built the first test kernel, which is up to commit:
e1bd6cd32e9eb6f0d88dad9ba8aaff9006dd0cb3
This kernel is available from:
http://people.canonical.com/~jsalisbury/lp1041883
Can you t
I can confirm that this works:
keyboard backlight up/down, tracpad toggle, volume toggle, volume.
peterrus@host:~$ uname -a
Linux host 3.5.0-10-generic #10~lp1041883v1 SMP Tue Sep 18 18:41:30 UTC 2012
x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member
@peterrus,
I created a Quantal test kernel. The test kernel was built after being
reset to f0d8bd83. The test kernel can be downloaded from:
http://people.canonical.com/~jsalisbury/lp1041883/
Can you test that kernel and confirm it does not have the bug?
Thanks in advance.
--
You received t
Alex, my experiments show that the problem is caused by wifi and bluetooth
initialization in rfkill. I've noticed that the problem can be reproduced
with these turned on (uncommented). I tried enabling/disabling wifi and
bluetooth NOT simultaneously, one is on and other is off. After reboot I
could
Sorry, I used the wrong account. The last comment was done by me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1041883
Title:
Recent patch to asus-wmi module makes system unbootable
To manage noti
I am using Debian Testing with 3.5.4 and also have very hard trouble
booting (one out of 20 times it works?). I had no problems with 3.5.0rc7
(+the WMI patch applied manually).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
jsalisbury - so it looks like it might be something Ubuntu specific
since mainline 3.5.2 works for peterrus. I would start by resetting to
f0d8bd83c3d4db8ae76df8a894eac04d441e887d which is Ubuntu-3.5.0-10.10 on
the Ubuntu-3.5.0-11.11 branch (which also includes 3.5.2). Make sure
this still works. I
* 3.5.0-10.10 still works.
* Mainline 3.5.1 boots, no black screen (good) no working asus-wmi (hotkeys
dont work), no need to use recovery mode for booting
* Mainline 3.5.2 works at first boot (no black screen, working hotkeys),
second boot (dito), and third boot (dito)
On Tue, Sep 18, 2012 at 6:2
@Dassburger,
thanks for the valuable information on asus_wmi_rfkill_init(). Will it
be possible to narrorw down which part of asus_wmi_rfkill_init cause the
hang? For instance, could it be one of the asus_new_rfkill() or
asus_setup_pci_hotplug() or so?
--
You received this bug notification beca
Will test right away
On Tue, Sep 18, 2012 at 6:13 PM, Joseph Salisbury <
joseph.salisb...@canonical.com> wrote:
> @peterus, I look forward to hearing your test results. I can kick off a
> bisect and start posting test kernels once we hear back.
>
> ** Tags added: performing-bisect
>
> --
> You r
@peterus, I look forward to hearing your test results. I can kick off a
bisect and start posting test kernels once we hear back.
** Tags added: performing-bisect
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
peterrus - regarding comment #32 please make sure the modules you've
blacklisted are in fact not getting loaded, e.g., 'lsmod |grep asus'.
Its possible that asus-wmi is a red herring. So, I guess there are 3
things to try:
1) Re-verify that 3.5.0-10.10 still works.
2) Try mainline 3.5.1
(http://
@Tim Gardner:
when I boot your kernel in recovery mode, it boots, I get into X etc etc,
but the hotkeys do not work (this could've been suspected), this makes it
really strange that the kernel won't boot in regular mode, which might not
even be related to this bug. With not booting I mean: Screen
@Tim Gardner: Seems to make no difference
In the meantime, is there a way to disable loading the module, adding it to
/etc/modprobe.d/blacklist.conf seems to have no effect
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
The use ASUS_WMI_METHODID_DSTS2 is to make sure asus-wmi and asus-nb-wmi
will be loaded correctly - without an DSTS id assigned, many of the
functions in asus-wmi / asus-nb-wmi will not work. That's why hotkeys
are not working
Preivously asus bios will either respnod to ASUS_WMI_METHODID_DSTS or
A
Please try this kernel at http://kernel.ubuntu.com/~rtg/lp1041883.1/
with the patch 'Revert "asus-wmi: use ASUS_WMI_METHODID_DSTS2 as default
DSTS ID."'. For example:
wget
http://kernel.ubuntu.com/~rtg/lp1041883.1/linux-image-3.5.0-15-generic_3.5.0-15.21_amd64.deb
wget
http://kernel.ubuntu.com/~
@Dassburger, so if I simply comment that out (there is one occurence?) the
problem would be gone? (and leaving me without a wifi switch)
On Tue, Sep 18, 2012 at 3:09 PM, BlueHawk
<1041...@bugs.launchpad.net>wrote:
> Just to confirm that this problem also exists for the UX32a. I tried the
> Quanta
Just to confirm that this problem also exists for the UX32a. I tried the
Quantal 3.5.4 kernel with nomodeset and get the random hangs on boot.
Booting off an install on SSD. Recovery booting as always, works fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
Alex - 'asus-wmi: use ASUS_WMI_METHODID_DSTS2 as default DSTS ID.' is
the only change to drivers/platform/x86/asus-wmi.c from
Ubuntu-3.5.0-10.10 to Ubuntu-3.5.0-11.11
** Also affects: linux (Ubuntu Quantal)
Importance: High
Status: Triaged
** Changed in: linux (Ubuntu Quantal)
St
Awesome, if you are in need of testing, tell me.
On Sun, Sep 9, 2012 at 10:53 PM, Dassburger
wrote:
> Oops! Yes, you're right. I was confused because my own experiments with
> this module.
>
> Actually, I've tracked down that asus_wmi_rfkill_init() makes module to
> crash, while probing for diff
Oops! Yes, you're right. I was confused because my own experiments with
this module.
Actually, I've tracked down that asus_wmi_rfkill_init() makes module to
crash, while probing for different devices (wifi, gps, wwan3g, etc).
Skipping it if dsts_id is ASUS_WMI_METHODID_DSTS2 makes module stable,
a
If the bug is not related to asus-wmi, why is then that once I enabled the
module through dkms the problem appears, and once I disable it, the problem
is gone? (Not actually expecting an answer here ;) but to point out that I
do think the problem lies in the module)
On Sun, Sep 9, 2012 at 4:14 PM,
1 - 100 of 125 matches
Mail list logo
