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 <email address hidden> wrote:
> 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 = led on. This used to be the other way around as far as I remember (and
> actually checked)
>
>
> On Wed, Sep 19, 2012 at 8:25 PM, PJ P <email address hidden> wrote:
>
>> 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 <email address hidden>wrote:
>>
>>> 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 would be unresponsive and at a black screen, but most
>>> times the caps lock would be flashing when the boot failed). I'd give it
>>> a day more of booting to see if it is stable. Seems good at this stage
>>> though.
>>>
>>> --
>>> 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
>>>
>>
>>
>
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 <email address hidden> wrote:
> If so: boots the first time, will try a few more boots after this post. people. canonical. com/~jsalisbury /lp1041883/ linux-image- 3.5.0-11- generic_ 3.5.0-11. 11~lp1041883v2_ amd64.deb( and its accompanying debs) /bugs.launchpad .net/bugs/ 1041883 comments. gmane.org/ gmane.linux. kernel/ 1315719). This updated 3.5.0-11- generic package. Using this 3.5.0-11- generic 3.5.0-11.11 ature: Ubuntu 3.5.0-10.10-generic 3.5.1 UUID=2e120efe- dafa-40e8- 868d-06223b0be1 58 /boot/vmlinuz- 3.5.0-10- generic 9bb3948b- 2fd3-46c4- b0bb-0ae32a8727 8a ro quiet splash lay=1 i915.semaphores=1 nmi_watchdog=0 ersions: d-modules- 3.5.0-10- generic N/A -modules- 3.5.0-10- generic N/A asset.tag: ATN123456789012 34567 asset.tag: No Asset Tag version: 1.0 MegatrendsInc. :bvrUX32VD. 207:bd06/ 29/2012: svnASUSTeKCOMPU TERINC. :pnUX32VD: pvr1.0: rvnASUSTeKCOMPU TERINC. :rnUX32VD: rvr1.0: cvnASUSTeKCOMPU TERINC. :ct10:cvr1. 0: version: 1.0 /bugs.launchpad .net/ubuntu/ +source/ linux/+ bug/1041883/ +subscriptions
> 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 = led on. This used to be the other way around as far as I remember (and
> actually checked)
>
>
> On Wed, Sep 19, 2012 at 8:25 PM, PJ P <email address hidden> wrote:
>
>> Assuming you are talking about this one:
>>
>>
>> http://
>>
>> On Wed, Sep 19, 2012 at 7:21 PM, BlueHawk <email address hidden>wrote:
>>
>>> 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 would be unresponsive and at a black screen, but most
>>> times the caps lock would be flashing when the boot failed). I'd give it
>>> a day more of booting to see if it is stable. Seems good at this stage
>>> though.
>>>
>>> --
>>> You received this bug notification because you are subscribed to the bug
>>> report.
>>> https:/
>>>
>>> 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://
>>> module is part of the linux-image-
>>> 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-
>>> ProcVersionSign
>>> 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=
>>> 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=
>>> root=UUID=
>>> pcie_aspm=force drm.vblankoffde
>>> RelatedPackageV
>>> linux-restricte
>>> linux-backports
>>> 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.
>>> dmi.board.name: UX32VD
>>> dmi.board.vendor: ASUSTeK COMPUTER INC.
>>> dmi.board.version: 1.0
>>> dmi.chassis.
>>> dmi.chassis.type: 10
>>> dmi.chassis.vendor: ASUSTeK COMPUTER INC.
>>> dmi.chassis.
>>> dmi.modalias:
>>> dmi:bvnAmerican
>>> dmi.product.name: UX32VD
>>> dmi.product.
>>> dmi.sys.vendor: ASUSTeK COMPUTER INC.
>>>
>>> To manage notifications about this bug go to:
>>>
>>> https:/
>>>
>>
>>
>