Regression: backlight status not maintained after reboot, Vaio PCG V505DX

Bug #379960 reported by Michael Doube
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Low
Unassigned

Bug Description

The backlight was previously (Intrepid) fully supported on this notebook, but now (Jaunty) the status of the backlight is reset to very dim on reboot. This means that the user has to increase backlight to something sensible just to see the login screen.

The notebook is a Vaio PCG-V505DX with ATi Radeon graphics:
01:00.0 VGA compatible controller: ATI Technologies Inc M9+ 5C61 [Radeon Mobility 9200 (AGP)] (rev 01)

]$ uname -a
Linux johnny 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC 2009 i686 GNU/Linux

This is possibly a duplicate of bug #12637

Tags: jaunty
Revision history for this message
Michael Doube (michael-doube) wrote :
Revision history for this message
Michael Doube (michael-doube) wrote :
Revision history for this message
Michael Doube (michael-doube) wrote :
Bryce Harrington (bryce)
Changed in xserver-xorg-video-ati (Ubuntu):
status: New → Confirmed
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Michael,

Do you know if this issue remains with the latest Karmic? If so, might be good to also attach the following:

sudo acpidump -o > acpidump.log

Revision history for this message
Michael Doube (michael-doube) wrote :

Leann

I'm unable to test a reboot on Karmic alpha 3 but I can test suspend-resume from a live CD. Backlight brightness is maintained correctly in the suspend-resume case.

Heres acpidump just in case it's helpful.

Mike

Revision history for this message
Joanna Laurson (joanna-laurson) wrote : Re: [Bug 379960] Re: Regression: backlight status not maintained after reboot, Vaio PCG V505DX

you replied to me...?

2009/8/5 Michael Doube <email address hidden>

> Leann
>
> I'm unable to test a reboot on Karmic alpha 3 but I can test suspend-
> resume from a live CD. Backlight brightness is maintained correctly in
> the suspend-resume case.
>
> Heres acpidump just in case it's helpful.
>
> Mike
>
> ** Attachment added: "acpidump.log"
> http://launchpadlibrarian.net/29934408/acpidump.log
>
> --
> Regression: backlight status not maintained after reboot, Vaio PCG V505DX
> https://bugs.launchpad.net/bugs/379960
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in The Linux Kernel: New
> Status in “xserver-xorg-video-ati” package in Ubuntu: Confirmed
>
> Bug description:
> The backlight was previously (Intrepid) fully supported on this notebook,
> but now (Jaunty) the status of the backlight is reset to very dim on reboot.
> This means that the user has to increase backlight to something sensible
> just to see the login screen.
>
> The notebook is a Vaio PCG-V505DX with ATi Radeon graphics:
> 01:00.0 VGA compatible controller: ATI Technologies Inc M9+ 5C61 [Radeon
> Mobility 9200 (AGP)] (rev 01)
>
> ]$ uname -a
> Linux johnny 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC 2009
> i686 GNU/Linux
>
> This is possibly a duplicate of bug #12637
>

Bryce Harrington (bryce)
tags: added: jaunty
Bryce Harrington (bryce)
affects: xserver-xorg-video-ati (Ubuntu) → linux (Ubuntu)
Revision history for this message
Michael Doube (michael-doube) wrote :

Checking this out on Jaunty and backlight is set to 100% brightness on a boot from cold, while the backlight level is set correctly to the previous value after suspend-resume.

]$ uname -a
Linux johnny 2.6.28-14-generic #47-Ubuntu SMP Sat Jul 25 00:28:35 UTC 2009 i686 GNU/Linux

Revision history for this message
Joseph Salisbury (jsalisbury) wrote : Unsupported series, setting status to "Won't Fix".

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux:
status: New → Won't Fix
Revision history for this message
penalvch (penalvch) wrote :

Michael Doube, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available (not the daily folder, but the one at the top) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.13-rc4

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

no longer affects: linux (Ubuntu)
affects: linux → linux (Ubuntu)
Changed in linux (Ubuntu):
importance: Undecided → Low
status: Won't Fix → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.