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, but screen stays black, I first have to suspend it by closing
the laptoplid and then reopening it. After that all known-to-work
functionbuttons work.

On Fri, Sep 28, 2012 at 3:54 PM, PJ P <email address hidden> wrote:

> 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 <email address hidden> wrote:
>
>> 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
>> 'nosplash', the system booted successfully,
>>
>> Third try: thinking it might have something to do with those kernel
>> parameters, I tried a normal boot, boot was successful.
>>
>> Fourth try: normal boot still works.
>>
>> Fifth try: quiet + nosplash boot also works.
>>
>> Seems quite random.
>>
>>
>> On Fri, Sep 28, 2012 at 3:04 PM, Tommy Nevtelen <
>> <email address hidden>> wrote:
>>
>>> On Fri, Sep 28, 2012 at 12:11:57PM -0000, 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
>>> playable at all:
>>> > > using GL_RENDERER "Gallium 0.4 on llvmpipe (LLVM 0x301)"
>>> >
>>> > I don't think recovery mode is supposed to to anything more than
>>> > recovery. It you want to boot a stable system for now, just blacklist
>>> > asus-wmi / asus-nb-wmi (but that won't help for actually fixing the
>>> > problem).
>>>
>>> My temporary fix for my UX32VD is to boot with nolapic. This enables a
>>> clean and working boot every time with fn-keys working. Sans backlight of
>>> course.
>>>
>>> --
>>> Tommy Nevtelen
>>>
>>> --
>>> You received this bug notification because you are subscribed to the bug
>>> report.
>>> https://bugs.launchpad.net/bugs/1041883
>>>
>>> Title:
>>>   Recent patch to asus-wmi module makes system unbootable
>>>
>>> Status in “linux” package in Ubuntu:
>>>   In Progress
>>> Status in “linux” source package in Quantal:
>>>   In Progress
>>>
>>> Bug description:
>>>   There has been recently a patch to the asus-wmi module (see
>>>   http://comments.gmane.org/gmane.linux.kernel/1315719). This updated
>>>   module is part of the linux-image-3.5.0-11-generic package. Using this
>>>   module renders the system unbootable (For reasons probably described
>>>   in the logs, but currently beyond my knowledge, stacktraces can be
>>>   seen though)
>>>
>>>   I have applied this patch before through dkms and had the exact same
>>>   problems. So I removed the patch, it is now part of the ubuntu kernel
>>>   though.
>>>
>>>   The behaviour seems somewhat random, sometimes the system boots, and
>>>   the Function hotkeys (keyboard backlight, volume etc) work (except the
>>>   known problem with the brightness keys and ambient light sensor). But
>>>   most of the time the system simply wont boot. I can however first
>>>   start the system in recovery mode, and then proceed normal boot, the
>>>   problem does not occur then.
>>>
>>>   Hardware: Asus Zenbook UX32V
>>>
>>>   If further information/testing is needed, please contact me.
>>>
>>>   ProblemType: Bug
>>>   DistroRelease: Ubuntu 12.10
>>>   Package: linux-image-3.5.0-11-generic 3.5.0-11.11
>>>   ProcVersionSignature: Ubuntu 3.5.0-10.10-generic 3.5.1
>>>   Uname: Linux 3.5.0-10-generic x86_64
>>>   ApportVersion: 2.5.1-0ubuntu2
>>>   Architecture: amd64
>>>   AudioDevicesInUse:
>>>    USER        PID ACCESS COMMAND
>>>    /dev/snd/controlC0:  peterrus   2343 F.... pulseaudio
>>>    /dev/snd/pcmC0D0c:   peterrus   2343 F...m pulseaudio
>>>    /dev/snd/pcmC0D0p:   peterrus   2343 F...m pulseaudio
>>>   Date: Sun Aug 26 18:08:05 2012
>>>   EcryptfsInUse: Yes
>>>   HibernationDevice: RESUME=UUID=2e120efe-dafa-40e8-868d-06223b0be158
>>>   InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64
>>> (20120627)
>>>   MachineType: ASUSTeK COMPUTER INC. UX32VD
>>>   ProcEnviron:
>>>    TERM=xterm
>>>    PATH=(custom, user)
>>>    LANG=en_US.UTF-8
>>>    SHELL=/bin/bash
>>>   ProcFB: 0 inteldrmfb
>>>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-10-generic
>>> root=UUID=9bb3948b-2fd3-46c4-b0bb-0ae32a87278a ro quiet splash
>>> pcie_aspm=force drm.vblankoffdelay=1 i915.semaphores=1 nmi_watchdog=0
>>>   RelatedPackageVersions:
>>>    linux-restricted-modules-3.5.0-10-generic N/A
>>>    linux-backports-modules-3.5.0-10-generic  N/A
>>>    linux-firmware                            1.90
>>>   SourcePackage: linux
>>>   StagingDrivers: rts5139
>>>   UpgradeStatus: No upgrade log present (probably fresh install)
>>>   dmi.bios.date: 06/29/2012
>>>   dmi.bios.vendor: American Megatrends Inc.
>>>   dmi.bios.version: UX32VD.207
>>>   dmi.board.asset.tag: ATN12345678901234567
>>>   dmi.board.name: UX32VD
>>>   dmi.board.vendor: ASUSTeK COMPUTER INC.
>>>   dmi.board.version: 1.0
>>>   dmi.chassis.asset.tag: No Asset Tag
>>>   dmi.chassis.type: 10
>>>   dmi.chassis.vendor: ASUSTeK COMPUTER INC.
>>>   dmi.chassis.version: 1.0
>>>   dmi.modalias:
>>> dmi:bvnAmericanMegatrendsInc.:bvrUX32VD.207:bd06/29/2012:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
>>>   dmi.product.name: UX32VD
>>>   dmi.product.version: 1.0
>>>   dmi.sys.vendor: ASUSTeK COMPUTER INC.
>>>
>>> To manage notifications about this bug go to:
>>>
>>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1041883/+subscriptions
>>>
>>
>>
>