Re: [Nix-dev] Intermittent Blank Screen upon Opening Laptop Lid

2016-07-06 Thread Roger Qiu 
It does seem like a lot of people are experiencing this problem (on 
NixOS and beyond). I'll have to perform some experiments and play around 
with it to see how I can replicate it deterministically.



On 5/07/2016 1:15 PM, Ruben Astudillo wrote:

I got the same problem. I think I know the conditions that trigger the
bug, it has to do with both power sources on my laptop (BAT0 ADP1) being
online as per-said on /sys/class/power_supply at the same time. To avoid
this I just suspend (to mem) and open the netbook without the adapter
conected.



--
Founder of Matrix AI
https://matrix.ai/
+61420925975

___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Intermittent Blank Screen upon Opening Laptop Lid

2016-07-04 Thread Ruben Astudillo 

I got the same problem. I think I know the conditions that trigger the
bug, it has to do with both power sources on my laptop (BAT0 ADP1) being
online as per-said on /sys/class/power_supply at the same time. To avoid
this I just suspend (to mem) and open the netbook without the adapter
conected.

--
-- Ruben Astudillo
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Intermittent Blank Screen upon Opening Laptop Lid

2016-07-04 Thread zimbatm 
What does lspci give out? My XPS13 has she same issues and it's the skylake
architecture, it's not very well supported by the kernel.

On Mon, 4 Jul 2016, 21:15 Vladimír Čunát,  wrote:

> On 07/03/2016 12:38 PM, Roger Qiu wrote:
> > What's the display detect button? I tried switching to text terminals
> > whenever this happens, and while something's happening with the disk
> > (disk indicator light), the screen's still blank.
>
> On my Acer it's Fn-F5, but I suppose on different notebooks it might be
> elsewhere or missing.
>
> --Vladimir
>
>
> ___
> nix-dev mailing list
> nix-dev@lists.science.uu.nl
> http://lists.science.uu.nl/mailman/listinfo/nix-dev
>
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Intermittent Blank Screen upon Opening Laptop Lid

2016-07-04 Thread Vladimír Čunát 
On 07/03/2016 12:38 PM, Roger Qiu wrote:
> What's the display detect button? I tried switching to text terminals
> whenever this happens, and while something's happening with the disk
> (disk indicator light), the screen's still blank.

On my Acer it's Fn-F5, but I suppose on different notebooks it might be
elsewhere or missing.

--Vladimir




smime.p7s
Description: S/MIME Cryptographic Signature
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Intermittent Blank Screen upon Opening Laptop Lid

2016-07-03 Thread Roger Qiu 

Hi Vladimir,

What's the display detect button? I tried switching to text terminals 
whenever this happens, and while something's happening with the disk 
(disk indicator light), the screen's still blank.


Thanks,

Roger

On 2/07/2016 5:54 AM, Vladimír Čunát wrote:

On 07/01/2016 03:10 PM, Roger Qiu wrote:

basically upon closing the lid and reopening it after 10 min, the screen
stays blank, and I can't do anything

Sometimes this happens to me (nvidia notebook), but in my case I can
switch to text-mode terminals, and pressing the display-detect button
recovers the X session.

--Vladimir




--
Founder of Matrix AI
https://matrix.ai/
+61420925975

___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Intermittent Blank Screen upon Opening Laptop Lid

2016-07-01 Thread Roger Qiu 

Also there's a few different power saving modes being activated here.

One's just the screen turning off. Which happens when I stop interacting 
with the computer for a bit. As soon as I move the mouse, everything 
comes back. This is fine. This does not have an intermittent persistent 
blank screen.


Second is the actual `systemctl suspend` command. I've used that, and it 
works. It actually turns off all the lights, and my fan stops. This also 
does not have the intermittent persistent blank screen.


Third is the problem I have, is where I close the lid, wait and reopen 
it. I don't actually know what's happening here. But the screen goes 
blank like situation 1, but of course this is one with the intermittent 
persistent blank screen.


Thanks,

Roger


On 1/07/2016 11:55 PM, Roger Qiu wrote:
I should be clear, that right after the logs that I posted is just 
`Power key pressed.` `Powering Off...` and `System is powering down.`.


So the logs posted below, were 1 minute before I hard pressed the 
power button and forced it to shutdown.


The laptop also doesn't suspend when I close the lid. This is because 
it's pretty much vanilla NixOS. I didn't create any scripts for lid 
actions.



On 1/07/2016 11:49 PM, Roger Qiu wrote:
I found something interesting on my previous boot logs, since I had 
to force shutdown.


The error is follows (from journalctl -b -1):

```

Jul 01 23:10:48 matrix-central kernel: nvidia-modeset: WARNING: 
GPU:0: Lost display notification; continuing.
Jul 01 23:12:32 matrix-central kernel: nvidia-modeset: ERROR: GPU:0: 
Idling EVO timed out: 0x957d:0:0:0x0040
Jul 01 23:12:55 matrix-central kernel: INFO: rcu_sched self-detected 
stall on CPU
Jul 01 23:12:55 matrix-central kernel: 7: (21000 ticks this 
GP) idle=be3/141/0 softirq=4499/4499 fqs=7000
Jul 01 23:12:55 matrix-central kernel:  (t=21000 jiffies 
g=12925 c=12924 q=135)

Jul 01 23:12:55 matrix-central kernel: Task dump for CPU 7:
Jul 01 23:12:55 matrix-central kernel: X   R running 
task0  2997   2969 0x00400088
Jul 01 23:12:55 matrix-central kernel:  8184e340 
88081edc3d68 8109892f 0007
Jul 01 23:12:55 matrix-central kernel:  8184e340 
88081edc3d88 8109be6d 88081edc3dc8
Jul 01 23:12:55 matrix-central kernel:  0008 
88081edc3db8 810c4180 88081edd6a40

Jul 01 23:12:55 matrix-central kernel: Call Trace:
Jul 01 23:12:55 matrix-central kernel:   [] 
sched_show_task+0xaf/0x120
Jul 01 23:12:55 matrix-central kernel: [] 
dump_cpu_task+0x3d/0x50
Jul 01 23:12:55 matrix-central kernel: [] 
rcu_dump_cpu_stacks+0x90/0xe0
Jul 01 23:12:55 matrix-central kernel: [] 
rcu_check_callbacks+0x53e/0x830
Jul 01 23:12:55 matrix-central kernel: [] ? 
native_smp_send_reschedule+0x4a/0x70
Jul 01 23:12:55 matrix-central kernel: [] 
update_process_times+0x39/0x60
Jul 01 23:12:55 matrix-central kernel: [] 
tick_sched_handle.isra.15+0x36/0x50
Jul 01 23:12:55 matrix-central kernel: [] 
tick_sched_timer+0x44/0x80
Jul 01 23:12:55 matrix-central kernel: [] 
__run_hrtimer+0x85/0x240
Jul 01 23:12:55 matrix-central kernel: [] ? 
tick_sched_handle.isra.15+0x50/0x50
Jul 01 23:12:55 matrix-central kernel: [] 
hrtimer_interrupt+0xf3/0x210
Jul 01 23:12:55 matrix-central kernel: [] 
local_apic_timer_interrupt+0x3c/0x70
Jul 01 23:12:55 matrix-central kernel: [] 
smp_apic_timer_interrupt+0x41/0x60
Jul 01 23:12:55 matrix-central kernel: [] 
apic_timer_interrupt+0x6e/0x80
Jul 01 23:12:55 matrix-central kernel:   [] ? 
read_tsc+0x9/0x10
Jul 01 23:12:55 matrix-central kernel: [] ? 
_nv001840kms+0xd0/0x120 [nvidia_modeset]
Jul 01 23:12:55 matrix-central kernel: [] ? 
_nv001840kms+0xb2/0x120 [nvidia_modeset]
Jul 01 23:12:55 matrix-central kernel: [] ? 
_nv001737kms+0xa3/0x110 [nvidia_modeset]
Jul 01 23:12:55 matrix-central kernel: [] ? 
_nv001964kms+0x145e/0x2440 [nvidia_modeset]
Jul 01 23:12:55 matrix-central kernel: [] ? 
_nv009724rm+0xd/0x40 [nvidia]
Jul 01 23:12:55 matrix-central kernel: [] ? 
nvkms_alloc+0x5d/0x70 [nvidia_modeset]
Jul 01 23:12:55 matrix-central kernel: [] ? 
_nv000171kms+0x40/0x40 [nvidia_modeset]
Jul 01 23:12:55 matrix-central kernel: [] ? 
_nv000327kms+0x2e/0x40 [nvidia_modeset]
Jul 01 23:12:55 matrix-central kernel: [] ? 
nvKmsIoctl+0x161/0x1e0 [nvidia_modeset]
Jul 01 23:12:55 matrix-central kernel: [] ? 
nvkms_ioctl_common+0x45/0x90 [nvidia_modeset]
Jul 01 23:12:55 matrix-central kernel: [] ? 
nvkms_ioctl+0x62/0x90 [nvidia_modeset]
Jul 01 23:12:55 matrix-central kernel: [] ? 
nvidia_frontend_compat_ioctl+0x40/0x50 [nvidia]
Jul 01 23:12:55 matrix-central kernel: [] ? 
nvidia_frontend_unlocked_ioctl+0xe/0x10 [nvidia]
Jul 01 23:12:55 matrix-central kernel: [] ? 
do_vfs_ioctl+0x2a6/0x4b0
Jul 01 23:12:55 matrix-central kernel: [] ? 
__sb_end_write+0x35/0x70
Jul 01 23:12:55 matrix-central kernel: [] ? 
__audit_syscall_entry+0xac/0x100
Jul 01 23:12:55 matrix-central kernel: [] ? 
do_audit_syscall_entry+0x55/0x80
Jul

Re: [Nix-dev] Intermittent Blank Screen upon Opening Laptop Lid

2016-07-01 Thread Roger Qiu 
I should be clear, that right after the logs that I posted is just 
`Power key pressed.` `Powering Off...` and `System is powering down.`.


So the logs posted below, were 1 minute before I hard pressed the power 
button and forced it to shutdown.


The laptop also doesn't suspend when I close the lid. This is because 
it's pretty much vanilla NixOS. I didn't create any scripts for lid actions.



On 1/07/2016 11:49 PM, Roger Qiu wrote:
I found something interesting on my previous boot logs, since I had to 
force shutdown.


The error is follows (from journalctl -b -1):

```

Jul 01 23:10:48 matrix-central kernel: nvidia-modeset: WARNING: GPU:0: 
Lost display notification; continuing.
Jul 01 23:12:32 matrix-central kernel: nvidia-modeset: ERROR: GPU:0: 
Idling EVO timed out: 0x957d:0:0:0x0040
Jul 01 23:12:55 matrix-central kernel: INFO: rcu_sched self-detected 
stall on CPU
Jul 01 23:12:55 matrix-central kernel: 7: (21000 ticks this 
GP) idle=be3/141/0 softirq=4499/4499 fqs=7000
Jul 01 23:12:55 matrix-central kernel:  (t=21000 jiffies 
g=12925 c=12924 q=135)

Jul 01 23:12:55 matrix-central kernel: Task dump for CPU 7:
Jul 01 23:12:55 matrix-central kernel: X   R  running 
task0  2997   2969 0x00400088
Jul 01 23:12:55 matrix-central kernel:  8184e340 
88081edc3d68 8109892f 0007
Jul 01 23:12:55 matrix-central kernel:  8184e340 
88081edc3d88 8109be6d 88081edc3dc8
Jul 01 23:12:55 matrix-central kernel:  0008 
88081edc3db8 810c4180 88081edd6a40

Jul 01 23:12:55 matrix-central kernel: Call Trace:
Jul 01 23:12:55 matrix-central kernel:   [] 
sched_show_task+0xaf/0x120
Jul 01 23:12:55 matrix-central kernel:  [] 
dump_cpu_task+0x3d/0x50
Jul 01 23:12:55 matrix-central kernel:  [] 
rcu_dump_cpu_stacks+0x90/0xe0
Jul 01 23:12:55 matrix-central kernel:  [] 
rcu_check_callbacks+0x53e/0x830
Jul 01 23:12:55 matrix-central kernel:  [] ? 
native_smp_send_reschedule+0x4a/0x70
Jul 01 23:12:55 matrix-central kernel:  [] 
update_process_times+0x39/0x60
Jul 01 23:12:55 matrix-central kernel:  [] 
tick_sched_handle.isra.15+0x36/0x50
Jul 01 23:12:55 matrix-central kernel:  [] 
tick_sched_timer+0x44/0x80
Jul 01 23:12:55 matrix-central kernel:  [] 
__run_hrtimer+0x85/0x240
Jul 01 23:12:55 matrix-central kernel:  [] ? 
tick_sched_handle.isra.15+0x50/0x50
Jul 01 23:12:55 matrix-central kernel:  [] 
hrtimer_interrupt+0xf3/0x210
Jul 01 23:12:55 matrix-central kernel:  [] 
local_apic_timer_interrupt+0x3c/0x70
Jul 01 23:12:55 matrix-central kernel:  [] 
smp_apic_timer_interrupt+0x41/0x60
Jul 01 23:12:55 matrix-central kernel:  [] 
apic_timer_interrupt+0x6e/0x80
Jul 01 23:12:55 matrix-central kernel:   [] ? 
read_tsc+0x9/0x10
Jul 01 23:12:55 matrix-central kernel:  [] ? 
_nv001840kms+0xd0/0x120 [nvidia_modeset]
Jul 01 23:12:55 matrix-central kernel:  [] ? 
_nv001840kms+0xb2/0x120 [nvidia_modeset]
Jul 01 23:12:55 matrix-central kernel:  [] ? 
_nv001737kms+0xa3/0x110 [nvidia_modeset]
Jul 01 23:12:55 matrix-central kernel:  [] ? 
_nv001964kms+0x145e/0x2440 [nvidia_modeset]
Jul 01 23:12:55 matrix-central kernel:  [] ? 
_nv009724rm+0xd/0x40 [nvidia]
Jul 01 23:12:55 matrix-central kernel:  [] ? 
nvkms_alloc+0x5d/0x70 [nvidia_modeset]
Jul 01 23:12:55 matrix-central kernel:  [] ? 
_nv000171kms+0x40/0x40 [nvidia_modeset]
Jul 01 23:12:55 matrix-central kernel:  [] ? 
_nv000327kms+0x2e/0x40 [nvidia_modeset]
Jul 01 23:12:55 matrix-central kernel:  [] ? 
nvKmsIoctl+0x161/0x1e0 [nvidia_modeset]
Jul 01 23:12:55 matrix-central kernel:  [] ? 
nvkms_ioctl_common+0x45/0x90 [nvidia_modeset]
Jul 01 23:12:55 matrix-central kernel:  [] ? 
nvkms_ioctl+0x62/0x90 [nvidia_modeset]
Jul 01 23:12:55 matrix-central kernel:  [] ? 
nvidia_frontend_compat_ioctl+0x40/0x50 [nvidia]
Jul 01 23:12:55 matrix-central kernel:  [] ? 
nvidia_frontend_unlocked_ioctl+0xe/0x10 [nvidia]
Jul 01 23:12:55 matrix-central kernel:  [] ? 
do_vfs_ioctl+0x2a6/0x4b0
Jul 01 23:12:55 matrix-central kernel:  [] ? 
__sb_end_write+0x35/0x70
Jul 01 23:12:55 matrix-central kernel:  [] ? 
__audit_syscall_entry+0xac/0x100
Jul 01 23:12:55 matrix-central kernel:  [] ? 
do_audit_syscall_entry+0x55/0x80
Jul 01 23:12:55 matrix-central kernel:  [] ? 
SyS_ioctl+0x81/0xa0
Jul 01 23:12:55 matrix-central kernel:  [] ? 
syscall_trace_leave+0x9e/0x120
Jul 01 23:12:55 matrix-central kernel:  [] ? 
system_call_fastpath+0x12/0x71
Jul 01 23:13:58 matrix-central kernel: INFO: rcu_sched self-detected 
stall on CPU
Jul 01 23:13:58 matrix-central kernel: 7: (84004 ticks this 
GP) idle=be3/141/0 softirq=4499/4499 fqs=27997
Jul 01 23:13:58 matrix-central kernel:  (t=84004 jiffies 
g=12925 c=12924 q=594)

Jul 01 23:13:58 matrix-central kernel: Task dump for CPU 7:
Jul 01 23:13:58 matrix-central kernel: X   R  running 
task0  2997   2969 0x00400088
Jul 01 23:13:58 matrix-central kernel:  8184e340 
88081edc3d68 8109892f

Re: [Nix-dev] Intermittent Blank Screen upon Opening Laptop Lid

2016-07-01 Thread Roger Qiu 
I found something interesting on my previous boot logs, since I had to 
force shutdown.


The error is follows (from journalctl -b -1):

```

Jul 01 23:10:48 matrix-central kernel: nvidia-modeset: WARNING: GPU:0: 
Lost display notification; continuing.
Jul 01 23:12:32 matrix-central kernel: nvidia-modeset: ERROR: GPU:0: 
Idling EVO timed out: 0x957d:0:0:0x0040
Jul 01 23:12:55 matrix-central kernel: INFO: rcu_sched self-detected 
stall on CPU
Jul 01 23:12:55 matrix-central kernel: 7: (21000 ticks this GP) 
idle=be3/141/0 softirq=4499/4499 fqs=7000
Jul 01 23:12:55 matrix-central kernel:  (t=21000 jiffies g=12925 
c=12924 q=135)

Jul 01 23:12:55 matrix-central kernel: Task dump for CPU 7:
Jul 01 23:12:55 matrix-central kernel: X   R  running 
task0  2997   2969 0x00400088
Jul 01 23:12:55 matrix-central kernel:  8184e340 
88081edc3d68 8109892f 0007
Jul 01 23:12:55 matrix-central kernel:  8184e340 
88081edc3d88 8109be6d 88081edc3dc8
Jul 01 23:12:55 matrix-central kernel:  0008 
88081edc3db8 810c4180 88081edd6a40

Jul 01 23:12:55 matrix-central kernel: Call Trace:
Jul 01 23:12:55 matrix-central kernel:   [] 
sched_show_task+0xaf/0x120
Jul 01 23:12:55 matrix-central kernel:  [] 
dump_cpu_task+0x3d/0x50
Jul 01 23:12:55 matrix-central kernel:  [] 
rcu_dump_cpu_stacks+0x90/0xe0
Jul 01 23:12:55 matrix-central kernel:  [] 
rcu_check_callbacks+0x53e/0x830
Jul 01 23:12:55 matrix-central kernel:  [] ? 
native_smp_send_reschedule+0x4a/0x70
Jul 01 23:12:55 matrix-central kernel:  [] 
update_process_times+0x39/0x60
Jul 01 23:12:55 matrix-central kernel:  [] 
tick_sched_handle.isra.15+0x36/0x50
Jul 01 23:12:55 matrix-central kernel:  [] 
tick_sched_timer+0x44/0x80
Jul 01 23:12:55 matrix-central kernel:  [] 
__run_hrtimer+0x85/0x240
Jul 01 23:12:55 matrix-central kernel:  [] ? 
tick_sched_handle.isra.15+0x50/0x50
Jul 01 23:12:55 matrix-central kernel:  [] 
hrtimer_interrupt+0xf3/0x210
Jul 01 23:12:55 matrix-central kernel:  [] 
local_apic_timer_interrupt+0x3c/0x70
Jul 01 23:12:55 matrix-central kernel:  [] 
smp_apic_timer_interrupt+0x41/0x60
Jul 01 23:12:55 matrix-central kernel:  [] 
apic_timer_interrupt+0x6e/0x80
Jul 01 23:12:55 matrix-central kernel:   [] ? 
read_tsc+0x9/0x10
Jul 01 23:12:55 matrix-central kernel:  [] ? 
_nv001840kms+0xd0/0x120 [nvidia_modeset]
Jul 01 23:12:55 matrix-central kernel:  [] ? 
_nv001840kms+0xb2/0x120 [nvidia_modeset]
Jul 01 23:12:55 matrix-central kernel:  [] ? 
_nv001737kms+0xa3/0x110 [nvidia_modeset]
Jul 01 23:12:55 matrix-central kernel:  [] ? 
_nv001964kms+0x145e/0x2440 [nvidia_modeset]
Jul 01 23:12:55 matrix-central kernel:  [] ? 
_nv009724rm+0xd/0x40 [nvidia]
Jul 01 23:12:55 matrix-central kernel:  [] ? 
nvkms_alloc+0x5d/0x70 [nvidia_modeset]
Jul 01 23:12:55 matrix-central kernel:  [] ? 
_nv000171kms+0x40/0x40 [nvidia_modeset]
Jul 01 23:12:55 matrix-central kernel:  [] ? 
_nv000327kms+0x2e/0x40 [nvidia_modeset]
Jul 01 23:12:55 matrix-central kernel:  [] ? 
nvKmsIoctl+0x161/0x1e0 [nvidia_modeset]
Jul 01 23:12:55 matrix-central kernel:  [] ? 
nvkms_ioctl_common+0x45/0x90 [nvidia_modeset]
Jul 01 23:12:55 matrix-central kernel:  [] ? 
nvkms_ioctl+0x62/0x90 [nvidia_modeset]
Jul 01 23:12:55 matrix-central kernel:  [] ? 
nvidia_frontend_compat_ioctl+0x40/0x50 [nvidia]
Jul 01 23:12:55 matrix-central kernel:  [] ? 
nvidia_frontend_unlocked_ioctl+0xe/0x10 [nvidia]
Jul 01 23:12:55 matrix-central kernel:  [] ? 
do_vfs_ioctl+0x2a6/0x4b0
Jul 01 23:12:55 matrix-central kernel:  [] ? 
__sb_end_write+0x35/0x70
Jul 01 23:12:55 matrix-central kernel:  [] ? 
__audit_syscall_entry+0xac/0x100
Jul 01 23:12:55 matrix-central kernel:  [] ? 
do_audit_syscall_entry+0x55/0x80
Jul 01 23:12:55 matrix-central kernel:  [] ? 
SyS_ioctl+0x81/0xa0
Jul 01 23:12:55 matrix-central kernel:  [] ? 
syscall_trace_leave+0x9e/0x120
Jul 01 23:12:55 matrix-central kernel:  [] ? 
system_call_fastpath+0x12/0x71
Jul 01 23:13:58 matrix-central kernel: INFO: rcu_sched self-detected 
stall on CPU
Jul 01 23:13:58 matrix-central kernel: 7: (84004 ticks this GP) 
idle=be3/141/0 softirq=4499/4499 fqs=27997
Jul 01 23:13:58 matrix-central kernel:  (t=84004 jiffies g=12925 
c=12924 q=594)

Jul 01 23:13:58 matrix-central kernel: Task dump for CPU 7:
Jul 01 23:13:58 matrix-central kernel: X   R  running 
task0  2997   2969 0x00400088
Jul 01 23:13:58 matrix-central kernel:  8184e340 
88081edc3d68 8109892f 0007
Jul 01 23:13:58 matrix-central kernel:  8184e340 
88081edc3d88 8109be6d 88081edc3dc8
Jul 01 23:13:58 matrix-central kernel:  0008 
88081edc3db8 810c4180 88081edd6a40

Jul 01 23:13:58 matrix-central kernel: Call Trace:
Jul 01 23:13:58 matrix-central kernel:   [] 
sched_show_task+0xaf/0x120
Jul 01 23:13:58 matrix-central kernel:  [] 
dump_cpu_task+0x3d/0x50
Jul 01 23:13:58

Re: [Nix-dev] Intermittent Blank Screen upon Opening Laptop Lid

2016-07-01 Thread Tomasz Czyż 
I have this issue sometimes on intel driver as well (once every few weeks),
I had this on debian/ubuntu as well, I think it's more a driver problem
rather than nixos specific thing if you are looking for a direction.

2016-07-01 14:15 GMT+01:00 Bjørn Forsman :

> On 1 July 2016 at 15:10, Roger Qiu  wrote:
> > Hi Nixers,
> >
> > I discovered this problem a while ago, basically upon closing the lid and
> > reopening it after 10 min, the screen stays blank, and I can't do
> anything.
> > Even switching to tty1 doesn't work.
> >
> > This doesn't always happen. And when I close the lid and reopen after a
> few
> > seconds, it usually works and displays something.
> >
> > What are the steps that I can take to debug this issue.
> >
> > It was happening back on NixOS 15.09. and is continuing on 16.03.
> >
> > I'm running NVIDIA and using NVIDIA video card driver.
>
> Did you check the system log?
>
> - Bjørn
> ___
> nix-dev mailing list
> nix-dev@lists.science.uu.nl
> http://lists.science.uu.nl/mailman/listinfo/nix-dev
>



-- 
Tomasz Czyż
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev

[Nix-dev] Intermittent Blank Screen upon Opening Laptop Lid

2016-07-01 Thread Roger Qiu 

Hi Nixers,

I discovered this problem a while ago, basically upon closing the lid 
and reopening it after 10 min, the screen stays blank, and I can't do 
anything. Even switching to tty1 doesn't work.


This doesn't always happen. And when I close the lid and reopen after a 
few seconds, it usually works and displays something.


What are the steps that I can take to debug this issue.

It was happening back on NixOS 15.09. and is continuing on 16.03.

I'm running NVIDIA and using NVIDIA video card driver.

Thanks,

Roger

--
Founder of Matrix AI
https://matrix.ai/
+61420925975

___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev