Emachines e525 cant see if turned comp, cant change brightness

[Jānis Kangarooo]

This is since 11.04 and now im reporting it from 11.10
This bug doesnt exist in 10.04 but about 10.10 i dont know.
1. if i turn comp on- all is black so i cant see anything- it reacts if i make volume up/down so i know its turned on
also cant change brightness
2. i was able to manage when changing brightness once up and once down right before grub starts loading then all is seenable but still cant change brightess so its max all the time.
If i press brightness shortcut fn+brightnessDown/Up indicator shows up in screen but brightess doesnt changes.
One interesting thing if i fn+brightnessUp then i get symbol ± so 10 times making brightness up would give me in text editor ±±±±±±±±±± even thought its already to max and indicator also shows its max.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: xorg 1:7.6+7ubuntu7
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic i686
ApportVersion: 1.23-0ubuntu3
Architecture: i386
CasperVersion: 1.287
Date: Sat Nov 12 18:49:00 2011
DistroCodename: oneiric
DistroVariant: ubuntu
LiveMediaBuild: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)

[Timothy Mayoh (timothy-m-deactivatedaccount)]

I have this model of computer and you seem to be suffering from bug 765438, same as me.

[Jānis Kangarooo (kangarooo)]

post a bug with that system using loggin in with my workaround and post bug with that system so proof is made

[penalvch (penalvch)]

Kangarooo Jānis, 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 all the way at the bottom) 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.12-rc7

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.

[Launchpad Janitor (janitor)]

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

[Jānis Kangarooo (kangarooo)]

Ill test it tomorrow

[Launchpad Janitor (janitor)]

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