cpfeil
Posts: 15
Joined: Wed Dec 25, 2013 1:35 pm

Re: Sleep Mode - and or turn off backlight?

Sat Oct 24, 2015 8:42 pm

Hi,

Thank you guys!

echo 1 > /sys/class/backlight/rpi_backlight/bl_power

Works great for me. Fantastic feature.
I will try it with a PIR and Running my Pi 24/7.

Best regards,
Christian

JimmyN
Posts: 1109
Joined: Wed Mar 18, 2015 7:05 pm
Location: Virginia, USA

Re: Sleep Mode - and or turn off backlight?

Sun Oct 25, 2015 2:20 am

What's happening?

Andrew
It's working fine for me, what do you get with

Code: Select all

uname -a
 Linux rpi2 4.1.11+ #822 PREEMPT Fri Oct 23 16:14:56 BST 2015 armv6l GNU/Linux
As noted before there's no brightness control yet, but you can turn it on and off. The best feature is that now when the screen blanks it turns the display off as well, good job!!.

JimmyN
Posts: 1109
Joined: Wed Mar 18, 2015 7:05 pm
Location: Virginia, USA

Re: Sleep Mode - and or turn off backlight?

Sun Oct 25, 2015 12:32 pm

I have discovered a problem with the screen blanking and not coming back if it's been inactive for quite a while. Using it off and on all day works OK, but I found that if left overnight it won't come out of "power off/blank" mode the next morning.

Friday night I left it running and when I went to use it Saturday morning a screen touch wouldn't wake it up. So I plugged a keyboard in, still nothing. Plugged a mouse in, still nothing. I didn't want to just pull the power so I used Putty to SSH in and see if it was still running or locked up. SSH connection worked and I used a "top" command and it was obviously still running and nothing looked unusual, then I touched the screen and it came up and worked normally. :shock:

Not knowing if that was a "stuff happens occasionally" event or an actual problem I decided to set up a test. So last night I plugged a keyboard and mouse in so they would already be in place, and I left a Putty session running on a PC and connected. This morning it was again blank and touching the screen, using the keyboard or the mouse wouldn't wake it up. I used Putty and just did an 'ls" command, then reached over and touched the screen and it came up. I'm starting to detect a pattern....

Does anybody have any idea what the problem might be? This is going to be hard to test, due to the long wait. Adding to that is the fact that since the screen is blank you have to SSH in to do anything, and it seems that any command you use at that point and the problem clears up. I know it's OK for at least a couple hours, but shows up overnight, so I don't know how long it actually needs to sit for the issue to occur.

I think I currently have the latest and greatest and everything is up to date.

Code: Select all

Linux rpi2 4.1.11+ #822 PREEMPT Fri Oct 23 16:14:56 BST 2015 armv6l GNU/Linux

JimmyN
Posts: 1109
Joined: Wed Mar 18, 2015 7:05 pm
Location: Virginia, USA

Re: Sleep Mode - and or turn off backlight?

Sun Oct 25, 2015 2:17 pm

I went away and left it after my last post, about an hour and a half. But this time nothing seemed to bring it back and I had to reboot. So it seems the SSH connection and issuing a command doesn't necessarily work, and it was just a coincidence that it worked yesterday morning and this morning. Over the last two days I've left it for that long before and didn't have any problem waking it up, but today it's being a problem.
I guess I'll just have to see if I can turn off the screen blanking, at least for now, so I don't have to SSH in and reboot each time I'm away for a while.

barrybpl
Posts: 14
Joined: Mon Feb 09, 2015 9:56 pm

Re: Sleep Mode - and or turn off backlight?

Mon Oct 26, 2015 8:33 am

Having just read the last post the same is happening here.

I can ssh to the pi fine and everything is working normally but I cant get the backlight to come back on.

The touchscreen is still working because I can run a kivy ui and can tell that it's accepting the touch inputs (presssing where I know the buttons are, still can't see anything).

Tried;

Code: Select all

[email protected]:~# echo 0 > /sys/class/backlight/rpi_backlight/bl_power
[email protected]:~# echo 1 > /sys/class/backlight/rpi_backlight/bl_power
and still nothing.

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

Re: Sleep Mode - and or turn off backlight?

Mon Oct 26, 2015 10:13 am

For people with unresponsive backlights, can you answer these questions:

1) Does a power cycle always fix the problem?
2) What modifications, if any, have been made to stock Raspbian Jessie?
3) How long, on average, does it take for the display to stop registering backlight commands?

With the touchscreen still delivering inputs it seems like the Atmel is still alive...
Rockets are loud.
https://astro-pi.org

JimmyN
Posts: 1109
Joined: Wed Mar 18, 2015 7:05 pm
Location: Virginia, USA

Re: Sleep Mode - and or turn off backlight?

Mon Oct 26, 2015 11:33 am

1) Yes a reboot or complete power cycle always fixes it.

2) Stock Jessie install, downloaded it Friday. Installation of Kivy is the only change. It doesn't happen when I'm playing with Kivy of course, since it's active. I haven't tried leaving Kivy running, but "idle" so the screen will blank to see what happens.

3) Since I posted yesterday morning I've just left it sitting idle and check it periodically. I found that it varies, and I also discovered it starts working again if I wait. It may sit for an hour or two and when I check it there is no response, screen stays blank. Come back an hour or so later, touch the screen and everything is fine. I left it on overnight and when I touched the screen this morning it came up after sitting all night. So the time seems to vary, and it will start working again without having to reboot if I wait a while.

EDIT: It worked first thing this morning after sitting all night, but it's been sitting blank for about an hour and a half and now there is no response. But if I wait a while it will start working again.

EDIT2: At 7:30am (my last edit) it wasn't working, now at 8:45am it's working again.

User avatar
elParaguayo
Posts: 1943
Joined: Wed May 16, 2012 12:46 pm
Location: London, UK

Re: Sleep Mode - and or turn off backlight?

Mon Oct 26, 2015 1:08 pm

For what it's worth - one of my Pis will be running a Kivy app 24/7. I plan to disable the backlight after a period of inactivity (I'd prefer to dim, but off will be fine for now).

I'm therefore happy to download the new image and try this out and report back.
RPi Information Screen: plugin based system for displaying weather, travel information, football scores etc.

joemensor
Posts: 8
Joined: Fri Oct 02, 2015 10:42 am

Re: Sleep Mode - and or turn off backlight?

Mon Oct 26, 2015 1:11 pm

JimmyN wrote:I went away and left it after my last post, about an hour and a half. But this time nothing seemed to bring it back and I had to reboot. So it seems the SSH connection and issuing a command doesn't necessarily work, and it was just a coincidence that it worked yesterday morning and this morning. Over the last two days I've left it for that long before and didn't have any problem waking it up, but today it's being a problem.
I guess I'll just have to see if I can turn off the screen blanking, at least for now, so I don't have to SSH in and reboot each time I'm away for a while.
I have managed to 'fix' the crashing I was getting by seemingly by running an 'apt-get update', so that's good. But I am also seeing these problems with the display not coming back on after a long period of time, then miraculously without a reboot some time later it will start 'working' again. Weird.

joemensor
Posts: 8
Joined: Fri Oct 02, 2015 10:42 am

Re: Sleep Mode - and or turn off backlight?

Mon Oct 26, 2015 1:18 pm

For info, when I run uname -a, I get the following:

Linux raspberrypi 4.1.11-v7+ #822 SMP PREEMPT Fri Oct 23 16:22:18 BST 2015 armv7l GNU/Linux

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

Re: Sleep Mode - and or turn off backlight?

Mon Oct 26, 2015 2:09 pm

In the case where the backlight is off and keypresses/touch events don't wake up the backlight, can you post the full output of dmesg here?
Rockets are loud.
https://astro-pi.org

barrybpl
Posts: 14
Joined: Mon Feb 09, 2015 9:56 pm

Re: Sleep Mode - and or turn off backlight?

Mon Oct 26, 2015 2:38 pm

I just left my pi with the screen not working after my post earlier and having just come back to it it's working perfectly again.

It was responding at the time, but here's the full dmesg output including the time it wasn't working.

Code: Select all

[email protected] ~/rpi-kivy-screen $ dmesg
[    0.000000] Booting Linux on physical CPU 0xf00
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Initializing cgroup subsys cpuacct
[    0.000000] Linux version 4.1.11-v7+ ([email protected]) (gcc version 4.8.3 20140303 (prerelease) (crosstool-NG linaro-1.13.1+bzr2650 - Linaro GCC 2014.03) ) #822 SMP PREEMPT Fri Oct 23 16:22:18 BST 2015
[    0.000000] CPU: ARMv7 Processor [410fc075] revision 5 (ARMv7), cr=10c5387d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] Machine model: Raspberry Pi 2 Model B Rev 1.1
[    0.000000] cma: Reserved 8 MiB at 0x2e800000
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] On node 0 totalpages: 192512
[    0.000000] free_area_init_node: node 0, pgdat 80859000, node_mem_map ae156000
[    0.000000]   Normal zone: 1692 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 192512 pages, LIFO batch:31
[    0.000000] [bcm2709_smp_init_cpus] enter (9420->f3003010)
[    0.000000] [bcm2709_smp_init_cpus] ncores=4
[    0.000000] PERCPU: Embedded 13 pages/cpu @ae114000 s20608 r8192 d24448 u53248
[    0.000000] pcpu-alloc: s20608 r8192 d24448 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: 190820
[    0.000000] Kernel command line: dma.dmachans=0x7f35 bcm2708_fb.fbwidth=800 bcm2708_fb.fbheight=480 bcm2709.boardrev=0xa01041 bcm2709.serial=0x7d4fa5de smsc95xx.macaddr=B8:27:EB:4F:A5:DE bcm2708_fb.fbswap=1 bcm2709.disk_led_gpio=47 bcm2709.disk_led_active_low=0 sdhci-bcm2708.emmc_clock_freq=250000000 vc_mem.mem_base=0x3dc00000 vc_mem.mem_size=0x3f000000  dwc_otg.lpm_enable=0 console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline fsck.repair=yes 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: 744640K/770048K available (5955K kernel code, 534K rwdata, 1644K rodata, 416K init, 757K bss, 17216K reserved, 8192K cma-reserved)
[    0.000000] Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
    vmalloc : 0xaf800000 - 0xff000000   (1272 MB)
    lowmem  : 0x80000000 - 0xaf000000   ( 752 MB)
    modules : 0x7f000000 - 0x80000000   (  16 MB)
      .text : 0x80008000 - 0x80773e88   (7600 kB)
      .init : 0x80774000 - 0x807dc000   ( 416 kB)
      .data : 0x807dc000 - 0x80861b6c   ( 535 kB)
       .bss : 0x80864000 - 0x8092179c   ( 758 kB)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[    0.000000] Preemptible hierarchical RCU implementation.
[    0.000000] 	Additional per-CPU info printed with stalls.
[    0.000000] NR_IRQS:608
[    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.000012] sched_clock: 56 bits at 19MHz, resolution 52ns, wraps every 4398046511078ns
[    0.000033] Switching to timer-based delay loop, resolution 52ns
[    0.000327] Console: colour dummy device 80x30
[    0.002098] console [tty1] enabled
[    0.002163] Calibrating delay loop (skipped), value calculated using timer frequency.. 38.40 BogoMIPS (lpj=192000)
[    0.002263] pid_max: default: 32768 minimum: 301
[    0.002638] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.002706] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.004040] Initializing cgroup subsys blkio
[    0.004123] Initializing cgroup subsys memory
[    0.004194] Initializing cgroup subsys devices
[    0.004256] Initializing cgroup subsys freezer
[    0.004331] Initializing cgroup subsys net_cls
[    0.004443] CPU: Testing write buffer coherency: ok
[    0.004565] ftrace: allocating 20224 entries in 60 pages
[    0.054143] CPU0: update cpu_capacity 1024
[    0.054232] CPU0: thread -1, cpu 0, socket 15, mpidr 80000f00
[    0.054279] [bcm2709_smp_prepare_cpus] enter
[    0.054443] Setting up static identity map for 0x8240 - 0x8274
[    0.114022] [bcm2709_boot_secondary] cpu:1 started (0) 18
[    0.114458] [bcm2709_secondary_init] enter cpu:1
[    0.114513] CPU1: update cpu_capacity 1024
[    0.114521] CPU1: thread -1, cpu 1, socket 15, mpidr 80000f01
[    0.133999] [bcm2709_boot_secondary] cpu:2 started (0) 17
[    0.134365] [bcm2709_secondary_init] enter cpu:2
[    0.134397] CPU2: update cpu_capacity 1024
[    0.134406] CPU2: thread -1, cpu 2, socket 15, mpidr 80000f02
[    0.154042] [bcm2709_boot_secondary] cpu:3 started (0) 18
[    0.154300] [bcm2709_secondary_init] enter cpu:3
[    0.154328] CPU3: update cpu_capacity 1024
[    0.154336] CPU3: thread -1, cpu 3, socket 15, mpidr 80000f03
[    0.154429] Brought up 4 CPUs
[    0.154564] SMP: Total of 4 processors activated (153.60 BogoMIPS).
[    0.154605] CPU: All CPU(s) started in HYP mode.
[    0.154641] CPU: Virtualization extensions available.
[    0.155684] devtmpfs: initialized
[    0.180245] VFP support v0.3: implementor 41 architecture 2 part 30 variant 7 rev 5
[    0.180612] clocksource jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.181770] pinctrl core: initialized pinctrl subsystem
[    0.182609] NET: Registered protocol family 16
[    0.188417] DMA: preallocated 4096 KiB pool for atomic coherent allocations
[    0.189687] bcm2709.uart_clock = 3000000
[    0.195296] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.
[    0.195370] hw-breakpoint: maximum watchpoint size is 8 bytes.
[    0.195591] Serial: AMBA PL011 UART driver
[    0.195843] 3f201000.uart: ttyAMA0 at MMIO 0x3f201000 (irq = 83, base_baud = 0) is a PL011 rev2
[    0.702395] console [ttyAMA0] enabled
[    0.706673] bcm2835-mbox 3f00b880.mailbox: mailbox enabled
[    0.786545] bcm2708-dmaengine 3f007000.dma: DMA legacy API manager at f3007000, dmachans=0xf35
[    0.795308] bcm2708-dmaengine 3f007000.dma: Initialized 7 DMA channels (+ 1 legacy)
[    0.803725] bcm2708-dmaengine 3f007000.dma: Load BCM2835 DMA engine driver
[    0.810653] bcm2708-dmaengine 3f007000.dma: dma_debug:0
[    0.816636] SCSI subsystem initialized
[    0.820680] usbcore: registered new interface driver usbfs
[    0.826291] usbcore: registered new interface driver hub
[    0.831786] usbcore: registered new device driver usb
[    0.837580] raspberrypi-firmware soc:firmware: Attached to firmware from 2015-10-23 16:24
[    0.873147] Switched to clocksource arch_sys_counter
[    0.927889] FS-Cache: Loaded
[    0.931185] CacheFiles: Loaded
[    0.945994] NET: Registered protocol family 2
[    0.951675] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[    0.958943] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
[    0.965681] TCP: Hash tables configured (established 8192 bind 8192)
[    0.972215] UDP hash table entries: 512 (order: 2, 16384 bytes)
[    0.978254] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[    0.985090] NET: Registered protocol family 1
[    0.990038] RPC: Registered named UNIX socket transport module.
[    0.996037] RPC: Registered udp transport module.
[    1.000763] RPC: Registered tcp transport module.
[    1.005535] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    1.013280] hw perfevents: enabled with armv7_cortex_a7 PMU driver, 5 counters available
[    1.022828] futex hash table entries: 1024 (order: 4, 65536 bytes)
[    1.044965] VFS: Disk quotas dquot_6.6.0
[    1.049302] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    1.058886] FS-Cache: Netfs 'nfs' registered for caching
[    1.065451] NFS: Registering the id_resolver key type
[    1.070592] Key type id_resolver registered
[    1.074832] Key type id_legacy registered
[    1.081696] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
[    1.089424] io scheduler noop registered
[    1.093422] io scheduler deadline registered (default)
[    1.098896] io scheduler cfq registered
[    1.105408] BCM2708FB: allocated DMA memory eec00000
[    1.110437] BCM2708FB: allocated DMA channel 0 @ f3007000
[    1.123286] Console: switching to colour frame buffer device 100x30
[    1.136209] Serial: 8250/16550 driver, 0 ports, IRQ sharing disabled
[    1.145918] vc-cma: Videocore CMA driver
[    1.151790] vc-cma: vc_cma_base      = 0x00000000
[    1.158433] vc-cma: vc_cma_size      = 0x00000000 (0 MiB)
[    1.165737] vc-cma: vc_cma_initial   = 0x00000000 (0 MiB)
[    1.173270] vc-mem: phys_addr:0x00000000 mem_base=0x3dc00000 mem_size:0x3f000000(1008 MiB)
[    1.199379] brd: module loaded
[    1.213564] loop: module loaded
[    1.219679] vchiq: vchiq_init_state: slot_zero = 0xaec80000, is_master = 0
[    1.230452] Loading iSCSI transport class v2.0-870.
[    1.238273] usbcore: registered new interface driver smsc95xx
[    1.246062] dwc_otg: version 3.00a 10-AUG-2012 (platform bus)
[    1.454118] Core Release: 2.80a
[    1.459118] Setting default values for core params
[    1.465840] Finished setting default values for core params
[    1.673715] Using Buffer DMA mode
[    1.678914] Periodic Transfer Interrupt Enhancement - disabled
[    1.686661] Multiprocessor Interrupt Enhancement - disabled
[    1.694113] OTG VER PARAM: 0, OTG VER FLAG: 0
[    1.700322] Dedicated Tx FIFOs mode
[    1.706019] WARN::dwc_otg_hcd_init:1047: FIQ DMA bounce buffers: virt = 0xaec14000 dma = 0xeec14000 len=9024
[    1.719900] FIQ FSM acceleration enabled for :
Non-periodic Split Transactions
Periodic Split Transactions
High-Speed Isochronous Endpoints
[    1.744506] dwc_otg: Microframe scheduler enabled
[    1.744605] WARN::hcd_init_fiq:412: FIQ on core 1 at 0x80400a40
[    1.752510] WARN::hcd_init_fiq:413: FIQ ASM at 0x80400d9c length 36
[    1.760784] WARN::hcd_init_fiq:438: MPHI regs_base at 0xaf89a000
[    1.768856] dwc_otg 3f980000.usb: DWC OTG Controller
[    1.775879] dwc_otg 3f980000.usb: new USB bus registered, assigned bus number 1
[    1.785233] dwc_otg 3f980000.usb: irq 32, io mem 0x00000000
[    1.792834] Init: Port Power? op_state=1
[    1.798723] Init: Power Port (0)
[    1.804145] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    1.812892] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.822090] usb usb1: Product: DWC OTG Controller
[    1.828740] usb usb1: Manufacturer: Linux 4.1.11-v7+ dwc_otg_hcd
[    1.836718] usb usb1: SerialNumber: 3f980000.usb
[    1.844188] hub 1-0:1.0: USB hub found
[    1.849885] hub 1-0:1.0: 1 port detected
[    1.856238] dwc_otg: FIQ enabled
[    1.856252] dwc_otg: NAK holdoff enabled
[    1.856263] dwc_otg: FIQ split-transaction FSM enabled
[    1.856302] Module dwc_common_port init
[    1.856683] usbcore: registered new interface driver usb-storage
[    1.864911] mousedev: PS/2 mouse device common for all mice
[    1.873301] bcm2835-cpufreq: min=600000 max=900000
[    1.880334] sdhci: Secure Digital Host Controller Interface driver
[    1.888405] sdhci: Copyright(c) Pierre Ossman
[    1.895030] mmc-bcm2835 3f300000.mmc: mmc_debug:0 mmc_debug2:0
[    1.902669] mmc-bcm2835 3f300000.mmc: DMA channels allocated
[    1.943538] sdhci-pltfm: SDHCI platform and OF driver helper
[    1.953675] ledtrig-cpu: registered to indicate activity on CPUs
[    1.961776] hidraw: raw HID events driver (C) Jiri Kosina
[    1.969298] usbcore: registered new interface driver usbhid
[    1.976776] usbhid: USB HID core driver
[    1.982790] Initializing XFRM netlink socket
[    1.988967] NET: Registered protocol family 17
[    1.990938] mmc0: host does not support reading read-only switch, assuming write-enable
[    1.993079] mmc0: new high speed SDHC card at address 59b4
[    1.993743] mmcblk0: mmc0:59b4 00000 14.9 GiB 
[    1.996474]  mmcblk0: p1 p2
[    2.023868] Key type dns_resolver registered
[    2.030491] Registering SWP/SWPB emulation handler
[    2.038125] registered taskstats version 1
[    2.044398] vc-sm: Videocore shared memory driver
[    2.050951] [vc_sm_connected_init]: start
[    2.056978] Indeed it is in host mode hprt0 = 00021501
[    2.064765] [vc_sm_connected_init]: end - returning 0
[    2.090630] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[    2.100846] VFS: Mounted root (ext4 filesystem) readonly on device 179:2.
[    2.135096] devtmpfs: mounted
[    2.140751] Freeing unused kernel memory: 416K (80774000 - 807dc000)
[    2.243234] usb 1-1: new high-speed USB device number 2 using dwc_otg
[    2.252992] Indeed it is in host mode hprt0 = 00001101
[    2.453599] usb 1-1: New USB device found, idVendor=0424, idProduct=9514
[    2.462459] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    2.473040] hub 1-1:1.0: USB hub found
[    2.479325] hub 1-1:1.0: 5 ports detected
[    2.558820] random: systemd urandom read with 52 bits of entropy available
[    2.573313] systemd[1]: systemd 215 running in system mode. (+PAM +AUDIT +SELINUX +IMA +SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ -SECCOMP -APPARMOR)
[    2.591999] systemd[1]: Detected architecture 'arm'.
[    2.740972] NET: Registered protocol family 10
[    2.749475] systemd[1]: Inserted module 'ipv6'
[    2.763226] usb 1-1.1: new high-speed USB device number 3 using dwc_otg
[    2.774365] systemd[1]: Set hostname to <twelfthpi>.
[    2.861466] uart-pl011 3f201000.uart: no DMA platform data
[    2.893692] usb 1-1.1: New USB device found, idVendor=0424, idProduct=ec00
[    2.902897] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    2.915410] smsc95xx v1.0.4
[    2.977372] smsc95xx 1-1.1:1.0 eth0: register 'smsc95xx' at usb-3f980000.usb-1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:4f:a5:de
[    3.243194] usb 1-1.3: new full-speed USB device number 4 using dwc_otg
[    3.368140] usb 1-1.3: New USB device found, idVendor=05a4, idProduct=1700
[    3.377370] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    3.386977] usb 1-1.3: Product: W/L Keyboard/Mouse
[    3.394016] usb 1-1.3: Manufacturer: ORTEK
[    4.647347] systemd[1]: Starting Forward Password Requests to Wall Directory Watch.
[    4.657915] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[    4.667984] systemd[1]: Expecting device dev-ttyAMA0.device...
[    4.679091] systemd[1]: Starting Remote File Systems (Pre).
[    4.689647] systemd[1]: Reached target Remote File Systems (Pre).
[    4.698226] systemd[1]: Starting Arbitrary Executable File Formats File System Automount Point.
[    4.712790] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
[    4.727198] systemd[1]: Starting Encrypted Volumes.
[    4.737625] systemd[1]: Reached target Encrypted Volumes.
[    4.745591] systemd[1]: Starting Swap.
[    4.754622] systemd[1]: Reached target Swap.
[    4.761324] systemd[1]: Expecting device dev-mmcblk0p1.device...
[    4.772408] systemd[1]: Starting Root Slice.
[    4.781723] systemd[1]: Created slice Root Slice.
[    4.788759] systemd[1]: Starting User and Session Slice.
[    4.799271] systemd[1]: Created slice User and Session Slice.
[    4.807343] systemd[1]: Starting /dev/initctl Compatibility Named Pipe.
[    4.819212] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
[    4.828552] systemd[1]: Starting Delayed Shutdown Socket.
[    4.839077] systemd[1]: Listening on Delayed Shutdown Socket.
[    4.847174] systemd[1]: Starting Journal Socket (/dev/log).
[    4.857768] systemd[1]: Listening on Journal Socket (/dev/log).
[    4.865935] systemd[1]: Starting udev Control Socket.
[    4.875675] systemd[1]: Listening on udev Control Socket.
[    4.883240] systemd[1]: Starting udev Kernel Socket.
[    4.892779] systemd[1]: Listening on udev Kernel Socket.
[    4.900285] systemd[1]: Starting Journal Socket.
[    4.909712] systemd[1]: Listening on Journal Socket.
[    4.916904] systemd[1]: Starting System Slice.
[    4.926217] systemd[1]: Created slice System Slice.
[    4.933317] systemd[1]: Starting File System Check on Root Device...
[    4.947668] systemd[1]: Starting system-systemd\x2dfsck.slice.
[    4.959225] systemd[1]: Created slice system-systemd\x2dfsck.slice.
[    4.967858] systemd[1]: Starting system-getty.slice.
[    4.978221] systemd[1]: Created slice system-getty.slice.
[    4.985972] systemd[1]: Starting system-serial\x2dgetty.slice.
[    4.997425] systemd[1]: Created slice system-serial\x2dgetty.slice.
[    5.006159] systemd[1]: Starting Increase datagram queue length...
[    5.020585] systemd[1]: Starting Restore / save the current clock...
[    5.040951] systemd[1]: Mounting POSIX Message Queue File System...
[    5.057368] systemd[1]: Mounted Huge Pages File System.
[    5.066239] systemd[1]: Mounting Debug File System...
[    5.105990] systemd[1]: Started Set Up Additional Binary Formats.
[    5.147388] systemd[1]: Starting Load Kernel Modules...
[    5.164141] systemd[1]: Starting udev Coldplug all Devices...
[    5.180751] systemd[1]: Starting Create list of required static device nodes for the current kernel...
[    5.202451] systemd[1]: Starting Slices.
[    5.212248] systemd[1]: Reached target Slices.
[    5.227001] systemd[1]: Mounted Debug File System.
[    5.238990] systemd[1]: Mounted POSIX Message Queue File System.
[    5.254096] systemd[1]: Started Increase datagram queue length.
[    5.288002] fuse init (API version 7.23)
[    5.298185] systemd[1]: Started Restore / save the current clock.
[    5.317068] systemd[1]: Started Create list of required static device nodes for the current kernel.
[    5.348210] systemd[1]: Time has been changed
[    5.370053] i2c /dev entries driver
[    5.386142] systemd[1]: Started Load Kernel Modules.
[    5.399075] systemd[1]: Started udev Coldplug all Devices.
[    5.556193] systemd[1]: Started File System Check on Root Device.
[    5.576613] systemd[1]: Starting Apply Kernel Variables...
[    5.591346] systemd[1]: Mounting Configuration File System...
[    5.606531] systemd[1]: Mounting FUSE Control File System...
[    5.622834] systemd[1]: Starting Create Static Device Nodes in /dev...
[    5.630640] systemd[1]: Starting Syslog Socket.
[    5.634552] systemd[1]: Listening on Syslog Socket.
[    5.634978] systemd[1]: Starting Journal Service...
[    5.646125] systemd[1]: Started Journal Service.
[    5.842889] systemd-udevd[110]: starting version 215
[    6.357907] rpi-ft5406 rpi_ft5406: Probing device
[    6.358512] input: FT5406 memory based driver as /devices/virtual/input/input0
[    6.370015] gpiomem-bcm2835 3f200000.gpiomem: Initialised: Registers at 0x3f200000
[    6.663456] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[    6.718192] input: ORTEK W/L Keyboard/Mouse as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3:1.0/0003:05A4:1700.0001/input/input1
[    6.773803] ortek 0003:05A4:1700.0001: input,hidraw0: USB HID v1.10 Keyboard [ORTEK W/L Keyboard/Mouse] on usb-3f980000.usb-1.3/input0
[    6.776620] input: ORTEK W/L Keyboard/Mouse as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3:1.1/0003:05A4:1700.0002/input/input2
[    6.834157] ortek 0003:05A4:1700.0002: input,hidraw1: USB HID v1.10 Mouse [ORTEK W/L Keyboard/Mouse] on usb-3f980000.usb-1.3/input1
[    6.917117] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
[    6.917879] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[    7.397347] systemd-journald[108]: Received request to flush runtime journal from PID 1
[    7.575105] random: nonblocking pool is initialized
[    8.512584] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[    8.513629] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[    8.829750] cfg80211: Calling CRDA to update world regulatory domain
[    8.971162] Adding 102396k swap on /var/swap.  Priority:-1 extents:5 across:573436k SSFS
[   11.983189] cfg80211: Calling CRDA to update world regulatory domain
[   15.143308] cfg80211: Calling CRDA to update world regulatory domain
[   18.303215] cfg80211: Calling CRDA to update world regulatory domain
[   21.463201] cfg80211: Calling CRDA to update world regulatory domain
[   24.623220] cfg80211: Calling CRDA to update world regulatory domain
[   27.783198] cfg80211: Calling CRDA to update world regulatory domain
[   30.943200] cfg80211: Calling CRDA to update world regulatory domain
[   34.103225] cfg80211: Calling CRDA to update world regulatory domain
[   37.263280] cfg80211: Calling CRDA to update world regulatory domain
[   40.423233] cfg80211: Calling CRDA to update world regulatory domain
[   43.583226] cfg80211: Exceeded CRDA call max attempts. Not calling CRDA
[216605.016674] rpi-backlight rpi_backlight: Backlight change failed
[216647.283846] rpi-backlight rpi_backlight: Backlight change failed
[216671.033852] rpi-backlight rpi_backlight: Backlight change failed
[216673.785310] rpi-backlight rpi_backlight: Backlight change failed
[216676.968648] rpi-backlight rpi_backlight: Backlight change failed
[216679.596046] rpi-backlight rpi_backlight: Backlight change failed
[216764.730965] gpiomem-bcm2835 3f200000.gpiomem: gpiomem device opened.
[216811.187847] rpi-backlight rpi_backlight: Backlight change failed
[216815.412379] rpi-backlight rpi_backlight: Backlight change failed
[217392.217475] rpi-backlight rpi_backlight: Backlight change failed
Sorry it's not helpful, but just to say, so far I've only noticed it not wake up once and I didn't reboot.
Only minor changes to stock Jessie, set new hostname, created new user and removed the pi user, set it to boot to console login prompt and installed gpm. All latest updates installed.
No idea on timings, the pi had over 2 days uptime when I noticed the screen wouldn't wake up and it was about 6 hours later I noticed it was working again but this is just when I happened to look.

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

Re: Sleep Mode - and or turn off backlight?

Mon Oct 26, 2015 5:22 pm

I've found a related issue which may be masking the legitimate backlight callback failures.

If you're not in the Xwindows environment, i.e. at the console only, the console won't unblank if the touchscreen is used. This happens independently of being able to control the backlight. This is because the touchscreen is a mouse input device - the console only responds to keypresses.

In LXDE, mouse events unblank the screen.

Even so, if you're getting callback failures then this needs further investigation. I've not seen this symptom yet - will continue testing.
Rockets are loud.
https://astro-pi.org

JimmyN
Posts: 1109
Joined: Wed Mar 18, 2015 7:05 pm
Location: Virginia, USA

Re: Sleep Mode - and or turn off backlight?

Mon Oct 26, 2015 5:51 pm

Here is the output from mine. The screen was blank and I kept checking dmesg periodically to see if anything showed up. Then when I finally touched the screen and it didn't come up I checked dmesg again and the last line had been added.

I'm not using the console, I have the desktop running all the time. I'm getting the dmesg output using Putty since I don't have a screen to start LXTerminal

Code: Select all

[    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.1.11+ ([email protected]) (gcc version 4.8.3 20140303 (prerelease) (crosstool-NG linaro-1.13.1+bzr2650 - Linaro GCC 2014.03) ) #822 PREEMPT Fri Oct 23 16:14:56 BST 2015
[    0.000000] CPU: ARMv6-compatible processor [410fb767] revision 7 (ARMv7), cr=00c5387d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
[    0.000000] Machine model: Raspberry Pi Model B Plus Rev 1.2
[    0.000000] cma: Reserved 8 MiB at 0x17800000
[    0.000000] Memory policy: Data cache writeback
[    0.000000] On node 0 totalpages: 98304
[    0.000000] free_area_init_node: node 0, pgdat c088be7c, node_mem_map d7493000
[    0.000000]   Normal zone: 864 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 98304 pages, LIFO batch:31
[    0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
[    0.000000] pcpu-alloc: [0] 0
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 97440
[    0.000000] Kernel command line: dma.dmachans=0x7f35 bcm2708_fb.fbwidth=800 bcm2708_fb.fbheight=480 bcm2708.boardrev=0x10 bcm2708.serial=0xdb4f95d6 smsc95xx.macaddr=B8:27:EB:4F:95:D6 bcm2708_fb.fbswap=1 bcm2708.disk_led_gpio=47 bcm2708.disk_led_active_low=0 sdhci-bcm2708.emmc_clock_freq=250000000 vc_mem.mem_base=0x1ec00000 vc_mem.mem_size=0x20000000  dwc_otg.lpm_enable=0 console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait
[    0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
[    0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
[    0.000000] Memory: 371544K/393216K available (6128K kernel code, 489K rwdata, 1780K rodata, 352K init, 720K bss, 13480K reserved, 8192K cma-reserved)
[    0.000000] Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
    vmalloc : 0xd8800000 - 0xff000000   ( 616 MB)
    lowmem  : 0xc0000000 - 0xd8000000   ( 384 MB)
    modules : 0xbf000000 - 0xc0000000   (  16 MB)
      .text : 0xc0008000 - 0xc07c1554   (7910 kB)
      .init : 0xc07c2000 - 0xc081a000   ( 352 kB)
      .data : 0xc081a000 - 0xc08947e4   ( 490 kB)
       .bss : 0xc08947e4 - 0xc0948980   ( 721 kB)
[    0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[    0.000000] Preemptible hierarchical RCU implementation.
[    0.000000]  Additional per-CPU info printed with stalls.
[    0.000000] NR_IRQS:522
[    0.000000] clocksource stc: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1911260446275 ns
[    0.000015] sched_clock: 32 bits at 1000kHz, resolution 1000ns, wraps every 2147483647500ns
[    0.000055] Switching to timer-based delay loop, resolution 1000ns
[    0.000338] Console: colour dummy device 80x30
[    0.001811] console [tty1] enabled
[    0.001876] Calibrating delay loop (skipped), value calculated using timer frequency.. 2.00 BogoMIPS (lpj=10000)
[    0.001979] pid_max: default: 32768 minimum: 301
[    0.002351] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.002433] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.003523] Initializing cgroup subsys blkio
[    0.003623] Initializing cgroup subsys memory
[    0.003699] Initializing cgroup subsys devices
[    0.003767] Initializing cgroup subsys freezer
[    0.003832] Initializing cgroup subsys net_cls
[    0.003956] CPU: Testing write buffer coherency: ok
[    0.004087] ftrace: allocating 19785 entries in 59 pages
[    0.110676] Setting up static identity map for 0x81c0 - 0x81f8
[    0.113471] devtmpfs: initialized
[    0.124464] VFP support v0.3: implementor 41 architecture 1 part 20 variant b rev 5
[    0.124907] clocksource jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.126903] pinctrl core: initialized pinctrl subsystem
[    0.127824] NET: Registered protocol family 16
[    0.133440] DMA: preallocated 4096 KiB pool for atomic coherent allocations
[    0.135015] bcm2708.uart_clock = 3000000
[    0.141019] hw-breakpoint: found 6 breakpoint and 1 watchpoint registers.
[    0.141113] hw-breakpoint: maximum watchpoint size is 4 bytes.
[    0.141303] Serial: AMBA PL011 UART driver
[    0.141636] 20201000.uart: ttyAMA0 at MMIO 0x20201000 (irq = 83, base_baud = 0) is a PL011 rev2
[    0.530464] console [ttyAMA0] enabled
[    0.534852] bcm2835-mbox 2000b880.mailbox: mailbox enabled
[    0.603051] bcm2708-dmaengine 20007000.dma: DMA legacy API manager at f2007000, dmachans=0xf35
[    0.611941] bcm2708-dmaengine 20007000.dma: Initialized 7 DMA channels (+ 1 legacy)
[    0.620476] bcm2708-dmaengine 20007000.dma: Load BCM2835 DMA engine driver
[    0.627475] bcm2708-dmaengine 20007000.dma: dma_debug:0
[    0.633639] SCSI subsystem initialized
[    0.637906] usbcore: registered new interface driver usbfs
[    0.643564] usbcore: registered new interface driver hub
[    0.649158] usbcore: registered new device driver usb
[    0.655191] raspberrypi-firmware soc:firmware: Attached to firmware from 2015-10-23 16:24
[    0.691040] Switched to clocksource stc
[    0.742064] FS-Cache: Loaded
[    0.745383] CacheFiles: Loaded
[    0.764736] NET: Registered protocol family 2
[    0.770640] TCP established hash table entries: 4096 (order: 2, 16384 bytes)
[    0.778100] TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
[    0.784735] TCP: Hash tables configured (established 4096 bind 4096)
[    0.791275] UDP hash table entries: 256 (order: 0, 4096 bytes)
[    0.797175] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[    0.803927] NET: Registered protocol family 1
[    0.808950] RPC: Registered named UNIX socket transport module.
[    0.815074] RPC: Registered udp transport module.
[    0.819823] RPC: Registered tcp transport module.
[    0.824606] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.832474] hw perfevents: enabled with armv6_1176 PMU driver, 3 counters available
[    0.841795] futex hash table entries: 256 (order: -1, 3072 bytes)
[    0.864279] VFS: Disk quotas dquot_6.6.0
[    0.868670] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    0.878280] FS-Cache: Netfs 'nfs' registered for caching
[    0.885378] NFS: Registering the id_resolver key type
[    0.890569] Key type id_resolver registered
[    0.894940] Key type id_legacy registered
[    0.902988] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
[    0.910918] io scheduler noop registered
[    0.915115] io scheduler deadline registered (default)
[    0.920725] io scheduler cfq registered
[    0.927265] BCM2708FB: allocated DMA memory 57c00000
[    0.932622] BCM2708FB: allocated DMA channel 0 @ f2007000
[    0.944627] Console: switching to colour frame buffer device 100x30
[    0.957427] Serial: 8250/16550 driver, 0 ports, IRQ sharing disabled
[    0.967663] vc-cma: Videocore CMA driver
[    0.973823] vc-cma: vc_cma_base      = 0x00000000
[    0.980506] vc-cma: vc_cma_size      = 0x00000000 (0 MiB)
[    0.987939] vc-cma: vc_cma_initial   = 0x00000000 (0 MiB)
[    0.995739] vc-mem: phys_addr:0x00000000 mem_base=0x1ec00000 mem_size:0x20000000(512 MiB)
[    1.026143] brd: module loaded
[    1.040706] loop: module loaded
[    1.047287] vchiq: vchiq_init_state: slot_zero = 0xd7c80000, is_master = 0
[    1.058517] Loading iSCSI transport class v2.0-870.
[    1.067073] usbcore: registered new interface driver smsc95xx
[    1.075143] dwc_otg: version 3.00a 10-AUG-2012 (platform bus)
[    1.283312] Core Release: 2.80a
[    1.288415] Setting default values for core params
[    1.295252] Finished setting default values for core params
[    1.503041] Using Buffer DMA mode
[    1.508322] Periodic Transfer Interrupt Enhancement - disabled
[    1.516137] Multiprocessor Interrupt Enhancement - disabled
[    1.523656] OTG VER PARAM: 0, OTG VER FLAG: 0
[    1.529909] Dedicated Tx FIFOs mode
[    1.535857] WARN::dwc_otg_hcd_init:1047: FIQ DMA bounce buffers: virt = 0xd7c14000 dma = 0x57c14000 len=9024
[    1.549826] FIQ FSM acceleration enabled for :
Non-periodic Split Transactions
Periodic Split Transactions
High-Speed Isochronous Endpoints
[    1.574472] dwc_otg: Microframe scheduler enabled
[    1.574603] WARN::hcd_init_fiq:412: FIQ on core 0 at 0xc04227d8
[    1.582570] WARN::hcd_init_fiq:413: FIQ ASM at 0xc0422ab0 length 36
[    1.590868] WARN::hcd_init_fiq:438: MPHI regs_base at 0xd8896000
[    1.599071] dwc_otg 20980000.usb: DWC OTG Controller
[    1.606206] dwc_otg 20980000.usb: new USB bus registered, assigned bus number 1
[    1.615688] dwc_otg 20980000.usb: irq 32, io mem 0x00000000
[    1.623401] Init: Port Power? op_state=1
[    1.629315] Init: Power Port (0)
[    1.634896] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    1.643792] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.653073] usb usb1: Product: DWC OTG Controller
[    1.659756] usb usb1: Manufacturer: Linux 4.1.11+ dwc_otg_hcd
[    1.667525] usb usb1: SerialNumber: 20980000.usb
[    1.675276] hub 1-0:1.0: USB hub found
[    1.681287] hub 1-0:1.0: 1 port detected
[    1.687806] dwc_otg: FIQ enabled
[    1.687831] dwc_otg: NAK holdoff enabled
[    1.687845] dwc_otg: FIQ split-transaction FSM enabled
[    1.687910] Module dwc_common_port init
[    1.688485] usbcore: registered new interface driver usb-storage
[    1.697126] mousedev: PS/2 mouse device common for all mice
[    1.705966] bcm2835-cpufreq: min=700000 max=1100000
[    1.713427] sdhci: Secure Digital Host Controller Interface driver
[    1.721710] sdhci: Copyright(c) Pierre Ossman
[    1.728575] mmc-bcm2835 20300000.mmc: mmc_debug:0 mmc_debug2:0
[    1.736497] mmc-bcm2835 20300000.mmc: DMA channels allocated
[    1.781701] sdhci-pltfm: SDHCI platform and OF driver helper
[    1.790094] ledtrig-cpu: registered to indicate activity on CPUs
[    1.800762] hidraw: raw HID events driver (C) Jiri Kosina
[    1.813946] usbcore: registered new interface driver usbhid
[    1.821671] usbhid: USB HID core driver
[    1.832075] Initializing XFRM netlink socket
[    1.840470] NET: Registered protocol family 17
[    1.848366] Key type dns_resolver registered
[    1.860163] registered taskstats version 1
[    1.866607] vc-sm: Videocore shared memory driver
[    1.873442] [vc_sm_connected_init]: start
[    1.880688] [vc_sm_connected_init]: end - returning 0
[    1.888089] Indeed it is in host mode hprt0 = 00021501
[    1.900927] mmc0: host does not support reading read-only switch, assuming write-enable
[    1.911454] Waiting for root device /dev/mmcblk0p2...
[    1.933433] mmc0: new high speed SDHC card at address 59b4
[    1.951644] mmcblk0: mmc0:59b4 00000 7.35 GiB
[    1.972155]  mmcblk0: p1 p2
[    2.067715] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[    2.078220] VFS: Mounted root (ext4 filesystem) readonly on device 179:2.
[    2.111158] usb 1-1: new high-speed USB device number 2 using dwc_otg
[    2.119948] Indeed it is in host mode hprt0 = 00001101
[    2.129884] devtmpfs: mounted
[    2.142176] Freeing unused kernel memory: 352K (c07c2000 - c081a000)
[    2.341873] usb 1-1: New USB device found, idVendor=0424, idProduct=9514
[    2.351832] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    2.363271] hub 1-1:1.0: USB hub found
[    2.370057] hub 1-1:1.0: 5 ports detected
[    2.602614] random: systemd urandom read with 66 bits of entropy available
[    2.618809] systemd[1]: systemd 215 running in system mode. (+PAM +AUDIT +SELINUX +IMA +SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ -SECCOMP -APPARMOR)
[    2.637511] systemd[1]: Detected architecture 'arm'.
[    2.651244] usb 1-1.1: new high-speed USB device number 3 using dwc_otg
[    2.751729] usb 1-1.1: New USB device found, idVendor=0424, idProduct=ec00
[    2.762083] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    2.776151] smsc95xx v1.0.4
[    2.853041] smsc95xx 1-1.1:1.0 eth0: register 'smsc95xx' at usb-20980000.usb-1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:4f:95:d6
[    2.886088] NET: Registered protocol family 10
[    2.895653] systemd[1]: Inserted module 'ipv6'
[    2.914720] systemd[1]: Set hostname to <rpi2>.
[    3.089711] uart-pl011 20201000.uart: no DMA platform data
[    3.131355] usb 1-1.4: new high-speed USB device number 4 using dwc_otg
[    3.263624] usb 1-1.4: New USB device found, idVendor=13fe, idProduct=5200
[    3.281247] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    3.290998] usb 1-1.4: Product: Silicon-Power32G
[    3.299875] usb 1-1.4: Manufacturer: UFD 3.0
[    3.309093] usb 1-1.4: SerialNumber: P13100510707375D01D7B006
[    3.324041] usb-storage 1-1.4:1.0: USB Mass Storage device detected
[    3.347706] scsi host0: usb-storage 1-1.4:1.0
[    4.055096] systemd[1]: Starting Forward Password Requests to Wall Directory Watch.
[    4.066348] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[    4.076773] systemd[1]: Expecting device dev-ttyAMA0.device...
[    4.088471] systemd[1]: Starting Remote File Systems (Pre).
[    4.099694] systemd[1]: Reached target Remote File Systems (Pre).
[    4.108492] systemd[1]: Starting home-jimmy-network\x2dfolder.automount.
[    4.159170] systemd[1]: Set up automount home-jimmy-network\x2dfolder.automount.
[    4.169348] systemd[1]: Starting home-jimmy-win7\x2dfolder.automount.
[    4.207959] systemd[1]: Set up automount home-jimmy-win7\x2dfolder.automount.
[    4.218106] systemd[1]: Starting Arbitrary Executable File Formats File System Automount Point.
[    4.233758] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
[    4.248397] systemd[1]: Starting Encrypted Volumes.
[    4.259292] systemd[1]: Reached target Encrypted Volumes.
[    4.267601] systemd[1]: Starting Swap.
[    4.277297] systemd[1]: Reached target Swap.
[    4.284441] systemd[1]: Expecting device dev-sda1.device...
[    4.295838] systemd[1]: Expecting device dev-mmcblk0p1.device...
[    4.307686] systemd[1]: Starting Root Slice.
[    4.317951] systemd[1]: Created slice Root Slice.
[    4.325439] systemd[1]: Starting User and Session Slice.
[    4.336983] systemd[1]: Created slice User and Session Slice.
[    4.345508] systemd[1]: Starting /dev/initctl Compatibility Named Pipe.
[    4.355736] scsi 0:0:0:0: Direct-Access     UFD 3.0  Silicon-Power32G PMAP PQ: 0 ANSI: 6
[    4.370162] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
[    4.381457] sd 0:0:0:0: [sda] 61767680 512-byte logical blocks: (31.6 GB/29.4 GiB)
[    4.392971] systemd[1]: Starting Delayed Shutdown Socket.
[    4.402561] sd 0:0:0:0: [sda] Write Protect is off
[    4.409727] sd 0:0:0:0: [sda] Mode Sense: 2b 80 00 08
[    4.413146] systemd[1]: Listening on Delayed Shutdown Socket.
[    4.421473] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[    4.435671] systemd[1]: Starting Journal Socket (/dev/log).
[    4.452023] systemd[1]: Listening on Journal Socket (/dev/log).
[    4.460789] systemd[1]: Starting udev Control Socket.
[    4.472468] systemd[1]: Listening on udev Control Socket.
[    4.480672] systemd[1]: Starting udev Kernel Socket.
[    4.492063] systemd[1]: Listening on udev Kernel Socket.
[    4.500170] systemd[1]: Starting Journal Socket.
[    4.511366] systemd[1]: Listening on Journal Socket.
[    4.519261] systemd[1]: Starting System Slice.
[    4.530119] systemd[1]: Created slice System Slice.
[    4.538076] systemd[1]: Starting File System Check on Root Device...
[    4.555708] systemd[1]: Starting system-systemd\x2dfsck.slice.
[    4.577200] systemd[1]: Created slice system-systemd\x2dfsck.slice.
[    4.588428] systemd[1]: Starting system-autologin.slice.
[    4.606648] systemd[1]: Created slice system-autologin.slice.
[    4.620457] systemd[1]: Starting system-serial\x2dgetty.slice.
[    4.638523] systemd[1]: Created slice system-serial\x2dgetty.slice.
[    4.648637] systemd[1]: Starting Increase datagram queue length...
[    4.667657]  sda: sda1
[    4.678017] systemd[1]: Starting Restore / save the current clock...
[    4.692372] sd 0:0:0:0: [sda] Attached SCSI removable disk
[    4.734576] systemd[1]: Mounting POSIX Message Queue File System...
[    4.785020] systemd[1]: Mounted Huge Pages File System.
[    4.828083] systemd[1]: Mounting Debug File System...
[    4.944610] systemd[1]: Started Set Up Additional Binary Formats.
[    5.041636] systemd[1]: Starting Load Kernel Modules...
[    5.062946] systemd[1]: Starting udev Coldplug all Devices...
[    5.096125] systemd[1]: Starting Create list of required static device nodes for the current kernel...
[    5.138402] fuse init (API version 7.23)
[    5.164777] systemd[1]: Starting Slices.
[    5.209937] systemd[1]: Reached target Slices.
[    5.240265] systemd[1]: Starting home-jimmy-Desktop-usbdrv.automount.
[    5.291022] i2c /dev entries driver
[    5.320382] systemd[1]: Set up automount home-jimmy-Desktop-usbdrv.automount.
[    5.347575] systemd[1]: Mounted Debug File System.
[    5.358427] systemd[1]: Mounted POSIX Message Queue File System.
[    5.373244] systemd[1]: Started File System Check on Root Device.
[    5.404686] systemd[1]: Started Increase datagram queue length.
[    5.419371] systemd[1]: Started Restore / save the current clock.
[    5.436573] systemd[1]: Started Load Kernel Modules.
[    5.471473] systemd[1]: Started Create list of required static device nodes for the current kernel.
[    5.510715] systemd[1]: Time has been changed
[    5.676596] systemd[1]: Started udev Coldplug all Devices.
[    5.888387] systemd[1]: Starting Create Static Device Nodes in /dev...
[    5.907426] systemd[1]: Starting Apply Kernel Variables...
[    5.944867] systemd[1]: Mounting Configuration File System...
[    6.000715] systemd[1]: Mounting FUSE Control File System...
[    6.070685] systemd[1]: Starting Syslog Socket.
[    6.104744] systemd[1]: Listening on Syslog Socket.
[    6.105072] systemd[1]: Starting Journal Service...
[    6.155649] systemd[1]: Started Journal Service.
[    6.528139] systemd-udevd[96]: starting version 215
[    7.563953] random: nonblocking pool is initialized
[    8.528172] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[    8.819022] rpi-ft5406 rpi_ft5406: Probing device
[    8.851812] input: FT5406 memory based driver as /devices/virtual/input/input0
[   10.070671] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
[   10.130909] gpiomem-bcm2835 20200000.gpiomem: Initialised: Registers at 0x20200000
[   10.244051] bcm2708_i2c 20804000.i2c: BSC1 Controller at 0x20804000 (irq 79) (baudrate 100000)
[   11.038088] sd 0:0:0:0: Attached scsi generic sg0 type 0
[   11.918318] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
[   11.919198] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   12.835583] systemd-journald[94]: Received request to flush runtime journal from PID 1
[   13.537169] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[   13.562145] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   14.949350] cfg80211: Calling CRDA to update world regulatory domain
[   15.244605] cfg80211: World regulatory domain updated:
[   15.244634] cfg80211:  DFS Master region: unset
[   15.244644] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
[   15.244659] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[   15.244671] cfg80211:   (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[   15.244682] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
[   15.244694] cfg80211:   (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A)
[   15.244705] cfg80211:   (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s)
[   15.244715] cfg80211:   (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
[   15.244725] cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
[   15.244735] cfg80211:   (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)
[   15.647901] Adding 102396k swap on /var/swap.  Priority:-1 extents:5 across:573436k SSFS
[   17.772166] bcm2708_fb soc:fb: Unknown ioctl 0x40187a22
[   35.356845] FS-Cache: Netfs 'cifs' registered for caching
[   35.357397] Key type cifs.spnego registered
[   35.357462] Key type cifs.idmap registered
[ 5347.728146] rpi-backlight rpi_backlight: Backlight change failed

DavidVTaylor
Posts: 7
Joined: Mon Oct 12, 2015 5:16 pm

Re: Sleep Mode - and or turn off backlight?

Tue Oct 27, 2015 12:29 am

Andrew - Very strange behavior. Not sure why your Pi is rebooting. I am testing with a vanilla configuration of the RPi 2 using the latest official Jessie image from the RPi Foundation site. The only thing attached to the Pi is the 7" display, a Trendnet USB Ethernet adapter, a Logitech USB mouse/keyboard adapter and a standard 2A USB wall wart.

After reading your response I tested turning the display off and on again and cannot reproduce the problems you are seeing with the exception of the permissions problem. Running "sudo su" before toggling the backlight works, but is not an ideal situation. I have not yet looked into whether there is an easy way to control permissions to work around this problem.

A new issue I have observed with the latest firmware is that the display now shows some vertical colored lines on the left side of the display after shutdown in addition to the usual B/W TV fade-to-gray snow effect. Not sure why that is happening, but it seems to be repeatable albeit with variations on a theme.

I have also observed on several occasions that the display sometimes fails to wake up after being idle for long periods of time. This is concerning since it suggests that out-of-the-box experience with the new RPi display and latest firmware is not very stable. I plan to repeat the test with the latest official firmware release for comparison.

I hope these problems get resolved soon since they are a real a show stopper for many real world uses. The lack of resiliency in the firmware display support is a very big problem since the only way to recover from a display problem is to power cycle the Rpi. This might be acceptable if the display integration were very stable, but that is unfortunately not the case.

David

barrybpl
Posts: 14
Joined: Mon Feb 09, 2015 9:56 pm

Re: Sleep Mode - and or turn off backlight?

Tue Oct 27, 2015 2:09 am

jdb wrote: If you're not in the Xwindows environment, i.e. at the console only, the console won't unblank if the touchscreen is used. This happens independently of being able to control the backlight. This is because the touchscreen is a mouse input device - the console only responds to keypresses..
I run gpm, the Linux console mouse driver so unblank using the touchscreen at the console works well, when it works at all.

I still haven't rebooted but now I'm finding it hit and miss if the screen will unblank at all. If it doesn't unblank, come a back a random amount of time later then it works again.

User avatar
jorabo
Posts: 40
Joined: Thu Feb 21, 2013 8:31 am
Location: Nuernberg
Contact: Website

Re: Sleep Mode - and or turn off backlight?

Tue Oct 27, 2015 9:05 am

Hi,
it seems, that the backlight driver does not recognize it's current state.
I get the same output in dmesg [ 1936.368969] rpi-backlight rpi_backlight: Backlight change failed.
But when the backlight is shut off, i can bring it back on by telling the device its current state by doing this:

echo 1 > /sys/class/backlight/rpi_backlight/bl_power
echo 0 > /sys/class/backlight/rpi_backlight/bl_power

Hope this helps !
Best regards

Jonny

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

Re: Sleep Mode - and or turn off backlight?

Tue Oct 27, 2015 10:51 am

I've been able to replicate this on a Pi left on the bench overnight.
Rockets are loud.
https://astro-pi.org

Aramas
Posts: 16
Joined: Tue Sep 29, 2015 10:24 am
Location: France - Lille

Re: Sleep Mode - and or turn off backlight?

Tue Oct 27, 2015 12:27 pm

Using mine as a kiosk with epiphany

It works well but if I let it off a long time it didn't come back with

echo 0 > /sys/class/backlight/rpi_backlight/bl_power

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

Re: Sleep Mode - and or turn off backlight?

Tue Oct 27, 2015 6:08 pm

Found out why:

There's a rate-limit built into the firmware to stop backlight toggling at more than twice per second. Signed-to-unsigned comparisons plus time counter roll-over means that bad things happen every ~half hour (i.e. the firmware refuses to change the backlight).

Working on a fix.
Rockets are loud.
https://astro-pi.org

Aramas
Posts: 16
Joined: Tue Sep 29, 2015 10:24 am
Location: France - Lille

Re: Sleep Mode - and or turn off backlight?

Wed Oct 28, 2015 8:12 am

thanks for the feedback

DavidVTaylor
Posts: 7
Joined: Mon Oct 12, 2015 5:16 pm

Re: Sleep Mode - and or turn off backlight?

Wed Oct 28, 2015 3:53 pm

Excellent. Glad to hear the backlight problem is getting sorted. The problem reminds me of the Microsoft counter rollover issue that wreaked havoc with LA flight control radio back in 2004. Nice to know the "fix" won't be to reboot the Pi every half hour ;)

Does anyone know if there are plans to address the fade-to-gray display effect when the Pi is shutdown? This is mostly a cosmetic issue, but it definitely detracts from what is otherwise an excellent display.

I was hoping the shutdown behavior would be addressed as part of the new backlight control features, but have not seen any improvements in that area. Things actually appear a little worse since I am now seeing random vertical lines on the display after shutdown.

As an alternate solution, I have been experimenting with turning off the display from within an init.d script at shutdown. So far I have not much luck on that approach. The init script works when tested from the shell, but does not seem to work when the Pi is stopped, possibly due to permissions issues.

User avatar
elParaguayo
Posts: 1943
Joined: Wed May 16, 2012 12:46 pm
Location: London, UK

Re: Sleep Mode - and or turn off backlight?

Wed Oct 28, 2015 5:09 pm

gsh wrote:That's the easy bit...

echo 80 > /sys/class/backlight/rpi-backlight/brightness

With my current build (not released yet) will do that... The thing I'm having trouble with right now is getting it to correctly blank the backlight when it goes to suspend, sometimes it works sometimes not...

Gordon
Quick question - this thread seems to have progressed to just turning the backlight on and off. However, I'm also interested in dimming the screen. From the earlier post it sounded like this would be possible.

Is this feature still available?

Of course I know the simple solution would be just to download the latest image and test it for myself...
RPi Information Screen: plugin based system for displaying weather, travel information, football scores etc.

JimmyN
Posts: 1109
Joined: Wed Mar 18, 2015 7:05 pm
Location: Virginia, USA

Re: Sleep Mode - and or turn off backlight?

Wed Oct 28, 2015 6:01 pm

No, still no dimming available right now. Values between 128~255 in "/sys/class/backlight/rpi-backlight/brightness" don't change anything, and values less than 128 turns the display off.

GekkePrutser
Posts: 36
Joined: Sat Mar 23, 2013 5:09 pm

Re: Sleep Mode - and or turn off backlight?

Mon Nov 02, 2015 12:17 pm

I'd also really love to have dimming - I assume this is still planned?

The display is very bright for normal use cases, though it's great that it can go so bright I would need to dim it for most uses.

Return to “Beginners”