Discovered LCD brightness related noise after 32days of use
I've had the cpu whine since day one but I just noticed that I have another noise related to the brightness but I can only hear it when the brightness is 13-16 bars and the higher the brightness the louder it gets. I never noticed it before since the only time I used full brightness was during movies when I put the sound up high so never got a chance to hear it. Also note that this isnt like the ones most people reported, because that one only occurs when brightness is less than full, and at full it does not occur. I was wondering if some others heard it and if someone actually got this fixed form Apple.
To hear this put ur brightness up 100% and close the screen/lid until its only open about an inch, then lift the back side of the MBP up and put your ears next to the air circulation holes that are behind the MBP and you should be able to hear it if you have this issue.. make sure its the holes on the right corner thats where its the loudest.
MacBook Pro 1.83Ghz/1Gb/80GB HD/128Mb X1600 Mac OS X (10.4.5)
I don't think the fact that it is a month old makes any difference. Apple is repairing inverter problems the last I heard. Call AppleCare and make sure you describe the problem as a problem with brightness so they don't just lump you in with the CPU noise and "it is normal."
Similar Messages
-
LCD brightness went down after the repair...
So I was having several issues with the LCD of my new Macbook pro (dead pixels, marks on the screen, uneven tones, backlighting issues, etc...), and Apple replaced the LCD screen for me. But now the brightness has gone down quite a bit. At least 2-3 notches down from the old screen. It is quite noticeable especially if I compare it with my friend's MacBook pro side by side. Maybe I thought Apple changed the manufacturer of LCD or something, but I've been told no by their tech support. Does anyone heard or experienced anything similar? Thanks...
Macbook Pro 1.83GHZ Mac OS X (10.4.5)egghead:
A little off the subject, but since you had the entire LCD replaced, I just had a quick questions, does your replaced LCD make any noise what so ever? Does it sound exactly the same from the highest all the way to off or is different hissing as you go lower. I would appreciate it if you could let me know. Much appreciated. Your situation ***** and I guess I shouldn't feel so bad about mine - I got my logic board replaced and I still have both whines. -
Laptop-mode-tools no longer adjusts LCD brightness
I just discovered that laptop-mode-tools no longer adjusts the brightness of the LCD when switched to battery. This is not a general issue. laptop-mode is active on battery (as well as being enabled via the systemd service), the computer knows it is on battery (checking with on_ac_power and reading from /sys/class/power_supply/*/* give the expected results) and other things are correctly adjusted e.g. bluetooth is blocked with rfkill. Moreover, as root I can adjust the brightness in the usual way by hand:
echo 10 >| /sys/class/backlight/acpi_video0/brightness
works just fine. The >| is needed because for interactive shell's, root's .bashrc sets noclobber. This obviously doesn't affect laptop-mode tools because it doesn't run an interactive shell. In contrast:
$ cat /etc/laptop-mode/conf.d/lcd-brightness.conf | grep -v "^#"
DEBUG=1
CONTROL_BRIGHTNESS=1
BATT_BRIGHTNESS_COMMAND="echo 7"
LM_AC_BRIGHTNESS_COMMAND="echo 10"
NOLM_AC_BRIGHTNESS_COMMAND="echo 12"
BRIGHTNESS_OUTPUT="/sys/class/backlight/acpi_video0/brightness"
DEBUG wasn't 1 when the problem started. I tried setting it to get more info but haven't found anything more in the journal/logs.
KDE is set to not touch the default brightness at all. All it does is (further) dim the display after so many minutes depending on the power supply and status.
This did work fine but I haven't been on battery for a while so I'm not sure when exactly it stopped working. My brightness is set by default to 12 on boot or wake from sleep which suggests laptop-mode tools does something or something else is now handling this which I'm not aware of. But the switch to battery does not trigger any alteration in the brightness and laptop-mode status does not even mention LCD brightness as one of the things laptop-mode tools controls.
Have I missed a change in how this is handled somewhere?I doubt this is related but it is currently my only lead so here goes. I set the LCD brightness control for debug so I've been trying to watch it. However, so far it is all smiles e.g. on boot it all works fine and says so.
However, I found I'm getting another error on boot which is
/usr/share/laptop-mode-tools/modules/pcie-aspm: line 10: write error: Operation not permitted
Note that I copied that by eye from VT1 so if a colon is out of place, that's why.
The contents of that file is:
#! /bin/sh
# Laptop mode tools module: PCIe Active State Power Management
if [ x$CONTROL_PCIE_ASPM = x1 ] || [ x$ENABLE_AUTO_MODULES = x1 -a x$CONTROL_PCIE_ASPM = xauto ]; then
if [ $ON_AC -eq 1 ]; then
log "VERBOSE" "On AC power: setting pcie_aspm to default"
if [ -f /sys/module/pcie_aspm/parameters/policy ]; then
echo default > /sys/module/pcie_aspm/parameters/policy
if [ $? -eq 0 ]; then
log "VERBOSE" "PCIe ASPM set to 'default'"
else
log "VERBOSE" "PCIe ASPM tweaking is prohibited by the kernel"
fi
else
log "VERBOSE" "PCIe ASPM is not available"
fi
else
log "VERBOSE" "On battery: setting pcie_aspm to powersave"
if [ -f /sys/module/pcie_aspm/parameters/policy ]; then
echo powersave > /sys/module/pcie_aspm/parameters/policy
if [ $? -eq 0 ]; then
log "VERBOSE" "PCIe ASPM set to 'powersave'"
else
log "VERBOSE" "PCIe ASPM tweaking is prohibited by the kernel"
fi
else
log "VERBOSE" "PCIe ASPM is not available"
fi
fi
else
log "VERBOSE" "PCIe ASPM power savings module is disabled"
fi
So I assume it is saying it cannot write to /sys/module/pcie_aspm/parameters/policy but the permissions etc. on that, at least, don't look strange:
l /sys/module/pcie_aspm/parameters/
total 0
drwxr-xr-x 2 root root 0 Gor 25 21:24 ./
drwxr-xr-x 3 root root 0 Gor 25 21:23 ../
-rw-r--r-- 1 root root 4.0K Gor 25 21:24 policy
Last edited by cfr (2013-07-25 20:47:13) -
I fixed the LCD Brightness in my Samsung NP300 Laptop
tl;dr: acpi_backlight=vendor to kernel at boot (add in grub configuration) + modprobe -r samsung_laptop && systemctl restart gdm. (i discovered it with pf-kernel, need to try in stock kernel)
Well, i don't know if this is known, but i could not find it.
Maybe its a bug to be fixed that im not aware of.
Well, i had the common problem with the LCD brightness not responding. It used to decrease, but not increase. All of this running Gnome 3.
After days of fight what i did was download pf-kernel and configure it. I selected the "samsung_laptop" module as my common sense told me, and in case it was needed the Q10 Samsung or something like that module too.
I rebooted into the pf-kernel, with no luck, the same problem was still happening.
I decided to stop gdm and use startx to try some things.
First i modprobed the samsung_laptop module just in case, started X again, and it was the same.
And then i did modprobe -r samsung_laptop, restarted X... AND IT WORKS.
NOTE: The acpi_backlight=vendor is needed in the grub configuration to this to work.
Oddly, without the samsung_laptop module.
So i rebooted to try this again. Unloaded the module, did systemctl restart gdm, aand there it was working again.
So, it may be a problem with that module, or maybe its not needed after all, im not sure.
I'm kind of newbie in all of this, so if this is dumb or something im sorry but i think it may be helpful for somebody else in my situation.
By googling i only found scripts to make this work that i did not like.
Is neccesary that i place a bug report? Im not sure if that kernel module is made to fix this or if its for something else, so i dont know if the bug report makes sense.
Last edited by nlabrad (2012-12-27 18:07:52)More history on what does what.
At first, i could only decrease the brightness 1 step, from the max to one below.
Then i put acpi_backlight=vendor in grub, and i could decrease the brightness to some value (which is not the real minimum), but could not increase it more than 2 steps over that minimum once decreased (like locked in the 2 lower values).
To manually change the brightness i echoed values to /sys/class/backlight/intel_backlight/brightness. The other one did not work (samsung...), but it wasn't what i wanted.
After changing kernel, unloading the kernel module samsung_laptop and restarting x it works.
Not sure if the kernel has something to do. -
LCD Brightness is lowered when touching mouse or keyboard
Hi Guys,
hopefully, the newbie corner is the right place to post this, at least I am one, just switching from ubuntu to arch.
Essentially I have the problem marked as solved here: https://bbs.archlinux.org/viewtopic.php?id=127818
For me, however, it is not solved. I don't think it is related to laptop-mode, but I don't know. I am using my laptop on AC only. If I leave the laptop unattended for a while and then move the mouse or touch any button it lowers LCD brightness. The laptop buttons for brightness do work. I really don't know which program is doing this and neither why.
Since the system is pretty much unusable in this state, I did a workaround by taking away file privileges (chmod 444 /sys/class/backlight/nv_backlight/brightness).this has been overridden by the system after reboot, too.
I am using a fresh install with gnome.
Thank you very much in advance for any clues how to solve this.
Karsten
Last edited by karsten_m (2011-10-19 21:06:01)Ok, the / of all the strange behaviour was gnome-power-manager.
Unfortunately I wasn't able to get to core of why it dims the screen, but the workaround is this: define the dimmed brightness as 100..
You can do this by running
dconf write /org/gnome/settings-daemon/plugins/power/idle-brightness 100
It does the trick.
If anyone's got a better idea - let it out... -
Sony Vaio FZ Series - LCD brightness
Hi All,
I have recently bought a Sony VAIO FZ11S and I've successfully installed Archlinux:
Fully working:
- CPU Scaling (using cpudyn)
- Multimedia keys (mute, volume up/down, play/stop, etc. using Xmodmap)
- Wireless (using iwl3945. Can't connect with AP with hidden SSID)
- Nvidia GeForce 8400M (using latest nvidia drivers with stock arch kernel 2.6.23)
- Audio (after adding 'options snd-hda-intel model=vaio' to /etc/modprobe.conf. MIC not tested yet)
Untested:
- bluetooth
- SD/MS card reader
- Video camera
NOT WORKING:
- LCD brightness adjustment: FN+F5/F6 are detected correctly by acpid but nothing happens. I'm using the module sony-laptop included with kernel 2.6. Folder /sys/class/backlight is empty. I can use nvidia-settings to change COLOR BRIGHTNESS but this is NOT a good solution IMHO. I'd like to get the same capabilities I get running Windows Vista. (change LCD backlight).
I've read somewhere it is a problem common to all laptop with the same NVIDIA videocard. Does anyone know a fix for this? I've also tried with latest nvidia beta drivers with no success.
- Hibernate/suspend. I tried with pm-tools to suspend/hibernate laptop but nothing is working correctly. I didn't investigate further. Has anyone got a quick solution for this?
lspci output:
00:00.0 Host bridge: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub (rev 0c)
00:01.0 PCI bridge: Intel Corporation Mobile PM965/GM965/GL960 PCI Express Root Port (rev 0c)
00:1a.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Contoller #4 (rev 03)
00:1a.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 (rev 03)
00:1a.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 (rev 03)
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 (rev 03)
00:1c.1 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 2 (rev 03)
00:1c.2 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 3 (rev 03)
00:1c.4 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 5 (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #3 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev f3)
00:1f.0 ISA bridge: Intel Corporation 82801HEM (ICH8M) LPC Interface Controller (rev 03)
00:1f.1 IDE interface: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) IDE Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) SATA AHCI Controller (rev 03)
00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus Controller (rev 03)
01:00.0 VGA compatible controller: nVidia Corporation GeForce 8400M GT (rev a1)
06:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02)
08:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8036 PCI-E Fast Ethernet Controller (rev 16)
09:03.0 CardBus bridge: Texas Instruments PCIxx12 Cardbus Controller
09:03.1 FireWire (IEEE 1394): Texas Instruments PCIxx12 OHCI Compliant IEEE 1394 Host Controller
09:03.2 Mass storage controller: Texas Instruments 5-in-1 Multimedia Card Reader (SD/MMC/MS/MS PRO/xD)
Please help
V.
Last edited by Vins (2007-12-09 11:37:08)I recently bought a Sony FZ180, almost identical stats and hardware.
I tried all the same suggestions, which worked fine on my old laptop, but will not for this one. If anyone can think of another method to control the backlight I would be grateful.
Also, I tested the SD slot, the TI driver recognizes when a card is inserted, but no devices or mount-points are created.
tifm_core: MMC/SD card detected in socket 0:1
tifm0 : demand removing card from socket 0:1
(The second line is from me removing the card, not a defective slot.)
Everything else works great, though. Arch boots to a full KDE desktop much, much faster than my cleaned-up vista partition. I'm really happy overall. -
Bug or Feature, gnome increases lcd brightness on laptop random?
When on battery, I dim the light on the lcd using the fn-f5 and fn-f6 button. This is all good. To save battery right. Sometimes, completely randomly it seems the brightness is turned to 100%. I used dbus-listen to snatch this up:
signal sender=:1.18 -> dest=(null destination) serial=40 path=/org/gnome/PowerManager/Backlight; interface=org.gnome.PowerManager.Backlight; member=BrightnessChanged
uint32 100
So I know that it is indeed gnome power manager that causes this to happen. Note that I have deactivated any control of the lcd while on battery. Such as dim light when idle, and reduce light when on battery. It is random, because I can't force it to happen again myself.
Note: Just now when I had the display turned down, and took a pause from typing this post the brightness increased by itself to 100% without me even touching the keyboard.
The following was printed to dbus-listen:
signal sender=:1.18 -> dest=(null destination) serial=41 path=/org/gnome/PowerManager/Backlight; interface=org.gnome.PowerManager.Backlight; member=BrightnessChanged
uint32 100
signal sender=:1.18 -> dest=(null destination) serial=42 path=/org/gnome/PowerManager/Backlight; interface=org.gnome.PowerManager.Backlight; member=BrightnessChanged
uint32 100
It would be nice to fix this, it is slightly annoying.
Update: I ran gnome-power-manager in verbose if that provides more useful info:
TI:13:55:58 TH:0x10f6090 FI:egg-debug.c FN:egg_debug_init,306
- Verbose debugging 1 (on console 0)GPM_VERBOSE
TI:13:55:58 TH:0x10f6090 FI:gpm-main.c FN:main,210
- GNOME Power Manager 2.30.1
TI:13:55:58 TH:0x10f6090 FI:gpm-session.c FN:gpm_session_init,511
- idle: 0, idle_inhibited: 0, suspend_inhibited: 0
TI:13:55:58 TH:0x10f6090 FI:gpm-session.c FN:gpm_session_register_client,367
- registered startup '(null)' to client id '/org/gnome/SessionManager/Client12'
TI:13:55:58 TH:0x10f6090 FI:egg-console-kit.c FN:egg_console_kit_init,305
- ConsoleKit session ID: /org/freedesktop/ConsoleKit/Session4
TI:13:55:58 TH:0x10f6090 FI:gpm-button.c FN:gpm_button_grab_keystring,176
- Grabbed modmask=8000, keycode=124
TI:13:55:58 TH:0x10f6090 FI:gpm-button.c FN:gpm_button_grab_keystring,176
- Grabbed modmask=8000, keycode=213
TI:13:55:58 TH:0x10f6090 FI:gpm-button.c FN:gpm_button_grab_keystring,176
- Grabbed modmask=8000, keycode=150
*** WARNING ***
TI:13:55:58 TH:0x10f6090 FI:gpm-button.c FN:gpm_button_xevent_key,203
- could not map keysym 1008ffa8 to keycode
TI:13:55:58 TH:0x10f6090 FI:gpm-button.c FN:gpm_button_grab_keystring,176
- Grabbed modmask=8000, keycode=233
TI:13:55:58 TH:0x10f6090 FI:gpm-button.c FN:gpm_button_grab_keystring,176
- Grabbed modmask=8000, keycode=232
TI:13:55:58 TH:0x10f6090 FI:gpm-button.c FN:gpm_button_grab_keystring,176
- Grabbed modmask=8000, keycode=160
TI:13:55:58 TH:0x10f6090 FI:gpm-button.c FN:gpm_button_grab_keystring,176
- Grabbed modmask=8000, keycode=244
TI:13:55:58 TH:0x10f6090 FI:gpm-button.c FN:gpm_button_grab_keystring,176
- Grabbed modmask=8000, keycode=238
TI:13:55:58 TH:0x10f6090 FI:gpm-button.c FN:gpm_button_grab_keystring,176
- Grabbed modmask=8000, keycode=237
TI:13:55:58 TH:0x10f6090 FI:gpm-button.c FN:gpm_button_grab_keystring,176
- Grabbed modmask=8000, keycode=236
TI:13:55:58 TH:0x10f6090 FI:gpm-brightness-xrandr.c FN:gpm_brightness_xrandr_update_cache,628
- screen 1 of 1
TI:13:55:58 TH:0x10f6090 FI:gpm-brightness-xrandr.c FN:gpm_brightness_xrandr_update_cache,633
- watching ::monitors_changed on 0x10fd210
TI:13:55:58 TH:0x10f6090 FI:gpm-brightness-xrandr.c FN:gpm_brightness_xrandr_update_cache,653
- adding resource 0x1197210
TI:13:55:58 TH:0x10f6090 FI:gpm-brightness.c FN:gpm_brightness_init,436
- detected XRANDR hardware
TI:13:55:58 TH:0x10f6090 FI:gpm-prefs-server.c FN:gpm_prefs_server_set_capability,84
- capability now 4
TI:13:55:58 TH:0x10f6090 FI:gpm-prefs-server.c FN:gpm_prefs_server_set_capability,84
- capability now 5
TI:13:55:58 TH:0x10f6090 FI:gpm-idle.c FN:gpm_idle_evaluate,187
- session_idle=0, idle_inhibited=0, suspend_inhibited=0, x_idle=0
TI:13:55:58 TH:0x10f6090 FI:gpm-idle.c FN:gpm_idle_evaluate,192
- X not idle
TI:13:55:58 TH:0x10f6090 FI:gpm-idle.c FN:gpm_idle_set_timeout_dim,261
- Setting dim idle timeout: 10s
TI:13:55:58 TH:0x10f6090 FI:gpm-dpms.c FN:gpm_dpms_clear_timeouts,311
- set timeouts to zero
TI:13:55:58 TH:0x10f6090 FI:gpm-backlight.c FN:gpm_backlight_brightness_evaluate_and_set,300
- 1. main brightness 1.000000
TI:13:55:58 TH:0x10f6090 FI:gpm-backlight.c FN:gpm_backlight_brightness_evaluate_and_set,320
- 2. battery scale 1.000000, brightness 1.000000
TI:13:55:58 TH:0x10f6090 FI:gpm-backlight.c FN:gpm_backlight_brightness_evaluate_and_set,338
- 3. idle scale 1.000000, brightness 1.000000
TI:13:55:58 TH:0x10f6090 FI:gpm-brightness-xrandr.c FN:gpm_brightness_xrandr_foreach_screen,448
- using resource 0x1197210
TI:13:55:58 TH:0x10f6090 FI:gpm-brightness-xrandr.c FN:gpm_brightness_xrandr_foreach_resource,410
- resource 1 of 5
TI:13:55:58 TH:0x10f6090 FI:gpm-brightness-xrandr.c FN:gpm_brightness_xrandr_foreach_resource,410
- resource 2 of 5
TI:13:55:58 TH:0x10f6090 FI:gpm-brightness-xrandr.c FN:gpm_brightness_xrandr_output_get_percentage,252
- hard value=7, min=0, max=15
TI:13:55:58 TH:0x10f6090 FI:gpm-brightness-xrandr.c FN:gpm_brightness_xrandr_output_get_percentage,254
- percentage 46
TI:13:55:58 TH:0x10f6090 FI:gpm-brightness-xrandr.c FN:gpm_brightness_xrandr_foreach_resource,410
- resource 3 of 5
TI:13:55:58 TH:0x10f6090 FI:gpm-brightness-xrandr.c FN:gpm_brightness_xrandr_foreach_resource,410
- resource 4 of 5
TI:13:55:58 TH:0x10f6090 FI:gpm-brightness-xrandr.c FN:gpm_brightness_xrandr_foreach_resource,410
- resource 5 of 5
*** WARNING ***
TI:13:55:58 TH:0x10f6090 FI:gpm-brightness.c FN:gpm_brightness_trust_cache,107
- using cache for value 46 (probably okay)
TI:13:55:58 TH:0x10f6090 FI:gpm-brightness-xrandr.c FN:gpm_brightness_xrandr_foreach_screen,448
- using resource 0x1197210
TI:13:55:58 TH:0x10f6090 FI:gpm-brightness-xrandr.c FN:gpm_brightness_xrandr_foreach_resource,410
- resource 1 of 5
TI:13:55:58 TH:0x10f6090 FI:gpm-brightness-xrandr.c FN:gpm_brightness_xrandr_foreach_resource,410
- resource 2 of 5
TI:13:55:58 TH:0x10f6090 FI:gpm-brightness-xrandr.c FN:gpm_brightness_xrandr_output_set,349
- percent=100, absolute=15
TI:13:55:58 TH:0x10f6090 FI:gpm-brightness-xrandr.c FN:gpm_brightness_xrandr_output_set,351
- hard value=7, min=0, max=15
TI:13:55:58 TH:0x10f6090 FI:gpm-brightness-xrandr.c FN:gpm_brightness_xrandr_output_set,366
- using step of 1
TI:13:55:58 TH:0x10f6090 FI:gpm-brightness-xrandr.c FN:gpm_brightness_xrandr_foreach_resource,410
- resource 3 of 5
TI:13:55:58 TH:0x10f6090 FI:gpm-brightness-xrandr.c FN:gpm_brightness_xrandr_foreach_resource,410
- resource 4 of 5
TI:13:55:58 TH:0x10f6090 FI:gpm-brightness-xrandr.c FN:gpm_brightness_xrandr_foreach_resource,410
- resource 5 of 5
TI:13:55:58 TH:0x10f6090 FI:gpm-backlight.c FN:gpm_backlight_brightness_evaluate_and_set,361
- emitting brightness-changed : 100
TI:13:55:58 TH:0x10f6090 FI:gpm-idle.c FN:gpm_idle_set_check_cpu,122
- Setting the CPU load check to 0
TI:13:55:58 TH:0x10f6090 FI:gpm-manager.c FN:gpm_manager_init,1950
- creating new control instance
TI:13:55:58 TH:0x10f6090 FI:gpm-manager.c FN:gpm_manager_init,1955
- creating new tray icon
TI:13:55:58 TH:0x10f6090 FI:gpm-phone.c FN:gpm_phone_dbus_connect,242
- get connection
TI:13:55:58 TH:0x10f6090 FI:gpm-phone.c FN:gpm_phone_dbus_connect,253
- get proxy
*** WARNING ***
TI:13:55:58 TH:0x10f6090 FI:gpm-phone.c FN:gpm_phone_dbus_connect,261
- Cannot connect, maybe the daemon is not running: Could not get owner of name 'org.gnome.phone': no such name
TI:13:55:58 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_init,1120
- Using per-time notification policy
TI:13:55:58 TH:0x10f6090 FI:gpm-idle.c FN:gpm_idle_set_timeout_blank,282
- Setting blank idle timeout: 600s
TI:13:55:58 TH:0x10f6090 FI:gpm-idle.c FN:gpm_idle_evaluate,187
- session_idle=0, idle_inhibited=0, suspend_inhibited=0, x_idle=0
TI:13:55:58 TH:0x10f6090 FI:gpm-idle.c FN:gpm_idle_evaluate,192
- X not idle
TI:13:55:58 TH:0x10f6090 FI:gpm-idle.c FN:gpm_idle_set_timeout_sleep,299
- Setting sleep idle timeout: 0s
TI:13:55:58 TH:0x10f6090 FI:gpm-idle.c FN:gpm_idle_evaluate,187
- session_idle=0, idle_inhibited=0, suspend_inhibited=0, x_idle=0
TI:13:55:58 TH:0x10f6090 FI:gpm-idle.c FN:gpm_idle_evaluate,192
- X not idle
TI:13:55:58 TH:0x10f6090 FI:gpm-disks.c FN:gpm_disks_set_spindown_timeout,132
- registered udisks_inhibitor_13 (60)
TI:13:55:58 TH:0x10f6090 FI:gpm-screensaver.c FN:gpm_screensaver_add_throttle,224
- adding throttle reason: 'On battery power': id 36075059
TI:13:55:58 TH:0x10f6090 FI:gpm-prefs-server.c FN:gpm_prefs_server_set_capability,84
- capability now 13
*** WARNING ***
TI:13:55:58 TH:0x10f6090 FI:gpm-phone.c FN:gpm_phone_coldplug,76
- not connected
TI:13:55:58 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_get_composite_device,595
- using original device as only one primary battery
TI:13:55:58 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_get_composite_device,595
- using original device as only one primary battery
TI:13:55:58 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_get_composite_device,595
- using original device as only one primary battery
TI:13:55:58 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_get_composite_device,595
- using original device as only one primary battery
TI:13:55:58 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_get_composite_device,595
- using original device as only one primary battery
TI:13:55:58 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_get_composite_device,595
- using original device as only one primary battery
TI:13:55:58 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_get_composite_device,595
- using original device as only one primary battery
TI:13:55:58 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_get_composite_device,595
- using original device as only one primary battery
TI:13:55:58 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_get_composite_device,595
- using original device as only one primary battery
TI:13:55:58 TH:0x10f6090 FI:gpm-upower.c FN:gpm_upower_get_device_icon,203
- got filename: gpm-battery-080
TI:13:55:58 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_recalculate_state_icon,438
- ** EMIT: icon-changed: gpm-battery-080
TI:13:55:58 TH:0x10f6090 FI:gpm-tray-icon.c FN:gpm_tray_icon_set_icon,129
- Setting icon to gpm-battery-080
TI:13:55:58 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_get_summary,264
- tooltip: Laptop battery 7 hours 40 minutes remaining (81.4%)
TI:13:55:58 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_recalculate_state_summary,470
- ** EMIT: summary-changed(1): Laptop battery 7 hours 40 minutes remaining (81.4%)
TI:13:55:58 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_device_add,746
- adding /org/freedesktop/UPower/devices/battery_BAT0 with state discharging
TI:13:55:58 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_device_add,750
- updating because we added a device
TI:13:55:58 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_update_composite_device,651
- printing device 0
native-path: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/PNP0C0A:00/power_supply/BAT0
vendor: ASUSTEK
model: UL50-56
power supply: yes
updated: Wed 16 Jun 2010 01:55:45 PM CEST (13 seconds ago)
has history: yes
has statistics: yes
battery
present: yes
rechargeable: yes
state: discharging
energy: 65.985 Wh
energy-empty: 0 Wh
energy-full: 81.06 Wh
energy-full-design: 84 Wh
energy-rate: 8.58 W
voltage: 16.086 V
time to empty: 7.7 hours
percentage: 81.4027%
capacity: 95.6964%
technology: lithium-ion
History (charge):
1276689345 81.403 discharging
1276689315 81.495 discharging
1276689285 81.588 discharging
1276689255 81.680 discharging
History (rate):
1276689345 8.580 discharging
1276689315 8.790 discharging
1276689285 8.775 discharging
1276689255 9.480 discharging
TI:13:55:58 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_update_composite_device,672
- using original device as only one primary battery
TI:13:55:58 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_device_add,746
- adding /org/freedesktop/UPower/devices/line_power_AC0 with state unknown
TI:13:56:15 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_device_changed_cb,905
- updating because /org/freedesktop/UPower/devices/battery_BAT0 changed
TI:13:56:15 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_update_composite_device,651
- printing device 0
native-path: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/PNP0C0A:00/power_supply/BAT0
vendor: ASUSTEK
model: UL50-56
power supply: yes
updated: Wed 16 Jun 2010 01:56:15 PM CEST (0 seconds ago)
has history: yes
has statistics: yes
battery
present: yes
rechargeable: yes
state: discharging
energy: 65.895 Wh
energy-empty: 0 Wh
energy-full: 81.06 Wh
energy-full-design: 84 Wh
energy-rate: 9.045 W
voltage: 16.077 V
time to empty: 7.3 hours
percentage: 81.2916%
capacity: 95.6964%
technology: lithium-ion
History (charge):
1276689375 81.292 discharging
1276689345 81.403 discharging
1276689315 81.495 discharging
1276689285 81.588 discharging
History (rate):
1276689375 9.045 discharging
1276689345 8.580 discharging
1276689315 8.790 discharging
1276689285 8.775 discharging
TI:13:56:15 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_update_composite_device,672
- using original device as only one primary battery
TI:13:56:15 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_device_changed_cb,914
- /org/freedesktop/UPower/devices/battery_BAT0 state is now discharging
TI:13:56:15 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_get_composite_device,595
- using original device as only one primary battery
TI:13:56:15 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_get_composite_device,595
- using original device as only one primary battery
TI:13:56:15 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_get_composite_device,595
- using original device as only one primary battery
TI:13:56:15 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_get_composite_device,595
- using original device as only one primary battery
TI:13:56:15 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_get_composite_device,595
- using original device as only one primary battery
TI:13:56:15 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_get_composite_device,595
- using original device as only one primary battery
TI:13:56:15 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_get_composite_device,595
- using original device as only one primary battery
TI:13:56:15 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_get_composite_device,595
- using original device as only one primary battery
TI:13:56:15 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_get_composite_device,595
- using original device as only one primary battery
TI:13:56:15 TH:0x10f6090 FI:gpm-upower.c FN:gpm_upower_get_device_icon,203
- got filename: gpm-battery-080
TI:13:56:15 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_recalculate_state_icon,453
- no change
TI:13:56:15 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_get_summary,264
- tooltip: Laptop battery 7 hours 15 minutes remaining (81.3%)
TI:13:56:15 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_recalculate_state_summary,478
- ** EMIT: summary-changed(2): Laptop battery 7 hours 15 minutes remaining (81.3%)
TI:13:56:45 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_device_changed_cb,905
- updating because /org/freedesktop/UPower/devices/battery_BAT0 changed
TI:13:56:45 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_update_composite_device,651
- printing device 0
native-path: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/PNP0C0A:00/power_supply/BAT0
vendor: ASUSTEK
model: UL50-56
power supply: yes
updated: Wed 16 Jun 2010 01:56:45 PM CEST (0 seconds ago)
has history: yes
has statistics: yes
battery
present: yes
rechargeable: yes
state: discharging
energy: 65.82 Wh
energy-empty: 0 Wh
energy-full: 81.06 Wh
energy-full-design: 84 Wh
energy-rate: 8.505 W
voltage: 16.082 V
time to empty: 7.7 hours
percentage: 81.1991%
capacity: 95.6964%
technology: lithium-ion
History (charge):
1276689405 81.199 discharging
1276689375 81.292 discharging
1276689345 81.403 discharging
1276689315 81.495 discharging
History (rate):
1276689405 8.505 discharging
1276689375 9.045 discharging
1276689345 8.580 discharging
1276689315 8.790 discharging
TI:13:56:45 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_update_composite_device,672
- using original device as only one primary battery
TI:13:56:45 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_device_changed_cb,914
- /org/freedesktop/UPower/devices/battery_BAT0 state is now discharging
TI:13:56:45 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_get_composite_device,595
- using original device as only one primary battery
TI:13:56:45 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_get_composite_device,595
- using original device as only one primary battery
TI:13:56:45 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_get_composite_device,595
- using original device as only one primary battery
TI:13:56:45 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_get_composite_device,595
- using original device as only one primary battery
TI:13:56:45 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_get_composite_device,595
- using original device as only one primary battery
TI:13:56:45 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_get_composite_device,595
- using original device as only one primary battery
TI:13:56:45 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_get_composite_device,595
- using original device as only one primary battery
TI:13:56:45 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_get_composite_device,595
- using original device as only one primary battery
TI:13:56:45 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_get_composite_device,595
- using original device as only one primary battery
TI:13:56:45 TH:0x10f6090 FI:gpm-upower.c FN:gpm_upower_get_device_icon,203
- got filename: gpm-battery-080
TI:13:56:45 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_recalculate_state_icon,453
- no change
TI:13:56:45 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_get_summary,264
- tooltip: Laptop battery 7 hours 40 minutes remaining (81.2%)
TI:13:56:45 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_recalculate_state_summary,478
- ** EMIT: summary-changed(2): Laptop battery 7 hours 40 minutes remaining (81.2%)
TI:13:57:15 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_device_changed_cb,905
- updating because /org/freedesktop/UPower/devices/battery_BAT0 changed
TI:13:57:15 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_update_composite_device,651
- printing device 0
native-path: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/PNP0C0A:00/power_supply/BAT0
vendor: ASUSTEK
model: UL50-56
power supply: yes
updated: Wed 16 Jun 2010 01:57:15 PM CEST (0 seconds ago)
has history: yes
has statistics: yes
battery
present: yes
rechargeable: yes
state: discharging
energy: 65.745 Wh
energy-empty: 0 Wh
energy-full: 81.06 Wh
energy-full-design: 84 Wh
energy-rate: 9.345 W
voltage: 16.054 V
time to empty: 7.0 hours
percentage: 81.1066%
capacity: 95.6964%
technology: lithium-ion
History (charge):
1276689435 81.107 discharging
1276689405 81.199 discharging
1276689375 81.292 discharging
1276689345 81.403 discharging
History (rate):
1276689435 9.345 discharging
1276689405 8.505 discharging
1276689375 9.045 discharging
1276689345 8.580 discharging
TI:13:57:15 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_update_composite_device,672
- using original device as only one primary battery
TI:13:57:15 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_device_changed_cb,914
- /org/freedesktop/UPower/devices/battery_BAT0 state is now discharging
TI:13:57:15 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_get_composite_device,595
- using original device as only one primary battery
TI:13:57:15 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_get_composite_device,595
- using original device as only one primary battery
TI:13:57:15 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_get_composite_device,595
- using original device as only one primary battery
TI:13:57:15 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_get_composite_device,595
- using original device as only one primary battery
TI:13:57:15 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_get_composite_device,595
- using original device as only one primary battery
TI:13:57:15 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_get_composite_device,595
- using original device as only one primary battery
TI:13:57:15 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_get_composite_device,595
- using original device as only one primary battery
TI:13:57:15 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_get_composite_device,595
- using original device as only one primary battery
TI:13:57:15 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_get_composite_device,595
- using original device as only one primary battery
TI:13:57:15 TH:0x10f6090 FI:gpm-upower.c FN:gpm_upower_get_device_icon,203
- got filename: gpm-battery-080
TI:13:57:15 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_recalculate_state_icon,453
- no change
TI:13:57:15 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_get_summary,264
- tooltip: Laptop battery 7 hours remaining (81.1%)
TI:13:57:15 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_recalculate_state_summary,478
- ** EMIT: summary-changed(2): Laptop battery 7 hours remaining (81.1%)
TI:13:57:24 TH:0x10f6090 FI:gpm-idle.c FN:gpm_idle_idletime_alarm_expired_cb,338
- idletime alarm: 1
TI:13:57:24 TH:0x10f6090 FI:gpm-idle.c FN:gpm_idle_evaluate,187
- session_idle=0, idle_inhibited=0, suspend_inhibited=0, x_idle=1
TI:13:57:24 TH:0x10f6090 FI:gpm-idle.c FN:gpm_idle_evaluate,221
- normal to dim
TI:13:57:24 TH:0x10f6090 FI:gpm-idle.c FN:gpm_idle_set_mode,108
- Doing a state transition: dim
TI:13:57:24 TH:0x10f6090 FI:gpm-backlight.c FN:gpm_backlight_notify_system_idle_changed,530
- we were active for 85.418504s
TI:13:57:24 TH:0x10f6090 FI:gpm-backlight.c FN:gpm_backlight_notify_system_idle_changed,533
- changing powersave idle status to 1
TI:13:57:24 TH:0x10f6090 FI:gpm-backlight.c FN:gpm_backlight_brightness_evaluate_and_set,300
- 1. main brightness 1.000000
TI:13:57:24 TH:0x10f6090 FI:gpm-backlight.c FN:gpm_backlight_brightness_evaluate_and_set,320
- 2. battery scale 1.000000, brightness 1.000000
TI:13:57:24 TH:0x10f6090 FI:gpm-backlight.c FN:gpm_backlight_brightness_evaluate_and_set,338
- 3. idle scale 1.000000, brightness 1.000000
TI:13:57:24 TH:0x10f6090 FI:gpm-brightness-xrandr.c FN:gpm_brightness_xrandr_foreach_screen,448
- using resource 0x1197210
TI:13:57:24 TH:0x10f6090 FI:gpm-brightness-xrandr.c FN:gpm_brightness_xrandr_foreach_resource,410
- resource 1 of 5
TI:13:57:24 TH:0x10f6090 FI:gpm-brightness-xrandr.c FN:gpm_brightness_xrandr_foreach_resource,410
- resource 2 of 5
TI:13:57:24 TH:0x10f6090 FI:gpm-brightness-xrandr.c FN:gpm_brightness_xrandr_output_get_percentage,252
- hard value=7, min=0, max=15
TI:13:57:24 TH:0x10f6090 FI:gpm-brightness-xrandr.c FN:gpm_brightness_xrandr_output_get_percentage,254
- percentage 46
TI:13:57:24 TH:0x10f6090 FI:gpm-brightness-xrandr.c FN:gpm_brightness_xrandr_foreach_resource,410
- resource 3 of 5
TI:13:57:24 TH:0x10f6090 FI:gpm-brightness-xrandr.c FN:gpm_brightness_xrandr_foreach_resource,410
- resource 4 of 5
TI:13:57:24 TH:0x10f6090 FI:gpm-brightness-xrandr.c FN:gpm_brightness_xrandr_foreach_resource,410
- resource 5 of 5
*** WARNING ***
TI:13:57:24 TH:0x10f6090 FI:gpm-brightness.c FN:gpm_brightness_trust_cache,107
- using cache for value 46 (probably okay)
TI:13:57:24 TH:0x10f6090 FI:gpm-brightness-xrandr.c FN:gpm_brightness_xrandr_foreach_screen,448
- using resource 0x1197210
TI:13:57:24 TH:0x10f6090 FI:gpm-brightness-xrandr.c FN:gpm_brightness_xrandr_foreach_resource,410
- resource 1 of 5
TI:13:57:24 TH:0x10f6090 FI:gpm-brightness-xrandr.c FN:gpm_brightness_xrandr_foreach_resource,410
- resource 2 of 5
TI:13:57:24 TH:0x10f6090 FI:gpm-brightness-xrandr.c FN:gpm_brightness_xrandr_output_set,349
- percent=100, absolute=15
TI:13:57:24 TH:0x10f6090 FI:gpm-brightness-xrandr.c FN:gpm_brightness_xrandr_output_set,351
- hard value=7, min=0, max=15
TI:13:57:24 TH:0x10f6090 FI:gpm-brightness-xrandr.c FN:gpm_brightness_xrandr_output_set,366
- using step of 1
TI:13:57:24 TH:0x10f6090 FI:gpm-brightness-xrandr.c FN:gpm_brightness_xrandr_foreach_resource,410
- resource 3 of 5
TI:13:57:24 TH:0x10f6090 FI:gpm-brightness-xrandr.c FN:gpm_brightness_xrandr_foreach_resource,410
- resource 4 of 5
TI:13:57:24 TH:0x10f6090 FI:gpm-brightness-xrandr.c FN:gpm_brightness_xrandr_foreach_resource,410
- resource 5 of 5
TI:13:57:24 TH:0x10f6090 FI:gpm-backlight.c FN:gpm_backlight_brightness_evaluate_and_set,361
- emitting brightness-changed : 100
TI:13:57:24 TH:0x10f6090 FI:gpm-idle.c FN:gpm_idle_evaluate,229
- setting up blank callback for 600s
TI:13:57:27 TH:0x10f6090 FI:gpm-idle.c FN:gpm_idle_idletime_reset_cb,353
- idletime reset
TI:13:57:27 TH:0x10f6090 FI:gpm-idle.c FN:gpm_idle_evaluate,187
- session_idle=0, idle_inhibited=0, suspend_inhibited=0, x_idle=0
TI:13:57:27 TH:0x10f6090 FI:gpm-idle.c FN:gpm_idle_set_mode,108
- Doing a state transition: normal
TI:13:57:27 TH:0x10f6090 FI:gpm-backlight.c FN:gpm_backlight_notify_system_idle_changed,508
- we have just been idle for 3.528874s
TI:13:57:27 TH:0x10f6090 FI:gpm-backlight.c FN:gpm_backlight_notify_system_idle_changed,515
- increasing idle dim time to 20s
TI:13:57:27 TH:0x10f6090 FI:gpm-idle.c FN:gpm_idle_set_timeout_dim,261
- Setting dim idle timeout: 20s
TI:13:57:27 TH:0x10f6090 FI:gpm-backlight.c FN:gpm_backlight_notify_system_idle_changed,533
- changing powersave idle status to 0
TI:13:57:27 TH:0x10f6090 FI:gpm-backlight.c FN:gpm_backlight_brightness_evaluate_and_set,300
- 1. main brightness 1.000000
TI:13:57:27 TH:0x10f6090 FI:gpm-backlight.c FN:gpm_backlight_brightness_evaluate_and_set,320
- 2. battery scale 1.000000, brightness 1.000000
TI:13:57:27 TH:0x10f6090 FI:gpm-backlight.c FN:gpm_backlight_brightness_evaluate_and_set,338
- 3. idle scale 1.000000, brightness 1.000000
TI:13:57:27 TH:0x10f6090 FI:gpm-brightness-xrandr.c FN:gpm_brightness_xrandr_foreach_screen,448
- using resource 0x1197210
TI:13:57:27 TH:0x10f6090 FI:gpm-brightness-xrandr.c FN:gpm_brightness_xrandr_foreach_resource,410
- resource 1 of 5
TI:13:57:27 TH:0x10f6090 FI:gpm-brightness-xrandr.c FN:gpm_brightness_xrandr_foreach_resource,410
- resource 2 of 5
TI:13:57:27 TH:0x10f6090 FI:gpm-brightness-xrandr.c FN:gpm_brightness_xrandr_output_get_percentage,252
- hard value=7, min=0, max=15
TI:13:57:27 TH:0x10f6090 FI:gpm-brightness-xrandr.c FN:gpm_brightness_xrandr_output_get_percentage,254
- percentage 46
TI:13:57:27 TH:0x10f6090 FI:gpm-brightness-xrandr.c FN:gpm_brightness_xrandr_foreach_resource,410
- resource 3 of 5
TI:13:57:27 TH:0x10f6090 FI:gpm-brightness-xrandr.c FN:gpm_brightness_xrandr_foreach_resource,410
- resource 4 of 5
TI:13:57:27 TH:0x10f6090 FI:gpm-brightness-xrandr.c FN:gpm_brightness_xrandr_foreach_resource,410
- resource 5 of 5
*** WARNING ***
TI:13:57:27 TH:0x10f6090 FI:gpm-brightness.c FN:gpm_brightness_trust_cache,107
- using cache for value 46 (probably okay)
TI:13:57:27 TH:0x10f6090 FI:gpm-brightness-xrandr.c FN:gpm_brightness_xrandr_foreach_screen,448
- using resource 0x1197210
TI:13:57:27 TH:0x10f6090 FI:gpm-brightness-xrandr.c FN:gpm_brightness_xrandr_foreach_resource,410
- resource 1 of 5
TI:13:57:27 TH:0x10f6090 FI:gpm-brightness-xrandr.c FN:gpm_brightness_xrandr_foreach_resource,410
- resource 2 of 5
TI:13:57:27 TH:0x10f6090 FI:gpm-brightness-xrandr.c FN:gpm_brightness_xrandr_output_set,349
- percent=100, absolute=15
TI:13:57:27 TH:0x10f6090 FI:gpm-brightness-xrandr.c FN:gpm_brightness_xrandr_output_set,351
- hard value=7, min=0, max=15
TI:13:57:27 TH:0x10f6090 FI:gpm-brightness-xrandr.c FN:gpm_brightness_xrandr_output_set,366
- using step of 1
TI:13:57:27 TH:0x10f6090 FI:gpm-brightness-xrandr.c FN:gpm_brightness_xrandr_foreach_resource,410
- resource 3 of 5
TI:13:57:27 TH:0x10f6090 FI:gpm-brightness-xrandr.c FN:gpm_brightness_xrandr_foreach_resource,410
- resource 4 of 5
TI:13:57:27 TH:0x10f6090 FI:gpm-brightness-xrandr.c FN:gpm_brightness_xrandr_foreach_resource,410
- resource 5 of 5
TI:13:57:27 TH:0x10f6090 FI:gpm-backlight.c FN:gpm_backlight_brightness_evaluate_and_set,361
- emitting brightness-changed : 100
TI:13:57:27 TH:0x10f6090 FI:gpm-idle.c FN:gpm_idle_evaluate,192
- X not idle
TI:13:57:45 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_device_changed_cb,905
- updating because /org/freedesktop/UPower/devices/battery_BAT0 changed
TI:13:57:45 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_update_composite_device,651
- printing device 0
native-path: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/PNP0C0A:00/power_supply/BAT0
vendor: ASUSTEK
model: UL50-56
power supply: yes
updated: Wed 16 Jun 2010 01:57:45 PM CEST (0 seconds ago)
has history: yes
has statistics: yes
battery
present: yes
rechargeable: yes
state: discharging
energy: 65.67 Wh
energy-empty: 0 Wh
energy-full: 81.06 Wh
energy-full-design: 84 Wh
energy-rate: 9.855 W
voltage: 16.062 V
time to empty: 6.7 hours
percentage: 81.0141%
capacity: 95.6964%
technology: lithium-ion
History (charge):
1276689465 81.014 discharging
1276689435 81.107 discharging
1276689405 81.199 discharging
1276689375 81.292 discharging
History (rate):
1276689465 9.855 discharging
1276689435 9.345 discharging
1276689405 8.505 discharging
1276689375 9.045 discharging
TI:13:57:45 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_update_composite_device,672
- using original device as only one primary battery
TI:13:57:45 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_device_changed_cb,914
- /org/freedesktop/UPower/devices/battery_BAT0 state is now discharging
TI:13:57:45 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_get_composite_device,595
- using original device as only one primary battery
TI:13:57:45 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_get_composite_device,595
- using original device as only one primary battery
TI:13:57:45 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_get_composite_device,595
- using original device as only one primary battery
TI:13:57:45 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_get_composite_device,595
- using original device as only one primary battery
TI:13:57:45 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_get_composite_device,595
- using original device as only one primary battery
TI:13:57:45 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_get_composite_device,595
- using original device as only one primary battery
TI:13:57:45 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_get_composite_device,595
- using original device as only one primary battery
TI:13:57:45 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_get_composite_device,595
- using original device as only one primary battery
TI:13:57:45 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_get_composite_device,595
- using original device as only one primary battery
TI:13:57:45 TH:0x10f6090 FI:gpm-upower.c FN:gpm_upower_get_device_icon,203
- got filename: gpm-battery-080
TI:13:57:45 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_recalculate_state_icon,453
- no change
TI:13:57:45 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_get_summary,264
- tooltip: Laptop battery 6 hours 35 minutes remaining (81.0%)
TI:13:57:45 TH:0x10f6090 FI:gpm-engine.c FN:gpm_engine_recalculate_state_summary,478
- ** EMIT: summary-changed(2): Laptop battery 6 hours 35 minutes remaining (81.0%)
Not only me I see:
https://bugzilla.gnome.org/show_bug.cgi?id=530346
Last edited by sveinemann (2010-06-16 12:03:48)OK, seems it was some kind of a bug because after today's full system upgrade I'm not able to reproduce the problem I posted before, Thanks sad clown for your help!!
-
CISCO UNITY - NOISE AFTER THE BIP
Hi,
We have the following scenario:
PSTN - PRI - AVAYA PBX - SIP TRUNK - CUBE - SIP TRUNK - CUCM - UNITY 7.0
When we call to the voicemail, after the "bip", we can hear a "sssssssh" sound. Have you ever experienced something similar? Can be related with the codec? It is strange, because the prompts and the "bip" are perfect, it is just the noise after that.
BRs!Hi Alicia,
Here is a link I found for Changing VAD/CNG values in Unity:
http://www.cisco.com/en/US/docs/voice_ip_comm/unity/3x/troubleshooting/guide/313/TSG_0450.html#wp1078077
Here are some important Links related to VAD/CNG:
Unity Hissing sound:
http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_tech_note09186a00801663a2.shtml#dtmf
Hissing sound in call :
http://www.cisco.com/en/US/tech/tk652/tk698/technologies_tech_note09186a00800a9982.shtml#topic2
VAD/CNG:
https://supportforums.cisco.com/docs/DOC-2580
I never saw VAD/CNG issues , so kindly let me know if it worked.
Regards,
Aman
“If you have knowledge, let others light their candles in it.” -
I've installed archlinux on my laptop, everything works well except the brightness control.
The screen originally has 11 brightness levels, but when I either press Fn+F6/F7 key or use gnome-power-manager to adjust brightness, it always skips a level.
/proc/acpi/video/VGA/LCD/brightness
levels: 100 60 20 28 36 44 52 60 68 76 84 92 100
current: 100
I can only get level 20 36 52 68 84 and 100
The problem also exists in console mode.
I tried adding video module to blacklist, then brightness cannot be adjusted at all.
However, I never get this problem in openSUSE, all 11 levels are available.
Could anyone help me? Thanks!:|http://forums.nvidia.com/index.php?show … t&p=386303
Hmmm...I found this on the nvidia forums:
I have a Samsung R700 laptop and my brightness stopped working after installing the restricted drivers. This is how I fixed it.
Press Ctrl-Alt-F1 to get a virtual console. Once you are in this console I think different video drivers are active so the following worked for me to adjust brightness.
Logged in and ran the following command:
echo -n 70 > /proc/acpi/video/NVID/LCD/brightness
then logged out and pressed Ctrl-Alt-F7 to go back to X
It's possible your brightness key on your laptop may work straight after you press ctrl-alt-f1 and you won't have to login and do the acpi stuff.
Also I have a startup script to set my brightness to a fixed value before X starts. It's not ideal but it's the only solution I could find that worked for me until the drivers are fixed!
Hope this helps.
Last edited by kclive18 (2008-07-08 11:19:25) -
LCD brightness level automatically reset
Dear Experts and other user,
Started from yesterday, my T61 laptop LCD brightness level automatically reset to lower in everytime i started it. I needed to manually tune up the brightness level.
The laptop is firmly connected to the AC power. And i have did nothing under the Windows system. Is it any hardware issue or software configuration issue?
Many thanks with your attention and advise.
EDMy "energy saver" pref does NOT have the options for "Automatically reduce the brightness of the display before the display sleeps" item mentioned above. It has only the 4 following entries:
Wake Options:
-Wake when the modem detects a ring
-Wake for Ethernet network administrator access
Other Options:
-Allow power button to sleep the computer
-Restart automatically after a power failure
This option does show up in the help file and I am imagining that I either don't have the hardware to support it or it is geared for laptops.
I have tried using the terminal to issue a pmset command (logged in as root of course) to see if I could affect this behavior.
pmset -a lessbright 0
pmset -a halfdim 0
neither of them showed up in the file:
/Library/Preferences/SystemConfiguration/com.apple.PowerManagement.plist
contents:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Custom Profile</key>
<dict>
<key>AC Power</key>
<dict>
<key>Automatic Restart On Power Loss</key>
<integer>0</integer>
<key>Disk Sleep Timer</key>
<integer>180</integer>
<key>Display Sleep Timer</key>
<integer>69</integer>
<key>Sleep On Power Button</key>
<integer>0</integer>
<key>System Sleep Timer</key>
<integer>69</integer>
<key>TTYSPreventSleep</key>
<integer>1</integer>
<key>Wake On AC Change</key>
<integer>0</integer>
<key>Wake On Clamshell Open</key>
<integer>1</integer>
<key>Wake On LAN</key>
<integer>0</integer>
<key>Wake On Modem Ring</key>
<integer>0</integer>
</dict>
</dict>
</dict>
</plist> -
Laptop mode lowers LCD brightness when on AC [SOLVED]
I have configured laptop-mode to turn LCD brightness to half of max value when on battery. Everything works fine. When disconnect my laptop from the power source it automatically lowers LCD brightness and when back on AC it comes back to max value. The problem I have is when coming back to AC and only if I leave the laptop unattended for awhile and then move the mouse or touch any button it lowers LCD brightness to what its supposed to be when on battery!!
I don't know whether this is a bug or a misconfigured file. Here is my laptop-mode LCD brightness configuration:
# Commands to execute to set the brightness on your LCD
BATT_BRIGHTNESS_COMMAND="echo 12"
LM_AC_BRIGHTNESS_COMMAND="echo 24"
NOLM_AC_BRIGHTNESS_COMMAND="echo 24"
BRIGHTNESS_OUTPUT="/sys/class/backlight/acpi_video0/brightness"
Any help will be appreciated!!!
Thanks in advanced, José.
Last edited by boina (2011-10-10 00:29:26)OK, seems it was some kind of a bug because after today's full system upgrade I'm not able to reproduce the problem I posted before, Thanks sad clown for your help!!
-
LCD Brightness, sony_acpi from aur won't build
I'm using a Sony VAIO vgn-sz430n, and the Fn keys won't work to change the brightness. I'm not so concerned about the Fn keys, for I've seen tons of documentation to get those working with xbindkeys, xmonad, openbox, etc. and I will worry about that later.
Most importantly, I cannot change the screen brightness. Xbacklight does not do anything, laptop-mode-tools and gnome/xfce4-power-manager do nothing. The screen brightness is always at the maximum.
I have an nvidia Geforce Go 7400 card with the proprietary nvidia driver
I read that I need the sony_acpi module, and I've been trying to install it from the AUR, but I get errors and I don't know what to do. I've tried with yaourt and manually. Here are the results from yaourt:
==> Building and installing package
==> Making package: sony_acpi 1-1 i686 (Sun Jun 14 14:56:12 CDT 2009)
==> Checking Runtime Dependencies...
==> Checking Buildtime Dependencies...
==> Retrieving Sources...
-> Found sony_acpi.tar.gz in build dir
==> Validating source files with md5sums...
sony_acpi.tar.gz ... Passed
==> Extracting Sources...
-> bsdtar -x -f sony_acpi.tar.gz
==> Removing existing pkg/ directory...
==> Entering fakeroot environment...
==> Starting build()...
make -C /lib/modules/2.6.29-ARCH/build SUBDIRS=/tmp/yaourt-tmp-agi/aur-sony_acpi/sony_acpi/src/sony_acpi modules
make[1]: Entering directory `/usr/src/linux-2.6.29-ARCH'
CC [M] /tmp/yaourt-tmp-agi/aur-sony_acpi/sony_acpi/src/sony_acpi/sony_acpi.o
/tmp/yaourt-tmp-agi/aur-sony_acpi/sony_acpi/src/sony_acpi/sony_acpi.c:55: warning: initialization from incompatible pointer type
/tmp/yaourt-tmp-agi/aur-sony_acpi/sony_acpi/src/sony_acpi/sony_acpi.c: In function 'sony_walk_callback':
/tmp/yaourt-tmp-agi/aur-sony_acpi/sony_acpi/src/sony_acpi/sony_acpi.c:253: error: dereferencing pointer to incomplete type
/tmp/yaourt-tmp-agi/aur-sony_acpi/sony_acpi/src/sony_acpi/sony_acpi.c:255: error: dereferencing pointer to incomplete type
/tmp/yaourt-tmp-agi/aur-sony_acpi/sony_acpi/src/sony_acpi/sony_acpi.c:256: error: dereferencing pointer to incomplete type
/tmp/yaourt-tmp-agi/aur-sony_acpi/sony_acpi/src/sony_acpi/sony_acpi.c: In function 'sony_acpi_add':
/tmp/yaourt-tmp-agi/aur-sony_acpi/sony_acpi/src/sony_acpi/sony_acpi.c:269: error: lvalue required as left operand of assignment
make[2]: *** [/tmp/yaourt-tmp-agi/aur-sony_acpi/sony_acpi/src/sony_acpi/sony_acpi.o] Error 1
make[1]: *** [_module_/tmp/yaourt-tmp-agi/aur-sony_acpi/sony_acpi/src/sony_acpi] Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.29-ARCH'
make: *** [default] Error 2
==> ERROR: Build Failed.
Aborting...
Error: Makepkg was unable to build sony_acpi package.
The strange thing is this works in other distributions, such as Ubuntu. If I fired up a live cd and tested out my Fn keys, the brightness would change and there would be an on screen display for feedback.
What is Ubuntu doing, specifically, that Arch is not doing? Is there any way I could load an ubuntu live cd and then find what files/programs/modules/whatever are in place that allow brightness changes? Does anyone know this offhand?
Help!I have Sony Vaio VGN-FZ38M with Nvidia 8400M GT. I used package 'nvclock' (it is in repo) to control lcd brightness, here site with more info: NVClock. Some time ago I also configured Fn keys to work with it (on Ubuntu), but on Arch I didn't manged but I didn't try hard (in general i don't need, my laptop is stationary all the time). Solution I've found somwehere in Ubuntu forums.
edit: typo in address
edit2:
here's the solution from Ubuntu: http://newyork.ubuntuforums.org/showthr … ?t=1004568
Last edited by folletto (2009-06-14 20:58:56) -
Laptop-mode / laptop-mode-tools lcd brightness issue
I have an issue with my lcd brightness config in laptop-mode tools
here is the brightness values
[venky@ARCHROCKS ~]$ cat /proc/acpi/video/VID/LCD/brightness
levels: 72 24 12 24 36 48 60 72 84 100
current: 72
[venky@ARCHROCKS ~]$
following is my lcd-bightness.conf file under /etc/laptop-mode/conf.d
# Configuration file for Laptop Mode Tools module lcd-brightness.
# For more information, consult the laptop-mode.conf(8) manual page.
# LCD brightness settings
# Using these settings, you can make laptop mode tools automatically adjust
# your LCD's brightness settings. The settings are extremely simple -- they
# only allow for the execution of a command, nothing more. The reason for this
# is that LCD brightness settings are very different between laptop vendors.
# Suggestions for commands:
# * If your system has the file "/proc/acpi/video/VID/LCD/brightness" (VID may
# be VID1 or similar), use this file as BRIGHTNESS_OUTPUT, and use
# the command "echo <value>". The possible values can be listed using the
# command:
# cat /proc/acpi/video/VID/LCD/brightness
# * If you have a file /sys/class/backlight/.../brightness, then you can use
# that file as BRIGHTNESS_OUTPUT, and the command "echo <value>".
# As far as I understand it the values are between 0 and
# the value contained in the file /sys/class/backlight/.../max_brightness.
# * For Toshiba laptops, use the command "toshset" with the -lcd or -inten
# command. Read the toshset(1) manual page for more information on the
# parameters for this command. If you use this command, set
# BRIGHTNESS_OUTPUT to "/dev/null".
# IMPORTANT: In versions 1.36 and earlier, these settings were included in the
# main laptop-mode.conf configuration file. If they are still present, they
# overrule the settings in this file. To fix this, simply delete the settings
# from the main config file.
# Should laptop mode tools control LCD brightness?
CONTROL_BRIGHTNESS=1
# Commands to execute to set the brightness on your LCD
BATT_BRIGHTNESS_COMMAND="echo 24"
LM_AC_BRIGHTNESS_COMMAND="echo 100"
NOLM_AC_BRIGHTNESS_COMMAND="echo 72"
BRIGHTNESS_OUTPUT="/proc/acpi/video/VID/LCD/brightness"
so basically while in AC power i want full brightness when on battery i want one notch more than the minimum brightness and when laptop-mode is not running i want 2 notches less than maximum brightness.
the battery mode works fine when i unplug the computer but when i replug the AC power it goes to 72 instead of 100. I mean laptop mode is running coz when I remove ac power it goes to 24 again.
Am I doing something wrong?When you plug in AC power, laptop-mode probably turns down, so LCD brightness is set to 72. It depends on if you have set in /etc/laptop-mode/laptop-mode.conf ENABLE_LAPTOP_MODE_ON_AC to 0 or 1.
-
T440S OSD Brightness control failure after resume from Sleep
Hi,
I have owned a T440S since late 2013.
Relevant Details:
T440S
Model : 20AQCTO1WW
OS : Windows 7 professional (original installation by Lenovo)
Latest Drivers installed as of June 2014 - including HotKey and Power Management
HotKey ver : 8.30
Power Managment : 6.65.1
Since receiving this laptop, OSD birightness control has always failed to work, i.e. does not appear on the screen
when using the Fn+F5/F6 key combination nor does it control actual screen brightness AFTER FIRST resuming from sleep
mode.
Sequence of steps that demonstrates the above symptom:
1. OSD brightness works fine after reboot
2. Putting the machine to sleep (I do not use hibernate) for a duration longer than a few minutes
3. Open lid the first time, hit Fn to resume machine
4. Pressing Fn+F5/F6 key combo does not display the brightness slider nor does it control brightness
5. Closing the lid and opening it again, causes OSD brightness slider to flash brifely and is now fully functional
using Fn+F5/F6 keys
Your tech department should easily be able to re-create this issue on any stock T440S/Win7pro machine, as
I have seen others comment about this very issue across other T440/OS variants.
This very same behavior has been there since the beginning.
When is Lenovo going to FINALLY FIX IT ONCE AND FOR ALL?
Thx,
--Alon
Solved!
Go to Solution.Try this hotfix:
https://support.microsoft.com/kb/2752407
W520: i7-2720QM, Q2000M at 1080/688/1376, 21GB RAM, 500GB + 750GB HDD, FHD screen
X61T: L7500, 3GB RAM, 500GB HDD, XGA screen, Ultrabase
Y3P: 5Y70, 8GB RAM, 256GB SSD, QHD+ screen -
Duet makes noise after switching between finder audio and Logic
Hi
My Duet makes noise after switching between "finder audio" and "Logic", In other words i would play a mp3 in the finder and when returning to Logic all my audio sounds like the "lo-fi" RTAS free plug digidesign gives away now.
This is happening on a White *iMac 24"*
Model Name: iMac
Model Identifier: iMac6,1
Processor Name: Intel Core 2 Duo
Processor Speed: 2.33 GHz
Number Of Processors: 1
Total Number Of Cores: 2
L2 Cache: 4 MB
Memory: 2 GB
Bus Speed: 667 MHz
Boot ROM Version: IM61.0093.B07
SMC Version (system): 1.10f3
MacOsx 10,5,7Does this happen every single time? The same thing happens to me every once in a while. I just close Logic and Maestro and unplug the Duet. Then, in this order, plug in the Duet, wait for it to click, load Maestro, load Logic. Works every time.
Edit: It does only seem to happen when I switch from Logic and the audio output from the Duet to internal and then come back quickly. I don't think it's an issue with the Duet hardware itself.
Message was edited by: AecDuck
Maybe you are looking for
-
Hi All, I am facing the below error while installing Oracle RAC in Silent Mode. SEVERE: There are no common subnets represented by network interfaces across all cluster nodes. SEVERE: [FATAL] [INS-40925] One or more nodes have interfaces not configur
-
Ok, ever since upgrading to iOS 8 I've noticed some issues with how Pages and Photostream works with mine and my wife's iPhone. We both have iPhone 5s w/ iOS 8 and now the pictures she takes on her phone do not automatically download into my Photostr
-
New iMac Can't See HD and screen goes black then grey then black..etc.
Hi I've got a new 20" Alu iMac and it was working fine for the past 3 weeks. All of a sudden this morning starting it up the screen went completely grey then after a while the apple logo came on (I thought it was eventually starting) then it went com
-
Purchase order relased e-mail should trigger
Hi All, When i relase purchsase order , An email should trigger to particular user. Can you explain how? venkat
-
How to store grid points in a file using Java Swing?
Please someone help me with any suggestions about how to store the grid points in a file using Java Swing