** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
** Summary changed:
- [Gateway NV55C] Two backlight interfaces that wont adjust backlight.
+ 8086:0046 [Gateway NV55C] Two backlight interfaces that wont adjust backlight.
--
You received this bug notification because you are a m
** Tags removed: kernel-bug-exists-upstream
** Tags added: needs-upstream-testing regression-potential
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1173961
Title:
[Gateway NV55C] Two backlight inte
** Description changed:
I couldn't get the backlight to work after I upgraded to 13.04.
WORKAROUND: The only grub lines that seem to work are these:
GRUB_CMDLINE_LINUX="acpi_osi=Linux acpi_backlight=vendor"
GRUB_CMDLINE_LINUX="acpi_osi="
I tried changing the grub parameters, and af
I didn't get an immediate failure and it's been ten minutes so I think
we're good.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1173961
Title:
[Gateway NV55C] Two backlight interfaces that wont adj
Max Oropeza, when you compose an e-mail via gmail, you would need to click
"Plain Text", as noted in:
https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Overview_on_Reporting_Bugs_Upstream
>"First Step: E-Mail the Maintainer Process
Please note, when E-Mailing a maintainer mailing list
I got a failure saying
"The error that the other server returned was: 550 5.7.1 Content-Policy reject
msg: The message contains HTML subpart, therefore we consider it SPAM or
Outlook Virus. TEXT/PLAIN is accepted.! BF:; S1752586Ab3HCWEZ"
Is there a way around it? I just copy and pasted from wh
I thought that was for the second step... Ok then, sending sending it
right now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1173961
Title:
[Gateway NV55C] Two backlight interfaces that wont adjus
Max Oropeza, as per the previously noted URL, it advises you to fill out all
the below information and send to appropriate mailing list (which would be
linux-acpi in this case):
[1.] One line summary of the problem:
Paste the downstream bug title.
[2.] Full description of the problem/report:
Pas
It doesn't really say what to say just who to send it to. Which is why I
included this page. It only said to CC this page so emails can appear
here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/117396
Max Oropeza, if you want to know what to say, then you would want to
read what was posted to you in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1173961/comments/17
.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
Max Oropeza, the issue you are reporting is an upstream one. Could you
please report this problem through the appropriate channel by following
the instructions _verbatim_ at
https://wiki.ubuntu.com/Bugs/Upstream/kernel#KernelTeam.2BAC8-KernelTeamBugPolicies.Overview_on_Reporting_Bugs_Upstream
?
Th
When I'd do a fresh install starting with 12.04 (that's when I got the
laptop I'm using now) the backlight wouldn't work but it was just a
simple solution by changing the GRUB line to
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_backlight=vendor". So when
the time came to update to 12.10 it happen
Max Oropeza, did this problem not occur in a release prior to Raring?
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1173961
Title:
So, I was able to install the kernel version 3.11.0-999-generic. Once I
rebooted, there was no difference. I changed the GRUB to
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_backlight=vendor" AND
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_osi='!Windows 2012" AND
GRUB_CMDLINE_LINUX_DEFAULT
** Tags removed: kernel-bug-exists-upstream-v3.9 needs-upstream-testing
** Tags added: kernel-bug-exists-upstream
kernel-bug-exists-upstream-3.11.0-999-generic
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of
Max Oropeza, thank you for updating your BIOS. Could you please test the latest
upstream kernel available following
https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional
upstream developers to examine the issue. Please do not test the kernel in the
mainline kernels archive dir
OK, so I was able to update my BIOS by installing Windows again.
Rebooted into Ubuntu and nothing happened. Nothing's changed I got this
from the terminal
maxo@Dayman:~$ sudo dmidecode -s bios-version && sudo dmidecode -s
bios-release-date
[sudo] password for maxo:
V1.30
08/13/2012
--
You rec
Christopher, I don't know how to update the BIOS on a full Ubuntu
computer and Ubuntu forums are still down. Do you by anychance know how
to do it? It came in a zip file.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
Max Oropeza, as per
http://support.gateway.com/us/en/product/default.aspx?tab=1&modelId=3265
an update is available for your BIOS (1.30). If you update to this, does
it change anything?
If not, could you please both specify what happened, and provide the output of
the following terminal command:
19 matches
Mail list logo