morphious6
Posts: 17
Joined: Thu Sep 17, 2015 8:21 pm

Re: Sleep Mode - and or turn off backlight?

Tue Dec 13, 2016 5:44 pm

Admins, can we Please get some kind of response to when this will be fixed? the screen is unusable in the current state the last update left it!

jdb
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 2120
Joined: Thu Jul 11, 2013 2:37 pm

Re: Sleep Mode - and or turn off backlight?

Wed Dec 14, 2016 3:52 pm

Please re-run sudo apt-get update && sudo apt-get upgrade. There is a fix in the firmware.
Rockets are loud.
https://astro-pi.org

morphious6
Posts: 17
Joined: Thu Sep 17, 2015 8:21 pm

Re: Sleep Mode - and or turn off backlight?

Wed Dec 14, 2016 4:28 pm

Hello, I just ran it , and rebooted. no screen shows when I boot and I do not see any links in rpi_backlight dir. This is what I get when I run the comand manually.

[email protected]:~# sudo bash -c "echo 1 > /sys/class/backlight/rpi_backlight/bl_power" Off
Off: /sys/class/backlight/rpi_backlight/bl_power: No such file or directory

Is there are package I can DL directly instead of a blanket update & upgrade ?

jdb
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 2120
Joined: Thu Jul 11, 2013 2:37 pm

Re: Sleep Mode - and or turn off backlight?

Wed Dec 14, 2016 5:20 pm

That's odd. Can you post the full dmesg log?
Rockets are loud.
https://astro-pi.org

morphious6
Posts: 17
Joined: Thu Sep 17, 2015 8:21 pm

Re: Sleep Mode - and or turn off backlight?

Wed Dec 14, 2016 10:14 pm

[email protected]:~# dmesg
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Initializing cgroup subsys cpuacct
[ 0.000000] Linux version 4.4.34-v7+ ([email protected]) (gcc version 4.9.3 (crosstool-NG crosstool-ng-1.22.0-88-g8460611) ) #930 SMP Wed Nov 23 15:20:41 GMT 2016
[ 0.000000] CPU: ARMv7 Processor [410fd034] revision 4 (ARMv7), cr=10c5383d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000] Machine model: Raspberry Pi 3 Model B Rev 1.2
[ 0.000000] cma: Reserved 8 MiB at 0x3d800000
[ 0.000000] Memory policy: Data cache writealloc
[ 0.000000] On node 0 totalpages: 253952
[ 0.000000] free_area_init_node: node 0, pgdat 808c4f40, node_mem_map bcf3a000
[ 0.000000] Normal zone: 2232 pages used for memmap
[ 0.000000] Normal zone: 0 pages reserved
[ 0.000000] Normal zone: 253952 pages, LIFO batch:31
[ 0.000000] [bcm2709_smp_init_cpus] enter (9520->f3003010)
[ 0.000000] [bcm2709_smp_init_cpus] ncores=4
[ 0.000000] PERCPU: Embedded 13 pages/cpu @bcef6000 s22592 r8192 d22464 u53248
[ 0.000000] pcpu-alloc: s22592 r8192 d22464 u53248 alloc=13*4096
[ 0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 251720
[ 0.000000] Kernel command line: 8250.nr_uarts=0 dma.dmachans=0x7f35 bcm2708_fb.fbwidth=1280 bcm2708_fb.fbheight=720 bcm2709.boardrev=0xa22082 bcm2709.serial=0xeb925dc1 smsc95xx.macaddr=B8:27:EB:92:5D:C1 bcm2708_fb.fbdepth=16 bcm2708_fb.fbswap=1 bcm2709.uart_clock=48000000 vc_mem.mem_base=0x3ea00000 vc_mem.mem_size=0x3f000000 dwc_otg.lpm_enable=0 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=noop rootwait
[ 0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[ 0.000000] Memory: 987784K/1015808K available (6357K kernel code, 432K rwdata, 1716K rodata, 476K init, 764K bss, 19832K reserved, 8192K cma-reserved)
[ 0.000000] Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
vmalloc : 0xbe800000 - 0xff800000 (1040 MB)
lowmem : 0x80000000 - 0xbe000000 ( 992 MB)
modules : 0x7f000000 - 0x80000000 ( 16 MB)
.text : 0x80008000 - 0x807ea674 (8074 kB)
.init : 0x807eb000 - 0x80862000 ( 476 kB)
.data : 0x80862000 - 0x808ce250 ( 433 kB)
.bss : 0x808d1000 - 0x809901ec ( 765 kB)
[ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[ 0.000000] Hierarchical RCU implementation.
[ 0.000000] Build-time adjustment of leaf fanout to 32.
[ 0.000000] NR_IRQS:16 nr_irqs:16 16
[ 0.000000] Architected cp15 timer(s) running at 19.20MHz (phys).
[ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x46d987e47, max_idle_ns: 440795202767 ns
[ 0.000005] sched_clock: 56 bits at 19MHz, resolution 52ns, wraps every 4398046511078ns
[ 0.000014] Switching to timer-based delay loop, resolution 52ns
[ 0.000171] Console: colour dummy device 80x30
[ 0.000700] console [tty1] enabled
[ 0.000724] Calibrating delay loop (skipped), value calculated using timer frequency.. 38.40 BogoMIPS (lpj=192000)
[ 0.000759] pid_max: default: 32768 minimum: 301
[ 0.000943] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.000964] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.001519] Disabling cpuset control group subsystem
[ 0.001550] Initializing cgroup subsys io
[ 0.001578] Initializing cgroup subsys memory
[ 0.001614] Initializing cgroup subsys devices
[ 0.001638] Initializing cgroup subsys freezer
[ 0.001660] Initializing cgroup subsys net_cls
[ 0.001700] CPU: Testing write buffer coherency: ok
[ 0.001752] ftrace: allocating 21236 entries in 63 pages
[ 0.028057] CPU0: update cpu_capacity 1024
[ 0.028101] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[ 0.028118] [bcm2709_smp_prepare_cpus] enter
[ 0.028218] Setting up static identity map for 0x8240 - 0x8274
[ 0.029163] [bcm2709_boot_secondary] cpu:1 started (0) 18
[ 0.029320] [bcm2709_secondary_init] enter cpu:1
[ 0.029348] CPU1: update cpu_capacity 1024
[ 0.029351] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[ 0.029553] [bcm2709_boot_secondary] cpu:2 started (0) 18
[ 0.029674] [bcm2709_secondary_init] enter cpu:2
[ 0.029686] CPU2: update cpu_capacity 1024
[ 0.029689] CPU2: thread -1, cpu 2, socket 0, mpidr 80000002
[ 0.029877] [bcm2709_boot_secondary] cpu:3 started (0) 17
[ 0.029963] [bcm2709_secondary_init] enter cpu:3
[ 0.029974] CPU3: update cpu_capacity 1024
[ 0.029977] CPU3: thread -1, cpu 3, socket 0, mpidr 80000003
[ 0.030008] Brought up 4 CPUs
[ 0.030058] SMP: Total of 4 processors activated (153.60 BogoMIPS).
[ 0.030073] CPU: All CPU(s) started in HYP mode.
[ 0.030087] CPU: Virtualization extensions available.
[ 0.030440] devtmpfs: initialized
[ 0.035966] VFP support v0.3: implementor 41 architecture 3 part 40 variant 3 rev 4
[ 0.036170] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[ 0.036554] pinctrl core: initialized pinctrl subsystem
[ 0.036844] NET: Registered protocol family 16
[ 0.039924] DMA: preallocated 4096 KiB pool for atomic coherent allocations
[ 0.043316] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.
[ 0.043341] hw-breakpoint: maximum watchpoint size is 8 bytes.
[ 0.043432] Serial: AMBA PL011 UART driver
[ 0.043510] uart-pl011 3f201000.uart: could not find pctldev for node /soc/[email protected]/uart0_pins, deferring probe
[ 0.043619] bcm2835-mbox 3f00b880.mailbox: mailbox enabled
[ 0.089067] bcm2835-dma 3f007000.dma: DMA legacy API manager at f3007000, dmachans=0x1
[ 0.089382] SCSI subsystem initialized
[ 0.089487] usbcore: registered new interface driver usbfs
[ 0.089543] usbcore: registered new interface driver hub
[ 0.089608] usbcore: registered new device driver usb
[ 0.097706] raspberrypi-firmware soc:firmware: Attached to firmware from 2016-11-25 16:05
[ 0.124043] clocksource: Switched to clocksource arch_sys_counter
[ 0.147522] FS-Cache: Loaded
[ 0.147703] CacheFiles: Loaded
[ 0.153934] NET: Registered protocol family 2
[ 0.154468] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[ 0.154538] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
[ 0.154644] TCP: Hash tables configured (established 8192 bind 8192)
[ 0.154714] UDP hash table entries: 512 (order: 2, 16384 bytes)
[ 0.154748] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[ 0.154883] NET: Registered protocol family 1
[ 0.155076] RPC: Registered named UNIX socket transport module.
[ 0.155092] RPC: Registered udp transport module.
[ 0.155106] RPC: Registered tcp transport module.
[ 0.155120] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 0.155652] hw perfevents: enabled with armv7_cortex_a7 PMU driver, 7 counters available
[ 0.156355] futex hash table entries: 1024 (order: 4, 65536 bytes)
[ 0.163024] VFS: Disk quotas dquot_6.6.0
[ 0.163188] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 0.164387] FS-Cache: Netfs 'nfs' registered for caching
[ 0.164859] NFS: Registering the id_resolver key type
[ 0.164898] Key type id_resolver registered
[ 0.164912] Key type id_legacy registered
[ 0.166126] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
[ 0.166207] io scheduler noop registered (default)
[ 0.166226] io scheduler deadline registered
[ 0.166261] io scheduler cfq registered
[ 0.167627] BCM2708FB: allocated DMA memory fdc10000
[ 0.167652] BCM2708FB: allocated DMA channel 0 @ f3007000
[ 0.176333] Console: switching to colour frame buffer device 160x45
[ 0.948271] bcm2835-rng 3f104000.rng: hwrng registered
[ 0.948384] vc-cma: Videocore CMA driver
[ 0.948422] vc-cma: vc_cma_base = 0x00000000
[ 0.948464] vc-cma: vc_cma_size = 0x00000000 (0 MiB)
[ 0.948509] vc-cma: vc_cma_initial = 0x00000000 (0 MiB)
[ 0.948666] vc-mem: phys_addr:0x00000000 mem_base=0x3ea00000 mem_size:0x3f000000(1008 MiB)
[ 0.956202] brd: module loaded
[ 0.960661] loop: module loaded
[ 0.961210] vchiq: vchiq_init_state: slot_zero = 0xbdc80000, is_master = 0
[ 0.962226] Loading iSCSI transport class v2.0-870.
[ 0.963953] usbcore: registered new interface driver smsc95xx
[ 0.965401] dwc_otg: version 3.00a 10-AUG-2012 (platform bus)
[ 1.166944] Core Release: 2.80a
[ 1.168315] Setting default values for core params
[ 1.169693] Finished setting default values for core params
[ 1.371251] Using Buffer DMA mode
[ 1.372599] Periodic Transfer Interrupt Enhancement - disabled
[ 1.373964] Multiprocessor Interrupt Enhancement - disabled
[ 1.375329] OTG VER PARAM: 0, OTG VER FLAG: 0
[ 1.376690] Dedicated Tx FIFOs mode
[ 1.378206] WARN::dwc_otg_hcd_init:1047: FIQ DMA bounce buffers: virt = 0xbdc04000 dma = 0xfdc04000 len=9024
[ 1.379664] FIQ FSM acceleration enabled for :
Non-periodic Split Transactions
Periodic Split Transactions
High-Speed Isochronous Endpoints
Interrupt/Control Split Transaction hack enabled
[ 1.386641] dwc_otg: Microframe scheduler enabled
[ 1.386670] WARN::hcd_init_fiq:413: FIQ on core 1 at 0x8044846c
[ 1.388048] WARN::hcd_init_fiq:414: FIQ ASM at 0x804487dc length 36
[ 1.389410] WARN::hcd_init_fiq:439: MPHI regs_base at 0xbe87e000
[ 1.390791] dwc_otg 3f980000.usb: DWC OTG Controller
[ 1.392160] dwc_otg 3f980000.usb: new USB bus registered, assigned bus number 1
[ 1.393557] dwc_otg 3f980000.usb: irq 62, io mem 0x00000000
[ 1.394959] Init: Port Power? op_state=1
[ 1.396289] Init: Power Port (0)
[ 1.397702] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 1.399063] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.400436] usb usb1: Product: DWC OTG Controller
[ 1.401803] usb usb1: Manufacturer: Linux 4.4.34-v7+ dwc_otg_hcd
[ 1.403190] usb usb1: SerialNumber: 3f980000.usb
[ 1.404998] hub 1-0:1.0: USB hub found
[ 1.406368] hub 1-0:1.0: 1 port detected
[ 1.408054] dwc_otg: FIQ enabled
[ 1.408059] dwc_otg: NAK holdoff enabled
[ 1.408063] dwc_otg: FIQ split-transaction FSM enabled
[ 1.408083] Module dwc_common_port init
[ 1.408212] usbcore: registered new interface driver usb-storage
[ 1.409726] mousedev: PS/2 mouse device common for all mice
[ 1.411510] bcm2835-cpufreq: min=600000 max=1200000
[ 1.414441] sdhci: Secure Digital Host Controller Interface driver
[ 1.417239] sdhci: Copyright(c) Pierre Ossman
[ 1.420290] sdhost: log_buf @ bdc07000 (fdc07000)
[ 1.474083] mmc0: sdhost-bcm2835 loaded - DMA enabled (>1)
[ 1.477053] sdhci-pltfm: SDHCI platform and OF driver helper
[ 1.480199] ledtrig-cpu: registered to indicate activity on CPUs
[ 1.483064] hidraw: raw HID events driver (C) Jiri Kosina
[ 1.486000] usbcore: registered new interface driver usbhid
[ 1.488734] usbhid: USB HID core driver
[ 1.491994] Initializing XFRM netlink socket
[ 1.494746] NET: Registered protocol family 17
[ 1.497564] Key type dns_resolver registered
[ 1.500675] Registering SWP/SWPB emulation handler
[ 1.504246] registered taskstats version 1
[ 1.507061] vc-sm: Videocore shared memory driver
[ 1.509719] [vc_sm_connected_init]: start
[ 1.512522] vc_vchi_sm_init: failed to open VCHI service (-1)
[ 1.512620] [vc_sm_connected_init]: failed to initialize shared memory service
[ 1.517707] [vc_sm_connected_init]: end - returning -1
[ 1.521678] 3f201000.uart: ttyAMA0 at MMIO 0x3f201000 (irq = 87, base_baud = 0) is a PL011 rev2
[ 1.524804] of_cfs_init
[ 1.527548] of_cfs_init: OK
[ 1.531029] Waiting for root device /dev/mmcblk0p2...
[ 1.531601] mmc0: host does not support reading read-only switch, assuming write-enable
[ 1.533506] mmc0: overclocking to 100000000Hz
[ 1.533612] mmc0: new high speed SDHC card at address 59b4
[ 1.534223] mmcblk0: mmc0:59b4 00000 14.9 GiB
[ 1.537176] mmcblk0: p1 p2
[ 1.574896] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[ 1.577760] VFS: Mounted root (ext4 filesystem) readonly on device 179:2.
[ 1.581574] devtmpfs: mounted
[ 1.585142] Freeing unused kernel memory: 476K (807eb000 - 80862000)
[ 1.604176] Indeed it is in host mode hprt0 = 00021501
[ 1.784102] usb 1-1: new high-speed USB device number 2 using dwc_otg
[ 1.787147] Indeed it is in host mode hprt0 = 00001101
[ 1.909604] random: systemd: uninitialized urandom read (16 bytes read, 24 bits of entropy available)
[ 1.916553] systemd[1]: systemd 215 running in system mode. (+PAM +AUDIT +SELINUX +IMA +SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ -SECCOMP -APPARMOR)
[ 1.920145] systemd[1]: Detected architecture 'arm'.
[ 1.984396] usb 1-1: New USB device found, idVendor=0424, idProduct=9514
[ 1.987593] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1.991506] hub 1-1:1.0: USB hub found
[ 1.994748] hub 1-1:1.0: 5 ports detected
[ 2.123795] NET: Registered protocol family 10
[ 2.128362] systemd[1]: Inserted module 'ipv6'
[ 2.133014] systemd[1]: Set hostname to <EI.house>.
[ 2.274098] usb 1-1.1: new high-speed USB device number 3 using dwc_otg
[ 2.312197] random: systemd-sysv-ge: uninitialized urandom read (16 bytes read, 63 bits of entropy available)
[ 2.374432] usb 1-1.1: New USB device found, idVendor=0424, idProduct=ec00
[ 2.377755] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 2.383865] smsc95xx v1.0.4
[ 2.447722] smsc95xx 1-1.1:1.0 eth0: register 'smsc95xx' at usb-3f980000.usb-1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:92:5d:c1
[ 2.607221] random: systemd: uninitialized urandom read (16 bytes read, 69 bits of entropy available)
[ 2.611979] random: systemd: uninitialized urandom read (16 bytes read, 69 bits of entropy available)
[ 2.616913] random: systemd: uninitialized urandom read (16 bytes read, 69 bits of entropy available)
[ 2.633251] random: systemd: uninitialized urandom read (16 bytes read, 69 bits of entropy available)
[ 2.646495] random: systemd: uninitialized urandom read (16 bytes read, 69 bits of entropy available)
[ 2.649956] random: systemd: uninitialized urandom read (16 bytes read, 69 bits of entropy available)
[ 2.681705] random: systemd: uninitialized urandom read (16 bytes read, 69 bits of entropy available)
[ 2.703282] random: systemd: uninitialized urandom read (16 bytes read, 70 bits of entropy available)
[ 2.798089] systemd[1]: Cannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service failed to load: No such file or directory.
[ 2.807546] systemd[1]: Starting Forward Password Requests to Wall Directory Watch.
[ 2.811234] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[ 2.814685] systemd[1]: Starting Remote File Systems (Pre).
[ 2.822051] systemd[1]: Reached target Remote File Systems (Pre).
[ 2.825551] systemd[1]: Starting Arbitrary Executable File Formats File System Automount Point.
[ 2.833220] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
[ 2.836838] systemd[1]: Starting Dispatch Password Requests to Console Directory Watch.
[ 2.840482] systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
[ 2.843980] systemd[1]: Starting Paths.
[ 2.851100] systemd[1]: Reached target Paths.
[ 2.854337] systemd[1]: Starting Encrypted Volumes.
[ 2.861123] systemd[1]: Reached target Encrypted Volumes.
[ 2.864392] systemd[1]: Starting Swap.
[ 2.871109] systemd[1]: Reached target Swap.
[ 2.874294] systemd[1]: Expecting device dev-sda1.device...
[ 2.881029] systemd[1]: Starting mnt-usb_1.automount.
[ 2.890252] systemd[1]: Set up automount mnt-usb_1.automount.
[ 2.893524] systemd[1]: Expecting device dev-mmcblk0p1.device...
[ 2.900242] systemd[1]: Starting Root Slice.
[ 2.906930] systemd[1]: Created slice Root Slice.
[ 2.909954] systemd[1]: Starting User and Session Slice.
[ 2.916479] systemd[1]: Created slice User and Session Slice.
[ 2.919549] systemd[1]: Starting /dev/initctl Compatibility Named Pipe.
[ 2.926456] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
[ 2.929750] systemd[1]: Starting Delayed Shutdown Socket.
[ 2.936982] systemd[1]: Listening on Delayed Shutdown Socket.
[ 2.940273] systemd[1]: Starting Journal Socket (/dev/log).
[ 2.947111] systemd[1]: Listening on Journal Socket (/dev/log).
[ 2.950278] systemd[1]: Starting udev Control Socket.
[ 2.957036] systemd[1]: Listening on udev Control Socket.
[ 2.960158] systemd[1]: Starting udev Kernel Socket.
[ 2.966692] systemd[1]: Listening on udev Kernel Socket.
[ 2.969677] systemd[1]: Starting Journal Socket.
[ 2.976019] systemd[1]: Listening on Journal Socket.
[ 2.978980] systemd[1]: Starting System Slice.
[ 2.985313] systemd[1]: Created slice System Slice.
[ 2.988265] systemd[1]: Starting File System Check on Root Device...
[ 3.024666] systemd[1]: Starting system-systemd\x2dfsck.slice.
[ 3.031815] systemd[1]: Created slice system-systemd\x2dfsck.slice.
[ 3.034972] systemd[1]: Starting system-getty.slice.
[ 3.042196] systemd[1]: Created slice system-getty.slice.
[ 3.045533] systemd[1]: Starting Increase datagram queue length...
[ 3.055062] systemd[1]: Starting Nameserver information manager...
[ 3.064597] systemd[1]: Starting Restore / save the current clock...
[ 3.093656] systemd[1]: Started Set Up Additional Binary Formats.
[ 3.096966] systemd[1]: Starting udev Coldplug all Devices...
[ 3.106458] systemd[1]: Mounting Debug File System...
[ 3.115892] systemd[1]: Mounting POSIX Message Queue File System...
[ 3.151880] systemd[1]: Starting Load Kernel Modules...
[ 3.163729] systemd[1]: Starting Create list of required static device nodes for the current kernel...
[ 3.173489] systemd[1]: Mounted Huge Pages File System.
[ 3.177366] systemd[1]: Starting LSB: Set keymap...
[ 3.187392] systemd[1]: Starting Slices.
[ 3.195576] systemd[1]: Reached target Slices.
[ 3.208045] systemd[1]: Mounted POSIX Message Queue File System.
[ 3.209460] fuse init (API version 7.23)
[ 3.218264] systemd[1]: Mounted Debug File System.
[ 3.226424] systemd[1]: Started Increase datagram queue length.
[ 3.242792] systemd[1]: Started File System Check on Root Device.
[ 3.254377] systemd[1]: Started Restore / save the current clock.
[ 3.267106] systemd[1]: Started Load Kernel Modules.
[ 3.275763] systemd[1]: Started Create list of required static device nodes for the current kernel.
[ 3.284844] systemd[1]: Started LSB: Set keymap.
[ 3.295563] systemd[1]: Started Nameserver information manager.
[ 3.310643] systemd[1]: Started udev Coldplug all Devices.
[ 3.314960] systemd[1]: Time has been changed
[ 3.577859] systemd[1]: Starting Create Static Device Nodes in /dev...
[ 3.624755] systemd[1]: Starting Apply Kernel Variables...
[ 3.635145] systemd[1]: Mounting FUSE Control File System...
[ 3.645766] systemd[1]: Mounting Configuration File System...
[ 3.656899] systemd[1]: Starting Syslog Socket.
[ 3.665452] systemd[1]: Listening on Syslog Socket.
[ 3.669100] systemd[1]: Starting Journal Service...
[ 3.682894] systemd[1]: Started Journal Service.
[ 3.852996] systemd-udevd[161]: starting version 215
[ 4.104750] gpiomem-bcm2835 3f200000.gpiomem: Initialised: Registers at 0x3f200000
[ 4.117803] bcm2835-wdt 3f100000.watchdog: Broadcom BCM2835 watchdog timer
[ 4.414282] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[ 4.780365] systemd-journald[160]: Received request to flush runtime journal from PID 1
[ 5.066872] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
[ 5.071269] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 6.303179] Adding 102396k swap on /var/swap. Priority:-1 extents:2 across:102400k SSFS
[ 6.646626] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 6.651748] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xC5E1
[ 10.557488] random: nonblocking pool is initialized

jdb
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 2120
Joined: Thu Jul 11, 2013 2:37 pm

Re: Sleep Mode - and or turn off backlight?

Wed Dec 14, 2016 11:04 pm

Hm, nothing unusual there. Is the module rpi_backlight present in lsmod?
Rockets are loud.
https://astro-pi.org

morphious6
Posts: 17
Joined: Thu Sep 17, 2015 8:21 pm

Re: Sleep Mode - and or turn off backlight?

Thu Dec 15, 2016 12:34 am

I do not see it.

[email protected]:~# lsmod
Module Size Used by
bcm2835_wdt 3225 0
bcm2835_gpiomem 3040 0
uio_pdrv_genirq 3164 0
uio 8000 1 uio_pdrv_genirq
fuse 84037 1
ipv6 347594 34

gfxfr
Posts: 9
Joined: Sun Dec 04, 2016 9:04 pm

Re: Sleep Mode - and or turn off backlight?

Fri Dec 16, 2016 6:47 am

Done and apt-get update/upgrade yesterday, the problem is still not fixed.

dmesg this morning :
[29620.574139] rpi-backlight rpi_backlight: Backlight change failed

lilgman
Posts: 9
Joined: Wed Nov 04, 2015 2:26 pm
Location: Lesotho, Africa

Re: Sleep Mode - and or turn off backlight?

Sat Dec 17, 2016 5:49 pm

I can also confirm that upgrading does not solve this problem. Anything else I could try?

Thanks!

morphious6
Posts: 17
Joined: Thu Sep 17, 2015 8:21 pm

Re: Sleep Mode - and or turn off backlight?

Sun Dec 18, 2016 3:43 pm

Bump, still not working :-(

RogueM
Posts: 3
Joined: Sat Apr 11, 2015 12:43 pm

Re: Sleep Mode - and or turn off backlight?

Sun Dec 18, 2016 7:17 pm

You can trigger manually a problem which I am relatively convinced is related by restarting the rpi-display-backlight service:

Code: Select all

sudo systemctl restart rpi-display-backlight
(or stop+ start, the culprit being start)

... I am going to try the Pi without this service running for a while and report back if the issue described herein (which I have also experienced) goes away.

EDIT: nope, makes no difference.

gfxfr
Posts: 9
Joined: Sun Dec 04, 2016 9:04 pm

Re: Sleep Mode - and or turn off backlight?

Tue Dec 20, 2016 12:23 pm

The last updates (last day) seems to resolve the problem

eaglebox
Posts: 2
Joined: Thu Dec 22, 2016 8:50 am

Re: Sleep Mode - and or turn off backlight?

Thu Dec 22, 2016 8:54 am

Nope, It did not!

Problem persists.

eaglebox
Posts: 2
Joined: Thu Dec 22, 2016 8:50 am

Re: Sleep Mode - and or turn off backlight?

Thu Dec 22, 2016 12:30 pm

I did a repeated apt-get update && apt-get upgrade and it looks ok for now! :D

Don't know why the update/upgrade earlier this morning did not solve the problem.

marmachine
Posts: 16
Joined: Wed Oct 12, 2016 6:58 pm

Re: Sleep Mode - and or turn off backlight?

Mon Jan 23, 2017 11:02 am

Hi Folks,

I came here looking for a solution to my trouble with my original 7" touchscreen attached to my RPi3... actually having same kind of trouble as you guys. However, since it's 2017... maybe there is a fix by now?
I use my RPi as a remote for my Domoticz system, so with a browser in kiosk mode and put the display to blank after 30 mins.
Most of the time it works fine, right when i touch it, it comes back on.

But, occasionally it doesn't; it will then show a white / cloudy background though, but nothing other than that.
Pi is then still accessible through SSH, so it seems not related to the system, but only to the display driver in my oppinion.
There is not really a pattern for this to happen, just random, but mostly not more than once per day.
Pulling the power plug (restarting) always does the trick... but doesn't solve the issue.
I have tried a second power adapter for pi and display seperately, that doesn't help.
I'm using the original 2,5A power supply now.

Any ideas?

Update: I installed NOOBS_v2.1.0 and my trouble has gone... (i was on v1.9.2 before)
Last edited by marmachine on Thu Jan 26, 2017 12:05 pm, edited 1 time in total.

boourns
Posts: 2
Joined: Sun Jan 22, 2017 4:28 am

Re: Sleep Mode - and or turn off backlight?

Tue Jan 24, 2017 9:12 pm

Edit: Sorry, nothing to see here... apparently something I was trying before had things messed up and the screen was just blanking instead of turning the backlight off after 10 min of inactivity. After looking at some other threads it seemed that the current behavior should have the backlight going off instead, so I reset some things and it is behaving that way now... excuse my noobness :D

vvvvvvvvvvvv ***Original Message of Confusion and Ignorance*** vvvvvvvvvvvvvvvvvvv
Just looking for clarification on one point when turning the backlight off. In some earlier comments in this thread ppl mentioned using the touchscreen to 'wake' it back up (i.e. turn the screen back on).
Am I correct in assuming you need to write a script to detect touch input, or keyboard/mouse input, and then issue the command to turn the back light back on?
If so, could someone point me in the right direction for detecting touchscreen input in python? (I'm definitely a noob)

Currently I've only tested the functionality using the following commands via ssh, which works fine:

Code: Select all

sudo bash -c "echo 1 > /sys/class/backlight/rpi_backlight/bl_power"
sudo bash -c "echo 0 > /sys/class/backlight/rpi_backlight/bl_power"
Thanks!

Smudgey
Posts: 7
Joined: Mon Jan 09, 2017 10:40 pm

Re: Sleep Mode - and or turn off backlight?

Fri Mar 31, 2017 3:28 pm

Has a fix been sorted for this problem? I have updated my Pi3 as described a week ago (March 2017) but my pi sometimes won't turn off the screen and sometimes won't turn it back on again. I am running a python home automation program, so not being able to see the screen is unacceptable.

marmachine
Posts: 16
Joined: Wed Oct 12, 2016 6:58 pm

Re: Sleep Mode - and or turn off backlight?

Fri Mar 31, 2017 6:06 pm

Smudgey wrote:Has a fix been sorted for this problem?
I've installed NOOBS_v2.1.0 and my trouble has gone... (i was on v1.9.2 before)

I'm using my Pi3 to display a pannel of Domoticz (home automation). I've connected a motionsensor to the GPIO pins to turn on the display and turn it off after some time of no motion. Works perfectly for me

Mirisbowring
Posts: 1
Joined: Sun Apr 02, 2017 2:53 pm

Re: Sleep Mode - and or turn off backlight?

Sun Apr 02, 2017 3:04 pm

I am using the latest raspbian and have an comparable problem...
After 20-30 minutes, the display turns off (official 7")... When I touch it, it turns on...

But I want to use this as a Status screen and coded a javafx application which is running great.

But after 20-30 minutes not using it, the display turns off, and I have noch Chance to reactivate the pi (neither a keyboard or mouse is working)...

Is there a fix?


MY PLAN:
The backlight has to turn off after 15 minutes (programmatically) but not the touch input.
I want to "wake" the screen up by touching it (it will be mounted into a wall)...

marmachine
Posts: 16
Joined: Wed Oct 12, 2016 6:58 pm

Re: Sleep Mode - and or turn off backlight?

Sun Apr 02, 2017 7:56 pm

Mirisbowring wrote:I am using the latest raspbian and have an comparable problem...
After 20-30 minutes, the display turns off (official 7")... When I touch it, it turns on...

But I want to use this as a Status screen and coded a javafx application which is running great.

But after 20-30 minutes not using it, the display turns off, and I have noch Chance to reactivate the pi (neither a keyboard or mouse is working)...

Is there a fix?


MY PLAN:
The backlight has to turn off after 15 minutes (programmatically) but not the touch input.
I want to "wake" the screen up by touching it (it will be mounted into a wall)...
I don't know about a fix, as i mentioned the NOOBS worked for me.

Regarding your plan though... i'm using an official 7" display together with the Pi3 in a desktop cage.
When the backlight is turned of, it wakes up as soon as you touch it, but depending where you touch it you might trigger something without knowing (cos you couldn't see). I have a simple motionsensor connected to the GPIO pins together with some code that will turn on the screen before i can even touch it. I use it with Domoticz, i've created a customized panel with status, temperatures, switches etc.

marmachine
Posts: 16
Joined: Wed Oct 12, 2016 6:58 pm

Re: Sleep Mode - and or turn off backlight?

Sun Apr 16, 2017 7:32 pm

Found this thread, might be what you need when you want to keep your screen on!?

OR

Install xscreensaver, in the gui you will now have (and can edit settings) the "screensaver" option under preferences. Read more here
sudo apt-get install xscreensaver

Smudgey
Posts: 7
Joined: Mon Jan 09, 2017 10:40 pm

Re: Sleep Mode - and or turn off backlight?

Sat May 06, 2017 1:06 pm

Thanks Marmachine getting the latest noobs worked. The screen goes blank and wakes up every time now. Except sometimes if I use VNC viewer on my iPad to control the Pi the screen stays on permanently even when I have logged off VNC viewer. The Pi has to be rebooted to get it turning off the screen again.

dddufte
Posts: 1
Joined: Wed Sep 13, 2017 7:21 am

Re: Sleep Mode - and or turn off backlight?

Wed Sep 13, 2017 11:14 am

I do run raspbian on a PI2 with an 7" touchscreen display.

Using (via crontab)

Code: Select all

echo 0 > /sys/class/backlight/rpi_backlight/bl_power
echo 1 > /sys/class/backlight/rpi_backlight/bl_power
worked for me with Rasbian (Debian Jessie) but since i did a system upgrade to Debian Stretch the behaviour has changed.

It still seems to work to disable the display via

Code: Select all

echo 1 > /sys/class/backlight/rpi_backlight/bl_power
but enabling the display via

Code: Select all

echo 0 > /sys/class/backlight/rpi_backlight/bl_power
for sure doesn't work anymore on my setup.

I did read this thread, but haven't seen any solution to this problem. The debian system is up-to-date - so simply running apt update && apt-upgrade is no solution at the current point.

I'm open for any input.


UPDATE:
I was wrong, in general both commands seems to work , but not waking up is not reproduceable for me. If i toggle off / on via cron in a short timeframe it tends to work. If the time between off and on is longer it (on) tends to not work.

martinmolema
Posts: 10
Joined: Sun Jan 04, 2015 3:54 pm

Re: Sleep Mode - and or turn off backlight?

Tue Dec 26, 2017 8:37 pm

I was reading this topic for a complete different purpose, but maybe I can add something. I am currently building the MagicMirror. To avoid the display being on continuously, I wanted to put the display into sleep mode. There is a command TVSERVICE, but this was not working for me.

However, when using an HDMI monitor (perhaps your display is one too?) you can use the command

Code: Select all

vcgencmd display_power 0
to turn of the complete power on the HDMI. Easy to switch it back on again with

Code: Select all

vcgencmd display_power 1
. The command can also be used to get the status by not adding the 0 or 1 as the last parameter.

Enjoy!

Martin

sbsm2010
Posts: 1
Joined: Wed Feb 14, 2018 11:12 am

Re: Sleep Mode - and or turn off backlight?

Mon Feb 19, 2018 2:05 pm

Turn of a raspberry pi touchscreen after a timeout of no touches

https://github.com/timothyhollabaugh/pi ... en-timeout

pi-touchscreen-timeout
Leaving the backlight on the Official Raspberry Pi touchscreen can quickly wear it out. If you have a use that requires the pi to be on all the time, but does not require the display on all the time, then turning off the backlight while not in use can dramatically increase the life of the backlight.

pi-touchscreen-timeout will transparently turn off the display backlight after there have been no touches fo a specifed timeout, independent of anything using the display at the moment. It will then turn the touchscreen back on when it is touched.

Note: This does not stop the touch event from getting to whatever is running on the display. Whatever is running will still recive a touch event, even if the display is off

The default timeout is ten seconds. It is defined in the top of timeout.c if you want to change it.

It uses the linux event device /dev/input/event0 to recive events from the touchscreen, and /sys/class/backlight/rpi-backlight/bl_power to turn the backlight on and off

Return to “Beginners”