Siduction Forum > Hardware - Support
Screen Freezes
(1/1)
finotti:
I'm having the following problem with my Lenovo t440p: once the screen locks, it freezes. (It might not freeze right away, maybe after a while being locked. I'm not sure.) But it seems that it is running. I can type my password, but nothing changes. But, if I switch to a VT (with Ctrl+Alt+Fn) and come back (with Ctrl+Alt+F7), it is unlocked.
So, basically switching back and forth to a VT unfreezes the screen.
Here is some info on the system:
--- Code: ---# inxi -G
Graphics: Device-1: Intel 4th Gen Core Processor Integrated Graphics driver: i915 v: kernel
Device-2: NVIDIA GK208M [GeForce GT 730M] driver: nouveau v: kernel
Device-3: Acer Integrated Camera type: USB driver: uvcvideo
Display: x11 server: X.Org 1.20.8 driver: intel resolution: 1: 1920x1080~60Hz
2: 1920x1080~60Hz
OpenGL: renderer: Mesa DRI Intel HD Graphics 4600 (HSW GT2) v: 4.5 Mesa 20.1.1
--- End code ---
--- Code: ---# inxi -v3
System: Host: t440p Kernel: 5.6.15-towo.1-siduction-amd64 x86_64 bits: 64 compiler: gcc
v: 10.1.0 Desktop: KDE Plasma 5.17.5
Distro: siduction 18.3.0 Patience - kde - (202002031718)
base: Debian GNU/Linux bullseye/sid
Machine: Type: Laptop System: LENOVO product: 20AWS2QV00 v: ThinkPad T440p serial: PC0AFBQN
Mobo: LENOVO model: 20AWS2QV00 v: SDK0E50510 WIN serial: L1HF5AM00X9
UEFI [Legacy]: LENOVO v: GLETA0WW (2.54 ) date: 08/27/2019
Battery: ID-1: BAT0 charge: 93.6 Wh condition: 94.6/99.5 Wh (95%) model: SANYO 45N1779
status: Unknown
CPU: Topology: Dual Core model: Intel Core i7-4600M bits: 64 type: MT MCP arch: Haswell
rev: 3 L2 cache: 4096 KiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 23146
Speed: 3007 MHz min/max: 800/3600 MHz Core speeds (MHz): 1: 3007 2: 3085 3: 2974
4: 2925
Graphics: Device-1: Intel 4th Gen Core Processor Integrated Graphics vendor: Lenovo driver: i915
v: kernel bus ID: 00:02.0
Device-2: NVIDIA GK208M [GeForce GT 730M] vendor: Lenovo driver: nouveau v: kernel
bus ID: 02:00.0
Device-3: Acer Integrated Camera type: USB driver: uvcvideo bus ID: 1-12:5
Display: x11 server: X.Org 1.20.8 driver: intel resolution: 1: 1920x1080~60Hz
2: 1920x1080~60Hz
OpenGL: renderer: Mesa DRI Intel HD Graphics 4600 (HSW GT2) v: 4.5 Mesa 20.1.1
direct render: Yes
Network: Device-1: Intel Ethernet I217-LM vendor: Lenovo ThinkPad T440p driver: e1000e
v: 3.2.6-k port: 4080 bus ID: 00:19.0
IF: enp0s25 state: down mac: 50:7b:9d:54:62:c8
Device-2: Intel Wireless 7260 driver: iwlwifi v: kernel port: 3000 bus ID: 04:00.0
IF: wlp4s0 state: up mac: 4c:eb:42:ab:b2:1a
Drives: Local Storage: total: 465.76 GiB used: 53.74 GiB (11.5%)
Info: Processes: 325 Uptime: 19d 12h 02m Memory: 15.40 GiB used: 6.00 GiB (39.0%)
Init: systemd runlevel: 5 Compilers: gcc: 9.3.0 Shell: bash v: 5.0.16 inxi: 3.1.03
--- End code ---
--- Code: ---# cat /etc/X11/xorg.conf.d/20-intel.conf
# /etc/X11/xorg.conf.d/20-intel.conf
Section "Device"
Identifier "IntelGraphics"
Driver "intel"
#Option "AccelMethod" "uxa"
#Option "AccelMethod" "sna"
Option "DRI" "3"
#Option "TripleBuffer" "true"
Option "TearFree" "true"
#Option "DRI" "false"
EndSection
# end of 20-intel.conf
--- End code ---
Any ideas?
towo:
Try booting with
--- Code: --- intel_iommu=igpu_off
--- End code ---
as bootparameter.
And btw, why you don't use the recent kernel?
hendrikL:
mh, why using the intel-driver not modesetting from the kernel?
What you can try, add to the boot-parameters "intel_iommu=igfx_off"
Also, if you don't need the 20-intel.conf, rename it!
--- Code: ---mv 20-intel.conf 20-intel.conf~
--- End code ---
ps. try first what towo wrote ;)
finotti:
Thanks, towo and HendrikL. The boot parameter seems to have fixed it!
Out of curiosity, what does it really do?
--- Quote from: towo on 2020/06/26, 07:26:46 ---And btw, why you don't use the recent kernel?
--- End quote ---
My wife uses this, so I don't have access to often to update it. But now it is up to date:
--- Code: ---# uname -a
Linux t440p 5.7.6-towo.1-siduction-amd64 #1 SMP PREEMPT siduction 5.7-9 (2020-06-24) x86_64 GNU/Linux
--- End code ---
--- Quote from: hendrikL on 2020/06/26, 07:29:48 ---mh, why using the intel-driver not modesetting from the kernel?
--- End quote ---
I assumed that the intel driver would be better? I think I was using modesetting before and can't quite remember if I changed it because I had a problem or just because I thought intel would work better.
Navigation
[0] Message Index
Go to full version