LCD Brightness on Laptop Always Set Very Low at Boot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Medium
|
Ben Collins | ||
linux-source-2.6.15 (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
On my Gateway 7405GX laptop (AMD64), the screen brightness "dims" too low at boot. It seems
to do this after GRUB. Therefore, I must increase the screen brightness each time I reboot
the computer (using Fn button and F7/F8). I have tried adjusting the limited settings in the
BIOS, but nothing changes. Also, this dimming effect occurs when running of AC Adapter and
battery. Ideally, the screen should initialize at full brightness when running on AC
or "remember" the previous setting from the previous saved settings on battery. Basically,
this is just annoying...not a showstopper bug.
Matt Zimmerman (mdz) wrote : | #1 |
reh4c (gene-hoffler) wrote : | #2 |
It says <Not Supported>. Hmmm...I wonder why. Suse 9.2 did the same
thing at boot, but Mandrake 10.1 did not dim at startup. This was
Mandrake for the i586, since the AMD64 version would not install
properly ;(
reh4c (gene-hoffler) wrote : | #3 |
Here is the output from 'dmesg' after applying all synaptic updates today (11
Feb 05). I hope this helps with the default screen brightness issue. Also, I
can't hibernate this computer...only screensaver and turn off LCD function properly:
ole=tty0 quiet splash)
Linux version 2.6.10-2-amd64-k8 (buildd@king) (gcc version 3.3.5 (Debian
1:3.3.5-6ubuntu1)) #1 Fri Feb 4 09:19:24 UTC 2005
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000d8000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000001fef0000 (usable)
BIOS-e820: 000000001fef0000 - 000000001fefb000 (ACPI data)
BIOS-e820: 000000001fefb000 - 000000001ff00000 (ACPI NVS)
BIOS-e820: 000000001ff00000 - 0000000020000000 (reserved)
BIOS-e820: 00000000fffe0000 - 0000000100000000 (reserved)
No mptable found.
On node 0 totalpages: 130800
DMA zone: 4096 pages, LIFO batch:1
Normal zone: 126704 pages, LIFO batch:16
HighMem zone: 0 pages, LIFO batch:1
ACPI: RSDP (v000 PTLTD ) @ 0x00000000000f8280
ACPI: RSDT (v001 Arima 161Fh 0x06040000 LTP 0x00000000) @ 0x000000001fef6b6e
ACPI: FADT (v001 Arima 161Fh 0x06040000 PTL_ 0x000f4240) @ 0x000000001fefae66
ACPI: SSDT (v001 PTLTD POWERNOW 0x06040000 LTP 0x00000001) @ 0x000000001fefaeda
ACPI: MADT (v001 PTLTD APIC 0x06040000 LTP 0x00000000) @
0x000000001fefafb0
ACPI: DSDT (v001 Arima 161Fh 0x06040000 MSFT 0x0100000e) @ 0x0000000000000000
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Processor #0 15:4 APIC version 16
ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 1, version 3, address 0xfec00000, GSI 0-23
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge)
ACPI: IRQ0 used by override.
ACPI: IRQ2 used by override.
ACPI: IRQ10 used by override.
Setting APIC routing to flat
Using ACPI (MADT) for SMP configuration information
Checking aperture...
CPU 0: aperture @ e0000000 size 256 MB
Built 1 zonelists
Kernel command line: root=/dev/hda1 ro console=tty0 quiet splash
Initializing CPU#0
PID hash table entries: 2048 (order: 11, 65536 bytes)
time.c: Using 1.193182 MHz PIT timer.
time.c: Detected 2004.618 MHz processor.
Console: colour VGA+ 80x25
Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
Inode-cache hash table entries: 32768 (order: 6, 262144 bytes)
Memory: 507040k/523200k available (1767k kernel code, 15496k reserved, 1003k
data, 148k init)
Calibrating delay loop... 3948.54 BogoMIPS (lpj=1974272)
Security Framework v1.0.0 initialized
SELinux: Disabled at boot.
Mount-cache hash table entries: 256 (order: 0, 4096 bytes)
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 1024K (64 bytes/line)
CPU: Mobile AMD Athlon(tm) 64 Processor 3200+ stepping 0a
ACPI: Looking for DSDT in initrd... not found!
Using local APIC NMI watchdog using perfctr0
Using local APIC timer interrupts.
Detected 12.528 MHz APIC timer.
checking if image is initramfs...it isn't (bad gzip magic numbers); looks like
an init...
Matt Zimmerman (mdz) wrote : | #4 |
You are running an old kernel; please install the "linux-k8" package which will
always give you the latest version.
reh4c (gene-hoffler) wrote : | #5 |
The screen still dims, and the ACPI issues seem to persist. Here's my latest
'dmesg' output. Is this the latest 'linux-K8' kernel? Thanks.
root@ubuntu:
Bootdata ok (command line is root=/dev/hda1 ro console=tty0 quiet splash)
Linux version 2.6.10-3-amd64-k8 (buildd@yellow) (gcc version 3.3.5 (Debian
1:3.3.5-8ubuntu2)) #1 Tue Feb 15 09:41:07 UTC 2005
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000d8000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000001fef0000 (usable)
BIOS-e820: 000000001fef0000 - 000000001fefb000 (ACPI data)
BIOS-e820: 000000001fefb000 - 000000001ff00000 (ACPI NVS)
BIOS-e820: 000000001ff00000 - 0000000020000000 (reserved)
BIOS-e820: 00000000fffe0000 - 0000000100000000 (reserved)
No mptable found.
On node 0 totalpages: 130800
DMA zone: 4096 pages, LIFO batch:1
Normal zone: 126704 pages, LIFO batch:16
HighMem zone: 0 pages, LIFO batch:1
ACPI: RSDP (v000 PTLTD ) @ 0x00000000000f8280
ACPI: RSDT (v001 Arima 161Fh 0x06040000 LTP 0x00000000) @ 0x000000001fef6b6e
ACPI: FADT (v001 Arima 161Fh 0x06040000 PTL_ 0x000f4240) @ 0x000000001fefae66
ACPI: SSDT (v001 PTLTD POWERNOW 0x06040000 LTP 0x00000001) @ 0x000000001fefaeda
ACPI: MADT (v001 PTLTD APIC 0x06040000 LTP 0x00000000) @
0x000000001fefafb0
ACPI: DSDT (v001 Arima 161Fh 0x06040000 MSFT 0x0100000e) @ 0x0000000000000000
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Processor #0 15:4 APIC version 16
ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 1, version 3, address 0xfec00000, GSI 0-23
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge)
ACPI: IRQ0 used by override.
ACPI: IRQ2 used by override.
ACPI: IRQ10 used by override.
Setting APIC routing to flat
Using ACPI (MADT) for SMP configuration information
Checking aperture...
CPU 0: aperture @ e0000000 size 256 MB
Built 1 zonelists
Kernel command line: root=/dev/hda1 ro console=tty0 quiet splash
Initializing CPU#0
PID hash table entries: 2048 (order: 11, 65536 bytes)
time.c: Using 1.193182 MHz PIT timer.
time.c: Detected 2004.609 MHz processor.
Console: colour VGA+ 80x25
Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
Inode-cache hash table entries: 32768 (order: 6, 262144 bytes)
Memory: 507040k/523200k available (1769k kernel code, 15508k reserved, 1004k
data, 148k init)
Calibrating delay loop... 3948.54 BogoMIPS (lpj=1974272)
Security Framework v1.0.0 initialized
SELinux: Disabled at boot.
Mount-cache hash table entries: 256 (order: 0, 4096 bytes)
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 1024K (64 bytes/line)
CPU: Mobile AMD Athlon(tm) 64 Processor 3200+ stepping 0a
ACPI: Looking for DSDT in initrd... not found!
Using local APIC NMI watchdog using perfctr0
Using local APIC timer interrupts.
Detected 12.528 MHz APIC timer.
checking if image is initramfs...it isn't (bad gzip magic numbers); looks like
an initrd
NET: Register...
reh4c (gene-hoffler) wrote : | #6 |
The same issues persist. Here's the 'dmesg' output after a kernel upgrade (25
Feb 05):
gene@ubuntu:~$ dmesg
Bootdata ok (command line is root=/dev/hda1 ro console=tty0 quiet splash)
Linux version 2.6.10-4-amd64-k8 (buildd@king) (gcc version 3.3.5 (Debian
1:3.3.5-8ubuntu2)) #1 Fri Feb 25 05:26:30 UTC 2005
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000d8000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000001fef0000 (usable)
BIOS-e820: 000000001fef0000 - 000000001fefb000 (ACPI data)
BIOS-e820: 000000001fefb000 - 000000001ff00000 (ACPI NVS)
BIOS-e820: 000000001ff00000 - 0000000020000000 (reserved)
BIOS-e820: 00000000fffe0000 - 0000000100000000 (reserved)
No mptable found.
On node 0 totalpages: 130800
DMA zone: 4096 pages, LIFO batch:1
Normal zone: 126704 pages, LIFO batch:16
HighMem zone: 0 pages, LIFO batch:1
ACPI: RSDP (v000 PTLTD ) @ 0x00000000000f8280
ACPI: RSDT (v001 Arima 161Fh 0x06040000 LTP 0x00000000) @ 0x000000001fef6b6e
ACPI: FADT (v001 Arima 161Fh 0x06040000 PTL_ 0x000f4240) @ 0x000000001fefae66
ACPI: SSDT (v001 PTLTD POWERNOW 0x06040000 LTP 0x00000001) @ 0x000000001fefaeda
ACPI: MADT (v001 PTLTD APIC 0x06040000 LTP 0x00000000) @
0x000000001fefafb0
ACPI: DSDT (v001 Arima 161Fh 0x06040000 MSFT 0x0100000e) @ 0x0000000000000000
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Processor #0 15:4 APIC version 16
ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 1, version 3, address 0xfec00000, GSI 0-23
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge)
ACPI: IRQ0 used by override.
ACPI: IRQ2 used by override.
ACPI: IRQ10 used by override.
Setting APIC routing to flat
Using ACPI (MADT) for SMP configuration information
Checking aperture...
CPU 0: aperture @ e0000000 size 256 MB
Built 1 zonelists
Kernel command line: root=/dev/hda1 ro console=tty0 quiet splash
Initializing CPU#0
PID hash table entries: 2048 (order: 11, 65536 bytes)
time.c: Using 1.193182 MHz PIT timer.
time.c: Detected 2004.626 MHz processor.
Console: colour VGA+ 80x25
Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
Inode-cache hash table entries: 32768 (order: 6, 262144 bytes)
Memory: 507088k/523200k available (1732k kernel code, 15460k reserved, 993k
data, 148k init)
Calibrating delay loop... 3948.54 BogoMIPS (lpj=1974272)
Security Framework v1.0.0 initialized
SELinux: Disabled at boot.
Mount-cache hash table entries: 256 (order: 0, 4096 bytes)
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 1024K (64 bytes/line)
CPU: Mobile AMD Athlon(tm) 64 Processor 3200+ stepping 0a
ACPI: Looking for DSDT in initrd... not found!
Using local APIC NMI watchdog using perfctr0
Using local APIC timer interrupts.
Detected 12.528 MHz APIC timer.
checking if image is initramfs...it isn't (bad gzip magic numbers); looks like
an initrd
NET: Registered protocol family 16
PCI: Using configuration type 1
mtrr: v2.0 (2...
reh4c (gene-hoffler) wrote : | #7 |
Update on this screen dimming issue. On my AMD64 laptop, Mandriva Limited Edition 2005 (for i386)
does not dim the screen at bootup (Mandrake 10.1 i386 did not either). However, Ubuntu Hoary,
VidaLinux 1.2 (for AMD64), and Suse 9.3 (full version) continue to have this problem. Obviously,
there must be some package/setting that causes it in these distros. It's very annoying since the
screen must be increased from the lowest brightness setting after each reboot/startup of the laptop.
Hibernating does work in Hoary, so that helps keep me from rebooting too much and having to adjust the
brightness. On hibernate, Hoary does report some BIOS bugs, so maybe this has something to do with
the screen dimming. I'm not a programmer, but wanted to report this bug as best I can.
Matthew Garrett (mjg59) wrote : | #8 |
So the brightness changes when you boot normally, but not when you hibernate?
What's the last line that's printed before the screen brightness changes?
Tollef Fog Heen (tfheen) wrote : | #9 |
If you could please respond to Matthew's questions, it would make it easier for us to debug this problem.
reh4c (gene-hoffler) wrote : | #10 |
Honestly, I'm putting this laptop on Ebay, because Gateway's lack of support in fixing a hinge
cracking issue has really pissed me off. This is the second time the laptop's hinge has cracked, and
this time they won't ship it to my overseas military address. Anyway, when the laptop boots, the
bootup text quickly scrolls down the screen. When, it says "Ok, booting the kernel...", that's when
brightness is automatically switched to very low. Then, I immediately use th "Fn" + brightness
up/down (F7/F8) to increase it back up. Actually, the laptop buttons [Fn and brightness minus (F7)]
must be used before [Fn and brightness plus (F8)] will work to successfully increase the brightness.
This is probably some sort of BIOS bug, but that's all the information I can provide with my limited
knowledge. Sorry about selling it, but I must do it before the warranty ends. Thanks.
Tollef Fog Heen (tfheen) wrote : | #11 |
Ok, thank you. This seems to be a kernel bug of some sort, so reassigning.
Ben Collins (ben-collins) wrote : | #12 |
This bug has been flagged because it is old and possibly inactive. It may or may
not be fixed in the latest release (Breezy Badger 5.10). It is being marked as
"NEEDSINFO". In two weeks time, if the bug is not updated back to "NEW" and
validated against Breezy, it will be closed.
This is needed in order to help manage the current bug list for the kernel. We
would like to fix all bugs, but need users to test and help with debugging.
If this change was in error for this bug, please respond and make the
appropriate change (or email <email address hidden> if you cannot make the
change).
Thanks for your help.
reh4c (gene-hoffler) wrote : | #13 |
I intended to sell this laptop. However, I am going to hold onto
it. Currently, it's being fixed by Gateway (Arima) for a defective
DVD burner. Hopefully, I will get it shipped back to me within 2
weeks. Immediately upon receiving it, I will test the final Breezy
64-bit release to see if the "brightness bug" still exists. Please
keep this bug report open and I'll report back. Thanks.
Ben Collins (ben-collins) wrote : | #14 |
Please confirm with breezy. If it still applies to breezy, please also test
dapper kernel (2.6.15) or wait for dapper flight 2 cd's due in a few days.
reh4c (gene-hoffler) wrote : | #15 |
I just received the laptop back from repair. First, I used an i386 live CD to test out the laptop.
The screen did not dim to the lowest setting when booting from this liveCD. However, when I booted
from the 64bit installation version (5.10 Breezy), the laptop dimming problem returned. As I
previously stated, I must increase the brightness level from bare minimum (can hardly read screen) to
a reasonable level at every reboot. Please advise me on how to capture debug info. to help you out in
solving this pain in the butt issue.
reh4c (gene-hoffler) wrote : | #16 |
Problem still exists with Dapper Flight 2. Please advise me on how
to capture debug data, etc. to help solve the issue.
Ben Collins (ben-collins) wrote : | #17 |
(In reply to comment #15)
> I just received the laptop back from repair. First, I used an i386 live CD to
test out the laptop.
> The screen did not dim to the lowest setting when booting from this liveCD.
However, when I booted
> from the 64bit installation version (5.10 Breezy), the laptop dimming problem
returned. As I
> previously stated, I must increase the brightness level from bare minimum (can
hardly read screen) to
> a reasonable level at every reboot. Please advise me on how to capture debug
info. to help you out in
> solving this pain in the butt issue.
Can you send dmesg output from the working i386 boot?
reh4c (gene-hoffler) wrote : | #18 |
- dmesg output as request Edit (15.3 KiB, text/plain)
Created an attachment (id=5449)
dmesg output as request
Here's the dmesg output from th i386 5.10 live cd. Hope it helps. Merry
Christmas!
Matt Zimmerman (mdz) wrote : | #19 |
This bug is targeting Dapper, but seems to be an upstream issue with no fix in sight. Ben, is this actually feasible to fix for Dapper?
Johnny Jelinek IV (johnnyjiv) wrote : | #20 |
actually -- to me, this is a showstopper :/ sad day.
Please fix asap!
reh4c (gene-hoffler) wrote : | #21 |
Problem still exists on Dapper AMD64 RC. What a pain!
Jame (lliyan) wrote : | #22 |
It sounds the same problem I ever encountered.
Method: Set up the brightness from the menu:
System -> Preference -> Power manager ~ brightness (AC , battery)
-jame
reh4c (gene-hoffler) wrote : Re: [Bug 12637] Re: LCD Brightness on Laptop Always Set Very Low at Boot | #23 |
Thanks. I sold the Gateway 7405GX laptop with that
issue. Overall, it was a low-quality piece of junk.
No more Gateways for me.
--- Jame <email address hidden> wrote:
> It sounds the same problem I ever encountered.
>
> Method: Set up the brightness from the menu:
> System -> Preference -> Power manager ~ brightness
> (AC , battery)
>
> -jame
>
> --
> LCD Brightness on Laptop Always Set Very Low at Boot
> https:/
>
Richard Green (rtg-aapsc) wrote : | #24 |
Bug confirmed still present on emachines M6810 with kernel 2.6.20-9 x86_64 (Feisty herd 4+)
AMD Athlon 64 3200+; ATI Radeon mobility 9600
Just before it dimms, the graphical screen is replaced by a text screen, and I see the words 'Kernel is Active' briefly appear at the bottom.
Johnny Jelinek IV (johnnyjiv) wrote : | #25 |
it still happens on my m6805.
On 2/28/07, Richard Green <email address hidden> wrote:
>
> Bug confirmed still present on emachines M6810 with kernel 2.6.20-9 x86_64
> (Feisty herd 4+)
> AMD Athlon 64 3200+; ATI Radeon mobility 9600
> Just before it dimms, the graphical screen is replaced by a text screen,
> and I see the words 'Kernel is Active' briefly appear at the bottom.
>
> --
> LCD Brightness on Laptop Always Set Very Low at Boot
> https:/
>
Richard Green (rtg-aapsc) wrote : | #26 |
Still happening on Feisty herd 5 Kubuntu live CD.
Richard Green (rtg-aapsc) wrote : | #27 |
Confirmed again on Kubuntu Feisty daily build 20070401 amd_64
Steven Harms (sharms) wrote : | #28 |
Can confirm on a Emachines M6805 using amd_64 on Feisty beta.
Guido Conaldi (guido-conaldi) wrote : | #29 |
Can confirm on my vaio VGN-S1XP with Feisty up-to-date.
Cannot be fixed using Power manager because it has never supported my laptop's LCD. Brightness can be set only with FN keys and it has to be done at every boot, but at least in Edgy the system did not 'forget' the brightness level I set at previous boot.
Aaron Peromsik (aperomsik) wrote : | #30 |
Guido, did you switch from 32-bit to 64-bit for Feisty? On my m6805, any 32-bit distro I have tried has not had this bug, but any 64-bit version does. Currently using 32-bit Edgy, partly to avoid this issue.
Guido Conaldi (guido-conaldi) wrote : | #31 |
No Aaron, I did not. I have always used 32-bit version (I have a Pentium M).
p1977p (1977boy) wrote : | #32 |
- copy of the brightness file Edit (61 bytes, text/plain)
I'm running Xubuntu Feisty on my AMD Turion 64 laptop with an Nvidia 6150 graphics card. I cannot use the Fn key for any purpose, including adjusting the brightness. somewhere on the net I found that one could do this by "echo {reqd br. level} > /proc/acpi/
Andreas Mohr (andi) wrote : | #33 |
I don't know, so far the debugging hints in here haven't been too detailed/helpful to actually be able to analyze/resolve the problem as an enduser.
I think that since it happens immediately after bootloader and when loading kernel, this may point to vga mode configuration at kernel bootup
triggering the dimming issue (probably some vga BIOS interrupt call either mis-called by Linux or buggy implementation which happens to dim
the display, too).
Please add the vga=ask kernel boot parameter / LILO parameter and try to find out whether choosing some particular value does NOT dim
the display; vga=normal or vga=extended may also be helpful.
If this simple enduser testing doesn't find a way to avoid the dimming, then it might help to completely disable ANY vga card fiddling in kernel;
this might be achieved by trying to completely disable the linux/arch/
very top of this function).
Further places to investigate at would be all video card related files in linux/arch/
Even an enduser could add all sorts of disabling "return;" statements to various video functions there to find a way to prevent this from happening.
And yes, these things obviously mean compiling a kernel from source (take /boot/config... file from existing kernel and copy to linux-2.
make-kpkg kernel_image and install it, tell bootloader to use it, that's one good way to do it).
HTH and good luck!
Andreas Mohr (andi) wrote : | #34 |
Oh, another important thing: does thorough experimentation with vbetool also happen to be able to trigger this problem, after bootup? Would be interesting to know...
Richard Green (rtg-aapsc) wrote : | #35 |
I don't know if I'm up to the challenge of compiling my own kernels. I
haven't done that since about 1.2.x sometime... And that was just to
config in a driver. I'm an old PL/I & COBOL programmer, and quite 'C'
challenged.
One item of note: this happens with amd_64 kernels only. Last week, I
did an installation of ubuntustudio on this machine, and was pleased to
discover that the LCD didn't go dim on me. But then disappointed to
discover that it installed a 32 bit kernel, and gnome. So I went back to
Kubuntu amd_64, then installed the ubuntustudio-audio packages (less one
that's broken on amd64) So it may be that some of that vga-init code
isn't 64-bit clean.
There's another video bug open on this machine, but that has to do with
xorg properly detecting the widescreen 1280x800 mode, and is probably
unrelated to this lower-level vga bug.
-- Rick Green
"Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety."
Guido Conaldi (guido-conaldi) wrote : | #36 |
The same issue came back with Gutsy i386 up-to-date on my vaio s1xp after having been fixed in final Fiesty.
Robert Drake (rdrake-ipsek) wrote : | #37 |
I've been ignoring the problem for a while because I don't reboot often, but I finally decided to check the bug again to see if any progress was happening.
I tried setting vga=ask, the kernel asks what vga mode you want and you're allowed to make your choice while the screen is bright.
after making the choice (doesn't matter which one, they all seem to work) you see the "Kernel is Active" message after a second and the screen dims again.
right after that you see a [PCI] cannot allocate region (not sure what it says after that, it flashes by real fast and it may or may not be related, might be something specific to my machine)
The question I have is this: what changes between the 32bit boot code and the 64bit boot code in regards to video at that stage.. it's very early in the boot process so nothing should be poking anything, but on the other hand it's possible they stored the brightness value in some memory location that the kernel blows away during boot and it's not video related at all.
If I get the chance, I'll start throwing "got here" kprintf's in the kernel in places before "Kernel is Active" to see what I find.
Richard Green (rtg-aapsc) wrote : | #38 |
On Thu, 20 Sep 2007, Robert Drake wrote:
> If I get the chance, I'll start throwing "got here" kprintf's in the
> kernel in places before "Kernel is Active" to see what I find.
>
On my emachines M6810, the 'Kernel alive' message comes on bright,
followed by a message beginning 'kernel mapping tables... ending with
something that might be an address. THEN, the screen dims. So you might
want to insert your debug flags after those messages, not before.
lostangel78 (lostangel78) wrote : | #39 |
Try typing this command in a terminal
xgamma -gamma 0.75
I have posted my own solution here:
http://
Richard Green (rtg-aapsc) wrote : | #40 |
Just booted the Hardy alpha 4 live CD (Kubuntu amd_64), and the LiveCD session booted up normally, without dimming the LCD!
Since this is a working laptop now, I don't want to do a complete reinstall with the hardy alpha. Is there a way I can install just the kernel package from the hardy CD, and have it be a grub option in my normal Gutsy system? (actually ubuntustudio 7.10 w/ kernel 2.6.22-14-rt)
I tried opening the liveCD in synaptic, but the only linux-image packages it finds on the CD appear to be older than the kernel I have installed in Gutsy...
I notice from the package descriptions in adept that Hardy is using a 'generic' kernel for both x86 and x86_64, as well as UP and SMP. The plain x86 kernel in 7.04 didn't exhibit this problem, so is the problem now fixed, or is this 'generic' kernel really an x86 32bit kernel under the covers?
Under Gutsy, the symptoms seem to be:
'Kernel is active' at bottom of screen
'kernel mapping tables...' at bottom of screen
then
[PCI].... appears at the top of the screen, and the screen dimms, almost simultaneously, I can't really tell which is first.
Richard Green (rtg-aapsc) wrote : | #41 |
Here's some more info. I went to system/
Well, that wasn't clean at all! it kills gdm immediately, which blew away my X session, as well as all the apps running, leaving me at a very ugly console with a huge font, reminiscent of my old commodore VIC-20.
I managed to reboot, and it did come up without X, but with the same ugly huge font, so I only saw about 10 lines of text, and my prompt was somewhere below the bottom of the screen, so I was typing blind.
...but the important part is that the screen dimmed, so this is definitely NOT an X issue, it's in the kernel. I also focussed my eyes at the top of the screen during the boot, and I was able to see that the [PCI} allocation... error that was displayed there came up DIM, just before the screen blanks, so the actual sequence is something like this:
'Kernel is alive'
'kernel mapping tables...'
(backlight goes to dim)
'[PCI] allocation'...
<rant>
Once I logged in at the console, I ran startx, and was able to get my desktop. I again went to system/
There is no 'upstart' directory under /etc. There is no upstart manpage. Where do I look for clues? `man init` is still there. scroll to the bottom, its author is Scott James Remnant. So he calls the project upstart, but the binary is still init, just to confuse us, right?
OK, the manpage mentions /etc/event.d. Go browse... rc-default seems to fall thru to runlevel 2. Looking at the /etc/rcn.d directories, I find that runlevel 1 would not start X, but all others 2 - 5 do. So I can probably edit one of those other directories to create a multiuser without X runlevel, but I still don't know how to pass a one-time parm thru grub to select that level. More studying to do, and I'm tired. I'm going to bed now...
</rant>
Johnny Jelinek IV (johnnyjiv) wrote : | #42 |
So you believe it's all kernel's fault? Can you verify it works with Ubuntu
8.04 Alpha 64 along with Kubuntu or should I pop out some CD's? Thanks
Richard!!
On Feb 13, 2008 1:38 AM, Richard Green <email address hidden> wrote:
> Here's some more info. I went to system/
> disabled gdm, thinking I'd reboot to a console, just to see if this was a
> kernel problem, or possibly an xorg problem, since it's happening just
> milliseconds before the screen blanks to switch to X.
> Well, that wasn't clean at all! it kills gdm immediately, which blew
> away my X session, as well as all the apps running, leaving me at a very
> ugly console with a huge font, reminiscent of my old commodore VIC-20.
> I managed to reboot, and it did come up without X, but with the same ugly
> huge font, so I only saw about 10 lines of text, and my prompt was somewhere
> below the bottom of the screen, so I was typing blind.
> ...but the important part is that the screen dimmed, so this is
> definitely NOT an X issue, it's in the kernel. I also focussed my eyes at
> the top of the screen during the boot, and I was able to see that the [PCI}
> allocation... error that was displayed there came up DIM, just before the
> screen blanks, so the actual sequence is something like this:
> 'Kernel is alive'
> 'kernel mapping tables...'
> (backlight goes to dim)
> '[PCI] allocation'...
>
> <rant>
> Once I logged in at the console, I ran startx, and was able to get my
> desktop. I again went to system/
> which AGAIN took immediate action, which in this case tried to start a
> second X server, which failed once, but eventually succeeded (as :1),
> leaving me at the gdm prompt. I have no idea which virtual console I was
> on, but ctrl-alt-f7 got me back to the X session. I probably should file a
> bug elswhere for this usability issue... Or just go back to school. In
> this new age of upstart, how do I cleanly do a one-time reboot to a normal
> console? On my old redhat or suse systems, I always had runlevel 3, but I
> discovered a while back that in ubuntu runlevel 3 is the same as runlevel 5,
> and now with upstart, I have no idea if 'runlevels' even exist anymore, and
> if they do, how to configure and specify them?
> System/
> distinctions, /etc/inittab is gone grrr...
> There is no 'upstart' directory under /etc. There is no upstart manpage.
> Where do I look for clues? `man init` is still there. scroll to the
> bottom, its author is Scott James Remnant. So he calls the project upstart,
> but the binary is still init, just to confuse us, right?
> OK, the manpage mentions /etc/event.d. Go browse... rc-default seems to
> fall thru to runlevel 2. Looking at the /etc/rcn.d directories, I find that
> runlevel 1 would not start X, but all others 2 - 5 do. So I can probably
> edit one of those other directories to create a multiuser without X
> runlevel, but I still don't know how to pass a one-time parm thru grub to
> select that level. More studying to do, and I'm tired. I'm going to bed
> now...
> </rant>
>
> --
> LCD Brightness on La...
Richard Green (rtg-aapsc) wrote : | #43 |
Well, I saw the problem with Ubuntu, Kubuntu, and Ubuntustudio x86_64 at
the 7.10 release, so I don't think it's a desktop issue. Also, last night
I managed to boot clumsily without X and gdm, and I also saw the problem
when there was no X launching, so that kinda confirms it for me that its
not X. It might not be the kernel VGA driver, but what else starts up at
boot, does not depend on X, and could be modifying the display backlight
level?
I'm tied up on an intractible DSL problem for a client right now, so I
can't even think about downloading an Ubuntu hardy alpha CD until later
tonight...
And besides, the Kubuntu hardy alpha CD did NOT show the problem, so
whatever they did to make a 'generic' kernel that works on x86 as well as
x86_64 either fixed or masked the problem.
encompass (encompass) wrote : | #44 |
I have the same issue with the Hardy Alpha 6. I have never had this issue unless I would have the brightness low when I turned the computer off. This is all the time with the system plugged in or running on the battery.
hunterthomson (darden-tyler) wrote : | #45 |
I have the same problems on my Ubuntu 64 bit Hardy 8.04 Lenovo Ideapad Y510 59012891 R intel T5550 1.83Ghz CPU, intel x3100 GPU... My laptop my suspend did work until a update I had like a week ago. My screen fully dims on shutdown and startup AND when VLC media player starts and Dims when games start i.e. Glest, Warzone 2100.... This is a vary in your face problem.
Pierre R (p-radermecker) wrote : | #46 |
I have the same problem after upgrading to Hardy using the "upgrade-manager -d" command. The screen is always dim at boot and I have to manually adjust it after each boot.
I am using a laptop Asus F7F and the 32 bit version.
Look forward to a fix. Thanks.
Pierre R (p-radermecker) wrote : | #47 |
On my laptop the problem has been fixed with the latest hardy updates (I have just uninstalled the evolution-
Thanks.
ajole (ajole) wrote : | #48 |
I have a 20" iMac and have not yet installed any operating system but OS 10.5, which is an upgrade from the 10.4 it had when new. I thought you folks might be interested to know, this bug is affecting my machine even without Ubuntu, as well as several others I know of personally, and if you google it, a lot of folks around the Mac world. I have tried the "unplug it and wait, then plug it in and boot" method, which didn't work. I then tried the "Zap the P-RAM" method which didn't work either. My tech folks are telling me to try the zap method 5 times in a row and see if that works.
Regardless, just wanted you to know this bug may not be an OS issue at all.
encompass (encompass) wrote : | #49 |
Very interesting... but I don't remember having this issue in the last
version of ubuntu. 7.04 or 7.10. This is a very new thing to me. i
should check with perhap installing an old version of ubuntu and see
if it gives the issue. Thanks for the information.
On Tue, Apr 22, 2008 at 1:28 AM, ajole <email address hidden> wrote:
> I have a 20" iMac and have not yet installed any operating system but OS 10.5, which is an upgrade from the 10.4 it had when new. I thought you folks might be interested to know, this bug is affecting my machine even without Ubuntu, as well as several others I know of personally, and if you google it, a lot of folks around the Mac world. I have tried the "unplug it and wait, then plug it in and boot" method, which didn't work. I then tried the "Zap the P-RAM" method which didn't work either. My tech folks are telling me to try the zap method 5 times in a row and see if that works.
> Regardless, just wanted you to know this bug may not be an OS issue at all.
>
>
>
> --
> LCD Brightness on Laptop Always Set Very Low at Boot
> https:/
> You received this bug notification because you are a direct subscriber
> of the bug.
>
Johnny Jelinek IV (johnnyjiv) wrote : | #50 |
This is primarily with the 64-bit version.
On Mon, Apr 21, 2008 at 5:59 PM, encompass <email address hidden> wrote:
> Very interesting... but I don't remember having this issue in the last
> version of ubuntu. 7.04 or 7.10. This is a very new thing to me. i
> should check with perhap installing an old version of ubuntu and see
> if it gives the issue. Thanks for the information.
>
> On Tue, Apr 22, 2008 at 1:28 AM, ajole <email address hidden> wrote:
> > I have a 20" iMac and have not yet installed any operating system but OS
> 10.5, which is an upgrade from the 10.4 it had when new. I thought you
> folks might be interested to know, this bug is affecting my machine even
> without Ubuntu, as well as several others I know of personally, and if you
> google it, a lot of folks around the Mac world. I have tried the "unplug it
> and wait, then plug it in and boot" method, which didn't work. I then tried
> the "Zap the P-RAM" method which didn't work either. My tech folks are
> telling me to try the zap method 5 times in a row and see if that works.
> > Regardless, just wanted you to know this bug may not be an OS issue at
> all.
> >
> >
> >
> > --
> > LCD Brightness on Laptop Always Set Very Low at Boot
> > https:/
> > You received this bug notification because you are a direct subscriber
> > of the bug.
> >
>
> --
> LCD Brightness on Laptop Always Set Very Low at Boot
> https:/
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
Grzegorz (grzegorzborkowski) wrote : | #51 |
I've just upgraded to 8.04 on my Belinea o.book 3 laptop. Now every time system boots, brightness is set to minimum. Functional keys for changing brightness don't work (I think they didn't work before upgrade, in 7.10, too) so I use Gnome applet for changing brightness. After system start, the slider in this applet is always set to 0, and I need to move it up to 100 to be able to work.
Please find the fix for this, as this is really uncomfortable.
encompass (encompass) wrote : | #52 |
Actually, for me this is a 32 bit issue. I really doubt it has
anything to do with the bit in the processor. It seems that when the
brightness is dark, and I try to press the button to make it brighter,
it jumps right to full. When I get my computer back and fixed. I
will test if the brightness jumps to other levels too.
Grzegorz (grzegorzborkowski) wrote : | #53 |
Some more observations:
I downloaded 8.04 and made bootable CD; started fresh live instance from CD. The screen is dark. When I do a first move with touchpad, though, it suddenly jumps to ca 57%. As I already said, the brighntesss Fn buttons don't work, so I use Gnome applet to change brightness to 100%.
I tried to boot also live 7.10 for comparison. The brightness seems ok, but it is hard to say precisely, becuase function keys does not work, and Gnome applet does not work at all.
Fortunatelly, after upgrading to 8.04 I have choice to run also old kernel 2.6.22-14. This kernel runs very well, brightness is ok (though Gnome applet does not work at all, but I don't need it, because brightness is ok).
When now (after booting with old kernel) I tried to run the new kernel, initially brightness was ok, but during loading (somehere around message "loading hardware drivers" - in disabled quiet mode) it fades (not instantly, but slowly - it takes about 1-2 second). Then restart again, now select old kernel - and during loading birghtness goes up at some moment (again not instantly), but this time much after "loading hardware drivers". But please not that the change of brighntess (also manual) seems always delayed, so it is really hard to say what was the trigger.
To put it simply: whenever I run new kernel, it fades brighness somewhere in the middle of loading progress bar (very not-precise). After restart, even manufacturing screen is dimmed. It is until i run old kernel - birghtness go up then during start, and stay high until I run new kernel (manufacturer logo is bright too at restart after running old kernel).
Hope it helps.
BTW. It is really strange for me that such big bug came into LTS version of Ubuntu. Very disappointing.
ajole (ajole) wrote : | #54 |
Just an update on the iMac; I loaded 8.04 and the reFit boot thingy, and it works wonderfully, no brightness issues at all. Did lose the mouse on one boot, but never recurred.
Watchdog (watchdog-lehighacreswatchdog) wrote : | #55 |
I have Ubuntu 8.04 32 bit all updates and having same issue on my laptop. My function keys "change" the brightness but not really. If i turn the brightness all the way down, the screen goes nearly black, as soon as i put brightness at the lowest level it comes to a VERY dim state, and further increasing of the brightness thru the 'F' keys does nothing.
Watchdog (watchdog-lehighacreswatchdog) wrote : | #56 |
Well after reading all this I did a little browsing in the power options and noticed an option to dim the screen when running on bettery (8.04 x86) and I told it not too and reboot. Still had the problem after reboot so I decided to take a look at the bios settings. There was nothing in my biso that can be causing a problem, however on my next boot I no longer had the problem. Odd...
GKid (motosierra) wrote : | #57 |
I have a Lenovo 3000 C200 and the same issue since the upgrade to Hardy (32bit). I was previously running Ubuntu 7.10 (32bit) with kernel 2.6.22-14rt flawlessly. All the new kernel options in 8.04 show this behavior in my laptop. Even the manufacturer bootup screen looks dimmed. The Fn keys work ok so I adjust the brightness every time I boot but it's really bugging me. :(
Bertilo (bertilow) wrote : | #58 |
I use Kubuntu 8.04 on a Lenovo 3000 C200 laptop. I did a fresh install of Hardy.
I get this dimming on every boot, at exactly the same point - somewhere around when the hardware drives are being loaded. When the desktop is fully loaded the brightness comes back automatically. But the login screen is quite dark.
The same thing happens at shutdown, and the reduced brightness then remains at the beginning of the next boot. I can however get the brightness up with the brightness keys, but only if I do it quickly at the very start. But the dimming then occurs again when the harware drivers are being loaded.
The brightness buttons on my laptop work at the start of the boot process, but then stop working as soon as the brightness drops. When the brightness automatically comes back (when the desktop is loaded), they start working again.
The same dimming also occurs every time I start VLC. It also happens when I switch off "Enable power saving" in KDE Control Center. (Reenebling the power saving however does not resurrect the brightness.)
I can always get the brightness back to normal if click on the Power Manager applet, and then change the brightness setting there. The brightness control there is set to maximum, although the actual brightness is very low. Changing the setting to something else (doesn't matter what) gets things back to normal (I usually take it down a notch, and then back up to maximum).
I can also - sometimes - get things back to normal if I touch anything in Monitor & Display -> Size, orientation & Positioning (in the Control Center), but that part of the Control Center behaves strangely and unpredictably.
Those solutions are of course just temporary. All I need to do to dim the screen, is to start VLC, or reboot.
Nothing like this happend in Gutsy, neither in Ubuntu nor in Kubuntu. I haven't seen it on any other version either. It started with one of the beta or RC versions of the Live CD, and it remains in the final release. It's very annoying.
ekso (ekso) wrote : | #59 |
I also confirm this bug on a HP Pavillion DV6705el with a NVidia GeForce 8400m over a clean install of Hardy 8.04 for i386.
The function keys for brightness do work, so it's just a bit bothersome to increase brightness every new boot.
encompass (encompass) wrote : | #60 |
Eks, do you know if the brightness changes while playing any videos
that you have? Does it go dim when you start mplayer, totem, vlc, or
others?
Bertilo (bertilow) wrote : | #61 |
In my case the brightness changes (dims) when I start a video in VLC, but not when I use any of the other video players that I have tested (Kaffeine e.g. works without any dimming).
It also changes (dims) when I start a virtual OS in VirtualBox. The dimming actually happens several times during the boot process of the virtual OS. I only notice that if I turn the brightness back up again immediately after each dimming. I need to use the Power Manager applet in Kubuntu to do that, since the ordinary brightness buttons stop working every time the screen dims. It would be nice to be able to do some other work while the virtual OS is booting (it does take a while), but the only thing I can do, is play whack-a-mole with the brightness bug.
Richard Green (rtg-aapsc) wrote : | #62 |
I'm happy to report that after upgrading my ubuntustudio install on an
emachines M6810 to hardy (amd64), I got a full-brilliance display on the
first boot!
maticmatija (maticmatija) wrote : | #63 |
Hi!
I have similar problems. I'm using Thinkpad r50e, ubuntu 8.04, fully updatet (kernel 2.6.24-17-generic). After kernel update I've rebooted four times: 3 times the brightnes was at top level, once it was lower. (with previous kernel it was lower all the time - I think).
In additon my screen dims when restarting X.
Matic
ekso (ekso) wrote : | #64 |
Encompass: No, it does not dims when I play videos with either Totem or VLC. It dims only during boot, AFTER grub, before the login screen. And on the login screen I cannot change brightness, only after an user have logged in.
Is there any way to have a "slow boot" so to debug WHERE it dims?
I've tried videotaping it, but it's hard to see when it starts to dim, which is not suddenly, it dims gradually, slowly. But it SEEMS to be when it loads:
[at 59.2684] NVRM: loading NVIDIA UNIX x86 Kernel Module 169.12 Thu Feb 14 17:53:07 PST 2008
Or it might be:
[at 59.3426] uvcvideo: Found UVC 1.00 device HP Webcam
[at 59.3461] usbcore: registered new interface driver uvcvideo
[at 59.3462] USB Video Class driver (v0.1.0)
These are the last "video related stuff" that seems to show up right before the dim starts.
BEFORE the NVidia Kernel Module there's:
[at 58.9249] nvidia: module license 'NVIDIA' taints kernel.
[at 59.2622] Linux video capture interface: v2.00
As you can see, it all happens in less than one second, without pausing the boot process is impossible to pin point the exact moment it starts dimming. But I don't know if it's possible to have a step-by-step boot process. It's not really annoying to me, adding the brightness applet to the panel helps to quickly change it, but if there's anyway I can help with this bug let me know.
ekso (ekso) wrote : | #65 |
encompass (encompass) wrote : | #66 |
One thing I noticed was that you could turn of the lcd and turn it
back on and it woudl jump to full brightness. Does anyone else have
this?
Pelle van der Scheer (pellesimon) wrote : | #67 |
I've got the same issue on a HP Pavilion dv6710ev
My brightness control is under /proc/acpi/
I can put the brightness to max using: sudo sh -c 'echo -n 95 > /proc/acpi/
(95 is the highest value available, use cat /proc/acpi/
As a workaround I put this line in /etc/rc.local before "exit 0" to get brightness maxed at every boot:
echo -n 95 > /proc/acpi/
maximilianhauser (maximilianhauser) wrote : | #68 |
I can confirm this bug, too. My hardware: HP Pavillion 9533eg with Hardy Heron. I found in the /boot/config-
encompass (encompass) wrote : | #69 |
I also noticed that if your screen turns off... for example when idle a very long time. Then the screen is dim when you come back. After pressing the button once to make the screen brighter... it goes to full brightness. Very interesting.
maticmatija (maticmatija) wrote : | #70 |
I'm updating my previous post.
With all updates (kernel 2.6.24-18-generic) I have even more problems. The screen brightness is set low in this situations:
- sometimes at boot of the computer
- sometimes at login screen
- sometimes after login
- sometimes (almost always) when I restart X
Matic
chourave (gaston72) wrote : | #71 |
I confirm this behaviour on my laptop Lenovo 3000 C200 model 8922AZG
I have just installed the 2.6.24-16-generic kernel on my Gutsy install.
With this new kernel my resume problem is fixed !!!! a real pleasure...
But the screen dims on every boot, and then, the brightness come back to 100% after opening the session.
(I have just tested the boot on AC)
Surprisingly, when I plug off the AC, the brightness doesn't respect the gnome setting. (something like 40% in place of 70%)
with previous releases : Feisty, Gutsy (kernel 2.6.22-14-generic) this doesn't happen.
chourave (gaston72) wrote : | #72 |
Some news :
blacklisting the video driver (echo blacklist video | sudo tee -a /etc/modprobe.
fixes the boot problem : the brightness of my LCD is maximal during the boot sequence.
But in fact it disable the brightness control : I can not control the brightness anymore in the gnome panel (no setting are available), and special key doesn't work anymore...
The problem seems to be in the kernel (2-6-24-16) for me, since it works with kernel 2-6-22-
Bertilo (bertilow) wrote : | #73 |
"echo blacklist video | sudo tee -a /etc/modprobe.
Johnny Jelinek IV (johnnyjiv) wrote : | #74 |
Wow, it's taken a little over 2 years to just propose a workable solution.
Very nice work chourave.
On Sun, Jun 8, 2008 at 4:29 AM, Bertilo <email address hidden> wrote:
> "echo blacklist video | sudo tee -a /etc/modprobe.
> too. The dimming is gone, but so is the functionality of my brightness
> controls. But I only ever used them to get the brightness up to max
> anyway, so I'm happy for now. Thank's a lot, chourave!
>
> --
> LCD Brightness on Laptop Always Set Very Low at Boot
> https:/
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
Miguel J (mjulier) wrote : | #75 |
I struggled with the same problem, before making my own workaround: screen would sometimes dim
- after install,
- at boot (but tends to improve with boot number: I even thought it was fixed, 1 month without trouble, and then back again),
- after using Windows Vista,
- when gdm starts,
- when VLC starts playing a video
- after running "xset dpms force off; sleep 1; xset dpms force on"
- after closing/opening lid (this is corrected is set "do nothing" on lid closing; it still switch off the screen though)
When logged in, I could correct the brightness using Fn-F5 (darker) or Fn-F6 (brighter), or 2 times Fn-F7 (LCD OFF/ON). When in GDM or in console mode, the only key that works is 2 times Fn-F7 (LCD OFF/ON).
I could find no real "good" solution, but I made a perfect (but ugly) workaround, which stills allows me to adjust the brightness, and even still adjusts the brightness on (dis)connecting the AC cord.
I found that the brightness value is stored in /sys/devices/
So my workaround is the following:
In /etc/rc.local, add this line before "exit 0":
/home/<
And in this file, copy this (adjust "FILE=" as necessary):
#!/bin/sh
FILE="/
PID=$$
COMMAND=`basename "$0"`
if ps -e | grep $COMMAND | grep -v $PID > /dev/null; then
echo "Program $COMMAND already running, not launching again"
else
while true; do
a=`cat "$FILE"`
echo "$a" > "$FILE"
sleep 1
done
fi
My information:
Linux 2.6.24-19-generic #1 SMP
Ubuntu 8.04 LTS
Laptop: ASUS M51L
Iceroyx (iceroyx) wrote : | #76 |
I also confirm this bug on my Acer Aspire 7720G with a NVidia GeForce 8400m over a clean install of Hardy 8.04 for i386.
Launchpad Janitor (janitor) wrote : This bug is now reported against the 'linux' package | #77 |
Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this linux-source-2.6.15 kernel bug to the new "linux" package. We appreciate your patience and understanding as we make this transition. Also, if you would be interested in testing the upcoming Intrepid Ibex 8.10 release, it is available at http://
uboltun (ekhaliul-gmail) wrote : | #78 |
I had a similar problem for my gateway MT6017. Every time I resume from suspend the screen is dimmed and I can not get it back up without reboot. When I changed "Auto Dim" in Bios to "Disable" the problem was fixed.
Leann Ogasawara (leannogasawara) wrote : | #79 |
The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:
1) If you are comfortable installing packages on your own, the linux-image-
--or--
2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://
Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.
Alberto (elba) wrote : | #80 |
I've found this page after some time I was fighting against this bug. Intrepid alpha5 should come in a few hours or perhaps minutes, but I describe my version of the bug in the meantime.
ASUS Z53H. Ubuntu Hardy 8.04. Kernel 2.6.24-21-generic -- to test the new Broadcom wireless drivers, but the bug was there before (2.6.24.19).
---The screen is dim on boot. I have to brighten it with Fn-F6. This function key is not active until the session begins. After typing username and password and waiting for Gnome to start, I can brighten the lcd with Fn key F6. I have to keep the key pressed for a while -- the slide has to climb all the way from minimum to maximum brightness (remember this). During the session, the screen gets dim on other occasions: when vlc reproduces a video (but not when it starts as a program, only after I select and file and vlc actually begins to reproduce it); when mplayer GUI _starts_ -- even before reproducing a video; when, after shifting to tty1 (CTRL-ALT-F1), I go back to Gnome (Alt-F7). In all these cases, I re-brighten the screen, but the brightness slide is already at its maximum -- this might have to do with the incongruence between actual and expected brightness. Thus, for _these_ kinds of dimming, pressing a fn-key once works, and I can also press Fn-F7 twice -- the screen is blanked and bright again; whereas, if I try Fn-F7 twice on boot, the screen blanks and turns _dim_ again. I don't know if this difference is meaningful.
Now, I report some weird behaviour of the bug and the testing I did, hoping that it may be useful for fixing the issue.
---I have GRUB and dual boot. (Must say I have booted WinXP only once during the last month -- fine.) On restart, after logging out of Ubuntu, also WinXP _starts_ with dim screen: I increase brightness, power off: when it restarts, it is bright from the beginning (tried only once). (It strikes me that it might be interesting to try not to brighten the screen while XP is on, power off, reboot and see if the screen is still dim even in XP. If you tell me to try this one, I'll do.) On the contrary, when I power off from Ubuntu, the screen is dim from the beginning: even GRUB has a dim display.
---The following may be interesting. I had to fix a cpu frequency scaling issue. Cpu freq scaling was not working, and I activated it by
$ modprobe acpi-cpufreq
I reconfigured the gnome applets and put a script in init.d to make the change permanent. I did update-rc.d etc. After that, all the dimming issue completely disappeared for a while. I mean: no trouble with VLC or mplayer, the boot was bright and so on. When the screen got dim because idle, touching the mouse set it back to bright -- for some ten days during which the pc was extensively used. Then, some days ago, the bug came back. I CANNOT exactly remember what I did, dammit. The session was suspended and resumed twice (I normally do not use suspend), some new software was installed, tried and uninstalled. When I realized the bug was back, I tried to remove my init.d file, to update-rc.d, to remove the module manually with modprobe, and then to reinstall it, but nothing worked. If this is really of some use to you, I can try to do e...
Alberto (elba) wrote : | #81 |
I've just tried chourave's fix. The only effect in my system is, I get stuck at minimum brightness... lol
Alberto (elba) wrote : | #82 |
AS far as I can see, the bug has been fixed in Intrepid alpha5 liveCD. The screen is still bright after CTRL-ALT-F1 ALT-F7. The brightness Fn-keys are also working. As soon as I can, I shall compile 2.6.27 within Hardy and report.
maticmatija (maticmatija) wrote : | #83 |
I've tested 8.10 alpha 5 live CD and the bug REMAINS. I've booted 3 times always with maximum brightness but after logging out the screen was darker. Also, when the monitor turns of after some idle time and you "wake" it, the brightness is lower.
I've noticed that in my 8.04, 2.6.24-19-generic (but not in 8.10 alpha 5 live CD) there is this line in dmesg output:
thinkpad_acpi: CMOS NVRAM (7) and EC (5) do not agree on display brightness level
Could this be of any help?
Alberto (elba) wrote : | #84 |
After reading maticmatija's message, I tested the Intrepid LiveCD again. I waited for the screen to blank and I touched the mouse: it came back to full brightness.
Is it possible that we have to do with a family of different, although possibly related, bugs? In my machine (ASUS Z53H) Hardy 8.04 seemed to switch off some hardware switch (a BIOS flag?). On turning on my pc after shutting down Hardy, the lcd was dim even when the splash ASUS screen popped up, that is, before the grub menu appeared. Conversely, if I reboot after shutting down Intrepid alpha5, the screen is bright since the beginning, and gets dim only at same time after grub. The simple conclusion is that, whatever Hardy does to _this_ machine, it does not evaporate at shutdown and is still there and _active_ when the pc is powered on, before the kernel is loaded and even before the operating system is chosen. But Intrepid seems to work.
Alberto (elba) wrote : | #85 |
Sorry, sloppy language. Edit: "if I reboot after shutting down Intrepid alpha5" should be "if I reboot Hardy 8.04 after shutting down Intrepid alpha5 LiveCD".
Alberto (elba) wrote : | #86 |
Compiled kernel 2.6.26 (2.6.26-4). The bug is still there (and behaves exactly the same).
I'll download and test 2.6.27 as soon as I can.
Alberto (elba) wrote : | #87 |
There is in fact a (little) difference. With 2.6.26 the screen is dim when I log in: but if I switch the lcd screen off and on by pressing twice the Fn-key F7, it immediately goes to full brightness and I need not increase brightness step by step, from minimum to full (as I had to do before). Moreover, on shutdown, the Ubuntu splash screen is displayed at high brightness. The pc screen is still bright when I power on (ASUS screen, grub, Ubuntu, all of these are at high brightness) -- and the system switches to dim just before the login screen appears.
((If I am feeding too much info (or maybe too irrelevant info) into this thread, please just tell me!))
Adriano Del Vigna (adriano-delvigna) wrote : | #88 |
Hi! I'm having similar anoying problem. Don't know if different enough to open a new ticket, but here it is.
When I switch on my laptop (a rebranded ECS laptop with Intel VGA) it's LCD brightness state change as:
1. Right after switching on: full bright (OK)
2. GRUB: full bright (OK)
3. Initng, but when the progress bar is waving from left to right and back: full bright (OK) -- I guess kernel does its initialization here
4. Initng, but when the progress bar resets and start growing as services are started: dims (NOT OK) -- I guess that some service, perhaps ACPI missconfiguration loading, dims the LCD
5. GDM: dimmed (NOT OK)
6. Desktop/GNOME Session: dimmed (NOT OK)
After log in I run a script (as root) with the following line to bring brightness back to a suitable state:
"echo 7 > /sys/class/
Although another way to get the same result would be:
"echo 100 > /proc/acpi/
These bring brightness back to normal. But, after running any SDL application, like 'dosbox', the LCD dims again, so I have to re-run the above commands. So, I ran some more tests, they are:
6.1. Desktop/GNOME Session, SDL 'dosbox': dims (NOT OK)
6.2. Desktop/GNOME Session, my own SDL application: dims (NOT OK)
Running the afore mentioned 'echoes' brings the brightness back to normal.
6.3. Desktop/GNOME Session, Screensaver: full bright (OK)
6.4. Desktop/GNOME Session, Suspend: full bright (OK)
6.5. Desktop/GNOME Session, Hibernate: full bright (OK)
Some more details about my system:
* Ubuntu Hardy 8.04
* PCI VGA Controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 03)
* Function keys for LCD brightness: they don't work, but I'm not concerned about them by now
* Kernel 2.6.24-19-generic
MY POINTS OF INVESTIGATION:
* Why LCD dims at boot, apparently at services loading time?
* Why the start of a SDL based application dims LCD?
* Screensaver, suspending and hibernating cause no problem
REMAINING TESTS:
* ACPI boot parameter "acpi_apic_
* ACPI boot parameter "acpi_osi=Linux" (as pointed in boot messages)
As soon as I learn on how to use them with GRUB+initng.
I'm attaching some logging files which may be helpful for debugging. Take some time looking at the 'ACPI Error' messages at 'dmesg.txt' and 'kern.log'.
Adriano Del Vigna (adriano-delvigna) wrote : | #89 |
Adriano Del Vigna (adriano-delvigna) wrote : | #90 |
Adriano Del Vigna (adriano-delvigna) wrote : | #91 |
Adriano Del Vigna (adriano-delvigna) wrote : | #92 |
Adriano Del Vigna (adriano-delvigna) wrote : | #93 |
Adriano Del Vigna (adriano-delvigna) wrote : | #94 |
Adriano Del Vigna (adriano-delvigna) wrote : | #95 |
About the remaining test, they gave no effect, not a change at all.
* ACPI boot parameter "acpi_apic_
* ACPI boot parameter "acpi_osi=Linux" (as pointed in boot messages)
I appended those parameters, each a time, at a /boot/grub/menu.lst special entry for ACPI tests (exactly the same as the latest kernel, but with the extra parameters).
By the way, while shuting down the laptop, the LCD dims too.
Adriano Del Vigna (adriano-delvigna) wrote : | #96 |
Additional comments:
- Another source of LCD dim: alternating between virtual terminals (Ctrl+Alt+F2; Alt+F3; Alt+F7...)
- Manual rebooting (typing 'sudo reboot', at a terminal) seems to not dim LCD
Ok, a few more tests as: https:/
** Methodology: Every parameter was tested after the kernel was booted with 'acpi=off', inclusive **
Results:
1. 'acpi=off': no LCD dim at boot (OK!!!) and function keys for brightness started to work for the first time ever!!
(*) Complain about 'pnpbios=off' necessary as a kernel paremeter;
2. 'acpi=ht': no LCD dim at boot (OK!!!) and function keys for brightness still working!!
(*) Complain about 'pnpbios=off' necessary as a kernel paremeter;
3. 'pci=noacpi': LCD dim back at initng time; function keys for brightness don't work anymore (NOT OK); LCD dim at shutdown time again;
4. 'acpi=noirq': LCD dim back at initng time; function keys for brightness don't work too (NOT OK); LCD dim at shutdown time again;
5. 'pnpacpi=off': LCD dim back at initng time; function keys for brightness don't work (NOT OK); LCD dim at shutdown time again;
(*) Complain about 'pnpbios=off' necessary as a kernel paremeter;
6. 'noapic': LCD dim back at initng time; function keys for brightness don't work (NOT OK); LCD dim at shutdown time again;
7. 'nolapic': boot hanged at 'Starting up ...\nLoading, please wait...'; initng waving the progress bar endlessly
Last comments:
- Font rendering at text virtual consoles degradated a little bit while changing ACPI parameters;
- Fan went to full speed without ACPI;
- System could not boot properly right after 'nolapic' test; hard reboot necessary to bring it back to work.
It seems that the problem lies within ACPI. I'll investigate more from there. More attachments below in the aim to help debugging, as indicated in the website above.
Adriano Del Vigna (adriano-delvigna) wrote : | #97 |
Adriano Del Vigna (adriano-delvigna) wrote : | #98 |
Alberto (elba) wrote : | #99 |
This is weird. I have a dual boot with Windows XP. I have not booted Win XP for almost one month. Today I used it, just to check compatibility between an Open Office file and MS Word. Power off, reboot to Ubuntu: the screen is bright since the beginning of the boot process (Asus splash, grub, Ubuntu splash, etc.). Shutdown and boot again: everything is still bright. I activate a virtual console and go back to gnome: bright screen. MPlayer: bright. This is very hard to understand. ("Yes! Bill Gates made the miracle!!!" -- gosh: could not be worse than that.) A new test: I run acpi_listen before loading mplayer and _no acpi codes_ are being sent any more when I run mplayer (when the screen went dim, acpi codes were sent every time mplayer started).
Windows has certainly not fixed a bug in the Linux kernel. If running mplayer resulted in some weird acpi codes being sent, and (2) these codes are not sent any more, and (3) the kernel is the same, the only thing I can think of is that some kind of bios flag has been switched on or off by WinXP. Some idiosyncratic feature of my laptop that is probably hidden to the Linux developers and probably open to Microsoft.
The conclusion I am inclined to draw is that it is high time for the Linux community to find effective ways for pressing on the manufacturers. Something like boycotting especially hostile manufacturers or explicitly and strongly recommending manufacturers that produce Linux drivers and Linux friendly machines.
Adriano Del Vigna (adriano-delvigna) wrote : | #100 |
Alberto,
I don't experience similar behaviour about alternating between Linux and Windows, Vista in my case.
I also ran acpi_listen before running SDL based dosbox and got not a single output from it. Weird at least.
cosphi (cosphi10) wrote : | #101 |
On my pc (asus f9 series) I fixed it just removing an option on the bios regarding display dimm when powered from battery. That's all.
cosphi (cosphi10) wrote : | #102 |
ubuntu 8.04
Bertilo (bertilow) wrote : | #103 |
I just tested Kubuntu 8.10 RC 1. The bug is still there. I didn't install. I just tested a live CD session.
Actually the bug is worse now: My brightness controls only manage to switch between "dark as hell" and "pretty dark" (back and forth). "Pretty dark" is much too dark to do any work.
Maybe "echo blacklist video | sudo tee -a /etc/modprobe.
Leann Ogasawara (leannogasawara) wrote : | #104 |
Keeping this open against the actively developed kernel bug against 2.6.15 this will be closed as it does not qualify for a Stable Release Update - https:/
Changed in linux-source-2.6.15: | |
status: | New → Won't Fix |
Bertilo (bertilow) wrote : | #105 |
Won't fix???? Why?
Johnny Jelinek IV (johnnyjiv) wrote : Re: [Bug 12637] Re: LCD Brightness on Laptop Always Set Very Low at Boot | #106 |
Well this one must be quite a bugger because it's taken this long to tackle.
On Thu, Oct 30, 2008 at 3:15 AM, Bertilo <email address hidden> wrote:
> Won't fix???? Why?
>
> --
> LCD Brightness on Laptop Always Set Very Low at Boot
> https:/
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
Grzegorz (grzegorzborkowski) wrote : | #107 |
Won't fix? You must be joking. Come on guys, nobody knows how to fix it for months/years, so you mean I should finally persuade myself that my screen is bright when it is dim?
maticmatija (maticmatija) wrote : | #108 |
does this have any relation with my dmesg's output:
"thinkpad_acpi: CMOS NVRAM (7) and EC (6) do not agree on display brightness level"
?
ekso (ekso) wrote : | #109 |
Upgraded to Intrepid Ibex, kernel 2.6.27-7. The bug is still there, dimming after boot. BUT, after login, it brightens again, it seems to be brightening to the same level that was left behind by the user.
If this is a kernel bug not solvable I think the Ubuntu team made a nice workaround. :)
Bertilo (bertilow) wrote : | #110 |
When I tested Intrepid Ibex, the bug was still there, and I still needed to put "blacklist video" in "/etc/modprobe.
The bug is clearly in the kernel. I've recently seen it (or some incarnation of it) in Mandrake 2009 and also in the Gparted live CD.
The bug should probably be reported to the Linux kernel developers, but I don't know how.
Bertilo (bertilow) wrote : | #111 |
I meant Mandriva Linux Free 2009 of course (not "Mandrake 2009"). Sorry...
Stéphane Démurget (stephane-demurget-free) wrote : | #112 |
- gnome-power-bugreport.sh Edit (2.4 KiB, text/plain)
Same issue on a Toshiba Portege M600 that has an intel video card (GMX 4600, but it does not seem to be the issue at all) on Intrepid with all updates as of today.
Here are the brightness files after a boot :
cat /proc/acpi/
<not supported>
<not supported>
<not supported>
levels: 100 42 0 14 28 42 56 70 84 100
current: 100
<not supported>
But the level should actually be 0 (display is dimmed). I also attach the gnome bug report file.
encompass (encompass) wrote : | #113 |
I believe progress has been made. I no longer have the issue on my Asus A7F anymore.
hunterthomson (darden-tyler) wrote : | #114 |
Hello, I posted before when Ubuntu switched to 8.04. The brightness was dim on boot/media player start/Game and not as bright. .I then switch to Archlinux but the problem cotinued but was not as bad, i.e. only dim once then not the next time you start vlc or game. Then came Ubuntu 8.10 and the problem became strange. Dim on boot and screen saver Only. And the brightness controls started going bright-> dim-> then bright again instead of dim->bright. I fooled around fixing the errors in the DSDT but could not fix the problem. This do to the lack of documentation on ACPI and AML. Then came chrismulderza on the ubuntuforums.org. He found out that the DSDT in the Lenovo Idea Pad Y510 was not giving the info to the kernel in the order it needed it and spesified in the ACPI standerds. In fact it was just spiting the info about the audio to the kernel and not ordering it at all. So, he fixed it and now the brightness is fixed.
http://
Just to make it clear.
This is all the deliberate act of Microsoft to make all computers only run on windows. They were taken to the supreme court of the United States of America and Found Guilty.
ACPI standers were made by a group of compays. Intel and Microsoft were among them. In the end intel made a compiler and Microsoft made one. Microsoft one is not standers compliant and Microsoft makes windows be able to run on messed up DSDT's and such that come out of there compiler. So, when computer manufacturers are writing the DSDT's and such they use the Micosoft compyler. Why maybe they are installing windows on most of the computers so they don't care. OR they just don't relies that the Microsoft complier sucks. At the end of the day windows only computers are pumped into the market.
Confirmed at Model Haier H60S
Linux ihw-laptop 2.6.27-9-generic #1 SMP Thu Nov 20 21:57:00 UTC 2008 i686 GNU/Linux
But
Fedora is OK for this issue.
Dim when boot. But it will be OK after X window startup (automatic).
gritty (kent-uoregon) wrote : | #116 |
This problem exists on a Lenovo x200 running Kubuntu 8.10.
$ uname -r
2.6.27.11-generic
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 8.10
Release: 8.10
Codename: intrepid
gritty (kent-uoregon) wrote : | #117 |
This is a follow up.
I installed "ubuntu-
I rebooted several times.
no problem
I then ran:
$ sudo apt-get update
$ sudo apt-get install linux-image-
I rebooted several times.
no problem
I then ran:
$ sudo apt-get install linux-image-
I rebooted and
the dimness appeared
I installed "ubuntu-
I rebooted several times and each time no problem.
Then I ran:
$ sudo apt-get install linux-image-
I rebooted and the dimness again appeared.
I the "ONLY" other thing I did was connect to the internet through my router.
So as far as I am concerned the problem is created with the "linux-
Karl Rixon (karl-rixon) wrote : | #118 |
echo blacklist video | sudo tee -a /etc/modprobe.
This above worked for me on an ASUS X71Q and Ubuntu Jaunty with 2.6.28-13-generic. After running the above and rebooting, then hitting F5 (brightness up) until it reached max, all of the problems went away. I can't use the gnome-panel brightness applet of course, but my Fn keys still work fine.
maticmatija (maticmatija) wrote : Re: [Bug 12637] Re: LCD Brightness on Laptop Always Set Very Low at Boot | #119 |
I've tested ubuntu 9.10 alpha 2 on my Thinkpad r50e and I couldn't reproduce
this bug. Can someone confirm this?
nexus (bugie) wrote : | #120 |
I had this problem on a Asus Z53Sseries notebook, too. Since a kernel update in ubuntu 8.10 this behaviour is gone. I currently use ubuntu 9.04 and everything is fine there.
encompass (encompass) wrote : | #121 |
I too no longer have this issue. It seems fixed for me. :)
Leann Ogasawara (leannogasawara) wrote : | #122 |
@reh4c, since you are the original bug reporter. Can you comment if this is resolved for you as well with the latest Jaunty 9.04 release? Please let us know your results. Thanks.
Changed in linux (Ubuntu): | |
status: | Confirmed → Incomplete |
Adriano Del Vigna (adriano-delvigna) wrote : | #123 |
Hey guys.
I'm not having this issue any more. Due to two main reasons. I switched to Fedora some time ago. To F10. And it did have the same issue in my laptop. In one of its kernel updates the issue was solved. Currently I'm running Fedora's kernel 2.6.27.
Probably this was an driver/ACPI update. The kernel solution was so good that even LCD dim when lauching SDL applications was solved. Now SDL applications don't dim LCD brightness anymore.
What I can do is, before upgrading to F11, give a try to newest Ubuntu release and post my findings here. I'll do that.
Cheers.
Leann Ogasawara (leannogasawara) wrote : | #124 |
I'm marking this Fix Release for now based on the multiple comments that this appears to be resolved. Thanks.
Changed in linux (Ubuntu): | |
status: | Incomplete → Fix Released |
Bertilo (bertilow) wrote : | #125 |
I just removed the "blacklist video" to check if the bug is still there. It is. There is absolutely no difference. The screen dims etc. (see my earlier comments). I use the latest Ubuntu 9.04. No fix in sight. Back to "blacklist video".
encompass (encompass) wrote : Jason Brower wants to stay in touch on LinkedIn | #126 |
LinkedIn
------------
Bug,
I'd like to add you to my professional network on LinkedIn.
- Jason Brower
Jason Brower
Developer at Xemec Oy
Finland
Confirm that you know Jason Brower
https:/
------
(c) 2010, LinkedIn Corporation
Is there a brightness control available in /proc/acpi/ video/* /*/brightness ?