Page 1 of 1
Blank screen at login
Posted: Sat Apr 12, 2025 3:21 pm
by MarieSophie
Hello,
MX have been running fine since my last reinstall (to solve problem with VPN) early february
This morning, after the computer froze, I click restart, and then it boots up, bios password, MX logo, log-in screen, login+password, and .... blank screen
I hit ESC, and see that it hang at line "/dev "
I waited 30min, nothing.
Hard-stop the computer, wait 2min, restart
Bios, MX logo, and straight to blank screen with a little white line on the top left
The cursor moves all right, but nothing else
Restart, re-blank screen
Then I tried previous kernel, same thing
Before reinstalling it all (again) I thought about:
Then I tried previous kernel with systemD ... and it starts !!
Then I re-tried the "default" still nothing.
What could be causing SystemD to work and not the default SysVinit ?
Did I miss (I don't read it) an update revocating SysVinit ?
Thank you !
MSSG
Re: Blank screen at login
Posted: Sat Apr 12, 2025 3:24 pm
by Eadwine Rose
According to the forum rules (please read): Please provide full Quick System Info, use copy for forum button, no edits.
LiveUSB version is OK if needed.
Re: Blank screen at login
Posted: Sat Apr 12, 2025 4:27 pm
by MarieSophie
Eadwine Rose wrote: Sat Apr 12, 2025 3:24 pm
According to the
forum rules (please read): Please provide full Quick System Info, use copy for forum button, no edits.
LiveUSB version is OK if needed.
I thought about that, but as I'm logged using a different system, I thought that would be irrelevant (or misleading)
Code: Select all
System:
Kernel: 6.1.0-32-amd64 [6.1.129-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
parameters: BOOT_IMAGE=/vmlinuz-6.1.0-32-amd64 root=UUID=<filter> ro quiet splash
init=/lib/systemd/systemd
Desktop: KDE Plasma v: 5.27.5 wm: kwin_x11 vt: 7 dm: SDDM Distro: MX-23.5_KDE_x64 Libretto Jan
12 2025 base: Debian GNU/Linux 12 (bookworm)
Machine:
Type: Laptop System: LENOVO product: 20AN006NCA v: ThinkPad T440p serial: <superuser required>
Chassis: type: 10 serial: <superuser required>
Mobo: LENOVO model: 20AN006NCA v: 0B98401 WIN serial: <superuser required> UEFI: LENOVO
v: GLET98WW (2.52 ) date: 02/27/2019
Battery:
ID-1: BAT0 charge: 22.1 Wh (53.6%) condition: 41.2/99.5 Wh (41.4%) volts: 11.2 min: 11.1
model: LGC 45N1153 type: Li-ion serial: <filter> status: not charging
CPU:
Info: model: Intel Core i7-4910MQ bits: 64 type: MT MCP arch: Haswell gen: core 4 level: v3
note: check built: 2013-15 process: Intel 22nm family: 6 model-id: 0x3C (60) stepping: 3
microcode: 0x28
Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache: L1: 256 KiB
desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB L3: 8 MiB desc: 1x8 MiB
Speed (MHz): avg: 2494 high: 2495 min/max: 800/3900 scaling: driver: intel_cpufreq
governor: ondemand cores: 1: 2494 2: 2494 3: 2495 4: 2495 5: 2495 6: 2495 7: 2495 8: 2495
bogomips: 46298
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities:
Type: gather_data_sampling status: Not affected
Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
Type: mds mitigation: Clear CPU buffers; SMT vulnerable
Type: meltdown mitigation: PTI
Type: mmio_stale_data status: Unknown: No mitigations
Type: reg_file_data_sampling status: Not affected
Type: retbleed status: Not affected
Type: spec_rstack_overflow status: Not affected
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Retpolines; IBPB: conditional; IBRS_FW; STIBP: conditional; RSB
filling; PBRSB-eIBRS: Not affected; BHI: Not affected
Type: srbds mitigation: Microcode
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: Intel 4th Gen Core Processor Integrated Graphics vendor: Lenovo driver: i915 v: kernel
arch: Gen-7.5 process: Intel 22nm built: 2013 ports: active: eDP-1 empty: DP-1, DP-2, HDMI-A-1,
HDMI-A-2, VGA-1 bus-ID: 00:02.0 chip-ID: 8086:0416 class-ID: 0300
Device-2: NVIDIA GK208M [GeForce GT 730M] vendor: Lenovo driver: N/A alternate: nouveau
non-free: series: 470.xx+ status: legacy-active (EOL~2023/24) arch: Kepler code: GKxxx
process: TSMC 28nm built: 2012-18 pcie: gen: 1 speed: 2.5 GT/s lanes: 8 link-max: gen: 3
speed: 8 GT/s bus-ID: 02:00.0 chip-ID: 10de:1290 class-ID: 0300
Device-3: Chicony Integrated Camera type: USB driver: uvcvideo bus-ID: 1-12:3
chip-ID: 04f2:b39a class-ID: 0e02
Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.9 compositor: kwin_x11 driver: X:
loaded: modesetting unloaded: fbdev,vesa dri: crocus gpu: i915 display-ID: :0 screens: 1
Screen-1: 0 s-res: 1600x900 s-dpi: 96 s-size: 423x238mm (16.65x9.37") s-diag: 485mm (19.11")
Monitor-1: eDP-1 model: LG Display 0x03fc built: 2013 res: 1600x900 hz: 60 dpi: 132 gamma: 1.2
size: 309x174mm (12.17x6.85") diag: 355mm (14") ratio: 16:9 modes: 1600x900
API: OpenGL v: 4.6 Mesa 24.2.8-1mx23ahs renderer: Mesa Intel HD Graphics 4600 (HSW GT2)
direct-render: Yes
Audio:
Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio vendor: Lenovo ThinkPad T440p
driver: snd_hda_intel v: kernel bus-ID: 00:03.0 chip-ID: 8086:0c0c class-ID: 0403
Device-2: Intel 8 Series/C220 Series High Definition Audio vendor: Lenovo ThinkPad T440p
driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:8c20 class-ID: 0403
API: ALSA v: k6.1.0-32-amd64 status: kernel-api tools: alsamixer,amixer
Server-1: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse status: active
2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Intel Ethernet I217-LM vendor: Lenovo ThinkPad T440p driver: e1000e v: kernel
port: 4080 bus-ID: 00:19.0 chip-ID: 8086:153a class-ID: 0200
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-2: Intel Wireless 7260 driver: iwlwifi v: kernel modules: wl pcie: gen: 1
speed: 2.5 GT/s lanes: 1 bus-ID: 04:00.0 chip-ID: 8086:08b2 class-ID: 0280
IF: wlan0 state: down mac: <filter>
IF-ID-1: proton0 state: unknown speed: N/A duplex: N/A mac: N/A
IF-ID-2: pvpnksintrf1 state: unknown speed: N/A duplex: N/A mac: <filter>
Drives:
Local Storage: total: 3.2 TiB used: 631.14 GiB (19.3%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Dogfish Technology model: SSD 512GB size: 476.94 GiB
block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 1A0
scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 vendor: Western Digital model: WD20SPZX-22UA7T0 size: 1.82 TiB
block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 5400 serial: <filter>
rev: 1A01 scheme: GPT
ID-3: /dev/sdc maj-min: 8:32 type: USB vendor: Sabrent model: SABRENT size: 931.51 GiB
block-size: physical: 4096 B logical: 512 B type: N/A serial: <filter> rev: 0104 scheme: MBR
ID-4: /dev/sdd maj-min: 8:48 type: USB vendor: Kingston model: DataTraveler 2.0 size: 953.9 MiB
block-size: physical: 512 B logical: 512 B type: N/A serial: <filter> rev: 1.00 scheme: MBR
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
ID-1: / raw-size: 128 GiB size: 124.93 GiB (97.60%) used: 14.69 GiB (11.8%) fs: ext4
dev: /dev/sda3 maj-min: 8:3
ID-2: /boot raw-size: 1024 MiB size: 973.4 MiB (95.06%) used: 272.3 MiB (28.0%) fs: ext4
dev: /dev/sda2 maj-min: 8:2
ID-3: /boot/efi raw-size: 750 MiB size: 748.5 MiB (99.80%) used: 288 KiB (0.0%) fs: vfat
dev: /dev/sda1 maj-min: 8:1
ID-4: /tmp raw-size: 32 GiB size: 31.2 GiB (97.50%) used: 31.9 MiB (0.1%) fs: ext4
dev: /dev/sdb2 maj-min: 8:18
ID-5: /var raw-size: 128 GiB size: 124.93 GiB (97.60%) used: 5.46 GiB (4.4%) fs: ext4
dev: /dev/sdb5 maj-min: 8:21
Swap:
Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: partition size: 32 GiB used: 4.9 MiB (0.0%) priority: -2 dev: /dev/sdb1
maj-min: 8:17
Sensors:
System Temperatures: cpu: 47.0 C mobo: N/A
Fan Speeds (RPM): fan-1: 0
Repos:
Packages: 2624 pm: dpkg pkgs: 2610 libs: 1375 tools: apt,apt-get,aptitude,nala pm: rpm pkgs: 0
pm: flatpak pkgs: 14
No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list
1: deb [arch=amd64 signed-by=/usr/share/keyrings/brave-browser-archive-keyring.gpg] https://brave-browser-apt-release.s3.brave.com/ stable main
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://mirror.math.princeton.edu/pub/mxlinux/mx/repo/ bookworm main non-free
2: deb http://mirror.math.princeton.edu/pub/mxlinux/mx/repo/ bookworm ahs
Active apt repos in: /etc/apt/sources.list.d/protonvpn-stable.list
1: deb [signed-by=/usr/share/keyrings/protonvpn-stable-archive-keyring.gpg] https://repo.protonvpn.com/debian stable main
Info:
Processes: 431 Uptime: 3h 22m wakeups: 6 Memory: 15.5 GiB used: 7.02 GiB (45.3%) Init: systemd
v: 252 target: graphical (5) default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI
Re: Blank screen at login
Posted: Sat Apr 12, 2025 4:30 pm
by MarieSophie
I have 26 updates waiting in my queue, I'm hesitating to go ahead :/
Re: Blank screen at login
Posted: Sat Apr 12, 2025 4:44 pm
by DukeComposed
MarieSophie wrote: Sat Apr 12, 2025 4:27 pm
I thought about that, but as I'm logged using a different system, I thought that would be irrelevant (or misleading)
I thought it went without saying that the QSI for a help request should belong to the affected system.
Re: Blank screen at login
Posted: Sat Apr 12, 2025 6:34 pm
by MarieSophie
DukeComposed wrote: Sat Apr 12, 2025 4:44 pm
MarieSophie wrote: Sat Apr 12, 2025 4:27 pm
I thought about that, but as I'm logged using a different system, I thought that would be irrelevant (or misleading)
I thought it went without saying that the QSI for a help request should belong to the affected system.
Yes, my point exactly !
But for the sake of non-confusion, by "system" I mean SysVinit versus SystemD.
The problem happen with SysVinit, which I can't log into, therefore no QSI, and the one I provided is with SystemD.
MSSG
Re: Blank screen at login
Posted: Sat Apr 12, 2025 8:04 pm
by j2mcgreg
@MarieSophie wrote:
Yes, my point exactly !
But for the sake of non-confusion, by "system" I mean SysVinit versus SystemD.
The problem happen with SysVinit, which I can't log into, therefore no QSI, and the one I provided is with SystemD.
MSSG
What you could do is log into the SystemD version, create a new user, give it admin access, and then log out. Now log in as the new user, at the grub screen click on Advanced Options and select a Sys V kernel as the boot choice. If this lets you get to the desktop, use Boot Options in MX Tools to make the switch permanent. Finally copy the contents of /home to the new user and then delete the old account. This wouldn't be the first time that a user's profile has gotten corrupted for unknown reasons. It happens, not often, but it does happen.
Re: Blank screen at login
Posted: Sat Apr 12, 2025 8:20 pm
by Germ
Are you logging into Plasma (Wayland)?
If so, try logging into Plasma (X-11)
In my experience, some machines just don't behave well with Wayland. Kind of hit and miss at times.
Re: Blank screen at login
Posted: Sat Apr 12, 2025 11:04 pm
by DukeComposed
MarieSophie wrote: Sat Apr 12, 2025 6:34 pm
But for the sake of non-confusion, by "system" I mean SysVinit versus SystemD.
"I'm logged using a different system" implies computer A is having the problem so you switched to computer B which may not be having the same problem and is likely worthless in terms of investigation.
systemd and sysvinit are known as "init systems". So if you've had to switch to systemd, it's important to specify that you're using a different init system. Even saying "I'm only using systemd now" would have given a clearer picture than "using a different system" did.
Re: Blank screen at login
Posted: Sun Apr 13, 2025 6:01 am
by MarieSophie
Germ wrote: Sat Apr 12, 2025 8:20 pm
Are you logging into Plasma (Wayland)?
If so, try logging into Plasma (X-11)
In my experience, some machines just don't behave well with Wayland. Kind of hit and miss at times.
I'm with X11 ...
Re: Blank screen at login
Posted: Sun Apr 13, 2025 6:04 am
by MarieSophie
DukeComposed wrote: Sat Apr 12, 2025 11:04 pm
MarieSophie wrote: Sat Apr 12, 2025 6:34 pm
But for the sake of non-confusion, by "system" I mean SysVinit versus SystemD.
"I'm logged using a different system" implies computer A is having the problem so you switched to computer B which may not be having the same problem and is likely worthless in terms of investigation.
systemd and sysvinit are known as "init systems". So if you've had to switch to systemd, it's important to specify that you're using a different init system. Even saying "I'm only using systemd now" would have given a clearer picture than "using a different system" did.
Right, TY for the precision, so by saying -"I thought it went without saying that the QSI for a help request should belong to the affected system. " you were indeed expecting me to provide QSI for a system (Init system) which I can't log into ?
Re: Blank screen at login
Posted: Sun Apr 13, 2025 6:05 am
by MarieSophie
MarieSophie wrote: Sat Apr 12, 2025 4:30 pm
I have 26 updates waiting in my queue, I'm hesitating to go ahead :/
Since the SystemD is (seems to be) working, should I go ahead with updates, or will it FU my system the same way as in SysVinit ?
Re: Blank screen at login
Posted: Sun Apr 13, 2025 6:57 am
by j2mcgreg
MarieSophie wrote: Sun Apr 13, 2025 6:05 am
MarieSophie wrote: Sat Apr 12, 2025 4:30 pm
I have 26 updates waiting in my queue, I'm hesitating to go ahead :/
Since the SystemD is (seems to be) working, should I go ahead with updates, or will it FU my system the same way as in SysVinit ?
I would.
Re: Blank screen at login
Posted: Sun Apr 13, 2025 6:56 pm
by DukeComposed
MarieSophie wrote: Sun Apr 13, 2025 6:04 am
so by saying -"I thought it went without saying that the QSI for a help request should belong to the affected system. " you were indeed expecting me to provide QSI for a system (Init system) which I can't log into ?
In a word, yes: by comparison a QSI from a machine you can log into isn't of much use if it doesn't present with any of the same symptoms. If you can't log into the machine, you can at least provide a QSI on it from a live session or, as you did in this case, by booting with a different init system.
Several people have switched to systemd for troubleshooting in threads over the years, but they at least stated unambiguously that they'd defaulted to using a different init, not a different machine. I'm less pointing out a problem with the methodology than with the nomenclature.
Re: Blank screen at login
Posted: Sun Apr 13, 2025 7:01 pm
by MarieSophie
DukeComposed wrote: Sun Apr 13, 2025 6:56 pm
MarieSophie wrote: Sun Apr 13, 2025 6:04 am
so by saying -"I thought it went without saying that the QSI for a help request should belong to the affected system. " you were indeed expecting me to provide QSI for a system (Init system) which I can't log into ?
In a word, yes: by comparison a QSI from a machine you can log into isn't of much use if it doesn't present with any of the same symptoms. If you can't log into the machine, you can at least provide a QSI on it from a live session or, as you did in this case, by booting with a different init system.
Several people have switched to systemd for troubleshooting in threads over the years, but they at least stated unambiguously that they'd defaulted to using a different init, not a different machine. I'm less pointing out a problem with the methodology than with the nomenclature.
Got it, thank you for the clarification, and sorry for my shortcut, instead of saying I logged in using a different system, I should have said I logged into the same box using a different init system
Noted ! and I will try to remember (probably won't, by try)
Re: Blank screen at login
Posted: Sun Apr 13, 2025 7:36 pm
by DukeComposed
MarieSophie wrote: Sun Apr 13, 2025 7:01 pm
Got it, thank you for the clarification, and sorry for my shortcut, instead of saying I logged in using a different system
I've seen people post an irrelevant QSI before because rules are rules and they think that it's some kind of captcha challenge. "I'm having a problem with X, but investigating X is too hard for me, so I'll post my problem with a QSI of Y because this forum is just going to ask for a QSI so maybe this unrelated thing will be good enough, lol" is not an unheard of line of thinking. When troubleshooting a problem, aim for as much clarity as you can. As
How to Report Bugs Effectively says, "If the programmer can't tell what you meant, you might as well not have said anything."
Re: Blank screen at login
Posted: Mon Apr 14, 2025 12:03 pm
by atomick
How does one "Sign-in - log in via choice X11 or Wayland ?
see only "failsafe wayland" in ~/.config/xfce4/xfconf/xfce4-perchannel-xml/xfce4-session.xml
<property name="FailsafeWayland" type="empty">
is there an easy way to perform this ?
Re: Blank screen at login
Posted: Mon Apr 14, 2025 2:40 pm
by Stevo
j2mcgreg wrote: Sat Apr 12, 2025 8:04 pm
@MarieSophie wrote:
Yes, my point exactly !
But for the sake of non-confusion, by "system" I mean SysVinit versus SystemD.
The problem happen with SysVinit, which I can't log into, therefore no QSI, and the one I provided is with SystemD.
MSSG
What you could do is log into the SystemD version, create a new user, give it admin access, and then log out. Now log in as the new user, at the grub screen click on Advanced Options and select a Sys V kernel as the boot choice. If this lets you get to the desktop, use Boot Options in MX Tools to make the switch permanent. Finally copy the contents of /home to the new user and then delete the old account. This wouldn't be the first time that a user's profile has gotten corrupted for unknown reasons. It happens, not often, but it does happen.
The GRUB kernel choice comes before any user logins...at least this isn't due to any 6.14 kernel problems. The new kernel is the Bookworm 6.1.0-33 (6.1.133) release.
Re: Blank screen at login
Posted: Mon Apr 14, 2025 2:42 pm
by Stevo
atomick wrote: Mon Apr 14, 2025 12:03 pm
How does one "Sign-in - log in via choice X11 or Wayland ?
see only "failsafe wayland" in ~/.config/xfce4/xfconf/xfce4-perchannel-xml/xfce4-session.xml
<property name="FailsafeWayland" type="empty">
is there an easy way to perform this ?
It's somewhere on your KDE user login screen, depending which one you have (so many choices!).
Re: Blank screen at login
Posted: Mon Apr 14, 2025 3:00 pm
by j2mcgreg
Stevo wrote: Mon Apr 14, 2025 2:40 pm
j2mcgreg wrote: Sat Apr 12, 2025 8:04 pm
@MarieSophie wrote:
Yes, my point exactly !
But for the sake of non-confusion, by "system" I mean SysVinit versus SystemD.
The problem happen with SysVinit, which I can't log into, therefore no QSI, and the one I provided is with SystemD.
MSSG
What you could do is log into the SystemD version, create a new user, give it admin access, and then log out. Now log in as the new user, at the grub screen click on Advanced Options and select a Sys V kernel as the boot choice. If this lets you get to the desktop, use Boot Options in MX Tools to make the switch permanent. Finally copy the contents of /home to the new user and then delete the old account. This wouldn't be the first time that a user's profile has gotten corrupted for unknown reasons. It happens, not often, but it does happen.
The GRUB kernel choice comes before any user logins...at least this isn't due to any 6.14 kernel problems. The new kernel is the Bookworm 6.1.0-33 (6.1.133) release.
I was thinking about a bad block on the drive where MX is located but where the next block in the chain wasn't clearly defined when the bad one was replaced automatically from the cache of spares. The new user's login sequence would be written to an unused area of the drive.
Re: Blank screen at login
Posted: Mon Apr 14, 2025 3:00 pm
by j2mcgreg
Stevo wrote: Mon Apr 14, 2025 2:40 pm
j2mcgreg wrote: Sat Apr 12, 2025 8:04 pm
@MarieSophie wrote:
Yes, my point exactly !
But for the sake of non-confusion, by "system" I mean SysVinit versus SystemD.
The problem happen with SysVinit, which I can't log into, therefore no QSI, and the one I provided is with SystemD.
MSSG
What you could do is log into the SystemD version, create a new user, give it admin access, and then log out. Now log in as the new user, at the grub screen click on Advanced Options and select a Sys V kernel as the boot choice. If this lets you get to the desktop, use Boot Options in MX Tools to make the switch permanent. Finally copy the contents of /home to the new user and then delete the old account. This wouldn't be the first time that a user's profile has gotten corrupted for unknown reasons. It happens, not often, but it does happen.
The GRUB kernel choice comes before any user logins...at least this isn't due to any 6.14 kernel problems. The new kernel is the Bookworm 6.1.0-33 (6.1.133) release.
I was thinking about a bad block on the drive where MX is located but where the next block in the chain wasn't clearly defined when the bad one was replaced automatically from the cache of spares. The new user's login sequence would be written to an unused area of the drive.
Re: Blank screen at login
Posted: Mon Apr 14, 2025 5:33 pm
by atomick
Thx Stevo . Currently and always have run the Xfce4 flavors running most recent spin of 23.6 saw downloaded installed. Not aware of such feature on KDE. thx.
Re: Blank screen at login
Posted: Fri Apr 18, 2025 6:25 am
by MarieSophie
Hello,
Situation:
SystemVinit = can't boot (past MX logo, blanck screen with a dash in the top left)
SystemD = boot up alright, but several errors, USB mounted as root owned, even though "RW, Users" in fstab; can't chown it back to user; update error, can't install.
So I guess that's a full reinstall ? (that's all I know how to do)
QSI should be the same as previous:
Code: Select all
System:
Kernel: 6.1.0-33-amd64 [6.1.133-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
parameters: BOOT_IMAGE=/vmlinuz-6.1.0-33-amd64 root=UUID=<filter> ro quiet splash
init=/lib/systemd/systemd
Desktop: KDE Plasma v: 5.27.5 wm: kwin_x11 vt: 7 dm: SDDM Distro: MX-23.6_KDE_x64 Libretto Jan
12 2025 base: Debian GNU/Linux 12 (bookworm)
Machine:
Type: Laptop System: LENOVO product: 20AN006NCA v: ThinkPad T440p serial: <superuser required>
Chassis: type: 10 serial: <superuser required>
Mobo: LENOVO model: 20AN006NCA v: 0B98401 WIN serial: <superuser required> UEFI: LENOVO
v: GLET98WW (2.52 ) date: 02/27/2019
Battery:
ID-1: BAT0 charge: 21.1 Wh (51.2%) condition: 41.2/99.5 Wh (41.4%) volts: 11.2 min: 11.1
model: LGC 45N1153 type: Li-ion serial: <filter> status: not charging
CPU:
Info: model: Intel Core i7-4910MQ bits: 64 type: MT MCP arch: Haswell gen: core 4 level: v3
note: check built: 2013-15 process: Intel 22nm family: 6 model-id: 0x3C (60) stepping: 3
microcode: 0x28
Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache: L1: 256 KiB
desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB L3: 8 MiB desc: 1x8 MiB
Speed (MHz): avg: 2223 high: 2274 min/max: 800/3900 scaling: driver: intel_cpufreq
governor: ondemand cores: 1: 2229 2: 2274 3: 2198 4: 2252 5: 2247 6: 2185 7: 2170 8: 2229
bogomips: 46292
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities:
Type: gather_data_sampling status: Not affected
Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
Type: mds mitigation: Clear CPU buffers; SMT vulnerable
Type: meltdown mitigation: PTI
Type: mmio_stale_data status: Unknown: No mitigations
Type: reg_file_data_sampling status: Not affected
Type: retbleed status: Not affected
Type: spec_rstack_overflow status: Not affected
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Retpolines; IBPB: conditional; IBRS_FW; STIBP: conditional; RSB
filling; PBRSB-eIBRS: Not affected; BHI: Not affected
Type: srbds mitigation: Microcode
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: Intel 4th Gen Core Processor Integrated Graphics vendor: Lenovo driver: i915 v: kernel
arch: Gen-7.5 process: Intel 22nm built: 2013 ports: active: eDP-1 empty: DP-1, DP-2, HDMI-A-1,
HDMI-A-2, VGA-1 bus-ID: 00:02.0 chip-ID: 8086:0416 class-ID: 0300
Device-2: NVIDIA GK208M [GeForce GT 730M] vendor: Lenovo driver: N/A alternate: nouveau
non-free: series: 470.xx+ status: legacy-active (EOL~2023/24) arch: Kepler code: GKxxx
process: TSMC 28nm built: 2012-18 pcie: gen: 1 speed: 2.5 GT/s lanes: 8 link-max: gen: 3
speed: 8 GT/s bus-ID: 02:00.0 chip-ID: 10de:1290 class-ID: 0300
Device-3: Chicony Integrated Camera type: USB driver: uvcvideo bus-ID: 2-12:3
chip-ID: 04f2:b39a class-ID: 0e02
Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.9 compositor: kwin_x11 driver: X:
loaded: modesetting unloaded: fbdev,vesa dri: crocus gpu: i915 display-ID: :0 screens: 1
Screen-1: 0 s-res: 1600x900 s-dpi: 96 s-size: 423x238mm (16.65x9.37") s-diag: 485mm (19.11")
Monitor-1: eDP-1 model: LG Display 0x03fc built: 2013 res: 1600x900 hz: 60 dpi: 132 gamma: 1.2
size: 309x174mm (12.17x6.85") diag: 355mm (14") ratio: 16:9 modes: 1600x900
API: OpenGL v: 4.6 Mesa 24.2.8-1mx23ahs renderer: Mesa Intel HD Graphics 4600 (HSW GT2)
direct-render: Yes
Audio:
Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio vendor: Lenovo ThinkPad T440p
driver: snd_hda_intel v: kernel bus-ID: 00:03.0 chip-ID: 8086:0c0c class-ID: 0403
Device-2: Intel 8 Series/C220 Series High Definition Audio vendor: Lenovo ThinkPad T440p
driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:8c20 class-ID: 0403
API: ALSA v: k6.1.0-33-amd64 status: kernel-api tools: alsamixer,amixer
Server-1: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse status: active
2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Intel Ethernet I217-LM vendor: Lenovo ThinkPad T440p driver: e1000e v: kernel
port: 4080 bus-ID: 00:19.0 chip-ID: 8086:153a class-ID: 0200
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-2: Intel Wireless 7260 driver: iwlwifi v: kernel modules: wl pcie: gen: 1
speed: 2.5 GT/s lanes: 1 bus-ID: 04:00.0 chip-ID: 8086:08b2 class-ID: 0280
IF: wlan0 state: down mac: <filter>
IF-ID-1: proton0 state: unknown speed: N/A duplex: N/A mac: N/A
IF-ID-2: pvpnksintrf1 state: unknown speed: N/A duplex: N/A mac: <filter>
Drives:
Local Storage: total: 3.2 TiB used: 556.79 GiB (17.0%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Dogfish Technology model: SSD 512GB size: 476.94 GiB
block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 1A0
scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 vendor: Western Digital model: WD20SPZX-22UA7T0 size: 1.82 TiB
block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 5400 serial: <filter>
rev: 1A01 scheme: GPT
ID-3: /dev/sdc maj-min: 8:32 type: USB vendor: Sabrent model: SABRENT size: 931.51 GiB
block-size: physical: 4096 B logical: 512 B type: N/A serial: <filter> rev: 0104 scheme: MBR
ID-4: /dev/sdd maj-min: 8:48 type: USB vendor: Kingston model: DataTraveler 2.0 size: 953.9 MiB
block-size: physical: 512 B logical: 512 B type: N/A serial: <filter> rev: 1.00 scheme: MBR
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
ID-1: / raw-size: 128 GiB size: 124.93 GiB (97.60%) used: 15.18 GiB (12.1%) fs: ext4
dev: /dev/sda3 maj-min: 8:3
ID-2: /boot raw-size: 1024 MiB size: 973.4 MiB (95.06%) used: 357.1 MiB (36.7%) fs: ext4
dev: /dev/sda2 maj-min: 8:2
ID-3: /boot/efi raw-size: 750 MiB size: 748.5 MiB (99.80%) used: 288 KiB (0.0%) fs: vfat
dev: /dev/sda1 maj-min: 8:1
ID-4: /tmp raw-size: 32 GiB size: 31.2 GiB (97.50%) used: 20.7 MiB (0.1%) fs: ext4
dev: /dev/sdb2 maj-min: 8:18
ID-5: /var raw-size: 128 GiB size: 124.93 GiB (97.60%) used: 6.09 GiB (4.9%) fs: ext4
dev: /dev/sdb5 maj-min: 8:21
Swap:
Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: partition size: 32 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sdb1
maj-min: 8:17
Sensors:
System Temperatures: cpu: 65.0 C mobo: N/A
Fan Speeds (RPM): fan-1: 3052
Repos:
Packages: 2628 pm: dpkg pkgs: 2614 libs: 1375 tools: apt,apt-get,aptitude,nala pm: rpm pkgs: 0
pm: flatpak pkgs: 14
No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list
1: deb [arch=amd64 signed-by=/usr/share/keyrings/brave-browser-archive-keyring.gpg] https://brave-browser-apt-release.s3.brave.com/ stable main
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://mirror.math.princeton.edu/pub/mxlinux/mx/repo/ bookworm main non-free
2: deb http://mirror.math.princeton.edu/pub/mxlinux/mx/repo/ bookworm ahs
Active apt repos in: /etc/apt/sources.list.d/protonvpn-stable.list
1: deb [signed-by=/usr/share/keyrings/protonvpn-stable-archive-keyring.gpg] https://repo.protonvpn.com/debian stable main
Info:
Processes: 327 Uptime: 27m wakeups: 2 Memory: 15.5 GiB used: 6.27 GiB (40.4%) Init: systemd
v: 252 target: graphical (5) default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI
Re: Blank screen at login
Posted: Fri Apr 18, 2025 6:27 am
by MarieSophie
j2mcgreg wrote: Mon Apr 14, 2025 3:00 pm
I was thinking about a bad block on the drive where MX is located but where the next block in the chain wasn't clearly defined when the bad one was replaced automatically from the cache of spares. The new user's login sequence would be written to an unused area of the drive.
Oh ! hum .... that's interesting. Could very well be. The drives are not new, several years old. The SMART pass green, but that doesn't mean it's all good.